Hi,<br><br>Maybe this is related to no-quorum-policy. What is no-quorum-policy? You can check no-quorum-policy in "crm configure show" command. If you can not see in "crm configure show" command, then it is "stop" by default. If that is your case, then please set it to ignore by "crm configure property no-quorum-policy=ignore". and try it again.<br>
<br>Thanks<br>hj<br><br><div class="gmail_quote">On Tue, Dec 29, 2009 at 6:43 AM, Martin Gombač <span dir="ltr"><<a href="mailto:martin@isg.si">martin@isg.si</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi guys once again :-)<br>
<br>
my resource Hosting on top of ms_drbd_r0 keeps restarting even if the changes aren't local to the node.<br>
By that, i mean Hosting get's restarted on node1 even if i restart or outdate and demote node 2.<br>
<br>
My constrains:<br>
colocation Hosting_on_ms_drbd_r0 inf: Hosting ms_drbd_r0:Master<br>
order ms_drbd_r0_b4_Hosting inf: ms_drbd_r0:promote Hosting:start<br>
<br>
My resources:<br>
primitive Hosting ocf:heartbeat:Xen \<br>
params xmfile="/etc/xen/Hosting.cfg" \<br>
meta target-role="Started" allow-migrate="true" is-managed="true" \<br>
op monitor interval="120s" timeout="300s"<br>
primitive drbd_r0 ocf:linbit:drbd \<br>
params drbd_resource="r0" \<br>
op monitor interval="15s" role="Master" timeout="30s" \<br>
op monitor interval="30s" role="Slave" timeout="30"<br>
ms ms_drbd_r0 drbd_r0 \<br>
meta notify="true" master-max="2" inteleave="true"<br>
<br>
I use location to:<br>
location cli-prefer-Hosting Hosting \<br>
rule $id="cli-prefer-rule-Hosting" inf: #uname eq ibm1<br>
<br>
Example:<br>
Shuting down heartbeat on node2/ibm2, while resource is running perfectly fine on node1, makes resource Hosting restart on node1.<br>
<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: notice: native_print: Hosting (ocf::heartbeat:Xen): Started ibm1<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: notice: clone_print: Master/Slave Set: ms_drbd_r0<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: notice: short_print: Masters: [ ibm1 ibm2]<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: WARN: native_color: Resource drbd_r0:1 cannot run anywhere<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: info: master_color: Promoting drbd_r0:0 (Master ibm1)<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: info: master_color: ms_drbd_r0: Promoted 1 instances of a possible 2 to master<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: info: master_color: Promoting drbd_r0:0 (Master ibm1<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: info: master_color: ms_drbd_r0: Promoted 1 instances of a possible 2 to master<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: info: stage6: Scheduling Node ibm2 for shutdown<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: notice: LogActions: Restart resource Hosting (Started ibm1)<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: notice: LogActions: Leave resource drbd_r0:0 (Master ibm1)<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: notice: LogActions: Demote drbd_r0:1 (Master -> Stopped ibm2)<br>
Dec 29 14:21:28 ibm1 pengine: [3716]: notice: LogActions: Stop resource drbd_r0:1 (ibm2)<br>
...<br>
Dec 29 14:21:28 ibm1 crmd: [3713]: info: te_rsc_command: Initiating action 8: stop Hosting_stop_0 on ibm1(local)<br>
Dec 29 14:21:28 ibm1 crmd: [3713]: info: do_lrm_rsc_op: Performing key=8:4:0:13282265-c62f-4341-9fa5-363cd30ddd3e op=Hosting_stop_0 )<br>
Dec 29 14:21:28 ibm1 lrmd: [3710]: info: rsc:Hosting:19: stop<br>
...<br>
Dec 29 14:21:34 ibm1 crmd: [3713]: info: match_graph_event: Action Hosting_stop_0 (8) confirmed on ibm1..si (rc=0)<br>
Dec 29 14:21:34 ibm1 crmd: [3713]: info: te_rsc_command: Initiating action 9: start Hosting_start_0 on ibm1..si (local)<br>
Dec 29 14:21:34 ibm1 lrmd: [3710]: info: rsc:Hosting:21: start<br>
....<br>
...<br>
.<br>
<br>
<br>
Please advise me on how to configure ordering and collocation constrains, to not get Hosting resource restarted each time when something happens to backup drbd resource on the second node.<br>
<br>
<br>
Thank you.<br>
Martin<br>
<br>
_______________________________________________<br>
Pacemaker mailing list<br>
<a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Dream with longterm vision!<br>kerdosa<br>