From owner-freebsd-questions@FreeBSD.ORG Sun Mar 29 17:33:51 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDBAA106566B for ; Sun, 29 Mar 2009 17:33:51 +0000 (UTC) (envelope-from chowse@charter.net) Received: from mta11.charter.net (mta11.charter.net [216.33.127.80]) by mx1.freebsd.org (Postfix) with ESMTP id 747BB8FC0A for ; Sun, 29 Mar 2009 17:33:50 +0000 (UTC) (envelope-from chowse@charter.net) Received: from imp10 ([10.20.200.10]) by mta11.charter.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090329173341.FRJO21265.mta11.charter.net@imp10> for ; Sun, 29 Mar 2009 13:33:41 -0400 Received: from [192.168.254.3] ([24.176.107.216]) by imp10 with charter.net id Z5Zg1b00D4g9tMU055Zh32; Sun, 29 Mar 2009 13:33:41 -0400 Message-Id: From: Charles Howse To: FreeBSD Questions In-Reply-To: <200903290451.n2T4pqhh005842@banyan.cs.ait.ac.th> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v930.3) Date: Sun, 29 Mar 2009 12:33:40 -0500 References: <5BCD53E0-5B9F-4349-8401-FBF0ACF369C2@charter.net> <200903290451.n2T4pqhh005842@banyan.cs.ait.ac.th> X-Mailer: Apple Mail (2.930.3) Subject: Re: analyzing httpd-error.log X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2009 17:33:52 -0000 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. > > 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? Also, in httpd.conf what level of detail should I set in the error.log to get the most information. It's currently set to 'warn', which I understand to be 'warn' and everything more critical than that. I don't care about the size of the log, or the amount of garbage per line.