[Pacemaker] How to prevent a node that joins the cluster after reboot from starting the resources.

ihjaz Mohamed ihjazmohamed at yahoo.co.in
Mon Aug 22 03:55:19 EDT 2011


Has any one here come across this issue?.

--- On Wed, 17/8/11, ihjaz Mohamed <ihjazmohamed at yahoo.co.in> wrote:

From: ihjaz Mohamed <ihjazmohamed at yahoo.co.in>
Subject: [Pacemaker] How to prevent a node that joins the cluster after reboot from starting the resources.
To: pacemaker at oss.clusterlabs.org
Date: Wednesday, 17 August, 2011, 12:23 PM

Hi All,

Am getting an unmanaged error as shown below when one of the node is rebooted 
and comes back to join the cluster. 

Online: [ aceblr101.com aceblr107.com ]

 Resource Group: HAService

     FloatingIP (ocf::heartbeat:IPaddr2):       Started aceblr107.com (unmanaged) FAILED

     acestatus  (lsb:acestatus):        Stopped

 Clone Set: pingdclone

     Started: [ aceblr101.com aceblr107.com ]

Failed actions:

    FloatingIP_stop_0 (node=aceblr107.com, call=7, rc=1, status=complete): unknown error
Below is my configuration:node $id="8bf8e613-f63c-43a6-8915-4b2dbf72a4a5" aceblr101.com

node $id="bde62a1f-0f29-4357-a988-0e26bb06c4fb" aceblr107.com

primitive FloatingIP ocf:heartbeat:IPaddr2 \

        params ip="xx.xxx.xxx.xxx" nic="eth0:0"

primitive acestatus lsb:acestatus \

        op start interval="30"

primitive pingd ocf:pacemaker:pingd \

        params host_list="xx.xxx.xxx.1" multiplier="100" \

        op monitor interval="15s" timeout="5s"

group HAService FloatingIP acestatus \

        meta target-role="Started"

clone pingdclone pingd \

        meta globally-unique="false"

location ip1_location FloatingIP \

        rule $id="ip1_location-rule" pingd: defined pingd

property $id="cib-bootstrap-options" \

        dc-version="1.0.11-1554a83db0d3c3e546cfd3aaff6af1184f79ee87" \

        cluster-infrastructure="Heartbeat" \

        expected-quorum-votes="2" \

        stonith-enabled="false" \

        no-quorum-policy="ignore" \

 see from the logs that when the rebooted node comes back and joins the 
cluster, the resources on that node is getting started even though the 
resources are started on the existing node.

When resources on both nodes are started it tries to stop it on one of the node which fails and goes to unmanaged mode.

Could anyone help me on how I should configure so that the 
resources are not started on the new node that joins the cluster after a
 reboot when it is already started on the existing node.

-----Inline Attachment Follows-----

Pacemaker mailing list: Pacemaker at oss.clusterlabs.org

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110822/ce6d40ec/attachment-0003.html>

More information about the Pacemaker mailing list