Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Nov 2005 22:03:24 -0500
From:      "Matt Emmerton" <matt@gsicomp.on.ca>
To:        "Dave" <dmehler26@woh.rr.com>, "Robert Slade" <bsd@bathnetworks.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: webalizer monitoring apache logs on freebsd6
Message-ID:  <005201c5ecb5$cf6e5f80$1200a8c0@gsicomp.on.ca>
References:  <003b01c5ec44$886949e0$0900a8c0@satellite><1132334068.1579.14.camel@lmail.bathnetworks.co.uk> <001901c5eca7$5a0d93e0$0900a8c0@satellite>

next in thread | previous in thread | raw e-mail | index | archive | help
[ top-posting corrected ]


> > On Fri, 2005-11-18 at 13:32, Dave wrote:
> >> Hello,
> >>     I'm trying to use webalizer to analyze apache2 web logs and report
on
> >> traffic on my freebsd6 box. Both apache2 and webalizer are set to scan
> >> the
> >> combined log type. Webalizer runs via cron and this error is what i get
> >> that's it. Any help appreciated.
> >> Thanks.
> >> Dave.
> >>
> >> Error: Skipping oversized log record
> >> Error: Skipping oversized log record
> >> Error: Skipping oversized log record
> >> Error: Skipping oversized log record
> >> Error: Skipping oversized log record
> >> Error: Skipping oversized log record
> >> Error: Skipping oversized log record
> >> Error: Skipping oversized log record
> >> Error: Skipping oversized log record
> >> Error: Skipping oversized log record
> >
> > Dave,
> >
> > This is usually the result of something trying to get into your web
> > server by sending a load of control codes. I believe it is an attempt to
> > exploit a Windows web server weakness. The problem is that the control
> > codes fill up the apache log file and webilizer cannot handle the
> > record.
> >
> > I usually ignore the error.
> >
> > Rob
>
>     Thanks. The problem is this is a nightly thing, webalizer always sends
> me this output.
> Thanks.
> Dave.

Even better -- run webalizer in "really quiet" mode (-Q).  You'll still get
warned about fatal errors (ie, can't find logfile, etc) but all other
status/error/warning messages are supressed.  A real benefit if you're
processing multiple logs nightly and don't want to get swamped with N emails
in the morning from cron.

--
Matt Emmerton




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005201c5ecb5$cf6e5f80$1200a8c0>