[Bug 3667] New: spamd dies (prerelease version - 3.0.0-pre3), Debian stable

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

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

           Summary: spamd dies (prerelease version - 3.0.0-pre3), Debian
                    stable
           Product: Spamassassin
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P4
         Component: spamc/spamd
        AssignedTo: spamassassin-dev@incubator.apache.org
        ReportedBy: will@code404.com


Spamd, running on a Debian (woody/stable) machine; SA version is 3.0.0-pre3.
Perl is v5.6.1, which should be supported with this SA release. Spamassassin
built (cleanly) from source.

Normally, when spamd is running, there is a master process with several child
processes:
root      2041     1 15 13:53 ?        00:00:00 /usr/local/bin/spamd -d
jason     2048  2041  4 13:53 ?        00:00:00 spamd child
root      2049  2041  0 13:53 ?        00:00:00 spamd child
root      2050  2041  0 13:53 ?        00:00:00 spamd child
root      2051  2041  0 13:53 ?        00:00:00 spamd child
root      2052  2041  0 13:53 ?        00:00:00 spamd child

We have seen several instances of spamd dying at (seemingly) random intervals.

When this happens, there is a master process, and then one child process which
keeps dying.

root     30172     1  0 Aug01 ?        00:03:46 /usr/local/bin/spamd -d
root     32122 30172  0 13:51 ?        00:00:00 /usr/local/bin/spamd -d

root     30172     1  0 Aug01 ?        00:03:47 /usr/local/bin/spamd -d
root      1140 30172  0 13:52 ?        00:00:00 /usr/local/bin/spamd -d

root     30172     1  0 Aug01 ?        00:03:47 /usr/local/bin/spamd -d
root      1275 30172  0 13:52 ?        00:00:00 /usr/local/bin/spamd -d

Running strace on the parent process shows this... I'll try to attach a longer
file of this to the bug report later.

rt_sigaction(SIGCHLD, {0x80933f0, [], SA_RESTART|0x4000000}, {0x80933f0, [],
SA_RESTART|0x4000000}, 8) = 0
wait4(-1, 0xbfffe818, 0, NULL)          = -1 ECHILD (No child processes)
rt_sigaction(SIGPIPE, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGPIPE, {0x80933f0, [], SA_RESTART|0x4000000}, {SIG_DFL}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [CHLD], 8) = 0
send(4, "<22>spamd[30172]: server hit by "..., 49, 0) = -1 ENOTCONN (Transport
endpoint is not connected)
fork()                                  = 923
wait4(923, [WIFEXITED(s) && WEXITSTATUS(s) == 0], 0, NULL) = 923
rt_sigaction(SIGPIPE, {SIG_DFL}, {0x80933f0, [], SA_RESTART|0x4000000}, 8) = 0
sigreturn()                             = ? (mask now [])
--- SIGCHLD (Child exited) ---



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