Re: [ClusterLabs] fence-agents-all missing some agents

On 01/02/18 01:59 -0500, Digimer wrote: > On RHEL 7 (and possible elsewhere), 'fence-agents-all' doesn't install > the following; > > fence-agents-virsh.x86_64 4.0.11-66.el7_4.3 updates > fence-sanlock.x86_64 3.5.0-1.el7base > fence-virtd.x86_64

[ClusterLabs] Synching Amazon EC2 Instances

I have a case of which I want to synchronize between two (or more) Ubuntu Amazon EC2s, I want to sync between the two servers, I followed this article , but I'm stuck at the step of getting the

Re: [ClusterLabs] Synching Amazon EC2 Instances

On Thu, 2018-02-01 at 16:22 +0200, Ibraheem abu hamdeh wrote: > I have a case of which I want to synchronize between two (or more) > Ubuntu Amazon EC2s, I want to sync between the two servers, I > followed this article, but I'm stuck at the step of getting > the private_binding_IP_address, I

[ClusterLabs] Issues with DB2 HADR Resource Agent

Hi, I am facing multiple issues with the DB2 Resource Agent. The first issue was that when I start Pacemaker, DB2 is also started and immediately after that DB2 gets stopped. I fixed that by removing \ before $ in Line numbers 686, 689 and 691. 684 CMD="if db2 connect to $db; 685 then 686

Re: [ClusterLabs] Issues with DB2 HADR Resource Agent

On 02/01/2018 05:57 PM, Dileep V Nair wrote: > Now the second issue I am facing is that when I crash the node were DB > is primary, the STANDBY DB is not getting promoted to PRIMARY. I could > fix that by adding below lines in db2_promote() > > 773 *) > 774 # must take over forced > 775 force="by

Re: [ClusterLabs] Issues with DB2 HADR Resource Agent

Thanks Ondrej for the response. I have set the PEER_WINDOW to 1000 which I guess is a reasonable value. What I am noticing is it does not wait for the PEER_WINDOW. Before that itself the DB goes into a REMOTE_CATCHUP_PENDING state and Pacemaker give an Error saying a DB in