<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Dec 16, 2012, at 7:29 PM, <a href="mailto:pacemaker-request@oss.clusterlabs.org">pacemaker-request@oss.clusterlabs.org</a> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Message: 5<br>Date: Mon, 17 Dec 2012 14:23:15 +1100<br>From: Andrew Beekhof <<a href="mailto:andrew@beekhof.net">andrew@beekhof.net</a>><br>To: The Pacemaker cluster resource manager<br><span class="Apple-tab-span" style="white-space: pre; "> </span><<a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>Subject: Re: [Pacemaker] Ordered resource is not restarting after<br><span class="Apple-tab-span" style="white-space: pre; "> </span>migration if it's already started on new host<br>Message-ID:<br><span class="Apple-tab-span" style="white-space: pre; "> </span><<a href="mailto:CAEDLWG35TfnGhMM_FuSSxedryAMSS5OwFxRdLG5Ytcmj7yxaWw@mail.gmail.com">CAEDLWG35TfnGhMM_FuSSxedryAMSS5OwFxRdLG5Ytcmj7yxaWw@mail.gmail.com</a>><br>Content-Type: text/plain; charset=ISO-8859-1<br><br>On Sat, Dec 15, 2012 at 10:58 AM, Neal Peters <<a href="mailto:nealppeters@gmail.com">nealppeters@gmail.com</a>> wrote:<br><blockquote type="cite">Hello-<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I'm running Pacemaker v. 1.1 (pacemaker-1.1.7-6.el6.x86_64) on CentOS 6.3 and am observing behavior on my systems that differs from the behavior described in the manual.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Basically, the desired behavior (and the behavior described in Pacemaker Explained Section 6.3.1) is that when a "first" resource in an ordered set is moved to a host where the "then" resource is already running, the "then" resource will be restarted.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">From Pacemaker Explained 6.3.1 Mandatory Ordering:<br></blockquote><blockquote type="cite">-If the first resource is (re)started while the then resource is running, the then resource will be stopped and restarted.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I am not seeing this behavior however. I am seeing that the "then" resource is left running.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I have 2 servers running a fairly basic setup that is fairly close to the one described in the Clusters from Scratch document. Config follows:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">node host2<br></blockquote><blockquote type="cite">node host1<br></blockquote><blockquote type="cite">primitive ClusterIP ocf:heartbeat:IPaddr2 \<br></blockquote><blockquote type="cite"> params ip="192.168.0.225" cidr_netmask="32" \<br></blockquote><blockquote type="cite"> op monitor interval="1s" \<br></blockquote><blockquote type="cite"> meta target-role="Started"<br></blockquote><blockquote type="cite">primitive DNSserver lsb:named \<br></blockquote><blockquote type="cite"> op monitor interval="1s"<br></blockquote><blockquote type="cite">colocation ip-with-DNSserver inf: DNSserver ClusterIP<br></blockquote><blockquote type="cite">order DNS-server-after-ip inf: ClusterIP DNSserver<br></blockquote><blockquote type="cite">property $id="cib-bootstrap-options" \<br></blockquote><blockquote type="cite"> dc-version="1.1.7-6.el6-148fccfd5985c5590cc601123c6c16e966b85d14" \<br></blockquote><blockquote type="cite"> cluster-infrastructure="openais" \<br></blockquote><blockquote type="cite"> expected-quorum-votes="2" \<br></blockquote><blockquote type="cite"> stonith-enabled="false" \<br></blockquote><blockquote type="cite"> no-quorum-policy="ignore" \<br></blockquote><blockquote type="cite"> last-lrm-refresh="1355268791"<br></blockquote><blockquote type="cite">rsc_defaults $id="rsc-options" \<br></blockquote><blockquote type="cite"> resource-stickiness="102"<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">When the DNSserver resource is migrated from one node to the other and named is already started on the other node (for whatever reason), named is not restarted<br></blockquote><br>1) Ordering constraints are behaving as expected, DNSserver is started<br>after ClusterIP<br>2) Starting something (DNSserver) that is already started is a no-op<br>3) Don't start cluster services outside of the cluster<br><br>3 is the root problem in your case<br></span></blockquote><div><br></div><div>Thank you for your prompt reply. It sounds as though Pacemaker is operating in the way that you expect in this situation.</div><div><br></div><div>Your description of Pacemaker behavior</div><div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">2) Starting something (DNSserver) that is already started is a no-op</span></blockquote></div><div><br></div><div>differs from behavior described in the documentation</div><div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><blockquote type="cite">-If the <b>first</b> resource is (re)started while the then resource is running, the <b>then</b> resource will be stopped and restarted.</blockquote></span></blockquote>( <a href="http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/s-resource-ordering.html#_mandatory_ordering">http://clusterlabs.org/doc/en-US/Pacemaker/1.1-crmsh/html/Pacemaker_Explained/s-resource-ordering.html#_mandatory_ordering</a> Section 6.3.1)</div><div><br></div><div>Is there a place that I can/should report this discrepancy between actual behavior and behavior described in the documentation?</div><div><br></div><div>Thank you.</div><div><br></div><br><blockquote type="cite"><br><blockquote type="cite"><br></blockquote><blockquote type="cite">Dec 14 15:32:28 host1 snmpd[5296]: Connection from UDP: [192.168.0.129]:51000->[192.168.0.93]<br></blockquote><blockquote type="cite">Dec 14 15:32:40 host1 lrmd: [8733]: info: rsc:ClusterIP:5: start<br></blockquote><blockquote type="cite">Dec 14 15:32:40 host1 IPaddr2(ClusterIP)[9542]: INFO: ip -f inet addr add 192.168.0.225/32 brd 192.168.0.225 dev eth1<br></blockquote><blockquote type="cite">Dec 14 15:32:40 host1 IPaddr2(ClusterIP)[9542]: INFO: ip link set eth1 up<br></blockquote><blockquote type="cite">Dec 14 15:32:40 host1 IPaddr2(ClusterIP)[9542]: INFO: /usr/lib64/heartbeat/send_arp -i 200 -r 5 -p /var/run/heartbeat/rsctmp/se<br></blockquote><blockquote type="cite">nd_arp-192.168.0.225 eth1 192.168.0.225 auto not_used not_used<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 crmd[8736]: info: process_lrm_event: LRM operation ClusterIP_start_0 (call=5, rc=0, cib-update=10, co<br></blockquote><blockquote type="cite">nfirmed=true) ok<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 lrmd: [8733]: info: rsc:ClusterIP:6: monitor<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 lrmd: [8733]: info: rsc:DNSserver:7: start<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 lrmd: [9601]: WARN: For LSB init script, no additional parameters are needed.<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 lrmd: [8733]: info: RA output: (DNSserver:start:stdout) Starting named:<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 lrmd: [8733]: info: RA output: (DNSserver:start:stdout) named: already running<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 lrmd: [8733]: info: RA output: (DNSserver:start:stdout) [ OK<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 lrmd: [8733]: info: RA output: (DNSserver:start:stdout) ]#015<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 lrmd: [8733]: info: RA output: (DNSserver:start:stdout)<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 crmd[8736]: info: process_lrm_event: LRM operation DNSserver_start_0 (call=7, rc=0, cib-update=11, co<br></blockquote><blockquote type="cite">nfirmed=true) ok<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 lrmd: [8733]: info: rsc:DNSserver:8: monitor<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 crmd[8736]: info: process_lrm_event: LRM operation ClusterIP_monitor_1000 (call=6, rc=0, cib-update=1<br></blockquote><blockquote type="cite">2, confirmed=false) ok<br></blockquote><blockquote type="cite">Dec 14 15:32:41 host1 crmd[8736]: info: process_lrm_event: LRM operation DNSserver_monitor_1000 (call=8, rc=0, cib-update=1<br></blockquote><blockquote type="cite">3, confirmed=false) ok<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Are there errors in my config that are keeping the restart from happening?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks in advance.<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">-Neal<br></blockquote><blockquote type="cite"><br></blockquote><br class="Apple-interchange-newline"></blockquote></div><br></body></html>