http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4693





------- Additional Comments From [EMAIL PROTECTED]  2005-11-28 20:08 -------
okay.. this is semi-reproducable.   starting spamd up like this

# spamd -p 777 --timeout-child=1 -D

and passing a message to it via

# cat msg.txt | spamc -p 777

gets me...

[27182] dbg: prefork: ordered 27204 to accept
[27182] dbg: prefork: sysread(7) not ready, wait max 300 secs
[27204] info: spamd: connection from localhost.localdomain [127.0.0.1] at port 
37675
[27182] dbg: prefork: child 27204: entering state 2
[27182] dbg: prefork: new lowest idle kid: 27205
[27204] info: spamd: setuid to dallase succeeded
[27204] error: child processing timeout at /usr/bin/spamd line 1085, <GEN7> 
line 2.
[27204] warn: spamd: timeout: (1 second timeout while trying to PROCESS) 
at /usr/bin/spamd line 1678, <GEN7> line 2.
[27204] dbg: config: copying current conf from backup
[27182] dbg: prefork: child 27204: entering state 1
[27182] dbg: prefork: new lowest idle kid: 27204
[27182] dbg: prefork: child reports idle
[27182] info: prefork: child states: II

then, if i let the spamd engine sit a bit before i issue a SIGINT to it, i get 
an error on the last line, which talks about "during global destruction".

[27204] dbg: prefork: sysread(8) not ready, wait max 300 secs
[27205] dbg: prefork: periodic ping from spamd parent
[27205] dbg: prefork: sysread(9) not ready, wait max 300 secs
[27204] dbg: prefork: periodic ping from spamd parent
[27204] dbg: prefork: sysread(8) not ready, wait max 300 secs
[27204] dbg: prefork: periodic ping from spamd parent
[27204] dbg: prefork: sysread(8) not ready, wait max 300 secs
[27205] dbg: prefork: periodic ping from spamd parent
[27205] dbg: prefork: sysread(9) not ready, wait max 300 secs
[27205] dbg: prefork: periodic ping from spamd parent
[27205] dbg: prefork: sysread(9) not ready, wait max 300 secs
[27182] dbg: prefork: new lowest idle kid: 27204
[27182] info: spamd: handled cleanup of child pid 27205 due to SIGCHLD
[27182] dbg: prefork: new lowest idle kid: none
[27182] info: spamd: handled cleanup of child pid 27204 due to SIGCHLD
[27182] info: spamd: server killed by SIGINT, shutting down
[27182] error: tcp timeout 
at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/SpamdForkScaling.pm line 
195 during global destruction.
tcp timeout 
at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/SpamdForkScaling.pm line 
195 during global destruction.


i'm not sure if these are related, but i'd wager a guess that they are... 
seeing that in Comment #1, a --timeout-child=60 was reached prior to the system 
spinning out of control from the global destruction log entries.




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

Reply via email to