Per Jessen wrote:
(this was also posted to spamassassin-general, but I thought somebody here might just recognize the problem).
I have a very unusual situation (I think):
I am running the exact same system (it was cloned) on several single-core and dual-core systems. The only difference is in the hardware, i.e. some systems are dual-core. (ok, there are more differences than that).
I am running spamd with maxchild=25 (the actual number in use is controlled externally).
The single-core systems vary from two to five, sometimes six. Perfectly normal. On the dual-core systems, I never see more than two active children. Not normal.
So I checked the logs -
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. Did you clone anything that is sensitive to the number of cores? Did you clone from a single-core or a multi-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. Have you tried running spamd with debugging enabled? Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org