spamd child eating 100% of Cpu help

[bsasninja]

Spamd child is eating 100% of CPU.
It happens only with a mail account.

Notes:
Spamassasin is globaly enabled on all domains, but I cant disable in this one.
Mail account is empty

The only fix I found by now is to stop and start exim. Is there a permanent solution to this?????

Help will be apreciated!

Thanks

[bsasninja]

solution: terminate the account and add it again.

[jack01]

bsasninja,

We have this same problem on 2 of our servers, the same user (different on each server) keeps hogging a "spamd child" process with high cpu, as if its endlessly looping or something.

Can you confirm that since reinstalling the account as per your solution that this really did stop for good?

Thanks.

P.S. does anyone else have a fix that does not involve removing the affected account(s)?

[yapluka]

Check that the account is not running out of space. I had the very same issue and this was the cause...

Good luck

[bsasninja]

150mb of space, 116mb used.

Using spamassassin 3.2.1

Thanks

[yapluka]

Did you try to trace the process ?

[bsasninja]

shows the following

open("/home/user/.spamassassin/auto-whitelist.lock.server1.domain.com.31435", O_WRONLY|O_CREAT|O_TRUNC|O_LARGEFILE, 0666) = 11
ioctl(11, SNDCTL_TMR_TIMEBASE or TCGETS, 0xbfe854f8) = -1 ENOTTY (Inappropriate ioctl for device)

stat64("/home/user/.spamassassin/auto-whitelist", {st_mode=S_IFREG|0600, st_size=10510336, ...}) = 0
open("/home/user/.spamassassin/auto-whitelist", O_RDWR|O_LARGEFILE) = 11

is there a way to tell spamassassin not to scan files over 1mb or so ?

Thanks

[dexus]

I had the same problem for last few days, but when my spamd stucks it did this:

stat64("/home/user/.spamassassin/bayes_toks.new", 0xbfffb120) = -1 ENOENT (No such file or directory)
open("/home/user/.spamassassin/__db.bayes_toks.new", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = -1 EEXIST (File exists)
open("/home/user/.spamassassin/__db.bayes_toks.new", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = -1 EEXIST (File exists)
open("/home/user/.spamassassin/__db.bayes_toks.new", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = -1 EEXIST (File exists)
stat64("/home/user/.spamassassin/bayes_toks.new", 0xbfffb120) = -1 ENOENT (No such file or directory)
open("/home/user/.spamassassin/__db.bayes_toks.new", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = -1 EEXIST (File exists)
open("/home/user/.spamassassin/__db.bayes_toks.new", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0600) = -1 EEXIST (File exists)

So I just deleted file /home/user/.spamassassin/__db.bayes_toks.new and spamd got out of loop

[cpanelnick]

Also make sure you have perl 5.8.8
and if you aren't using nfs

uncomment lock_method flock in /etc/mail/spamassassin/local.cf and run

/scripts/restartsrv_exim

[isputra]

In my case, my customer is running out of space.
So i do like dexus said and works.

I have perl 5.8.8 :
----------
root@server [~]# perl -v
This is perl, v5.8.8 built for i686-linux
----------

cpanelnick, could you explain to me what is lock_method flock in /etc/mail/spamassassin/local.cf for ?

[adapter]

same problem here, if i delete the db file in the spamassasin folder i am out from the loop, but is there any fast way to fix this problem? i can't do it for all my server and over quota account

Thx

[myrtlenet]

Same problem

Some accounts close to quota, others have plenty of space. Other thing is it seems to be random. It started out with 3 accounts, now its around 7.

I ended up turning Bayesian off altogether

[Arsalan]

try deleting the databases of Bayesian in /home/user/.spamassassin


We found that large databases are usually responsible for this problem. Removing the files usually resolves the issue. Further more, keep an eye out on their size.

[cpanelnick]

This is a bug in the berkleydb library. We have tracked it down and are testing a work around patch for spamassassin. We have also reported the problem to spamassassin and the DB_File author. We will release an autofixer for spamassassin once the testing has been completed and proven to not create any unwanted side effected.

Note: RHEL 5 && Centos 5 are not affected

[cpanelnick]

Update: To install the patch:

https://__YOUR_SEVER_IP_HERE__:2087/scripts2/autofixer

Enter:

spamd_dbm_fix