I posted this in linux-ha but got no response, and didn't even see my post get to the list.<br>so here it is here. seems more like a drbd issue anyhow.<br><br>I have two systems, with heartbeat and DRBD installed.<br>Initially I tested with just DRBD, and was able to fail back and forth very well and easily.
<br><br>However, when using heartbeat, it won't fail over, no matter what I do. status doesn't change.<br><br>I have it setup so that DRBD goes over a cross-over cable between the two systems on a private IP.<br>and heartbeat is run over the public (internet facing) interfaces.
<br><br>My heartbeat config looks like this:<br><br>vi /etc/ha.d/ha.cf -<br>logfacility local0<br><br>logfile /var/log/ha-log<br><br>debugfile /var/log/ha-debug<br><br>udpport 694<br><br>keepalive 1<br><br>deadtime 60<br>
<br>bcast eth0<br><br>node LAB-TEST-01<br><br>node LAB-TEST-02<br><br>auto_failback on<br><br>and /etc/ha.d/haresources (note IP address is the virtual public IP):<br><br>lab-test-01 <a href="http://192.168.10.218">192.168.10.218
</a> drbddisk Filesystem::/dev/drbd0::/mysql::ext3 Filesystem::/dev/drbd1::/data::ext3<br>configs on both systems are the same, hosts files identical with all the entries.<br>I've tried with auto_failback on and off seems to make no difference.
<br><br>I test by pulling the public cable on lab-test-01, or using ifconfig eth0 down<br><br>Also, when I bring the server back up drbd can't see the other system (either one), it becomes<br>secondary/unknown and primary/unknown.
<br><br>It seems for some cases I need to use the drbdadm primary all on the primary at boot up to fix that.<br>One other note about the heartbeat issue above. I found if I enter the commands manually it seems to work.<br>
which makes it really weird.<br><br>Can anyone tell me what's going wrong?<br><br>Dan.<br>