Paul Dickson wrote: > Yeah, if there were a verbose /diagnostic switch for rebuildspamdb.pl we > could see which item it is getting stuck on so it could be trouble-shot. It > isn't the same item every time, which says to me it's a bug in the rebuild > script. The fact that sometimes it completes without issue tells me the > 'problem' .eml has been replaced by something new. At some point another > email that hangs up the rebuild script arrives and it's back to hanging, or > taking so long it might as well be killed. > > Hard to troubleshoot when you don't know which out of 60,000 combined emails > are causing the problem ;) > > > > Paul K. Dickson > Systems Administrator > Frederick County Government, IIT > [email protected] > 301-600-2399/x12399 > Come on guys, this is troubleshooting 101. :) If we assume your theory is correct then we already know that removing the spam fixes the problem, so now you add half back to see which half has the trouble maker. If it works you swap halves. Repeat the process on the failing half thus continually reducing the sample size until you find the guilty party, then put it in by itself to confirm failure. Once you've done that, send the culprit to Fritz, and I'm betting he'll gladly track down the cause and fix the script since you've put in the time to identify the failure mode. Otherwise, he's just like everyone else, and has lots to do, most if it probably has higher priority on his list.
Melvin ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
