I have an other question:
During the expire operation does the SA use the bayes db to check the
email or the SA works without use bayes?
SA logs:
warn: bayes: cannot open bayes databases
/var/spamassassin/bayes_db/bayes_* R/W: lock failed: Interrupted system call
info: prefork: child states:
BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBIBBIBBBBBBBBBBBBBBBBBIB
Thanks
Leonardo
On 08/28/2012 05:19 PM, RW wrote:
On Tue, 28 Aug 2012 16:48:29 +0200
Leonardo Verzetti wrote:
Sometime the expire operation don't work properly, it seems that the
compression failed (the byes_db size don't decrease) while the lock
persists and the spam child in busy (B) status increase. What is the
reason for this issue? Are there any information on SA log about this?
There are known problems with autoexpiry due its being carried out as a
side effect of scanning a mail, and hence under the same timeouts.
Switching to expiry from cron is the right thing to do.
You may want to check for any cruft in the bayes directory.
I would like perform a cronjob in order to expire the byes_db. Have i
to stop the MTA service before?
Shouldn't be needed.
--
Leonardo Verzetti
Product Engineer
Shared Hosting Products
R&D - Dada.pro
leonardo.verze...@register.it
