Yes Timo, found "Warning: Killed with signal 15" in the log. What can be "something" that killed dovecot?

Mar 26 17:18:43 Info: pop3-login: Login: user=<xxx>, method=PLAIN, rip=x.x.x.x, lip=y.y.y.y Mar 26 17:18:43 Info: POP3(xxx): Disconnected: Logged out top=0/0, retr=0/0, del=0/207, size=35162343 Mar 26 17:18:43 Warning: Killed with signal 15 Mar 26 17:18:43 Info: pop3-login: Disconnected: Shutting down (no auth attempts): rip=x.x.x.x, lip=y.y.y.y Mar 26 17:18:43 Info: pop3-login: Disconnected: Shutting down (auth failed, 11997592 attempts): user=<??�>, method=??� Mar 26 17:18:43 Panic: pop3-login: file client-common.c: line 25 (client_unlink): assertion failed: (clients_count > 0) Mar 26 17:18:46 Info: dovecot v1.1.11 starting up (core dumps disabled)

Thanks,

Long Le

On Mon, 2009-03-30 at 01:54 -0400, Timo Sirainen wrote:

Well. There are two problems: First is that it's crashing, which is
clearly a bug. It just shouldn't happen. If you upgraded to v1.1.13
you would probably get a core dump, and that might be useful in
figuring out the crash (http://dovecot.org/bugreport.html), but the
real problem appears to be in the Disconnected reason. "Shutting down"
means that the whole Dovecot is being shut down. Which most likely
means that something killed dovecot master process. Do you see such a
line in logs? Probably "Warning: killed with signal <something>".

On Mar 29, 2009, at 11:41 PM, Long Le Dinh wrote:

...

Any help on this? It happens more frequently :(. Is this related to
LDAP authen?

Thanks,

Long Le

On Fri, 2009-03-27 at 13:14 +0700, Long Le Dinh wrote:

...

Hi,

I got below log in last 2 days, I have to restart dovecot as pop3- login failed and service cannot respond.

Mar 26 14:19:31 Info: pop3-login: Disconnected: Shutting down (auth
failed, 1 attempts): method=PLAIN, rip=x.x.x.x Mar 26 14:19:31 Info: pop3-login: Disconnected: Shutting down
(tried to use disabled plaintext auth): method=??<B7> Mar 26 14:19:31 Panic: pop3-login: file client-common.c: line 25
(client_unlink): assertion failed: (clients_count > 0) Mar 26 14:19:31 Error: child 31902 (login) killed with signal 6
(ip=x.x.x.x)

My system info: dovecot -n # 1.1.11: /etc/dovecot.conf # OS: Linux 2.6.18-8.el5 i686 CentOS release 5 (Final) ext3 log_path: /var/log/dovecot.log login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_gid: 100 mail_location: maildir:/home/%u/Maildir mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: verbose: yes debug: yes passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: passwd userdb: driver: ldap args: /etc/dovecot-ldap.conf

We're using Maildir format, no NFS. Any help/clue is appreciated.

Thanks,

Long Le

No, it happens randomly.

Long Le

On Tue, 2009-03-31 at 12:16 -0400, Timo Sirainen wrote:

On Mar 30, 2009, at 2:59 AM, Long Le Dinh wrote:

...

Yes Timo, found "Warning: Killed with signal 15" in the log. What
can be "something" that killed dovecot?

Does it happen at the same time every day? If so, it's most likely a
cronjob. Otherwise I'm not sure, are there more admins and one of them
would be restarting Dovecot? In any case:

...

Mar 26 17:18:43 Warning: Killed with signal 15 .. Mar 26 17:18:46 Info: dovecot v1.1.11 starting up (core dumps
disabled)

There is only 3 second difference, so most likely /etc/init.d/dovecot
restart was called.

The crashes still shouldn't be happening though, but they're invisible
to users since they would have been disconnected in any case.