pop3s terminated abnormally, signaled to death.
Adam Tworkowski
atworkowski at masterfile.com
Wed Jan 11 20:09:40 CET 2006
Hi,
I had a situation yesterday were POP3 suddenly became inaccessible.
IMAP and mail delivery had no issue. At one point the server load when
to 40 because of the pop3d. Eventually a restore was done from backups.
Does anyone have insight into this?
The only reference I can find to "signaled to death" [sic] is in
relation to Berkley DB but I haven't found anything useful about "25".
Any pointers would be appreciated.
/kolab/var/imap/logs/master.log
Jan 10 11:44:38 mail <debug> master[30674]: about to
exec /kolab/bin/pop3d
Jan 10 11:44:38 mail <error> master[6351]: process 30672 exited,
signaled to death by 25
Jan 10 11:44:38 mail <warning> master[6351]: service pop3s pid 30672 in
READY state: terminated abnormally
Jan 10 11:44:38 mail <debug> master[30675]: about to
exec /kolab/bin/pop3d
Jan 10 11:44:38 mail <error> master[6351]: process 30674 exited,
signaled to death by 25
SuSE9.2 with Kolab 2.0 (which is due to be upgraded this month).
Thanks,
Adam
--
Regards,
Adam Tworkowski, atworkowski at masterfile.com
Systems Administrator, Computer Department
Masterfile Corporation, www.masterfile.com
************************************************************************
This email message is intended only for the named recipient(s) above and
may contain information that is privileged, confidential, subject to
copyright and/or exempt from disclosure under applicable law. You are
hereby notified that any unauthorized use of this transmission is
strictly prohibited. If you are not the named recipient(s), please
immediately notify the sender and delete this email message.
************************************************************************
More information about the users
mailing list