Having used Analog for the past 5 years wit a BT Connect account(s) with excellent results, a problem has occurred that results in a failure to analyze the latest log files I am receiving from the BT server (Unix / Solaris) outputs.

My question is, am I and is Analog correct in the belief that the log files are incorrect and corrupt or is there a way of analyzing these files.

I have attempted to strip out the added character in Excel but this is a time wasting exercise as they bulk processing usually results in failure.

Information below is sampled from the report and some log file extracts.
........................................................................ ................................................................... analog: Warning L: Large number of corrupt lines in logfile 20051109.log: turn
  debugging on or try different LOGFORMAT
  (For help on all errors and warnings, see docs/errors.html)
    Current logfile format:
      %S %j %j [%d/%M/%Y:%h:%n:%j] "%j%w%r%wHTTP%j" %c %b "%f" "%B"\n
      %S %j %j [%d/%M/%Y:%h:%n:%j] "%j%w%r" %c %b "%f" "%B"\n
      %S %j %j [%d/%M/%Y:%h:%n:%j] "%r" %c %b "%f" "%B"\n
analog: Warning R: Turning off empty Failure Report
analog: Warning R: Turning off empty Failed Referrer Report
analog: Warning R: Turning off empty Search Word Report
analog: Warning R: In Domain Report, turning off pie chart of only one wedge
analog: Warning R: In Host Report, turning off pie chart with no wedges
analog: Warning R: In Directory Report, turning off pie chart of only one
  wedge
analog: Warning R: In Request Report, turning off pie chart with no wedges analog: Warning R: In Referrer Report, turning off pie chart with no wedges analog: Warning R: In Referring Site Report, turning off pie chart of only one
  wedge
analog: Warning R: In Operating System Report, turning off pie chart of only
  one wedge
Complete!
........................................................................ .................................................................... The following Debug+C reports for all corrupt lines and the * is under the final ( " - ) hyphen at the end of the line

C: 62.253.96.44 - - [09/Nov/2005:23:38:41 +0000] "GET /hooklinks/pike/articles/artindex.html HTTP/1.1" 200 4819 "FROM http://www.hooklinks.co.uk/pike/navigation2/homenav2.html"; "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; Hotbar 4.6.1)" - C: * Can this be accommodated in a Format created for the purpose? If so can you provide an example?
.................................................
BT advise on their site they use the Combined Log Format, is this a server config error on their server?

Previously received log file extract that was successfully analysed ok.No '-' at the end of the line. 62.252.192.10 - - [01/Jan/2005:13:39:20 +0000] "GET /hooklinks/pike/gallery/largeimages/paulmusialek1.jpg HTTP/1.1" 200 31046 "FROM http://www.hooklinks.co.uk/pike/gallery/pics/paulmus1.html"; "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; FunWebProducts; AskBar 3.00)"

If anybody can offer a solution I would be truly grateful.

I continue in tasking BT for an acceptable answer as I am convinced the problem is with their server report formatting and currently await the service desks answers.

Regards

David

+------------------------------------------------------------------------
|  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
+------------------------------------------------------------------------

Reply via email to