http://bugzilla.spamassassin.org/show_bug.cgi?id=3983
------- Additional Comments From [EMAIL PROTECTED] 2004-12-14 14:20 -------
Ah! I think that there may be a race condition. I changed the line
dbg ("prefork: adjust: decreasing, too many idle children ($num_idle >
$self->{max_idle}), killed $pid");
in SpamdForkScaling.pm from dbg to warn and found the following sequence in
syslog when one of the children entered state 'K'.
Dec 14 15:10:14 bluegill.adi.com spamd[1459]: prefork: child states: III at
/opt/perl/lib/site_perl/5.8.5/Mail/SpamAssassin/SpamdForkScaling.pm line 331,
<GEN6> line 349.
Dec 14 15:10:14 bluegill.adi.com spamd[1459]: server hit by SIGCHLD
Dec 14 15:10:14 bluegill.adi.com spamd[1459]: handled cleanup of child pid 13252
Dec 14 15:10:14 bluegill.adi.com spamd[1459]: prefork: adjust: decreasing, too
many idle children (3 > 2), killed 13252 at /opt/perl/lib/site_perl/5.8.5/
Mail/SpamAssassin/SpamdForkScaling.pm line 380, <GEN6> line 349.
Dec 14 15:10:14 bluegill.adi.com spamd[1459]: prefork: child states: IIK at
/opt/perl/lib/site_perl/5.8.5/Mail/SpamAssassin/SpamdForkScaling.pm line 331.
Note the order of the lines. Most of the time, the line with 'prefork: adjust:
decreasing, too many idle children' happens before the lines with 'server hit
by SIGCHLD' and 'handled cleanup of child'. This time it came after those
lines and we lost a child. I expect that this is a race condition.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
