<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">In talking with andreask from IRC, I miss understood the need to include the op monitor. I figured it was pulled from the resource script by default.<div><br></div><div>I used pcs to add the new attributes and one was then promoted to master </div><div><br></div><div>pcs resource add_operation PGSQL monitor interval=5s role=Master</div><div>pcs resource add_operation PGSQL monitor interval=7s</div><div><br></div><div>v/r</div><div><br></div><div>STEVE</div><div><br></div><div>On Mar 27, 2013, at 7:08 AM, Steven Bambling <<a href="mailto:smbambling@arin.net">smbambling@arin.net</a>> wrote:</div><div><div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html charset=us-ascii"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div>I've built and installed the lastest resource-agents from github on Centos 6 and configured two resources <div><div><br></div><div>1 primitive PGVIP:</div><div>pcs resource create PGVIP ocf:heartbeat:IPaddr2 ip=10.1.22.48 cidr_netmask=25 op monitor interval=1</div><div><br></div><div>Before setting up the PGSQL resource I manually configured sync/streaming replication on the three nodes with <a href="http://p1.example.com/">p1.example.com</a> as the master and verified that replication was working. I think removed the synchronous_standby_name from my postgresql.conf and stop all postgres services on all nodes</div><div><br></div><div>1 master/slave PGSQL: -- I've the resource to use sync replication. Also I am using PGSQL 9.2.3</div><div><br></div><div>pcs resource create PGSQL ocf:heartbeat:pgsql params pgctl="/usr/pgsql-9.2/bin/pg_ctl" pgdata="/var/lib/pgsql/9.2/data" config="/var/lib/pgsql/9.2/data/postgresql.conf" stop_escalate="5"<b> rep_mode="sync" </b>node_list="<a href="http://p1.example.com/">p1.example.com</a> p2.<a href="http://example.com/">example.com</a> p3.<a href="http://example.com/">example.com</a>" restore_command='cp /var/lib/pgsql/9.2/archive/%f "%p"' master_ip="10.1.22.48" repuser="postgres" restart_on_promote="true" tmpdir="/var/lib/pgsql/9.2/tmpdir" xlog_check_count="3" crm_attr_timeout="5" check_wal_receiver="true" --master</div><div><br></div><div>I'm able to successfully get all the nodes in the cluster started and the PGVIP resource starts on the 1st node and the PGSQL:[012] resource start on each node in the cluster. The one thing I don't understand is why none of the slaves is taking over the master role.</div></div><div><br></div><div>Also how would I go about force promoting one of the slaves into the master role via the PCS command line utility. </div><div><br></div><div>v/r</div><div><br></div><div>STEVE</div></div>_______________________________________________<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">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br><br>Project Home: http://www.clusterlabs.org<br>Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf<br>Bugs: http://bugs.clusterlabs.org<br></blockquote></div><br></div></body></html>