https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6304
Summary: 3.3.0 Proposed released Cut 2 has "scary" messages
thrown by SpamD compared to 3.2.5
Product: Spamassassin
Version: 3.3.0
Platform: Other
OS/Version: All
Status: NEW
Severity: major
Priority: P2
Component: spamc/spamd
AssignedTo: [email protected]
ReportedBy: [email protected]
Since moving the server to 3.3.0, I'm seeing these in the logs that were not
there before:
Jan 22 13:10:01 talonjr spamd[8959]: spamd: handled cleanup of child pid
[8972] due to SIGCHLD: INTERRUPTED, signal 2 (0002)
Are these just more informative? Since a quick look of 3.2.5 shows the same
info() line, I'm worried that this isn't good. I had 0 of these before with
3.2.5 and and get about 5 per minute with the 3.3.0 cut 2 proposed release.
They look like spawns and then kills:
Jan 22 13:25:44 talonjr spamd[8959]: spamd: server successfully spawned
child process, pid 9141
Jan 22 13:25:44 talonjr spamd[8959]: spamd: handled cleanup of child pid
[9141] due to SIGCHLD: INTERRUPTED, signal 2 (0002)
After running for a few days in production I have voted to release 3.3.0.
However, I believe the root cause and meaning of these messages needs to be
determined.
In 3.3.0, the relevant code changes are a single line with a reference change:
3.3.0:
unless
($Mail::SpamAssassin::Logger::LOG_SA{INHIBIT_LOGGING_IN_SIGCHLD_HANDLER}) {
3.2.5 (just one $ change
unless
($$Mail::SpamAssassin::Logger::LOG_SA{INHIBIT_LOGGING_IN_SIGCHLD_HANDLER}) {
That small change doesn't seem to be the cause.
Just in case I added info ("spamd: %s vs %s",
$$Mail::SpamAssassin::Logger::LOG_SA{INHIBIT_LOGGING_IN_SIGCHLD_HANDLER},
$Mail::SpamAssassin::Logger::LOG_SA{INHIBIT_LOGGING_IN_SIGCHLD_HANDLER});
gave me Jan 22 14:30:13 talonjr spamd[13043]: spamd: vs 0 with a
uninitialied value error.
Looking at this makes me wonder if we have a timing change on min-spares
causing the issue?
Jan 22 14:30:46 talonjr spamd[13043]: spamd: server successfully spawned
child process, pid 13087
Jan 22 14:30:46 talonjr spamd[13043]: prefork: child states: BBIIIII
Jan 22 14:30:50 talonjr spamd[13043]: prefork: child states: BIIIIII
Jan 22 14:30:54 talonjr spamd[13043]: prefork: child states: BIIIIII
Jan 22 14:30:54 talonjr spamd[13043]: prefork: child states: IIIIIII
Jan 22 14:30:54 talonjr spamd[13043]: Use of uninitialized value in sprintf
at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/Logger.pm line
241.
Jan 22 14:30:54 talonjr spamd[13043]: spamd: vs 0
Jan 22 14:30:54 talonjr spamd[13043]: spamd: handled cleanup of child pid
[13087] due to SIGCHLD: INTERRUPTED, signal 2 (0002)
Jan 22 14:30:54 talonjr spamd[13043]: prefork: child states: IIIIII
Here's the spamd command line I'm running
/usr/local/bin/spamd -d --min-spare=5 --min-children=5
--max-conn-per-child=1000
--max-children=40 -q -x -u spamd --allowed-ips=127.0.0.1,removed -i
removed -r /var/run/spamd.pid
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
