Hi David I'm able to get the fail-over to work (from the primary server IP to the secondary server IP) using an if-last-action-failed construct. However, I can't seem to get it to do so 'quickly'. If I drop the primary connection from the server side, it take around 15 minutes for the client side to detect this and then do the fail-over. I've tried playing with the following parameters (using various settings):
$InputTCPServerKeepAlive on $InputTCPServerKeepAlive_probes 1 $InputTCPServerKeepAlive_time 1 $InputTCPServerKeepAlive_intvl 1 and have confirmed using tcpdump that these do indeed have an effect (for example, number of seconds between keep-alive pings), but still the rsyslog client still doesn't perform the fail-over for around 15 minutes. Any ideas? The idea here is for the fail-over to occur as quickly as possible as this is a high-availability environment (all nodes in the mesh are interconnected with two Ethernet fabrics using SCTP, but rsyslog is only using TCP, hence we need this failover mechanism to work). Peter -- Sent from: http://rsyslog-users.1305293.n2.nabble.com/ _______________________________________________ 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.
