Re: [Pacemaker] Stopping corosync on the slave in a 2 node cluster causes all the resources on the master to stop. Please Help.

Hi Florian, I've just had a chance to try your suggestions. The interleave option didn't appear to make a difference, but getting rid of the order ActiveMQ_Data_after_ping_gateway_clone constraint has done the job perfectly. I don't think I can see any real reason why I needed that constraint.

[Pacemaker] Stopping corosync on the slave in a 2 node cluster causes all the resources on the master to stop. Please Help.

Hi Guys, I was hoping that someone might be able to do a quick review of my cluster config, shown below, to work out why when I shutdown corosync on the master all the resources failover to the slave without a problem, but if I shutdown corosync on the slave all of the resources on the master stop

[Pacemaker] DRBD 2 node cluster and STONITH configuration help required.

Hi there, I have successfully configured a 2 node DRBD pacemaker cluster using the instructions provided by LINBIT here: http://www.drbd.org/users-guide-emb/ch-pacemaker.html. The cluster works perfectly and I can migrate the resources back and forth between the two nodes without a problem. Howe

Re: [Pacemaker] Two node DRBD cluster will not automatically failover to the secondary

> Hi, > > For stateful resources like drbd you will have to setup stonith resources > for them to function properly or at all. > "stonith-enabled" is true by default. > > Sincerely > Shravan > > On Thu, Dec 17, 2009 at 6:29 AM, Tom Pride wrote: > >> Hi t

[Pacemaker] Two node DRBD cluster will not automatically failover to the secondary

Hi there, I have setup a two node DRBD culster with pacemaker using the instructions provided on the drbd.org website: http://www.drbd.org/users-guide-emb/ch-pacemaker.html The cluster works perfectly and I can migrate the resources back and forth between the two nodes without a problem. However