I wrote:
> Sometimes it writes messages to the relevant log files immediately;
> sometimes it seems to treasure them up in a buffer somewhere and
> write them some time later.
I've discovered that the source of the problem was the line
*.* @@192.168.2.100
which someone had added to my rsyslog.conf.
But 192.168.2.100 was unreachable or not accepting connections.
Evidently, the timeout for those connections amounts to 134
seconds, and during each connection attempt, all other logging
stops. Evidently, rsyslogd waits 30 seconds (during which time
logging is normal) before attempting the remote connection again.
Commenting out the 92.168.2.100 line made my problem go away.
_______________________________________________
rsyslog mailing list
https://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.
