Matt Kettler wrote:
The fact that they keep laying around is a problem. This suggests SA
keeps getting killed before the expire can complete. Do you have any
kind of limits set such as CPU time or memory that SA might be running
against and dying?
You can try kicking off an expire manually using sa-learn
--force-expire. (add -D if you want some debug output)..
note: this could run for a long time, particularly if bayes_toks is
really large.
----
Another one of the fileles appeared -- 17M long.
while bayes_toks is 8.8M. auto-whitelist is 78M -- that seems a bit
excessive...
Don't know what really large means -- bayes_toks isn't that large
compared to some of the other files. No limits that I know of...
Ahh...seeing some oddness in the log though:
(Interrupted? timeouts?...weird...)...
Jul 25 15:23:59 Ishtar spamd[2447]: bayes: cannot open bayes databases
/home/user/.spamassassin/bayes_* R/W: lock failed: Interrupted system call
Jul 25 15:24:48 Ishtar spamd[2443]: bayes: cannot open bayes databases
/home/user/.spamassassin/bayes_* R/W: lock failed: Interrupted system call
Jul 25 15:28:21 Ishtar spamd[2355]: bayes: expire_old_tokens: child processing
timeout at /usr/bin/spamd line 1085, <GEN6> line 22.
Jul 25 15:36:55 Ishtar spamd[2447]: bayes: cannot open bayes databases
/home/user/.spamassassin/bayes_* R/W: lock failed: Interrupted system call
Jul 25 15:41:38 Ishtar spamd[2443]: bayes: expire_old_tokens: child processing
timeout at /usr/bin/spamd line 1085.
Jul 25 16:14:14 Ishtar spamd[2355]: bayes: cannot open bayes databases
/home/user/.spamassassin/bayes_* R/W: lock failed: Interrupted system call
Jul 25 16:19:00 Ishtar spamd[2385]: bayes: expire_old_tokens: child processing
timeout at /usr/bin/spamd line 1085.
Jul 25 16:29:05 Ishtar spamd[2356]: bayes: expire_old_tokens: child processing
timeout at /usr/bin/spamd line 1085.
Jul 25 17:06:02 Ishtar spamd[2385]: bayes: cannot open bayes databases
/home/user/.spamassassin/bayes_* R/W: lock failed: Interrupted system call
