RE: Logging & rsyslogd

From: John Lauro <john.lauro#covenanteyes.com>
Date: Mon, 16 Feb 2009 17:51:45 -0500


Put a - in front of the path in syslogd.conf.

Ie:

local0.*
-/mnt/log/haproxy_0.log
local1.*
-/mnt/log/haproxy_1.log
local2.*
-/mnt/log/haproxy_2.log
local3.*
-/mnt/log/haproxy_3.log
local4.*
-/mnt/log/haproxy_4.log
local5.*
-/mnt/log/haproxy_5.log  

That will help a lot with your load. Without the -, syslog is asked to sync the disk after every entry.    

Also, levels are incremental. Debug includes info, info includes crit, notice includes warning, etc..  

So, just list one level (ie: info) in your Haproxy config, and if you want to break it out by level then do it in your syslogd.conf.        

From: Mayur B [mailto:mayurb#gmail.com] Sent: Monday, February 16, 2009 5:14 PM
To: haproxy#formilux.org
Subject: Logging & rsyslogd  

Hello,

After enabling logging in rsyslogd & haproxy.config using the following lines, are CPU utilization has gone thru the roof. It used to be at 5-10% utilization, and it is now above 95% most of the time.

rsyslogd.conf:
# Save HA-Proxy logs
local0.*
/mnt/log/haproxy_0.log

local1.*
/mnt/log/haproxy_1.log

local2.*
/mnt/log/haproxy_2.log

local3.*
/mnt/log/haproxy_3.log

local4.*
/mnt/log/haproxy_4.log

local5.*
/mnt/log/haproxy_5.log
Received on 2009/02/16 23:51

This archive was generated by hypermail 2.2.0 : 2009/02/17 01:00 CET