You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "M. Lewis" <ca...@cajuninc.com> on 2006/10/27 22:43:14 UTC

SA TIMED OUT

I upgraded to SA 3.1.4 last night and now I have two issues that I'm 
trying to resolve:

(1)
spamassassin -D --lint is giving me an error:
[2533] warn: config: failed to parse line, skipping: dcc_timeout 18


(2)
In the logs I'm seeing a good number of the following type of entry:
Oct 27 15:40:21 moe amavis[2548]: (02548-01-2) (!)SA TIMED OUT, 
backtrace: at 
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/DnsResolver.pm line 
363\n\teval {...} called at 
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/DnsResolver.pm line 
363\n\tMail::SpamAssassin::DnsResolver::poll_responses('Mail::SpamAssassin::DnsResolver=HASH(0x4005820)', 
72) called at 
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/Plugin/URIDNSBL.pm 
line 
710\n\tMail::SpamAssassin::Plugin::URIDNSBL::complete_lookups('Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1ff8200)', 
'HASH(0x4cbdad0)', 72) called at 
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/Plugin/URIDNSBL.pm 
line 
412\n\tMail::SpamAssassin::Plugin::URIDNSBL::check_post_dnsbl('Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0x1ff8200)', 
'HASH(0x6816dd0)') called at 
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/PluginHandler.pm line 
159\n\teval {...} called at /usr/lib/perl5/vendor_perl/5.8.8/Mail/Sp...


I've checked the archives and maybe I missed something, but I wasn't 
able to find anything that seemed relavent.

Thanks for any pointers.
Mike


[root@moe ~]# spamassassin -V
SpamAssassin version 3.1.4
   running on Perl version 5.8.8

-- 

  Let the machine do the dirty work.  - Elements of Programming Style
   15:35:01 up 16:21,  0 users,  load average: 0.32, 0.31, 0.28

  Linux Registered User #241685  http://counter.li.org

Re: SA TIMED OUT

Posted by "M. Lewis" <ca...@cajuninc.com>.
Gary V wrote:
>> I upgraded to SA 3.1.4 last night and now I have two issues that I'm 
>> trying to resolve:
>>
>> (1)
>> spamassassin -D --lint is giving me an error:
>> [2533] warn: config: failed to parse line, skipping: dcc_timeout 18
>>
> 
> You need to enable (uncomment) the DCC plugin in v310.pre

Done and the error is gone now.


> 
>> (2)
>> In the logs I'm seeing a good number of the following type of entry:
>> Oct 27 15:40:21 moe amavis[2548]: (02548-01-2) (!)SA TIMED OUT, 
>> backtrace: at <...>
> 
>> I've checked the archives and maybe I missed something, but I wasn't 
>> able to find anything that seemed relavent.
>>
>> Thanks for any pointers.
>> Mike
> 
> The newer version takes longer to scan (quite noticable on a low powered 
> system). Newer versions of amavisd-new allow scans to take longer 
> without timomg out where older versions have a default of $sa_timeout = 
> 30; which should be included in amavisd.conf and raised to something 
> like 60 seconds. I also suggest moving Bayes to SQL, and if not, then 
> set lock_method = flock in local.cf if appropriate.
> http://spamassassin.apache.org/full/3.1.x/doc/Mail_SpamAssassin_Conf.html#miscellaneous_options 

Thanks Gary for the explanation. I will check into all of these.

Thanks,
Mike


> 
> 
> _________________________________________________________________
> Try Search Survival Kits: Fix up your home and better handle your cash 
> with Live Search! 
> http://imagine-windowslive.com/search/kits/default.aspx?kit=improve&locale=en-US&source=hmtagline 
> 
> 

-- 

  May the bugs of many programs nest on your hard drive.
   22:45:01 up  3:13,  0 users,  load average: 0.10, 0.17, 0.17

  Linux Registered User #241685  http://counter.li.org

Re: SA TIMED OUT

Posted by "M. Lewis" <ca...@cajuninc.com>.
Gary V wrote:
>>> spamassassin -D --lint is giving me an error:
>>> [2533] warn: config: failed to parse line, skipping: dcc_timeout 18
> 
> BTW, as Matt says, your DNS may be slow. If DCC doesn't respond within 
> 10 seconds, I would imagine it's unlikely it will respond - so I 
> wouldn't waste time waiting around another 8 seconds. Many people find a 
> local caching DNS server really helps on net tests.
> 
> Gary V

Yes, I have been using a caching NS prior to rebuilding the machine 
yesterday. I simply forgot to turn it on this time. Duh.

Thanks,
Mike


-- 

  IBM: Icons Bygones My Mom's
   22:50:01 up  3:18,  0 users,  load average: 0.53, 0.30, 0.22

  Linux Registered User #241685  http://counter.li.org

RE: SA TIMED OUT

Posted by Gary V <mr...@hotmail.com>.
>>spamassassin -D --lint is giving me an error:
>>[2533] warn: config: failed to parse line, skipping: dcc_timeout 18

BTW, as Matt says, your DNS may be slow. If DCC doesn't respond within 10 
seconds, I would imagine it's unlikely it will respond - so I wouldn't waste 
time waiting around another 8 seconds. Many people find a local caching DNS 
server really helps on net tests.

Gary V

_________________________________________________________________
Stay in touch with old friends and meet new ones with Windows Live Spaces 
http://clk.atdmt.com/MSN/go/msnnkwsp0070000001msn/direct/01/?href=http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us


RE: SA TIMED OUT

Posted by Gary V <mr...@hotmail.com>.
>I upgraded to SA 3.1.4 last night and now I have two issues that I'm trying 
>to resolve:
>
>(1)
>spamassassin -D --lint is giving me an error:
>[2533] warn: config: failed to parse line, skipping: dcc_timeout 18
>

You need to enable (uncomment) the DCC plugin in v310.pre

>(2)
>In the logs I'm seeing a good number of the following type of entry:
>Oct 27 15:40:21 moe amavis[2548]: (02548-01-2) (!)SA TIMED OUT, backtrace: 
>at <...>

>I've checked the archives and maybe I missed something, but I wasn't able 
>to find anything that seemed relavent.
>
>Thanks for any pointers.
>Mike

The newer version takes longer to scan (quite noticable on a low powered 
system). Newer versions of amavisd-new allow scans to take longer without 
timomg out where older versions have a default of $sa_timeout = 30; which 
should be included in amavisd.conf and raised to something like 60 seconds. 
I also suggest moving Bayes to SQL, and if not, then set lock_method = flock 
in local.cf if appropriate.
http://spamassassin.apache.org/full/3.1.x/doc/Mail_SpamAssassin_Conf.html#miscellaneous_options

_________________________________________________________________
Try Search Survival Kits: Fix up your home and better handle your cash with 
Live Search! 
http://imagine-windowslive.com/search/kits/default.aspx?kit=improve&locale=en-US&source=hmtagline