<p dir="ltr">Why did you hide the resource agent provider? Is it a custom one</p>
<div class="gmail_quote">Le 30 avr. 2014 01:10, &quot;Andrew Beekhof&quot; &lt;<a href="mailto:andrew@beekhof.net">andrew@beekhof.net</a>&gt; a écrit :<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On 29 Apr 2014, at 11:06 pm, Sékine Coulibaly &lt;<a href="mailto:scoulibaly@gmail.com">scoulibaly@gmail.com</a>&gt; wrote:<br>
<br>
&gt; Hi,<br>
&gt;<br>
&gt; Let me explain my use case. I&#39;m using RHEL 6.3<br>
<br>
fwiw, there are updates to pacemaker 1.1.10 in 6.4 and 6.5.<br>
Its even supported now.<br>
<br>
&gt; with Corosync + Pacemaker + PostgreSQL9.2 + repmgr 2.0. I have two nodes names clustera and clusterb.<br>
&gt;<br>
&gt; I have a total of 3 resources :<br>
&gt; - APACHE<br>
&gt; - BOUM<br>
&gt; - MS_POSTGRESQL<br>
&gt;<br>
&gt; They are defined as follow :<br>
&gt;<br>
&gt; sudo crm configure  primitive APACHE ocf:heartbeat:apache \<br>
&gt;    params configfile=/etc/httpd/conf/httpd.conf \<br>
&gt;    op monitor interval=5s timeout=10s \<br>
&gt;    op start interval=0 timeout=10s \<br>
&gt;    op stop interval=0 timeout=10s<br>
&gt;<br>
&gt;  sudo crm configure primitive BOUM ocf:heartbeat:anything \<br>
&gt;    params binfile=/usr/local/boum/current/bin/boum \<br>
&gt;    workdir=/var/boum \<br>
&gt;    logfile=/var/log/boum/boum_STDOUT \<br>
&gt;    errlogfile=/var/log/boum/boum_STDERR \<br>
&gt;    pidfile=/var/run/boum.pid \<br>
&gt;    op monitor interval=5s timeout=10s \<br>
&gt;    op start interval=0 timeout=10s \<br>
&gt;    op stop interval=0 timeout=10s<br>
&gt;<br>
&gt; sudo crm configure primitive POSTGRESQL ocf:xxxxxx:postgresql \<br>
&gt;    params repmgr_conf=/var/lib/pgsql/repmgr/repmgr.conf pgctl=/usr/pgsql-9.2/bin/pg_ctl pgdata=/opt/pgdata \<br>
&gt;    op start interval=0 timeout=90s \<br>
&gt;    op stop interval=0 timeout=60s \<br>
&gt;    op promote interval=0 timeout=120s \<br>
&gt;    op monitor interval=53s role=Master \<br>
&gt;    op monitor interval=60s role=Slave<br>
&gt;<br>
&gt; Since the PostgreSQL is in streaming replication, I need to have a master and a slave constantly running. Hence, I created an MasterSlave resource, called MS_POSTGRESQL.<br>
&gt;<br>
&gt; I want to that APACHE, BOUM and the master node of PostgreSQL run altogether on the same node. It looks like that as soon as I add a colocation, the Postgresql slave doesn&#39;t start anymore.<br>
&gt;<br>
&gt; I end up with :<br>
&gt;<br>
&gt; Online: [ clusterb clustera ]<br>
&gt;<br>
&gt;  Master/Slave Set: MS_POSTGRESQL [POSTGRESQL]<br>
&gt;      Masters: [ clustera ]<br>
&gt;      Stopped: [ POSTGRESQL:1 ]<br>
&gt; APACHE  (ocf::heartbeat:apache):        Started clustera<br>
&gt; BOUM     (ocf::heartbeat:anything):   Started clustera<br>
&gt;<br>
&gt; My configuration is as follows :<br>
&gt;<br>
&gt;<br>
&gt; node clustera \<br>
&gt;         attributes standby=&quot;off&quot;<br>
&gt; node clusterb \<br>
&gt;         attributes standby=&quot;off&quot;<br>
&gt; primitive APACHE ocf:heartbeat:apache \<br>
&gt;         params configfile=&quot;/etc/httpd/conf/httpd.conf&quot; \<br>
&gt;         op monitor interval=&quot;5s&quot; timeout=&quot;10s&quot; \<br>
&gt;         op start interval=&quot;0&quot; timeout=&quot;10s&quot; \<br>
&gt;         op stop interval=&quot;0&quot; timeout=&quot;10s&quot; \<br>
&gt;         meta target-role=&quot;Started&quot;<br>
&gt; primitive BOUM ocf:heartbeat:anything \<br>
&gt;         params binfile=&quot;/usr/local/boum/current/bin/boum&quot; workdir=&quot;/var/boum&quot; logfile=&quot;/var/log/boum/boum_STDOUT&quot; errlogfile=&quot;/var/log/boum/boum_STDERR&quot; pidfile=&quot;/var/run/boum.pid&quot; \<br>

