<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Use ping to set an attribute, then add a location.<br>
<br>
primitive re-ping-core ocf:pacemaker:ping \<br>
meta failure-timeout="60" \<br>
params name="at-ping-core" host_list="10.250.52.1"
multiplier="100" attempts="5" \<br>
op monitor interval="20" timeout="15" \<br>
op start interval="0" timeout="5" \<br>
op stop interval="0" timeout="5"<br>
location lo-named-ping cl-named \<br>
rule $id="cl-named-ping-rule" -inf: not_defined at-ping-core
or at-ping-core lte 0<br>
<br>
<br>
<div class="moz-cite-prefix">On 7/20/12 7:45 PM, Matteo Bignotti
wrote:<br>
</div>
<blockquote cite="mid:5009EDA3.8080102@switchvox.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Thank you man,<br>
<br>
I realized what it was, We're running pacemaker held up by a
third item (r-series) which through a usb connection and a
resource agent controls the cluster. When I unplug the network
cable he doesn't understand that it's disconnected because the
usb is still up if I unplug both it works.<br>
<br>
Now, let me try and ask...<br>
<br>
in my pacemaker I have this configuration<br>
<br>
--------------------------------------------------------------------------<br>
<br>
<b>primitive GatewayStatus ocf:pacemaker:ping \<br>
params host_list="10.10.0.1" multiplier="100" \<br>
op monitor interval="5" timeout="10"</b><br>
primitive ResourceCustom ocf:Company:resourcecustom \<br>
op monitor interval="10" timeout="20" \<br>
op stop interval="0" timeout="15" on-fail="standby" \<br>
meta migration-threshold="2" failure-timeout="30s"
target-role="Started"<br>
primitive rseries ocf:Company:rseries \<br>
params tty="/dev/rseries0" \<br>
op monitor interval="10" role="Master" timeout="30s" \<br>
op monitor interval="60" role="Slave" timeout="30s"<br>
ms rseries_ms rseries \<br>
meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" target-role="Master"<br>
clone GatewayStatusClone GatewayStatus<br>
<br>
colocation rsc-like-master inf: ResourceCustom rseries_ms:Master<br>
order rsc-after-rseries inf: rseries_ms:promote
ResourceCustom:start<br>
<br>
-------------------------------------------------------------------------------------------------<br>
<br>
============<br>
Last updated: Fri Jul 20 16:43:50 2012<br>
Last change: Fri Jul 20 16:11:15 2012 via cibadmin on cluster_01<br>
Stack: openais<br>
Current DC: cluster_01 - partition with quorum<br>
Version: 1.1.6.1-3.el5-0c7312c689715e096b716419e2ebc12b57962052<br>
2 Nodes configured, 2 expected votes<br>
5 Resources configured.<br>
============<br>
<br>
Online: [ cluster_01 cluster_02 ]<br>
<br>
ResourceCustom (ocf::Company:resourcecustom): Started
cluster_01<br>
Master/Slave Set: rseries_ms [rseries]<br>
Masters: [ cluster_01 ]<br>
Slaves: [ cluster_02 ]<br>
Clone Set: GatewayStatusClone [GatewayStatus]<br>
Started: [ cluster_01 cluster_02 ]<br>
<br>
<br>
------------------------------------------------------------------------------------------<br>
<br>
<br>
Now since I have the GatewayStatus, can I configure the cluster
telling it that IF the network fails I want ResourceCustom,
rseries:Master and Gateway to be together? I ask because when I
tried putting GatewayStatusClone in the colocation... havoc
happened... and nothing worked. did I do something wrong and it
should be the right configuration?<br>
<br>
thanks<br>
<br>
On 07/20/2012 02:14 PM, David Vossel wrote:<br>
</div>
<blockquote
cite="mid:9a7c067c-4c64-4bf0-8eb8-d7adc3514941@zmail18.collab.prod.int.phx2.redhat.com"
type="cite">
<pre wrap="">----- Original Message -----
</pre>
<blockquote type="cite">
<pre wrap="">From: "Matteo Bignotti" <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:mbignotti@switchvox.com"><mbignotti@switchvox.com></a>
To: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>
Sent: Friday, July 20, 2012 4:01:26 PM
Subject: [Pacemaker] Pull the plug on one node, the resource doesn't promote the other node to master
Hi guys,
I am having trouble understanding why this happens:
I have this cluster with 2 nodes, when I put one node in standby or
crash the resource, it correctly promotes on the second machine as
master.
But if I UNPLUG the first machine from the network, the resource
won't
promote the other one to master.
I am using corosync/pacemaker
why is that?
</pre>
</blockquote>
<pre wrap="">Are you using stonith? If node1 disappears, pacemaker has to have some sort of guarantee from a fencing device that it is in fact gone before the promotion happens.
This situation (unplugging node) differs from standby and the rsc crash because pacemaker still knows the state of node1 with after the standby/rsc crash. If the state of node1 can't be verified (unplugged from network), it needs to be fenced before the cluster can continue.
If you are still having trouble, upload a crm_report and we'll have a look.
-- Vossel
</pre>
<blockquote type="cite">
<pre wrap="">thanks
_______________________________________________
Pacemaker mailing list: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a>
</pre>
</blockquote>
<pre wrap="">_______________________________________________
Pacemaker mailing list: <a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a>
</pre>
</blockquote>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Pacemaker mailing list: <a class="moz-txt-link-abbreviated" href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a>
<a class="moz-txt-link-freetext" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
Project Home: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org">http://www.clusterlabs.org</a>
Getting started: <a class="moz-txt-link-freetext" href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a>
Bugs: <a class="moz-txt-link-freetext" href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a>
</pre>
</blockquote>
<br>
</body>
</html>