cyr_expire, deliver.db and other curiosities

[Alain Spineux]

On Jan 30, 2008 1:06 PM, Sven Juergensen (KielNET)
<s.juergensen at kielnet.de> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi list,
>
> I could use an overview of how
> cyr_expire and the entry
> ~ delprune        cmd="/usr/sbin/cyr_expire -E 3"
> in the cyrus.conf within the START
> section works.
>
> Background is, that for some
> reason, every now and then cyrus
> decides that it is a good idea
> to resign and stop responding
> on the pop3/imap4 ports.

Here the problem is.

>
> This can be remedied by restarting
> cyrus in it's entirety but when
> doing this after a couple of months
> uptime, the cyr_expire kicks in and
> it takes >30 minutes to get it back
> to work:

Always by two they are !
>
> - ---8<---
> Jan 30 06:44:46 srv1 cyrus/master[32247]: about to exec /usr/sbin/cyr_expire
> Jan 30 06:44:48 srv1 cyrus/cyr_expire[32247]: duplicate_prune: pruning
> back 3 days
> Jan 30 06:44:48 srv1 cyrus/cyr_expire[32247]: mydelete: starting txn
> 2147483650
> Jan 30 06:44:48 srv1 cyrus/cyr_expire[32247]: mydelete: committing txn
> 2147483650
> [entries omitted]
> Jan 30 06:58:31 srv1 cyrus/cyr_expire[32247]: duplicate_prune: purged
> 717903 out of 817184 entries
> Jan 30 06:58:31 srv1 cyrus/cyr_expire[32247]: expunged 0 out of 0
> messages from 0 mailboxes
> - --->8---
>
> Would it make sense to enter the
> above cyr_deliver command from the
> START section into the EVENT section
> or does this make things worse?

I always saw it in the EVENT section (in Kolab and fedora/centos distribution)
Here is the line in my kolab cyrus.conf

  delprune      cmd="cyr_expire -E 3" period=1440

>
> All this is just combatting the
> symptoms, not the reason. If anyone
> has an idea about what causes this,
> sizing of the hardware, underlying
> filesystem or harddisk technology,
> I'd be thankful for some pointers.

If you are speaking about unavailability at restart time ...
This is probably bacause cyr_expire is reading all maiboxes,
searching for emails to delete, and this _before_ to start the
first service because of the START section.
In the EVENTS you should just get some slowdown.

For your main problem, without more info( log ) , I cannot help you.

>
> The server itself has to deal with
> about 20k inboxes.
>
> Thanks and best regards,
>
> sven03
>
> Mit freundlichen Gruessen
>
> i. A. Sven Juergensen
>
> - --
> Fachbereich
> Informationstechnologie
>
> KielNET GmbH
> Gesellschaft fuer Kommunikation
> Preusserstr. 1-9, 24105 Kiel
>
> Telefon : 0431 / 2219-053
> Telefax : 0431 / 2219-005
> E-Mail  : s.juergensen at kielnet.de
> Internet: http://www.kielnet.de
>
> AS# 25295
>
> Key fingerprint:
> 65B6 90FC 010A 39CE DCA5  336D 9C45 3B7A B02D E132
>
> "221 2.7.0 Error: I can break rules, too. Goodbye."
>
> Geschaeftsfuehrer Eberhard Schmidt
> HRB 4499 (Amtsgericht Kiel)
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.7 (GNU/Linux)
>
> iD8DBQFHoGg6nEU7erAt4TIRAhIvAJoC7d6rj8hsfcw9r/CZUh4d5Kj1GgCfXtU2
> SddW0Sv5p9o0/3ev+JGFwrM=
> =VBI7
> -----END PGP SIGNATURE-----
> ----
> Cyrus Home Page: http://cyrusimap.web.cmu.edu/
> Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you