> On Wed, 6 Oct 2004, Ernie Dunbar wrote: > >> Every hour or so, it spews forth a dozen or so messages like this: >> >> Oct 5 13:26:25 pop spamd[267]: server hit by SIGCHLD >> Oct 5 13:26:25 pop spamd[267]: handled cleanup of child pid 9980 >> Oct 5 13:26:25 pop spamd[267]: server successfully spawned child >> process, pid 19660 > > These are normal restarts of the spamd child processes. They happen by > default after each one handles 200 mails. Those of us who've been seeing > memory spikes get these more often because we set --max-conn-per-child to > a lower number.
Okay, so they're safe to filter out of logcheck. Thanks. :) >> Oct 5 13:26:39 pop spamd[19660]: Cannot open bayes databases >> /home/spamc/.spamassassin/bayes_* R/O: tie failed: Permission denied Oct > > The typical cause of this is that the file ownership changed on the > bayes files when you converted them to 3.0. At least this was the problem > I encountered. > > When I did all my conversions following the UPGRADE procedure as root, I > had to go back in and convert the files back to their correct ownerships. > Check for that. That's kind of the odd thing. I set the ownership back to spamc, but it was changed to root for bayes_journal and bayes_toks shortly therafter. What I did instead of UPGRADEing, was nuke the whole database and rebuild it from scratch using some new spam.
