Oddly enough, I did have a similar problem when I first upgraded to v3.18. What I was noticing was a permissions failing message at the end of the expirary cycle. Same thing with a sa-learn --force sync. I went back to 3.17 and everything worked as expected. My second upgrade to v3.18 failed the first time during expirary, but has worked flawlessly ever since. I am wondeing if perhaps there was something in the bayes.db that 3.18 didn't like. I was going to report it until it started working auto magically.... <g>
-----Original Message----- From: Daryl C. W. O'Shea [mailto:[EMAIL PROTECTED] Sent: Monday, March 12, 2007 5:30 PM To: Michal Jeczalik Cc: users@spamassassin.apache.org Subject: Re: Do you experience problems with 3.1.8? Michał Jęczalik wrote: > Hello, > > after upgrading from 3.1.7 I have numerous problems with my spamd. It > hangs up during high load and become permamently unresponsive. > According to advices I have found on devel list, I'm using > --round-robin now and it hangs less often. But now I have a lot of > ~/.spamassassin/bayes_toks.expire[pid] lockfiles, that don't disappear > and quickly foul user's quota. It's interesting that on another host > with similar load conditions everything works ok. Anyway - am I the > only one experiencing these problems? There's no rumour on the devel > list, there's no rumour here - what's wrong? :) In this situation > 3.1.8 is quite unusable for me and I'm thinking about downgrade. The > only reason I have not done it already is that I'm not sure if this is > a simple task > - my users won't stand another spamassassin blackout, after numerous > spam floods due to those hang-ups in past couple of days. ;-) This has nothing to do with 3.1.8 specifically. The same thing would happen with 3.1.7. Reverting to an earlier SA version will do nothing for you. spamd isn't "hanging up", it's doing bayes expiries, as you can tell from having the bayes_toks.expire* lock files left after you kill off the child process(es) doing the expiry. Since you're killing off the expiries before they complete, this will (of course) keep happening. If your system is too loaded to deal with bayes auto expiries, disable bayes_auto_expire and then schedule them to be done via a cron job using sa-learn --force-expire -u username. Daryl
