thr3ads.net - dovecot - [Dovecot] Dovecot hangs randomly [Jul 2005]

If this information is useful, please help other people find it:
Share via:

Jacob Elder

2005-Jul-28 16:19 UTC

[Dovecot] Dovecot hangs randomly

I have been run into a weird problem with dovecot. We have 4  
identical servers running dovecot, serving both IMAP and POP3  
clients. Every few hours, clients start timing out after the PASS  
command. Here is what the process tree looks like at that time:

  6718 ?        Ss     0:00 /usr/sbin/dovecot
6719 ?        S      0:00  \_ dovecot-auth
6881 ?        S      0:00  |   \_ dovecot-auth
6883 ?        S      0:00  |   \_ dovecot-auth
6890 ?        S      0:00  |   \_ dovecot-auth
6928 ?        S      0:00  |   \_ dovecot-auth
6929 ?        S      0:00  |   \_ dovecot-auth
6934 ?        S      0:00  |   \_ dovecot-auth
6936 ?        S      0:00  |   \_ dovecot-auth
6939 ?        S      0:00  |   \_ dovecot-auth
6720 ?        S      0:00  \_ imap-login
6721 ?        S      0:00  \_ imap-login
6722 ?        S      0:00  \_ imap-login
6782 ?        S      0:00  \_ pop3-login
6808 ?        S      0:00  \_ pop3-login
6884 ?        S      0:00  \_ pop3-login
6885 ?        S      0:00  \_ pop3-login
6886 ?        S      0:00  \_ pop3-login
6887 ?        S      0:00  \_ pop3-login
6888 ?        S      0:00  \_ pop3-login
6889 ?        S      0:00  \_ pop3-login
6931 ?        S      0:00  \_ pop3-login
6937 ?        S      0:00  \_ pop3-login
6940 ?        S      0:00  \_ pop3-login

After running invoke-rc.d dovecot stop, the process tree looks like  
this:

6782 ?        S      0:00 pop3-login
6808 ?        S      0:00 pop3-login
6881 ?        S      0:00 dovecot-auth
6883 ?        S      0:00 dovecot-auth
6884 ?        S      0:00 pop3-login
6885 ?        S      0:00 pop3-login
6886 ?        S      0:00 pop3-login
6887 ?        S      0:00 pop3-login
6889 ?        S      0:00 pop3-login
6890 ?        S      0:00 dovecot-auth
6928 ?        S      0:00 dovecot-auth
6929 ?        S      0:00 dovecot-auth
6931 ?        S      0:00 pop3-login
6934 ?        S      0:00 dovecot-auth
6936 ?        S      0:00 dovecot-auth
6939 ?        S      0:00 dovecot-auth

If I run "killall -9 dovecot-auth pop3-login; invoke-rc.d dovecot  
start", service resumes for a few hours. This happens both on 2.6.8  
and 2.4.27. This is Debian testing, 512 MB RAM, about 20 users per  
server. We use libnss-ldap and libpam-ldap for all users other than  
root. Samba, SSH, saslauthd (for Postfix), login, etc all work as  
expected. There is a 5th server that is identical to the other 4  
except is NOT using libpam-ldap, and dovecot does not hang on this  
machine. Any ideas?

--
Jacob Elder

Jacob Elder

2005-Jul-31 01:08 UTC

head link

[Dovecot] Re: Dovecot hangs randomly

Our logs are filled with messages like this:

Jul 30 09:53:57 chatham dovecot-auth: Login process has too old  
(124s) requests, killing it.
Jul 30 09:56:17 chatham dovecot-auth: Login process has too old  
(124s) requests, killing it.
Jul 30 09:57:17 chatham dovecot-auth: Login process has too old  
(124s) requests, killing it.
Jul 30 09:58:17 chatham dovecot-auth: Login process has too old  
(124s) requests, killing it.
Jul 30 09:58:52 chatham dovecot-auth: Login process has too old  
(122s) requests, killing it.
Jul 30 10:01:51 chatham dovecot: login: received another "not  
listening" notification (if you can't login at all, see src/lib/ 
fdpass.c)
Jul 30 10:02:17 chatham dovecot-auth: Login process has too old  
(124s) requests, killing it.
Jul 30 10:03:52 chatham dovecot-auth: Login process has too old  
(122s) requests, killing it.
Jul 30 10:07:07 chatham dovecot-auth: Login process has too old  
(124s) requests, killing it.
Jul 30 10:07:07 chatham dovecot-auth: Login process has too old  
(124s) requests, killing it.
Jul 30 10:07:07 chatham dovecot-auth: Login process has too old  
(125s) requests, killing it.
Jul 30 10:07:17 chatham dovecot-auth: Login process has too old  
(123s) requests, killing it.
Jul 30 10:07:52 chatham dovecot-auth: Login process has too old  
(123s) requests, killing it.
Jul 30 10:09:07 chatham dovecot: Killed with signal 15
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (13)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (15)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (16)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (18)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (24)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (7)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (10)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (11)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (17)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (27)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (20)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (22)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (23)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (29)
Jul 30 10:09:07 chatham dovecot-auth: I/O leak: 0x8054940 (30)

Can anyone decipher this?

--
Jacob Elder



