http://bugzilla.spamassassin.org/show_bug.cgi?id=3828
------- Additional Comments From [EMAIL PROTECTED] 2004-12-08 11:10 -------
just had a child hang on another box.. took up 7+ min of cpu before it was
killed. here is the last 2 dbg mesgs from the log for pid 29170.
2004-12-08 12:31:52.653883500 debug: [29170] check:
subtests=__COMMENT_EXISTS,__CT,__CTYPE_HAS_BOUNDARY,__CTYPE_MULTIPART_ALT,__HAS_MSGID,__HAS_SUBJECT,__MIME_HTML,__MIME_QP,__MIME_VERSION,__MSGID_OK_DIGITS,__SANE_MSGID,__TAG_EXISTS_BODY,__TAG_EXISTS_HEAD,__TAG_EXISTS_HTML
2004-12-08 12:31:52.653926500 debug: [29170] call_plugins: run callback on
check_end
i added the 'run callback' dbg message in SpamAssassin.pm when i was trying to
get deeper into the code to find where it was hanging. the common thing i find
among all children that hang like this is that it appears to happen in
PluginHandler::callback()... i'm going to dbg that function out to see if that
is where its hanging up. it has to be somewhere within the foreach loops or
the call to &$methodref i would guess.
foreach my $plugin (@{$self->{plugins}}) {
foreach my $cbpair (@{$self->{cbs}->{$subname}}) {
$ret = &$methodref ($plugin, @_);
if it made it through those, it should have gave me a logmsg() from spamd. a
normal message process currently debugs for me like this...
2004-12-08 12:29:37.523345500 debug: [29170] check:
subtests=__COMMENT_EXISTS,__CT,__CTYPE_HAS_BOUNDARY,__CTYPE_MULTIPART_ALT,__HAS_MSGID,__HAS_SUBJECT,__MIME_BASE64,__MIME_HTML,__MIME_VERSION,__MSGID_OK_DIGITS,__MSGID_OK_HOST,__SANE_MSGID,__TAG_EXISTS_BODY,__TAG_EXISTS_CENTER,__TAG_EXISTS_HTML
2004-12-08 12:29:37.523390500 debug: [29170] call_plugins: run callback on
check_end
2004-12-08 12:29:37.523392500 logmsg: [29170] clean message (1.7/7.0) for
[EMAIL PROTECTED]:0 in 3.0 seconds, 18052 bytes.
2004-12-08 12:29:37.523395500 logmsg: [29170] result: . 1 -
AWL,DCC_CHECK,HTML_IMAGE_RATIO_04,HTML_MESSAGE,HTML_TAG_EXIST_TBODY,MIME_BASE64_TEXT,NO_REAL_NAME
scantime=3.0,size=18052,mid=<[EMAIL PROTECTED]>,autolearn=disabled
2004-12-08 12:29:37.523438500 logmsg: [29170] calling status->finish
2004-12-08 12:29:37.523440500 debug: [29170] generic: call_plugins
per_msg_finish
2004-12-08 12:29:37.523442500 debug: [29170] call_plugins: run callback on
per_msg_finish
2004-12-08 12:29:37.523461500 debug: [29170] generic: call_plugins
per_msg_finish complete
2004-12-08 12:29:37.523463500 debug: [29170] generic: done deleting self keys
2004-12-08 12:29:37.523465500 logmsg: [29170] calling mail->finish
2004-12-08 12:29:37.523467500 debug: [29170] finish: called for Message.pm
2004-12-08 12:29:37.523469500 debug: [29170] finish: completed for Message.pm
so after a check_end, it should give me the result and start cleaning up. man i
wish i could reproduce this and not wait for it to happen :)
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
