(bump) Still getting this on and off. Thanks
On Sat, May 1, 2010 at 11:31 AM, K Post <nntp.p...@gmail.com> wrote: > This builds on my previous thread "SMTP not responding every night at > the same approximte time" > > > Win32, 2.0.2 (1.0.12) -- I haven't updated yet, but have seen similar > things to this sporatically for a while now. > > Here's a clip from the log: > May-01-10 00:41:33 msg88264-08990 88.199.249.6 > <spamm...@somedomain.com> Connection idle for 180 secs - timeout > May-01-10 00:41:48 msg88260-10103 88.199.249.6 > <spamm...@somedomain2.com> Connection idle for 180 secs - timeout > May-01-10 00:42:29 Info: Loop in Worker_2 was not active for 189 seconds > May-01-10 00:42:39 Info: Worker_2 : last sigoff in main, > c:\assp\assp.pl, 9301, main::sigoffTry, 1, , , at 11 0:3345 > 1272688425.69521 - 9301 > May-01-10 00:43:00 msg88307-04742 [InvalidAddress] 190.166.204.2 > <spamm...@thriddomain.com> invalid address rejected: > i...@ourdomain.org > May-01-10 00:43:01 Info: Worker_2 : last sigon in main, > c:\assp\assp.pl, 9303, main::sigonTry, 1, , , at 11 0:3345 > 1272688425.69543 - 9303 > May-01-10 00:43:01 msg88307-04742 190.166.204.2 > <spamm...@thriddomain.com> Message-Score: added 2 for invalid address > i...@ourdomain.org, total score for this message is now 2 > > Lines 9301 and 9301 are: > &sigoffTry(__LINE__); > and > &sigonTry(__LINE__); > > I've seen this warning / error before. It almost always seems to be > during rebuilds (which this error was). > > We've rebuilt since this error, but I know where the slowdown is. > Look at this excerpt from the rebuild log. > May-01-10 05:43:15 done - Generating weighted Bayesian tuplets > > May-01-10 05:43:15 Resulting file 'c:/assp/spamdb.rb.tmp' is 3,908,453 bytes > May-01-10 05:47:53 Bayesian Pairs: 165,592 in new mail, 1,774,986 now in list > > May-01-10 05:47:57 HELO Blacklist: 0 in new mail, 2272 now in list > > See that lag between the 2nd and 3rd line? What processing is going > on between building spamdb.rb.tmp and reporting the pairs. Can the > processing reqired to do that be tweaked to either be less intensive > (and take longer), have it be optimized, or have it yield to normal > ASSP operating better? > > I'm pretty sure that at 44 after midnight this same thing was going > on. USUALLY, I get a text message that SMTP isn't responding for the > couple minutes between lines 2 and 3 above. Sometimes (as in last > night) I get a warning/info line logged, but no outage. > > This is running on a fairly old and overburdened machine, but it's > what we've got - and as a charity, that has to be good enough :( > I'm just trying to get to the root of this annoyance and see if > there's anything that could be done with the code to improve it. > > THANK YOU > ------------------------------------------------------------------------------ _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
