Anand Dalvi wrote:

>     i am very new when it comes to this utility...so my prior apologies. i
> have been trying to generate Analog monthly reports.there seems to be a
> problem with the LOGFORMAT in my config file. i have tried turning DEBUG on
> as well as SETTINGS on, but cannot fathom what i need to put into LOGFORMAT
> entry in the config file. i am producing the output message that i get when
> i execute the /usr/local/analogmonth/analogmonth.pl script below. The
> command line within the script takes care of reading the correct config file
> instead of the default config file with the suggested -G+g combination
> flags. i am sorry again for having attached more than 10 lines of this
> message, but pls. try and help....

1] The command line is "-G +g", but I assume you got this right in your script
since Analog didn't complain about "too many paramters for -G command" or
something.

2] DEBUG C will tell you exactly what lines in the logfile are corrupt and show
an asterisk below the first character that doesn't match your format. However,
your output says "S: Corrupt lines: 0" for the logfile, so it's likely that it's
not a logformat problem but a logfile problem. Analog didn't reports any errors
when opening or closing the logfile so it must exists. The next question is to
see whether there really is any data in
/logs/files/2000-08/access_log.mama.00-08-01.www1.mamamedia.com.gz and see if
the gzip command is working right. Try "gzip -cd
/logs/files/2000-08/access_log.mama.00-08-01.www1.mamamedia.com.gz" from a
command-line and see if you get any output.

HTH,


Jeremy Wadsack
Wadsack-Allen Digital Group


------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------

Reply via email to