Can you post a couple of sample lines (or email me off list with a log file) and I
will try and build a LOGFORMAT command for you.
SC
*** REPLY SEPARATOR ***
On 24/03/2004 at 10:18 Savin, Jill wrote:
I've just downloaded and configued and tried out analog, and I get this
I've just downloaded and configued and tried out analog, and I get this
error message in report.html
Successful requests: 0
Corrupt logfile lines: 35,129
any idea where to start troubleshooting?
+
| TO UNSUBSCRIBE from
Savin, Jill [EMAIL PROTECTED] wrote:
I've just downloaded and configued and tried out analog, and I get
this error message in report.html
While it's creating report.html, Analog will display warnings and errors
that will alert you to potential problems. If you aren't seeing them on
the screen,
On Mon, 23 Jul 2001, StitchingtheSquare wrote:
From: StitchingtheSquare
e-mail : [EMAIL PROTECTED]
Hi,
I have two lines on my logfile which are coming up as corrupt. The two lines are:
63.17.74.161 - - [21/May/2001:17:42:53 -0600] GET /papillon.htm HTTP/1.1
On Tue, 15 Jun 1999, Mark Avnet wrote:
This is the log format line I am using in the config file:
APACHELOGFORMAT (%h %l %u %t "%{referer}i" - %v "%r" %s %b
[%{user-agent}i])
Here are the first several lines of my logfile:
205.231.86.183 - - [02/Jun/1999:15:19:50 -0400] "-" -
Jeff Drury - Support Supervisor wrote:
On Tue, 15 Jun 1999, Mark Avnet wrote:
Hi. I am new to Analog, and I now have it up and running, except for
one glitch that I cannot seem to get past. I am using Apache and,
therefore, the Apache log format. My problem is that when I run
Hi. I am new to Analog, and I now have it up and running, except for
one glitch that I cannot seem to get past. I am using Apache and,
therefore, the Apache log format. My problem is that when I run Analog,
it tells me that there was one successful request and 372 corrupt
logfile lines. I
On Tue, 15 Jun 1999, Mark Avnet wrote:
Hi. I am new to Analog, and I now have it up and running, except for
one glitch that I cannot seem to get past. I am using Apache and,
therefore, the Apache log format. My problem is that when I run Analog,
it tells me that there was one successful
On Tue, 15 Jun 1999, Mark Avnet wrote:
Hi. I am new to Analog, and I now have it up and running, except for
one glitch that I cannot seem to get past. I am using Apache and,
therefore, the Apache log format. My problem is that when I run Analog,
it tells me that there was one successful
Stephen Turner wrote:
On Tue, 15 Jun 1999, Mark Avnet wrote:
Hi. I am new to Analog, and I now have it up and running, except for
one glitch that I cannot seem to get past. I am using Apache and,
therefore, the Apache log format. My problem is that when I run Analog,
it tells me
Jeremy Wadsack wrote:
!Aengus Lawlor wrote:
!
! Is there a way to get Analog to dumpt the lines it doesn't recognize
! into a file, so that I can analyze them to figure out what the
!problem might be?
!
!Well, analog will output all the bad lines to STDERR.
Not on my machine, it doesn't. It
Is there a way to get Analog to dumpt the lines it doesn't recognize
into a file, so that I can analyze them to figure out what the problem
might be?
Aengus
This is the analog-help mailing list. To unsubscribe from this
Aengus Lawlor wrote:
Is there a way to get Analog to dumpt the lines it doesn't recognize
into a file, so that I can analyze them to figure out what the problem
might be?
Well, analog will output all the bad lines to STDERR. And, (as I learned
earlier today) this can be logged to a file on
13 matches
Mail list logo