not happy about losing bayes yet maybe it is time to migrate to SQL
im guessing that SA SQL setup is easy ???
anyone care to chime in?
I'm also interested in this, so thought I would follow up. Can anyone
provide any insight into how difficult it would be to convert from a
local berkeley db
Hi,
spamd[30339]: bayes: cannot open bayes databases
/home/spamd/.spamassassin/bayes_* R/W: lock failed: Interrupted system call
what is bayes_mutex ?
Many years ago Matt wrote this post that describes it:
http://lists.mailscanner.info/pipermail/mailscanner/2004-November/043067.html
In
notes:
when using flock as the file locking in
/etc/mail/spamassassin/local.cf we get
spamd[2489]: bayes: cannot open bayes databases
/home/spamd/.spamassassin/bayes_* R/W: lock failed:
Interrupted system call
spamd[2489]: bayes: cannot open bayes databases
From: R-Elists list...@abbacomm.net
Date: Wed, 14 Apr 2010 08:43:21 -0700
having spent the better part of a two days searching as well as trying
different configs and SA restarts
we do not have a hardware horsepower resource starvation issue
in reference to the error
I'd guess that you have a bayes expire running that is either
taking too long or not finishing and leaving lock files around.
Turn off bayes_auto_expire and use bayes_learn_to_journal.
Add a cron job to periodically sa-learn --sync (say hourly)
and another cron job to do sa-learn
On 4/14/2010 4:59 PM, R-Elists wrote:
I'd guess that you have a bayes expire running that is either
taking too long or not finishing and leaving lock files around.
Turn off bayes_auto_expire and use bayes_learn_to_journal.
Add a cron job to periodically sa-learn --sync (say hourly)
and another
That was going to be my guess, too. You're not swapping, or
having some other i/o issue are you?
/Jason
no sir
i shutdown spamassassin
backed it all up
dusted bayes
started spamassassin
retrained 200 plus of each
seems ok so far...
3.2.5 was working awesome overall yet
