You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by AMBlock <am...@3dresearch.com> on 2019/03/20 07:50:11 UTC
SA info: check: exceeded time limit
Hello,
I have a lightly used mail server (about 2,000 messages/day) running
FreeBSD
11/postfix-3.2/amavisd-new-2.11/spamassassin-3.4.1/clamav-0.99.3.
For about 25% of the messages which are passed to amavisd, the log
shows a warning about bayes old tokens, followed by spamassassin
timeout, which seems to be 5 minutes:
Mar 20 00:53:58 /usr/local/sbin/amavisd[98131]: (98131-01) CALLING SA
check
(0)
Mar 20 00:58:58 /usr/local/sbin/amavisd[98131]: (98131-01) _WARN:
bayes: expire_old_tokens:
__alarm__ignore__(76/::Plugin::Check::run_eval_tests/1106)
Mar 20 00:58:58 /usr/local/sbin/amavisd[98131]: (98131-01) SA info:
check: exceeded time limit in
Mail::SpamAssassin::Plugin::Check::_eval_tests_type11_prineg400_set3,
skipping further tests
Mar 20 00:58:58 /usr/local/sbin/amavisd[98131]: (98131-01) DONE SA
check
(0)
My questions:
1. Is the warning expire_old_tokens related to spamassassin timing out?
2. In /usr/local/etc/amavisd.conf I explicitly set:
$sa_timeout = 30;
why is amavisd ignoring it?
3. How to fix the expire_old_tokens problem (if indeed that's causing
the timeout)?
Please advise...
Re: SA info: check: exceeded time limit
Posted by AMBlock <am...@3dresearch.com>.
On Wed, 20 Mar 2019 11:30:01 -0400
AMBlock <am...@3dresearch.com> wrote:
> On Wed, 20 Mar 2019 06:20:08 -0400
> "Kevin A. McGrail" <km...@apache.org> wrote:
>
> > I would guess you have auto expiry of Bayes tokens enabled. You
> > should look at disabling that and running a cron job in the wee
> > hours instead.
> >
> > Try bayes_auto_expire = 0 and restart amavisd. If that works, I am
> > sure someone here can share a good cron script.
>
> Thank you for the quick reply.
>
> Armed with your advice I found this page:
>
> https://wiki.apache.org/spamassassin/BayesForceExpire
>
> Now anxiously watching amavisd.log and maillog...
Things are much better now.
Before:
Mar 20 00:18:49 size: 41935, TIMING 300691
Mar 20 01:24:46 size: 15470, TIMING 300633
Mar 20 00:46:54 size: 25711, TIMING 300591
Mar 20 00:58:59 size: 3772, TIMING 300506
Mar 20 00:11:01 size: 1202, TIMING 300438
Mar 20 01:30:02 size: 4021, TIMING 300362
After:
Mar 20 22:30:42 size: 3522, TIMING 4122
Mar 20 22:34:06 size: 12370, TIMING 579
Mar 20 22:57:26 size: 2179337, TIMING 4510
Mar 20 22:58:22 size: 18033, TIMING 180
Mar 20 23:04:04 size: 19996, TIMING 1632
Mar 20 23:07:28 size: 175832, TIMING 2057
Mar 20 23:13:05 size: 8663, TIMING 181
Mar 20 23:14:24 size: 2314, TIMING 1392
Much appreciate your expert help!
Re: SA info: check: exceeded time limit
Posted by AMBlock <am...@3dresearch.com>.
On Wed, 20 Mar 2019 06:20:08 -0400
"Kevin A. McGrail" <km...@apache.org> wrote:
> I would guess you have auto expiry of Bayes tokens enabled. You
> should look at disabling that and running a cron job in the wee hours
> instead.
>
> Try bayes_auto_expire = 0 and restart amavisd. If that works, I am
> sure someone here can share a good cron script.
Thank you for the quick reply.
Armed with your advice I found this page:
https://wiki.apache.org/spamassassin/BayesForceExpire
Now anxiously watching amavisd.log and maillog...
Re: SA info: check: exceeded time limit
Posted by "Kevin A. McGrail" <km...@apache.org>.
I would guess you have auto expiry of Bayes tokens enabled. You should
look at disabling that and running a cron job in the wee hours instead.
Try bayes_auto_expire = 0 and restart amavisd. If that works, I am sure
someone here can share a good cron script.
On Wed, Mar 20, 2019, 03:50 AMBlock <amblock@3dresearch.com wrote:
> Hello,
>
> I have a lightly used mail server (about 2,000 messages/day) running
> FreeBSD
> 11/postfix-3.2/amavisd-new-2.11/spamassassin-3.4.1/clamav-0.99.3.
>
> For about 25% of the messages which are passed to amavisd, the log
> shows a warning about bayes old tokens, followed by spamassassin
> timeout, which seems to be 5 minutes:
>
> Mar 20 00:53:58 /usr/local/sbin/amavisd[98131]: (98131-01) CALLING SA
> check
> (0)
> Mar 20 00:58:58 /usr/local/sbin/amavisd[98131]: (98131-01) _WARN:
> bayes: expire_old_tokens:
> __alarm__ignore__(76/::Plugin::Check::run_eval_tests/1106)
> Mar 20 00:58:58 /usr/local/sbin/amavisd[98131]: (98131-01) SA info:
> check: exceeded time limit in
> Mail::SpamAssassin::Plugin::Check::_eval_tests_type11_prineg400_set3,
> skipping further tests
> Mar 20 00:58:58 /usr/local/sbin/amavisd[98131]: (98131-01) DONE SA
> check
> (0)
>
> My questions:
>
> 1. Is the warning expire_old_tokens related to spamassassin timing out?
>
> 2. In /usr/local/etc/amavisd.conf I explicitly set:
>
> $sa_timeout = 30;
>
> why is amavisd ignoring it?
>
> 3. How to fix the expire_old_tokens problem (if indeed that's causing
> the timeout)?
>
> Please advise...
>