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
