By the way, in case I came across too harsh.

If you do upgrade to 8.2, and have the same problem, we will be very quick to dig in and track it down.

you should be able to upgrade to 8.2 without making any changes to your config file, just uninstall the current packages and install the new ones. The only place you may need to make changes is in your startup scripts (and even there, it's fairly unlikely)

David Lang


 On Wed, 30 Apr 2014, David Lang wrote:

Well, the rsyslog community only supports the current version. If it's a simple config issue, we try to help people whatever version. but what you are dealing with is something that will require digging into the old codebase, something that's not trivial.

If you are sticking with rsyslog v5 because it's supported by Red Hat, then i would suggest that you as them for support.

Adiscon also offers paid support for old versions (and 5.8 is _very_ old, current is 8.2), so that is also an option.

It could be related to the chrooted socket, it could just be a bug (disabling rate limiting didn't work in that version)

David Lang

On Wed, 30 Apr 2014, Anwar El fatayri wrote:

Hey Rainer,
We're waiting for RHEL7 before switching to rsyslog v7 or v8...
At the moment we use rsyslog v5 under RHEL6 and we really need to resolve this problem.
Could that be realted to the chrooted log socket ??? --->
$AddUnixListenSocket /var/named/chroot/dev/log
$SystemLogRateLimitInterval 0 and $SystemLogRateLimitBurst 0 are added in the begining of the rsyslog.conf file.
Thx in advance
Anwar




Date: Wed, 30 Apr 2014 11:11:18 +0200
From: [email protected]
To: [email protected]
Subject: Re: [rsyslog] Rsyslog V5 (5.8.10) -- Rate-limiting

It's probably a bug with this very outdated version. Can you reproduce it
with 8.2?

Rainer


On Wed, Apr 30, 2014 at 10:49 AM, Anwar El fatayri <
[email protected]> wrote:

Hey all,
I've configured rsyslog to stop droping messages :
$SystemLogRateLimitInterval 0$SystemLogRateLimitBurst 0
However, I still get this message in /var/log/messages :
 imuxsock begins to drop messages from pid 26441 due to rate-limiting

26441 is the pid of named... Any ideas ??
Anwar


_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad
of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you
DON'T LIKE THAT.

_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.

_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.


_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of 
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE 
THAT.

Reply via email to