Displaying 3 results from an estimated 3 matches for "123s".
Did you mean:
123
2005 Feb 03
2
dovecot-auth hangs with IO leak
...n failure; logname= uid=0 euid=0 tty= ruser= rhost=127.0.0.1
Feb 3 18:16:19 eta dovecot-auth: (pam_unix) check pass; user unknown
After recent upgrades from probably 0.99.10 to 0.99.13, these lines begin to appear in /var/log/mail.log:
Feb 3 16:31:00 eta dovecot-auth: Login process has too old (123s) requests, killing it.
Feb 3 16:31:00 eta dovecot-auth: Login process has too old (124s) requests, killing it.
And some more like this, which shows the problem:
Feb 3 16:45:23 eta dovecot-auth: I/O leak: 0x8054940 (13)
Feb 3 16:45:23 eta dovecot-auth: I/O leak: 0x8054940 (14)
Feb 3 16:45:23 et...
2005 Jul 28
2
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
2004 Feb 05
0
Password prompt
...O leak: 0x80848d0 (1)
Feb 4 12:02:05 geonosis pop3: I/O leak: 0x8050cc0 (0)
Feb 4 12:02:05 geonosis pop3: I/O leak: 0x80848d0 (1)
and:
Feb 4 11:35:02 geonosis dovecot-auth: Login process has too old (125s)
requests, killing it.
Feb 4 11:35:50 geonosis dovecot-auth: Login process has too old (123s)
requests, killing it.
This is the most recent version of Dovecot.
IMAP appears to work pretty flawlessly.
Please advise
Thanks
z