http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5255
Summary: spamd SIGHUP handler can't deal with restarting on
solaris if run using hand-specified perl interpreter
commandline
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: other
Status: NEW
Severity: major
Priority: P5
Component: spamc/spamd
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
at least that's what I think it is:
http://buildbot.spamassassin.org/t-solaris-10/builds/10/test/0
t/spamc_y...................ok
t/spamd.....................ok
t/spamd_allow_user_rules....ok
t/spamd_hup.................# Failed test 4 in t/spamd_hup.t at line 40
# t/spamd_hup.t line 40 is: ok (-e $pid_file);
Could not open pid file log/spamd.pid: No such file or directory
dubious
Test returned status 2 (wstat 512, 0x200)
DIED. FAILED tests 4-90
Failed 87/90 tests, 3.33% okay
looking into the issue, the spamd log in t/log/d.spamd_hup contained:
[17977] info: spamd: server hit by SIGHUP, restarting
[17977] dbg: prefork: new lowest idle kid: 18013
[17977] info: spamd: child 18014 killed successfully
[17977] dbg: prefork: new lowest idle kid: none
[17977] info: spamd: child 18013 killed successfully
[17977] dbg: prefork: select returned err Interrupted system call, probably
signalle
d
Too late for "-T" option at ../spamd/spamd.raw line 1.
in other words, the spamd was being re-execed, but without the
correct flags to the perl interpreter; probably something like
"perl spamd.raw ..." instead of "perl -T -w spamd.raw ...".
This is actually an entirely valid, although probably rare, condition.
(Normally one would run spamd as "spamd" instead of as "perl spamd"
or "/usr/local/perl561/bin/perl -T -w spamd" etc.)
anyway, I just wanted to log this bug to track the issue... fix
is ready to check in.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
