Hi Aengus
Thanks for you support but the problem still exists, one of my
questions was is the log file line corrupt or was the a Format to
handle it if they were not, I have looked at the linked info and
substituted formats and added characters to the array as below.
The following amendment to the results is one of many options tried by
adding %j, %w, %W, singly and twice with and without a DEFAULTLOGFORMAT
as here in in this extract from the CFG file:
All that I seem to achive is moving the Debug C asterisk * past the
hyphen!
#
HOSTURL "none"
# Host name will be a link to here
#
DEFAULTLOGFORMAT
# this is the log format used for drag and dropped logs
#
LOGFORMAT (%S %j %u [%d/%M/%Y:%h:%n:%j] "%j%w%r%wHTTP%j" %c %b "%f"
"%B" %j %j)
LOGFORMAT (%S %j %u [%d/%M/%Y:%h:%n:%j] "%j%w%r" %c %b "%f" "%B" %j %j)
LOGFORMAT (%S %j %u [%d/%M/%Y:%h:%n:%j] "%r" %c %b "%f" "%B" %j %j)
#
# Log file format DEFAULT, AUTO, COMMON, MS-COMMON, COMBINED,
MICROSOFT-NA,
# MICROSOFT-INT, WEBSITE-NA, WEBSITE-INT, WEBSTAR, EXTENDED,
MS-EXTENDED,
# WEBSTAR-EXTENDED, NETSCAPE, REFERRER, or BROWSER
#
LOGFILE "*.log"
C: 62.253.96.44 - - [09/Nov/2005:23:38:46 +0000] "GET
/hooklinks/pike/navigation2/images/homenav2_01-homenav2_12_ove.jpg
HTTP/1.1" 200 3510 "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:
*
C: 81.7.38.31 - - [09/Nov/2005:23:59:59 +0000] "GET
/hooklinks/pike/navigation2/pikeframe.html?=rbaits1.html HTTP/1.1" 304
106 "FROM -" "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)"
-
C:
*
analog: Warning L: Large number of corrupt lines in logfile
20051109.log: turn
debugging on or try different LOGFORMAT
Current logfile format:
%S %j %j [%d/%M/%Y:%h:%n:%j] "%j%w%r%wHTTP%j" %c %b "%f" "%B" %j
%j\n
%S %j %j [%d/%M/%Y:%h:%n:%j] "%j%w%r" %c %b "%f" "%B" %j %j\n
%S %j %j [%d/%M/%Y:%h:%n:%j] "%r" %c %b "%f" "%B" %j %j\n
analog: Warning R: Turning off empty time reports
analog: Warning R: Turning off empty Request Report
analog: Warning R: Turning off empty Failure Report
analog: Warning R: Turning off empty File Type Report
analog: Warning R: Turning off empty Directory Report
analog: Warning R: Turning off empty Host Report
analog: Warning R: Turning off empty Domain Report
analog: Warning R: Turning off empty Referrer Report
analog: Warning R: Turning off empty Referring Site Report
analog: Warning R: Turning off empty Failed Referrer Report
analog: Warning R: Turning off empty Browser Report
analog: Warning R: Turning off empty Organisation Report
analog: Warning R: Turning off empty Search Word Report
analog: Warning R: Turning off empty Browser Summary
analog: Warning R: Turning off empty Operating System Report
analog: Warning R: Turning off empty File Size Report
analog: Warning R: Turning off empty Status Code Report
Complete!
If all of this suggests an answer, the FORMAT is wrong or the log file
corrupt perhaps you can offer some other advice than reading the help
files , as without a sound grounding in principles and method I am just
as likely to make an error too.
2 lines of "corrupt log files" above what do you get when you run those
2 lines through Analog?
Regards
David
On 3 Jan 2006, at 21:39, Aengus wrote:
On Tuesday, January 03, 2006 4:04 PM [EDT],
David Batten <[EMAIL PROTECTED]> wrote:
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.
A "corrupt" logfile is one that doesn't match the LOGFORMAT that
Analog is
currently using - that doesn't mean that Analog can't read it, or
interpret
it, it just means that the logfile doesn't match whatever format you
told
Analog to use. It might not match because the lofile really is
corrupt, and
total garbage, but it might also be because Analog finds data that it
doesn't expect to find in a specific field in the logfile.
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
So, what different LOGFORMATs did you try? Better yet, what LOGFORMAT
were
you using to start with?
......................................................................
..
....................................................................
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)" -
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 you aren't specifying a LOGFORMAT already, then you can find the
Combined
format in the Analog documentation, and modify it to take account of
the new
field. (I'm sort of assuming that you already have a LOGFORMAT to fix
that
FROM entry in the Referrer field - Analog won't complain about it, but
the
links in your Referrer report won't work properly if you don't already
have
a custom LOGFORMAT).
http://analog.cx/docs/logfmt.html
Aengus
+----------------------------------------------------------------------
--
| 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
+------------------------------------------------------------------------
