A few minutes after restarting spamassassin, a spamd child appears to hang at 100% CPU.
Code: Select all
11052 qscand 20 0 188m 65m 2572 R 100.0 0.8 3:25.59 spamd child
Restarting spamassassin resolves the problem for a short time, but then it just happens again.
"spamassassin --lint" gives no errors.
This all started after reinstalling qmail-scanner following the installation of Plesk MU#49
Initially qmail-scanner was not using spamassassin at all, probably because of something related to all this. I had to reinstall it twice and manually run qmail-scanner-reconfigure a couple of times before it started using spamassassin. It also took a very long time (many minutes) for the reconfigure to complete.
So it is as though something is getting "stuck" but I don't know what.
local.cf has nothing much in it and there are no custom rules.
I see plenty of people posting about similar issues on google, but no real resolution of the issue.
Any suggestions as to where I might start looking to try to debug this?