On Wed, 19 Jan 2011, Sean Conner wrote:
It was thus said that the Great Robert Jennings once stated:
With TCP it appears the clients remote logging stops indefinitely, in
fact even when a failback occurs it still isnt logging messages to the
primary server until I restart the client rsyslog process.
With UDP behaviour is as expected, with a ~20-30 second failover period
where messages are lost (settings not tweaked in anyway)
Does the virtual IP address have its own MAC address? It could be an ARP
issue.
Also, if you are using UDP, have you thought maybe of setting the rsyslogd
on each box to listen to a multicast address and send the traffic out to
said multicast address? That way, both machines will get the traffic. This
will only work if all the systems are on the same network segment though
(I'm doing this on my home network with a syslog daemon specifically
programmed to accept multicast addresses).
I actually do that (a multicast MAC address rather than a multicast IP
address, but the same concept), the problem is reconciling the logs on the
two boxes. if one goes down from 1:00-1:10 and the other is down from
2:00-2:10, neither has a complete set of logs
David Lang
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com
