Ubuntu
rsyslog package

rate limit cannot be disabled: imuxsock begins to drop messages

Bug #1092936 reported by Ralf Hildebrandt
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
rsyslog (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm seeing lots of message like this:

Dec 21 13:09:35 webmail rsyslogd-2177: imuxsock begins to drop messages from pid 1552 due to rate-limiting
Dec 21 13:09:38 webmail rsyslogd-2177: imuxsock lost 190 messages from pid 1552 due to rate-limiting

although the config contains:
$SystemLogRateLimitInterval 0

which should disable the rate-limiting. And yes, rsyslogd has been restarted after setting SystemLogRateLimitInterval 0!

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: rsyslog 5.8.6-1ubuntu8.1
ProcVersionSignature: Ubuntu 3.2.0-32.51-virtual 3.2.30
Uname: Linux 3.2.0-32-virtual i686
ApportVersion: 2.0.1-0ubuntu17
Architecture: i386
Date: Fri Dec 21 16:49:10 2012
MarkForUpload: True
SourcePackage: rsyslog
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.rsyslog.conf: 2012-12-10T22:56:12.367034

Revision history for this message
Ralf Hildebrandt (ralf-hildebrandt) wrote :
Revision history for this message
Mikko Pesari (mpesari) wrote :

Hi Ralf, try adding this line to your config file, should fix it:
$IMUXSockRateLimitInterval 0

Steve Langasek (vorlon)
tags: added: bot-stop-nagging
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in rsyslog (Ubuntu):
status: New → Confirmed
Revision history for this message
Denis Konstantinov (linvinus) wrote :

small clarification:

line with option
$IMUXSockRateLimitInterval 0

must be after
$ModLoad imuxsock

Ashok (ashokdolare)
Changed in rsyslog (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.