That stack trace from process 15506 looks like a victim as well. It also
is blocked trying to acquire the exclusive parse/append lock on the same
file. You can try killing it to see if that clears the other stuck
processes, but I don't think that it will.
Check the stack of the other stuck processes. We're looking for something
other than
#0 0x1033daa4 in flock () from /usr/lib/libc.so.12
#1 0x000240a4 in lock_work (lock=0xefffe058 "/tmp/.708.25204", sb=0xefffdf18,
op=2, pid=0x0) at env_unix.c:1345
at the top of the stack.
Oh, yeah, are there any interesting syslog messages from any of the
imapds?
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
_______________________________________________
Imap-uw mailing list
Imap-uw@u.washington.edu
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
