From: Mark M. <Mar...@ij...> - 2003-03-29 13:58:10
|
Paul, | I upgraded to spamassassin 2.52 earlier this week, and also switched to | Berkeley db for the database. I have had a few weird problems that I think | might involve locking contention. |... | After restarting them and observing them throughout the day, I caught one | process in the wedged up poll state which appeared to have the lock for the | database. All of the other processes were spinning trying to get that lock. | After a while, I guess one of them broke the lock and the processes moved | on. Eventually, another process wedged up, stuck in a call to poll while | the others spun on the lock. In the spamassassin directory there were a ton | of abandoned bayes.lock.* files. I'm still at 2.51 with three patches applied. So far it is still rnning ok. Looks like a thing to report/ask at SAtalk mailing list. Setting $sa_debug=1; in amavisd.conf and running amavisd non-daemonized: # amavisd foreground would provide some SA log output on the screen that might be helpful to SA people in diagnosing the problem. Mark |