Ok, I have update my config but it seems to fail when unfencing itself.
fence_node -U fails as well as it can't find cman and cman fails because
it can't unfence. A bit of a catch 22. SoŠ
# fence_node -U
fence_node: cannot connect to cman
New config:
<?xml version="1.0"?>
<cluster config_version="7" name="Xanadu">
<clusternodes>
<clusternode name="xanadunode1" nodeid="1">
<fence>
<method name="Method">
<device name="SCSI_Fence"/>
</method>
</fence>
<unfence>
<device action="on" name="SCSI_Fence"/>
</unfence>
</clusternode>
<clusternode name="xanadunode2" nodeid="2">
<fence>
<method name="Method">
<device name="SCSI_Fence"/>
</method>
</fence>
<unfence>
<device action="on" name="SCSI_Fence"/>
</unfence>
</clusternode>
</clusternodes>
<cman expected_votes="1" two_node="1"/>
<fencedevices>
<fencedevice agent="fence_scsi" name="SCSI_Fence"/>
</fencedevices>
</cluster>
Additionally these errors are being thrown to the console.
dlm: no local IP address has been set
dlm: cannot start dlm lowcomms -107
Thanks!
On 8/7/12 1:22 AM, "Digimer" <[email protected]> wrote:
>
>
>Without a way to put the lost node into a known state, the only safe
>option remaining is to hang. This is by design. You have to add fencing
>to your cluster.
>
>This explains it in detail;
>
>https://alteeve.com/w/2-Node_Red_Hat_KVM_Cluster_Tutorial#Concept.3B_Fenci
>ng
>
>--
>Digimer
>Papers and Projects: https://alteeve.com
--
Linux-cluster mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-cluster
