Re: [Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
On Wed, 2009-04-29 at 14:52 -0400, jsie...@psu.edu wrote: This is 64bit AIX 5.3. Looking through previous versions of dovecot, I see this warning. I didn't realize this was something bad until today. My environment uses mbox/mbox-snarf plugin. The message in the logs is: local0.log.20090429:Apr 29 12:41:16 hostname dovecot: IMAP(jsiegle): Timeout leak: 1100054c0 Fixed: http://hg.dovecot.org/dovecot-1.2/rev/66b6cd495702 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
On Wed, 29 Apr 2009, Timo Sirainen wrote: On Wed, 2009-04-29 at 14:52 -0400, jsie...@psu.edu wrote: This is 64bit AIX 5.3. Looking through previous versions of dovecot, I see this warning. I didn't realize this was something bad until today. It's not exactly bad. It gets logged only when the process is exiting. But it shouldn't be happening either. local0.log.20090429:Apr 29 12:41:16 hostname dovecot: IMAP(jsiegle): Timeout leak: 1100054c0 How easily can you reproduce this? For example if you do: telnet localhost 143 1 login user pass 2 select inbox 3 logout Oh lovely. Now when I do these steps I see in the logs: Apr 30 08:06:23 tr27n12.aset.psu.edu syslog: PSU mbox-snarf name is INBOX Apr 30 08:06:23 tr27n12.aset.psu.edu dovecot: Panic: IMAP(tstem38): file istream-mail-stats.c: line 75: assertion failed: (ret != -1 || stream-istream.eof || stream-istream.stream_errno != 0) Apr 30 08:06:23 tr27n12.aset.psu.edu dovecot: child 630886 (imap) killed with signal 6 I don't get this error for other folders, just the INBOX. I don't get the timeout leak very often. Maybe 15 times a day total for multiple users. I'll do some more debugging of that problem and report back. -Jonathan smime.p7s Description: S/MIME Cryptographic Signature
Re: [Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
On Apr 29, 2009, at 2:58 PM, Timo Sirainen wrote: On Wed, 2009-04-29 at 14:52 -0400, jsie...@psu.edu wrote: This is 64bit AIX 5.3. Looking through previous versions of dovecot, I see this warning. I didn't realize this was something bad until today. It's not exactly bad. It gets logged only when the process is exiting. But it shouldn't be happening either. local0.log.20090429:Apr 29 12:41:16 hostname dovecot: IMAP(jsiegle): Timeout leak: 1100054c0 How easily can you reproduce this? For example if you do: telnet localhost 143 1 login user pass 2 select inbox 3 logout Does it get logged? What if you select some other mailbox instead? Yes it gets logged. I did your steps and reproduced. I also did login;select;close;logout and that also gave me the error. smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
On Thu, 2009-04-30 at 15:04 -0400, Jonathan Siegle wrote: telnet localhost 143 1 login user pass 2 select inbox 3 logout Does it get logged? What if you select some other mailbox instead? Yes it gets logged. I did your steps and reproduced. I also did login;select;close;logout and that also gave me the error. What about another mailbox than INBOX? If it happens only with INBOX, the problem is mbox-snarf plugin. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
On Apr 30, 2009, at 3:06 PM, Timo Sirainen wrote: On Thu, 2009-04-30 at 15:04 -0400, Jonathan Siegle wrote: telnet localhost 143 1 login user pass 2 select inbox 3 logout Does it get logged? What if you select some other mailbox instead? Yes it gets logged. I did your steps and reproduced. I also did login;select;close;logout and that also gave me the error. What about another mailbox than INBOX? If it happens only with INBOX, the problem is mbox-snarf plugin. It doesn't do it on folders. so login;select folder;logout doesn't produce the error. smime.p7s Description: S/MIME cryptographic signature
[Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
This is 64bit AIX 5.3. Looking through previous versions of dovecot, I see this warning. I didn't realize this was something bad until today. My environment uses mbox/mbox-snarf plugin. The message in the logs is: local0.log.20090429:Apr 29 12:41:16 hostname dovecot: IMAP(jsiegle): Timeout leak: 1100054c0 In dbx(the AIX debugger) I see: $ dbx imap Type 'help' for help. reading symbolic information ... (dbx) gotoi 0x1100054c0 Goto address is not within current function or block. (set $unsafegoto to override) (dbx) set $unsafegoto (dbx) gotoi 0x1100054c0 stopped in cmd-append. at 0x1100054c0 0x1100054c0 (???) 0001 Invalid opcode. (dbx) where cmd-append.() at 0x1100054c0 If you need more info, don't hesitate to ask. Thanks, Jonathan
Re: [Dovecot] Timeout leak with dovecot version dovecot1.2(8985:f43bebab3dac)
On Wed, 2009-04-29 at 14:52 -0400, jsie...@psu.edu wrote: This is 64bit AIX 5.3. Looking through previous versions of dovecot, I see this warning. I didn't realize this was something bad until today. It's not exactly bad. It gets logged only when the process is exiting. But it shouldn't be happening either. local0.log.20090429:Apr 29 12:41:16 hostname dovecot: IMAP(jsiegle): Timeout leak: 1100054c0 How easily can you reproduce this? For example if you do: telnet localhost 143 1 login user pass 2 select inbox 3 logout Does it get logged? What if you select some other mailbox instead? (dbx) set $unsafegoto (dbx) gotoi 0x1100054c0 stopped in cmd-append. at 0x1100054c0 I don't think this is correct, because there are no timeout callbacks in cmd-append.c. signature.asc Description: This is a digitally signed message part
