Date: Sun, 29 Mar 2009 14:54:35 -0400 From: Glen Barber <glen.j.barber@gmail.com> To: Charles Howse <chowse@charter.net> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: analyzing httpd-error.log Message-ID: <4ad871310903291154j74c35b0p545157b848adf8b9@mail.gmail.com> In-Reply-To: <B832EFF4-F951-4830-9C96-944287DE8E8D@charter.net> References: <5BCD53E0-5B9F-4349-8401-FBF0ACF369C2@charter.net> <200903290451.n2T4pqhh005842@banyan.cs.ait.ac.th> <B832EFF4-F951-4830-9C96-944287DE8E8D@charter.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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. =A0My research hasn't turned up a >>> good solution for webalizer and -error.log. >> What are the errors? >> The format of error log is pretty much different from the format of >> transfer log. No wonder webalizer is not liking it. You may have to >> write your own format for th error log. > > Well, can anyone suggest a port that will parse the error.log and output = it > to a web page that's easy to read? > Webalizer is probably your best bet. > Also, in httpd.conf what level of detail should I set in the error.log to > get the most information. =A0It's currently set to 'warn', which I unders= tand > to be 'warn' and everything more critical than that. =A0I don't care abou= t the > size of the log, or the amount of garbage per line. The 'debug' log level will provide the most verbosity. --=20 Glen Barber
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4ad871310903291154j74c35b0p545157b848adf8b9>