In fact, I see some perl errors in mail-log today, like this:
Nov 27 08:21:37 server spamd[31606]: Premature padding of base64 data
at /usr/lib/perl5/vendor_perl/5.8.7/Mail/SpamAssassin/Uti
l.pm line 547, <GEN21445> line 212.
Nov 27 08:49:03 server spamd[427]: Use of uninitialized value in hash
element at /usr/lib/perl5/vendor_perl/5.8.7/Mail/SpamAssa
ssin/Plugin/TextCat.pm line 398, <GEN22132> line 307.
Nov 27 08:49:03 server spamd[427]: Use of uninitialized value in hash
element at /usr/lib/perl5/vendor_perl/5.8.7/Mail/SpamAssa
ssin/Plugin/TextCat.pm line 407, <GEN22132> line 307.
Nov 27 08:49:07 server spamd[427]: Use of uninitialized value in
substitution (s///) at /usr/lib/perl5/vendor_perl/5.8.7/Mail/S
pamAssassin/Plugin/TextCat.pm line 397, <GEN22135> line 640.
Nov 27 08:49:07 server spamd[427]: Use of uninitialized value in hash
element at /usr/lib/perl5/vendor_perl/5.8.7/Mail/SpamAssa
ssin/Plugin/TextCat.pm line 398, <GEN22135> line 640.
Nov 27 08:49:07 server spamd[427]: Use of uninitialized value in hash
element at /usr/lib/perl5/vendor_perl/5.8.7/Mail/SpamAssa
ssin/Plugin/TextCat.pm line 407, <GEN22135> line 640.
Bu with these errors, spamd is functioning very well, so far.
The crashes occurs eventually.
For example, on Nov 26 15:21 my spamd daemon crash and monit restart
it. On mail-log, I can see this:
-- > here spamd working fine...
Nov 26 15:21:51 dmz spamd[6427]: spamd: connection from localhost
[127.0.0.1] at port 53289
----------> detecting and quarantine spam message
Nov 26 15:21:51 dmz spamd[6427]: spamd: checking message (unknown) for
[EMAIL PROTECTED]:1001
Nov 26 15:21:55 server spamd[6427]: spamd: identified spam (37.2/5.0)
for [EMAIL PROTECTED]:1001 in 4.6 seconds, 1523 bytes.
Nov 26 15:21:55 server spamd[6427]: spamd: result: Y 37 -
BAYES_99,RAZOR2_CF_RANGE_51_100,RAZOR2_CF_RANGE_E8_51_100,RAZOR2_CHECK,RCVD_IN_NJABL_DUL,RCVD_IN_SORBS_DUL,RCVD_IN_XBL,UNPARSEABLE_RELAY,UNWANTED_LANGUAGE_BODY,URIBL_AB_SURBL,URIBL_BLACK,URIBL_JP_SURBL,URIBL_OB_SURBL,URIBL_SC_SURBL,URIBL_WS_SURBL
scantime=4.6,size=1523,[EMAIL PROTECTED],uid=1001,required_score=5.0,rhost=localhost,raddr=127.0.0.1,rport=53289,mid=(unknown),bayes=1,autolearn=no
Nov 26 15:21:55 server qmail-scanner[6987]:
SA:SPAM-QUARANTINED:RC:0(67.173.128.33):SA:1(37.2/5.0): 4.683741 1470
[EMAIL PROTECTED] [EMAIL PROTECTED] Fwd:
<[EMAIL PROTECTED]> 1164561710.6989-0.server:885
orig-server11645617105406987:1470
---> here, another process using spamc can't connect to spamd at
localhost and problems begins...
---> spamd no reports any other errors (like perls errors, or other
stuff, just "connection refused")
Nov 26 15:21:56 server spamc[7030]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#1 of 3): Connection refused
Nov 26 15:21:57 server spamc[7030]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#2 of 3): Connection refused
Nov 26 15:21:58 server spamc[7030]: connect(AF_INET) to spamd at
127.0.0.1 failed, retrying (#3 of 3): Connection refused
Nov 26 15:21:59 server spamc[7030]: connection attempt to spamd aborted
after 3 retries
--> here, monit restarts spamd daemon and all is back to normal
Nov 26 15:22:02 server spamd[7085]: logger: removing stderr method
Nov 26 15:22:09 server spamd[7097]: spamd: server started on port
783/tcp (running version 3.1.6)
Nov 26 15:22:09 server spamd[7097]: spamd: server pid: 7097
I'm using Suse 10.1 with perl-5.8.7-5, spamassassin-3.1.6-4.1 and
perl-spamassassin-3.1.6-4.11
My spamd options: /usr/sbin/spamd -x -u spamd -d -m 15
Mark escreveu:
-----Original Message-----
From: Rejaine Monteiro [mailto:[EMAIL PROTECTED]
Sent: maandag 27 november 2006 12:03
To: Jeff Funk
Cc: users@spamassassin.apache.org
Subject: Re: spamd crashing...
What you use to monitor and restarts spamd when failed?
I'm have some crashes too, so I'm using monit to do this.
My problems are : spamd daemon stop works or tcp port
783 is not responding.
Spamd crashing is, seen from the program itself, rather unlikely. A child
crashing? Maybe; but the parent? Sound more like your perl itself is
unstable (core-dumping and such; any such indication in your system logs).
I recently saw this posted:
... @INC (@INC contains:
/usr/lib/perl5/site_perl/5.8.8/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.8
/usr/lib/perl5/site_perl/5.8.7/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.6/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.5/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.4/i386-linux-thread-multi
/usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi
Never understood why Linux does this anyway (I'm on FreeBSD). Probably
because someone thought it might be a cool idea to include stuff from an
older installation in the INC path. Never mind that xs stuff compiled for
a previous version can seriously instablize your system. At any rate, I
would start looking in this direction first.
My spamd, the old 2.54 I used for ages, and the new 3.0.17, has never ever
crashed; and I mean it. The only real reason I think the parent process
could potentially crash (not on signal 11) is because the main "accept"
loop might not have an eval around it or some such. But I'm pretty sure
they took care of that.
- Mark
