On 12/14/1999, Stephen Turner wrote:
>On Mon, 13 Dec 1999, Cate Burton wrote:
>
> > What is the difference between this, which does not work
> > [...]
> >
> > And this older log, which does
> > [...]
>
>Hmmm... nothing that I can see immediately. Maybe the first logfile has
>lines in lots of different formats?
>
>If you turn debugging on, it will tell you which lines were corrupt, and (if
>you are using version 4) where they are corrupt.
While I didn't have this exact problem, the debugging is a good way to
see where there are errors in the log files. Two lines in your config
file will set things up (almost) nicely for analysis:
DEBUG C
ERRFILE errors.nov
The DEBUG C line tells Analog to report log entry errors and the ERRFILE
tells Analog what file to write the errors to. (Note from the Debugging
section of the 4.0 docs: "The ERRFILE command will erase any previous contents
of that file. (So don't use the same ERRFILE command twice, or you may lose
messages!)").
Once the run has completed, you can read the ERRFILE to see what Analog
didn't like about the log entries. If your editor is set right (mono-spaced
font instead of proportional), you should see an "*" where Analog found
a problem.
The two biggest problems I found in my log files were line breaks and
unmatched or too many quotes. I haven't yet taken the time to track down
why there are line breaks, but when an entry wraps to a new line (with a
line feed character inserted) instead of remaining one continuous line,
Analog can't parse it correctly. It is rejected as incomplete. The
unmatched quotes are found in search queries, where the search engine
delimits some search terms with double quotation marks. If the LOGFORMAT
command is counting items based on parts of an entry being withing
quotation marks, the "extra" quotes will throw off the count and the
line will be rejected as incomplete or invalid.
It could be like Stephan says, that there are lines within the logfile
that are in different formats. Use DEBUG to ferret them out; it is a
whole lot easier than trying to peruse the entire log file.
Of course, if DEBUG gives you a mirror of the logfile . . .
Good luck.
Bruce
Bruce Harper, Virginia Tech Webmaster
Bruce B. Harper (540)231-4360
Web Application Research & Development [EMAIL PROTECTED]
840 Pointe West Commons, Suite 6
Blacksburg, Virginia 24060
Virginia Tech home page http://www.vt.edu/
------------------------------------------------------------------------
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]/
------------------------------------------------------------------------
