On Thu, 19 Sep 2013, Lucas Tobey wrote:
Hi,
I'm having a strange issue with Rsyslog. I have two destinations
configured for omrelp:
rsyslogd 5.8.11
$ModLoad omrelp
*.* :omrelp:x.x.x.x:20514;RSYSLOG_ForwardFormat
*.* :omrelp:y.y.y.y:20514;RSYSLOG_ForwardFormat
The problem is that when when one of the destinations is not reachable
like y.y.y.y, the other destination, x.x.x.x, does not receive any logs
as well. I'm thinking this might have something to do with the way RELP
works, but after waiting for quite some time for messages to show up on
x.x.x.x due to a timeout or other function I never did receive the logs.
Is this something I can control? Is it a bug?
Yes, you have told rsyslog to deliver these messages in a reliable way, and it
will not complete delivering one message and go on to the next if one of the
boxes is down.
To decouple delivery of messages to the two destinations, you need to create an
action queue for each destination. When you do so, you can set a bunch of
parameters for the queue, including thresholds for discarding messages and if
you want the queue to include the ability to write to disk.
David Lang
_______________________________________________
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.
