Dave Dewey wrote:
> Just upgraded SA to the latest via CPAN, along with Amavisd-new 2.3.3; am
> seeing many
> of these in my logs now:
>
> Sep 20 22:34:18 logger amavis[21071]: (21071-01-16) SA TIMED OUT, backtrace:
> at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/Eva lTests.pm line
> 973\n\teval {...} called at
> /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/EvalTests.pm line
> 973\n\tMail::SpamAssassin::PerMsgStatus::_check_whitelist('Mail::SpamAssassin::PerMsgStatus=HASH(0xc80771c)','HASH(0x940fef4)','[EMAIL
> PROTECTED]')
> called at /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/EvalTests.pm line
> 1131\n\tMail::SpamAssassin::PerMsgStatus::check_from_in_black
> list('Mail::SpamAssassin::PerMsgStatus=HASH(0xc80771c)') called at
> /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/PerMsgStatus.pm line
> 2581\n\teval {...} called at
> /usr/lib/perl5/site_perl/5.8.3/Mail/SpamAssassin/PerMsgStatus.pm line
> 2580\n\tMail::SpamAssassin::
> PerMsgStatus::run_eval_tests('Mail::SpamAssassin::PerMsgStatus=HASH(0xc80771c)','HASH(0xb3d7708)','')
> called at /usr/lib/perl5/site_
> perl/5.8.3/Mail/SpamAssassin/PerMsg..
>
> Looks related to AWL, but whether or not AWL is enabled or disabled makes no
> difference.
Nope.. processing the real whitelist, not the AWL, in that trace.
What's your amavis timeout set for? It may just be too short, as it doesn't look
like SA is hung up, it just looks like it did some bayes DB maintenance and
amavis gave up on it.
If you've got bayes, I'd suggest at least 120 seconds, if not more, as a
timeout. Either that or disable bayes auto expire in your local.cf and run
expiry manually with a cronjob.
