Re: Re: help with fence_xvmd

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

 



ESGLinux wrote:
Hi again,

I have found that when I run the comand this way:
fence_xvmd -fddddd -I vnet0
Debugging threshold is now 5
-- args @ 0xbfa1cb58 --
  args->addr = 225.0.0.12
  args->domain = (null)
  args->key_file = /etc/cluster/fence_xvm.key
  args->op = 2
  args->hash = 2
  args->auth = 2
  args->port = 1229
  args->ifindex = 4
  args->family = 2
  args->timeout = 30
  args->retr_time = 20
  args->flags = 1
  args->debug = 5
-- end args --
Reading in key file /etc/cluster/fence_xvm.key into 0xbfa1bb58 (4096 max size)
Actual key length = 4096 bytesOpened ckpt vm_states
Setting up ipv4 multicast receive (225.0.0.12:1229 <http://225.0.0.12:1229>)
Joining multicast group
ipv4_recv_sk: success, fd = 7
My Node ID = 1
Domain                   UUID                                 Owner State
------                   ----                                 ----- -----
Domain-0                 00000000-0000-0000-0000-000000000000 00001 00001
NODO1                    73f4ab26-62de-732d-e5a2-1eb1740840ec 00001 00002
NODO2                    73f4ab26-62de-732d-e5a2-1eb1740840ed 00001 00002
Storing NODO1
Storing NODO2
........

But when I try to fence the from the node:
fence_xvm -H NODO2 -ddd -o null
Debugging threshold is now 3
-- args @ 0xbfed88bc --
  args->addr = 225.0.0.12
  args->domain = NODO2
  args->key_file = /etc/cluster/fence_xvm.key
  args->op = 0
  args->hash = 2
  args->auth = 2
  args->port = 1229
  args->ifindex = 0
  args->family = 2
  args->timeout = 30
  args->retr_time = 20
  args->flags = 0
  args->debug = 3
-- end args --
Reading in key file /etc/cluster/fence_xvm.key into 0xbfed786c (4096 max size)
Actual key length = 4096 bytesSending to 225.0.0.12 via 127.0.0.1
Sending to 225.0.0.12 via 192.168.1.186
Sending to 225.0.0.12 via 192.168.1.187
Sending to 225.0.0.12 via 10.0.0.1
Sending to 225.0.0.12 via 192.168.122.1
Waiting for connection from XVM host daemon.
.....
Timed out waiting for response

and doesn´t fence.



So your vm hosts are not on the eth0 network of Domain-0, but they are on the private network. IIRC, fence_xvmd listens, by default, on eth0.

You can overcome this by, if you use RHEL 5.3, adding -I vnet0 ( or whatever device which domain-0 uses to communicate with domU ) into the fence_xvmd 's parameter list .IIRC, this parm -I does not exist on RHEL 5.2 or ealier. You can do that by adding FENCE_XVMD_OPTS="-I vnet0" into /etc/sysconfig/cman.

hth,
Vu


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