On Thu, 12 Apr 2012, Andy Jezierski wrote:

Started happening a month or so ago.  Every now and then out of the blue
I'll get the following error:

spamd[61494]: bayes: cannot open bayes databases /usr/local/spamd/bayes_*
R/W: lock failed: Interrupted system call

This causes scans to take 40-60 seconds to complete as they seem to wait
to try to get a bayes lock again.

Restarting spamd corrects the problem until it decides to happen again.
Sometimes the next day, sometimes several days or weeks.

Any ideas?

Trying to autolearn while an expire is underway? Though only delaying for 60 seconds seems to argue against that.

Do you have autoexpire enabled? That's suggested by restarting spamd fixing the problem. If so, it's better to do that from a cron job.

--
 John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
 jhar...@impsec.org    FALaholic #11174     pgpk -a jhar...@impsec.org
 key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
  ...to announce there must be no criticism of the President or to
  stand by the President right or wrong is not only unpatriotic and
  servile, but is morally treasonous to the American public.
                                          -- Theodore Roosevelt, 1918
-----------------------------------------------------------------------
 Tomorrow: Thomas Jefferson's 269th Birthday

Reply via email to