[Bug 3625] New: sysklogd rpm install stopped spamd processing

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=3625

           Summary: sysklogd rpm install stopped spamd processing
           Product: Spamassassin
           Version: SVN Trunk (Latest Devel Version)
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: major
          Priority: P5
         Component: spamc/spamd
        AssignedTo: spamassassin-dev@incubator.apache.org
        ReportedBy: dallase@nmgi.com


I believe a syslog rpm install overnight stopped the processing of mail on 
several of my boxes here.. they were all running 3.0.0-pre2.

As you can see, I use daemontools to supervise the spamd daemon... there are 2 
spamd processes running, one is not responding and is contantly eating CPU.   
Both seem to be parent processes, as there is no 'spamd child' anywhere.

[root@spamfilter root]# ps auxwww | grep spamd
root      1383  0.0  0.0  1344   60 ?        S    Jul14   0:00 supervise spamd
root      2352  0.0  0.4 25036 1088 ?        S    Jul14   9:07 /usr/bin/perl -
T -w /usr/bin/spamd -q -x -m 4 --max-conn-per-child 25
root      2366  0.0  0.0  1352    4 ?        S    Jul14   
0:00 /usr/local/bin/multilog t s4096000 /var/log/spamd
root     14260  0.0  0.2  1764  596 pts/0    R    09:48   0:00 grep spamd
root     14262  0.0  3.1 25036 8012 ?        R    09:48   0:00 /usr/bin/perl -
T -w /usr/bin/spamd -q -x -m 4 --max-conn-per-child 25


Maillog shows the last message that was scanned came in at 12:08am...

Jul 21 00:08:26 spamfilter spamd[2746]: identified spam (19.6/5.0) for 
dmccloud@axiscsi.com:0 in 0.7 seconds, 1426 bytes.
Jul 21 00:08:26 spamfilter spamd[2746]: result: Y 19 - 
DRUGS_PAIN,FORGED_MUA_AOL_FROM,HELO_DYNAMIC_IPADDR,MIME_BOUND_DD_DIGITS,MIME_MIS
SING_BOUNDARY,MISSING_MIMEOLE,MISSING_OUTLOOK_NAME,MSGID_SPAM_CAPS,RCVD_BY_IP,RC
VD_DOUBLE_IP_SPAM,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DSBL,RCVD_IN_NJABL_DUL,RCVD_IN_
SORBS_DUL,RCVD_IN_XBL 
scantime=0.7,size=1426,mid=<IN...@schoolsucks.com>,autolearn=spam
Jul 21 02:57:50 spamfilter spamc[8100]: spamd responded with bad 
string 'PROCESS SPAMC/1.3'

The spamd responded with bad string continued from 12:08am until killing the 
spamd daemon at 8:45am.
stracing a spamc hangs on recv'ing data from spamd.

[root@spamfilter spamd]# echo | strace spamc
..
..
alarm(600)                              = 0
recv(3,

Loads are constantly running 1.00-1.30 on all the boxes
looks like spamd is in a loop....

 2352 root      16   0 21524 1088   408 S     2.5  0.4   9:12 spamd
18650 root      18   0 21952 7628   836 R     0.5  3.0   0:00 spamd

[root@spamfilter spamd]# kill -9 2352

after killing that process, it can now pipe through spamc, and you see the 
children respawned.

[root@spamfilter spamd]# echo | spamc
X-Spam-Score: 2.0
X-Spam-Flag: NO

[root@spamfilter spamd]# ps auxw | grep spamd
root      1383  0.0  0.0  1344   64 ?        S    Jul14   0:00 supervise spamd
root      2366  0.0  0.0  1352    4 ?        S    Jul14   
0:00 /usr/local/bin/multilog t s4096000 /var/log/spamd
root     19126  9.5  9.1 25068 23216 ?       S    09:52   0:02 /usr/bin/perl -
T -w /usr/bin/spamd -A 127.0.0.0/8 -i 127.0.0.1 -q -x
root     19154  2.0  9.4 25868 24112 ?       S    09:52   0:00 spamd child
root     19155  1.4  8.8 25516 22536 ?       S    09:52   0:00 spamd child
root     19157  3.1  9.5 25904 24120 ?       S    09:52   0:00 spamd child
root     19159  0.0  9.1 25068 23216 ?       S    09:52   0:00 spamd child

if I look at the other boxes, everything is identical, and the exact same 
problem occurred.   the only thing in common is they all updated their sysklogd 
last night at midnight (12:08am).

[root@spamfilter log]# cat yum.log
07/21/04 00:08:01 Updated: libxml2-devel.i386
--> 07/21/04 00:08:01 Updated: sysklogd.i386
07/21/04 00:08:01 Updated: libxml2.i386

[root@mailgw log]# cat yum.log
07/21/04 00:08:04 Updated: libxml2-devel.i386
--> 07/21/04 00:08:04 Updated: sysklogd.i386
07/21/04 00:08:04 Updated: libxml2.i386

[root@spamd1 log]# cat yum.log
07/21/04 00:08:00 Updated: libxml2-devel.i386
--> 07/21/04 00:08:00 Updated: sysklogd.i386
07/21/04 00:08:00 Updated: libxml2.i386

The rpm install of sysklogd would have restarted syslogging, would that cause 
spamd to do weird things??

i guess i can re-install the sysklogd rpm and try to replicate.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.