Sorry, I meant turning them off for mailboxes. We'll still use it for
deliverdb stuff, because deadlocks there seem to be much less disruptive
and happen less often for some reason. And, of course, it would hurt
performance a lot.
Michael
--On Tuesday, January 15, 2002 20:11:59 -0500 Lawren
Are the database locking gremlins (referred to below) the same issue as the
locking lmtp problem that I and many others posted to the list about?
Did I miss something, or does using a flat file for the database rectify the
problem where users cannot move or delete messages until the Imap PID for
The database deadlocking gremlins usually cause an lmtpd or imapd
process to crash while holding a database lock. The number one thing
is to find out which process crashed, why it crashed, and to stop it.
The master should syslog whenever a process exiting abnormally
("grep signal /var/log/cyru
You've apparently made the aquaintance of the database deadlocking
gremlins. We've been running into this one since upgrading to 2.0.16, and
have yet to find a good solution for it. Because we've finally gotten sick
of them, we're about to install a version of cyrus that was recompiled
using
Yesterday I started to see (for the first time since upgrading to
cyrus-2.0.16 on Jan 4th) a lot of messages from sendmail which
indicated: "Could not connect to socket /var/imap/socket/lmtp:
Connection refused by localhost". I checked and there were no lmtpd
processes running, even though my
