For about a week I've been seeing SA time-outs in MailScanner (120 sec time-out) and on investigating it seems the reason are extremely large bayes journal files. I ran "sa-learn -D --sync" and that took quite long, about two minutes. As I understand SA should try to sync once a day? So, it seems that when the sync should happen it takes so long and then times out with MS. I then took a look at the bayes dir and found this:
-rw-rw-rw- 1 spamd www 36 Sep 11 12:43 bayes.mutex -rw-rw-rw- 1 root www 12968 Sep 11 13:13 bayes_journal -rw-rw-rw- 1 root www 170591392 Sep 11 12:04 bayes_journal.old -rw-rw-rw- 1 spamd www 2408448 Sep 11 11:47 bayes_seen -rw-rw-rw- 1 spamd www 20951040 Sep 11 11:47 bayes_toks There was a message received at 12:04, then the --sync apparently was about to happen, but never finished? There are only a few thousand messages arriving per day, many of them whitelisted. It's nearly impossible that the journal could grow so large. Not only that it should sync automatically after some time I forced a sync only a few days ago. Also, when this happens I find that a lot of swap space is allocated although there's still 100 MB or more of free RAM available and only a restart of MailScanner frees that up. (I sent a message about this to the MS list as well.) But the basic underlying problem seems to be this massive journal bloat. This is SA 3.0-RC2 on Suse 9.0 with MailScanner 4.32.5 (I think). I have RC3 on an almost identical system and haven't seen the same there yet. Where there any changes after RC2 in that area, so testing of RC4 might prove useful? Also, could it be any of the Perl modules involved? If so, which should I check or upgrade? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de & http://msie.winware.org
