Re: Unable to start any node of pgsql Master/Slave Cluster

Hi,

I am also in same trouble, I need a little help.
 
I have  set-up two node(node1 & node2) initial postgres Master at node1 &
standby on other node. Installed required cluster tool & configuration on
both node.
But pgsql resource agent stating both  postgres cluster in recovery mode. I
have confirmed my replication set-up working as expected(script attached
with this post). 


Any help is appreciated. 
Thank you.

=============================
Environment :
=============================
OS : Cent-OS x86_64
RMP installed:
cman-3.0.12.1-59.el6.x86_64
pacemaker-cluster-libs-1.1.10-14.el6.x86_64
pacemaker-1.1.10-14.el6.x86_64
pacemaker-libs-1.1.10-14.el6.x86_64
pacemaker-cli-1.1.10-14.el6.x86_64
corosynclib-1.4.1-17.el6.x86_64
corosync-1.4.1-17.el6.x86_64

STATUS & CONFIGURATION :
=============================
1. crm_mon -Afr -1 output:
=============================
-------------START:: crm_mon -Afr -1
output-------------------------------------
Last updated: Wed Oct  8 16:34:02 2014
Last change: Wed Oct  8 16:22:56 2014 via crmd on node1
Stack: cman
Current DC: node1 - partition with quorum
Version: 1.1.10-14.el6-368c726
2 Nodes configured
4 Resources configured


Online: [ node1 node2 ]

Full list of resources:

 Resource Group: master-group
     vip-master	(ocf::heartbeat:IPaddr2):	Stopped 
     vip-rep	(ocf::heartbeat:IPaddr2):	Stopped 
 Master/Slave Set: msPostgresql [pgsql]
     Slaves: [ node1 node2 ]

Node Attributes:
* Node node1:
    + master-pgsql                    	: -INFINITY 
    + pgsql-data-status               	: DISCONNECT
* Node node2:
    + master-pgsql                    	: -INFINITY 
    + pgsql-data-status               	: DISCONNECT
    + pgsql-status                    	: HS:alone  

Migration summary:
* Node node1: 
* Node node2: 

Failed actions:
    pgsql_monitor_0 on node1 'unknown error' (1): call=72, status=Timed Out, 
	last-rc-change='Wed Oct  8 16:22:56 2014', queued=60002ms, exec=0ms
-------------END:: crm_mon -Afr -1
output------------------------------------------

=============================
2. crm configure show output:
=============================
-------------START:: crm configure show
output------------------------------------------

node node1 \
	attributes pgsql-data-status=DISCONNECT
node node2 \
	attributes pgsql-data-status=DISCONNECT
primitive pgsql pgsql \
	params pgctl="/usr/pgsql-9.3/bin/pg_ctl" psql="/usr/pgsql-9.3/bin/psql"
config="/var/lib/pgsql/data/postgresql.conf" pgdata="/var/lib/pgsql/data"
start_opt="-p 5432" tmpdir="/var/lib/pgsql/tmpdir" rep_mode=sync
node_list="node1 node2" restore_command="scp node1:/var/lib/pgsql/arc/%f %p"
primary_conninfo_opt="keepalives_idle=60 keepalives_interval=5
keepalives_count=5" master_ip=192.168.2.3 stop_escalate=0
restart_on_promote=true xlog_check_count=3 crm_attr_timeout=5 \
	op start interval=0s on-fail=restart timeout=60s \
	op monitor interval=4s on-fail=restart timeout=60s \
	op monitor interval=3s on-fail=restart role=Master timeout=60s \
	op promote interval=0s on-fail=restart timeout=60s \
	op demote interval=0s on-fail=stop timeout=60s \
	op stop interval=0s on-fail=block timeout=60s \
	op notify interval=0s timeout=60s
primitive vip-master IPaddr2 \
	params ip=192.168.0.3 nic=eth0 cidr_netmask=24 \
	op start interval=0s on-fail=restart timeout=60s \
	op monitor interval=10s on-fail=restart timeout=60s \
	op stop interval=0s on-fail=block timeout=60s
primitive vip-rep IPaddr2 \
	params ip=192.168.2.3 nic=eth2 cidr_netmask=24 \
	op start interval=0s on-fail=stop timeout=60s \
	op monitor interval=10s on-fail=restart timeout=60s \
	op stop interval=0s on-fail=ignore timeout=60s \
	meta migration-threshold=0
group master-group vip-master vip-rep
ms msPostgresql pgsql \
	meta master-max=1 master-node-max=1 clone-max=2 clone-node-max=1
notify=true
colocation colocation-master-group-msPostgresql-INFINITY inf:
master-group:Started msPostgresql:Master
order order-msPostgresql-master-group-0 0: msPostgresql:demote
master-group:stop symmetrical=false
order order-msPostgresql-master-group-INFINITY inf: msPostgresql:promote
master-group:start symmetrical=false
property cib-bootstrap-options: \
	dc-version=1.1.10-14.el6-368c726 \
	cluster-infrastructure=cman \
	no-quorum-policy=ignore \
	stonith-enabled=false \
	last-lrm-refresh=1412765576
rsc_defaults rsc_defaults-options: \
	resource-stickiness=INFINITY \
	migration-threshold=1
-------------END:: crm configure show
output------------------------------------------

====================================================
3. Script attached to create Postgres replication
===================================================
PFA.
replication_remote.sh
<http://linux-ha.996297.n3.nabble.com/file/n15847/replication_remote.sh>  
====================================================
4. corosync.conf & cluster.conf attached
===================================================
PFA

cluster.conf <http://linux-ha.996297.n3.nabble.com/file/n15847/cluster.conf>  

corosync.conf
<http://linux-ha.996297.n3.nabble.com/file/n15847/corosync.conf>  


Regards,
Amul Sul



--
View this message in context: http://linux-ha.996297.n3.nabble.com/Unable-to-start-any-node-of-pgsql-Master-Slave-Cluster-tp15816p15847.html
Sent from the Linux-HA mailing list archive at Nabble.com.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems