Re: fence_apc_snmp woes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.




----- Original Message -----
From: "Jeremy Carroll" <Jeremyc@xxxxxxxxxxxxxx>
To: "linux clustering" <linux-cluster@xxxxxxxxxx>
Sent: Friday, August 24, 2007 6:35:55 AM (GMT-0800) America/Los_Angeles
Subject: RE:  fence_apc_snmp woes

Try to run the fence agent manually. See if it works. Most likely the
problem is fenced cannot successfully run the program to power down the
switch. Post your results.

Ex:
fence_apc_snmp -v -a oc-index3 -c <passwd> -n 18 -o off 


-----Original Message-----
From: linux-cluster-bounces@xxxxxxxxxx
[mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Brian Sheets
Sent: Friday, August 24, 2007 6:06 AM
To: linux clustering
Subject:  fence_apc_snmp woes

I have a 2 node cluster on debian. Below is my cluster.conf. If I down
node1's nic 
node2 sees and tries to fence


Aug 24 10:57:38 oc-index4 fenced[7599]: oc-index3 not a cluster member
after 0 sec post_fail_delay
Aug 24 10:57:38 oc-index4 fenced[7599]: fencing node "oc-index3"
Aug 24 10:57:38 oc-index4 fence_manual: Node 172.16.14.100 needs to be
reset before recovery can procede.  Waiting for 172.16.14.100 to rejoin
the cluster or for manual acknowledgement that it has been reset (i.e.
fence_ack_manual -n 172.16.14.100)
Aug 24 10:59:34 oc-index4 fenced[7599]: fence "oc-index3" success

It states that it's fencing, but never does, and if I do a
fence_ack_manual, then fence_apc_snmp gets run and the node1 gets
powered down.

what am I missing?

<?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

[Index of Archives]     [Corosync Cluster Engine]     [GFS]     [Linux Virtualization]     [Centos Virtualization]     [Centos]     [Linux RAID]     [Fedora Users]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Camping]

  Powered by Linux