[Pacemaker] syntax in rsc_template after update

Hi, I am in the process of updating my SUSE SLES 11 system from SP3 to SP4. This involves some version changes: crmsh from 1.2.6 to 2.1.2 pacemaker from 1.1.11 to 1.1.12 corosync stays on 1.4.7 and openais on 1.1.4 After restarting the updated system complains about syntax error

Re: [Pacemaker] Invisible dependency (at least to me)

Hi, my first post on this might have been to complicated. I broke it down to a test case. I have four resources: A1, B1, C1 and B2. B1 is a Master/Slave. The complete group should run on node korfwf01 (preferably) or on node korfwf02, not on korfwm01, not on korfwm02. B1:Master depends on A1, C

Re: [Pacemaker] is_managed meta attribute on suse 10 with heartbeat + pacemaker

Hi, On 15.07.2014 14:03, emmanuel segura wrote: > I was using crm_resource, because using crmsh i can't start a resource > on a specific node. > > example: > > crm(live)resource# start Dummy2 node02 > usage: start You can "move" a stopped resource, then start it: crm resource move Dummy2 nod

[Pacemaker] Invisible dependency (at least to me)

Hi, I have this configuration (minus the stonith resources and stuff on other nodes for brevity): node korfwf01 node korfwf02 rsc_template template-DRBD ocf:linbit:drbd \ op start interval="0" timeout="240" \

Re: [Pacemaker] Ordered Resources

Hi, On 30.06.2014 01:08, Dan Journo wrote: > The resources I have (and the order I need them to start are) > - IPAddr > - Promote DRBD > - Asterisk > They also need to be running on the same node. order ord-my-IPaddr-before-my-DRBD inf: \ my-IPaddr my-DRBD:pr

Re: [Pacemaker] Not unmoving colocated resources can provoke DRBD split-brain

ds, Robert -- Mit freundlichen Grüßen / Best regards ______ Robert Dahlem System & Network Services Fidelity Information Services KORDOBA GmbH Königsberger Straße 29 • 60487 Frankfurt Tel.: +49 69 13829-2180 Fax.: +49 69 13829-5-2180 <mailto:robert.dah...

Re: [Pacemaker] Not unmoving colocated resources can provoke DRBD split-brain

Hi Andrew, On 02.06.2014 02:57, Andrew Beekhof wrote: >> This seems to be some kind of a race condition: I added >> sleep 3 >> to a central point in /usr/lib/ocf/resource.d/linbit/drbd. > > Define central? === $ diff -u dr

Re: [Pacemaker] Not unmoving colocated resources can provoke DRBD split-brain

Hi, On 30.05.2014 13:20, Robert Dahlem wrote: >> run crm_report for the period covered by these commands and attach the >> result: >> >> # crm node standby korfwf01 ; sleep 10 >> # crm node standby korfwf02 ; sleep 10 >> # crm node online korfwf02 ; sl

Re: [Pacemaker] Not unmoving colocated resources can provoke DRBD split-brain

Hi, On 23.05.2014 02:40, Andrew Beekhof wrote: > run crm_report for the period covered by these commands and attach the result: > > # crm node standby korfwf01 ; sleep 10 > # crm node standby korfwf02 ; sleep 10 > # crm node online korfwf02 ; sleep 10 > # crm node online korfwf01 ; sleep 10 > #

Re: [Pacemaker] Not unmoving colocated resources can provoke DRBD split-brain

Hi, On 22.05.2014 16:59, Digimer wrote: > I can't speak to the pacemaker issue, but I can say that a proper > stonith config in pacemaker and fencing config in drbd would prevent a > split-brain. This would cause a node to reboot in this scenario, so you > still need to resolve it, but a reboot i

[Pacemaker] Not unmoving colocated resources can provoke DRBD split-brain

Hi, I have a 4-Node-Cluster (korfwf01, korfwf02, korfwm01, korfwm02). There is a DRBD resource which should only run on korfwf01 korfwf02: primitive DRBD-ffm ocf:linbit:drbd params drbd_resource=ffm \ op start interval=0 timeout=240 \ op promote interval=0 timeout=90 \ op demote interva

[Pacemaker] Priority Resource Option

Hi, the documentation states: "If not all resources can be active, the cluster will stop lower priority resources in order to keep higher priority ones active." What I did not find yet: what causes a resource not to be able to become active? I think I am looking for some kind of antagonist to "pr