Hey everyone -
As detailed in Github issue #146 (https://github.com/rsyslog/rsyslog/issues/146) action.execOnlyWhenPreviousIsSuspended does not appear to be currently working. Does anyone have an alternative method of addressing the use case where a destination server ends up being down for an extended period? If we need to get these messages out of the current message queue, what is the best course of action? Currently they seem to get suspended forever until the application runs out of memory. I'm trying to find out how to address this scenario without using action.execOnlyWhenPreviousIsSuspended? since it currently isn't working on CentOS 6 with 8.4.2. -- James _______________________________________________ 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.
