Sorry William

But if you wanna implement dual primary i think you don't nee promote for
your drbd
Try to use clone without master/slave

2012/1/30 William Seligman <selig...@nevis.columbia.edu>

> I'm trying to follow the directions for setting up a dual-primary DRBD
> setup
> with CMAN and Pacemaker. I'm stuck at an annoying spot: Pacemaker won't
> promote
> the DRBD resources to primary at either node.
>
>
> Here's the result of crm_mon:
>
> Last updated: Mon Jan 30 17:07:03 2012
> Stack: cman
> Current DC: hypatia-tb - partition with quorum
> Version: 1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f
> 2 Nodes configured, unknown expected votes
> 2 Resources configured.
> ============
>
> Online: [ orestes-tb hypatia-tb ]
>
>  Master/Slave Set: AdminClone [AdminDrbd]
>     Slaves: [ hypatia-tb orestes-tb ]
>
>
>
> /etc/cluster/cluster.conf:
>
> <cluster config_version="6" name="Nevis_HA">
>  <logging debug="off"/>
>  <cman expected_votes="1" two_node="1" />
>  <clusternodes>
>    <clusternode name="hypatia-tb" nodeid="1">
>      <fence>
>        <method name="pcmk-redirect">
>          <device name="pcmk" port="hypatia-tb"/>
>        </method>
>      </fence>
>    </clusternode>
>    <clusternode name="orestes-tb" nodeid="2">
>      <fence>
>        <method name="pcmk-redirect">
>          <device name="pcmk" port="orestes-tb"/>
>        </method>
>      </fence>
>    </clusternode>
>  </clusternodes>
>  <fencedevices>
>    <fencedevice name="pcmk" agent="fence_pcmk"/>
>  </fencedevices>
>  <!-- <fence_daemon post_join_delay="30" /> -->
> </cluster>
>
>
> crm configure show:
>
> node hypatia-tb
> node orestes-tb
> primitive AdminDrbd ocf:linbit:drbd \
>        params drbd_resource="admin" \
>        op monitor interval="60s" role="Master" \
>        op stop interval="0" timeout="320" \
>        op start interval="0" timeout="240"
> primitive Clvmd lsb:clvmd
> ms AdminClone AdminDrbd \
>        meta master-max="2" master-node-max="1" clone-max="2"
> clone-node-max="1"
> notify="true"
> clone ClvmdClone Clvmd
> colocation ClvmdWithAdmin inf: ClvmdClone AdminClone:Master
> order AdminBeforeClvmd inf: AdminClone:promote ClvmdClone:start
> property $id="cib-bootstrap-options" \
>        dc-version="1.1.5-5.el6-01e86afaaa6d4a8c4836f68df80ababd6ca3902f" \
>        cluster-infrastructure="cman" \
>        stonith-enabled="false"
>
>
> DRBD looks OK:
>
> # cat /proc/drbd
> version: 8.4.0 (api:1/proto:86-100)
> GIT-hash: 28753f559ab51b549d16bcf487fe625d5919c49c build by gardner@,
> 2012-01-25
> 19:10:28
>  0: cs:Connected ro:Secondary/Secondary ds:UpToDate/UpToDate C r-----
>    ns:0 nr:0 dw:0 dr:0 al:0 bm:0 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
>
>
> I can manually do "drbdadm primary admin" on both nodes and get a
> Primary/Primary state. That still does not get Pacemaker to promote the
> resource.
>
>
> The only vaguely relevant lines in /var/log/messages seem to be:
>
> Jan 30 17:38:13 hypatia-tb lrmd: [11260]: info: RA output
> (AdminDrbd:0:start:stdout)
> Jan 30 17:38:13 hypatia-tb lrmd: [11260]: info: RA output:
> (AdminDrbd:0:start:stderr) Could not map uname=
> hypatia-tb.nevis.columbia.edu to
> a UUID: The object/attribute does not exist
> Jan 30 17:38:13 hypatia-tb lrmd: [11260]: info: RA output
> (AdminDrbd:0:start:stdout)
>
>
> I've tried running with iptables both on and off, and the results are the
> same.
>
>
> Any clues?
> --
> Bill Seligman             | Phone: (914) 591-2823
> Nevis Labs, Columbia Univ | mailto://selig...@nevis.columbia.edu
> PO Box 137                |
> Irvington NY 10533 USA    | http://www.nevis.columbia.edu/~seligman/
>
>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>



-- 
esta es mi vida e me la vivo hasta que dios quiera
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to