Hello, Michael Parker wrote: > Richard Hobbs wrote: >> Hello, >> >> Could the size of "bayes_seen" and "bayes_toks" be causing this timeout? >> > > No, those aren't really that big, but it does look like you have an > expiration problem.
I've heard that this file should be around 10MB on a "standard" system, so surely 80MB is huge? Also, our mail server deals with around 1000-1500 emails per day, and is a single-CPU Pentium(R) 4 CPU 2.26GHz with 512MB RAM - should this be able to cope? > To solve your immediate problem you could just turn off bayes, that will > get mail flowing again and then you can address your real problem. How effective would spam checking be with bayes disabled, though? I know it's better than a broken solution, but just out of interest... > I'd guess that the spike in CPU you are seeing is due to bayes > expiration running and then getting killed off. Expiration can be very > IO intensive and it locks the database while running which can cause a > backup depending on you setup. To make matters worse it looks like > you've got something timing out and killing off the expiration so its > not allowed to complete. That sounds about right - i have no idea what "spamd" is doing during that time other than running a lot of "pread" system calls, but that would make sense. I think exim gives 5 minutes to the spam checker, and then kills it off and rejects the mail with the error in my previous mail. > Long term, I'd suggest turning off auto expiration and then running > sa-learn --force-expire via a cronjob. I believe there is good > information on setting this up on the wiki. Well, i've just run "sa-learn --force-expire" manually, and despite saying it had removed a whole load of entries from the database, the bayes_toks and bayes_seen files are still the same size (80MB and 10MB, respectively). > You can remove any *.expire* files that are older than 5 minutes, they > are left over from previously timed out expiration attempts. Done. > Like I said, check out the wiki, you should find more information there > on the problem and possible solutions. Hmm... will do, but you think it's all working perfectly, just slower than we'd like, right? Please correct me if that statement is incorrect. Thanks again, Richard. > Michael >> ====================================================================== >> mail:/home/spamcheck/.spamassassin# ls -l >> total 101060 >> -rw------- 1 spamcheck spamcheck 2637824 2007-08-28 12:42 auto-whitelist >> -rw------- 1 spamcheck spamcheck 6 2007-02-27 16:35 >> auto-whitelist.mutex >> -rw------- 1 spamcheck spamcheck 56 2007-08-28 12:52 bayes.lock >> -rw------- 1 spamcheck spamcheck 6 2007-02-27 16:33 bayes.mutex >> -rw------- 1 spamcheck spamcheck 10530816 2007-08-28 11:11 bayes_seen >> -rw------- 1 spamcheck spamcheck 83738624 2007-08-28 12:52 bayes_toks >> -rw------- 1 spamcheck spamcheck 1298432 2007-02-27 18:14 >> bayes_toks.expire1698 >> -rw------- 1 spamcheck spamcheck 1327104 2007-02-28 02:17 >> bayes_toks.expire17474 >> -rw------- 1 spamcheck spamcheck 2473984 2007-02-28 02:31 >> bayes_toks.expire17865 >> -rw------- 1 spamcheck spamcheck 1302528 2007-02-28 02:48 >> bayes_toks.expire17866 >> -rw------- 1 spamcheck spamcheck 1335296 2007-02-28 03:17 >> bayes_toks.expire18715 >> -rw------- 1 spamcheck spamcheck 2572288 2007-02-28 03:37 >> bayes_toks.expire19618 >> -rw------- 1 spamcheck spamcheck 655360 2007-02-28 09:19 >> bayes_toks.expire28928 >> -rw------- 1 spamcheck spamcheck 1302528 2007-08-28 10:14 >> bayes_toks.expire3058 >> -rw------- 1 spamcheck spamcheck 1302528 2007-08-28 10:34 >> bayes_toks.expire3059 >> -rw------- 1 spamcheck spamcheck 1298432 2007-02-27 17:33 >> bayes_toks.expire31684 >> -rw------- 1 spamcheck spamcheck 1302528 2007-02-27 18:42 >> bayes_toks.expire31685 >> -rw------- 1 spamcheck spamcheck 5017600 2007-08-28 11:08 >> bayes_toks.expire4625 >> -rw------- 1 spamcheck spamcheck 5013504 2007-08-28 12:35 >> bayes_toks.expire7150 >> -rw------- 1 spamcheck spamcheck 5013504 2007-08-28 12:52 >> bayes_toks.expire7925 >> -rw-r--r-- 1 spamcheck spamcheck 1175 2005-07-20 14:23 user_prefs >> mail:/home/spamcheck/.spamassassin# >> ====================================================================== >> >> If so, what can i do about this? >> >> Thanks again, >> Richard. >> >> >> Richard Hobbs wrote: >>> Hello, >>> >>> Mark Martinec wrote: >>>> Richard, >>>> >>>>> To add information to this problem, it appears that spamd does >>>>> eventually give up after 5 minutes >>>> Capture a message causing touble from a MTA queue, >>>> and feed it to a command line spamassassin with -t -D options. >>> I would love to do this, but it's not the same messages all the time - >>> in a batch of identical messages, some get through and others cause the >>> hanging. It seems to be completely random. >>> >>> Do you have any other ideas? >>> >>> Thanks again, >>> Richard. >>> > > > _____________________________________________________________________ > This e-mail has been scanned for viruses by Verizon Business Internet Managed > Scanning Services - powered by MessageLabs. For further information visit > http://www.verizonbusiness.com/uk > > -- Richard Hobbs (Systems Administrator) Toshiba Research Europe Ltd. - Speech Technology Group Email: [EMAIL PROTECTED] Web: http://www.toshiba-europe.com/research/ Tel: +44 1223 376964 Mobile: +44 7811 803377
