aganguly01 at gmail
Sep 9, 2009, 9:21 AM
Post #3 of 3
(2111 views)
Permalink
|
Hi Aengus,
Very much appreciated for your support inputs.I have resolved the issue.
Regards
-A
On Wed, Sep 9, 2009 at 6:55 PM, Aengus <analog07 [at] eircom> wrote:
> On 9/9/2009 7:54 AM, Arnab Ganguly wrote:
>
>> Hi All,
>> In the analog report, we do get one field as "Corrupt logfile lines". What
>> exactly is this ? If you browse through the access log we don't see any
>> such through human eye.Is there anything I am missing out.
>>
>
> "Corrupt logfile lines" are lines that don't match any of the LOGFORMAT
> entries being used.
>
> You can see which lines are considered corrupt by running Analog in Debug
> mode. Add DEBUG C to your analog.cfg, or add +VC to the command line.
>
> http://analog.cx/docs/debug.html#debugs
>
> You might find it useful to use the ERRFILE command to capture the output
> to a file.
>
> http://analog.cx/docs/debug.html#ERRFILE
>
> 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
> +------------------------------------------------------------------------
>
|
