I am not sure how this dropped off the list, but restoring it for the
archives.
Steve,
I am not sure what a "zero length string" means. Is this a file with a
single null character in it? In any event this does sound like a bug.
Can you produce a file that unequivovably reproduces this bug? That
might help the author pin it down.
--
Jeremy Wadsack
Seven Simple Machines
Steve wrote:
Hi Jeremy,
Did all the usual things.
A complication is that all the suspect logs are in many zip files, so
manipulating them is non-trivial. Other analysis programs had
no dramas with them over the years, so I suspected Analog.
It turns out that it is a special type of file that is the problem. A pseudo
empty file. That is, a file with a single zero length
string in it. Analog doesn't like that at all for some reason. Dead empty (zero
bytes) files are not a problem.
Why do I have such files? Well I have all the archival error logs in the same
zip files. I haven't been able to work out if Analog
can be told to include only *.access_log files within zip files (tried "LOGFILE
path\*.zip:*.access_log" with no joy), so it reads
all the error logs as well. That doesn't matter because it cant recognise the
data as access data, but when you have a few of them
that (for some reason) have a single zero length string in them, then voila.
My only solution is to pick through all the zips and delete the suspect error
logs. Have made some progress .....
Regards,
Steve.
-----Original Message-----
From: Jeremy Wadsack [mailto:[EMAIL PROTECTED]
Sent: Friday, 3 June 2005 0229
To: [EMAIL PROTECTED]; Support for analog web log analyzer
Subject: Re: [analog-help] XP implementation crashes reading UNIX style log
files
Steve wrote:
Analog 6.0 (binary) running on XP with gobs of resources.
When I ask Analog to process a UNIX style log file it crashes. By "UNIX style"
I mean a log file with LF only EOLs. DOS/Windows
style log files (with CRLF EOLs) are just fine. By "crashes" I mean stops
execution and pops up one of those Windows must close
this
application" type message boxes. 100% repeatable and consistent bug.
I have lots of archival "UNIX style" log files from when my Apache was running
on Unix. I don't want to have to convert all of them
if I can avoid it.
My guess is that the Windows implementation of Analog doesn't see the LF only
EOL as an EOL and tries to read a VERY long line into
a buffer somewhere until it overwrites something and crashes. Just a guess.
Any simple solutions, or is it the dreaded log file conversion effort?
You might try downloading/installing Analog again? I just tested this
with the log file that ships with Analog (using dos2unix to convert it)
and Analog read it without any problems. If a new copy of Analog still
causes this, can you reproduce the behavior on the sample logfile.log or
is it maybe something else in the logfiles?
--
Jeremy Wadsack
Seven Simple Machines
+------------------------------------------------------------------------
| 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
+------------------------------------------------------------------------
