You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Daniel Lemke <le...@jam-software.com> on 2012/08/02 09:37:02 UTC
Bayes causes long scan times once every 24 hours
We have a strange problem with our Bayes filter here, looks like the learning and/or the journal sync regularly causes a high scan times of about 90 seconds.
It occurs once every day at nearly the same time (around 8.04pm).
This is an extract from spamd logs when the problem just occurred:
http://pastebin.com/iutSEajZ
Debug log for the corresponding period of time can be found here:
http://download.jam-software.de/SaWin/spamdDebugLog-Jul26.txt
We already tried disabling Bayes autolearn and set the bayes_journal_max_size to 0, without success.
This is kind of curious as it occurs every day at the same time, no matter how often journal or token sync was done before.
So the token or journal file sizes apparently don't matter.
Bayes files are stored using the default Berkeley DB, system is a Windows 2008 64 bit.
Does anybody have an idea what may be the cause for this?
________________________________
----------------------------------------------------
JAM Software GmbH
Geschäftsführer: Joachim Marder
Am Wissenschaftspark 26 * 54296 Trier * Germany
Tel: 0651-145 653 -0 * Fax: 0651-145 653 -29
Handelsregister Nr. HRB 4920 (AG Wittlich) http://www.jam-software.de
RE: Bayes causes long scan times once every 24 hours
Posted by Daniel Lemke <le...@jam-software.com>.
> -----Original Message-----
> From: Axb [mailto:axb.lists@gmail.com]
> Sent: Thursday, August 02, 2012 9:53 AM
> To: users@spamassassin.apache.org
> Subject: Re: Bayes causes long scan times once every 24 hours
> Shots in the dark:
>
> - do you have an AV doing a scheduled scan during period? (or some other
> scheduled job which could be blocking files)
>
No AV - but a backup...
Good point, will check that out! :)
Regards
Daniel
________________________________
--------------------------------------------------------
JAM Software GmbH
Managing Director: Joachim Marder
Am Wissenschaftspark 26 * 54296 Trier * Germany
Phone: +49 (0)651-145 653 -0 * Fax: +49 (0)651-145 653 -29
Commercial register number HRB 4920 (AG Wittlich) http://www.jam-software.com
Re: Bayes causes long scan times once every 24 hours
Posted by Axb <ax...@gmail.com>.
On 08/02/2012 09:37 AM, Daniel Lemke wrote:
> We have a strange problem with our Bayes filter here, looks like the learning and/or the journal sync regularly causes a high scan times of about 90 seconds.
> It occurs once every day at nearly the same time (around 8.04pm).
>
> This is an extract from spamd logs when the problem just occurred:
> http://pastebin.com/iutSEajZ
>
> Debug log for the corresponding period of time can be found here:
> http://download.jam-software.de/SaWin/spamdDebugLog-Jul26.txt
>
> We already tried disabling Bayes autolearn and set the bayes_journal_max_size to 0, without success.
> This is kind of curious as it occurs every day at the same time, no matter how often journal or token sync was done before.
> So the token or journal file sizes apparently don't matter.
>
> Bayes files are stored using the default Berkeley DB, system is a Windows 2008 64 bit.
>
> Does anybody have an idea what may be the cause for this?
- Your Bayes DB size shouldn't be an issue - we can rule that out.
- No apparent Bayes DB lock issues
Shots in the dark:
- do you have an AV doing a scheduled scan during period? (or some other
scheduled job which could be blocking files)
- what happens if you put ".spamassassin/bayes_* " outside of windows
system32 path? Maybe within your SA dir structure?
probably unhelpful :)
Axb
Re: Bayes causes long scan times once every 24 hours
Posted by RW <rw...@googlemail.com>.
On Thu, 2 Aug 2012 07:37:02 +0000
Daniel Lemke wrote:
> We have a strange problem with our Bayes filter here, looks like the
> learning and/or the journal sync regularly causes a high scan times
> of about 90 seconds. It occurs once every day at nearly the same time
> (around 8.04pm).
>
> This is an extract from spamd logs when the problem just occurred:
> http://pastebin.com/iutSEajZ
>
> Debug log for the corresponding period of time can be found here:
> http://download.jam-software.de/SaWin/spamdDebugLog-Jul26.txt
>
> We already tried disabling Bayes autolearn and set the
> bayes_journal_max_size to 0, without success. This is kind of curious
> as it occurs every day at the same time, no matter how often journal
> or token sync was done before. So the token or journal file sizes
> apparently don't matter.
If it weren't for its happening at the same, it would almost certainly
be due to autoexpiry. The standard advice would be to turn-off
autexpiry and expire by running sa-learn --force-expire from cron (or
Windows equivalent). If you aren't already doing this it's worth ruling
it out.