&gt;         op monitor interval=&quot;5s&quot; timeout=&quot;10s&quot; \<br>
&gt;         op start interval=&quot;0&quot; timeout=&quot;10s&quot; \<br>
&gt;         op stop interval=&quot;0&quot; timeout=&quot;10s&quot;<br>
&gt; primitive POSTGRESQL ocf:xxxxxxx:postgresql \<br>
&gt;         params repmgr_conf=&quot;/var/lib/pgsql/repmgr/repmgr.conf&quot; pgctl=&quot;/usr/pgsql-9.2/bin/pg_ctl&quot; pgdata=&quot;/opt/pgdata&quot; \<br>
&gt;         op start interval=&quot;0&quot; timeout=&quot;90s&quot; \<br>
&gt;         op stop interval=&quot;0&quot; timeout=&quot;60s&quot; \<br>
&gt;         op promote interval=&quot;0&quot; timeout=&quot;120s&quot; \<br>
&gt;         op monitor interval=&quot;53s&quot; role=&quot;Master&quot; \<br>
&gt;         op monitor interval=&quot;60s&quot; role=&quot;Slave&quot;<br>
&gt; ms MS_POSTGRESQL POSTGRESQL \<br>
&gt;         meta clone-max=&quot;2&quot; target-role=&quot;Started&quot; resource-stickiness=&quot;100&quot; notify=&quot;true&quot;<br>
&gt; colocation link-resources inf: ZK UFO BOUM APACHE MS_POSTGRESQL<br>
<br>
Could you send the raw xml (cibadmin -Ql) please?<br>
I&#39;ve never gotten used to crmsh&#39;s colocation syntax and don&#39;t have it installed locally (pcs is the supplied tool for configuring pacemaker on rhel)<br>
<br>
&gt; property $id=&quot;cib-bootstrap-options&quot; \<br>
&gt;         dc-version=&quot;1.1.7-6.el6-148fccfd5985c5590cc601123c6c16e966b85d14&quot; \<br>
&gt;         cluster-infrastructure=&quot;openais&quot; \<br>
&gt;         expected-quorum-votes=&quot;2&quot; \<br>
&gt;         stonith-enabled=&quot;false&quot; \<br>
&gt;         no-quorum-policy=&quot;ignore&quot; \<br>
&gt;         default-resource-stickiness=&quot;10&quot; \<br>
&gt;         start-failure-is-fatal=&quot;false&quot; \<br>
&gt;         last-lrm-refresh=&quot;1398775386&quot;<br>
&gt;<br>
&gt; Is this a normal behaviour ? If it is, is there a workaround I didn&#39;t think of ?<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
&gt; <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
&gt;<br>
&gt; Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
&gt; Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
&gt; Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
<br>_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">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>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br></blockquote></div>