RE: Spamd dies after tcp timeout

[Sander Holthaus - Orange XL]

I did some more digging, and I also find the following entry several times
in the maillog:
 
prefork: select returned undef! recovering
 
Spamd is currentlty die-ing twice a day :-| Never had any problem with any
other version in this regard...
 
Kind Regards,
Sander Holthaus - Orange XL




From: Sander Holthaus - Orange XL [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, September 27, 2005 9:21 PM
To: users@spamassassin.apache.org
Subject: Spamd dies after tcp timeout


Since a few days, I been having more serious problems with
SpamAssassin 3.10. It just dies after the following two messages in the
error-log:
 
Sep 27 15:16:32 OrangeXL4 spamd[63730]: prefork: child states: II
Sep 27 15:18:12 OrangeXL4 spamd[63730]: tcp timeout at
/usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/SpamdForkScaling.pm
line 195.
Sep 27 15:18:12 OrangeXL4 spamd[63730]: tcp timeout at
/usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/SpamdForkScaling.pm
line 195.
 
Next to that, I get quite a few Pyzor / Alarm erros (for about 5% of
all mail).
 
Never had any of such problems with SpamAssassin 3.0.x or 2.xx
 
I'm using SpamAssassin on FreeBSD 4.10 with Perl 5.8.5 installed. 
 
Kind Regards,
Sander Holthaus

Re: Spamd dies after tcp timeout

[Daryl C. W. O'Shea]

Sander Holthaus - Orange XL wrote:

Next to that, I get quite a few Pyzor / Alarm erros (for about 5% of all
mail).
 
Never had any of such problems with SpamAssassin 3.0.x or 2.xx


The error has actually always been present.  We just didn't report it 
before.  If you were to call Pyzor independently you'd see the same 
error just as often.


There's a third party patch for Pyzor available:

Patches (you need all three):
http://antispam.imp.ch/08-opensource.html?lng=0

Discussion:
http://bugzilla.spamassassin.org/show_bug.cgi?id=4580


Daryl