Lars,<br><br>we found the "fly in the ointment" . we know why it fails, but no idea how to fix it.<br>Take this basic setup:<br><br>test1 and test2 running drbd and heartbeat.<br>drbd is on a cross-over cable between the two.
<br>heartbeat is on the public interface.<br>test1 is primary (for the sake of argument)<br><br>unplug the public ethernet interface from test1.<br>Nothing changes.<br><br>test2 cannot become primary. it is impossible.<br>
test1 is already primary.<br>drbd connection is active.<br><br>heartbeat attempts to run a drbddisk r0 start on test2<br>which is physically impossible, because drbd is already running.<br>test2 never gets the virtual ip resource (though I'm not sure why).
<br>the debug log says "success" but it doesn't actually do it.<br>running the command manually for the virtual ip works ok though.<br><br>heartbeat would need to do the following for this to work properly:<br>
1. don't attempt to start drbd - this will never work<br>2. do an unmount of the drbd filesystems on test1<br>3. do a drbdadm secondary on test1<br>4. then do a drbdadm primary all on test2<br><br>I'm not even sure this is possible.
<br><br>Dan.<br>