it happened twice in last few weeks: the cleanup (part of postfix)
eats up all the cpu cycles and cannot be killed (even with -9).
I guess that means that it's stuck in system call - it looks like
kernel problem. any ideas on what to do (well, I know I can reboot:-)?
how to troubleshoot?
this is debian unstable, postfix 1.1.7-7, kernel 2.4.18. this doesn't
seem to be related to kernel upgrade (which I did long time ago), I am
not even sure if it's postfix related, it seems like updated some part
of postifx during may
following messages in syslog might be related (other than I've found
nothing suspicious):
Jun 20 11:12:02 localhost postfix/smtpd[6575]: warning: premature
end-of-input from public/cleanup socket while reading input attribute
name
Jun 20 11:12:02 localhost postfix/smtpd[6575]: fatal: unable to connect
to the public cleanup service
Jun 20 11:12:03 localhost postfix/master[505]: warning: process
/usr/lib/postfix/smtpd pid 6575 exit status 1
Jun 20 11:12:03 localhost postfix/master[505]: warning:
/usr/lib/postfix/smtpd: bad command startup -- throttling
there's no bug for this (in postfix package), should I file one - does
it look like cleanup bug? or kernel bug?
TIA
erik
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
