On 8/29/99 4:44 PM Bob Williams ([EMAIL PROTECTED]) wrote:

>Hello,
>
>A while back, the logs produced by my ISP's installation of W* 
>suddenly stopped working with Analog. I've upgraded Analog two or 
>three times since then, and am currently trying to use 3.31a (Mac). 
>Regardless of whether I use my old config file or the default one 
>included with Analog, I get the same results.
>
>Here are the first few lines from my most recent log file:
>
>192.231.106.2:80       08/12/99        22:55:00        OK      192.231.106.2 
>       :trivectus:Products:SuperLockPro:Documentation:Introduction.html 
>       5023 
>       http://www.trivectus.com/Products/SuperLockPro/Documentation/CoverPag 
>e.html Mozilla/4.61 (Macintosh; U; PPC)
>192.231.106.2:80       08/12/99        22:55:11        OK      192.231.106.2 
>       :trivectus:Products:SuperLockPro:Documentation:Background.GIF   556 
>       http://www.trivectus.com/Products/SuperLockPro/Documentation/Introduc 
>tion.html      Mozilla/4.61 (Macintosh; U; PPC)
>
>When I try to run Analog on this file, this is what I get:
>
>Processing...
>analog: Warning C: Ignoring corrupt format line in logfile
>   (For help on all errors and warnings, see docs/errors.html)
>analog: Warning C:   (reason: one item occurs twice in format)
>analog: Warning C: Ignoring corrupt format line in logfile
>[repeat previous a number of times]
>analog: Warning L: Large number of corrupt lines in logfile WebSTAR.log: try
>   different LOGFORMAT
>     Current logfile format:
>       !!LOG_FORMAT<WebSTAR format string>\n
>       !!%j\n
>analog: Warning R: Turning off empty time reports
>[more report warnings]
>
>The report file pretty much just says that every line was corrupt. 
>This is with the format set to WEBSTAR; with the format set to AUTO, 
>I get this:
>
>Processing...
>analog: Warning F: Can't auto-detect format of logfile WebSTAR.log: ignoring
>   it
>
>and then all the report warnings.
>
>It looks to me like it might be complaining about the dual IP 
>addresses. I'm not at all familiar with W*'s log format, but I'd 
>guess that since one of the addresses has a port number, that it is 
>being used to represent something different and thus is not 
>duplicated information.
>
>What makes this really weird is that my ISP has told me that I'm one 
>of a very small handful of customers that are all having this 
>problem. None of the other customers are, and their reports are being 
>produced by the same server installation. The engineers there aren't 
>sure what to make of it. All I know at this point is that i have a 
>couple million lines of log files that I need processed but can't.
>
>Can someone please advise me on what to do, or what to tell my ISP to do?

I hope those were not literally the first few lines of your log file. 
Every WebSTAR log file must start with a '!!LOG_FORMAT' line. The warning 
messages you are getting suggests that there might be a format line, 
although Analog considers it corrupt. If there is a format line, it would 
start '!!LOG_FORMAT', then you should show us what it says. I can't tell 
exactly what is happening without it. If there isn't a format line then 
that is your problem.

Newer versions of WebSTAR may have a couple of other lines starting with 
'!!' before the '!!LOG_FORMAT' line, but there will never be a regular 
log entry before the first '!!LOG_FORMAT'.

Jason

-----------------
[EMAIL PROTECTED]
-----------------
Dr. Seuss books . . . can be read and enjoyed on several levels. For
example, 'One Fish Two Fish, Red Fish Blue Fish' can be deconstructed
as a searing indictment of the narrow-minded binary counting system.
  -- Peter van der Linden, Expert C Programming, Deep C Secrets


------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------

Reply via email to