I have meet the similar issue when the postgres is not stopped normally.
You could run pg_controldata to check if your postgres status is
shutdown/shutdown in recovery.
I change the /usr/lib/ocf/resource.d/heartbeat/pgsqlms to avoid this problem:
elsif ( $pgisready_rc == 2 ) {
# The instance
Thomas,
Hi Honza
On 4/6/18 10:59 AM, Jan Friesse wrote:
Thomas Lamprecht napsal(a):
Am 03/09/2018 um 05:26 PM schrieb Jan Friesse:
I've tested it too and yes, you are 100% right. Bug is there and it's
pretty easy to reproduce when node with lowest nodeid is paused. It's
slightly harder
I am having issues with my PAF setup. I am new to Postgres and have setup the
cluster as seen below.
I am getting this error when trying to start my cluster resources.
Master/Slave Set: pgsql-ha [pgsqld]
pgsqld (ocf::heartbeat:pgsqlms): FAILED dcmilphlum224 (unmanaged)
On 04/23/2018 08:09 PM, Andrew Edenburn wrote:
> I am having issues with my PAF setup. I am new to Postgres and have setup the
> cluster as seen below.
>
> I am getting this error when trying to start my cluster resources.
>
>
>
> Master/Slave Set: pgsql-ha [pgsqld]
>
> pgsqld
Hi Honza
On 4/6/18 10:59 AM, Jan Friesse wrote:
> Thomas Lamprecht napsal(a):
>> Am 03/09/2018 um 05:26 PM schrieb Jan Friesse:
>>> I've tested it too and yes, you are 100% right. Bug is there and it's
>>> pretty easy to reproduce when node with lowest nodeid is paused. It's
>>> slightly harder
I'm sorry I missed that.
The log after deleting corosync.conf states:
"I, [2018-04-19T23:59:15.690007 #19357] INFO -- : Running:
/usr/sbin/corosync-cmapctl totem.cluster_name\n",
"I, [2018-04-19T23:59:15.690021 #19357] INFO -- : CIB USER:
hacluster, groups: \n",
"D,