On Mon, 9 Jan 2017, Jaroslav Shejbal via rsyslog wrote:
Hi,
I have an issue with rsyslog when I remove systemd from my debian system.
It look like dropping messages that are sent to to the socket. I never had
this issue when i've run it under a systemd, but I have my reasons to not
having systemd. David Lang at github pointed out rate limiting, but I tried
that with no effect.
sending 1000 logs to /dev/log is probably triggering the rate limiting
see http://www.rsyslog.com/doc/v8-stable/configuration/modules/imuxsock.html
it would probably also be good if you delivered messages to the socket that were
valid log messages
you are not providing the full config (what you are providing includes
references to templates that you don't provide, what else is missing?)
David Lang
My config and test script with output can be found here:
http://pastebin.com/wHCe2c8m
My github issue can be found here:
https://github.com/rsyslog/rsyslog/issues/1348
So I am asking you all here for any kind of help or advice. It is very
appeciated. I can provide anything what is needed to debug.
Best Regards,
Jaroslav Shejbal
_______________________________________________
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.
