Re: [analog-help] corrupt logfile lines....
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 error message in report.html Successful requests: 0 Corrupt logfile lines: 35,129 any idea where to start troubleshooting? + | TO UNSUBSCRIBE from this list: |http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives + + | TO UNSUBSCRIBE from this list: |http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +
[analog-help] corrupt logfile lines....
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 this list: |http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +
Re: [analog-help] corrupt logfile lines....
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, then add the ERRFILE directive to your analog.cfg file, so that they will be captured to a file. Successful requests: 0 Corrupt logfile lines: 35,129 If they're all corrupt, then your Analog isn't recognizing the format of your logfile. You often don't need to specify a LOGFORMAT, but if Analog can't recognize the log files without one, then you'll have to specify a LOGFORMAT. If you have specified a LOGFORMAT, then it's not right. http://www.analog.cx/docs/logfmt.html any idea where to start troubleshooting? http://www.analog.cx/docs/debug.html Aengus + | TO UNSUBSCRIBE from this list: |http://lists.isite.net/listgate/analog-help/unsubscribe.html | | Digest version: http://lists.isite.net/listgate/analog-help-digest/ | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general | List archives: http://www.analog.cx/docs/mailing.html#listarchives +
Re: [analog-help] Corrupt logfile lines
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
http://www.google.com/custom?q=papillon+dogssite=searchhl=enlr=safe=offcof=L:http://www.refdesk.com/rd.gif;LH:94;LW:282;BGC:white;T:black;AH:center;start=10sa=N;
200 12972
216.136.3.126 - - [24/May/2001:02:15:56 -0600] GET /pekingese.htm HTTP/1.1
http://www.google.com/custom?q=Pekingesesite=searchhl=enlr=safe=offcof=L:http://gasco/images/cgname.gif;LH:42;LW:548;AH:center;start=150sa=N;
200 11246
I can see that the problem in my syntax is in the Referrer. I have tried using
%f %r ; %f %r %q ; %f %r %i ;%f %r=%q and %f %r=%j to no avail. Mention of
the {User-Agent} is made in the logfile format in generating a command line for the
Apache server but I can find no command line syntax that will work.
I wonder can anyone assist?
The problem is that the referrer has embedded quotes, so analog thinks that
the referrer ends there. There are programs on the Helper Applications page
to sort this out.
--
Stephen Turner http://www.statslab.cam.ac.uk/~sret1/
Statistical Laboratory, Wilberforce Road, Cambridge, CB3 0WB, England
This is Henman's 8th Wimbledon, and he's only lost 7 matches. BBC, 2/Jul/01
+
| 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/analog-help@lists.isite.net/
|http://lists.isite.net/listgate/analog-help/archives/
|http://www.tallylist.com/archives/index.cfm/mlist.7
+
Re: [analog-help] Corrupt logfile lines
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] "-" - redding.nfic.com
"GET / HTTP/1.0" 304 - [Mozilla/4.6 [en] (WinNT; U)]
205.231.86.183 - - [02/Jun/1999:15:19:50 -0400]
"http://redding.nfic.com/" - redding.nfic.com "GET /apache_pb.gif
HTTP/1.0" 304 - [Mozilla/4.6 [en] (WinNT; U)]
Sorry for taking a couple of days over this, but I've tracked it down.
The problem is that putting the browser in square brackets (instead of the
usual quote marks) is unsafe, because the browser string contains square
brackets itself. It looks to analog as if the browser is
Mozilla/4.6 [en
and then it finds some junk looking like
(WinNT; U)]
on the end of the line and rejects it as corrupt.
--
Stephen Turner[EMAIL PROTECTED]http://www.statslab.cam.ac.uk/~sret1/
Statistical Laboratory, 16 Mill Lane, Cambridge CB2 1SB, England
"Due to the conflict in Kosovo, we will not be showing the movie Wag the
Dog. Instead, we will show Mortal Kombat: Annihilation." Cable Wireless
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/analog-help@lists.isite.net/
Re: [analog-help] Corrupt logfile lines
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 Analog, it tells me that there was one successful request and 372 corrupt logfile lines. I looked through the logfile, and the format seems to be right, but I continue to get these results. Any ideas? I'm running Apache on RHL6.0 logging only access logs, I found that I didn't need to specify a logformat and in fact omitted it from analog.cfg. -Jeff Jeffery Drury Technical Support Supervisor E-Znet Incorporated http://www.eznet.net Email: [EMAIL PROTECTED] Water creates a neurosis in golfers. The very thought of this harmless fluid robs them of their power of rational thought, turns their legs to jelly, and produces a palsy of the upper limbs. -Peter Dobereiner 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/analog-help@lists.isite.net/ Thanks, but not specifying a log format did not help. It brought me from 1 successful request to 0, just as every other change I have made has done. Mark 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/analog-help@lists.isite.net/
[analog-help] Corrupt logfile lines
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 looked through the logfile, and the format seems to be right, but I continue to get these results. Any ideas? Mark 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/analog-help@lists.isite.net/
Re: [analog-help] Corrupt logfile lines
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 request and 372 corrupt logfile lines. I looked through the logfile, and the format seems to be right, but I continue to get these results. Any ideas? I'm running Apache on RHL6.0 logging only access logs, I found that I didn't need to specify a logformat and in fact omitted it from analog.cfg. -Jeff Jeffery Drury Technical Support Supervisor E-Znet Incorporated http://www.eznet.net Email: [EMAIL PROTECTED] Water creates a neurosis in golfers. The very thought of this harmless fluid robs them of their power of rational thought, turns their legs to jelly, and produces a palsy of the upper limbs. -Peter Dobereiner 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/analog-help@lists.isite.net/
Re: [analog-help] Corrupt logfile lines
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 request and 372 corrupt logfile lines. I looked through the logfile, and the format seems to be right, but I continue to get these results. Any ideas? Well, presumably the format isn't right in some way -- or maybe just the top line isn't, which analog uses to diagnose the format. There isn't a single Apache format. Look in docs/logfile.html for the definitions of the standard formats which analog recognises, and some common problems with them. If you logfile is not in one of those formats given there, you will need to write a LOGFORMAT command for it. If you still can't figure it out, post the top 5 to 10 lines of your logfile here, and we'll have a look. -- Stephen Turner[EMAIL PROTECTED]http://www.statslab.cam.ac.uk/~sret1/ Statistical Laboratory, 16 Mill Lane, Cambridge CB2 1SB, England "Due to the conflict in Kosovo, we will not be showing the movie Wag the Dog. Instead, we will show Mortal Kombat: Annihilation." Cable Wireless 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/analog-help@lists.isite.net/
Re: [analog-help] Corrupt logfile lines
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 that there was one successful request and 372 corrupt
logfile lines. I looked through the logfile, and the format seems to be
right, but I continue to get these results. Any ideas?
Well, presumably the format isn't right in some way -- or maybe just
the top line isn't, which analog uses to diagnose the format.
There isn't a single Apache format. Look in docs/logfile.html for the
definitions of the standard formats which analog recognises, and some common
problems with them. If you logfile is not in one of those formats given
there, you will need to write a LOGFORMAT command for it.
If you still can't figure it out, post the top 5 to 10 lines of your logfile
here, and we'll have a look.
--
Stephen Turner[EMAIL PROTECTED]http://www.statslab.cam.ac.uk/~sret1/
Statistical Laboratory, 16 Mill Lane, Cambridge CB2 1SB, England
"Due to the conflict in Kosovo, we will not be showing the movie Wag the
Dog. Instead, we will show Mortal Kombat: Annihilation." Cable Wireless
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/analog-help@lists.isite.net/
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:
common
common
205.231.86.183 - - [02/Jun/1999:15:19:50 -0400] "-" - redding.nfic.com
"GET / HTTP/1.0" 304 - [Mozilla/4.6 [en] (WinNT; U)]
205.231.86.183 - - [02/Jun/1999:15:19:50 -0400]
"http://redding.nfic.com/" - redding.nfic.com "GET /apache_pb.gif
HTTP/1.0" 304 - [Mozilla/4.6 [en] (WinNT; U)]
205.231.86.85 - - [03/Jun/1999:13:08:33 -0400] "-" - redding.nfic.com
"GET /bazaar/bza2.0/c/miscConf.cgi? HTTP/1.0" 200 12 [-]
205.231.86.85 - - [03/Jun/1999:13:09:15 -0400] "-" - redding.nfic.com
"GET /bazaar/bza2.0/html/index.html HTTP/1.0" 200 425 [Mozilla/4.6 [en]
(X11; U; SunOS 5.6 sun4u)]
205.231.86.85 - - [03/Jun/1999:13:09:16 -0400]
"http://redding.nfic.com/bazaar/bza2.0/html/index.html" -
redding.nfic.com "GET /bazaar/bza2.0/images/Leather-lite2.gif HTTP/1.0"
200 14524 [Mozilla/4.6 [en] (X11; U; SunOS 5.6 sun4u)]
205.231.86.85 - - [03/Jun/1999:15:48:50 -0400] "-" - redding.nfic.com
"GET /bazaar/bza2.0/html/index.html HTTP/1.0" 200 425 [Mozilla/4.6 [en]
(X11; U; SunOS 5.6 sun4u)]
This is what is resulting in 1 successful request and 3XX corrupt
lines. Any
changes that I have tried to make result in 0 successful requests. Is
anything wrong with the way I have done this?
Mark S. Avnet
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/analog-help@lists.isite.net/
Re[2]: [analog-help] Corrupt Logfile Lines
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 just gives a "Large number of corrupt entries" error. !And, (as I learned !earlier today) this can be logged to a file on Windows NT, Borne or Korn !shell by using ! analog 2 analog.log !Of course, this will include all of the rest of analog's warnings and !errors, and each line will be prepended by a C:, but they'll be there. You !could also write a scrip to process this log if you needed just those !lines (for instance, only read lines beginning with C:, or something). This is where I sheepishly admit that I never tried DEBUG ON, which does indeed display the corrupt lines. As it happens, the problem appears to have had something to do with logfile lines starting with CHR$(0) and all debug mode gave me for my trouble was a couple of thousand lines with just C: at the start, and nothing else. Opening the log file in a text editor, and just saving it converted the null chars to spaces, and seems to have fixed the problem was. !Jeremy Wadsack Aengus 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.
[analog-help] Corrupt Logfile Lines
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 mailing list, send mail to [EMAIL PROTECTED] with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
Re: [analog-help] Corrupt Logfile Lines
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 Windows NT, Borne or Korn shell by using analog 2 analog.log Of course, this will include all of the rest of analog's warnings and errors, and each line will be prepended by a C:, but they'll be there. You could also write a scrip to process this log if you needed just those lines (for instance, only read lines beginning with C:, or something). HTH -- Jeremy Wadsack OutQuest Magazine a Wadsack-Allen publication 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.
