View Revisions: Issue #542

Summary 0000542: pgpool service will not come up after failover
Revision 2019-09-07 06:48 by t-ishii
Description We have 2 node Postgres 9.6.7 cluster with streaming replication. Pgpool is managed by our cluster as a managed resource and therefore has only one instance running.

We have seen cases where the machine that has Postgres master and pgpool is shutdown, Postgres on the other machine will assume the role of master. The cluster also attempts to start pgpool, but pgpool service fail to start.

In such a case postgres database is accessed with port 5432 but pgpool does not come up and we cannot access the database with port 9999. I do not know why, but at some point the cluster manages to bring up pgpool. Attached please find the log messages generated when I ran pgpool in debug mode.

172.18.255.42 is the down server
172.18.255.41 is the active server that pgpool does not come up

2019-09-01 15:59 is the time the cluster managed to bring up pgpool

Your help is most needed.
Revision 2019-09-02 16:53 by avi
Description We have 2 node Postgres 9.6.7 cluster with streaming replication. Pgpool is managed by our cluster as a managed resource and therefore has only one instance running.

We have seen cases where the machine that has Postgres master and pgpool is shutdown, Postgres on the other machine will assume the role of master. The cluster also attempts to start pgpool, but pgpool service fail to start.

In such a case postgres database is accessed with port 5432 but pgpool does not come up and we cannot access the database with port 9999. I do not know why, but at some point the cluster manages to bring up pgpool. Attached please find the log messages generated when I ran pgpool in debug mode.

172.18.255.42 is the down server
172.18.255.41 is the active server that pgpool does not come up

2019-09-01 15:59 is the time the cluster managed to bring up pgpool

Your help is most needed.