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
Charles Howse skrev:
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 solut
On Mar 30, 2009, at 4:09 PM, Mel Flynn wrote:
On Monday 30 March 2009 22:55:35 Charles Howse wrote:
grep "$date" httpd-error.log | grep -v 192.168.254.254 | grep -v
192.168.254.3 > /root/err.log
Using pcregrep, installed by devel/pcre, typically available on apache
systems:
pcregrep "$date.
On Monday 30 March 2009 22:55:35 Charles Howse wrote:
> grep "$date" httpd-error.log | grep -v 192.168.254.254 | grep -v
> 192.168.254.3 > /root/err.log
Using pcregrep, installed by devel/pcre, typically available on apache
systems:
pcregrep "$date.* \[client (?!192\.168\.254)" /var/log/httpd-er
On Mar 30, 2009, at 3:11 PM, Mel Flynn wrote:
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
wrote:
On Mar 28, 2009, at 11:51 PM, Olivier Nicole wrote:
Hi,
Webalizer is doing what it's s
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
> >
> > wrote:
> >> On Mar 28, 2009, at 11:51 PM, Olivier Nicole wrote:
> >>> Hi,
> >>>
> Webalizer is doing what it's supposed to with ht
On Mar 29, 2009, at 1:54 PM, Glen Barber wrote:
On Sun, Mar 29, 2009 at 1:33 PM, Charles Howse
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
On Sun, Mar 29, 2009 at 1:33 PM, Charles Howse 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 proc
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 -e
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 prett
Hi,
I'm running 6.4-STABLE, Apache22, logwatch and Webalizer.
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 webalize
11 matches
Mail list logo
