Date: Tue, 31 Mar 2009 21:01:18 +0200 (CEST) From: Oliver Fromme <olli@lurza.secnetix.de> To: freebsd-questions@FreeBSD.ORG, chowse@charter.net Subject: Re: analyzing httpd-error.log Message-ID: <200903311901.n2VJ1IoO015482@lurza.secnetix.de> In-Reply-To: <5BCD53E0-5B9F-4349-8401-FBF0ACF369C2@charter.net>
next in thread | previous in thread | raw e-mail | index | archive | help
The problem with Apache's error.log is that there is no standard format. Error messages generated by Apache itself are somewhat standardized, but messages from third-party modules are not. All kind of things will end up in the error.log, including stuff written to stdout by CGI programs, such as perl error messages, exception traces from Python programs (usually multiple lines each), and so on. There is no simple way to reliably parse and analyze all of that completely automatically. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one?" -- Tom Cargil, C++ Journal
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903311901.n2VJ1IoO015482>