deiwise ([EMAIL PROTECTED]):
> I recently asked my hosters to zip up my log files on the server, as > I needed to download them all again following some fun I had with > FDisk - as "text only" it would have taken a while as there was > about 600-800MB worth. > After getting the zipped archive and extracting it > (successfully), I can no longer get Analog to work. > It's always worked perfectly before, so I'm either > thinking that the files themselves are corrupt, or I'm > using the wrong LOGFORMAT. > I didn't backup my analog.cfg file stupidly - but I > did backup the LOGFORMAT commands, as shown below: > LOGFORMAT COMBINED > LOGFORMAT > (%m/%d/%Y%h:%n:%j\t%s\t%v\t%j\t%u\t%j\t%r\t%f\t%j\t%B\t%c\t%b\t%T) > I'm calling the LOGFILE normally, as is the OUTFILE - > but it's still reporting "corrupt logfile - try using > an alternative LOGFORMAT." The LOGFORMATs above are > definately the ones that have worked in the past; and > I've checked that the logs are plain text and not > containing bad characters (as a result of a bad > download). > I'd be most grateful for any clues someone might be > able to offer, or suggestions. Use analog --settings to find out how Analog is applying LOGFORMAT directives to LOGFILES. Use DEBUG C to have Analog tell you exactly which lines are corrupt and where in the line the parsing stops. -- Jeremy Wadsack Wadsack-Allen Digital Group +------------------------------------------------------------------------ | This is the analog-help mailing list. To unsubscribe from this | mailing list, go to | http://lists.isite.net/listgate/analog-help/unsubscribe.html | | List archives are available at | http://www.mail-archive.com/[email protected]/ | http://lists.isite.net/listgate/analog-help/archives/ | http://www.tallylist.com/archives/index.cfm/mlist.7 +------------------------------------------------------------------------
