It looks like it may be some sort of memory leak in spamd. A long ps gave me some additional relevant details to the problem. As you can see, two spamd sessions are in lock_p state. There are also two spamc connections in FIN_WAIT2.
000 S qd 22432 22431 0 75 0 - 331 wait4 13:49 ? 00:00:00 /var/maildir/bin/qmail-qfilter /usr/bin/spamc -p 000 S qd 22352 22351 0 76 0 - 331 wait4 13:42 ? 00:00:00 /var/maildir/bin/qmail-qfilter /usr/bin/spamc -p 000 S qd 22432 22431 0 75 0 - 331 wait4 13:49 ? 00:00:00 /var/maildir/bin/qmail-qfilter /usr/bin/spamc -p 000 S qd 22352 22351 0 76 0 - 331 wait4 13:42 ? 00:00:00 /var/maildir/bin/qmail-qfilter /usr/bin/spamc -p 000 S qd 22351 5516 0 75 0 - 333 wait4 13:42 ? 00:00:00 /var/maildir/bin/qmail-smtpd 000 S qd 22431 5516 0 75 0 - 333 wait4 13:49 ? 00:00:00 /var/maildir/bin/qmail-smtpd 140 S spamd 910 1 0 75 0 - 4241 schedu Oct24 ? 00:00:40 /usr/bin/perl /usr/bin/spamd -u spamd -p 1212 040 D spamd 22354 910 19 75 0 - 33029 lock_p 13:42 ? 00:01:14 /usr/bin/perl /usr/bin/spamd -u spamd -p 1212 040 D spamd 22434 910 2 75 0 - 4299 lock_p 13:49 ? 00:00:00 /usr/bin/perl /usr/bin/spamd -u spamd -p 1212 000 S qd 22433 22432 0 76 0 - 475 schedu 13:49 ? 00:00:00 /usr/bin/spamc -p 1212 000 S qd 22353 22352 0 76 0 - 475 schedu 13:42 ? 00:00:00 /usr/bin/spamc -p 1212 000 R jbly 22436 22386 0 76 0 - 46 - 13:49 pts/2 00:00:00 grep spam [jbly@boink jbly]$ ps -eo pid,min_flt,maj_flt,cmd | grep spam 910 547971 15718 /usr/bin/perl /usr/bin/spamd -u spamd -p 1212 -d 22352 36 316 /usr/mail/bin/qmail-qfilter /usr/bin/spamc -p 1212 22353 22 152 /usr/bin/spamc -p 1212 22354 71900 197674 /usr/bin/perl /usr/bin/spamd -u spamd -p 1212 -d 22847 36 316 /usr/mail/bin/qmail-qfilter /usr/bin/spamc -p 1212 22848 17 122 /usr/bin/spamc -p 1212 22849 1383 1470 /usr/bin/perl /usr/bin/spamd -u spamd -p 1212 -d 22854 37 148 grep spam That 71900 minor page faults and and 197674 major is rather concerning to me. (Oh and for the record yes, the system is crawling right now.) I also now see why it's intermittent. Spamd is hitting its bounds for memory allocation and gets killed. However this will not happen if enough of these stray spamd processes get run at once. The system simply can't recover fast enough at that point. So now I need to figure out where the leak is. Stay tuned. Same bat-time, same bat-channel. -James > -----Original Message----- > ... > For your problem, first check any local IPTables firewall rules you have an > make sure you're not doing something silly that will block fin packets that > don't have the ack bit set. > ... > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
