I am running 2 rsyslog servers (prd-syslog-001, prd-syslog-002) sharing a virtual IP managed by heartbeat (prd-syslog-000) clients are configured to send logs to the virtualIP *.info;mail.none;authpriv.none;cron.none @@prd-syslog-000 authpriv.* @@prd-syslog-000 local7.* @@prd-syslog-000
I have found when the primary host goes down and the secondary takes over, logs are not arriving at the secondary host unless I restart rsyslog on the client, this was not the behaviour I was expecting. Is there any default configuration that may be stopping logs from being sent when the server sitting behind the virtual ip changes? The functionality I was trying to achive is as follows: * clients log to prd-syslog-000 * heartbeat controls prd-syslog-000 address (prd-syslog-001 primary, prd-syslog-002 on failover) * prd-syslog-002 is configured to forward logs to prd-syslog-001 * during downtime of prd-syslog-001 these logs will sit queued * when prd-syslog-001 comes back up it will take over prd-syslog-000 and start recieving client logs * prd-syslog-002 will flush its queue back to prd-syslog-001 The reason I am using this setup as opposed to logging to two rsyslog hosts is to support devices that can only log to one host, and provide one location with a consistent set of logs instead of two machines with out of sync logs. running rsyslog-3.22 Thanks, Rob _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
