followup: stuck lmtpd processes

Rob Siemborski rjs3 at andrew.cmu.edu
Wed Sep 24 10:57:39 EDT 2003


On Wed, 24 Sep 2003, Scott Adkins wrote:

> Also, when we find the specific imaps process that happens to have the
> cyrus.header lock file opened for writing and has it locked, if we kill
> it off, we find that the write lock goes to another imaps process or to
> one of the LMTP processes and gets stuck there... we kill that one off
> and it goes to the next one and gets stuck.  We never saw a case where
> all the other processes became unstuck and the problem went away.

So, if these processes are getting stuck -- what are they getting stuck
waiting for?  Processes don't acquire a lock and then just stop.

> As a consquence, the only solution we have when we see the problem is to
> restart the Cyrus server (we usually wait until after work hours at least).
> I am not convinced the patch described below has helped us much, as when
> we saw the LMTP processes stacking up, it was right in our face and we
> could deal with it sooner than later.

I agree.

-Rob

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456
Research Systems Programmer * /usr/contributed Gatekeeper





More information about the Info-cyrus mailing list