On Fri, 2011-02-25 at 10:12 -0500, Chris Hoogendyk wrote:
Feb 24 15:52:57 marlin dovecot: [ID 583609 local2.error] dovecot: child 21233 (login) killed with signal 16 (ip=128.119.55.8)
Signal 16 is SIGUSR1. Dovecot master process sends it to login processes when max number of login processes has been reached and it's telling the processes to kill their oldest connections.
But I don't know why the process itself would get killed. That's not intentional and I can't see any bugs in the code related to that either..
Feb 24 15:52:58 marlin dovecot: [ID 583609 local2.warning] dovecot: Killed with signal 15 (by pid=26750 uid=0 code=kill)
Note that the first line is logged as an error.
These items from the SMF service log for dovecot:
[ Feb 24 15:52:58 Stopping because process received fatal signal from outside the service. ] [ Feb 24 15:52:58 Executing stop method ("/etc/mail/svc/method/dovecot.init.d stop") ] Stopping Dovecot
You could try if you can reproduce this by killing one of the login processes with -USR1.