Cyrus restart: ctl_deliver takes very long!

[Andreas]

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