Fence Issues

[adamb]

Looking for input on a fence issue I am having with a fresh Proxmox 3.3 cluster.

I can manually fence with no issues like so. This atleast proves that the management port is on the network and functioning as expected.

root@vaultprox3:~# fence_ipmilan -l USERID -p PASSW0RD -a 10.80.12.187 -o reboot
Success: Rebooted

root@vaultprox3:~# fence_node vaultprox4 -vv
fence vaultprox4 dev 0.0 agent fence_ipmilan result: error from agent
agent args: nodename=vaultprox4 agent=fence_ipmilan ipaddr=10.80.12.187 lanplus=1 login=USERID passwd=PASSW0RD power_wait=5
fence vaultprox4 failed

However if I try to use fence_node, or kill corosync or anything like that fence fails. I can't for the life of me figure out what the issue is. Here is my cluster.conf.

root@vaultprox3:~# cat /etc/pve/cluster.conf
<?xml version="1.0"?>
<cluster config_version="5" name="vaultprox">
  <cman expected_votes="3" keyfile="/var/lib/pve-cluster/corosync.authkey"/>
  <quorumd allow_kill="0" interval="3" label="vaultprox_qdisk" master_wins="1" tko="10"/>
  <totem token="54000"/>
  <fencedevices>
    <fencedevice agent="fence_ipmilan" ipaddr="10.80.12.186" lanplus="1" login="USERID" name="ipmi1" passwd="PASSW0RD" power_wait="5"/>
    <fencedevice agent="fence_ipmilan" ipaddr="10.80.12.187" lanplus="1" login="USERID" name="ipmi2" passwd="PASSW0RD" power_wait="5"/>
  </fencedevices>
  <clusternodes>
    <clusternode name="vaultprox3" nodeid="1" votes="1">
      <fence>
        <method name="1">
          <device name="ipmi1"/>
        </method>
      </fence>
    </clusternode>
    <clusternode name="vaultprox4" nodeid="2" votes="1">
      <fence>
        <method name="1">
          <device name="ipmi2"/>
        </method>
      </fence>
    </clusternode>
  </clusternodes>
  <rm>
  </rm>
</cluster>

At this point I am at a loss as to what the issue could be. I appreciate the input!

root@vaultprox3:~# pveversion -v
proxmox-ve-2.6.32: 3.3-138 (running kernel: 2.6.32-33-pve)
pve-manager: 3.3-2 (running version: 3.3-2/995e687e)
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-31-pve: 2.6.32-132
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.1-35
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-23
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-9
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

 

[adamb]

Would appreciate some input on this from the Dev's. From my perspective fencing is pretty much broke in 3.3 using fence_ipmilan.

 

[dietmar]

Would appreciate some input on this from the Dev's. From my perspective fencing is pretty much broke in 3.3 using fence_ipmilan.

Please try to run 'fence_ipmilan' manually, using the exactly same flags you specified in the cluster config (use -P for lanplus).

 

[adamb]

Please try to run 'fence_ipmilan' manually, using the exactly same flags you specified in the cluster config (use -P for lanplus).

You know if I could buy you a beer I would!

Using lanplus and it would fail, so I removed it from the cluster.conf and all is well. Although I am unsure as to why it is causing an issue. I am using lanplas across a large number of 2.3 and 3.2 cluster, as far as I know its just for added security.