Quantcast
Viewing all articles
Browse latest Browse all 171040

fence_scsi: No such file or directory

Hi,

I'm testing proxmox to see if it will suit my needs for a two-node cluster. I'm using two VMs to host my nodes, proxmox1 and proxmox2. In the absence of a fencing utility for libvirt guests, I've decided to use fence_scsi for testing. In reality I'll probably use a PDU setup, but I really want to do some legitimate testing with fencing.

First, make sure all the nodes are up and quorum is established with clustat:
Code:

Member Status: Quorate


 Member Name                                                    ID  Status
 ------ ----                                                    ---- ------
 proxmox1                                                            1 Online, Local
 proxmox2                                                            2 Online
 /dev/block/8:33                                                    0 Online, Quorum Disk


I've uncommented FENCE_JOIN and restarted cman, but rgmanager won't start, so I manually join the fence domain on both nodes:

Code:

root@proxmox1:/var/log# fence_tool join
root@proxmox2:~# fence_tool join
root@proxmox1:/var/log# fence_tool ls
fence domain
member count  2
victim count  0
victim now    0
master nodeid 1
wait state    none
members      1 2

I try to fence node proxmox2 from proxmox1:

Code:

root@proxmox1:~# fence_node proxmox2
fence proxmox2 failed

Nothing in the fenced.log other than "fenced fenced 1364188437 started"

So I decided to try and manually fence from the command line using fence_scsi and the options from the config:


Code:

root@proxmox1:~# fence_scsi -d /dev/disk/by-id/scsi-149455400000000006c756e30000000000000000000000000 -n proxmox2 -o off
No such file or directory

Googling 'fence_scsi no such file or directory' let me to this bug report, which seems too old to affect me on ProxMox 3.2, but I'm not sure:

https://bugzilla.redhat.com/show_bug.cgi?id=409391



Here is my cluster.conf:

Code:

<?xml version="1.0"?>
<cluster config_version="5" name="ITGCluster">
  <cman expected_votes="3" keyfile="/var/lib/pve-cluster/corosync.authkey"/>
  <quorumd allow_kill="0" interval="1" label="proxmox_qdisk" tko="10" votes="1"/>
  <totem token="54000"/>
  <clusternodes>
    <clusternode name="proxmox1" nodeid="1" votes="1">
      <fence>
        <method name="scsi">
          <device key="1" name="virt_scsi"/>
        </method>
      </fence>
      <unfence>
        <device action="on" key="1" name="virt_scsi"/>
      </unfence>
    </clusternode>
    <clusternode name="proxmox2" nodeid="2" votes="1">
      <fence>
        <method name="scsi">
          <device key="2" name="virt_scsi"/>
        </method>
      </fence>
      <unfence>
        <device action="on" key="2" name="virt_scsi"/>
      </unfence>
    </clusternode>
  </clusternodes>
  <fencedevices>
    <fencedevice action="off" agent="fence_scsi" devices="/dev/disk/by-id/scsi-149455400000000006c756e30000000000000000000000000" logfile="/var/log/fence_scsi.log" name="virt_scsi"/>
  </fencedevices>
  <rm>
    <service autostart="1" exclusive="0" name="TestIP" recovery="relocate">
      <ip address="10.99.0.138"/>
    </service>
    <pvevm autostart="1" vmid="100"/>
  </rm>
</cluster>



So to conclude, I'd like to either get fence_scsi to work, or find some other way of reliably fencing a libvirt guest.

Viewing all articles
Browse latest Browse all 171040

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>