Hi Larry,
Thanks for the info, I finally had to shutdown Cyrus and restart since
the user's Mailbox had been locked out since 10/24. The problem
occurred 7 or 8 times this week on our other mail server however, so I am
sure I will be able to reproduce it next week and try to get more info.
I did save an lsof from this incident but I wasn't aware of how to get the
filename out of gdb before. From the backtrace, I assumed it was trying
to get a lock on the seen file, but I will verify for sure next time.
Thanks for the help, you folks have really put together a nice package
and we all appreciate the support you provide through this list.
John
Lawrence Greenfield wrote:
> Date: Wed, 31 Oct 2001 01:50:21 -0600
> From: John Wade <[EMAIL PROTECTED]>
>
> 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
