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