From: Lawrence Greenfield (leg plus at andrew dot cmu dot edu)
Date: Fri Nov 02 2001 - 15:36:26 EST
Date: Wed, 31 Oct 2001 01:50:21 -0600
From: John Wade <>
Hi Cyrus Experts,
Back on September 4, 2001, there was a discussion on this list
about a locking problem in Cyrus 2.0.16 where an imapd process
would get a lock on a seen file and not release it an all other
attempts to access that mailbox either via imapd or lmptd would
await the lock. There was a another post about some workaround
scripts on 10/24, but I never saw a posting if anyone found the
root cause.
I have a server sitting in this situation right now and I was
wondering if there was anything I could do to help debug this
problem.
from gdb, the backtrace on the offending imapd process (PID 3098)
is:
This doesn't seem to be the offending process; it's the open
demonstrating the symptom, but much more important is the process that
is holding the lock that it can't get.
lsof on the file that it is attempting to lock ("print filename" from
gdb) will show what process is actually holding the lock.
Larry
|
|
|