is the retry limit tuneable ? also is ther a way to trace what rsyslog is actually doing there ?
thanks On Thu, Jun 6, 2013 at 1:26 PM, David Lang <[email protected]> wrote: > On Thu, 6 Jun 2013, Marcelo Veglienzone wrote: > > Hi all, >> >> I have a central rsyslog server saving files locally in flat files as well >> as pushing the messages to two logstash instances where mail and cron >> messages go to one instance and the rest go the other one. >> I've tried to implement the usage of >> $**ActionExecOnlyWhenPreviousIsSu**spended but it's not working for me. >> >> So the question is, how does rsyslog check for availability ? >> > > It trys to send a message to the destination, if it gets an error it's not > working. At that point the retry logic kicks in and it tries again until it > exceeds the retry limit, at that point it's considered unavailable. > > At least, that's my understanding :-) > > David Lang > ______________________________**_________________ > rsyslog mailing list > http://lists.adiscon.net/**mailman/listinfo/rsyslog<http://lists.adiscon.net/mailman/listinfo/rsyslog> > http://www.rsyslog.com/**professional-services/<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. > -- Marcelo Veglienzone _______________________________________________ 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.
