[rsyslog-notify] Forum Thread: Re: Rate limiting - (Mode 'reply')
noreply at adiscon.com
noreply at adiscon.com
Thu May 7 10:17:36 CEST 2015
User: shivam99aa
Forumlink: http://kb.monitorware.com/viewtopic.php?p=25521#p25521
Message:
----------
[quote="dlang":ygd5uqkp]what messages are you loosing? messages arriving
via UDP, messages arriving via /dev/log, others?
what rate are messages arriving at?
I'm assuming you are talking about UDP messages
[/quote:ygd5uqkp]
I am reading messages on local machine using /dev/log and then sending to
other machine on network via omrelp for storing all log messages.
So i do not think UDP can be blamed here. Correct me please if i am wrong.
[quote="dlang":ygd5uqkp]
with v5 you can loose messages due to DNS lookup delays (you can try
starting rsyslog with -x)
If you are getting error messages at startup, it can cause other problems
because the full config isn't parsed. can you post your full
config?[/quote:ygd5uqkp]
I also started rsyslog with -x option and nothing comes on screen but i do
get these messages in syslog log file
rsyslogd: WARNING: rsyslogd is running in compatibility mode. Automatically
generated config directives may interfer with your rsyslog.conf settings.
We suggest upgrading your config and adding -c5 as the first rsyslogd
option.
rsyslogd: invalid selector line (port), probably not doing what was
intended
rsyslogd: Warning: backward compatibility layer added to following
directive to rsyslog.conf: ModLoad immark
rsyslogd: Warning: backward compatibility layer added to following
directive to rsyslog.conf: MarkMessagePeriod 1200
rsyslogd: Warning: backward compatibility layer added to following
directive to rsyslog.conf: ModLoad imuxsock
I am attaching my rsyslog.conf here. Please take a look and suggest me what
can be done.
More information about the rsyslog-notify
mailing list