Re: Locking problem in Cyrus 2.0.16 Revisited

2001-11-14 Thread John Wade
Hi All, Had another locking problem today and was able to get reasonably complete info. Unfortunately, I only had a limited time to debug since I di not identify the problem until long after it started.. So here goes. At the point I identified the problem, I had 6 blocked IMAP processes and

Re: Locking problem in Cyrus 2.0.16 Revisited

2001-11-10 Thread John Wade
OK, had another crash today, but unfortunately the symbol table info for the lib files was not loading properly so I could not get full details.I did a make clean in the lib directory, recompiled cyrus and tested gdb and now the symbol table is loading properly. Next time I should be able to

Re: Locking problem in Cyrus 2.0.16 Revisited

2001-11-02 Thread John Wade
Hi Larry, Thanks for the reply. Comments interspersed below: Lawrence Greenfield wrote: >This seems to mean that Cyrus uses the old style text file to store the >seen info rather than a Berkely DB. Is there a particular reason this >is defined this way by default? Is the Berkel

Re: Locking problem in Cyrus 2.0.16 Revisited

2001-11-02 Thread John Wade
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

Re: Locking problem in Cyrus 2.0.16 Revisited

2001-11-02 Thread Lawrence Greenfield
Date: Fri, 02 Nov 2001 20:49:17 + From: Simon Loader <[EMAIL PROTECTED]> > > 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

Re: Locking problem in Cyrus 2.0.16 Revisited

2001-11-02 Thread Simon Loader
> > 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

Re: Locking problem in Cyrus 2.0.16 Revisited

2001-11-02 Thread Lawrence Greenfield
Date: Fri, 02 Nov 2001 09:07:32 -0600 From: John Wade <[EMAIL PROTECTED]> I did have a couple of questions that came out from looking at the source. First, in seen_db.c although all the comments reference the Berkely DB structure for the seen file, there is a define statement

Re: Locking problem in Cyrus 2.0.16 Revisited

2001-11-02 Thread Lawrence Greenfield
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 ot

Re: Locking problem in Cyrus 2.0.16 Revisited

2001-11-02 Thread John Wade
Hi All, I am trying to work through our file locking problem in Cyrus 2.0.16. Since the problem appears to be tied to locking the seen file, I have recompiled with SEEN_DEBUG turned on to see if I can get any more info. I will let you know anything I find. Any other suggestions on how to gather

Locking problem in Cyrus 2.0.16 Revisited

2001-10-30 Thread 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 wa