Hi all,
I am running SA 3.2.5 and exim 4.69 on a RedHat Enterprise Linux box
(release 4, Nahant Update 6).
I noticed today that our /var/log/maillog was spewing out a lot of:
"cannot open bayes databases /var/spool/spamassassin/bayes_* R/W:
lock failed: Interrupted system call"
errors. I checked the /var/spool/spamassassin directory and saw that it
had over 300 large (10-to-20 meg)
bayes_toks.expire files in it. I google-searched this and found that
several others had this problem, so I
attempted to resolve it the same way they did. Only it didn't work for
me, and now I have had to shutdown bayes.
Please tell me where I went wrong!
First, I did a ls -l -t" on the directory (to sort it by modification
time), and then manually deleted all
of the bayes_toks.expirennn files, keeping only the ones that were
created in the last half hour. That
left me with the bayes_seen, bayes_journal and bayes_toks file (the
latter of which is 84 megs in size)
and 5 of the bayes_toks.expired files.
Next I did: sa-learn -D --force-expire.
This ran rather quickly (wasn't expecting that, as I was led to believe
that my 84 meg bayes_toks file
would slow it down) and produced these results:
[clip]
[23409] dbg: bayes: tie-ing to DB file R/O
/var/spool/spamassassin/bayes_toks
[23409] dbg: bayes: tie-ing to DB file R/O
/var/spool/spamassassin/bayes_seen
[23409] dbg: bayes: found bayes db version 3
[23409] dbg: bayes: opportunistic call attempt skipped, found fresh
running expire magic token
[23409] dbg: config: score set 3 chosen.
[23409] dbg: learn: initializing learner
[23409] dbg: bayes: bayes journal sync starting
[23409] dbg: locker: safe_lock: created
/var/spool/spamassassin/bayes.mutex
[23409] dbg: locker: safe_lock: trying to get lock on
/var/spool/spamassassin/bayes with 300 timeout
[23409] dbg: locker: safe_lock: timed out after 300 seconds
bayes: cannot open bayes databases /var/spool/spamassassin/bayes_* R/W:
lock failed: Interrupted system call
[23409] dbg: bayes: bayes journal sync completed
[23409] dbg: bayes: expiry starting
[23409] dbg: locker: safe_lock: created
/var/spool/spamassassin/bayes.mutex
[23409] dbg: locker: safe_lock: trying to get lock on
/var/spool/spamassassin/bayes with 300 timeout
[23409] dbg: locker: safe_lock: timed out after 300 seconds
bayes: cannot open bayes databases /var/spool/spamassassin/bayes_* R/W:
lock failed: Interrupted system call
[23409] dbg: bayes: expiry completed
[23409] dbg: bayes: untie-ing
(it sat for 3 minutes at each of the two "300 timeout" warnings).
I don't think it did anything though and I am still getting bayes errors
galore in /var/maillog.
Plus the 5 bayes_toks.expire files I left behind are still there.
Also, I read that the 300 second timeout might be the problem. That it
is not giving bayes enough
time to complete an expiry. It was recommended that that be raised to
3000 or more. But I cannot
find that 300 value anywhere (I looked in spamd, all of the .cf files
for SpamAssassin (in /var/share
and the local.cf) and also in the exim config files that call
SpamAssassin. Where is it? Maybe if I changed
that to 3000 and re-ran sa-learn, all would be well?
Any advice would be greatly appreciated. We are running bayesless for
now. Thanks!
- jim -
-
