Dear all,In version 8.22.0 (at least), rsyslog doesn't notify when the rate limit feature is triggered. I'm using rsyslog on an embedded device with linux 3.19.x
I'm sure some messages are dropped by rsyslog as I can get all of them if I increase the SysSock.RateLimit.Burst
Is it a known bug or does my syslog configuration file below misses something:
# rsyslog configuration file (for Red Hat-based systems) # note that most of this config file uses old-style format, # because it is well-known AND quite suitable for simple cases # like we have with the default config. For more advanced # things, RainerScript configuration is suggested. # # For more information see /usr/share/doc/rsyslog-*/rsyslog_conf.html # or latest version online at http://www.rsyslog.com/doc/rsyslog_conf.html # If you experience problems, see http://www.rsyslog.com/doc/troubleshoot.html #### MODULES #### module(load="imuxsock" SysSock.RateLimit.Interval="5" SysSock.RateLimit.Burst="200" SysSock.RateLimit.Severity="1") # provides support for local system logging (e.g. via logger command). SysSock.RateLimit.Interval : rate limiting will only work, if a process sends more than 200 messages in 5 seconds. Voir https://www.rsyslog.com/doc/v8-stable/configuration/modules/imuxsock.html#imuxsock-rate-limiting-label et https://www.rsyslog.com/tag/rate-limiting/ module(load="imklog") # provides kernel logging support (previously done by rklogd) #module(load"immark") # provides --MARK-- message capability #### GLOBAL DIRECTIVES #### #### RULES (Règles par défaut NON TRAITES APRES CHARGEMENT PROG VARUNA)#### # Log all kernel messages to the console. # Logging much else clutters up the screen. #kern.* /dev/console # Log anything (except mail) of level info or higher. # Don't log private authentication messages! *.debug;mail.none;authpriv.none;cron.none /var/log/messages # The authpriv file has restricted access. authpriv.* /var/log/secure # Log all the mail messages in one place. mail.* /var/log/maillog # Log cron stuff cron.* /var/log/cron # Everybody gets emergency messages *.emerg :omusrmsg:* # Save news errors of level crit and higher in a special file. uucp,news.crit /var/log/spooler # Save boot messages also to boot.log local7.* /var/log/boot.log # ### begin forwarding rule ### # The statement between the begin ... end define a SINGLE forwarding # rule. They belong together, do NOT split them. If you create multiple # forwarding rules, duplicate the whole block! # Remote Logging (we use TCP for reliable delivery) # # An on-disk queue is created for this action. If the remote host is # down, messages are spooled to disk and sent when it is up again. #$WorkDirectory /var/lib/rsyslog # where to place spool files #$ActionQueueFileName fwdRule1 # unique name prefix for spool files #$ActionQueueMaxDiskSpace 1g # 1gb space limit (use as much as possible) #$ActionQueueSaveOnShutdown on # save messages to disk on shutdown #$ActionQueueType LinkedList # run asynchronously #$ActionResumeRetryCount -1 # infinite retries if host is down # remote host is: name/ip:port, e.g. 192.168.0.1:514, port optional #*.* @@remote-host:514 # ### end of the forwarding rule ###Sorry if this issue was already solved in a previous post but the archives are not accessible...
Thanks in advance Best regards, Thomas
<<attachment: thomas_spitz.vcf>>
_______________________________________________ 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.
