You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2004/07/27 17:27:03 UTC

[Bug 3637] New: spamd child in a loop

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

           Summary: spamd child in a loop
           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


been seeing this occur almost daily... have to kill -9 the pid for spamd to 
respawn the child.

  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
31833 root      20   0 29576  28M  2252 R    67.3  3.8 296:28 spamd

[root@spamd1 root]# strace -p 31833

^C

strace never shows any output.  that PID in the mail log shows the connection 
comes in but never finishes processing.

[root@spamd1 root]# grep "\[31833\]" /var/log/maillog
Jul 27 01:39:20 spamd1 spamd[31833]: connection from localhost [127.0.0.1] at 
port 58116
Jul 27 01:39:20 spamd1 spamd[31833]: processing message <E1BpLcK-0001SY-
1X@pink.serverstoday.com> for xxx@xxxx.com:0.


on another box, same thing...


  PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
21845 root      19   0 27164  26M   120 R    78.9  3.5 320:48 spamd

[root@spamd2 root]# strace -p 21845

^C
[root@spamd1 root]# grep "\[21845\]" /var/log/maillog
Jul 27 01:22:09 spamd2 spamd[21845]: connection from localhost [127.0.0.1] at 
port 53224
Jul 27 01:22:09 spamd2 spamd[21845]: processing message <E1BpLLg-00066g-
3A@pink.serverstoday.com> for xxx@xxxx.com:0.


the only thing in common between spamd1 and spamd2 is those particular children 
both hung on message from "pink.serverstoday.com".


my log shows the mail was accepted but spamc reached it timeout of 60 seconds..

+---------+---------------------+--------------------------------+--------------
--------
| elapsed | datetime            | mailfrom                       | rcptto
+---------+---------------------+--------------------------------+--------------
--------
| 60.5699 | 2004-07-27 01:23:09 | mydbmail@pink.serverstoday.com | 
dpcwerth@ruraltel.net      
| 60.5894 | 2004-07-27 01:40:20 | mydbmail@pink.serverstoday.com | 
lbean@ruraltel.net         

so spamc disconnected from spamd after its timeout, but those spamd children 
continued to run forever for some reason.

so, should there be a spamd children timeout setting as well to prevent this?

i know the best solution is obviously figure out what caused the loop, but a 
timeout on spamd children just in case would be nice dont you think?

d



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