Very probably a mail message is coming in and a bayes expire is trying to run.
This ends up taking too long, the spamd child gets killed, the mail goes
through unscored, and then process repeats with the next child.
Turn off bayes_auto_expire and do a manual expire run to get things cleaned up.
Then schedule the expire as a cron job. Once a day is enough for most people,
but depending on mail volume you may have to do more than one run a day on a
really busy site. It doesn't sound like you are in that category since things
ran fine for months.
Loren
----- Original Message -----
From: Michael Martinell
To: users@spamassassin.apache.org
Sent: Wednesday, January 09, 2008 7:32 AM
Subject: bayes error
Hello.
I am running a qmail server with spamassassin on debian etch. This setup has
been running fine for several months, however in the last few days mail has
became extremely slow. I found this in the log (mail.warn):
spamd[5050]: pyzor: check failed: internal error
spamd[8040]: bayes: cannot open bayes databases
/home/spamassassin/.spamassassin/bayes_* R/W: lock failed: File exists
These entries repeat consistently. I moved bayes.lock and a message was
quickly accepted, creating a new lock file. As soon as the new lock file was
created the server became very slow again. I also noticed that I have around
400-500 bayes_toks.expire* files in /home/spamassassin/.spamassassin. Is this
something to be concerned about?
Also, are the following files normal in this directory?
auto-whitelist
bayes_journal
bayes.lock
bayes.lock.mail.dakotasioux.com.17237
bayes.lock.mail.dakotasioux.com.24374
bayes.lock.mail.dakotasioux.com.24687
bayes.lock.mail.dakotasioux.com.5050
bayes.lock.mail.dakotasioux.com.8040
bayes.lock.mail.dakotasioux.com.8490
bayes_seen
bayes_toks
If you need any additional information please let me know.
