I sorted it out.
I thought it would be like 'obliterate-peer.sh' or 'rhcs_fence' on cman
where cman just had to be running for the fence-handler script to work.
I dug into crm-fence-peer.sh and saw that it was parsing cib.xml. I'd
not configured DRBD inside pacemaker, so the fence handler was
On Sun, Sep 29, 2013 at 10:25:12PM -0700, Digimer wrote:
I sorted it out.
I thought it would be like 'obliterate-peer.sh' or 'rhcs_fence' on cman
where cman just had to be running for the fence-handler script to work.
I dug into crm-fence-peer.sh and saw that it was parsing cib.xml. I'd
not
On 30/09/13 04:02, Lars Ellenberg wrote:
On Sun, Sep 29, 2013 at 10:25:12PM -0700, Digimer wrote:
I sorted it out.
I thought it would be like 'obliterate-peer.sh' or 'rhcs_fence' on cman
where cman just had to be running for the fence-handler script to work.
I dug into crm-fence-peer.sh and
Hi all,
I'm back to learning pacemaker and DRBD 8.4. I've got a couple VMs
with fence_xvm / fence_virtd working (I can crash a node with 'echo c
/proc/sysrq-trigger' and it reboots).
However, when I start DRBD (not added to pacemaker, just running with
'handlers { fence-peer
I fixed my pacemaker fencing issue (upgraded from pacemaker 1.1.9 to
1.1.10 and changed my fencing from fence_xvm to fence_virsh). So now I
can repeatedly crash a node and it will be fenced successfully. However,
drbd still complains that the fence is broken;
When I start DRBD on the crashed node