On Jul 28, 2005, at 12:19 PM, Jacob Elder wrote:
> I have been run into a weird problem with dovecot. We have 4  
> identical servers running dovecot, serving both IMAP and POP3  
> clients. Every few hours, clients start timing out after the PASS  
> command. Here is what the process tree looks like at that time:
>
>  6718 ?        Ss     0:00 /usr/sbin/dovecot
> 6719 ?        S      0:00  \_ dovecot-auth
> 6881 ?        S      0:00  |   \_ dovecot-auth
> 6883 ?        S      0:00  |   \_ dovecot-auth
> 6890 ?        S      0:00  |   \_ dovecot-auth
> 6928 ?        S      0:00  |   \_ dovecot-auth
> 6929 ?        S      0:00  |   \_ dovecot-auth
> 6934 ?        S      0:00  |   \_ dovecot-auth
> 6936 ?        S      0:00  |   \_ dovecot-auth
> 6939 ?        S      0:00  |   \_ dovecot-auth
> 6720 ?        S      0:00  \_ imap-login
> 6721 ?        S      0:00  \_ imap-login
> 6722 ?        S      0:00  \_ imap-login
> 6782 ?        S      0:00  \_ pop3-login
> 6808 ?        S      0:00  \_ pop3-login
> 6884 ?        S      0:00  \_ pop3-login
> 6885 ?        S      0:00  \_ pop3-login
> 6886 ?        S      0:00  \_ pop3-login
> 6887 ?        S      0:00  \_ pop3-login
> 6888 ?        S      0:00  \_ pop3-login
> 6889 ?        S      0:00  \_ pop3-login
> 6931 ?        S      0:00  \_ pop3-login
> 6937 ?        S      0:00  \_ pop3-login
> 6940 ?        S      0:00  \_ pop3-login
>
> After running invoke-rc.d dovecot stop, the process tree looks like  
> this:
>
> 6782 ?        S      0:00 pop3-login
> 6808 ?        S      0:00 pop3-login
> 6881 ?        S      0:00 dovecot-auth
> 6883 ?        S      0:00 dovecot-auth
> 6884 ?        S      0:00 pop3-login
> 6885 ?        S      0:00 pop3-login
> 6886 ?        S      0:00 pop3-login
> 6887 ?        S      0:00 pop3-login
> 6889 ?        S      0:00 pop3-login
> 6890 ?        S      0:00 dovecot-auth
> 6928 ?        S      0:00 dovecot-auth
> 6929 ?        S      0:00 dovecot-auth
> 6931 ?        S      0:00 pop3-login
> 6934 ?        S      0:00 dovecot-auth
> 6936 ?        S      0:00 dovecot-auth
> 6939 ?        S      0:00 dovecot-auth
>
> If I run "killall -9 dovecot-auth pop3-login; invoke-rc.d dovecot  
> start", service resumes for a few hours. This happens both on 2.6.8  
> and 2.4.27. This is Debian testing, 512 MB RAM, about 20 users per  
> server. We use libnss-ldap and libpam-ldap for all users other than  
> root. Samba, SSH, saslauthd (for Postfix), login, etc all work as  
> expected. There is a 5th server that is identical to the other 4  
> except is NOT using libpam-ldap, and dovecot does not hang on this  
> machine. Any ideas?
>
> --
> Jacob Elder
>
>
>
>

Timo Sirainen

2005-Aug-14 22:24 UTC

head link

[Dovecot] Dovecot hangs randomly

On Thu, 2005-07-28 at 12:19 -0400, Jacob Elder wrote:> I have been run into a weird problem with dovecot. We have 4  
> identical servers running dovecot, serving both IMAP and POP3  
> clients. Every few hours, clients start timing out after the PASS  
> command. Here is what the process tree looks like at that time:
> 
>   6718 ?        Ss     0:00 /usr/sbin/dovecot
> 6719 ?        S      0:00  \_ dovecot-auth
> 6881 ?        S      0:00  |   \_ dovecot-auth
> 6883 ?        S      0:00  |   \_ dovecot-auth
> 6890 ?        S      0:00  |   \_ dovecot-auth
> 6928 ?        S      0:00  |   \_ dovecot-auth
> 6929 ?        S      0:00  |   \_ dovecot-auth
> 6934 ?        S      0:00  |   \_ dovecot-auth
> 6936 ?        S      0:00  |   \_ dovecot-auth
> 6939 ?        S      0:00  |   \_ dovecot-auth
..> If I run "killall -9 dovecot-auth pop3-login; invoke-rc.d dovecot  
> start", service resumes for a few hours. This happens both on 2.6.8  
> and 2.4.27. This is Debian testing, 512 MB RAM, about 20 users per  
> server. We use libnss-ldap and libpam-ldap for all users other than  
> root. Samba, SSH, saslauthd (for Postfix), login, etc all work as  
> expected. There is a 5th server that is identical to the other 4  
> except is NOT using libpam-ldap, and dovecot does not hang on this  
> machine. Any ideas?
Looks like you have several dovecot-auth processes hanging there.
Dovecot creates a new process for each PAM lookup, so that's probably
the reason. You could try to check with strace what those dovecot-auth
processes are doing? I guess Dovecot should itself also do some
timeouting and start killing PAM processes if they don't finish within a
minute..

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20050815/efdf633c/attachment.bin>

Reasonably Related Threads

Search for more possibly parallel threads

dovecot - Jul 2005 - Dovecot hangs randomly

[Dovecot] Dovecot hangs randomly

[Dovecot] Re: Dovecot hangs randomly

[Dovecot] Dovecot hangs randomly

Reasonably Related Threads