Hi, We have a simple heartbeat setup failing over between two hosts running CentOS.
Essentially, we have two mysql server instances. maindb runs on db0 and leafdb runs on db1. The system is configured so that if db0 fails, db1 takes over maindb and if db1 fails, db0 takes over leafdb. haresources looks like this: db0 IPaddr2::172.28.28.10/32 Filesystem::-Lsan0::/mnt/san0::ext3 mysql-main db1 IPaddr2::172.28.28.9/32 IPaddr2::172.28.28.11/32 Filesystem::-Lsan1::/mnt/san1::ext3 mysql-leaf On the same machines, we also have instances of dnscache and tinydns running on different IP addresses. dnscache runs on 172.28.28.6 on machine db0 and 172.28.28.5 on db1. What we are seeing is that the DNS service stops working after a failover until the dnscache/tinydns services are restarted. I have no idea why this might be - any ideas? Regardless, I can think of a couple of options we can implement to prevent this scenario: 1. Have heartbeat restart dnscache and tinydns after a failover. How can I do this? 2. Add a new resource failover over the dnscache/tinydns services. 3. Move dnscache and tinydns off the HA hosts onto a couple of "normal" boxes. Any advice appreciated. R. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
