Problem afther sa-update
Hi all I have a problem on spamassassin afther sa-update The server download the update, it reload the service and the child process wasn't correctly killed and the father process go on zombie state. Message on spamd log: Thu Jun 14 08:57:46 2012 [20774] info: spamd: server hit by SIGHUP, restarting Thu Jun 14 08:57:46 2012 [20774] info: spamd: child [9228] killed successfully: interrupted, signal 2 (0002) Thu Jun 14 08:58:49 2012 [20774] warn: Use of uninitialized value $selerr in concatenation (.) or string at /usr/share/perl5/Mail/SpamAssassin/SpamdForkScaling.pm line 332. Thu Jun 14 08:58:49 2012 [20774] warn: prefork: select returned error on server filehandle: My server: Debian 6.0.4 SpamAssassin version 3.3.2 running on Perl version 5.10.1 Can you help me? Thanks Leonardo -- Leonardo Verzetti Product Engineer Shared Hosting Products RD - Dada.pro leonardo.verze...@register.it
Re: Problem afther sa-update
On 6/15/2012 6:23 AM, Leonardo Verzetti wrote: Hi all I have a problem on spamassassin afther sa-update The server download the update, it reload the service and the child process wasn't correctly killed and the father process go on zombie state. Message on spamd log: Thu Jun 14 08:57:46 2012 [20774] info: spamd: server hit by SIGHUP, restarting Thu Jun 14 08:57:46 2012 [20774] info: spamd: child [9228] killed successfully: interrupted, signal 2 (0002) Thu Jun 14 08:58:49 2012 [20774] warn: Use of uninitialized value $selerr in concatenation (.) or string at /usr/share/perl5/Mail/SpamAssassin/SpamdForkScaling.pm line 332. Thu Jun 14 08:58:49 2012 [20774] warn: prefork: select returned error on server filehandle: I would recommend you change your sa-update script to do a stop and start of spamassassin rather than a SIGHUP as an immediate workaround. After that, I seem to remember we have changed some stuff in trunk. Let me work on an rc today. Regards, KAM
Pyzor broke after update
messages:
Jun 15 10:12:28 smtp1 python: abrt: detected unhandled Python exception in
/usr/bin/pyzor
Jun 15 10:12:28 smtp1 abrtd: New client connected
Jun 15 10:12:28 smtp1 abrtd: Directory 'pyhook-2012-06-15-10:12:28-32379'
creation detected
Jun 15 10:12:28 smtp1 abrt-server[32380]: Saved Python crash dump of pid 32379
to /var/spool/abrt/pyhook-2012-06-15-10:12:28-32379
Jun 15 10:12:28 smtp1 abrt-server[32380]: statvfs('(null)'): Bad address
Jun 15 10:12:28 smtp1 abrtd: Package 'pyzor' isn't signed with proper key
Jun 15 10:12:28 smtp1 abrtd: Corrupted or bad dump
/var/spool/abrt/pyhook-2012-06-15-10:12:28-32379 (res:2), deleting
Jun 15 10:12:31 smtp1 MailScanner: Process did not exit cleanly, returned 2
with signal 0
I am getting the message above after updating MS yesterday. Unable to trace
this one back.
[root@smtp1 ~]# spamassassin -D pyzor sample-spam.txt
Jun 15 10:13:45.440 [742] dbg: pyzor: network tests on, attempting Pyzor
Jun 15 10:13:47.833 [742] dbg: pyzor: pyzor is available: /usr/bin/pyzor
Jun 15 10:13:47.834 [742] dbg: pyzor: opening pipe: /usr/bin/pyzor check
/tmp/.spamassassin742YetsRQtmp
Jun 15 10:13:48.083 [742] dbg: pyzor: [745] finished successfully
Jun 15 10:13:48.083 [742] dbg: pyzor: got response: public.pyzor.org:24441
(200, 'OK') 351 0
MailScanner --lint --debug:
pyzor: check failed: internal error, python traceback seen in response
But cannot find the trace
--
Jeremy McSpadden
Flux Labs, Inc
http://www.fluxlabs.nethttp://www.fluxlabs.net/
Endless Solutions
Office : 850-250-5590
Cell : 850-890-2543
Fax : 850-254-2955
