Can you please give this fix a try (details in description):

http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=24b62834801043bf2d9560b0
cca3967e5762bea1

This will be released as part of 5.8.1. Please provide feedback.

Thanks,
Rainer

> -----Original Message-----
> From: [email protected] [mailto:rsyslog-
> [email protected]] On Behalf Of Hongqing Yang
> Sent: Wednesday, April 27, 2011 8:32 AM
> To: rsyslog-users
> Subject: Re: [rsyslog] cannot turn off the rate limit
> 
> Rainer,
> 
> I have tested rsyslog 5.7.9 with $SystemLogRateLimitInterval 0 and
> $RepeatedMsgReduction off as below
> 
> #### MODULES ####
> 
> $ModLoad imuxsock # provides support for local system logging (e.g. via
> logger command)
> $SystemLogRateLimitInterval 0
> $RepeatedMsgReduction off
> $ModLoad imklog   # provides kernel logging support (previously done by
> rklogd)
> #$ModLoad immark  # provides --MARK-- message capability
> 
> The rsyslog template is used, but imuxsock still drops messages, please
> find the logs in attachments.
> 
> Thanks,
> Hongqing
> 
> 
> 
> 
> 
> ----- Original Message -----
> From: "Rainer Gerhards" <[email protected]>
> To: "rsyslog-users" <[email protected]>
> Sent: Tuesday, April 26, 2011 9:13:19 PM
> Subject: Re: [rsyslog] cannot turn off the rate limit
> 
> There is some mismatch in your rsyslog versions... Because the messages
> you
> cite from your log ("imuxsock begins to drop messages from pid 358 due
> to
> rate-limiting") are NOT even present in 4.6.3. It looks like you are
> running
> either a newer version as service and use an old one for the debug log
> OR
> rsyslog versions and modules are mixed up on your system.
> 
> Rainer
> 
> > -----Original Message-----
> > From: [email protected] [mailto:rsyslog-
> > [email protected]] On Behalf Of Hongqing Yang
> > Sent: Tuesday, April 26, 2011 8:11 AM
> > To: rsyslog-users
> > Subject: Re: [rsyslog] cannot turn off the rate limit
> >
> > Rainer,
> >
> > Thanks for your reply.  I think the commend you mentioned is
> > RepeatedMsgReduction off, am I right?
> > but the messages are still dropped.
> >
> > <46>2011-04-26T05:36:20.002095+00:00 localhost rsyslogd-2177:
> imuxsock
> > begins to drop messages from pid 358 due to rate-limiting
> > <46>2011-04-26T05:36:23.297653+00:00 localhost rsyslogd-2177:
> imuxsock
> > lost 559 messages from pid 358 due to rate-limiting
> >
> > There is no errors in the debug logs. By the way, in my situation,
> the
> > dropped messages are not repeated messages.
> >
> > Thanks.
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "Rainer Gerhards" <[email protected]>
> > To: "rsyslog-users" <[email protected]>
> > Sent: Monday, April 25, 2011 8:58:54 PM
> > Subject: Re: [rsyslog] cannot turn off the rate limit
> >
> > You should have a look at the syslog error log ;)
> >
> > 6950.906989271:7f1afcdeb720: cfline: '$SystemLogRateLimitInterval 0'
> > 6950.907004432:7f1afcdeb720: Called LogError, msg: invalid or yet-
> > unknown
> > config
> >  file command - have you forgotten to load a module?
> > 6950.907033424:7f1afcdeb720: config line NOT successfully processed
> >
> > The error message is emitted, but probably thrown away ;)
> >
> > Anyhow, you use 4.6.3, which does not support the new type of rate
> > limiting
> > at all. So I guess what comes into your way is repated message
> > reduction,
> > which you can turn off via a separate statement (Which I don't know
> out
> > of my
> > head, but if you search for repated message reduction you should find
> > it
> > relatively easily :).
> >
> > HTH
> >
> > Rainer
> > > -----Original Message-----
> > > From: [email protected] [mailto:rsyslog-
> > > [email protected]] On Behalf Of Hongqing Yang
> > > Sent: Monday, April 25, 2011 12:36 PM
> > > To: rsyslog-users
> > > Subject: Re: [rsyslog] cannot turn off the rate limit
> > >
> > > Hi, Rainer,
> > >
> > > Please find the rsyslog.conf and rsyslog log file in  attachments.
> > > Thanks.
> > >
> > >
> > > ----- Original Message -----
> > > From: "Rainer Gerhards" <[email protected]>
> > > To: "rsyslog-users" <[email protected]>
> > > Sent: Monday, April 25, 2011 5:55:56 PM
> > > Subject: Re: [rsyslog] cannot turn off the rate limit
> > >
> > > Sorry, I'Ve not been precise enough. I need a rsyslog debug log,
> not
> > > the
> > > logfile. See this page:
> > >
> > > http://www.rsyslog.com/doc/troubleshoot.html
> > >
> > > Note that we have a public holiday over here and I am meeting with
> > > family. So
> > > I have no lab at hand. But with the debug log, I may be able to
> tell
> > > something.
> > >
> > > Rainer
> > >
> > > > -----Original Message-----
> > > > From: [email protected] [mailto:rsyslog-
> > > > [email protected]] On Behalf Of Hongqing Yang
> > > > Sent: Monday, April 25, 2011 11:27 AM
> > > > To: rsyslog-users
> > > > Subject: Re: [rsyslog] cannot turn off the rate limit
> > > >
> > > > Sorry, failed to attach the file. Now it is fine.
> > > >
> > > > ----- Original Message -----
> > > > From: "Hongqing Yang" <[email protected]>
> > > > To: "rsyslog-users" <[email protected]>
> > > > Sent: Monday, April 25, 2011 5:24:29 PM
> > > > Subject: Re: [rsyslog] cannot turn off the rate limit
> > > >
> > > > Hi, Rainer,
> > > >
> > > > Thanks for your reply, Now I try to transfer guest installation
> > logs
> > > > from  KVM to host by virtio.
> > > > But I find the logs are different, after discussed with the
> > anaconda
> > > > team, I know I have
> > > > to turn ratelimit off.
> > > >
> > > > The configuration of rsyslog is below:
> > > >
> > > > #### MODULES ####
> > > >
> > > > $ModLoad imuxsock.so    # provides support for local system
> logging
> > > > (e.g. via logger command)
> > > > $SystemLogRateLimitInterval 0
> > > > $ModLoad imklog.so      # provides kernel logging support
> > (previously
> > > > done by rklogd)
> > > > #$ModLoad immark.so     # provides --MARK-- message capability
> > > >
> > > > the logs on the guest can be found in attachment.
> > > >
> > > > Thanks.
> > > >
> > > > ----- Original Message -----
> > > > From: "Rainer Gerhards" <[email protected]>
> > > > To: "rsyslog-users" <[email protected]>
> > > > Sent: Monday, April 25, 2011 4:57:43 PM
> > > > Subject: Re: [rsyslog] cannot turn off the rate limit
> > > >
> > > > Can you please send a debug log. Probably it is sufficient to see
> > the
> > > > startup, but we may need a full session.
> > > >
> > > > Rainer
> > > >
> > > > > -----Original Message-----
> > > > > From: [email protected] [mailto:rsyslog-
> > > > > [email protected]] On Behalf Of Hongqing Yang
> > > > > Sent: Monday, April 25, 2011 10:16 AM
> > > > > To: [email protected]
> > > > > Subject: [rsyslog] cannot turn off the rate limit
> > > > >
> > > > > Hi, All
> > > > >
> > > > > I try to turn off the rate limit by adding
> > > > $SystemLogRateLimitInterval
> > > > > 0  after $ModLoad imuxsock.so,
> > > > > but it does not work, now I cannot get all the logs.  Do you
> have
> > > any
> > > > > idea how to fix it? Thanks.
> > > > >
> > > > >
> > > > > Hongqing
> > > > > _______________________________________________
> > > > > rsyslog mailing list
> > > > > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > > > > http://www.rsyslog.com
> > > > _______________________________________________
> > > > rsyslog mailing list
> > > > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > > > http://www.rsyslog.com
> > > > _______________________________________________
> > > > rsyslog mailing list
> > > > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > > > http://www.rsyslog.com
> > > _______________________________________________
> > > rsyslog mailing list
> > > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > > http://www.rsyslog.com
> > _______________________________________________
> > rsyslog mailing list
> > http://lists.adiscon.net/mailman/listinfo/rsyslog
> > http://www.rsyslog.com
> _______________________________________________
> rsyslog mailing list
> http://lists.adiscon.net/mailman/listinfo/rsyslog
> http://www.rsyslog.com
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com

Reply via email to