Thanks very much for the detailed reply!
Quoting Mark Martinec <mark.martinec...@ijs.si>:
If you can isolate one such message which causes a crash and
be able to reproduce it from a command line spamassassin, that would
be ideal. Otherwise, enable debugging and when a process crashes
check what was the last thing it was doing.
About catching a problem mail so I can reproduce the issue, Im not
sure how to do this as I believe (could well be mistaken!) that at the
time the mail is passed to spamassassin it doesnt exist on the
filesystem. I will look into this tho to check on how I might be able
to do it...
My first suspect would be a file-based database if you happen to
use it for bayes or awl. Moving bayes and awl to MySQL & InnoDB
is more stable and faster for many of us.
Ok, I think this will be first on my list then (to change to MySQL
config). And actually thanks for the idea that it could be the DB, Ive
just chucked away all the flat DB files etc and restarted SA. So far
no 100% CPU issues...
Second suspect would be some runaway regexp from third party rules.
AFAIK Im running totally default rules as per FreeBSD ports install.
As you already found out and reported, the crash could also be
due to some 5.10.1 bug (like the #69973), although that particular
one was avoided if you use recent versions of perl modules from ports
(such as the p5-HTML-Parser). I'm running 5.12.1 now on our FreeBSD
mailer and is stable (just plain install from their source tarball,
and then deleted and reinstalled all perl modules from ports).
As mentioned I reinstalled perl yesterday, my ports tree is up to date
so I should have latest of everything. The package u mention is at
version: p5-HTML-Parser-3.65. Perl 5.10.1 bug 69973 has been fixed in
the ports tree BTW, I even got a mention as the reporter in fresh
ports ;)
My primary suspect would be bayes auto-expiry. Try turning it off
(bayes_auto_expire 0) and do expiry runs manually or from cron.
Its already off so it cant be that, assuming this line in the file
/usr/local/etc/mail/spamassassin/local.cf is correct:
bayes_auto_expire 0
A second candidate again could be some third-party regexp rule.
As above, dont think I have any 3rd party regexp rules...
I doubt that 7.0 vs 8.0 would make any difference in this regard.
Compare the versions of your bdb if using it - the last db47
from ports seems fine. There were problems with some early 4.*
versions of bdb.
Im a bit confused about this TBH as SA seems to use version 1.85 DB
files which are not compatible with db4.x. A anyway if I switch to
MySQL I wont have to worry about this....
thanks again! Andy.
PS will report back once Ive got MySQL configured...
PPS thats about 10mins with no 100% CPU now, so removing the old DB
files is looking good for fixing that prob (and putting the blame on
the flat file DBs).
