Hi all,
Dallas, I think the problem isn't the request timing out - Rick says
'the child never exits from processing the message'...how can this be??
Rick, as a workaround either raise the timeout limit (both my servers
are located near Cologne/Germany). And take a look at how fast DNS is
for you
Dirk
Dallas Engelken schrieb:
-----Original Message-----
From: Rick Macdougall [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 11:59
To: [EMAIL PROTECTED]
Cc: users@spamassassin.apache.org
Subject: Re: Strange problem
Sanford Whiteman wrote:
Both servers have exactly the same config except for the
auto-learn
and bayes/user prefs are stored in mysql on the FreeBSD server.
Thanks to all who replied.
I found the problem and it's related to ixhash, the timeout
doesn't work correctly / work at all.
I see
Jul 10 11:13:01 spa010 spamd[29830]: ixhash timeout reached
at /etc/mail/spamassassin/ixhash.pm line 91, <GEN12101> line 2226.
Jul 10 11:13:01 spa010 spamd[29830]: ixhash timeout reached
at/etc/mail/spamassassin/ixhash.pm line 91, <GEN12101> line 2226.
In the logs and the child never exits from processing the message.
I've cc'd Dallas to see if he has any insights into the problem.
the warns are being generated because the timeout value has been exceeded...
my $timeout = $permsgstatus->{main}->{conf}->{'ixhash_timeout'} ||
5;
eval {
Mail::SpamAssassin::Util::trap_sigalrm_fully(sub { die "ixhash
timeout reached"; });
the code is right.. you need to figure out why it times out. have you
hardcoded ixhash_timeout to some other value? have you tried manual
lookups from that box?
# host -tA abc.ix.dnsbl.manitu.net
Host abc.ix.dnsbl.manitu.net not found: 3(NXDOMAIN)
d
