[Pacemaker] 10.8 and pingd problem

Serge Dubrouski sergeyfd at gmail.com
Wed Mar 17 16:10:50 EDT 2010


Hello -

I've just installed fresh new Pacemaker 1.0.8 and ran into a problem
with pind. When Corosync/Pacemaker/Pingd start it doesn't initialize
pingd attribute for the nodes so the resources in the cluster stay
down. Then if I change configuration (delete/add pingd resource or
clone, stop/start node, etc.) pingd attr gets set and resources start
up. My configuration looks like this and used to work fine with 1.0.7:

primitive child_DoFencing stonith:external/xen0 \
        meta $id="primitive-child_DoFencing.meta" \
        params hostlist="fc-node1 fc-node2" dom0="home"
primitive drbd0 ocf:heartbeat:drbd \
        params drbd_resource="drbd0" \
        op monitor interval="59s" role="Master" timeout="10s" \
        op monitor interval="60s" role="Slave" timeout="10s"
primitive fs0 ocf:heartbeat:Filesystem \
        meta $id="primitive-fs0.meta" \
        params fstype="ext2" directory="/mnt" device="/dev/drbd0"
primitive myIP ocf:heartbeat:IPaddr \
        meta $id="primitive-myIP.meta" \
        params ip="192.168.1.130" \
        op monitor interval="30s" timeout="30s" \
        op start interval="0s" timeout="30s" \
        op stop interval="0s" timeout="30s"
primitive myPgsql ocf:heartbeat:pgsql \
        meta $id="primitive-myPgsql.meta" \
        params ctl_opt="-w" \
        op monitor interval="30s" timeout="30s" \
        op start interval="0s" timeout="30s" \
        op stop interval="0s" timeout="30s"
primitive pingd ocf:pacemaker:pingd \
        params dampen="5s" multiplier="1000" host_list="192.168.2.1"
group myGroup myIP fs0 myPgsql \
        meta $id="group-myGroup.meta"
ms ms-drbd0 drbd0 \
        meta clone-max="2" clone-node-max="1" master-max="1"
master-node-max="1" notify="yes" globally-unique="false" \
        meta target-role="Started"
clone DoFencing child_DoFencing \
        meta clone-max="2" clone-node-max="1"
clone pingd-clone pingd \
        meta target-role="Started"
location connected myGroup \
        rule $id="connected-rule" -inf: not_defined pingd or pingd lte 0
location primNode myGroup \
        rule $id="prefered_primNode" 1000: #uname eq fc-node1
colocation myGroup_on_drbd0 inf: myGroup ms-drbd0:Master
order drbd0_before_myGroup : ms-drbd0:promote myGroup:start
property $id="cib-bootstrap-options" \
        default-resource-stickiness="600" \
        default-resource-failure-stickiness="-520" \
        dc-version="1.0.6-cebe2b6ff49b36b29a3bd7ada1c4701c7470febe" \
        cluster-infrastructure="openais" \
        expected-quorum-votes="2" \
        last-lrm-refresh="1254058067" \
        no-quorum-policy="ignore"


-- 
Serge Dubrouski.




More information about the Pacemaker mailing list