jpff writes: > I tried switching bayes off and it has run for 4 hrs before the > failing starts again > > Apr 18 08:16:37 snout spamd[29102]: spamd: copy_config timeout, respawning > child process after 1 messages at /usr/bin/spamd line 968. > Apr 18 08:16:46 snout spamd[29096]: spamd: copy_config timeout, respawning > child process after 1 messages at /usr/bin/spamd line 968. > 2007-04-18 08:17:16 1He4JI-0007Z8-MA spam acl condition: error reading from > spamd socket: Connection timed out > 2007-04-18 08:17:41 1He4JI-0007Z8-MA H=lists9.rootsweb.com [66.43.27.45] > F=<[EMAIL PROTECTED]> temporarily rejected after DATA > Apr 18 08:17:54 snout spamd[27089]: prefork: child states: BIBBB > Apr 18 08:17:54 snout spamd[27089]: prefork: child states: BIBBB > Apr 18 08:17:54 snout spamd[29101]: spamd: copy_config timeout, respawning > child process after 1 messages at /usr/bin/spamd line 968. > Apr 18 08:17:56 snout spamd[27089]: prefork: child states: BIBBB > .... > Apr 18 08:19:51 snout spamd[27089]: prefork: cannot ping 29102, file handle > not defined, child likely to still be processing SIGCHLD handler after > killing itself > Apr 18 08:19:52 snout spamd[27089]: prefork: killing failed child 29102 > fd=undefined at > /usr/local/share/perl/5.8.4/Mail/SpamAssassin/SpamdForkScaling.pm line 137. > Apr 18 08:19:52 snout spamd[27089]: prefork: killed child 29102 > Apr 18 08:19:52 snout spamd[27089]: prefork: cannot ping 29101, file handle > not defined, child likely to still be processing SIGCHLD handler after > killing itself > Apr 18 08:19:52 snout spamd[27089]: prefork: killing failed child 29101 > fd=undefined at > /usr/local/share/perl/5.8.4/Mail/SpamAssassin/SpamdForkScaling.pm line 137. > Apr 18 08:19:52 snout spamd[27089]: prefork: killed child 29101 > Apr 18 08:19:52 snout spamd[27089]: prefork: cannot ping 29096, file handle > not defined, child likely to still be processing SIGCHLD handler after > killing itself > Apr 18 08:19:52 snout spamd[27089]: prefork: killing failed child 29096 > fd=undefined at > /usr/local/share/perl/5.8.4/Mail/SpamAssassin/SpamdForkScaling.pm line 137. > Apr 18 08:19:52 snout spamd[27089]: prefork: killed child 29096 > Apr 18 08:19:54 snout spamd[27089]: spamd: handled cleanup of child pid 29096 > due to SIGCHLD > Apr 18 08:19:54 snout spamd[27089]: spamd: handled cleanup of child pid 29101 > due to SIGCHLD > Apr 18 08:19:54 snout spamd[27089]: spamd: handled cleanup of child pid 29102 > due to SIGCHLD > > Is it really that case that I am the only one with this kind of problem?
Well -- yes, it looks like it. ;) A bugzilla search for "copy_config timeout" yields 2 bugs resolved back in 3.1.0 days: http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4852 http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4699 a case where the copy_config timeout is working as it should, but a separate bug is triggered: http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4693 and a case where "copy_config" is referenced in passing: http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4906 So no sign of others reporting your bug, I'm afraid. copy_config failures like that -- unless it's under extremely heavy load -- should be rare; copy_config() nowadays it's a simple copy of entries from one hash object to another, which is a fast operation. Could you try using a different perl interpreter? Is the load that high? --j.
