Brian Sheets wrote:
Yes, not only does it work manually, when I run fence_ack_manual, that causes the fence_apc_snmp to work.
So,
System failure
fenced says its trying to fence
then the fenced says its waiting for ack, which never comes and the system doesn't get powered down
then I run fence_ack_manual, and then the system powers down.
It looks like a fence_manual config entry is still loaded in your
cluster for fencing that node. Did you change your cluster.conf file
without increasing the version number and telling cman to reload the
config? fence_ack_manual should only do something if fence_manual is
setup for that node, also, you should not have seen that fence_manual
config entry when fence_apc_snmp is configured as the sole fence agent.
Thanks,
Eric
eric@xxxxxxxxxxx
<?xml version="1.0"?>
<cluster name="index" config_version="2">
<cman two_node="1" expected_votes="1">
</cman>
<clusternodes>
<clusternode name="oc-index3" votes="1">
<fence>
<method name="single">
<device name="oc-cab1-pdu2" port="18"
option="off"/>
</method>
</fence>
</clusternode>
<clusternode name="oc-index4" votes="1">
<fence>
<method name="single">
<device name="oc-cab1-pdu1" port="16" option="off"/>
</method>
</fence>
</clusternode>
</clusternodes>
<fencedevices>
<fencedevice name="oc-cab1-pdu2" agent="fence_apc_snmp"
ipaddr="172.16.14.9" login="apc" passwd="xxxx"/>
<fencedevice name="oc-cab1-pdu1" agent="fence_apc_snmp"
ipaddr="172.16.14.8" login="apc" passwd="xxxx"/>
</fencedevices>
</cluster>
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
--
Linux-cluster mailing list
Linux-cluster@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/linux-cluster
