On 9/14/19 9:30 PM, @lbutlr wrote:
I am still getting spammed processes that last for hours or days. When I kill
them, `kill -9` they come back after the load drops. The processes use 100% of
the processor.
nobody 72041 100.0 2.2 87264 76940 - R 10:36 35:28.97 spamd
child (perl)
root 52954 0.0 1.9 76992 67124 - I 13:41 0:01.60 spamd
child (perl)
root 55342 0.0 0.2 24904 7828 - Ss Sun15 0:06.06
/usr/local/sbin/spamass-milter -f -p /var/run/spamass-milter.sock -u spamd -r
10 -i 65.121.55.40/29 -i 127.0.0.1 -e covisp.net
root 73409 0.0 2.1 84860 75240 - I Wed20 0:59.01 spamd
child (perl)
root 84607 0.0 1.8 73880 63700 - Ss Tue01 0:20.77
/usr/local/bin/perl -T -w /usr/local/bin/spamd -c -H /var/spool/spamd -d -r
/var/run/spamd/spamd.pid
The only way to get rid of it is to stop spamd and restart it.
Running SA 3.4.2 on FreeBSD 11.3 with no updates pending. I tried updating
perl, but that did not work at all, it appears SA can’t use perl 5.30.
I’ve just setup cron to stop/start sa-spamd periodically until I figure out why
this is happening.
What is starting spamd as nobody instead of root like the other processes?
Is this what you're looking for?
https://spamassassin.apache.org/full/3.4.x/doc/spamd.txt
-m num, --max-children=num Allow maximum num children
--min-children=num Allow minimum num children
--min-spare=num Lower limit for number of spare children
--max-spare=num Upper limit for number of spare children
--max-conn-per-child=num Maximum connections accepted by child
before it is respawned
