--On Monday, May 13, 2002 3:08 PM -0500 Dustin Puryear <[EMAIL PROTECTED]> wrote:
> We continue to have problems with Cyrus. Another poster mentioned they > have the same problem, but also didn't get any responses. Would one of > the developers please investigate if this is a bug? What's going on? This > is a real show stopper for us, and apparently for others as well. I haven't noticed that really.... > > Okay, we have Cyrus installed on FreeBSD 4.4-RELEASE: > > cyrus-imapd-2.0.16_1 The cyrus mail server, supporting POP3 and IMAP4 > protocols cyrus-imapd-2.0.16_2 The cyrus mail server, supporting POP3 and > IMAP4 protocols cyrus-sasl-1.5.24_7 RFC 2222 SASL (Simple Authentication > and Security Layer) cyrus-sasl-1.5.24_8 RFC 2222 SASL (Simple > Authentication and Security Layer) cyrus-sasl-1.5.27_2 RFC 2222 SASL > (Simple Authentication and Security Layer) So you are running Cyrus IMAPD 2.0.16 with Cyrus SASLv1 1.5.24_7? That's a litttle odd why not 2.1.2 or 2.1.3-BETA? > Every once in a while Cyrus stops responding to connections. Now, it does > ACCEPT the connection, but it doesn't seem to send. Okay, so lets say > that I stop Cyrus and it happens to work: > working.. > mercury# telnet mars 110 > Trying 10.0.0.5... > Connected to mars.actioncore.com. > Escape character is '^]'. > +OK <[EMAIL PROTECTED]> Cyrus POP3 v2.0.16 server > ready > > I get a new pop3d process: > > cyrus 1537 0.0 0.8 18836 2128 p0 S 9:52PM 0:00.03 pop3d: > pop3d: mercury.actioncore.com[10.0.0.1] (pop3d) > > And a TCP connection: > > mars# netstat -f inet -ln | grep 10.0.0.1 > tcp4 0 0 10.0.0.5.110 10.0.0.1.2060 > ESTABLISHED > > If I wait a few seconds to several minutes, Cyrus stops working: > > mercury# telnet mars 110 > Trying 10.0.0.5... > Connected to mars.actioncore.com. > Escape character is '^]' > ^C > > And the connection does exist (the connection was made from 10.0.0.1): > > mars# netstat -f inet -ln | grep 10.0.0.1 > tcp4 0 0 10.0.0.5.110 10.0.0.1.2057 ESTABLISHED > > Something I did notice is that when I run lsof that lsof seems to stall > after it hits some for the pop3d processes. Not sure if that is important > or just a fluke. > > What can we do to debug this further? What are some possible issues here > to consider? DNS? Corrupted database files? What? > > Regards, Dustin Well You know without further information like running gdb on the process, or giving us some detail from /var/log/messages and such. We wont be able to help you, ie is cyrus attempting to run recover over and over again and failing? As you wrote a very nice message, it lacked the common information required to help.
