Date: Mon, 30 Mar 2009 22:11:30 +0200 From: Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> To: freebsd-questions@freebsd.org Cc: Charles Howse <chowse@charter.net> Subject: Re: analyzing httpd-error.log Message-ID: <200903302211.30208.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> In-Reply-To: <8BDE67B0-B6B1-4AAC-A0FD-0E519E74CBAF@charter.net> References: <5BCD53E0-5B9F-4349-8401-FBF0ACF369C2@charter.net> <4ad871310903291154j74c35b0p545157b848adf8b9@mail.gmail.com> <8BDE67B0-B6B1-4AAC-A0FD-0E519E74CBAF@charter.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 29 March 2009 22:25:55 Charles Howse wrote: > On Mar 29, 2009, at 1:54 PM, Glen Barber wrote: > > On Sun, Mar 29, 2009 at 1:33 PM, Charles Howse <chowse@charter.net> > > > > wrote: > >> On Mar 28, 2009, at 11:51 PM, Olivier Nicole wrote: > >>> Hi, > >>> > >>>> Webalizer is doing what it's supposed to with httpd-access.log, but > >>>> when I give it the error log to process is coughs, spits and spills > >>>> out errors with no data processed. My research hasn't turned up a > >>>> good solution for webalizer and -error.log. > > > > What are the errors? > > Intrusion attempts, (a few) bad links in my website, also I use the > error.log to troubleshoot cgi scripts. Nothing beats tail -f for debugging. 404's can be gathered from access log, by webalizer (or awstats or ...) and are summarized when enabled. If I remember correctly, there's also a referer top list, that specifies which pages link to invalid pages, but it may have been awstats that does this. Can't think of anything specific for apache error log, I roll my own grok rules if I'm really interested in a specific vulnerability. See sysutils/grok. -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903302211.30208.mel.flynn%2Bfbsd.questions>