https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5809
--- Comment #27 from James Kosin <[EMAIL PROTECTED]> 2008-04-14 07:35:50 PST --- (In reply to comment #26) > that wasn't the bug, no. the bug was caused by subtle memory corruption in > the > parent. but if your parent is still running fine and its the kids that bail, > that's not it... > are you _sure_ the parent is still alive? it seems odd that _all_ of the kids > would get this wrong simultaneously. The log snippet below doesn't suggest the parent failed.??? Am I missing anything? Log snippet... Mar 28 15:37:26 beta spamd[20943]: config: copying current conf from backup Mar 28 15:37:27 beta spamd[20277]: prefork: child 20943: entering state 1 Mar 28 15:37:27 beta spamd[20943]: prefork: periodic ping from spamd parent Mar 28 15:37:27 beta spamd[20277]: prefork: new lowest idle kid: 20313 Mar 28 15:37:27 beta spamd[20943]: prefork: sysread(10) not ready, wait max 300 secs Mar 28 15:37:27 beta spamd[20277]: prefork: child reports idle Mar 28 15:37:27 beta spamd[20277]: prefork: child states: III Mar 28 15:37:28 beta spamd[20277]: prefork: child 20943: entering state 3 Mar 28 15:37:28 beta spamd[20277]: prefork: new lowest idle kid: 20313 Mar 28 15:37:28 beta spamd[20314]: prefork: parent closed, exiting Mar 28 15:37:28 beta spamd[20313]: prefork: parent closed, exiting -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
