Paul R. Ganci wrote: > I am at my wits end regarding this issue. I am getting very frequent: > > May 14 09:58:05 citlatepetl spamd[5125]: Cannot open bayes databases > /home/spam-filter/etc/mail/spamassassin/bayes_* R/W: lock failed: File > exists > This is very common, and is not a problem UNLESS your autolearner never kicks in. (ie: autolearning always fails)
Basically all it means is two SA processes tried to update the bayes DB at the same time. If two messages come in at the same time and both get autolearned, the second one will fail to lock the bayes DB and generate the above message. Now, if a SA instance crashes and leaves a lockfile laying about, this can be a problem. From then on, all SA learning will fail until the lock gets removed. > bayes_auto_expire 0 With this setting you've got a cronjob running sa-learn --force-expire. Right? If not, fix that. > -rw-rw-rw- 1 prganci users 165988 May 14 10:05 bayes_journal > -rw------- 1 pangione users 34 May 14 10:00 bayes.lock That's a little troubling.. are you having problems with spamd instances crashing? The lock is at least 5 minutes old here.. that's a long time unless an expiry is being run. However, I'd not worry too much yet, but I would check on it. If the lockfile gets to be really old (1hr) then I'd worry. > Please note that I always start off with bayes.lock with -rw-rw-rw- so it is > spamd/spamc which is changing the owner/protection on the lock file. The > /etc/procmailrc file looks like: Please note you shouldn't start off with a bayes.lock at all. That file should only ever be created by spamassassin, and should only exist while bayes manipulation is in progress. Also note the lock should NEVER be anything but -rw------. EVER. If it's -rw-rw-rw- the whole purpose of the file is defeated.
