http://bugzilla.spamassassin.org/show_bug.cgi?id=4026
Summary: spamd spawns children endlessly
Product: Spamassassin
Version: 3.0.1
Platform: All
OS/Version: Linux
Status: NEW
Severity: major
Priority: P5
Component: spamc/spamd
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
I don't know when exactly it happens, but it is again time for it. Spamd will
not accept any new connections because the original spamd instance is spawning
one child after another, which seems to die instantly without processing
anything. The following is the output of a ptrace of the father spamd process.
---
fork() = 26236
wait4(26236, [WIFEXITED(s) && WEXITSTATUS(s) == 0], 0, NULL) = 26236
rt_sigaction(SIGPIPE, {SIG_DFL}, {0x80933f0, [], SA_RESTART|0x4000000}, 8) = 0
wait4(-1, 0xbffff658, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigaction(SIGCHLD, {0x80933f0, [], SA_RESTART|0x4000000}, {0x80933f0, [],
SA_RESTART|0x4000000}, 8) = 0
sigreturn() = ? (mask now [])
--- SIGCHLD (Child exited) ---
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[13358]: server hit by "..., 41, 0) = -1 ENOTCONN (Transport
endpoint is not connected)
fork() = 26237
wait4(26237, [WIFEXITED(s) && WEXITSTATUS(s) == 0], 0, NULL) = 26237
rt_sigaction(SIGPIPE, {SIG_DFL}, {0x80933f0, [], SA_RESTART|0x4000000}, 8) = 0
wait4(-1, 0xbffff658, WNOHANG, NULL) = -1 ECHILD (No child processes)
rt_sigaction(SIGCHLD, {0x80933f0, [], SA_RESTART|0x4000000}, {0x80933f0, [],
SA_RESTART|0x4000000}, 8) = 0
sigreturn() = ? (mask now [])
--- SIGCHLD (Child exited) ---
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[13358]: server hit by "..., 41, 0) = -1 ENOTCONN (Transport
endpoint is not connected)
fork() = 26238
---
No mails are scanned anymore and people start complaining about the amount of
spam they get. This started after the upgrade from 2.63 to 3.0.1 and I will
downgrade to 2.63 asap. Do you need any other information that could be
helpful?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
