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 con
Hi Oliver
> pgsql(pgsql)[61018]:2014/09/18_13:36:41 WARNING: PostgreSQL template1
> isn't running
> pgsql(pgsql)[61018]:2014/09/18_13:36:41 WARNING: Connection error
> (connection to the server went bad and the
> session was not interactive) occurred while executing the psql command.
I
Okay, I've tried your suggestions but unfortunately it didn't make any
difference. Please also note that I'm running PostgreSQL 9.3.5.
--
View this message in context:
http://linux-ha.996297.n3.nabble.com/Unable-to-start-any-node-of-pgsql-Master-Slave-Cluster-tp15816p15822.html
Sent from the Li
I'm sorry.
restart_on_promote is a parameter of pgsql RA.
# pcs resource update pgsql restart_on_promote=false
--
Regards,
Takehiro Matsushima
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
Se
> Change "restart_on_promote" value to "false".
How? :)
--
View this message in context:
http://linux-ha.996297.n3.nabble.com/Unable-to-start-any-node-of-pgsql-Master-Slave-Cluster-tp15816p15820.html
Sent from the Linux-HA mailing list archive at Nabble.com.
__
Hi,
I've faced similer problem, with PostgreSQL 9.3.3.
(I know it fixed on PostgreSQL 9.3.4.)
You can avoid if this problem is same as mine. Try following
1. Change "restart_on_promote" value to "false".
2. Stop pacemaker.
3. Remove once "recovery.conf".
4. Start PostgreSQL manually(It runs as
I've monitored the cluster log and the running processes while the script
containing
rm -f /var/lib/pgsql/9.3/data/recovery.conf
rm -f /var/lib/pgsql/9.3/data/ra_tmp/PGSQL.lock
crm_attribute -l reboot -N $(uname -n) -n "pgsql-data-status" -v "LATEST"
crm_attribute -l reboot -N $(uname -n) -n "
CIB Dump:
I'm currently a bit struggling with setting up a PostgreSQL 9.3 HA
Master/Slave Cluster using CentOS 7 (Corosync 2 and Pacemaker 1.1.10).
Please note that I've deliberately stopped node2 currently in order to keep
the scenario simpler (I hope).
After starting the cluster on node1, crm_mon shows t
