sending appache error to a syslog server

sezam2 · 02-17-2009, 06:39 AM

Hello

i finaly succeded in setting a syslog server
(on a suse 10 sp2 environement working on xen virtual machine)

my server create a folder having the host name or the url in wich he saves the log files he recive from

Quote:

destination std {
file ("/var/log/HOSTS1/$YEAR-$MONTH/$HOST/$FACILITY-$YEAR-$MONTH-$DAY"
owner(root) group(root) perm(0600) dir_perm(0700) create_dirs(yes)
);
};
log {
source(src);
destination(std);
};

know i want to send apache log files specially error to my syslog server

i need a hand in this issue

thanks

unSpawn · 02-17-2009, 05:31 PM

Here's a simple explanation: Sending Apache httpd Logs to Syslog and a more elaborate one. BTW please don't crosspost questions on LQ.

sezam2 · 02-18-2009, 09:51 AM

Quote:

Originally Posted by unSpawn

Here's a simple explanation: Sending Apache httpd Logs to Syslog and a more elaborate one. BTW please don't crosspost questions on LQ.

thanks i 'am going to consider you remarqu but i wanted to give the maximum of detail...

i use sues 10 sp2
lets talk busnes ( hihi)
i tried to follow the how to you gave me but

when i tri the classic way to view error

Quote:

if i use in /etc/apache2/mod_log_config.conf
CustomLog /var/log/apache2/agent_log "%{User-agent}i"
#ErrorLog "|/home/user/cronolog-1.6.2/src/cronolog /var/log/apache2/sami/error

it work tail -f /var/log/apache2/sami/error
alow me to see apache error log
but
if i use in /etc/apache2/mod_log_config.conf
ErrorLog syslog:local1
and
in /etc/syslog.conf
local0.* -/var/log/localmessages
local1.crit /var/log/apache.crit

nothing i can see nothing

unSpawn · 02-18-2009, 03:39 PM

Quote:

Originally Posted by sezam2

if i use in /etc/apache2/mod_log_config.conf

That included configuration file might be just for defining logging formats, logfile locations and custom logging. ErrorLog can be in the main configuration file for all instances or in the main configuration file plus Vhost containers. It's unclear to me if having an ErrorLog directive in /etc/apache2/mod_log_config.conf should work.