2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11630]: [1-1] 2019-08-27 16:44:24: pid 11630: LOG: Backend status file /tmp/pgpool_status does not exist 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11630]: [2-1] 2019-08-27 16:44:24: pid 11630: LOG: waiting for watchdog to initialize 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [2-1] 2019-08-27 16:44:24: pid 11631: LOG: setting the local watchdog node name to "lcm-34-189.dev.lcm.local:9999 Linux lcm-34-189.dev.lcm.local" 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [3-1] 2019-08-27 16:44:24: pid 11631: LOG: watchdog cluster is configured with 2 remote nodes 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [4-1] 2019-08-27 16:44:24: pid 11631: LOG: watchdog remote node:0 on 10.198.34.188:9000 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [5-1] 2019-08-27 16:44:24: pid 11631: LOG: watchdog remote node:1 on 10.198.34.190:9000 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [6-1] 2019-08-27 16:44:24: pid 11631: LOG: interface monitoring is disabled in watchdog 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [7-1] 2019-08-27 16:44:24: pid 11631: LOG: watchdog node state changed from [DEAD] to [LOADING] 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [8-1] 2019-08-27 16:44:24: pid 11631: LOG: new outbound connection to 10.198.34.188:9000 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [9-1] 2019-08-27 16:44:24: pid 11631: LOG: setting the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" as watchdog cluster master 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [10-1] 2019-08-27 16:44:24: pid 11631: LOG: watchdog node state changed from [LOADING] to [INITIALIZING] 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [11-1] 2019-08-27 16:44:24: pid 11631: LOG: new watchdog node connection is received from "10.198.34.188:22451" 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [12-1] 2019-08-27 16:44:24: pid 11631: LOG: new node joined the cluster hostname:"lcm-34-188.dev.lcm.local" port:9000 pgpool_port:9999 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [13-1] 2019-08-27 16:44:24: pid 11631: LOG: new watchdog node connection is received from "10.198.34.190:4494" 2019-08-27T16:44:24+00:00 lcm-34-189 pgpool[11631]: [14-1] 2019-08-27 16:44:24: pid 11631: LOG: new node joined the cluster hostname:"lcm-34-190.dev.lcm.local" port:9000 pgpool_port:9999 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11631]: [15-1] 2019-08-27 16:44:25: pid 11631: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY] 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11631]: [16-1] 2019-08-27 16:44:25: pid 11631: LOG: successfully joined the watchdog cluster as standby node 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11631]: [16-2] 2019-08-27 16:44:25: pid 11631: DETAIL: our join coordinator request is accepted by cluster leader node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11630]: [3-1] 2019-08-27 16:44:25: pid 11630: LOG: watchdog process is initialized 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11631]: [17-1] 2019-08-27 16:44:25: pid 11631: LOG: new IPC connection received 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11630]: [4-1] 2019-08-27 16:44:25: pid 11630: LOG: we have joined the watchdog cluster as STANDBY node 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11630]: [4-2] 2019-08-27 16:44:25: pid 11630: DETAIL: syncing the backend states from the MASTER watchdog node 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11631]: [18-1] 2019-08-27 16:44:25: pid 11631: LOG: new IPC connection received 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11631]: [19-1] 2019-08-27 16:44:25: pid 11631: LOG: new IPC connection received 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11631]: [20-1] 2019-08-27 16:44:25: pid 11631: LOG: received the get data request from local pgpool-II on IPC interface 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11631]: [21-1] 2019-08-27 16:44:25: pid 11631: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to master watchdog node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11631]: [21-2] 2019-08-27 16:44:25: pid 11631: DETAIL: waiting for the reply... 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11634]: [4-1] 2019-08-27 16:44:25: pid 11634: LOG: 3 watchdog nodes are configured for lifecheck 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11634]: [5-1] 2019-08-27 16:44:25: pid 11634: LOG: watchdog nodes ID:0 Name:"lcm-34-189.dev.lcm.local:9999 Linux lcm-34-189.dev.lcm.local" 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11634]: [5-2] 2019-08-27 16:44:25: pid 11634: DETAIL: Host:"lcm-34-189.dev.lcm.local" WD Port:9000 pgpool-II port:9999 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11634]: [6-1] 2019-08-27 16:44:25: pid 11634: LOG: watchdog nodes ID:1 Name:"lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11634]: [6-2] 2019-08-27 16:44:25: pid 11634: DETAIL: Host:"10.198.34.188" WD Port:9000 pgpool-II port:9999 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11634]: [7-1] 2019-08-27 16:44:25: pid 11634: LOG: watchdog nodes ID:2 Name:"lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11634]: [7-2] 2019-08-27 16:44:25: pid 11634: DETAIL: Host:"10.198.34.190" WD Port:9000 pgpool-II port:9999 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11630]: [5-1] 2019-08-27 16:44:25: pid 11630: LOG: master watchdog node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" returned status for 3 backend nodes 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11630]: [6-1] 2019-08-27 16:44:25: pid 11630: LOG: Setting up socket for 0.0.0.0:9999 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11630]: [7-1] 2019-08-27 16:44:25: pid 11630: LOG: Setting up socket for :::9999 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11630]: [8-1] 2019-08-27 16:44:25: pid 11630: LOG: pgpool-II successfully started. version 4.0.4 (torokiboshi) 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11630]: [9-1] 2019-08-27 16:44:25: pid 11630: LOG: node status[0]: 0 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11630]: [10-1] 2019-08-27 16:44:25: pid 11630: LOG: node status[1]: 0 2019-08-27T16:44:25+00:00 lcm-34-189 pgpool[11630]: [11-1] 2019-08-27 16:44:25: pid 11630: LOG: node status[2]: 0 2019-08-27T16:44:26+00:00 lcm-34-189 pgpool[11637]: [8-1] 2019-08-27 16:44:26: pid 11637: LOG: creating watchdog heartbeat receive socket. 2019-08-27T16:44:26+00:00 lcm-34-189 pgpool[11637]: [8-2] 2019-08-27 16:44:26: pid 11637: DETAIL: set SO_REUSEPORT 2019-08-27T16:44:26+00:00 lcm-34-189 pgpool[11638]: [8-1] 2019-08-27 16:44:26: pid 11638: LOG: creating socket for sending heartbeat 2019-08-27T16:44:26+00:00 lcm-34-189 pgpool[11638]: [8-2] 2019-08-27 16:44:26: pid 11638: DETAIL: set SO_REUSEPORT 2019-08-27T16:44:26+00:00 lcm-34-189 pgpool[11635]: [8-1] 2019-08-27 16:44:26: pid 11635: LOG: creating watchdog heartbeat receive socket. 2019-08-27T16:44:26+00:00 lcm-34-189 pgpool[11635]: [8-2] 2019-08-27 16:44:26: pid 11635: DETAIL: set SO_REUSEPORT 2019-08-27T16:44:26+00:00 lcm-34-189 pgpool[11636]: [8-1] 2019-08-27 16:44:26: pid 11636: LOG: creating socket for sending heartbeat 2019-08-27T16:44:26+00:00 lcm-34-189 pgpool[11636]: [8-2] 2019-08-27 16:44:26: pid 11636: DETAIL: set SO_REUSEPORT 2019-08-27T16:44:35+00:00 lcm-34-189 pgpool[11631]: [22-1] 2019-08-27 16:44:35: pid 11631: LOG: new outbound connection to 10.198.34.190:9000 2019-08-31T16:32:37+00:00 lcm-34-189 pgpool[11673]: [8-1] 2019-08-31 16:32:37: pid 11673: LOG: failed to connect to PostgreSQL server on "10.198.34.188:5432", timed out 2019-08-31T16:32:37+00:00 lcm-34-189 pgpool[11673]: [9-1] 2019-08-31 16:32:37: pid 11673: ERROR: failed to make persistent db connection 2019-08-31T16:32:37+00:00 lcm-34-189 pgpool[11673]: [9-2] 2019-08-31 16:32:37: pid 11673: DETAIL: connection to host:"10.198.34.188:5432" failed 2019-08-31T16:32:37+00:00 lcm-34-189 pgpool[11673]: [10-1] 2019-08-31 16:32:37: pid 11673: LOG: health check retrying on DB node: 0 (round:1) 2019-08-31T16:32:37+00:00 lcm-34-189 pgpool[11672]: [8-1] 2019-08-31 16:32:37: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:32:37+00:00 lcm-34-189 pgpool[11672]: [8-2] 2019-08-31 16:32:37: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:32:47+00:00 lcm-34-189 pgpool[11672]: [9-1] 2019-08-31 16:32:47: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:32:47+00:00 lcm-34-189 pgpool[11672]: [9-2] 2019-08-31 16:32:47: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:32:48+00:00 lcm-34-189 pgpool[11673]: [11-1] 2019-08-31 16:32:48: pid 11673: LOG: failed to connect to PostgreSQL server on "10.198.34.188:5432", timed out 2019-08-31T16:32:48+00:00 lcm-34-189 pgpool[11673]: [12-1] 2019-08-31 16:32:48: pid 11673: ERROR: failed to make persistent db connection 2019-08-31T16:32:48+00:00 lcm-34-189 pgpool[11673]: [12-2] 2019-08-31 16:32:48: pid 11673: DETAIL: connection to host:"10.198.34.188:5432" failed 2019-08-31T16:32:48+00:00 lcm-34-189 pgpool[11673]: [13-1] 2019-08-31 16:32:48: pid 11673: LOG: health check retrying on DB node: 0 (round:2) 2019-08-31T16:32:57+00:00 lcm-34-189 pgpool[11672]: [10-1] 2019-08-31 16:32:57: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:32:57+00:00 lcm-34-189 pgpool[11672]: [10-2] 2019-08-31 16:32:57: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:32:59+00:00 lcm-34-189 pgpool[11673]: [14-1] 2019-08-31 16:32:59: pid 11673: LOG: failed to connect to PostgreSQL server on "10.198.34.188:5432", timed out 2019-08-31T16:32:59+00:00 lcm-34-189 pgpool[11673]: [15-1] 2019-08-31 16:32:59: pid 11673: ERROR: failed to make persistent db connection 2019-08-31T16:32:59+00:00 lcm-34-189 pgpool[11673]: [15-2] 2019-08-31 16:32:59: pid 11673: DETAIL: connection to host:"10.198.34.188:5432" failed 2019-08-31T16:32:59+00:00 lcm-34-189 pgpool[11673]: [16-1] 2019-08-31 16:32:59: pid 11673: LOG: health check retrying on DB node: 0 (round:3) 2019-08-31T16:33:06+00:00 lcm-34-189 pgpool[11673]: [17-1] 2019-08-31 16:33:06: pid 11673: LOG: failed to connect to PostgreSQL server on "10.198.34.188:5432", getsockopt() detected error "No route to host" 2019-08-31T16:33:06+00:00 lcm-34-189 pgpool[11673]: [18-1] 2019-08-31 16:33:06: pid 11673: ERROR: failed to make persistent db connection 2019-08-31T16:33:06+00:00 lcm-34-189 pgpool[11673]: [18-2] 2019-08-31 16:33:06: pid 11673: DETAIL: connection to host:"10.198.34.188:5432" failed 2019-08-31T16:33:06+00:00 lcm-34-189 pgpool[11673]: [19-1] 2019-08-31 16:33:06: pid 11673: LOG: health check failed on node 0 (timeout:0) 2019-08-31T16:33:06+00:00 lcm-34-189 pgpool[11673]: [20-1] 2019-08-31 16:33:06: pid 11673: LOG: received degenerate backend request for node_id: 0 from pid [11673] 2019-08-31T16:33:06+00:00 lcm-34-189 pgpool[11631]: [23-1] 2019-08-31 16:33:06: pid 11631: LOG: new IPC connection received 2019-08-31T16:33:06+00:00 lcm-34-189 pgpool[11631]: [24-1] 2019-08-31 16:33:06: pid 11631: LOG: failover request from local pgpool-II node received on IPC interface is forwarded to master watchdog node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:33:06+00:00 lcm-34-189 pgpool[11631]: [24-2] 2019-08-31 16:33:06: pid 11631: DETAIL: waiting for the reply... 2019-08-31T16:33:07+00:00 lcm-34-189 pgpool[11672]: [11-1] 2019-08-31 16:33:07: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:33:07+00:00 lcm-34-189 pgpool[11672]: [11-2] 2019-08-31 16:33:07: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:33:11+00:00 lcm-34-189 pgpool[11631]: [25-1] 2019-08-31 16:33:11: pid 11631: LOG: remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is not replying.. 2019-08-31T16:33:11+00:00 lcm-34-189 pgpool[11631]: [25-2] 2019-08-31 16:33:11: pid 11631: DETAIL: marking the node as lost 2019-08-31T16:33:11+00:00 lcm-34-189 pgpool[11631]: [26-1] 2019-08-31 16:33:11: pid 11631: LOG: remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is lost 2019-08-31T16:33:11+00:00 lcm-34-189 pgpool[11631]: [27-1] 2019-08-31 16:33:11: pid 11631: LOG: watchdog cluster has lost the coordinator node 2019-08-31T16:33:11+00:00 lcm-34-189 pgpool[11631]: [28-1] 2019-08-31 16:33:11: pid 11631: LOG: unassigning the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" from watchdog cluster master 2019-08-31T16:33:11+00:00 lcm-34-189 pgpool[11631]: [29-1] 2019-08-31 16:33:11: pid 11631: LOG: We have lost the cluster master node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:33:11+00:00 lcm-34-189 pgpool[11631]: [30-1] 2019-08-31 16:33:11: pid 11631: LOG: watchdog node state changed from [STANDBY] to [JOINING] 2019-08-31T16:33:11+00:00 lcm-34-189 pgpool[11673]: [21-1] 2019-08-31 16:33:11: pid 11673: LOG: degenerate backend request for 1 node(s) from pid [11673] is canceled by other pgpool 2019-08-31T16:33:11+00:00 lcm-34-189 pgpool[11631]: [31-1] 2019-08-31 16:33:11: pid 11631: LOG: watchdog node state changed from [JOINING] to [INITIALIZING] 2019-08-31T16:33:12+00:00 lcm-34-189 pgpool[11631]: [32-1] 2019-08-31 16:33:12: pid 11631: LOG: watchdog node state changed from [INITIALIZING] to [STANDING FOR MASTER] 2019-08-31T16:33:12+00:00 lcm-34-189 pgpool[11631]: [33-1] 2019-08-31 16:33:12: pid 11631: LOG: watchdog node state changed from [STANDING FOR MASTER] to [MASTER] 2019-08-31T16:33:12+00:00 lcm-34-189 pgpool[11631]: [34-1] 2019-08-31 16:33:12: pid 11631: LOG: I am announcing my self as master/coordinator watchdog node 2019-08-31T16:33:12+00:00 lcm-34-189 pgpool[11631]: [35-1] 2019-08-31 16:33:12: pid 11631: LOG: I am the cluster leader node 2019-08-31T16:33:12+00:00 lcm-34-189 pgpool[11631]: [35-2] 2019-08-31 16:33:12: pid 11631: DETAIL: our declare coordinator message is accepted by all nodes 2019-08-31T16:33:12+00:00 lcm-34-189 pgpool[11631]: [36-1] 2019-08-31 16:33:12: pid 11631: LOG: setting the local node "lcm-34-189.dev.lcm.local:9999 Linux lcm-34-189.dev.lcm.local" as watchdog cluster master 2019-08-31T16:33:12+00:00 lcm-34-189 pgpool[11631]: [37-1] 2019-08-31 16:33:12: pid 11631: LOG: I am the cluster leader node but we do not have enough nodes in cluster 2019-08-31T16:33:12+00:00 lcm-34-189 pgpool[11631]: [37-2] 2019-08-31 16:33:12: pid 11631: DETAIL: waiting for the quorum to start escalation process 2019-08-31T16:33:12+00:00 lcm-34-189 pgpool[11630]: [12-1] 2019-08-31 16:33:12: pid 11630: LOG: Pgpool-II parent process received watchdog quorum change signal from watchdog 2019-08-31T16:33:12+00:00 lcm-34-189 pgpool[11631]: [38-1] 2019-08-31 16:33:12: pid 11631: LOG: new IPC connection received 2019-08-31T16:33:12+00:00 lcm-34-189 pgpool[11631]: [39-1] 2019-08-31 16:33:12: pid 11631: LOG: new IPC connection received 2019-08-31T16:33:13+00:00 lcm-34-189 pgpool[11631]: [40-1] 2019-08-31 16:33:13: pid 11631: LOG: adding watchdog node "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" to the standby list 2019-08-31T16:33:13+00:00 lcm-34-189 pgpool[11631]: [41-1] 2019-08-31 16:33:13: pid 11631: LOG: quorum found 2019-08-31T16:33:13+00:00 lcm-34-189 pgpool[11631]: [41-2] 2019-08-31 16:33:13: pid 11631: DETAIL: starting escalation process 2019-08-31T16:33:13+00:00 lcm-34-189 pgpool[11631]: [42-1] 2019-08-31 16:33:13: pid 11631: LOG: escalation process started with PID:21171 2019-08-31T16:33:13+00:00 lcm-34-189 pgpool[21171]: [42-1] 2019-08-31 16:33:13: pid 21171: LOG: watchdog: escalation started 2019-08-31T16:33:13+00:00 lcm-34-189 pgpool[11630]: [13-1] 2019-08-31 16:33:13: pid 11630: LOG: Pgpool-II parent process received watchdog quorum change signal from watchdog 2019-08-31T16:33:13+00:00 lcm-34-189 pgpool[11631]: [43-1] 2019-08-31 16:33:13: pid 11631: LOG: new IPC connection received 2019-08-31T16:33:13+00:00 lcm-34-189 pgpool[11630]: [14-1] 2019-08-31 16:33:13: pid 11630: LOG: watchdog cluster now holds the quorum 2019-08-31T16:33:13+00:00 lcm-34-189 pgpool[11630]: [14-2] 2019-08-31 16:33:13: pid 11630: DETAIL: updating the state of quarantine backend nodes 2019-08-31T16:33:13+00:00 lcm-34-189 pgpool[11631]: [44-1] 2019-08-31 16:33:13: pid 11631: LOG: new IPC connection received 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21174]: + FAILED_NODE_ID= 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21175]: esc.sh: Escalation script being called, delegateIP being called !!!!!!!!!!!!!!!!!! 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21174]: + FAILED_NODE_HOST= 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21174]: + FAILED_NODE_PORT= 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21174]: + FAILED_NODE_PGDATA= 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21174]: + NEW_MASTER_NODE_ID= 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21174]: + NEW_MASTER_NODE_HOST= 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21174]: + OLD_MASTER_NODE_ID= 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21174]: + OLD_PRIMARY_NODE_ID= 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21174]: + NEW_MASTER_NODE_PORT= 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21174]: + NEW_MASTER_NODE_PGDATA= 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21174]: + PGHOME=/opt/vmware/vpostgres/9.6 2019-08-31T16:33:13+00:00 lcm-34-189 logger[21174]: + logger -i -p local1.info esc.sh: Escalation script being called, delegateIP being called '!!!!!!!!!!!!!!!!!!' 2019-08-31T16:33:13+00:00 lcm-34-189 pgpool[21171]: [43-1] 2019-08-31 16:33:13: pid 21171: LOG: watchdog escalation successful 2019-08-31T16:33:13+00:00 lcm-34-189 pgpool[11631]: [45-1] 2019-08-31 16:33:13: pid 11631: LOG: watchdog escalation process with pid: 21171 exit with SUCCESS. 2019-08-31T16:33:17+00:00 lcm-34-189 pgpool[11672]: [12-1] 2019-08-31 16:33:17: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:33:17+00:00 lcm-34-189 pgpool[11672]: [12-2] 2019-08-31 16:33:17: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:33:26+00:00 lcm-34-189 pgpool[11673]: [22-1] 2019-08-31 16:33:26: pid 11673: LOG: failed to connect to PostgreSQL server on "10.198.34.188:5432", timed out 2019-08-31T16:33:26+00:00 lcm-34-189 pgpool[11673]: [23-1] 2019-08-31 16:33:26: pid 11673: ERROR: failed to make persistent db connection 2019-08-31T16:33:26+00:00 lcm-34-189 pgpool[11673]: [23-2] 2019-08-31 16:33:26: pid 11673: DETAIL: connection to host:"10.198.34.188:5432" failed 2019-08-31T16:33:26+00:00 lcm-34-189 pgpool[11673]: [24-1] 2019-08-31 16:33:26: pid 11673: LOG: health check retrying on DB node: 0 (round:1) 2019-08-31T16:33:27+00:00 lcm-34-189 pgpool[11672]: [13-1] 2019-08-31 16:33:27: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:33:27+00:00 lcm-34-189 pgpool[11672]: [13-2] 2019-08-31 16:33:27: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:33:27+00:00 lcm-34-189 pgpool[11673]: [25-1] 2019-08-31 16:33:27: pid 11673: LOG: failed to connect to PostgreSQL server on "10.198.34.188:5432", getsockopt() detected error "No route to host" 2019-08-31T16:33:27+00:00 lcm-34-189 pgpool[11673]: [26-1] 2019-08-31 16:33:27: pid 11673: ERROR: failed to make persistent db connection 2019-08-31T16:33:27+00:00 lcm-34-189 pgpool[11673]: [26-2] 2019-08-31 16:33:27: pid 11673: DETAIL: connection to host:"10.198.34.188:5432" failed 2019-08-31T16:33:27+00:00 lcm-34-189 pgpool[11673]: [27-1] 2019-08-31 16:33:27: pid 11673: LOG: health check retrying on DB node: 0 (round:2) 2019-08-31T16:33:30+00:00 lcm-34-189 pgpool[11673]: [28-1] 2019-08-31 16:33:30: pid 11673: LOG: failed to connect to PostgreSQL server on "10.198.34.188:5432", getsockopt() detected error "No route to host" 2019-08-31T16:33:30+00:00 lcm-34-189 pgpool[11673]: [29-1] 2019-08-31 16:33:30: pid 11673: ERROR: failed to make persistent db connection 2019-08-31T16:33:30+00:00 lcm-34-189 pgpool[11673]: [29-2] 2019-08-31 16:33:30: pid 11673: DETAIL: connection to host:"10.198.34.188:5432" failed 2019-08-31T16:33:30+00:00 lcm-34-189 pgpool[11673]: [30-1] 2019-08-31 16:33:30: pid 11673: LOG: health check retrying on DB node: 0 (round:3) 2019-08-31T16:33:37+00:00 lcm-34-189 pgpool[11672]: [14-1] 2019-08-31 16:33:37: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:33:37+00:00 lcm-34-189 pgpool[11672]: [14-2] 2019-08-31 16:33:37: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:33:41+00:00 lcm-34-189 pgpool[11673]: [31-1] 2019-08-31 16:33:41: pid 11673: LOG: failed to connect to PostgreSQL server on "10.198.34.188:5432", timed out 2019-08-31T16:33:41+00:00 lcm-34-189 pgpool[11673]: [32-1] 2019-08-31 16:33:41: pid 11673: ERROR: failed to make persistent db connection 2019-08-31T16:33:41+00:00 lcm-34-189 pgpool[11673]: [32-2] 2019-08-31 16:33:41: pid 11673: DETAIL: connection to host:"10.198.34.188:5432" failed 2019-08-31T16:33:41+00:00 lcm-34-189 pgpool[11673]: [33-1] 2019-08-31 16:33:41: pid 11673: LOG: health check failed on node 0 (timeout:0) 2019-08-31T16:33:41+00:00 lcm-34-189 pgpool[11673]: [34-1] 2019-08-31 16:33:41: pid 11673: LOG: received degenerate backend request for node_id: 0 from pid [11673] 2019-08-31T16:33:41+00:00 lcm-34-189 pgpool[11631]: [46-1] 2019-08-31 16:33:41: pid 11631: LOG: new IPC connection received 2019-08-31T16:33:41+00:00 lcm-34-189 pgpool[11631]: [47-1] 2019-08-31 16:33:41: pid 11631: LOG: watchdog received the failover command from local pgpool-II on IPC interface 2019-08-31T16:33:41+00:00 lcm-34-189 pgpool[11631]: [48-1] 2019-08-31 16:33:41: pid 11631: LOG: watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from local pgpool-II on IPC interface 2019-08-31T16:33:41+00:00 lcm-34-189 pgpool[11631]: [49-1] 2019-08-31 16:33:41: pid 11631: LOG: failover requires the majority vote, waiting for consensus 2019-08-31T16:33:41+00:00 lcm-34-189 pgpool[11631]: [49-2] 2019-08-31 16:33:41: pid 11631: DETAIL: failover request noted 2019-08-31T16:33:41+00:00 lcm-34-189 pgpool[11631]: [50-1] 2019-08-31 16:33:41: pid 11631: LOG: failover command [DEGENERATE_BACKEND_REQUEST] request from pgpool-II node "lcm-34-189.dev.lcm.local:9999 Linux lcm-34-189.dev.lcm.local" is queued, waiting for the confirmation from other nodes 2019-08-31T16:33:41+00:00 lcm-34-189 pgpool[11673]: [35-1] 2019-08-31 16:33:41: pid 11673: LOG: degenerate backend request for node_id: 0 from pid [11673], will be handled by watchdog, which is building consensus for request 2019-08-31T16:33:42+00:00 lcm-34-189 pgpool[11631]: [51-1] 2019-08-31 16:33:42: pid 11631: LOG: watchdog received the failover command from remote pgpool-II node "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" 2019-08-31T16:33:42+00:00 lcm-34-189 pgpool[11631]: [52-1] 2019-08-31 16:33:42: pid 11631: LOG: watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local 2019-08-31T16:33:42+00:00 lcm-34-189 pgpool[11631]: [53-1] 2019-08-31 16:33:42: pid 11631: LOG: we have got the consensus to perform the failover 2019-08-31T16:33:42+00:00 lcm-34-189 pgpool[11631]: [53-2] 2019-08-31 16:33:42: pid 11631: DETAIL: 2 node(s) voted in the favor 2019-08-31T16:33:42+00:00 lcm-34-189 pgpool[11631]: [54-1] 2019-08-31 16:33:42: pid 11631: LOG: received degenerate backend request for node_id: 0 from pid [11631] 2019-08-31T16:33:42+00:00 lcm-34-189 pgpool[11630]: [15-1] 2019-08-31 16:33:42: pid 11630: LOG: Pgpool-II parent process has received failover request 2019-08-31T16:33:42+00:00 lcm-34-189 pgpool[11631]: [55-1] 2019-08-31 16:33:42: pid 11631: LOG: new IPC connection received 2019-08-31T16:33:42+00:00 lcm-34-189 pgpool[11631]: [56-1] 2019-08-31 16:33:42: pid 11631: LOG: received the failover indication from Pgpool-II on IPC interface 2019-08-31T16:33:42+00:00 lcm-34-189 pgpool[11631]: [57-1] 2019-08-31 16:33:42: pid 11631: LOG: watchdog is informed of failover start by the main process 2019-08-31T16:33:42+00:00 lcm-34-189 pgpool[11630]: [16-1] 2019-08-31 16:33:42: pid 11630: LOG: starting degeneration. shutdown host 10.198.34.188(5432) 2019-08-31T16:33:42+00:00 lcm-34-189 pgpool[11630]: [17-1] 2019-08-31 16:33:42: pid 11630: LOG: Restart all children 2019-08-31T16:33:42+00:00 lcm-34-189 pgpool[11630]: [18-1] 2019-08-31 16:33:42: pid 11630: LOG: execute command: /usr/local/etc/failover.sh 0 10.198.34.188 5432 /db/data 1 10.198.34.189 0 0 5432 /db/data 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21203]: failover.sh: start: failed_node_id=0 old_primary_node_id=0 failed_host=10.198.34.188 new_master_host=10.198.34.189 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + FAILED_NODE_ID=0 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + FAILED_NODE_HOST=10.198.34.188 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + FAILED_NODE_PORT=5432 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + FAILED_NODE_PGDATA=/db/data 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + NEW_MASTER_NODE_ID=1 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + NEW_MASTER_NODE_HOST=10.198.34.189 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + OLD_MASTER_NODE_ID=0 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + OLD_PRIMARY_NODE_ID=0 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + NEW_MASTER_NODE_PORT=5432 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + NEW_MASTER_NODE_PGDATA=/db/data 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + PGHOME=/opt/vmware/vpostgres/9.6 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + VIDM_NETMASK=255.255.254.0 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + logger -i -p local1.info failover.sh: start: failed_node_id=0 old_primary_node_id=0 failed_host=10.198.34.188 new_master_host=10.198.34.189 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + '[' 0 -ne 0 ']' 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: + ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@10.198.34.188 2019-08-31T16:33:42+00:00 lcm-34-189 logger[21205]: Pseudo-terminal will not be allocated because stdin is not a terminal. 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: ssh: connect to host 10.198.34.188 port 22: No route to host 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: + logger -i -p local1.info failover.sh: ssh: postgres@10.198.34.189 pg_ctl promote 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21206]: failover.sh: ssh: postgres@10.198.34.189 pg_ctl promote 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: + ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@10.198.34.189 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: Pseudo-terminal will not be allocated because stdin is not a terminal. 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: Warning: Permanently added '10.198.34.189' (RSA) to the list of known hosts. 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: Welcome to SUSE Linux Enterprise Server 11 SP4 (x86_64) - Kernel \r (\l). 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: could not change directory to "/root": Permission denied 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: server promoting 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: + [[ 0 -ne 0 ]] 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: + logger -i -p local1.info failover.sh: end: new_master_node_id=1 started as the primary node 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21244]: failover.sh: end: new_master_node_id=1 started as the primary node 2019-08-31T16:33:43+00:00 lcm-34-189 pgpool[11630]: [19-1] 2019-08-31 16:33:43: pid 11630: LOG: find_primary_node_repeatedly: waiting for finding a primary node 2019-08-31T16:33:43+00:00 lcm-34-189 logger[21205]: + exit 0 2019-08-31T16:33:43+00:00 lcm-34-189 pgpool[11630]: [20-1] 2019-08-31 16:33:43: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:43+00:00 lcm-34-189 pgpool[11630]: [21-1] 2019-08-31 16:33:43: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:44+00:00 lcm-34-189 pgpool[11630]: [22-1] 2019-08-31 16:33:44: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:44+00:00 lcm-34-189 pgpool[11630]: [23-1] 2019-08-31 16:33:44: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:45+00:00 lcm-34-189 pgpool[11630]: [24-1] 2019-08-31 16:33:45: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:45+00:00 lcm-34-189 pgpool[11630]: [25-1] 2019-08-31 16:33:45: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:46+00:00 lcm-34-189 pgpool[11630]: [26-1] 2019-08-31 16:33:46: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:46+00:00 lcm-34-189 pgpool[11630]: [27-1] 2019-08-31 16:33:46: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:47+00:00 lcm-34-189 pgpool[11630]: [28-1] 2019-08-31 16:33:47: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:47+00:00 lcm-34-189 pgpool[11630]: [29-1] 2019-08-31 16:33:47: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:47+00:00 lcm-34-189 pgpool[11672]: [15-1] 2019-08-31 16:33:47: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:33:47+00:00 lcm-34-189 pgpool[11672]: [15-2] 2019-08-31 16:33:47: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:33:48+00:00 lcm-34-189 pgpool[11630]: [30-1] 2019-08-31 16:33:48: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:48+00:00 lcm-34-189 pgpool[11630]: [31-1] 2019-08-31 16:33:48: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:49+00:00 lcm-34-189 pgpool[11630]: [32-1] 2019-08-31 16:33:49: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:49+00:00 lcm-34-189 pgpool[11630]: [33-1] 2019-08-31 16:33:49: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:50+00:00 lcm-34-189 pgpool[11630]: [34-1] 2019-08-31 16:33:50: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:50+00:00 lcm-34-189 pgpool[11630]: [35-1] 2019-08-31 16:33:50: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:51+00:00 lcm-34-189 pgpool[11630]: [36-1] 2019-08-31 16:33:51: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:51+00:00 lcm-34-189 pgpool[11630]: [37-1] 2019-08-31 16:33:51: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:52+00:00 lcm-34-189 pgpool[11630]: [38-1] 2019-08-31 16:33:52: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:52+00:00 lcm-34-189 pgpool[11630]: [39-1] 2019-08-31 16:33:52: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:53+00:00 lcm-34-189 pgpool[11630]: [40-1] 2019-08-31 16:33:53: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:53+00:00 lcm-34-189 pgpool[11630]: [41-1] 2019-08-31 16:33:53: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:54+00:00 lcm-34-189 pgpool[11630]: [42-1] 2019-08-31 16:33:54: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:54+00:00 lcm-34-189 pgpool[11630]: [43-1] 2019-08-31 16:33:54: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:55+00:00 lcm-34-189 pgpool[11630]: [44-1] 2019-08-31 16:33:55: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:55+00:00 lcm-34-189 pgpool[11630]: [45-1] 2019-08-31 16:33:55: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:56+00:00 lcm-34-189 pgpool[11630]: [46-1] 2019-08-31 16:33:56: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:56+00:00 lcm-34-189 pgpool[11630]: [47-1] 2019-08-31 16:33:56: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:57+00:00 lcm-34-189 pgpool[11630]: [48-1] 2019-08-31 16:33:57: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:57+00:00 lcm-34-189 pgpool[11630]: [49-1] 2019-08-31 16:33:57: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:57+00:00 lcm-34-189 pgpool[11672]: [16-1] 2019-08-31 16:33:57: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:33:57+00:00 lcm-34-189 pgpool[11672]: [16-2] 2019-08-31 16:33:57: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:33:58+00:00 lcm-34-189 pgpool[11630]: [50-1] 2019-08-31 16:33:58: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:58+00:00 lcm-34-189 pgpool[11630]: [51-1] 2019-08-31 16:33:58: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:33:59+00:00 lcm-34-189 pgpool[11630]: [52-1] 2019-08-31 16:33:59: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:33:59+00:00 lcm-34-189 pgpool[11630]: [53-1] 2019-08-31 16:33:59: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:34:00+00:00 lcm-34-189 pgpool[11630]: [54-1] 2019-08-31 16:34:00: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:34:00+00:00 lcm-34-189 pgpool[11630]: [55-1] 2019-08-31 16:34:00: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:34:01+00:00 lcm-34-189 pgpool[11630]: [56-1] 2019-08-31 16:34:01: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:34:01+00:00 lcm-34-189 pgpool[11630]: [57-1] 2019-08-31 16:34:01: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:34:02+00:00 lcm-34-189 pgpool[11630]: [58-1] 2019-08-31 16:34:02: pid 11630: LOG: find_primary_node: standby node is 1 2019-08-31T16:34:02+00:00 lcm-34-189 pgpool[11630]: [59-1] 2019-08-31 16:34:02: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11630]: [60-1] 2019-08-31 16:34:03: pid 11630: LOG: find_primary_node: primary node is 1 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11630]: [61-1] 2019-08-31 16:34:03: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11630]: [62-1] 2019-08-31 16:34:03: pid 11630: LOG: starting follow degeneration. shutdown host 10.198.34.188(5432) 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11630]: [63-1] 2019-08-31 16:34:03: pid 11630: LOG: starting follow degeneration. shutdown host 10.198.34.190(5432) 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11630]: [64-1] 2019-08-31 16:34:03: pid 11630: LOG: failover: 2 follow backends have been degenerated 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11630]: [65-1] 2019-08-31 16:34:03: pid 11630: LOG: failover: set new primary node: 1 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11630]: [66-1] 2019-08-31 16:34:03: pid 11630: LOG: failover: set new master node: 1 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[21366]: [65-1] 2019-08-31 16:34:03: pid 21366: LOG: start triggering follow command. 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[21366]: [66-1] 2019-08-31 16:34:03: pid 21366: LOG: execute command: /usr/local/etc/follow_master.sh 0 10.198.34.188 5432 /db/data 1 0 10.198.34.189 0 5432 /db/data 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11672]: [17-1] 2019-08-31 16:34:03: pid 11672: LOG: trying to connect to PostgreSQL server on "10.198.34.188:5432" using INET socket 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11672]: [17-2] 2019-08-31 16:34:03: pid 11672: DETAIL: select() interrupted. retrying... 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11631]: [58-1] 2019-08-31 16:34:03: pid 11631: LOG: new IPC connection received 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11631]: [59-1] 2019-08-31 16:34:03: pid 11631: LOG: received the failover indication from Pgpool-II on IPC interface 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11631]: [60-1] 2019-08-31 16:34:03: pid 11631: LOG: watchdog is informed of failover end by the main process 2019-08-31T16:34:03+00:00 lcm-34-189 pgpool[11630]: [67-1] 2019-08-31 16:34:03: pid 11630: LOG: failover done. shutdown host 10.198.34.188(5432) 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + FAILED_NODE_ID=0 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + FAILED_NODE_HOST=10.198.34.188 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21402]: follow_master.sh: start: pg_basebackup for 0 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + FAILED_NODE_PORT=5432 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + FAILED_NODE_PGDATA=/db/data 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + NEW_MASTER_NODE_ID=1 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + OLD_MASTER_NODE_ID=0 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + NEW_MASTER_NODE_HOST=10.198.34.189 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + OLD_PRIMARY_NODE_ID=0 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + NEW_MASTER_NODE_PORT=5432 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + NEW_MASTER_NODE_PGDATA=/db/data 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + PGHOME=/opt/vmware/vpostgres/9.6 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + ARCHIVEDIR=/var/vmware/vpostgres/9.6/archive 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + REPL_USER=repl 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + PCP_USER=pgpool 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + PGPOOL_PATH=/usr/local/bin 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + PCP_PORT=9898 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + logger -i -p local1.info follow_master.sh: start: pg_basebackup for 0 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: + ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@10.198.34.188 2019-08-31T16:34:03+00:00 lcm-34-189 logger[21401]: Pseudo-terminal will not be allocated because stdin is not a terminal. 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11671]: [8-1] 2019-08-31 16:34:04: pid 11671: LOG: restart request received in pcp child process 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [68-1] 2019-08-31 16:34:04: pid 11630: LOG: PCP child 11671 exits with status 0 in failover() 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [69-1] 2019-08-31 16:34:04: pid 11630: LOG: fork a new PCP child pid 21406 in failover() 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [70-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11639 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [71-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11639 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [72-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11640 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [73-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11640 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [74-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11641 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [75-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11641 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [76-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11642 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [77-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11642 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [78-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11643 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [79-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11643 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [80-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11644 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [81-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11644 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [82-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11645 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [83-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11645 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [84-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11646 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [85-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11646 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [86-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11647 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [87-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11647 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [88-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11648 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [89-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11648 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [90-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11649 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [91-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11649 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [92-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11650 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [93-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11650 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [94-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11651 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [95-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11651 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [96-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11652 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [97-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11652 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [98-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11653 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [99-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11653 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [100-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11654 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [101-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11654 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [102-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11655 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [103-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11655 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [104-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11656 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [105-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11656 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [106-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11657 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [107-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11657 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [108-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11658 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [109-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11658 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [110-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11659 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [111-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11659 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [112-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11660 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [113-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11660 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [114-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11661 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [115-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11661 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [116-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11662 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [117-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11662 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [118-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11663 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [119-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11663 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [120-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11664 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [121-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11664 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [122-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11665 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [123-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11665 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [124-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11666 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [125-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11666 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [126-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11667 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [127-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11667 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [128-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11668 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [129-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11668 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [130-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11669 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [131-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11669 exited with success and will not be restarted 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [132-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11670 exits with status 0 2019-08-31T16:34:04+00:00 lcm-34-189 pgpool[11630]: [133-1] 2019-08-31 16:34:04: pid 11630: LOG: child process with pid: 11670 exited with success and will not be restarted 2019-08-31T16:34:13+00:00 lcm-34-189 pgpool[11672]: [18-1] 2019-08-31 16:34:13: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:34:13+00:00 lcm-34-189 pgpool[11672]: [18-2] 2019-08-31 16:34:13: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:34:19+00:00 lcm-34-189 pgpool[11631]: [61-1] 2019-08-31 16:34:19: pid 11631: LOG: watchdog received the failover command from remote pgpool-II node "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" 2019-08-31T16:34:19+00:00 lcm-34-189 pgpool[11631]: [62-1] 2019-08-31 16:34:19: pid 11631: LOG: watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local 2019-08-31T16:34:19+00:00 lcm-34-189 pgpool[11631]: [63-1] 2019-08-31 16:34:19: pid 11631: LOG: failover requires the majority vote, waiting for consensus 2019-08-31T16:34:19+00:00 lcm-34-189 pgpool[11631]: [63-2] 2019-08-31 16:34:19: pid 11631: DETAIL: failover request noted 2019-08-31T16:34:19+00:00 lcm-34-189 pgpool[11631]: [64-1] 2019-08-31 16:34:19: pid 11631: LOG: failover command [DEGENERATE_BACKEND_REQUEST] request from pgpool-II node "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is queued, waiting for the confirmation from other nodes 2019-08-31T16:34:19+00:00 lcm-34-189 pgpool[11630]: [134-1] 2019-08-31 16:34:19: pid 11630: LOG: Pgpool-II parent process received inform quarantine nodes signal from watchdog 2019-08-31T16:34:23+00:00 lcm-34-189 pgpool[11672]: [19-1] 2019-08-31 16:34:23: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:34:23+00:00 lcm-34-189 pgpool[11672]: [19-2] 2019-08-31 16:34:23: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:34:33+00:00 lcm-34-189 pgpool[11672]: [20-1] 2019-08-31 16:34:33: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:34:33+00:00 lcm-34-189 pgpool[11672]: [20-2] 2019-08-31 16:34:33: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:34:43+00:00 lcm-34-189 pgpool[11672]: [21-1] 2019-08-31 16:34:43: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:34:43+00:00 lcm-34-189 pgpool[11672]: [21-2] 2019-08-31 16:34:43: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:34:53+00:00 lcm-34-189 pgpool[11672]: [22-1] 2019-08-31 16:34:53: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:34:53+00:00 lcm-34-189 pgpool[11672]: [22-2] 2019-08-31 16:34:53: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:35:03+00:00 lcm-34-189 pgpool[11672]: [23-1] 2019-08-31 16:35:03: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:35:03+00:00 lcm-34-189 pgpool[11672]: [23-2] 2019-08-31 16:35:03: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:35:13+00:00 lcm-34-189 pgpool[11672]: [24-1] 2019-08-31 16:35:13: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:35:13+00:00 lcm-34-189 pgpool[11672]: [24-2] 2019-08-31 16:35:13: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:35:22+00:00 lcm-34-189 pgpool[21372]: [67-1] 2019-08-31 16:35:22: pid 21372: LOG: md5 authentication successful with frontend 2019-08-31T16:35:23+00:00 lcm-34-189 pgpool[11672]: [25-1] 2019-08-31 16:35:23: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:35:23+00:00 lcm-34-189 pgpool[11672]: [25-2] 2019-08-31 16:35:23: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:35:33+00:00 lcm-34-189 pgpool[11672]: [26-1] 2019-08-31 16:35:33: pid 11672: LOG: trying connecting to PostgreSQL server on "10.198.34.188:5432" by INET socket 2019-08-31T16:35:33+00:00 lcm-34-189 pgpool[11672]: [26-2] 2019-08-31 16:35:33: pid 11672: DETAIL: timed out. retrying... 2019-08-31T16:35:36+00:00 lcm-34-189 pgpool[11672]: [27-1] 2019-08-31 16:35:36: pid 11672: LOG: failed to connect to PostgreSQL server on "10.198.34.188:5432", getsockopt() detected error "Connection timed out" 2019-08-31T16:35:36+00:00 lcm-34-189 pgpool[11672]: [28-1] 2019-08-31 16:35:36: pid 11672: ERROR: failed to make persistent db connection 2019-08-31T16:35:36+00:00 lcm-34-189 pgpool[11672]: [28-2] 2019-08-31 16:35:36: pid 11672: DETAIL: connection to host:"10.198.34.188:5432" failed 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21401]: ssh: connect to host 10.198.34.188 port 22: No route to host 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21401]: + logger -i -p local1.info follow_master.sh: end: finished running the script 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21630]: follow_master.sh: end: finished running the script 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21401]: + exit 0 2019-08-31T16:35:38+00:00 lcm-34-189 pgpool[21366]: [67-1] 2019-08-31 16:35:38: pid 21366: LOG: execute command: /usr/local/etc/follow_master.sh 2 10.198.34.190 5432 /db/data 1 0 10.198.34.189 0 5432 /db/data 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + FAILED_NODE_ID=2 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + FAILED_NODE_HOST=10.198.34.190 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + FAILED_NODE_PORT=5432 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21634]: follow_master.sh: start: pg_basebackup for 2 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + FAILED_NODE_PGDATA=/db/data 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + NEW_MASTER_NODE_ID=1 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + OLD_MASTER_NODE_ID=0 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + NEW_MASTER_NODE_HOST=10.198.34.189 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + OLD_PRIMARY_NODE_ID=0 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + NEW_MASTER_NODE_PORT=5432 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + NEW_MASTER_NODE_PGDATA=/db/data 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + PGHOME=/opt/vmware/vpostgres/9.6 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + ARCHIVEDIR=/var/vmware/vpostgres/9.6/archive 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + REPL_USER=repl 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + PCP_USER=pgpool 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + PGPOOL_PATH=/usr/local/bin 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + PCP_PORT=9898 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + logger -i -p local1.info follow_master.sh: start: pg_basebackup for 2 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: + ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null root@10.198.34.190 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: Pseudo-terminal will not be allocated because stdin is not a terminal. 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: Warning: Permanently added '10.198.34.190' (RSA) to the list of known hosts. 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: Welcome to SUSE Linux Enterprise Server 11 SP4 (x86_64) - Kernel \r (\l). 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: 2019-08-31T16:35:38+00:00 lcm-34-189 logger[21633]: could not change directory to "/root": Permission denied 2019-08-31T16:35:39+00:00 lcm-34-189 logger[21633]: waiting for server to shut down.... done 2019-08-31T16:35:39+00:00 lcm-34-189 logger[21633]: server stopped 2019-08-31T16:35:39+00:00 lcm-34-189 logger[21633]: could not change directory to "/root": Permission denied 2019-08-31T16:35:39+00:00 lcm-34-189 logger[21633]: Password: 2019-08-31T16:35:42+00:00 lcm-34-189 pgpool[21406]: [69-1] 2019-08-31 16:35:42: pid 21406: LOG: forked new pcp worker, pid=21643 socket=8 2019-08-31T16:35:42+00:00 lcm-34-189 pgpool[11631]: [65-1] 2019-08-31 16:35:42: pid 11631: LOG: new IPC connection received 2019-08-31T16:35:42+00:00 lcm-34-189 pgpool[21406]: [70-1] 2019-08-31 16:35:42: pid 21406: LOG: PCP process with pid: 21643 exit with SUCCESS. 2019-08-31T16:35:42+00:00 lcm-34-189 pgpool[21406]: [71-1] 2019-08-31 16:35:42: pid 21406: LOG: PCP process with pid: 21643 exits with status 0 2019-08-31T16:35:43+00:00 lcm-34-189 logger[21633]: could not change directory to "/root": Permission denied 2019-08-31T16:35:44+00:00 lcm-34-189 logger[21633]: waiting for server to start.... done 2019-08-31T16:35:44+00:00 lcm-34-189 logger[21633]: server started 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11631]: [66-1] 2019-08-31 16:35:44: pid 11631: LOG: watchdog received the failover command from remote pgpool-II node "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11631]: [67-1] 2019-08-31 16:35:44: pid 11631: LOG: watchdog is processing the failover command [FAILBACK_REQUEST] received from lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11631]: [68-1] 2019-08-31 16:35:44: pid 11631: LOG: The failover request does not need quorum to hold 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11631]: [68-2] 2019-08-31 16:35:44: pid 11631: DETAIL: proceeding with the failover 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11631]: [68-3] 2019-08-31 16:35:44: pid 11631: HINT: REQ_DETAIL_CONFIRMED 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11631]: [69-1] 2019-08-31 16:35:44: pid 11631: LOG: received failback request for node_id: 2 from pid [11631] 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11630]: [135-1] 2019-08-31 16:35:44: pid 11630: LOG: Pgpool-II parent process has received failover request 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11631]: [70-1] 2019-08-31 16:35:44: pid 11631: LOG: new IPC connection received 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11631]: [71-1] 2019-08-31 16:35:44: pid 11631: LOG: received the failover indication from Pgpool-II on IPC interface 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11631]: [72-1] 2019-08-31 16:35:44: pid 11631: LOG: watchdog is informed of failover start by the main process 2019-08-31T16:35:44+00:00 lcm-34-189 logger[21633]: pcp_attach_node -- Command Successful 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11630]: [136-1] 2019-08-31 16:35:44: pid 11630: LOG: starting fail back. reconnect host 10.198.34.190(5432) 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11630]: [137-1] 2019-08-31 16:35:44: pid 11630: LOG: Node 1 is not down (status: 2) 2019-08-31T16:35:44+00:00 lcm-34-189 logger[21633]: + logger -i -p local1.info follow_master.sh: end: finished running the script 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11630]: [138-1] 2019-08-31 16:35:44: pid 11630: LOG: Do not restart children because we are failing back node id 2 host: 10.198.34.190 port: 5432 and we are in streaming replication mode and not all backends were down 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11630]: [139-1] 2019-08-31 16:35:44: pid 11630: LOG: find_primary_node_repeatedly: waiting for finding a primary node 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11630]: [140-1] 2019-08-31 16:35:44: pid 11630: LOG: find_primary_node: primary node is 1 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11630]: [141-1] 2019-08-31 16:35:44: pid 11630: LOG: find_primary_node: standby node is 2 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11630]: [142-1] 2019-08-31 16:35:44: pid 11630: LOG: failover: set new primary node: 1 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11630]: [143-1] 2019-08-31 16:35:44: pid 11630: LOG: failover: set new master node: 1 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11672]: [29-1] 2019-08-31 16:35:44: pid 11672: ERROR: Failed to check replication time lag 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11672]: [29-2] 2019-08-31 16:35:44: pid 11672: DETAIL: No persistent db connection for the node 0 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11672]: [29-3] 2019-08-31 16:35:44: pid 11672: HINT: check sr_check_user and sr_check_password 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11672]: [29-4] 2019-08-31 16:35:44: pid 11672: CONTEXT: while checking replication time lag 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11672]: [30-1] 2019-08-31 16:35:44: pid 11672: LOG: worker process received restart request 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11631]: [73-1] 2019-08-31 16:35:44: pid 11631: LOG: new IPC connection received 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11631]: [74-1] 2019-08-31 16:35:44: pid 11631: LOG: received the failover indication from Pgpool-II on IPC interface 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11631]: [75-1] 2019-08-31 16:35:44: pid 11631: LOG: watchdog is informed of failover end by the main process 2019-08-31T16:35:44+00:00 lcm-34-189 pgpool[11630]: [144-1] 2019-08-31 16:35:44: pid 11630: LOG: failback done. reconnect host 10.198.34.190(5432) 2019-08-31T16:35:44+00:00 lcm-34-189 logger[21657]: follow_master.sh: end: finished running the script 2019-08-31T16:35:44+00:00 lcm-34-189 logger[21633]: + exit 0 2019-08-31T16:35:45+00:00 lcm-34-189 pgpool[21406]: [72-1] 2019-08-31 16:35:45: pid 21406: LOG: restart request received in pcp child process 2019-08-31T16:35:45+00:00 lcm-34-189 pgpool[11630]: [145-1] 2019-08-31 16:35:45: pid 11630: LOG: PCP child 21406 exits with status 0 in failover() 2019-08-31T16:35:45+00:00 lcm-34-189 pgpool[11630]: [146-1] 2019-08-31 16:35:45: pid 11630: LOG: fork a new PCP child pid 21660 in failover() 2019-08-31T16:35:45+00:00 lcm-34-189 pgpool[11630]: [147-1] 2019-08-31 16:35:45: pid 11630: LOG: worker child process with pid: 11672 exits with status 256 2019-08-31T16:35:45+00:00 lcm-34-189 pgpool[11630]: [148-1] 2019-08-31 16:35:45: pid 11630: LOG: fork a new worker child process with pid: 21661 2019-08-31T16:35:45+00:00 lcm-34-189 pgpool[11630]: [149-1] 2019-08-31 16:35:45: pid 11630: LOG: child process with pid: 21366 exits with status 0 2019-08-31T16:35:45+00:00 lcm-34-189 pgpool[11630]: [150-1] 2019-08-31 16:35:45: pid 11630: LOG: child process with pid: 21366 exited with success and will not be restarted 2019-08-31T16:35:50+00:00 lcm-34-189 pgpool[21377]: [67-1] 2019-08-31 16:35:50: pid 21377: LOG: failback event detected 2019-08-31T16:35:50+00:00 lcm-34-189 pgpool[21377]: [67-2] 2019-08-31 16:35:50: pid 21377: DETAIL: restarting myself 2019-08-31T16:35:50+00:00 lcm-34-189 pgpool[21372]: [68-1] 2019-08-31 16:35:50: pid 21372: LOG: selecting backend connection 2019-08-31T16:35:50+00:00 lcm-34-189 pgpool[21372]: [68-2] 2019-08-31 16:35:50: pid 21372: DETAIL: failback event detected, discarding existing connections 2019-08-31T16:35:50+00:00 lcm-34-189 pgpool[11630]: [151-1] 2019-08-31 16:35:50: pid 11630: LOG: child process with pid: 21377 exits with status 256 2019-08-31T16:35:50+00:00 lcm-34-189 pgpool[11630]: [152-1] 2019-08-31 16:35:50: pid 11630: LOG: fork a new child process with pid: 21691 2019-08-31T16:35:52+00:00 lcm-34-189 pgpool[21691]: [152-1] 2019-08-31 16:35:52: pid 21691: LOG: md5 authentication successful with frontend 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21367]: [67-1] 2019-08-31 16:39:03: pid 21367: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21367]: [67-2] 2019-08-31 16:39:03: pid 21367: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [153-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21367 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [154-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22082 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21370]: [67-1] 2019-08-31 16:39:03: pid 21370: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21370]: [67-2] 2019-08-31 16:39:03: pid 21370: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21386]: [67-1] 2019-08-31 16:39:03: pid 21386: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21386]: [67-2] 2019-08-31 16:39:03: pid 21386: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21371]: [67-1] 2019-08-31 16:39:03: pid 21371: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21371]: [67-2] 2019-08-31 16:39:03: pid 21371: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21378]: [67-1] 2019-08-31 16:39:03: pid 21378: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21378]: [67-2] 2019-08-31 16:39:03: pid 21378: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21380]: [67-1] 2019-08-31 16:39:03: pid 21380: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21380]: [67-2] 2019-08-31 16:39:03: pid 21380: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21373]: [67-1] 2019-08-31 16:39:03: pid 21373: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21373]: [67-2] 2019-08-31 16:39:03: pid 21373: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [155-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21370 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21399]: [67-1] 2019-08-31 16:39:03: pid 21399: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21399]: [67-2] 2019-08-31 16:39:03: pid 21399: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21374]: [67-1] 2019-08-31 16:39:03: pid 21374: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21374]: [67-2] 2019-08-31 16:39:03: pid 21374: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21388]: [67-1] 2019-08-31 16:39:03: pid 21388: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21388]: [67-2] 2019-08-31 16:39:03: pid 21388: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21382]: [67-1] 2019-08-31 16:39:03: pid 21382: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21382]: [67-2] 2019-08-31 16:39:03: pid 21382: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21384]: [67-1] 2019-08-31 16:39:03: pid 21384: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21384]: [67-2] 2019-08-31 16:39:03: pid 21384: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21385]: [67-1] 2019-08-31 16:39:03: pid 21385: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21385]: [67-2] 2019-08-31 16:39:03: pid 21385: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21383]: [67-1] 2019-08-31 16:39:03: pid 21383: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21387]: [67-1] 2019-08-31 16:39:03: pid 21387: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21387]: [67-2] 2019-08-31 16:39:03: pid 21387: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21390]: [67-1] 2019-08-31 16:39:03: pid 21390: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21390]: [67-2] 2019-08-31 16:39:03: pid 21390: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21392]: [67-1] 2019-08-31 16:39:03: pid 21392: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21392]: [67-2] 2019-08-31 16:39:03: pid 21392: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21383]: [67-2] 2019-08-31 16:39:03: pid 21383: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21389]: [67-1] 2019-08-31 16:39:03: pid 21389: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21389]: [67-2] 2019-08-31 16:39:03: pid 21389: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21376]: [67-1] 2019-08-31 16:39:03: pid 21376: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21376]: [67-2] 2019-08-31 16:39:03: pid 21376: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21391]: [67-1] 2019-08-31 16:39:03: pid 21391: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21391]: [67-2] 2019-08-31 16:39:03: pid 21391: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21396]: [67-1] 2019-08-31 16:39:03: pid 21396: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21396]: [67-2] 2019-08-31 16:39:03: pid 21396: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [156-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22083 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [157-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21371 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [158-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22084 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [159-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21373 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21397]: [67-1] 2019-08-31 16:39:03: pid 21397: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21397]: [67-2] 2019-08-31 16:39:03: pid 21397: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [160-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22085 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [161-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21374 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [162-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22086 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [163-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21376 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [164-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22087 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21394]: [67-1] 2019-08-31 16:39:03: pid 21394: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21394]: [67-2] 2019-08-31 16:39:03: pid 21394: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21395]: [67-1] 2019-08-31 16:39:03: pid 21395: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21395]: [67-2] 2019-08-31 16:39:03: pid 21395: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21379]: [67-1] 2019-08-31 16:39:03: pid 21379: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21379]: [67-2] 2019-08-31 16:39:03: pid 21379: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21369]: [67-1] 2019-08-31 16:39:03: pid 21369: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21369]: [67-2] 2019-08-31 16:39:03: pid 21369: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21381]: [67-1] 2019-08-31 16:39:03: pid 21381: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21381]: [67-2] 2019-08-31 16:39:03: pid 21381: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [165-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21378 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21375]: [67-1] 2019-08-31 16:39:03: pid 21375: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21375]: [67-2] 2019-08-31 16:39:03: pid 21375: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21398]: [67-1] 2019-08-31 16:39:03: pid 21398: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21398]: [67-2] 2019-08-31 16:39:03: pid 21398: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [166-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22088 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [167-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21369 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [168-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22089 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [169-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21375 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21393]: [67-1] 2019-08-31 16:39:03: pid 21393: LOG: failback event detected 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[21393]: [67-2] 2019-08-31 16:39:03: pid 21393: DETAIL: restarting myself 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [170-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22090 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [171-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21379 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [172-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22091 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [173-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21380 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [174-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22092 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [175-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21381 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [176-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22093 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [177-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21382 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [178-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22094 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [179-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21383 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [180-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22095 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [181-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21384 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [182-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22096 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [183-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21385 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [184-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22097 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [185-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21386 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [186-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22098 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [187-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21387 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [188-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22099 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [189-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21388 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [190-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22100 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [191-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21389 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [192-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22101 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [193-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21390 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [194-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22102 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [195-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21391 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [196-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22103 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [197-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21392 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [198-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22104 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [199-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21393 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [200-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22105 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [201-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21394 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [202-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22106 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [203-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21395 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [204-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22107 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [205-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21396 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [206-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22108 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [207-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21397 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [208-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22109 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [209-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21398 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [210-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22110 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [211-1] 2019-08-31 16:39:03: pid 11630: LOG: child process with pid: 21399 exits with status 256 2019-08-31T16:39:03+00:00 lcm-34-189 pgpool[11630]: [212-1] 2019-08-31 16:39:03: pid 11630: LOG: fork a new child process with pid: 22111 2019-08-31T16:39:22+00:00 lcm-34-189 pgpool[11631]: [76-1] 2019-08-31 16:39:22: pid 11631: LOG: new outbound connection to 10.198.34.188:9000 2019-08-31T16:39:27+00:00 lcm-34-189 pgpool[11631]: [77-1] 2019-08-31 16:39:27: pid 11631: LOG: new watchdog node connection is received from "10.198.34.188:14802" 2019-08-31T16:39:27+00:00 lcm-34-189 pgpool[11631]: [78-1] 2019-08-31 16:39:27: pid 11631: LOG: new node joined the cluster hostname:"lcm-34-188.dev.lcm.local" port:9000 pgpool_port:9999 2019-08-31T16:39:27+00:00 lcm-34-189 pgpool[11631]: [79-1] 2019-08-31 16:39:27: pid 11631: LOG: remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" decided it is the true master 2019-08-31T16:39:27+00:00 lcm-34-189 pgpool[11631]: [79-2] 2019-08-31 16:39:27: pid 11631: DETAIL: re-initializing the local watchdog cluster state because of split-brain 2019-08-31T16:39:27+00:00 lcm-34-189 pgpool[22140]: [80-1] 2019-08-31 16:39:27: pid 22140: LOG: watchdog: de-escalation started 2019-08-31T16:39:27+00:00 lcm-34-189 pgpool[11631]: [80-1] 2019-08-31 16:39:27: pid 11631: LOG: watchdog node state changed from [MASTER] to [JOINING] 2019-08-31T16:39:27+00:00 lcm-34-189 pgpool[11631]: [81-1] 2019-08-31 16:39:27: pid 11631: LOG: unassigning the local node "lcm-34-189.dev.lcm.local:9999 Linux lcm-34-189.dev.lcm.local" from watchdog cluster master 2019-08-31T16:39:27+00:00 lcm-34-189 pgpool[11631]: [82-1] 2019-08-31 16:39:27: pid 11631: LOG: setting the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" as watchdog cluster master 2019-08-31T16:39:27+00:00 lcm-34-189 pgpool[11631]: [83-1] 2019-08-31 16:39:27: pid 11631: LOG: watchdog node state changed from [JOINING] to [INITIALIZING] 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22143]: + FAILED_NODE_ID= 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22144]: Desc.sh: de-escalation script being called, delegateIP is being released !!!!!!!!!!!!!!!!!! 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22143]: + FAILED_NODE_HOST= 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22143]: + FAILED_NODE_PORT= 2019-08-31T16:39:27+00:00 lcm-34-189 pgpool[22140]: [81-1] 2019-08-31 16:39:27: pid 22140: LOG: watchdog de-escalation successful 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22143]: + FAILED_NODE_PGDATA= 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22143]: + NEW_MASTER_NODE_ID= 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22143]: + NEW_MASTER_NODE_HOST= 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22143]: + OLD_MASTER_NODE_ID= 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22143]: + OLD_PRIMARY_NODE_ID= 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22143]: + NEW_MASTER_NODE_PORT= 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22143]: + NEW_MASTER_NODE_PGDATA= 2019-08-31T16:39:27+00:00 lcm-34-189 pgpool[11631]: [84-1] 2019-08-31 16:39:27: pid 11631: LOG: watchdog de-escalation process with pid: 22140 exit with SUCCESS. 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22143]: + PGHOME=/opt/vmware/vpostgres/9.6 2019-08-31T16:39:27+00:00 lcm-34-189 logger[22143]: + logger -i -p local1.info Desc.sh: de-escalation script being called, delegateIP is being released '!!!!!!!!!!!!!!!!!!' 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11631]: [85-1] 2019-08-31 16:39:28: pid 11631: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY] 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11631]: [86-1] 2019-08-31 16:39:28: pid 11631: LOG: successfully joined the watchdog cluster as standby node 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11631]: [86-2] 2019-08-31 16:39:28: pid 11631: DETAIL: our join coordinator request is accepted by cluster leader node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11631]: [87-1] 2019-08-31 16:39:28: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [213-1] 2019-08-31 16:39:28: pid 11630: LOG: we have joined the watchdog cluster as STANDBY node 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [213-2] 2019-08-31 16:39:28: pid 11630: DETAIL: syncing the backend states from the MASTER watchdog node 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11631]: [88-1] 2019-08-31 16:39:28: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11631]: [89-1] 2019-08-31 16:39:28: pid 11631: LOG: received the get data request from local pgpool-II on IPC interface 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11631]: [90-1] 2019-08-31 16:39:28: pid 11631: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to master watchdog node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11631]: [90-2] 2019-08-31 16:39:28: pid 11631: DETAIL: waiting for the reply... 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [214-1] 2019-08-31 16:39:28: pid 11630: LOG: master watchdog node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" returned status for 3 backend nodes 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [215-1] 2019-08-31 16:39:28: pid 11630: LOG: primary node:0 on master watchdog node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is different from local primary node:1 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [216-1] 2019-08-31 16:39:28: pid 11630: LOG: backend:0 is set to UP status 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [216-2] 2019-08-31 16:39:28: pid 11630: DETAIL: backend:0 is UP on cluster master "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [217-1] 2019-08-31 16:39:28: pid 11630: LOG: backend:1 is set to UP status 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [217-2] 2019-08-31 16:39:28: pid 11630: DETAIL: backend:1 is UP on cluster master "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [218-1] 2019-08-31 16:39:28: pid 11630: LOG: backend:2 is set to UP status 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [218-2] 2019-08-31 16:39:28: pid 11630: DETAIL: backend:2 is UP on cluster master "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [219-1] 2019-08-31 16:39:28: pid 11630: LOG: primary node was chenged after the sync from "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [219-2] 2019-08-31 16:39:28: pid 11630: DETAIL: all children needs to be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [220-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22082 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[21661]: [148-1] 2019-08-31 16:39:28: pid 21661: LOG: worker process received restart request 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [221-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22082 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [222-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 21372 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [223-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 21372 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [224-1] 2019-08-31 16:39:28: pid 11630: LOG: worker child process with pid: 21661 exits with status 256 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [225-1] 2019-08-31 16:39:28: pid 11630: LOG: fork a new worker child process with pid: 22179 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [226-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 21691 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [227-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 21691 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [228-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22083 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [229-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22083 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [230-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22084 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [231-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22084 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [232-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22085 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [233-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22085 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [234-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22086 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [235-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22086 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [236-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22087 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [237-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22087 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [238-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22088 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [239-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22088 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [240-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22089 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [241-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22089 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [242-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22090 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [243-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22090 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [244-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22091 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [245-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22091 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [246-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22092 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [247-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22092 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [248-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22093 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [249-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22093 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [250-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22094 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [251-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22094 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [252-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22095 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [253-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22095 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [254-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22096 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [255-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22096 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [256-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22097 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [257-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22097 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [258-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22098 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [259-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22098 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [260-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22099 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [261-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22099 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [262-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22100 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [263-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22100 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [264-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22101 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [265-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22101 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [266-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22102 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [267-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22102 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [268-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22103 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [269-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22103 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [270-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22104 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [271-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22104 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [272-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22105 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [273-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22105 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [274-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22106 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [275-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22106 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [276-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22107 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [277-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22107 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [278-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22108 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [279-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22108 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [280-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22109 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [281-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22109 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [282-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22110 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [283-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22110 exited with success and will not be restarted 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [284-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22111 exits with status 0 2019-08-31T16:39:28+00:00 lcm-34-189 pgpool[11630]: [285-1] 2019-08-31 16:39:28: pid 11630: LOG: child process with pid: 22111 exited with success and will not be restarted 2019-08-31T16:39:32+00:00 lcm-34-189 pgpool[11631]: [91-1] 2019-08-31 16:39:32: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is the coordinator as per our record but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:32+00:00 lcm-34-189 pgpool[11631]: [91-2] 2019-08-31 16:39:32: pid 11631: DETAIL: cluster is in the split-brain 2019-08-31T16:39:32+00:00 lcm-34-189 pgpool[11631]: [92-1] 2019-08-31 16:39:32: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is the coordinator as per our record but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:32+00:00 lcm-34-189 pgpool[11631]: [92-2] 2019-08-31 16:39:32: pid 11631: DETAIL: cluster is in the split-brain 2019-08-31T16:39:33+00:00 lcm-34-189 pgpool[11631]: [93-1] 2019-08-31 16:39:33: pid 11631: LOG: watchdog node state changed from [STANDBY] to [JOINING] 2019-08-31T16:39:33+00:00 lcm-34-189 pgpool[11631]: [94-1] 2019-08-31 16:39:33: pid 11631: LOG: unassigning the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" from watchdog cluster master 2019-08-31T16:39:33+00:00 lcm-34-189 pgpool[11631]: [95-1] 2019-08-31 16:39:33: pid 11631: LOG: setting the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" as watchdog cluster master 2019-08-31T16:39:33+00:00 lcm-34-189 pgpool[11631]: [96-1] 2019-08-31 16:39:33: pid 11631: LOG: watchdog node state changed from [JOINING] to [INITIALIZING] 2019-08-31T16:39:33+00:00 lcm-34-189 pgpool[11630]: [286-1] 2019-08-31 16:39:33: pid 11630: LOG: Pgpool-II parent process received watchdog quorum change signal from watchdog 2019-08-31T16:39:33+00:00 lcm-34-189 pgpool[11631]: [97-1] 2019-08-31 16:39:33: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11631]: [98-1] 2019-08-31 16:39:34: pid 11631: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY] 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11631]: [99-1] 2019-08-31 16:39:34: pid 11631: LOG: successfully joined the watchdog cluster as standby node 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11631]: [99-2] 2019-08-31 16:39:34: pid 11631: DETAIL: our join coordinator request is accepted by cluster leader node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11631]: [100-1] 2019-08-31 16:39:34: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11630]: [287-1] 2019-08-31 16:39:34: pid 11630: LOG: we have joined the watchdog cluster as STANDBY node 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11630]: [287-2] 2019-08-31 16:39:34: pid 11630: DETAIL: syncing the backend states from the MASTER watchdog node 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11631]: [101-1] 2019-08-31 16:39:34: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11631]: [102-1] 2019-08-31 16:39:34: pid 11631: LOG: received the get data request from local pgpool-II on IPC interface 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11631]: [103-1] 2019-08-31 16:39:34: pid 11631: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to master watchdog node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11631]: [103-2] 2019-08-31 16:39:34: pid 11631: DETAIL: waiting for the reply... 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11630]: [288-1] 2019-08-31 16:39:34: pid 11630: LOG: master watchdog node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" returned status for 3 backend nodes 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11630]: [289-1] 2019-08-31 16:39:34: pid 11630: LOG: backend nodes status remains same after the sync from "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11630]: [290-1] 2019-08-31 16:39:34: pid 11630: LOG: Pgpool-II parent process received watchdog quorum change signal from watchdog 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11631]: [104-1] 2019-08-31 16:39:34: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11630]: [291-1] 2019-08-31 16:39:34: pid 11630: LOG: watchdog cluster now holds the quorum 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11630]: [291-2] 2019-08-31 16:39:34: pid 11630: DETAIL: updating the state of quarantine backend nodes 2019-08-31T16:39:34+00:00 lcm-34-189 pgpool[11631]: [105-1] 2019-08-31 16:39:34: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:38+00:00 lcm-34-189 pgpool[11631]: [106-1] 2019-08-31 16:39:38: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is the coordinator as per our record but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:38+00:00 lcm-34-189 pgpool[11631]: [106-2] 2019-08-31 16:39:38: pid 11631: DETAIL: cluster is in the split-brain 2019-08-31T16:39:38+00:00 lcm-34-189 pgpool[11631]: [107-1] 2019-08-31 16:39:38: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is the coordinator as per our record but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:38+00:00 lcm-34-189 pgpool[11631]: [107-2] 2019-08-31 16:39:38: pid 11631: DETAIL: cluster is in the split-brain 2019-08-31T16:39:39+00:00 lcm-34-189 pgpool[11631]: [108-1] 2019-08-31 16:39:39: pid 11631: LOG: watchdog node state changed from [STANDBY] to [JOINING] 2019-08-31T16:39:39+00:00 lcm-34-189 pgpool[11631]: [109-1] 2019-08-31 16:39:39: pid 11631: LOG: unassigning the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" from watchdog cluster master 2019-08-31T16:39:39+00:00 lcm-34-189 pgpool[11631]: [110-1] 2019-08-31 16:39:39: pid 11631: LOG: setting the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" as watchdog cluster master 2019-08-31T16:39:39+00:00 lcm-34-189 pgpool[11631]: [111-1] 2019-08-31 16:39:39: pid 11631: LOG: watchdog node state changed from [JOINING] to [INITIALIZING] 2019-08-31T16:39:39+00:00 lcm-34-189 pgpool[11630]: [292-1] 2019-08-31 16:39:39: pid 11630: LOG: Pgpool-II parent process received watchdog quorum change signal from watchdog 2019-08-31T16:39:39+00:00 lcm-34-189 pgpool[11631]: [112-1] 2019-08-31 16:39:39: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:40+00:00 lcm-34-189 pgpool[11631]: [113-1] 2019-08-31 16:39:40: pid 11631: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY] 2019-08-31T16:39:40+00:00 lcm-34-189 pgpool[11631]: [114-1] 2019-08-31 16:39:40: pid 11631: LOG: successfully joined the watchdog cluster as standby node 2019-08-31T16:39:40+00:00 lcm-34-189 pgpool[11631]: [114-2] 2019-08-31 16:39:40: pid 11631: DETAIL: our join coordinator request is accepted by cluster leader node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:39:40+00:00 lcm-34-189 pgpool[11631]: [115-1] 2019-08-31 16:39:40: pid 11631: LOG: watchdog node state changed from [STANDBY] to [JOINING] 2019-08-31T16:39:40+00:00 lcm-34-189 pgpool[11631]: [116-1] 2019-08-31 16:39:40: pid 11631: LOG: unassigning the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" from watchdog cluster master 2019-08-31T16:39:40+00:00 lcm-34-189 pgpool[11631]: [117-1] 2019-08-31 16:39:40: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:40+00:00 lcm-34-189 pgpool[11631]: [118-1] 2019-08-31 16:39:40: pid 11631: LOG: setting the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" as watchdog cluster master 2019-08-31T16:39:40+00:00 lcm-34-189 pgpool[11631]: [119-1] 2019-08-31 16:39:40: pid 11631: LOG: watchdog node state changed from [JOINING] to [INITIALIZING] 2019-08-31T16:39:41+00:00 lcm-34-189 pgpool[11631]: [120-1] 2019-08-31 16:39:41: pid 11631: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY] 2019-08-31T16:39:41+00:00 lcm-34-189 pgpool[11631]: [121-1] 2019-08-31 16:39:41: pid 11631: LOG: watchdog node state changed from [STANDBY] to [JOINING] 2019-08-31T16:39:41+00:00 lcm-34-189 pgpool[11631]: [122-1] 2019-08-31 16:39:41: pid 11631: LOG: unassigning the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" from watchdog cluster master 2019-08-31T16:39:41+00:00 lcm-34-189 pgpool[11631]: [123-1] 2019-08-31 16:39:41: pid 11631: LOG: setting the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" as watchdog cluster master 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [124-1] 2019-08-31 16:39:42: pid 11631: LOG: watchdog node state changed from [JOINING] to [PARTICIPATING IN ELECTION] 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [125-1] 2019-08-31 16:39:42: pid 11631: LOG: watchdog node state changed from [PARTICIPATING IN ELECTION] to [INITIALIZING] 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [126-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is the coordinator as per our record but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [126-2] 2019-08-31 16:39:42: pid 11631: DETAIL: cluster is in the split-brain 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [127-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is the coordinator as per our record but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [127-2] 2019-08-31 16:39:42: pid 11631: DETAIL: cluster is in the split-brain 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [128-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [128-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [129-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [129-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [130-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [130-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [131-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [131-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [132-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [132-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [133-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [133-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [134-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [134-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [135-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [135-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [136-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [136-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [137-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [137-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [138-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [138-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [139-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [139-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [140-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [140-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [141-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [141-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [142-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [142-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [143-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [143-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [144-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [144-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [145-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [145-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [146-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [146-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [147-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [147-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [148-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [148-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [149-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [149-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [150-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [150-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [151-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [151-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [152-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [152-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [153-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [153-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [154-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [154-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [155-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [155-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11630]: [293-1] 2019-08-31 16:39:42: pid 11630: LOG: Pgpool-II parent process received watchdog quorum change signal from watchdog 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [156-1] 2019-08-31 16:39:42: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [157-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [157-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11630]: [294-1] 2019-08-31 16:39:42: pid 11630: LOG: watchdog cluster now holds the quorum 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11630]: [294-2] 2019-08-31 16:39:42: pid 11630: DETAIL: updating the state of quarantine backend nodes 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [158-1] 2019-08-31 16:39:42: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [159-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [159-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [160-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [160-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [161-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [161-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [162-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [162-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [163-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [163-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [164-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [164-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [165-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [165-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [166-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [166-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [167-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [167-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [168-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [168-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [169-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [169-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [170-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [170-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [171-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [171-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [172-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [172-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [173-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [173-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [174-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [174-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [175-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [175-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [176-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [176-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [177-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [177-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [178-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [178-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [179-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [179-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [180-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [180-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [181-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [181-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [182-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [182-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [183-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [183-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [184-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [184-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [185-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [185-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [186-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [186-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [187-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [187-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [188-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [188-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [189-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [189-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [190-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [190-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [191-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [191-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [192-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [192-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [193-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [193-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [194-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [194-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [195-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [195-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [196-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [196-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [197-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [197-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [198-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [198-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [199-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [199-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [200-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [200-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [201-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [201-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [202-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [202-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [203-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [203-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [204-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [204-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [205-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [205-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [206-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [206-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [207-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [207-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [208-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [208-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [209-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [209-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [210-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [210-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [211-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [211-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [212-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [212-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [213-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [213-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [214-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [214-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [215-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [215-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [216-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [216-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [217-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [217-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [218-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [218-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [219-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [219-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [220-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [220-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [221-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [221-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [222-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [222-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [223-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [223-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [224-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [224-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [225-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [225-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [226-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [226-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [227-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [227-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [228-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [228-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [229-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [229-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [230-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [230-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [231-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [231-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [232-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [232-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [233-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [233-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [234-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [234-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [235-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [235-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [236-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [236-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [237-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [237-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [238-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [238-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [239-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [239-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [240-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [240-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [241-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [241-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [242-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [242-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [243-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [243-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [244-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [244-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [245-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [245-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [246-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [246-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [247-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [247-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [248-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [248-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [249-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [249-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [250-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [250-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [251-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [251-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [252-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [252-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [253-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [253-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [254-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [254-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [255-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [255-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [256-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [256-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [257-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [257-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [258-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [258-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [259-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [259-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [260-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [260-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [261-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [261-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [262-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [262-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [263-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [263-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [264-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [264-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [265-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [265-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [266-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [266-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [267-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [267-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [268-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [268-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [269-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [269-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [270-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [270-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [271-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [271-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [272-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [272-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [273-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [273-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [274-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [274-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [275-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [275-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [276-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [276-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [277-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [277-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [278-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [278-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [279-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [279-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [280-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [280-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [281-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [281-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [282-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [282-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [283-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [283-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [284-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [284-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [285-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [285-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [286-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [286-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [287-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [287-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [288-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [288-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [289-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [289-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [290-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [290-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [291-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [291-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [292-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [292-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [293-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [293-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [294-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [294-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [295-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [295-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [296-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [296-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [297-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [297-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [298-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [298-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [299-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [299-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [300-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [300-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [301-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [301-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [302-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [302-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [303-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [303-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [304-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [304-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [305-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [305-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [306-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [306-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [307-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [307-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [308-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [308-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [309-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [309-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [310-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [310-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [311-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [311-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [312-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [312-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [313-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [313-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [314-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [314-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [315-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [315-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [316-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [316-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [317-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [317-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [318-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [318-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [319-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [319-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [320-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [320-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [321-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [321-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [322-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [322-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [323-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [323-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [324-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [324-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [325-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [325-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [326-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [326-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [327-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [327-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [328-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [328-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [329-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [329-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [330-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [330-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [331-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [331-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [332-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [332-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [333-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [333-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [334-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [334-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [335-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [335-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [336-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [336-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [337-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [337-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [338-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [338-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [339-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [339-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [340-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [340-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [341-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [341-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [342-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [342-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [343-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [343-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [344-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [344-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [345-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [345-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [346-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [346-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [347-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [347-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [348-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [348-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [349-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [349-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [350-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [350-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [351-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [351-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [352-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [352-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [353-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [353-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [354-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [354-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [355-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [355-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [356-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [356-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [357-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [357-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [358-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [358-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [359-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [359-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [360-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [360-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [361-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [361-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [362-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [362-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [363-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [363-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [364-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [364-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [365-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [365-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [366-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [366-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [367-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [367-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [368-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [368-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [369-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [369-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [370-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [370-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [371-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [371-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [372-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [372-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [373-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [373-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [374-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [374-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [375-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [375-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [376-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [376-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [377-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [377-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [378-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [378-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [379-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [379-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [380-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [380-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [381-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [381-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [382-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [382-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [383-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [383-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [384-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [384-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [385-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [385-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [386-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [386-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [387-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [387-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [388-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [388-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [389-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [389-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [390-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [390-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [391-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [391-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [392-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [392-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [393-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [393-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [394-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [394-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [395-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [395-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [396-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [396-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [397-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [397-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [398-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [398-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [399-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [399-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [400-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [400-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [401-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [401-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [402-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [402-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [403-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [403-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [404-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [404-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [405-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [405-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [406-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [406-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [407-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [407-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [408-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [408-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [409-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [409-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [410-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [410-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [411-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [411-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [412-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [412-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [413-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [413-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [414-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [414-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [415-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [415-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [416-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [416-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [417-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [417-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [418-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [418-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [419-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [419-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [420-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [420-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [421-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [421-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [422-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [422-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [423-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [423-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [424-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [424-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [425-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [425-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [426-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [426-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [427-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [427-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [428-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [428-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [429-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [429-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [430-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [430-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [431-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [431-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [432-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [432-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [433-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [433-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [434-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [434-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [435-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [435-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [436-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [436-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [437-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [437-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [438-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [438-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [439-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [439-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [440-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [440-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [441-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [441-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [442-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [442-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [443-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [443-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [444-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [444-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [445-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [445-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [446-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [446-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [447-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [447-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [448-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [448-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [449-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [449-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [450-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [450-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [451-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [451-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [452-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [452-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [453-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [453-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [454-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [454-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [455-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [455-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [456-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [456-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [457-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [457-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [458-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [458-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [459-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [459-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [460-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [460-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [461-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [461-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [462-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [462-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [463-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [463-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [464-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [464-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [465-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [465-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [466-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [466-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [467-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [467-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [468-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [468-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [469-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [469-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [470-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [470-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [471-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [471-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [472-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [472-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [473-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [473-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [474-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [474-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [475-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [475-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [476-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [476-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [477-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [477-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [478-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [478-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [479-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [479-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [480-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [480-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [481-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [481-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [482-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [482-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [483-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [483-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [484-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [484-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [485-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [485-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [486-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [486-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [487-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [487-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [488-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [488-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [489-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [489-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [490-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [490-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [491-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [491-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [492-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [492-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [493-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [493-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [494-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [494-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [495-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [495-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [496-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [496-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [497-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [497-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [498-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [498-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [499-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [499-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [500-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [500-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [501-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [501-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [502-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [502-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [503-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [503-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [504-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [504-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [505-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [505-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [506-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [506-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [507-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [507-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [508-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [508-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [509-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [509-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [510-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [510-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [511-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [511-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [512-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [512-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [513-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [513-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [514-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [514-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [515-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [515-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [516-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [516-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [517-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [517-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [518-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [518-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [519-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [519-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [520-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [520-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [521-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [521-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [522-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [522-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [523-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [523-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [524-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [524-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [525-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [525-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [526-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [526-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [527-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [527-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [528-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [528-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [529-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [529-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [530-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [530-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [531-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [531-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [532-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [532-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [533-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [533-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [534-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [534-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [535-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [535-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [536-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [536-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [537-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [537-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [538-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [538-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [539-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [539-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [540-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [540-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [541-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [541-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [542-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [542-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [543-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [543-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [544-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [544-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [545-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [545-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [546-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [546-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [547-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [547-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [548-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [548-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [549-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [549-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [550-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [550-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [551-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [551-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [552-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [552-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [553-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [553-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [554-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [554-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [555-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [555-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [556-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [556-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [557-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [557-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [558-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [558-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [559-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [559-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [560-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [560-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [561-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [561-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [562-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [562-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [563-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [563-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [564-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [564-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [565-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [565-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [566-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [566-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [567-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [567-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [568-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [568-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [569-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [569-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [570-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [570-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [571-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [571-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [572-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [572-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [573-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [573-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [574-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [574-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [575-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [575-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [576-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [576-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [577-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [577-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [578-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [578-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [579-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [579-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [580-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [580-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [581-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [581-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [582-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [582-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [583-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [583-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [584-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [584-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [585-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [585-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [586-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [586-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [587-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [587-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [588-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [588-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [589-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [589-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [590-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [590-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [591-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [591-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [592-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [592-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [593-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [593-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [594-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [594-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [595-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [595-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [596-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [596-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [597-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [597-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [598-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [598-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [599-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [599-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [600-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [600-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [601-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [601-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [602-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [602-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [603-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [603-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [604-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [604-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [605-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [605-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [606-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [606-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [607-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [607-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [608-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [608-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [609-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [609-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [610-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [610-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [611-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [611-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [612-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [612-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [613-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [613-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [614-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [614-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [615-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [615-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [616-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [616-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [617-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [617-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [618-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [618-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [619-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [619-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [620-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [620-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [621-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [621-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [622-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [622-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [623-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [623-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [624-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [624-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [625-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [625-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [626-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [626-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [627-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [627-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [628-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [628-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [629-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [629-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [630-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [630-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [631-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [631-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [632-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [632-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [633-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [633-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [634-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [634-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [635-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [635-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [636-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [636-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [637-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [637-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [638-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [638-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [639-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [639-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [640-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [640-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [641-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [641-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [642-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [642-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [643-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [643-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [644-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [644-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [645-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [645-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [646-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [646-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [647-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [647-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [648-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [648-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [649-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [649-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [650-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [650-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [651-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [651-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [652-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [652-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [653-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [653-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [654-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [654-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [655-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [655-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [656-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [656-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [657-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [657-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [658-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [658-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [659-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [659-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [660-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [660-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [661-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [661-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [662-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [662-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [663-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [663-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [664-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [664-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [665-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [665-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [666-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [666-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [667-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [667-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [668-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [668-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [669-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [669-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [670-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [670-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [671-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [671-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [672-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [672-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [673-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [673-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [674-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [674-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [675-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [675-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [676-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [676-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [677-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [677-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [678-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [678-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [679-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [679-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [680-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [680-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [681-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [681-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [682-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [682-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [683-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [683-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [684-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [684-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [685-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [685-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [686-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [686-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [687-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [687-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [688-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [688-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [689-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [689-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [690-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [690-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [691-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [691-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [692-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [692-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [693-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [693-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [694-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [694-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [695-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [695-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [696-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [696-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [697-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [697-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [698-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [698-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [699-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [699-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [700-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [700-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [701-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [701-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [702-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [702-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [703-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [703-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [704-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [704-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [705-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [705-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [706-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [706-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [707-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [707-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [708-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [708-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [709-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [709-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [710-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [710-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [711-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [711-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [712-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [712-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [713-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [713-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [714-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [714-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [715-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [715-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [716-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [716-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [717-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [717-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [718-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [718-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [719-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [719-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [720-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [720-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [721-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [721-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [722-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [722-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [723-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [723-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [724-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [724-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [725-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [725-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [726-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [726-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [727-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [727-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [728-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [728-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [729-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [729-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [730-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [730-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [731-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [731-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [732-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [732-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [733-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [733-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [734-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [734-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [735-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [735-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [736-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [736-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [737-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [737-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [738-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [738-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [739-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [739-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [740-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [740-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [741-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [741-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [742-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [742-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [743-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [743-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [744-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [744-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [745-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [745-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [746-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [746-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [747-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [747-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [748-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [748-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [749-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [749-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [750-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [750-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [751-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [751-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [752-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [752-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [753-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [753-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [754-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [754-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [755-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [755-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [756-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [756-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [757-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [757-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [758-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [758-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [759-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [759-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [760-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [760-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [761-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [761-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [762-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [762-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [763-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [763-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [764-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [764-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [765-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [765-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [766-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [766-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [767-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [767-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [768-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [768-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [769-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [769-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [770-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [770-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [771-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [771-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [772-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [772-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [773-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [773-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [774-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [774-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [775-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [775-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [776-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [776-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [777-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [777-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [778-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [778-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [779-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [779-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [780-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [780-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [781-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [781-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [782-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [782-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [783-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [783-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [784-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [784-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [785-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [785-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [786-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [786-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [787-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [787-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [788-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [788-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [789-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [789-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [790-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [790-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [791-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [791-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [792-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [792-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [793-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [793-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [794-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [794-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [795-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [795-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [796-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [796-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [797-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [797-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [798-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [798-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [799-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [799-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [800-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [800-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [801-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [801-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [802-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [802-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [803-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [803-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [804-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [804-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [805-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [805-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [806-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [806-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [807-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [807-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [808-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [808-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [809-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [809-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [810-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [810-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [811-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [811-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [812-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [812-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [813-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [813-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [814-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [814-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [815-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [815-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [816-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [816-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [817-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [817-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [818-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [818-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [819-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [819-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [820-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [820-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [821-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [821-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [822-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [822-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [823-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [823-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [824-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [824-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [825-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [825-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [826-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [826-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [827-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [827-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [828-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [828-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [829-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [829-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [830-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [830-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [831-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [831-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [832-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [832-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [833-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [833-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [834-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [834-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [835-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [835-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [836-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [836-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [837-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [837-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [838-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [838-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [839-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [839-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [840-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [840-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [841-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [841-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [842-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [842-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [843-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [843-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [844-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [844-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [845-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [845-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [846-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [846-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [847-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [847-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [848-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [848-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [849-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [849-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [850-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [850-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [851-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [851-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [852-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [852-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [853-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [853-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [854-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [854-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [855-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [855-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [856-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [856-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [857-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [857-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [858-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [858-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [859-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [859-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [860-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [860-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [861-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [861-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [862-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [862-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [863-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [863-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [864-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [864-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [865-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [865-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [866-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [866-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [867-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [867-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [868-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [868-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [869-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [869-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [870-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [870-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [871-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [871-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [872-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [872-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [873-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [873-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [874-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [874-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [875-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [875-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [876-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [876-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [877-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [877-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [878-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [878-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [879-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [879-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [880-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [880-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [881-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [881-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [882-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [882-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [883-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [883-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [884-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [884-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [885-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [885-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [886-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [886-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [887-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [887-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [888-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [888-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [889-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [889-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [890-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [890-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [891-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [891-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [892-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [892-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [893-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [893-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [894-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [894-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [895-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [895-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [896-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [896-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [897-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [897-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [898-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [898-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [899-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [899-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [900-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [900-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [901-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [901-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [902-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [902-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [903-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [903-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [904-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [904-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [905-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [905-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [906-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [906-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [907-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [907-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [908-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [908-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [909-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [909-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [910-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [910-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [911-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [911-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [912-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [912-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [913-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [913-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [914-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [914-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [915-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [915-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [916-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [916-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [917-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [917-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [918-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [918-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [919-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [919-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [920-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [920-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [921-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [921-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [922-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [922-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [923-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [923-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [924-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [924-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [925-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [925-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [926-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [926-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [927-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [927-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [928-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [928-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [929-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [929-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [930-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [930-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [931-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [931-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [932-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [932-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [933-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [933-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [934-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [934-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [935-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [935-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [936-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [936-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [937-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [937-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [938-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [938-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [939-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [939-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [940-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [940-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [941-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [941-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [942-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [942-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [943-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [943-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [944-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [944-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [945-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [945-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [946-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [946-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [947-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [947-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [948-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [948-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [949-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [949-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [950-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [950-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [951-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [951-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [952-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [952-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [953-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [953-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [954-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [954-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [955-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [955-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [956-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [956-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [957-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [957-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [958-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [958-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [959-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [959-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [960-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [960-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [961-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [961-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [962-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [962-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [963-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [963-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [964-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [964-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [965-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [965-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [966-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [966-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [967-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [967-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [968-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [968-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [969-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [969-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [970-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [970-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [971-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [971-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [972-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [972-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [973-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [973-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [974-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [974-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [975-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [975-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [976-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [976-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [977-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [977-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [978-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [978-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [979-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [979-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [980-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [980-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [981-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [981-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [982-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [982-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [983-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [983-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [984-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [984-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [985-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [985-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [986-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [986-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [987-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [987-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [988-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [988-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [989-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [989-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [990-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [990-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [991-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [991-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [992-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [992-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [993-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [993-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [994-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [994-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [995-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [995-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [996-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [996-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [997-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [997-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [998-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [998-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [999-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [999-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1000-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1000-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1001-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1001-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1002-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1002-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1003-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1003-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1004-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1004-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1005-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1005-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1006-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1006-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1007-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1007-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1008-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1008-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1009-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1009-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1010-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1010-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1011-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1011-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1012-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1012-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1013-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1013-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1014-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1014-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1015-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1015-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1016-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1016-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1017-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1017-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1018-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1018-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1019-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1019-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1020-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1020-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1021-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1021-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1022-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1022-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1023-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1023-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1024-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1024-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1025-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1025-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1026-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1026-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1027-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1027-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1028-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1028-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1029-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1029-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1030-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1030-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1031-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1031-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1032-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1032-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1033-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1033-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1034-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1034-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1035-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1035-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1036-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1036-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1037-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1037-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1038-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1038-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1039-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1039-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1040-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1040-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1041-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1041-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1042-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1042-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1043-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1043-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1044-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1044-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1045-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1045-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1046-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1046-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1047-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1047-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1048-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1048-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1049-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1049-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1050-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1050-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1051-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1051-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1052-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1052-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1053-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1053-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1054-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1054-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1055-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1055-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1056-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1056-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1057-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1057-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1058-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1058-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1059-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1059-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1060-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1060-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1061-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1061-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1062-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1062-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1063-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1063-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1064-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1064-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1065-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1065-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1066-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1066-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1067-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1067-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1068-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1068-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1069-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1069-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1070-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1070-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1071-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1071-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1072-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1072-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1073-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1073-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1074-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1074-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1075-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1075-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1076-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1076-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1077-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1077-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1078-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1078-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1079-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1079-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1080-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1080-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1081-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1081-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1082-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1082-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1083-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1083-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1084-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1084-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1085-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1085-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1086-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1086-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1087-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1087-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1088-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1088-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1089-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1089-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1090-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1090-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1091-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1091-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1092-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1092-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1093-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1093-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1094-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1094-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1095-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1095-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1096-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1096-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1097-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1097-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1098-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1098-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1099-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1099-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1100-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1100-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1101-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1101-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1102-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1102-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1103-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1103-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1104-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1104-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1105-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1105-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1106-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1106-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1107-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1107-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1108-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1108-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1109-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1109-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1110-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1110-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1111-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1111-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1112-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1112-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1113-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1113-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1114-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1114-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1115-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1115-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1116-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1116-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1117-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1117-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1118-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1118-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1119-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1119-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1120-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1120-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1121-1] 2019-08-31 16:39:42: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:39:42+00:00 lcm-34-189 pgpool[11631]: [1121-2] 2019-08-31 16:39:42: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:39:43+00:00 lcm-34-189 pgpool[11631]: [1122-1] 2019-08-31 16:39:43: pid 11631: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY] 2019-08-31T16:39:43+00:00 lcm-34-189 pgpool[11630]: [295-1] 2019-08-31 16:39:43: pid 11630: LOG: Pgpool-II parent process received watchdog quorum change signal from watchdog 2019-08-31T16:39:43+00:00 lcm-34-189 pgpool[11631]: [1123-1] 2019-08-31 16:39:43: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:48+00:00 lcm-34-189 pgpool[11631]: [1124-1] 2019-08-31 16:39:48: pid 11631: LOG: successfully joined the watchdog cluster as standby node 2019-08-31T16:39:48+00:00 lcm-34-189 pgpool[11631]: [1124-2] 2019-08-31 16:39:48: pid 11631: DETAIL: our join coordinator request is accepted by cluster leader node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:39:48+00:00 lcm-34-189 pgpool[11631]: [1125-1] 2019-08-31 16:39:48: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:48+00:00 lcm-34-189 pgpool[11630]: [296-1] 2019-08-31 16:39:48: pid 11630: LOG: we have joined the watchdog cluster as STANDBY node 2019-08-31T16:39:48+00:00 lcm-34-189 pgpool[11630]: [296-2] 2019-08-31 16:39:48: pid 11630: DETAIL: syncing the backend states from the MASTER watchdog node 2019-08-31T16:39:48+00:00 lcm-34-189 pgpool[11631]: [1126-1] 2019-08-31 16:39:48: pid 11631: LOG: new IPC connection received 2019-08-31T16:39:48+00:00 lcm-34-189 pgpool[11631]: [1127-1] 2019-08-31 16:39:48: pid 11631: LOG: received the get data request from local pgpool-II on IPC interface 2019-08-31T16:39:48+00:00 lcm-34-189 pgpool[11631]: [1128-1] 2019-08-31 16:39:48: pid 11631: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to master watchdog node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:39:48+00:00 lcm-34-189 pgpool[11631]: [1128-2] 2019-08-31 16:39:48: pid 11631: DETAIL: waiting for the reply... 2019-08-31T16:39:56+00:00 lcm-34-189 pgpool[11630]: [297-1] 2019-08-31 16:39:56: pid 11630: WARNING: get backend node status from master watchdog failed 2019-08-31T16:39:56+00:00 lcm-34-189 pgpool[11630]: [297-2] 2019-08-31 16:39:56: pid 11630: DETAIL: ipc command timeout 2019-08-31T16:39:56+00:00 lcm-34-189 pgpool[11630]: [298-1] 2019-08-31 16:39:56: pid 11630: WARNING: failed to get the backend status from the master watchdog node 2019-08-31T16:39:56+00:00 lcm-34-189 pgpool[11630]: [298-2] 2019-08-31 16:39:56: pid 11630: DETAIL: using the local backend node status 2019-08-31T16:39:56+00:00 lcm-34-189 pgpool[11631]: [1129-1] 2019-08-31 16:39:56: pid 11631: LOG: read from socket failed, remote end closed the connection 2019-08-31T16:40:28+00:00 lcm-34-189 pgpool[22167]: [220-1] 2019-08-31 16:40:28: pid 22167: LOG: md5 authentication successful with frontend 2019-08-31T16:41:01+00:00 lcm-34-189 pgpool[21660]: [146-1] 2019-08-31 16:41:01: pid 21660: LOG: forked new pcp worker, pid=22412 socket=8 2019-08-31T16:41:01+00:00 lcm-34-189 pgpool[11631]: [1130-1] 2019-08-31 16:41:01: pid 11631: LOG: new IPC connection received 2019-08-31T16:41:01+00:00 lcm-34-189 pgpool[21660]: [147-1] 2019-08-31 16:41:01: pid 21660: LOG: PCP process with pid: 22412 exit with SUCCESS. 2019-08-31T16:41:01+00:00 lcm-34-189 pgpool[21660]: [148-1] 2019-08-31 16:41:01: pid 21660: LOG: PCP process with pid: 22412 exits with status 0 2019-08-31T16:41:16+00:00 lcm-34-189 pgpool[11631]: [1131-1] 2019-08-31 16:41:16: pid 11631: LOG: "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" is our coordinator node, but "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" is also announcing as a coordinator 2019-08-31T16:41:16+00:00 lcm-34-189 pgpool[11631]: [1131-2] 2019-08-31 16:41:16: pid 11631: DETAIL: broadcasting the cluster in split-brain message 2019-08-31T16:41:16+00:00 lcm-34-189 pgpool[11631]: [1132-1] 2019-08-31 16:41:16: pid 11631: WARNING: we have not received a beacon message from master node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" and it has not replied to our info request 2019-08-31T16:41:16+00:00 lcm-34-189 pgpool[11631]: [1132-2] 2019-08-31 16:41:16: pid 11631: DETAIL: re-initializing the cluster 2019-08-31T16:41:16+00:00 lcm-34-189 pgpool[11631]: [1133-1] 2019-08-31 16:41:16: pid 11631: LOG: watchdog node state changed from [STANDBY] to [JOINING] 2019-08-31T16:41:16+00:00 lcm-34-189 pgpool[11631]: [1134-1] 2019-08-31 16:41:16: pid 11631: LOG: unassigning the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" from watchdog cluster master 2019-08-31T16:41:16+00:00 lcm-34-189 pgpool[11631]: [1135-1] 2019-08-31 16:41:16: pid 11631: LOG: master/coordinator node "lcm-34-190.dev.lcm.local:9999 Linux lcm-34-190.dev.lcm.local" decided to resigning from master, probably because of split-brain 2019-08-31T16:41:16+00:00 lcm-34-189 pgpool[11631]: [1135-2] 2019-08-31 16:41:16: pid 11631: DETAIL: but it was not our coordinator/master anyway. ignoring the message 2019-08-31T16:41:18+00:00 lcm-34-189 pgpool[11631]: [1136-1] 2019-08-31 16:41:18: pid 11631: LOG: watchdog node state changed from [JOINING] to [PARTICIPATING IN ELECTION] 2019-08-31T16:41:18+00:00 lcm-34-189 pgpool[11631]: [1137-1] 2019-08-31 16:41:18: pid 11631: LOG: watchdog node state changed from [PARTICIPATING IN ELECTION] to [JOINING] 2019-08-31T16:41:18+00:00 lcm-34-189 pgpool[11631]: [1138-1] 2019-08-31 16:41:18: pid 11631: LOG: setting the remote node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" as watchdog cluster master 2019-08-31T16:41:18+00:00 lcm-34-189 pgpool[11631]: [1139-1] 2019-08-31 16:41:18: pid 11631: LOG: failed to forward data message to IPC command socket 2019-08-31T16:41:18+00:00 lcm-34-189 pgpool[11631]: [1140-1] 2019-08-31 16:41:18: pid 11631: LOG: watchdog node state changed from [JOINING] to [INITIALIZING] 2019-08-31T16:41:18+00:00 lcm-34-189 pgpool[11630]: [299-1] 2019-08-31 16:41:18: pid 11630: LOG: Pgpool-II parent process received watchdog quorum change signal from watchdog 2019-08-31T16:41:18+00:00 lcm-34-189 pgpool[11631]: [1141-1] 2019-08-31 16:41:18: pid 11631: LOG: new IPC connection received 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11631]: [1142-1] 2019-08-31 16:41:19: pid 11631: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY] 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11631]: [1143-1] 2019-08-31 16:41:19: pid 11631: LOG: successfully joined the watchdog cluster as standby node 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11631]: [1143-2] 2019-08-31 16:41:19: pid 11631: DETAIL: our join coordinator request is accepted by cluster leader node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11631]: [1144-1] 2019-08-31 16:41:19: pid 11631: LOG: new IPC connection received 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [300-1] 2019-08-31 16:41:19: pid 11630: LOG: we have joined the watchdog cluster as STANDBY node 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [300-2] 2019-08-31 16:41:19: pid 11630: DETAIL: syncing the backend states from the MASTER watchdog node 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11631]: [1145-1] 2019-08-31 16:41:19: pid 11631: LOG: new IPC connection received 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11631]: [1146-1] 2019-08-31 16:41:19: pid 11631: LOG: received the get data request from local pgpool-II on IPC interface 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11631]: [1147-1] 2019-08-31 16:41:19: pid 11631: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to master watchdog node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11631]: [1147-2] 2019-08-31 16:41:19: pid 11631: DETAIL: waiting for the reply... 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [301-1] 2019-08-31 16:41:19: pid 11630: LOG: master watchdog node "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" returned status for 3 backend nodes 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [302-1] 2019-08-31 16:41:19: pid 11630: LOG: backend:0 is set to UP status 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [302-2] 2019-08-31 16:41:19: pid 11630: DETAIL: backend:0 is UP on cluster master "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [303-1] 2019-08-31 16:41:19: pid 11630: LOG: backend:1 is set to UP status 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [303-2] 2019-08-31 16:41:19: pid 11630: DETAIL: backend:1 is UP on cluster master "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [304-1] 2019-08-31 16:41:19: pid 11630: LOG: backend:2 is set to UP status 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [304-2] 2019-08-31 16:41:19: pid 11630: DETAIL: backend:2 is UP on cluster master "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [305-1] 2019-08-31 16:41:19: pid 11630: LOG: backend nodes status remains same after the sync from "lcm-34-188.dev.lcm.local:9999 Linux lcm-34-188.dev.lcm.local" 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [306-1] 2019-08-31 16:41:19: pid 11630: LOG: Pgpool-II parent process received watchdog quorum change signal from watchdog 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11631]: [1148-1] 2019-08-31 16:41:19: pid 11631: LOG: new IPC connection received 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [307-1] 2019-08-31 16:41:19: pid 11630: LOG: watchdog cluster now holds the quorum 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11630]: [307-2] 2019-08-31 16:41:19: pid 11630: DETAIL: updating the state of quarantine backend nodes 2019-08-31T16:41:19+00:00 lcm-34-189 pgpool[11631]: [1149-1] 2019-08-31 16:41:19: pid 11631: LOG: new IPC connection received