I don't know that this has been fixed, I haven't seen anything about it.
This is one of the many reasons why RepeatedMsgReduction is discouraged. It makes some sense if the consumer of the logs is a person reading them, but that's far from a common situation
If this is still seen as a problem, I wonder if the message remains stalled past a log rotation (HUP)
David Lang On Tue, 1 Sep 2015, Kevin Newman wrote:
Hi, I seem to be affected by Bugzilla 527 regarding stale timestamps on RepeatedMsgReduction, but because of the migration to GitHub I'm having trouble finding out whether this bug was ever resolved or if it even made it into the new Issues list. http://bugzilla.adiscon.com/show_bug.cgi?id=527 Can anyone confirm that this bug is still present in the latest build or is it resolved? And if it's still present, do I need to reopen this bug in the new GitHub issues list? Thanks! -Kevin ______________________________________________ See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email _______________________________________________ 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.
