https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6410
Summary: "Use of uninitialized value $selerr" on SIGHUP to
spamd
Product: Spamassassin
Version: 3.3.1
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: spamc/spamd
AssignedTo: [email protected]
ReportedBy: [email protected]
We have process in cron that update rules files and restart spamd with a
SIGHUP.
Occasionally, this causes errors like this:
Apr 15 13:27:02 spam3 spamd[9506]: prefork: child states: BBBIBBBBBBBI
Apr 15 13:27:02 spam3 spamd[9506]: spamd: server hit by SIGHUP, restarting
Apr 15 13:27:02 spam3 spamd[9506]: spamd: child [13467] killed successfully:
interrupted, signal 2 (0002)
Apr 15 13:27:02 spam3 spamd[9506]: spamd: child [13485] killed successfully:
interrupted, signal 2 (0002)
Apr 15 13:27:02 spam3 spamd[9506]: spamd: child [13484] killed successfully:
interrupted, signal 2 (0002)
Apr 15 13:27:02 spam3 spamd[9506]: spamd: child [13466] killed successfully:
interrupted, signal 2 (0002)
Apr 15 13:27:02 spam3 spamd[9506]: spamd: child [13453] killed successfully:
interrupted, signal 2 (0002)
Apr 15 13:27:02 spam3 spamd[9506]: spamd: child [12626] killed successfully:
interrupted, signal 2 (0002)
Apr 15 13:27:02 spam3 spamd[9506]: spamd: child [13447] killed successfully:
interrupted, signal 2 (0002)
Apr 15 13:27:03 spam3 spamd[13483]: spamd: Tell: Setting local for exim:65534
in 1.0 seconds, 377880 bytes
Apr 15 13:28:06 spam3 spamd[9506]: Use of uninitialized value $selerr in
concatenation (.) or string at
/usr/local/share/perl/5.10.0/Mail/SpamAssassin/SpamdForkScaling.pm line 332.
Apr 15 13:28:06 spam3 spamd[9506]: prefork: select returned error on server
filehandle:
Spamd does process some further messages but doesn't log any further prefork:
messages. Shortly afterwards it dies completely:
Apr 15 13:35:53 spam3 spamd[13483]: spamd: connection from dirh.bris.ac.uk
[137.222.10.22] at port 61660
Apr 15 13:35:54 spam3 spamd[13483]: spamd: Tell: Setting local for exim:65534
in 1.0 seconds, 3443 bytes
Apr 15 13:37:21 spam3 spamd[9506]: prefork: cannot ping 13483, file handle not
defined, child likely to still be processing SIGCHLD handler after killing
itself
Apr 15 13:37:21 spam3 spamd[9506]: prefork: killing failed child 13483
fd=undefined at
/usr/local/share/perl/5.10.0/Mail/SpamAssassin/SpamdForkScaling.pm line 172.
Apr 15 13:37:21 spam3 spamd[9506]: prefork: error closing socket: Bad file
descriptor
Apr 15 13:37:21 spam3 spamd[9506]: prefork: killed child 13483
Apr 15 13:37:21 spam3 spamd[9506]: prefork: cannot ping 13471, file handle not
defined, child likely to still be processing SIGCHLD handler after killing
itself
Apr 15 13:37:21 spam3 spamd[9506]: prefork: killing failed child 13471
fd=undefined at
/usr/local/share/perl/5.10.0/Mail/SpamAssassin/SpamdForkScaling.pm line 172.
Apr 15 13:37:21 spam3 spamd[9506]: prefork: error closing socket: Bad file
descriptor
Apr 15 13:37:21 spam3 spamd[9506]: prefork: killed child 13471
Apr 15 13:37:21 spam3 spamd[9506]: prefork: cannot ping 13472, file handle not
defined, child likely to still be processing SIGCHLD handler after killing
itself
Apr 15 13:37:21 spam3 spamd[9506]: prefork: killing failed child 13472
fd=undefined at
/usr/local/share/perl/5.10.0/Mail/SpamAssassin/SpamdForkScaling.pm line 172.
Apr 15 13:37:21 spam3 spamd[9506]: prefork: error closing socket: Bad file
descriptor
Apr 15 13:37:21 spam3 spamd[9506]: prefork: killed child 13472
Spamd then stops processing or logging anything, until it next receives a
SIGHUP - when it usually restarts successfully and gets back to work.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
