Re: [Declude.JunkMail] Log Corruption

[Matt]

Title: Message

I guess this is somewhat rhetorical at this point, but why change the logs to single lines and not at the same time seek to normalize the format using the same standards that are used for Web logs or even a simple comma separated (quoted qualifier) database format? Matt Andy Schmidt wrote: >> I haven't seen the new log format <<   I'm not aware of any new log format.  The FORMAT of the log files stayed the same (regular "version" specific changes may apply) on the ORDER changes.   Meaning: all log lines for a SINGLE message are now appearing in one set of lines - instead of log lines for various different messages appearing in strict "time" order.   Before it was a "time" log, now it's more of a "message" log - but the log lines stay the same. Best Regards Andy Schmidt H&M Systems Software, Inc. 600 East Crescent Avenue, Suite 203 Upper Saddle River, NJ 07458-1846 Phone:  +1 201 934-3414 x20 (Business) Fax:    +1 201 934-9206 http://www.HM-Software.com/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Matt Sent: Tuesday, March 01, 2005 04:16 PM To: Declude.JunkMail@declude.com Subject: Re: [Declude.JunkMail] Log Corruption There has always been corruption of the logs.  What seems to have changed here is that there is a new log format and the programmed exceptions in DLanalyzer are no longer able to handle the types of corruption as seamlessly as in the past. I haven't seen the new log format, but I would imagine that if they built it in a column format and kept it to a single line, similar to Web logging standards, it should be even easier to parse the data and correct for issues.  If they didn't keep to consistent columns, then this could be just as big of an issue to parse as before and a lot of the exception rules would have to be rewritten for the new format. Matt Goran Jovanovic wrote: Yesterday's report on my declude logfile showed =...................................1........0.01% 02/28/2005..........................1........0.01% FF156FB0094D05A.....................1........0.01% I005................................1........0.01% QCEA370970074D08A...................1........0.01% SET.................................1........0.01% SNIFFQCE053ABD0086D062..............1........0.01% This is from Total Messages Processed: 12,316 And loglevel set to HIGH and the size of the file is 122 MB I am running 2.0.5 Goran Jovanovic The LAN Shoppe -----Original Message----- From: [EMAIL PROTECTED] [mailto:Declude.JunkMail- [EMAIL PROTECTED]] On Behalf Of Colbeck, Andrew Sent: Tuesday, March 01, 2005 2:33 PM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Log Corruption I had the opposite experience. Back at, oh, 1.7x I ran on LOGLEVEL HIGH, and had lots of log corruption. I had to drop down to MID. The increase in spam volume made it such that at MID, I had lots of log corruption again. With 2.x and the lines being written in a batch, I noticed an immediate drop in my disk usage and a huge drop in corrupted lines. Andrew 8) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Andy Schmidt Sent: Tuesday, March 01, 2005 9:22 AM To: Declude.JunkMail@declude.com Subject: RE: [Declude.JunkMail] Log Corruption Hi, Yesterday was actually a good day (here a snippet): TEST # FAILED Percentage 18:51:58................1........0.01% SNIF02/28/2005..........1........0.01% SPA02/28/2005...........1........0.01% WEIG02/28/2005..........1........0.01% Sure, I used to get reports that were "clean", but considering it only happens a "few" times a day, I don't consider it a major issue and I can live with it. Also I used to run in MID log level, but after 1.76 (or so), they removed the test summary line form MID level, and I needed to switch to HIGH log level. It's entirely possible that the log corruption is not really specific to 2.0x - but rather a secondary result because they forded me to deal with tremendously large log files (vs. the old MID log files). Best Regards Andy Schmidt H&M Systems Software, Inc. 600 East Crescent Avenue, Suite 203 Upper Saddle River, NJ 07458-1846 Phone: +1 201 934-3414 x20 (Business) Fax: +1 201 934-9206 http://www.HM-Software.com/ --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com. -- ===================================================== MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ ===================================================== -- ===================================================== MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ =====================================================