[ClusterLabs] Node Fencing and STONITH in Amazon Web Services

If you don’t mind, please allow me to walk through my architecture just a bit. I know that I am far from an expert on this stuff, but I feel like I have a firm grasp on how this all works conceptually. That said, I welcome your insights and advice on how to approach this problem—and any

Re: [ClusterLabs] Error When Creating LVM Resource

That makes sense. I wasn’t yet configuring the constraints on the cluster and was alarmed by the error messages…especially the ones where it seemed like the services weren’t starting anywhere. Eventually, however, that somehow magically resolved itself, so I did went ahead with adding the

Re: [ClusterLabs] Error When Creating LVM Resource

On Fri, Aug 26, 2016 at 9:32 AM, Jason A Ramsey wrote: > Failed Actions: > > * gctvanas-lvm_start_0 on node1 'not running' (7): call=42, > status=complete, exitreason='LVM: targetfs did not activate correctly', > > last-rc-change='Fri Aug 26 10:57:22 2016', queued=0ms,

[ClusterLabs] FYI: pacemaker will keep compatibility with python 2.6

Hello everybody, just an FYI: Pacemaker's test suites are mostly written in python. A few months ago, I raised the possibility of dropping support for python 2.6, to make it easier to support python 3. After some experience with updating our code, I found that we can support python 2.6+ and 3.2+

[ClusterLabs] Error When Creating LVM Resource

So, I’m setting up a two node cluster that will eventually (hopefully) serve as an HA iSCSI Target (Active/Passive) on RHEL 6. I’m using the [incredibly poorly written] guide I found on Linbit’s website (“Highly available iSCSI storage with DRBD and Pacemaker”). I have somehow gotten pretty far

Re: [ClusterLabs] ocf scripts shell and local variables

On 2016-08-26 08:56, Ken Gaillot wrote: On 08/26/2016 08:11 AM, Gabriele Bulfon wrote: I tried adding some debug in ocf-shellfuncs, showing env and ps -ef into the corosync.log I suspect it's always using ksh, because in the env output I produced I find this: KSH_VERSION=.sh.version This is

[ClusterLabs] ocf scripts shell and local variables

I tried adding some debug in ocf-shellfuncs, showing env and ps -ef into the corosync.log I suspect it's always using ksh, because in the env output I produced I find this: KSH_VERSION=.sh.version This is normally not present in the environment, unless ksh is running the shell. I also tried

Re: [ClusterLabs] ocf::heartbeat:IPaddr

I looked around what you suggested, inside ocf-binaris and ocf-shellfuncs etc. So I found also these logs in corosync.log : Aug 25 17:50:33 [2250] crmd: notice: process_lrm_event: xstorage1-xstorage2_wan2_IP_start_0:22 [ /usr/lib/ocf/resource.d/heartbeat/IPaddr[71]: local: not found [No

[ClusterLabs] Fwd: need some advise on pacemaker cluster setup with oracle db

hello experts, i need some advise in a pacemaker cluster setup. i have configured a pacemaker cluster with 2 x bl460c gen9 servers on a rhel 7.2 platform. cluster is configured and fencing is configured using fence_ipmilan agent and it is working. there are 16 luns from a 3par storage as a

[ClusterLabs] Fwd: need some advise on pacemaker cluster setup with oracle db

hello experts, i need some advise in a pacemaker cluster setup. i have configured a pacemaker cluster with 2 x bl460c gen9 servers on a rhel 7.2 platform. cluster is configured and fencing is configured using fence_ipmilan agent and it is working. there are 16 luns from a 3par storage as a