Jeremy C. Reed
2006-Aug-10 22:40 UTC
[Dovecot] stale imap processes with 1.0.rc6 on FreeBSD
Was running dovecot-1.0.rc2 but many stale imap processes (only one user
of IMAP).
Switched to dovecot-1.0.rc6 but problem continued.
This is on FreeBSD 4 something. Maybe it has bug with kqueue??
I read messages about the stale imap processes on the list. It seems to
hit *BSD systems. But email about new release candidate indicated it
should be fixed.
I read on the pkgsrc commit list about --with-ioloop=best
So I configured with that and saw that the I/O loop method is now kqueue.
(I saved configure output and it was poll before).
But the stale imap processes problem continues.
For one user over past couple hours I have eight imap processes in "I"
state.
I have:
File offsets ........................ : 64bit
I/O loop method ..................... : kqueue
File change notification method ..... : kqueue
Building with SSL support ........... : yes (OpenSSL)
Building with IPv6 support .......... : yes
Building with pop3 server ........... : yes
Building with mail delivery agent .. : yes
Building with GSSAPI support ........ : no
Building with user database modules . : static prefetch passwd passwd-file
checkpassword (modules)
Building with password lookup modules : passwd passwd-file pam
checkpassword (modules)
Building with SQL drivers ............:
And I have:
protocols = imap pop3
protocol imap {
imap_client_workarounds = outlook-idle delay-newmail
}
(Just started using delay-newmail today.)
My maillogs don't show any problems.
The IMAP user tells me that Outlook says it has reset connections often.
I see multiple imap-login Login within a few minutes for this same user
who said received a connection reset in outlook at the same time.
Just received a screenshot that said:
Microsoft Office Outlook
Failed to update headers.
The TCP/IP connection unexpectedly terminated by the server.
Then also received an error (in Outlook I think), like:
imap session idle too long, connection reset
(I don't have or use Outlook myself so can't test myself.)
It is used for a lot of pop3 and seems fine with that. (It uses stunnel
for pop3s but not imaps for over a week to eliminate stunnel from our
troubleshooting).
Any ideas on troubleshooting this would be appreciated.
Jeremy C. Reed
Timo Sirainen
2006-Aug-10 23:32 UTC
[Dovecot] stale imap processes with 1.0.rc6 on FreeBSD
On Thu, 2006-08-10 at 17:40 -0500, Jeremy C. Reed wrote:> Was running dovecot-1.0.rc2 but many stale imap processes (only one user > of IMAP). > > Switched to dovecot-1.0.rc6 but problem continued.I don't really understand this problem.. Is this user using SSL? What if you try the attached patch, does it change anything?> For one user over past couple hours I have eight imap processes in "I" > state.Could you get process traces and gdb backtraces from them? See http://dovecot.org/bugreport.html#hangs -------------- next part -------------- A non-text attachment was scrubbed... Name: ssl-change.diff Type: text/x-patch Size: 629 bytes Desc: not available URL: <http://dovecot.org/pipermail/dovecot/attachments/20060811/2fcc8f4f/attachment-0002.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 191 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20060811/2fcc8f4f/attachment-0003.bin>
Jeremy C. Reed
2006-Aug-10 23:44 UTC
[Dovecot] stale imap processes with 1.0.rc6 on FreeBSD
> On Thu, 2006-08-10 at 17:40 -0500, Jeremy C. Reed wrote: > > Was running dovecot-1.0.rc2 but many stale imap processes (only one user > > of IMAP). > > > > Switched to dovecot-1.0.rc6 but problem continued. > > I don't really understand this problem.. Is this user using SSL? What if > you try the attached patch, does it change anything?No ssl as far as I know. (I tried to explain in my previous email: no imaps in protocols and not using stunnel for imaps for over week. Also the end user said stopped using imaps over a week ago to make sure that was not the problem.) I didn't try the patch yet as it looks to be for SSL only.> > For one user over past couple hours I have eight imap processes in "I" > > state. > > Could you get process traces and gdb backtraces from them? See > http://dovecot.org/bugreport.html#hangsAttaching to program: /local/service/dovecot/libexec/dovecot/imap, process 49042 Reading symbols from /usr/lib/libc.so.4...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. 0x2811d590 in kevent () from /usr/lib/libc.so.4 (gdb) bt full #0 0x2811d590 in kevent () from /usr/lib/libc.so.4 No symbol table info available. #1 0x80a8b20 in event_callback (context=0x80d8030) at ioloop-notify-kqueue.c:41 ctx = (struct ioloop_notify_handler_context *) 0x80d8030 io = (struct io *) 0x16b ev = {ident = 135045792, filter = 1, flags = 0, fflags = 134910204, data = 135098368, udata = 0x80dd050} #2 0x80a9230 in io_loop_handler_run (ioloop=0x80d6000) at ioloop-poll.c:203 ctx = (struct ioloop_handler_context *) 0x80ca140 pollfd = (struct pollfd *) 0x2 tv = {tv_sec = 0, tv_usec = 430177} io = (struct io *) 0x80ca540 t_id = 2 msecs = 363 ret = 0 call = 363 #3 0x80a8915 in io_loop_run (ioloop=0x80d6000) at ioloop.c:274 ioloop = (struct ioloop *) 0x80d6000 #4 0x806104d in main (argc=1, argv=0xbfbffa74, envp=0xbfbffa7c) at main.c:273 No locals. #5 0x8055ac9 in _start () No symbol table info available.
Timo Sirainen
2006-Aug-11 01:56 UTC
[Dovecot] stale imap processes with 1.0.rc6 on FreeBSD
On Thu, 2006-08-10 at 17:40 -0500, Jeremy C. Reed wrote:> I read on the pkgsrc commit list about --with-ioloop=best > > So I configured with that and saw that the I/O loop method is now kqueue. > (I saved configure output and it was poll before).What about --with-ioloop=poll --with-notify=none Are everyone who are having these stale imap process problems running BSDs? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 191 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20060811/0f0e304a/attachment.bin>