SA_TIMED_OUT

[Clovis Tristao <cl...@agr.unicamp.br>]

Hi,

The Amavis is generated this error in /var/log/maillog:

Jan 27 04:03:40 jacaranda amavis[26216]: (26216-01) SA TIMED OUT, 
backtrace: at 
/usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/BayesStore/DBM.pm line 
1846\n\teval {...} called at 
/usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/BayesStore/DBM.pm line 
1846\n\tMail::SpamAssassin::BayesStore::DBM::tok_unpack('Mail::SpamAssassin::BayesStore::DBM=HASH(0xb3b792c)', 
'undef') called at 
/usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/BayesStore/DBM.pm line 
851\n\tMail::SpamAssassin::BayesStore::DBM::tok_get('Mail::SpamAssassin::BayesStore::DBM=HASH(0xb3b792c)', 
'-\\x{ce}\\x{f3}7\\x{cb}') called at 
/usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/BayesStore/DBM.pm line 
1333\n\tMail::SpamAssassin::BayesStore::DBM::tok_sync_counters('Mail::SpamAssassin::BayesStore::DBM=HASH(0xb3b792c)', 
0, 1, 1138341789, '-\\x{ce}\\x{f3}7\\x{cb}') called at 
/usr/lib/perl5/site_perl/5.8.6/Mail/SpamAssassin/BayesStore/DBM.pm line 
1044\n\tMail::SpamAssassin::BayesStore::DBM::mult...

Any idea? What's happening?
How to fix?
Tks a lot,

Clóvis

-- 
Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola
Administrador de Redes - Secao de Informatica (SINFO)
E-mail: mailto:clovis@agr.unicamp.br http://www.agr.unicamp.br
Fone(0xx19) 37881031-37881038 ou FAX(55xx19) 37881005/37881010

Re: SA_TIMED_OUT

[Gary V <mr...@hotmail.com>]

>>You can turn off auto-expiry and set up a cron job to do it every so 
>>often.
>>
>>
>I have try, i will edit local.cf and setup /bayes_auto_expire/ to 0. It's 
>correct?
>Thanks a lot,
>
>Clóvis

Yes, and here is a sample cron job:
http://www200.pair.com/mecham/spam/bayes-maint.txt

Also, you can simply give spamassassin more time to process.
In amavisd.conf, set:

$sa_timeout = 60;  # default is 30 seconds.

Gary V

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE! 
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

Re: SA_TIMED_OUT

[Clovis Tristao <cl...@agr.unicamp.br>]

Hi Loren,

Loren Wilton wrote:
> Looks like Amvis thought an SA transaction was taking too long.  The
> backtrace seems to indicate that SA was in Bayes.
>
> I suspect that you have a fairly large bayes database, and this user got hit
> with a bayes expiry run.  Since Amvis killed SA before this could complete,
> it will probably keep happening to a lot of messages until the update can
> happen.
>
> You can turn off auto-expiry and set up a cron job to do it every so often.
>
>   
I have try, i will edit local.cf and setup /bayes_auto_expire/ to 0. 
It's correct?
Thanks a lot,

Clóvis


-- 
Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola
Administrador de Redes - Secao de Informatica (SINFO)
E-mail: mailto:clovis@agr.unicamp.br http://www.agr.unicamp.br
Fone(0xx19) 37881031-37881038 ou FAX(55xx19) 37881005/37881010

Re: SA_TIMED_OUT

[Loren Wilton <lw...@earthlink.net>]

Looks like Amvis thought an SA transaction was taking too long.  The
backtrace seems to indicate that SA was in Bayes.

I suspect that you have a fairly large bayes database, and this user got hit
with a bayes expiry run.  Since Amvis killed SA before this could complete,
it will probably keep happening to a lot of messages until the update can
happen.

You can turn off auto-expiry and set up a cron job to do it every so often.

        Loren