If you look at the error message you'll see the line and then a line following it with a * indicating which character in the line caused the parser to fail. Because you are using tab-delimiters the * doesn't quite line up (it counts tab as 1 character rather than a tab stop) but replacing the tabs with spaces shows that the parser failed precisely where Aengus suggested.
You have written a log file format that is only looking for lines with www.usawaterquality.org in them so the 'corrupt' lines are those that don't have that. -- Jeremy Wadsack Seven Simple Machines > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:analog-help- > [EMAIL PROTECTED] On Behalf Of Aimee Mandeville > Sent: Thursday, August 02, 2007 5:59 AM > To: [email protected] > Subject: [analog-help] RE: currupt files > > Here is a sample of the error file that is being generated. > > Aimee > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Wednesday, August 01, 2007 3:00 PM > To: [email protected] > Subject: analog-help Digest, Vol 36, Issue 1 > > Send analog-help mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.meer.net/mailman/listinfo/analog-help > or, via email, send a message with subject or body 'help' to > [EMAIL PROTECTED] > > You can reach the person managing the list at > [EMAIL PROTECTED] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of analog-help digest..." > > > Today's Topics: > > 1. Re: corrupt files (Aengus) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 31 Jul 2007 18:14:33 -0400 > From: "Aengus" <[EMAIL PROTECTED]> > Subject: Re: [analog-help] corrupt files > To: "Support for analog web log analyzer" <[email protected]> > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; format=flowed; charset=iso-8859-1; > reply-type=original > > On Tuesday, July 31, 2007 7:33 AM [EDT], > Aimee Mandeville <[EMAIL PROTECTED]> wrote: > > > Thanks for the clarification on that. Do you have any thoughts as to > > why Analog is having difficulty parsing these lines? I've attached a > > sample of the CORRUPT lines. > > > > The log file I am analyzing has 69,989 lines and 65,634 of them are > > corrupt. > > > > I am using the following format: > > > > LOGFORMAT (#%j) > > > > LOGFORMAT > > > (%S\t%u\t%B\t%Y-%m-%d\t%h:%n:%j\t%j\t%j\t%j\t%j\t%j\t%j\t%j\t%b\t%j\t%j\ > > t%r\t%j\t%c\twww.usawaterquality.org\t%j) > > You haven't provided any examples of the lines that Analog considers > corrupt, but at a guess, they don't have www.usawaterquality.org in > them. > > If you enable debugging (DEBUG ON), Analog will generate output that > will > indicate where the line stops matching th LOGFORMAT Analog expected to > find. > > Aengus > > > > > ------------------------------ > > +----------------------------------------------------------------------- > - > | TO UNSUBSCRIBE from this list: > | http://lists.meer.net/mailman/listinfo/analog-help > | > | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general > | List archives: http://www.analog.cx/docs/mailing.html#listarchives > +----------------------------------------------------------------------- > - > > > End of analog-help Digest, Vol 36, Issue 1 > ****************************************** +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Analog Documentation: http://analog.cx/docs/Readme.html | List archives: http://www.analog.cx/docs/mailing.html#listarchives | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general +------------------------------------------------------------------------
