Cory Hawkless wrote:
>
> Hi All,
>
>  
>
> Having a problem with my SA setup. I’m using amavisd and Postfix. For
> some reason I get the following occasionally
>
>  
>
> Aug 19 15:37:20.176 ceg.caznet.com.au /usr/sbin/amavisd[11115]:
> (11115-01-6) SA dbg: bayes: database connection established
>
> Aug 19 15:37:20.177 ceg.caznet.com.au /usr/sbin/amavisd[11115]:
> (11115-01-6) SA dbg: bayes: found bayes db version 3
>
> Aug 19 15:37:20.179 ceg.caznet.com.au /usr/sbin/amavisd[11115]:
> (11115-01-6) SA dbg: bayes: Using userid: 4
>
> Aug 19 15:37:20.184 ceg.caznet.com.au /usr/sbin/amavisd[11115]:
> (11115-01-6) SA dbg: bayes: corpus size: nspam = 5993, nham = 24505
>
> Aug 19 15:39:30.977 ceg.caznet.com.au /usr/sbin/amavisd[11114]:
> (11114-02-4) (!)SA TIMED OUT, backtrace: at
> /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm
> line 1961\n\teval {...} called at
> /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm
> line
> 1961\n\tMail::SpamAssassin::PerMsgStatus::_get_parsed_uri_list('Mail::SpamAssassin::PerMsgStatus=HASH(0xb0945cc)')
> called at
> /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PerMsgStatus.pm
> line
> 1852\n\tMail::SpamAssassin::PerMsgStatus::get_uri_detail_list('Mail::SpamAssassin::PerMsgStatus=HASH(0xb0945cc)')
> called at
> /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/Plugin/URIDNSBL.pm
> line
> 207\n\tMail::SpamAssassin::Plugin::URIDNSBL::parsed_metadata('Mail::SpamAssassin::Plugin::URIDNSBL=HASH(0xae5421c)',
> 'HASH(0xb05f97c)') called at
> /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/PluginHandler.pm
> line 202\n\teval {...} called at
> /usr/lib/perl5/vendor_perl/5.10.0/Mail/SpamAssassin/Plugin[...]
>
>  
>

Roughly twice a day?

If so, I'm guessing a bayes expire run makes the SA run just long enough
to get killed (expiry does take a while, depending on hardware and DB
size, it adds around 1-2 minutes to a run.

. Try either:
1) extend the amavis timeout by 30 seconds
2) disable SA's bayes_auto_expire, and use a cronjob to run sa-learn
--force-expire instead.

and see if it goes away.

  • SA Timeouts Cory Hawkless
    • Re: SA Timeouts Matt Kettler

Reply via email to