Dave Howorth wrote:
excerpt from a single-core system: ... Notice that the single-core system reports "handled cleanup of child pid nnnnn due to SIGCHLD" which is never seen on the dual-core system, and that the dual-core reports "child nnnnn killed successfully", which is never seen on the single-core system. What am I missing here?
What version are you running (OS, perl and spamd)? The obvious thing that springs to my mind is perl and threads (!horror!). Though I don't see any such code in spamd itself, perhaps it uses some libraries that do.
openSUSE 11.0, perl 5.10.0, spamassassin 3.2.5 - the latest and greatest. kernel 2.6.25.5-1.1-pae.
Did you clone anything that is sensitive to the number of cores? Did you clone from a single-core or a multi-core master?
I cloned from the dual-core master.
In your dual-core logs, I'm surprised not to see "spamd: server hit by SIG$sig, restarting" because that child killed message appears in the restart_handler called after a SIGHUP.
Ah, my fault - those lines are present, I just grepped for the wrong thing. The "child killed" messages are caused by regular config reload (SIGHUP spamd). I'm more surprised not to see any "handled cleanup of child pid nnnnn due to SIGCHLD". It is as if the spamd master isn't getting the SIGCHLD.
Have you tried running spamd with debugging enabled?
Only on my test-system, which is single-core. I could take a production system out of service and try to reproduce, but I'd like an idea of what I should be looking for. thanks Dave. -- /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org