http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5313
------- Additional Comments From [EMAIL PROTECTED] 2007-03-22 23:26 ------- (In reply to comment #28) > (In reply to comment #27) > > Created an attachment (id=3886) --> (http://issues.apache.org/SpamAssassin/attachment.cgi?id=3886&action=view) [edit] [edit] > > patch > > > > BTW, please try applying this patch (should apply ok to 3.1.x). I have a > > feeling it may fix the bug! it also adds some additional lightweight > > instrumentation that may at least produce useful info in the logs to aid in > > debugging. > > Of the 4 machines experiencing this problem: > > 1 - Has had the patch applied > 1 - Has been set to run with "--round-robin" > 2 - Have been untouched. > > "--round-robin" is a complete memory hog (which I'm sure you know). Other > than > that, it's stable thus far. > > I will let you know the results here within the next 24-48 hours. > > Thanks Justin! Summary of patch: Firstly, a snippet from the logs with your patch applied: [...snip...] Mar 23 01:08:16 smtp-proxy02 spamd[62786]: JMD bug5313 child_exited 61509 at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/SpamdForkScaling.pm line 113. Mar 23 01:08:16 smtp-proxy02 spamd[62786]: JMD bug5313 child_just_exited = 0 at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/SpamdForkScaling.pm line 221. Mar 23 01:08:16 smtp-proxy02 spamd[62786]: JMD bug5313 IO::Socket=GLOB(0x95f9548)/18 removed from selector at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/SpamdForkScaling.pm line 381. Mar 23 01:08:16 smtp-proxy02 spamd[62786]: JMD bug5313 child_just_exited = 0 at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/SpamdForkScaling.pm line 221. Mar 23 01:08:16 smtp-proxy02 spamd[62786]: JMD bug5313 child_exited 61508 at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/SpamdForkScaling.pm line 113. Mar 23 01:08:16 smtp-proxy02 spamd[62786]: JMD bug5313 child_just_exited = 0 at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/SpamdForkScaling.pm line 221. Mar 23 01:08:16 smtp-proxy02 spamd[62786]: JMD bug5313 IO::Socket=GLOB(0x95f732c)/17 removed from selector at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/SpamdForkScaling.pm line 381. Mar 23 01:08:16 smtp-proxy02 spamd[62786]: JMD bug5313 child_just_exited = 0 at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/SpamdForkScaling.pm line 221. Mar 23 01:08:17 smtp-proxy02 spamd[62786]: JMD bug5313 child_just_exited = 0 at /usr/local/lib/perl5/site_perl/5.8.8/Mail/SpamAssassin/SpamdForkScaling.pm line 221. [...snip...] Good news! The bug has yet to crop up and it's been well over the time period it normally takes for this bug to crop up. This particular bug, seems to be fixed with your patch applied. Certainly if I experience anything different I will append to this bug report with any further findings. In regards to round-robin, (since you had told me to try it) it too seems to fix the problem as suggested, however be aware that even with 4 gigs of memory I still at one point ate up all memory and additionally over 1g of swap. Not a good solution for high volume filters like I have setup. This just an informative message and will be changing from round-robin back to 3.1.8 w/ your patch applied in the morning. ;) The other two remaining machines that I have yet to touch will remain as such until our busiest days see the light of day with your patch applied (Monday/Tuesday). Again, if I happen to run into any problems on these given days, you'll hear from me, otherwise, it seems we are good to go with thus far. Thanks for the help. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
