Hello everyone,
Daniel Rogers posted a patch a week or so back to spamc that helped
with the problem of spamc dying while reading in messages from spamass-
milter. I'd thought the patch worked perfectly, when three days later I
had no hung spamc/d processes. I haven't checked in perhaps a week, but
tonite...
$ ps ax | grep spam
170 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
173 ? S 0:01 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
174 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
175 ? S 0:21 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
361 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
362 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
363 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
364 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
365 ? S 0:00 /usr/bin/spamc
367 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
368 ? S 0:00 /usr/bin/spamc
369 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
370 ? S 0:00 /usr/bin/spamc
371 ? S 0:00 /usr/bin/spamc
373 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
374 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
376 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
377 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
378 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
379 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
380 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
381 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
384 ? S 0:00 /usr/bin/spamc
385 ? S 0:00 /usr/bin/spamc
386 ? S 0:00 /usr/bin/spamc
387 ? S 0:00 /usr/bin/spamc
388 ? S 0:00 /usr/bin/spamc
389 ? S 0:00 /usr/bin/spamc
392 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
393 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
394 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
395 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
396 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
397 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
12925 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
12927 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
12929 ? S 0:00 /usr/bin/spamc
12930 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
12931 ? S 0:00 /usr/bin/spamc
12932 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
12934 ? S 0:00 /usr/local/bin/spamass-milter /var/run/sendmail/spamass.sock
12935 ? S 0:00 /usr/bin/spamc
12936 ? S 0:00 /usr/bin/perl /usr/sbin/spamd -d -u spamd -c -a -A
127.0.0.1,207.106.55.133
14217 pts/0 S 0:00 grep spam
While this state doesn't seem to usually impair SA's ability to process
mail, it will overflow the process table eventually. I've been unable
to figure out what makes them multiply like this. Is this
spamass-milter flakiness that we've been incorrectly attributing to
spamc?
Thanks for any insight.
Ross Vandegrift
[EMAIL PROTECTED]
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
