AW: Cyrus restart: ctl_deliver takes very long!

[Christoph Nagelreiter]

Hello,

where is the difference between the following cyrus.conf files (check: EVENTS brackets --> are both cyris.conf files okay) and do i have to put the command "ctl_deliver -r" in the START section?

I got the following warning messages:

Mar 10 18:14:01 oscar-mail ctl_mboxlist: ctl_mboxlist -c is deprecated: use ctl_cyrusdb -c instead^H


START {
   mboxlist cmd="ctl_cyrusdb -r"
   deliver cmd="ctl_deliver -r"
}

SERVICES {
   imap cmd="imapd" listen="imap" prefork=5
   imaps cmd="imapd -s" listen="imaps" prefork=0
   pop3 cmd="pop3d" listen="pop3" prefork=5
   pop3s cmd="pop3d -s" listen="pop3s" prefork=0
   sieve cmd="timsieved" listen="sieve" prefork=0
   lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0
}

EVENTS {
   checkpoint cmd="ctl_mboxlist -c" period=5

   delprune cmd="ctl_deliver -E 3" period=1440
}




START {
   mboxlist cmd="ctl_cyrusdb -r"
   deliver cmd="ctl_deliver -r"
}

SERVICES {
   imap cmd="imapd" listen="imap" prefork=5
   imaps cmd="imapd -s" listen="imaps" prefork=0
   pop3 cmd="pop3d" listen="pop3" prefork=5
   pop3s cmd="pop3d -s" listen="pop3s" prefork=0
   sieve cmd="timsieved" listen="sieve" prefork=0
   lmtpunix cmd="lmtpd" listen="/var/imap/socket/lmtp" prefork=0
}

EVENTS {
   checkpoint cmd="ctl_cyrusdb -c" period=5

   delprune cmd="ctl_deliver -E 3" period=1440
}

Regards,
Chris

-----Ursprüngliche Nachricht-----
Von: Andreas [mailto:andreas at conectiva.com.br] 
Gesendet: Montag, 08. März 2004 15:24
An: Christoph Nagelreiter
Cc: info-cyrus at lists.andrew.cmu.edu
Betreff: Re: Cyrus restart: ctl_deliver takes very long!


On Mon, Mar 08, 2004 at 02:40:28AM +0100, Christoph Nagelreiter wrote:
> ERRORS in cyrus.log  (is this normal???):
> 
> Mar  8 02:24:01 oscar-mail ctl_deliver[5263]: DBERROR db4: 5 lockers
(...)

Take a look at this text: http://www.openldap.org/faq/index.cgi?_highlightWords=locks&file=893

It's written for openldap, but explains several important Berkeley DB configuration parameters. In particular:

"On a very busy system you might see error messages talking about running out of locks, lockers, or lock objects. Usually the default values are plenty, and in older versions of the BDB library the errors were more likely due to library bugs than actual system load. However, it is possible that you have actually run out of lock resources due to heavy system usage. If this happens, you should read about the set_lk_max_lockers[1], set_lk_max_locks[2], and set_lk_max_objects[3] keywords."

1. http://www.sleepycat.com/docs/api_c/env_set_lk_max_lockers.html
2. http://www.sleepycat.com/docs/api_c/env_set_lk_max_locks.html
3. http://www.sleepycat.com/docs/api_c/env_set_lk_max_objects.html

The links above talk about the C api, but don't get alarmed, these paremeters can be set with a DB_CONFIG configuration file located in the DB environment home.

I also suppose the db_stat utility can be used to diagnose this.

---
Home Page: http://asg.web.cmu.edu/cyrus
Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html