Andrew -
You'll need to change your log file format. If you have one in your config file you can add the parameter for the host name (or make it junk with %j). See http://analog.cx/docs/logfmt.html for details on the command. If you don't currently have a custom log format, you can turn on debugging (http://analog.cx/docs/debug.html) to have Analog tell you what the current log format is (along with lots of other information). -- Jeremy Wadsack Seven Simple Machines > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:analog-help- > [EMAIL PROTECTED] On Behalf Of Andrew Myers > Sent: Thursday, June 14, 2007 2:26 PM > To: [email protected] > Subject: [analog-help] Analog 6.0 suddenly choking > > Apologies: This is a resend because I mistakenly sent the first in HTML > format and (maybe) nobody wanted to bother wading through the code. I > hope someone has an idea or advice: > > Original posting: > I have been successful analyzing logs from our server at Network > Solutions for a year or so but as of June 2 Analog cannnot parse my > logfiles. It reports a large number of corrupt lines and returns no > results for any of the logfiles after that date. Network Solutions told > me they have added an additional field. Whereas in the past they > provided only IPs, they are now including website addresses (i.e., they > are doing the DNS translations that I formerly had to look up). Here > are two logfile lines, the first from an older logfile that causes no > trouble, the second from a new one that fails. BTW, I looked at the > error file after turning on debugging and if I am reading it correctly > the problem in each line may possibly be the second hyphen following the > IP address. At least that's where an asterisk appears on a blank line > below a corrupt line in the error report. As for my analog.cfg file, I > tried omitting/including various LOGFORMAT commands with no change in > the results. Anyway, first a line from an older (working) logfile: > > 212.165.130.14 - - [02/Jun/2007:12:04:23 -0400] "GET /js/today.js > HTTP/1.0" 200 1010 "http://www.centralcm.com/links.html"; "Mozilla/4.0 > (compatible; MSIE 6.0; Windows NT 5.1; SV1)" > > And now a line from a logfile that fails utterly: > > www.centralcm.com 24.228.44.169 - - [11/Jun/2007:19:44:12 -0400] "GET > /catalog/images/sata_90.jpg HTTP/1.1" 200 8044 > "http://www.centralcm.com/catalog/"; "Mozilla/4.0 (compatible; MSIE 6.0; > Windows NT 5.1; SV1; .NET CLR 2.0.50727)" > > As you can see, they are quite similar except for the addition of > "www.centralcm.com" in the second example. I am baffled. I can't > figure out why the second line fails and how I might address this > problem. Thanks for any advice. Feel free to ask me anything about my > .cfg file, etc. Thanks in advance. > > --Andrew Myers-- > CCM Webmaster > > -- > <!-- Andrew B. Myers [EMAIL PROTECTED] --> > <!-- Website http://www.centralcm.com/ --> > > +------------------------------------------------------------------------ > | TO UNSUBSCRIBE from this list: > | http://lists.meer.net/mailman/listinfo/analog-help > | > | Analog Documentation: http://analog.cx/docs/Readme.html > | List archives: http://www.analog.cx/docs/mailing.html#listarchives > | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general > +------------------------------------------------------------------------ +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Analog Documentation: http://analog.cx/docs/Readme.html | List archives: http://www.analog.cx/docs/mailing.html#listarchives | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general +------------------------------------------------------------------------
