Personally I use fence_xvm. IIRC, it's the supported equivalent of fence_virsh.
On 24 Oct 2013, at 6:38 pm, Beo Banks beo.ba...@googlemail.com wrote:
hi,
i have enable the debug option and i use the ip instead of hostname
primitive stonith-zarafa02 stonith:fence_virsh \
params
*hi,
i wants to testing the fail-over capabilities of my cluster.
i run pkill -9 corosync on 2nd node and i saw on the 1node that he wants to
stonith the node2 but he giving up after too many failures to fence node
via commandline it works without any problems
fence_virsh -a host2 -l root -x
Am Mittwoch, 23. Oktober 2013, 10:57:28 schrieb Beo Banks:
*hi,
i wants to testing the fail-over capabilities of my cluster.
i run pkill -9 corosync on 2nd node and i saw on the 1node that he wants to
stonith the node2 but he giving up after too many failures to fence node
via
hi,
thanks for answer.
the pacemaker|corosync is running on both nodes.
[chkconfig | grep corosync
corosync0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
chkconfig | grep pacemaker
pacemaker 0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
@ssh key
no, i created the
Am Mittwoch, 23. Oktober 2013, 12:39:35 schrieb Beo Banks:
hi,
thanks for answer.
the pacemaker|corosync is running on both nodes.
[chkconfig | grep corosync
corosync0:Aus 1:Aus 2:Ein 3:Ein 4:Ein 5:Ein 6:Aus
chkconfig | grep pacemaker
pacemaker 0:Aus 1:Aus