We switched to rsyslog and since then seeing a huge increase in the log volume. Thanks for all the help!
Thanks Sachin -----Original Message----- From: Sachin Shetty [mailto:sshe...@egnyte.com] Sent: Saturday, October 15, 2011 11:35 AM To: 'Willy Tarreau' Cc: 'haproxy@formilux.org' Subject: RE: syslogd dropping requests from haproxy Thanks Willy - I will these and let you know. -----Original Message----- From: Willy Tarreau [mailto:w...@1wt.eu] Sent: Saturday, October 15, 2011 11:32 AM To: Sachin Shetty Cc: haproxy@formilux.org Subject: Re: syslogd dropping requests from haproxy On Sat, Oct 15, 2011 at 01:35:46AM +0530, Sachin Shetty wrote: > Found some more info, when haproxy configured to send logs to remote host > instead of local syslogd, it works fine. Definately something to do with the > local syslogd under heavy load. Check that your syslog doesn't log synchronously. For the basic sysklogd, it means you need to have a "-" in front of your file names. And even with this, sysklogd's limits are quickly reached (between 300 and 1000 logs/s depending on the machine). For high loads, I strongly recommend syslog-ng. It's the only one I found which managed to log more than 10000 logs/s without dropping any : http://www.balabit.com/network-security/syslog-ng Regards, Willy
