[pgpool-general: 8062] Re: Possible race condition during startup causing node to enter network isolation
Emond Papegaaij
emond.papegaaij at gmail.com
Fri Apr 1 16:03:29 JST 2022
Hi,
Unfortunately, this issue still pops up every once in a while. We are now
running 4.3.1. In our latest failure, the issue occured in a simple restart
of all services on node 1, with node 3 being the leader. Pgpool on node 1
tries to rejoin the cluster, but gets rejected over and over again. Node 3
reports that 'only life-check process can mark this node alive again'. I've
attached the full logs of both node 1 and 3. The configuration hasn't
changed since last time.
Best regards,
Emond
On Mon, Nov 29, 2021 at 4:12 PM Emond Papegaaij <emond.papegaaij at gmail.com>
wrote:
> On Mon, Nov 29, 2021 at 3:55 PM Bo Peng <pengbo at sraoss.co.jp> wrote:
>
>> Thank you for your test.
>>
>> Because we did some bug fix for watchdog since 4.2.4, it might be an
>> upgrade issue.
>> If you can reproduce this issue in 4.2.6, could you share the pgpool logs
>> of all nodes?
>>
>
> I'll continue to monitor the tests. If one fails again, I'll share the
> logs. As I said, this could take some time, because the failure only occurs
> about once a week. Thanks for your help so far.
>
> Best regards,
> Emond
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20220401/1518673d/attachment-0001.htm>
-------------- next part --------------
2022-04-01 05:59:29: pid 1: LOG: Backend status file /var/run/postgresql/pgpool_status does not exist
2022-04-01 05:59:29: pid 1: LOG: health_check_stats_shared_memory_size: requested size: 12288
2022-04-01 05:59:29: pid 1: LOG: memory cache initialized
2022-04-01 05:59:29: pid 1: DETAIL: memcache blocks :64
2022-04-01 05:59:29: pid 1: LOG: allocating (136981880) bytes of shared memory segment
2022-04-01 05:59:29: pid 1: LOG: allocating shared memory segment of size: 136981880
2022-04-01 05:59:29: pid 1: LOG: health_check_stats_shared_memory_size: requested size: 12288
2022-04-01 05:59:29: pid 1: LOG: health_check_stats_shared_memory_size: requested size: 12288
2022-04-01 05:59:29: pid 1: LOG: memory cache initialized
2022-04-01 05:59:29: pid 1: DETAIL: memcache blocks :64
2022-04-01 05:59:29: pid 1: LOG: pool_discard_oid_maps: discarded memqcache oid maps
2022-04-01 05:59:29: pid 1: LOG: waiting for watchdog to initialize
2022-04-01 05:59:29: pid 13: LOG: setting the local watchdog node name to "172.29.30.1:5432 Linux 43a0ec8556bb"
2022-04-01 05:59:29: pid 13: LOG: watchdog cluster is configured with 2 remote nodes
2022-04-01 05:59:29: pid 13: LOG: watchdog remote node:0 on 172.29.30.2:9009
2022-04-01 05:59:29: pid 13: LOG: watchdog remote node:1 on 172.29.30.3:9009
2022-04-01 05:59:29: pid 13: LOG: interface monitoring is disabled in watchdog
2022-04-01 05:59:29: pid 13: LOG: watchdog node state changed from [DEAD] to [LOADING]
2022-04-01 05:59:29: pid 13: LOG: new outbound connection to 172.29.30.2:9009
2022-04-01 05:59:29: pid 13: LOG: new outbound connection to 172.29.30.3:9009
2022-04-01 05:59:29: pid 13: LOG: watchdog node state changed from [LOADING] to [INITIALIZING]
2022-04-01 05:59:29: pid 13: LOG: new watchdog node connection is received from "172.29.30.2:25773"
2022-04-01 05:59:29: pid 13: LOG: new node joined the cluster hostname:"172.29.30.2" port:9009 pgpool_port:5432
2022-04-01 05:59:29: pid 13: DETAIL: Pgpool-II version:"4.3.1" watchdog messaging version: 1.2
2022-04-01 05:59:29: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 05:59:29: pid 13: LOG: new watchdog node connection is received from "172.29.30.3:33980"
2022-04-01 05:59:29: pid 13: LOG: new node joined the cluster hostname:"172.29.30.3" port:9009 pgpool_port:5432
2022-04-01 05:59:29: pid 13: DETAIL: Pgpool-II version:"4.3.1" watchdog messaging version: 1.2
2022-04-01 05:59:30: pid 13: LOG: read from socket failed, remote end closed the connection
2022-04-01 05:59:30: pid 13: LOG: client socket of 172.29.30.3:5432 Linux 3a3112e1320b is closed
2022-04-01 05:59:30: pid 13: LOG: remote node "172.29.30.3:5432 Linux 3a3112e1320b" is reporting that it has lost us
2022-04-01 05:59:30: pid 13: LOG: read from socket failed, remote end closed the connection
2022-04-01 05:59:30: pid 13: LOG: outbound socket of 172.29.30.3:5432 Linux 3a3112e1320b is closed
2022-04-01 05:59:30: pid 13: LOG: remote node "172.29.30.3:5432 Linux 3a3112e1320b" is not reachable
2022-04-01 05:59:30: pid 13: DETAIL: marking the node as lost
2022-04-01 05:59:30: pid 13: LOG: remote node "172.29.30.3:5432 Linux 3a3112e1320b" is lost
2022-04-01 05:59:30: pid 13: LOG: watchdog cluster has lost the coordinator node
2022-04-01 05:59:30: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 05:59:31: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDING FOR LEADER]
2022-04-01 05:59:31: pid 13: LOG: our stand for coordinator request is rejected by node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:59:31: pid 13: DETAIL: we might be in partial network isolation and cluster already have a valid leader
2022-04-01 05:59:31: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 05:59:31: pid 13: LOG: watchdog node state changed from [STANDING FOR LEADER] to [NETWORK ISOLATION]
2022-04-01 05:59:41: pid 13: LOG: new watchdog node connection is received from "172.29.30.3:189"
2022-04-01 05:59:41: pid 13: LOG: new node joined the cluster hostname:"172.29.30.3" port:9009 pgpool_port:5432
2022-04-01 05:59:41: pid 13: DETAIL: Pgpool-II version:"4.3.1" watchdog messaging version: 1.2
2022-04-01 05:59:41: pid 13: LOG: The newly joined node:"172.29.30.3:5432 Linux 3a3112e1320b" had left the cluster because it was lost
2022-04-01 05:59:41: pid 13: DETAIL: lost reason was "NOT REACHABLE" and startup time diff = 1
2022-04-01 05:59:41: pid 13: LOG: new outbound connection to 172.29.30.3:9009
2022-04-01 05:59:42: pid 13: LOG: trying again to join the cluster
2022-04-01 05:59:42: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 05:59:42: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 05:59:42: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 05:59:43: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 05:59:43: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 05:59:43: pid 13: HINT: rejoining the cluster.
2022-04-01 05:59:43: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 05:59:43: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 05:59:43: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 05:59:53: pid 13: LOG: trying again to join the cluster
2022-04-01 05:59:53: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 05:59:53: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 05:59:53: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 05:59:53: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 05:59:54: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 05:59:54: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 05:59:54: pid 13: HINT: rejoining the cluster.
2022-04-01 05:59:54: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 05:59:54: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 05:59:54: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:00:04: pid 13: LOG: trying again to join the cluster
2022-04-01 06:00:04: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:00:04: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:00:04: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:00:04: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:00:05: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:00:05: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:00:05: pid 13: HINT: rejoining the cluster.
2022-04-01 06:00:05: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:00:05: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:00:05: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:00:15: pid 13: LOG: trying again to join the cluster
2022-04-01 06:00:15: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:00:15: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:00:15: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:00:15: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:00:16: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:00:16: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:00:16: pid 13: HINT: rejoining the cluster.
2022-04-01 06:00:16: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:00:16: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:00:16: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:00:26: pid 13: LOG: trying again to join the cluster
2022-04-01 06:00:26: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:00:26: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:00:26: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:00:26: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:00:27: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:00:27: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:00:27: pid 13: HINT: rejoining the cluster.
2022-04-01 06:00:27: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:00:27: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:00:27: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:00:37: pid 13: LOG: trying again to join the cluster
2022-04-01 06:00:37: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:00:37: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:00:37: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:00:37: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:00:38: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:00:38: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:00:38: pid 13: HINT: rejoining the cluster.
2022-04-01 06:00:38: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:00:38: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:00:38: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:00:49: pid 13: LOG: trying again to join the cluster
2022-04-01 06:00:49: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:00:49: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:00:49: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:00:49: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:00:50: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:00:50: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:00:50: pid 13: HINT: rejoining the cluster.
2022-04-01 06:00:50: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:00:50: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:00:50: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:01:00: pid 13: LOG: trying again to join the cluster
2022-04-01 06:01:00: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:01:00: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:01:00: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:01:00: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:01:01: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:01:01: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:01:01: pid 13: HINT: rejoining the cluster.
2022-04-01 06:01:01: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:01:01: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:01:01: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:01:11: pid 13: LOG: trying again to join the cluster
2022-04-01 06:01:11: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:01:11: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:01:11: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:01:11: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:01:12: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:01:12: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:01:12: pid 13: HINT: rejoining the cluster.
2022-04-01 06:01:12: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:01:12: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:01:12: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:01:22: pid 13: LOG: trying again to join the cluster
2022-04-01 06:01:22: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:01:22: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:01:22: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:01:22: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:01:23: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:01:23: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:01:23: pid 13: HINT: rejoining the cluster.
2022-04-01 06:01:23: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:01:23: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:01:23: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:01:33: pid 13: LOG: trying again to join the cluster
2022-04-01 06:01:33: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:01:33: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:01:33: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:01:33: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:01:34: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:01:34: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:01:34: pid 13: HINT: rejoining the cluster.
2022-04-01 06:01:34: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:01:34: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:01:34: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:01:44: pid 13: LOG: trying again to join the cluster
2022-04-01 06:01:44: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:01:44: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:01:44: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:01:44: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:01:45: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:01:45: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:01:45: pid 13: HINT: rejoining the cluster.
2022-04-01 06:01:45: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:01:45: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:01:45: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:01:55: pid 13: LOG: trying again to join the cluster
2022-04-01 06:01:55: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:01:55: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:01:55: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:01:55: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:01:56: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:01:56: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:01:56: pid 13: HINT: rejoining the cluster.
2022-04-01 06:01:56: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:01:56: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:01:56: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:02:06: pid 13: LOG: trying again to join the cluster
2022-04-01 06:02:06: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:02:06: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:02:06: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:02:06: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:02:07: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:02:07: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:02:07: pid 13: HINT: rejoining the cluster.
2022-04-01 06:02:07: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:02:07: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:02:07: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:02:17: pid 13: LOG: trying again to join the cluster
2022-04-01 06:02:17: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:02:17: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:02:17: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:02:17: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:02:18: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:02:18: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:02:18: pid 13: HINT: rejoining the cluster.
2022-04-01 06:02:18: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:02:18: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:02:18: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:02:28: pid 13: LOG: trying again to join the cluster
2022-04-01 06:02:28: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:02:28: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:02:28: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:02:28: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:02:29: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:02:29: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:02:29: pid 13: HINT: rejoining the cluster.
2022-04-01 06:02:29: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:02:29: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:02:29: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:02:39: pid 13: LOG: trying again to join the cluster
2022-04-01 06:02:39: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:02:39: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:02:39: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:02:39: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:02:40: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:02:40: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:02:40: pid 13: HINT: rejoining the cluster.
2022-04-01 06:02:40: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:02:40: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:02:40: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:02:50: pid 13: LOG: trying again to join the cluster
2022-04-01 06:02:50: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:02:50: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:02:50: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:02:50: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:02:51: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:02:51: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:02:51: pid 13: HINT: rejoining the cluster.
2022-04-01 06:02:51: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:02:51: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:02:51: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:03:01: pid 13: LOG: trying again to join the cluster
2022-04-01 06:03:01: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:03:01: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:03:01: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:03:01: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:03:02: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:03:02: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:03:02: pid 13: HINT: rejoining the cluster.
2022-04-01 06:03:02: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:03:02: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:03:02: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:03:13: pid 13: LOG: trying again to join the cluster
2022-04-01 06:03:13: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:03:13: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:03:13: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:03:13: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:03:14: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:03:14: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:03:14: pid 13: HINT: rejoining the cluster.
2022-04-01 06:03:14: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:03:14: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:03:14: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:03:24: pid 13: LOG: trying again to join the cluster
2022-04-01 06:03:24: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:03:24: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:03:24: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:03:24: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:03:25: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:03:25: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:03:25: pid 13: HINT: rejoining the cluster.
2022-04-01 06:03:25: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:03:25: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:03:25: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:03:35: pid 13: LOG: trying again to join the cluster
2022-04-01 06:03:35: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:03:35: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:03:35: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:03:35: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:03:36: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:03:36: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:03:36: pid 13: HINT: rejoining the cluster.
2022-04-01 06:03:36: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:03:36: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:03:36: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:03:46: pid 13: LOG: trying again to join the cluster
2022-04-01 06:03:46: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:03:46: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:03:46: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:03:46: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:03:47: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:03:47: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:03:47: pid 13: HINT: rejoining the cluster.
2022-04-01 06:03:47: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:03:47: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:03:47: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:03:57: pid 13: LOG: trying again to join the cluster
2022-04-01 06:03:57: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:03:57: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:03:57: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:03:57: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:03:58: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:03:58: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:03:58: pid 13: HINT: rejoining the cluster.
2022-04-01 06:03:58: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:03:58: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:03:58: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:04:08: pid 13: LOG: trying again to join the cluster
2022-04-01 06:04:08: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:04:08: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:04:08: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:04:08: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:04:09: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:04:09: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:04:09: pid 13: HINT: rejoining the cluster.
2022-04-01 06:04:09: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:04:09: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:04:09: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:04:19: pid 13: LOG: trying again to join the cluster
2022-04-01 06:04:19: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:04:19: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:04:19: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:04:19: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:04:20: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:04:20: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:04:20: pid 13: HINT: rejoining the cluster.
2022-04-01 06:04:20: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:04:20: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:04:20: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:04:30: pid 13: LOG: trying again to join the cluster
2022-04-01 06:04:30: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:04:30: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:04:30: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:04:30: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:04:31: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:04:31: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:04:31: pid 13: HINT: rejoining the cluster.
2022-04-01 06:04:31: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:04:31: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:04:31: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:04:41: pid 13: LOG: trying again to join the cluster
2022-04-01 06:04:41: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:04:41: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:04:41: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:04:41: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:04:42: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:04:42: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:04:42: pid 13: HINT: rejoining the cluster.
2022-04-01 06:04:42: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:04:42: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:04:42: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:04:52: pid 13: LOG: trying again to join the cluster
2022-04-01 06:04:52: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:04:52: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:04:52: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:04:52: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:04:53: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:04:53: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:04:53: pid 13: HINT: rejoining the cluster.
2022-04-01 06:04:53: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:04:53: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:04:53: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:05:03: pid 13: LOG: trying again to join the cluster
2022-04-01 06:05:03: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:05:03: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:05:03: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:05:03: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:05:04: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:05:04: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:05:04: pid 13: HINT: rejoining the cluster.
2022-04-01 06:05:04: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:05:04: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:05:04: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:05:14: pid 13: LOG: trying again to join the cluster
2022-04-01 06:05:14: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:05:14: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:05:14: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:05:14: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:05:15: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:05:15: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:05:15: pid 13: HINT: rejoining the cluster.
2022-04-01 06:05:15: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:05:15: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:05:15: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:05:25: pid 13: LOG: trying again to join the cluster
2022-04-01 06:05:25: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:05:25: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:05:25: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:05:25: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:05:26: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:05:26: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:05:26: pid 13: HINT: rejoining the cluster.
2022-04-01 06:05:26: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:05:26: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:05:26: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:05:36: pid 13: LOG: trying again to join the cluster
2022-04-01 06:05:36: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:05:36: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:05:36: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:05:36: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:05:37: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:05:37: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:05:37: pid 13: HINT: rejoining the cluster.
2022-04-01 06:05:37: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:05:37: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:05:37: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:05:48: pid 13: LOG: trying again to join the cluster
2022-04-01 06:05:48: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:05:48: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:05:48: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:05:48: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:05:49: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:05:49: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:05:49: pid 13: HINT: rejoining the cluster.
2022-04-01 06:05:49: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:05:49: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:05:49: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:05:59: pid 13: LOG: trying again to join the cluster
2022-04-01 06:05:59: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:05:59: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:05:59: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:05:59: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:06:00: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:06:00: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:06:00: pid 13: HINT: rejoining the cluster.
2022-04-01 06:06:00: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:06:00: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:06:00: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:06:10: pid 13: LOG: trying again to join the cluster
2022-04-01 06:06:10: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:06:10: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:06:10: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:06:10: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:06:11: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:06:11: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:06:11: pid 13: HINT: rejoining the cluster.
2022-04-01 06:06:11: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:06:11: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:06:11: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:06:21: pid 13: LOG: trying again to join the cluster
2022-04-01 06:06:21: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:06:21: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:06:21: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:06:21: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:06:22: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:06:22: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:06:22: pid 13: HINT: rejoining the cluster.
2022-04-01 06:06:22: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:06:22: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:06:22: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:06:32: pid 13: LOG: trying again to join the cluster
2022-04-01 06:06:32: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:06:32: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:06:32: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:06:32: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:06:33: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:06:33: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:06:33: pid 13: HINT: rejoining the cluster.
2022-04-01 06:06:33: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:06:33: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:06:33: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:06:43: pid 13: LOG: trying again to join the cluster
2022-04-01 06:06:43: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:06:43: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:06:43: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:06:43: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:06:44: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:06:44: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:06:44: pid 13: HINT: rejoining the cluster.
2022-04-01 06:06:44: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:06:44: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:06:44: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:06:54: pid 13: LOG: trying again to join the cluster
2022-04-01 06:06:54: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:06:54: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:06:54: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:06:54: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:06:55: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:06:55: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:06:55: pid 13: HINT: rejoining the cluster.
2022-04-01 06:06:55: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:06:55: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:06:55: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:07:05: pid 13: LOG: trying again to join the cluster
2022-04-01 06:07:05: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:07:05: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:07:05: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:07:05: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:07:06: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:07:06: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:07:06: pid 13: HINT: rejoining the cluster.
2022-04-01 06:07:06: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:07:06: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:07:06: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:07:16: pid 13: LOG: trying again to join the cluster
2022-04-01 06:07:16: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:07:16: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:07:16: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:07:16: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:07:17: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:07:17: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:07:17: pid 13: HINT: rejoining the cluster.
2022-04-01 06:07:17: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:07:17: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:07:17: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:07:27: pid 13: LOG: trying again to join the cluster
2022-04-01 06:07:27: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:07:27: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:07:27: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:07:27: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:07:28: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:07:28: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:07:28: pid 13: HINT: rejoining the cluster.
2022-04-01 06:07:28: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:07:28: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:07:28: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:07:38: pid 13: LOG: trying again to join the cluster
2022-04-01 06:07:38: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:07:38: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:07:38: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:07:38: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:07:39: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:07:39: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:07:39: pid 13: HINT: rejoining the cluster.
2022-04-01 06:07:39: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:07:39: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:07:39: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:07:49: pid 13: LOG: trying again to join the cluster
2022-04-01 06:07:49: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:07:49: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:07:49: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:07:49: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:07:50: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:07:50: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:07:50: pid 13: HINT: rejoining the cluster.
2022-04-01 06:07:50: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:07:50: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:07:50: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:08:00: pid 13: LOG: trying again to join the cluster
2022-04-01 06:08:00: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:08:00: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:08:01: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:08:01: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:08:02: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:08:02: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:08:02: pid 13: HINT: rejoining the cluster.
2022-04-01 06:08:02: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:08:02: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:08:02: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:08:12: pid 13: LOG: trying again to join the cluster
2022-04-01 06:08:12: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:08:12: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:08:12: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:08:12: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:08:13: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:08:13: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:08:13: pid 13: HINT: rejoining the cluster.
2022-04-01 06:08:13: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:08:13: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:08:13: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:08:23: pid 13: LOG: trying again to join the cluster
2022-04-01 06:08:23: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:08:23: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:08:23: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:08:23: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:08:24: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:08:24: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:08:24: pid 13: HINT: rejoining the cluster.
2022-04-01 06:08:24: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:08:24: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:08:24: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:08:34: pid 13: LOG: trying again to join the cluster
2022-04-01 06:08:34: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:08:34: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:08:34: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:08:34: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:08:35: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:08:35: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:08:35: pid 13: HINT: rejoining the cluster.
2022-04-01 06:08:35: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:08:35: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:08:35: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:08:45: pid 13: LOG: trying again to join the cluster
2022-04-01 06:08:45: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:08:45: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:08:45: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:08:45: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:08:46: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:08:46: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:08:46: pid 13: HINT: rejoining the cluster.
2022-04-01 06:08:46: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:08:46: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:08:46: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:08:56: pid 13: LOG: trying again to join the cluster
2022-04-01 06:08:56: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:08:56: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:08:56: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:08:56: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:08:57: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:08:57: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:08:57: pid 13: HINT: rejoining the cluster.
2022-04-01 06:08:57: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:08:57: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:08:57: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:09:07: pid 13: LOG: trying again to join the cluster
2022-04-01 06:09:07: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:09:07: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:09:07: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:09:07: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:09:08: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:09:08: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:09:08: pid 13: HINT: rejoining the cluster.
2022-04-01 06:09:08: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:09:08: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:09:08: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:09:18: pid 13: LOG: trying again to join the cluster
2022-04-01 06:09:18: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:09:18: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:09:18: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:09:18: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:09:19: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:09:19: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:09:19: pid 13: HINT: rejoining the cluster.
2022-04-01 06:09:19: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:09:19: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:09:19: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:09:29: pid 13: LOG: trying again to join the cluster
2022-04-01 06:09:29: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:09:29: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:09:29: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:09:29: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:09:30: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:09:30: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:09:30: pid 13: HINT: rejoining the cluster.
2022-04-01 06:09:30: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:09:30: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:09:30: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:09:40: pid 13: LOG: trying again to join the cluster
2022-04-01 06:09:40: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:09:40: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:09:40: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:09:40: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:09:41: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:09:41: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:09:41: pid 13: HINT: rejoining the cluster.
2022-04-01 06:09:41: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:09:41: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:09:41: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:09:51: pid 13: LOG: trying again to join the cluster
2022-04-01 06:09:51: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:09:51: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:09:51: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:09:51: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:09:52: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:09:52: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:09:52: pid 13: HINT: rejoining the cluster.
2022-04-01 06:09:52: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:09:52: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:09:52: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:10:02: pid 13: LOG: trying again to join the cluster
2022-04-01 06:10:02: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:10:02: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:10:02: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:10:02: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:10:03: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:10:03: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:10:03: pid 13: HINT: rejoining the cluster.
2022-04-01 06:10:03: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:10:03: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:10:03: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
2022-04-01 06:10:13: pid 13: LOG: trying again to join the cluster
2022-04-01 06:10:13: pid 13: LOG: watchdog node state changed from [NETWORK ISOLATION] to [JOINING]
2022-04-01 06:10:13: pid 13: LOG: removing the remote node "172.29.30.3:5432 Linux 3a3112e1320b" from watchdog cluster leader
2022-04-01 06:10:13: pid 13: LOG: setting the remote node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 06:10:13: pid 13: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 06:10:14: pid 13: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 06:10:14: pid 13: NOTICE: our join coordinator is rejected by node "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 06:10:14: pid 13: HINT: rejoining the cluster.
2022-04-01 06:10:14: pid 13: LOG: leader node "172.29.30.3:5432 Linux 3a3112e1320b" thinks we are lost, and "172.29.30.3:5432 Linux 3a3112e1320b" is not letting us join
2022-04-01 06:10:14: pid 13: HINT: please verify the watchdog life-check and network is working properly
2022-04-01 06:10:14: pid 13: LOG: watchdog node state changed from [STANDBY] to [NETWORK ISOLATION]
-------------- next part --------------
2022-04-01 05:50:34: pid 1: LOG: Backend status file /var/run/postgresql/pgpool_status does not exist
2022-04-01 05:50:34: pid 1: LOG: health_check_stats_shared_memory_size: requested size: 12288
2022-04-01 05:50:34: pid 1: LOG: memory cache initialized
2022-04-01 05:50:34: pid 1: DETAIL: memcache blocks :64
2022-04-01 05:50:34: pid 1: LOG: allocating (136981880) bytes of shared memory segment
2022-04-01 05:50:34: pid 1: LOG: allocating shared memory segment of size: 136981880
2022-04-01 05:50:34: pid 1: LOG: health_check_stats_shared_memory_size: requested size: 12288
2022-04-01 05:50:34: pid 1: LOG: health_check_stats_shared_memory_size: requested size: 12288
2022-04-01 05:50:34: pid 1: LOG: memory cache initialized
2022-04-01 05:50:34: pid 1: DETAIL: memcache blocks :64
2022-04-01 05:50:34: pid 1: LOG: pool_discard_oid_maps: discarded memqcache oid maps
2022-04-01 05:50:34: pid 1: LOG: waiting for watchdog to initialize
2022-04-01 05:50:34: pid 12: LOG: setting the local watchdog node name to "172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 05:50:34: pid 12: LOG: watchdog cluster is configured with 2 remote nodes
2022-04-01 05:50:34: pid 12: LOG: watchdog remote node:0 on 172.29.30.1:9009
2022-04-01 05:50:34: pid 12: LOG: watchdog remote node:1 on 172.29.30.2:9009
2022-04-01 05:50:34: pid 12: LOG: interface monitoring is disabled in watchdog
2022-04-01 05:50:34: pid 12: LOG: watchdog node state changed from [DEAD] to [LOADING]
2022-04-01 05:50:34: pid 12: LOG: new outbound connection to 172.29.30.1:9009
2022-04-01 05:50:34: pid 12: LOG: new outbound connection to 172.29.30.2:9009
2022-04-01 05:50:34: pid 12: LOG: new watchdog node connection is received from "172.29.30.1:1770"
2022-04-01 05:50:34: pid 12: LOG: new node joined the cluster hostname:"172.29.30.1" port:9009 pgpool_port:5432
2022-04-01 05:50:34: pid 12: DETAIL: Pgpool-II version:"4.3.1" watchdog messaging version: 1.2
2022-04-01 05:50:34: pid 12: LOG: new watchdog node connection is received from "172.29.30.2:37534"
2022-04-01 05:50:34: pid 12: LOG: new node joined the cluster hostname:"172.29.30.2" port:9009 pgpool_port:5432
2022-04-01 05:50:34: pid 12: DETAIL: Pgpool-II version:"4.3.1" watchdog messaging version: 1.2
2022-04-01 05:50:39: pid 12: LOG: watchdog node state changed from [LOADING] to [JOINING]
2022-04-01 05:50:39: pid 12: LOG: setting the remote node "172.29.30.1:5432 Linux ea684c11f759" as watchdog cluster leader
2022-04-01 05:50:39: pid 12: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 05:50:40: pid 12: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 05:50:40: pid 12: LOG: signal_user1_to_parent_with_reason(1)
2022-04-01 05:50:40: pid 12: LOG: successfully joined the watchdog cluster as standby node
2022-04-01 05:50:40: pid 12: DETAIL: our join coordinator request is accepted by cluster leader node "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:50:40: pid 1: LOG: watchdog process is initialized
2022-04-01 05:50:40: pid 1: DETAIL: watchdog messaging data version: 1.2
2022-04-01 05:50:40: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:50:40: pid 1: LOG: Pgpool-II parent process received watchdog state change signal from watchdog
2022-04-01 05:50:40: pid 12: LOG: new IPC connection received
2022-04-01 05:50:40: pid 1: LOG: we have joined the watchdog cluster as STANDBY node
2022-04-01 05:50:40: pid 1: DETAIL: syncing the backend states from the LEADER watchdog node
2022-04-01 05:50:40: pid 12: LOG: new IPC connection received
2022-04-01 05:50:40: pid 12: LOG: received the get data request from local pgpool-II on IPC interface
2022-04-01 05:50:40: pid 12: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:50:40: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:50:40: pid 12: LOG: new IPC connection received
2022-04-01 05:50:40: pid 1: LOG: leader watchdog node "172.29.30.1:5432 Linux ea684c11f759" returned status for 3 backend nodes
2022-04-01 05:50:40: pid 1: LOG: backend:2 is set to down status
2022-04-01 05:50:40: pid 1: DETAIL: backend:2 is DOWN on cluster leader "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:50:40: pid 1: LOG: Setting up socket for 0.0.0.0:5432
2022-04-01 05:50:40: pid 1: LOG: Setting up socket for :::5432
2022-04-01 05:50:40: pid 1: LOG: pgpool-II successfully started. version 4.3.1 (tamahomeboshi)
2022-04-01 05:50:40: pid 1: LOG: node status[0]: 0
2022-04-01 05:50:40: pid 1: LOG: node status[1]: 0
2022-04-01 05:50:40: pid 1: LOG: node status[2]: 0
2022-04-01 05:50:40: pid 13: LOG: 3 watchdog nodes are configured for lifecheck
2022-04-01 05:50:40: pid 13: LOG: watchdog nodes ID:2 Name:"172.29.30.3:5432 Linux 3a3112e1320b"
2022-04-01 05:50:40: pid 13: DETAIL: Host:"172.29.30.3" WD Port:9009 pgpool-II port:5432
2022-04-01 05:50:40: pid 13: LOG: watchdog nodes ID:0 Name:"172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:50:40: pid 13: DETAIL: Host:"172.29.30.1" WD Port:9009 pgpool-II port:5432
2022-04-01 05:50:40: pid 13: LOG: watchdog nodes ID:1 Name:"172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:50:40: pid 13: DETAIL: Host:"172.29.30.2" WD Port:9009 pgpool-II port:5432
2022-04-01 05:50:40: pid 46: LOG: PCP process: 46 started
2022-04-01 05:50:40: pid 47: LOG: process started
2022-04-01 05:50:40: pid 48: LOG: process started
2022-04-01 05:50:40: pid 12: LOG: new IPC connection received
2022-04-01 05:50:40: pid 49: LOG: process started
2022-04-01 05:50:41: pid 53: LOG: set SO_REUSEPORT option to the socket
2022-04-01 05:50:41: pid 53: LOG: creating socket for sending heartbeat
2022-04-01 05:50:41: pid 53: DETAIL: set SO_REUSEPORT
2022-04-01 05:50:41: pid 52: LOG: set SO_REUSEPORT option to the socket
2022-04-01 05:50:41: pid 52: LOG: creating watchdog heartbeat receive socket.
2022-04-01 05:50:41: pid 52: DETAIL: set SO_REUSEPORT
2022-04-01 05:50:41: pid 51: LOG: set SO_REUSEPORT option to the socket
2022-04-01 05:50:41: pid 51: LOG: creating socket for sending heartbeat
2022-04-01 05:50:41: pid 51: DETAIL: set SO_REUSEPORT
2022-04-01 05:50:41: pid 50: LOG: set SO_REUSEPORT option to the socket
2022-04-01 05:50:41: pid 50: LOG: creating watchdog heartbeat receive socket.
2022-04-01 05:50:41: pid 50: DETAIL: set SO_REUSEPORT
2022-04-01 05:50:45: pid 12: LOG: new IPC connection received
2022-04-01 05:50:48: pid 36: LOG: new connection received
2022-04-01 05:50:48: pid 36: DETAIL: connecting host=3d5e02b01620.tkh_network port=41564
2022-04-01 05:50:48: pid 36: LOG: pool_reuse_block: blockid: 0
2022-04-01 05:50:48: pid 36: CONTEXT: while searching system catalog, When relcache is missed
2022-04-01 05:50:48: pid 36: LOG: ParameterStatus message from backend: 0
2022-04-01 05:50:48: pid 36: DETAIL: parameter name: "is_superuser" value: "on"
2022-04-01 05:50:48: pid 36: LOG: ParameterStatus message from backend: 0
2022-04-01 05:50:48: pid 36: DETAIL: parameter name: "session_authorization" value: "keyhub"
2022-04-01 05:50:50: pid 29: LOG: new connection received
2022-04-01 05:50:50: pid 29: DETAIL: connecting host=6cd58d66716b.tkh_network port=41574
2022-04-01 05:50:50: pid 12: LOG: new IPC connection received
2022-04-01 05:50:50: pid 29: LOG: ParameterStatus message from backend: 0
2022-04-01 05:50:50: pid 29: DETAIL: parameter name: "is_superuser" value: "on"
2022-04-01 05:50:50: pid 29: LOG: ParameterStatus message from backend: 0
2022-04-01 05:50:50: pid 29: DETAIL: parameter name: "session_authorization" value: "keyhub"
2022-04-01 05:50:54: pid 26: LOG: new connection received
2022-04-01 05:50:54: pid 26: DETAIL: connecting host=2975c820a0c8.tkh_network port=41584
2022-04-01 05:50:54: pid 26: LOG: ParameterStatus message from backend: 0
2022-04-01 05:50:54: pid 26: DETAIL: parameter name: "is_superuser" value: "on"
2022-04-01 05:50:54: pid 26: LOG: ParameterStatus message from backend: 0
2022-04-01 05:50:54: pid 26: DETAIL: parameter name: "session_authorization" value: "keyhub"
2022-04-01 05:50:56: pid 12: LOG: new IPC connection received
2022-04-01 05:51:01: pid 12: LOG: new IPC connection received
2022-04-01 05:51:06: pid 12: LOG: new IPC connection received
2022-04-01 05:51:11: pid 12: LOG: new IPC connection received
2022-04-01 05:51:17: pid 12: LOG: new IPC connection received
2022-04-01 05:51:22: pid 12: LOG: new IPC connection received
2022-04-01 05:51:27: pid 12: LOG: new IPC connection received
2022-04-01 05:51:32: pid 12: LOG: new IPC connection received
2022-04-01 05:51:35: pid 46: LOG: forked new pcp worker, pid=60 socket=7
2022-04-01 05:51:35: pid 60: LOG: received failback request for node_id: 2 from pid [60]
2022-04-01 05:51:35: pid 12: LOG: new IPC connection received
2022-04-01 05:51:35: pid 12: LOG: failover request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:35: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:51:35: pid 60: LOG: failback request for node_id: 2 from pid [60], will be handled by watchdog
2022-04-01 05:51:35: pid 46: LOG: PCP process with pid: 60 exit with SUCCESS.
2022-04-01 05:51:35: pid 46: LOG: PCP process with pid: 60 exits with status 0
2022-04-01 05:51:35: pid 12: LOG: signal_user1_to_parent_with_reason(2)
2022-04-01 05:51:35: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:51:35: pid 1: LOG: Pgpool-II parent process received sync backend signal from watchdog
2022-04-01 05:51:35: pid 12: LOG: new IPC connection received
2022-04-01 05:51:35: pid 1: LOG: leader watchdog has performed failover
2022-04-01 05:51:35: pid 1: DETAIL: syncing the backend states from the LEADER watchdog node
2022-04-01 05:51:35: pid 12: LOG: new IPC connection received
2022-04-01 05:51:35: pid 12: LOG: received the get data request from local pgpool-II on IPC interface
2022-04-01 05:51:35: pid 12: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:35: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:51:35: pid 1: LOG: leader watchdog node "172.29.30.1:5432 Linux ea684c11f759" returned status for 3 backend nodes
2022-04-01 05:51:35: pid 1: LOG: backend:0 is set to UP status
2022-04-01 05:51:35: pid 1: DETAIL: backend:0 is UP on cluster leader "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:35: pid 1: LOG: backend:1 is set to UP status
2022-04-01 05:51:35: pid 1: DETAIL: backend:1 is UP on cluster leader "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:35: pid 1: LOG: backend:2 is set to UP status
2022-04-01 05:51:35: pid 1: DETAIL: backend:2 is UP on cluster leader "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:35: pid 1: LOG: No backend node was detached because of backend status sync from "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:35: pid 1: DETAIL: no need to restart children
2022-04-01 05:51:35: pid 1: LOG: start health check process for host 172.29.30.3(5432)
2022-04-01 05:51:35: pid 47: LOG: worker process received restart request
2022-04-01 05:51:35: pid 1: LOG: worker child process with pid: 47 exits with status 256
2022-04-01 05:51:35: pid 1: LOG: fork a new worker child process with pid: 62
2022-04-01 05:51:35: pid 62: LOG: process started
2022-04-01 05:51:35: pid 12: LOG: new IPC connection received
2022-04-01 05:51:35: pid 61: LOG: process started
2022-04-01 05:51:35: pid 61: LOG: health check failed on node 2 (timeout:0)
2022-04-01 05:51:35: pid 61: LOG: received degenerate backend request for node_id: 2 from pid [61]
2022-04-01 05:51:35: pid 12: LOG: new IPC connection received
2022-04-01 05:51:35: pid 12: LOG: failover request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:35: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:51:35: pid 12: LOG: remote node "172.29.30.1:5432 Linux ea684c11f759" is asking to inform about quarantined backend nodes
2022-04-01 05:51:35: pid 12: LOG: signal_user1_to_parent_with_reason(4)
2022-04-01 05:51:35: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:51:35: pid 1: LOG: Pgpool-II parent process received inform quarantine nodes signal from watchdog
2022-04-01 05:51:35: pid 61: LOG: degenerate backend request for node_id: 2 from pid [61], will be handled by watchdog, which is building consensus for request
2022-04-01 05:51:36: pid 12: LOG: signal_user1_to_parent_with_reason(2)
2022-04-01 05:51:36: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:51:36: pid 1: LOG: Pgpool-II parent process received sync backend signal from watchdog
2022-04-01 05:51:36: pid 12: LOG: new IPC connection received
2022-04-01 05:51:36: pid 1: LOG: leader watchdog has performed failover
2022-04-01 05:51:36: pid 1: DETAIL: syncing the backend states from the LEADER watchdog node
2022-04-01 05:51:36: pid 12: LOG: new IPC connection received
2022-04-01 05:51:36: pid 12: LOG: received the get data request from local pgpool-II on IPC interface
2022-04-01 05:51:36: pid 12: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:36: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:51:36: pid 1: LOG: leader watchdog node "172.29.30.1:5432 Linux ea684c11f759" returned status for 3 backend nodes
2022-04-01 05:51:36: pid 1: LOG: backend:2 is set to down status
2022-04-01 05:51:36: pid 1: DETAIL: backend:2 is DOWN on cluster leader "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:36: pid 1: LOG: 1 backend node(s) were detached because of backend status sync from "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:36: pid 1: DETAIL: restarting the children processes
2022-04-01 05:51:36: pid 1: LOG: Node 0 is not down (status: 1)
2022-04-01 05:51:36: pid 62: ERROR: Failed to check replication time lag
2022-04-01 05:51:36: pid 62: DETAIL: No persistent db connection for the node 2
2022-04-01 05:51:36: pid 62: HINT: check sr_check_user and sr_check_password
2022-04-01 05:51:36: pid 62: CONTEXT: while checking replication time lag
2022-04-01 05:51:36: pid 62: LOG: worker process received restart request
2022-04-01 05:51:36: pid 1: LOG: worker child process with pid: 62 exits with status 256
2022-04-01 05:51:36: pid 1: LOG: fork a new worker child process with pid: 63
2022-04-01 05:51:36: pid 63: LOG: process started
2022-04-01 05:51:36: pid 12: LOG: new IPC connection received
2022-04-01 05:51:37: pid 12: LOG: signal_user1_to_parent_with_reason(2)
2022-04-01 05:51:37: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:51:37: pid 1: LOG: Pgpool-II parent process received sync backend signal from watchdog
2022-04-01 05:51:37: pid 12: LOG: new IPC connection received
2022-04-01 05:51:37: pid 1: LOG: leader watchdog has performed failover
2022-04-01 05:51:37: pid 1: DETAIL: syncing the backend states from the LEADER watchdog node
2022-04-01 05:51:37: pid 12: LOG: new IPC connection received
2022-04-01 05:51:37: pid 12: LOG: received the get data request from local pgpool-II on IPC interface
2022-04-01 05:51:37: pid 12: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:37: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:51:37: pid 1: LOG: leader watchdog node "172.29.30.1:5432 Linux ea684c11f759" returned status for 3 backend nodes
2022-04-01 05:51:37: pid 1: LOG: backend:2 is set to UP status
2022-04-01 05:51:37: pid 1: DETAIL: backend:2 is UP on cluster leader "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:37: pid 1: LOG: No backend node was detached because of backend status sync from "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:51:37: pid 1: DETAIL: no need to restart children
2022-04-01 05:51:37: pid 63: LOG: worker process received restart request
2022-04-01 05:51:37: pid 1: LOG: worker child process with pid: 63 exits with status 256
2022-04-01 05:51:37: pid 1: LOG: fork a new worker child process with pid: 64
2022-04-01 05:51:37: pid 64: LOG: process started
2022-04-01 05:51:37: pid 12: LOG: new IPC connection received
2022-04-01 05:51:38: pid 43: LOG: new connection received
2022-04-01 05:51:38: pid 43: DETAIL: connecting host=tkh-app.tkh_network port=58340
2022-04-01 05:51:38: pid 43: LOG: selecting backend connection
2022-04-01 05:51:38: pid 43: DETAIL: failover or failback event detected, discarding existing connections
2022-04-01 05:51:38: pid 43: LOG: ParameterStatus message from backend: 0
2022-04-01 05:51:38: pid 43: DETAIL: parameter name: "application_name" value: "PostgreSQL JDBC Driver"
2022-04-01 05:51:40: pid 42: LOG: new connection received
2022-04-01 05:51:40: pid 42: DETAIL: connecting host=tkh-app.tkh_network port=58354
2022-04-01 05:51:40: pid 42: LOG: selecting backend connection
2022-04-01 05:51:40: pid 42: DETAIL: failover or failback event detected, discarding existing connections
2022-04-01 05:51:40: pid 42: LOG: ParameterStatus message from backend: 0
2022-04-01 05:51:40: pid 42: DETAIL: parameter name: "application_name" value: "PostgreSQL JDBC Driver"
2022-04-01 05:51:43: pid 12: LOG: new IPC connection received
2022-04-01 05:51:48: pid 12: LOG: new IPC connection received
2022-04-01 05:51:53: pid 12: LOG: new IPC connection received
2022-04-01 05:51:58: pid 12: LOG: new IPC connection received
2022-04-01 05:52:03: pid 12: LOG: new IPC connection received
2022-04-01 05:52:08: pid 12: LOG: new IPC connection received
2022-04-01 05:52:13: pid 12: LOG: new IPC connection received
2022-04-01 05:52:18: pid 12: LOG: new IPC connection received
2022-04-01 05:52:20: pid 13: LOG: watchdog: lifecheck started
2022-04-01 05:52:23: pid 12: LOG: new IPC connection received
2022-04-01 05:52:28: pid 12: LOG: new IPC connection received
2022-04-01 05:52:30: pid 46: LOG: forked new pcp worker, pid=72 socket=7
2022-04-01 05:52:30: pid 12: LOG: new IPC connection received
2022-04-01 05:52:30: pid 46: LOG: PCP process with pid: 72 exit with SUCCESS.
2022-04-01 05:52:30: pid 46: LOG: PCP process with pid: 72 exits with status 0
2022-04-01 05:52:31: pid 46: LOG: forked new pcp worker, pid=80 socket=7
2022-04-01 05:52:31: pid 46: LOG: PCP process with pid: 80 exit with SUCCESS.
2022-04-01 05:52:31: pid 46: LOG: PCP process with pid: 80 exits with status 0
2022-04-01 05:52:33: pid 12: LOG: new IPC connection received
2022-04-01 05:52:38: pid 12: LOG: new IPC connection received
2022-04-01 05:52:43: pid 12: LOG: new IPC connection received
2022-04-01 05:52:48: pid 12: LOG: new IPC connection received
2022-04-01 05:52:54: pid 12: LOG: new IPC connection received
2022-04-01 05:52:59: pid 12: LOG: new IPC connection received
2022-04-01 05:53:04: pid 12: LOG: new IPC connection received
2022-04-01 05:53:09: pid 12: LOG: new IPC connection received
2022-04-01 05:53:14: pid 12: LOG: new IPC connection received
2022-04-01 05:53:19: pid 12: LOG: new IPC connection received
2022-04-01 05:53:24: pid 12: LOG: new IPC connection received
2022-04-01 05:53:29: pid 12: LOG: new IPC connection received
2022-04-01 05:53:34: pid 12: LOG: new IPC connection received
2022-04-01 05:53:39: pid 12: LOG: new IPC connection received
2022-04-01 05:53:44: pid 12: LOG: new IPC connection received
2022-04-01 05:53:49: pid 12: LOG: new IPC connection received
2022-04-01 05:53:54: pid 12: LOG: new IPC connection received
2022-04-01 05:53:59: pid 12: LOG: new IPC connection received
2022-04-01 05:54:04: pid 12: LOG: new IPC connection received
2022-04-01 05:54:09: pid 12: LOG: new IPC connection received
2022-04-01 05:54:15: pid 12: LOG: new IPC connection received
2022-04-01 05:54:20: pid 12: LOG: new IPC connection received
2022-04-01 05:54:25: pid 12: LOG: new IPC connection received
2022-04-01 05:54:30: pid 12: LOG: new IPC connection received
2022-04-01 05:54:35: pid 12: LOG: new IPC connection received
2022-04-01 05:54:40: pid 12: LOG: new IPC connection received
2022-04-01 05:54:45: pid 12: LOG: new IPC connection received
2022-04-01 05:54:50: pid 12: LOG: new IPC connection received
2022-04-01 05:54:55: pid 12: LOG: new IPC connection received
2022-04-01 05:55:00: pid 12: LOG: new IPC connection received
2022-04-01 05:55:05: pid 12: LOG: new IPC connection received
2022-04-01 05:55:09: pid 12: LOG: remote node "172.29.30.1:5432 Linux ea684c11f759" is shutting down
2022-04-01 05:55:09: pid 12: LOG: watchdog cluster has lost the coordinator node
2022-04-01 05:55:09: pid 12: LOG: removing the remote node "172.29.30.1:5432 Linux ea684c11f759" from watchdog cluster leader
2022-04-01 05:55:09: pid 12: LOG: We have lost the cluster leader node "172.29.30.1:5432 Linux ea684c11f759"
2022-04-01 05:55:09: pid 12: LOG: watchdog node state changed from [STANDBY] to [JOINING]
2022-04-01 05:55:09: pid 12: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 05:55:10: pid 12: LOG: watchdog node state changed from [INITIALIZING] to [STANDING FOR LEADER]
2022-04-01 05:55:10: pid 12: LOG: watchdog node state changed from [STANDING FOR LEADER] to [PARTICIPATING IN ELECTION]
2022-04-01 05:55:10: pid 12: LOG: watchdog node state changed from [PARTICIPATING IN ELECTION] to [INITIALIZING]
2022-04-01 05:55:10: pid 12: LOG: setting the remote node "172.29.30.2:5432 Linux 8045f8151440" as watchdog cluster leader
2022-04-01 05:55:10: pid 12: LOG: new IPC connection received
2022-04-01 05:55:11: pid 12: LOG: watchdog node state changed from [INITIALIZING] to [STANDBY]
2022-04-01 05:55:11: pid 12: LOG: signal_user1_to_parent_with_reason(1)
2022-04-01 05:55:11: pid 12: LOG: successfully joined the watchdog cluster as standby node
2022-04-01 05:55:11: pid 12: DETAIL: our join coordinator request is accepted by cluster leader node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:11: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:55:11: pid 1: LOG: Pgpool-II parent process received watchdog state change signal from watchdog
2022-04-01 05:55:11: pid 12: LOG: signal_user1_to_parent_with_reason(3)
2022-04-01 05:55:11: pid 12: LOG: new IPC connection received
2022-04-01 05:55:11: pid 1: LOG: we have joined the watchdog cluster as STANDBY node
2022-04-01 05:55:11: pid 1: DETAIL: syncing the backend states from the LEADER watchdog node
2022-04-01 05:55:11: pid 12: LOG: new IPC connection received
2022-04-01 05:55:11: pid 12: LOG: received the get data request from local pgpool-II on IPC interface
2022-04-01 05:55:11: pid 12: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:11: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:55:11: pid 1: LOG: leader watchdog node "172.29.30.2:5432 Linux 8045f8151440" returned status for 3 backend nodes
2022-04-01 05:55:11: pid 1: LOG: backend:0 is set to UP status
2022-04-01 05:55:11: pid 1: DETAIL: backend:0 is UP on cluster leader "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:11: pid 1: LOG: backend:1 is set to UP status
2022-04-01 05:55:11: pid 1: DETAIL: backend:1 is UP on cluster leader "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:11: pid 1: LOG: backend:2 is set to UP status
2022-04-01 05:55:11: pid 1: DETAIL: backend:2 is UP on cluster leader "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:11: pid 1: LOG: backend nodes status remains same after the sync from "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:11: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:55:11: pid 1: LOG: Pgpool-II parent process received watchdog quorum change signal from watchdog
2022-04-01 05:55:11: pid 12: LOG: new IPC connection received
2022-04-01 05:55:11: pid 1: LOG: watchdog cluster now holds the quorum
2022-04-01 05:55:11: pid 1: DETAIL: updating the state of quarantine backend nodes
2022-04-01 05:55:11: pid 12: LOG: new IPC connection received
2022-04-01 05:55:12: pid 12: LOG: new watchdog node connection is received from "172.29.30.1:42116"
2022-04-01 05:55:12: pid 12: LOG: new node joined the cluster hostname:"172.29.30.1" port:9009 pgpool_port:5432
2022-04-01 05:55:12: pid 12: DETAIL: Pgpool-II version:"4.3.1" watchdog messaging version: 1.2
2022-04-01 05:55:12: pid 12: LOG: The newly joined node:"172.29.30.1:5432 Linux ea684c11f759" had left the cluster because it was shutdown
2022-04-01 05:55:12: pid 12: LOG: new outbound connection to 172.29.30.1:9009
2022-04-01 05:55:14: pid 42: LOG: reading and processing packets
2022-04-01 05:55:14: pid 42: DETAIL: postmaster on DB node 0 was shutdown by administrative command
2022-04-01 05:55:14: pid 42: LOG: received degenerate backend request for node_id: 0 from pid [42]
2022-04-01 05:55:14: pid 43: LOG: reading and processing packets
2022-04-01 05:55:14: pid 43: DETAIL: postmaster on DB node 0 was shutdown by administrative command
2022-04-01 05:55:14: pid 43: LOG: received degenerate backend request for node_id: 0 from pid [43]
2022-04-01 05:55:14: pid 12: LOG: new IPC connection received
2022-04-01 05:55:14: pid 12: LOG: new IPC connection received
2022-04-01 05:55:14: pid 12: LOG: failover request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:14: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:55:14: pid 12: LOG: failover request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:14: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:55:14: pid 12: LOG: remote node "172.29.30.2:5432 Linux 8045f8151440" is asking to inform about quarantined backend nodes
2022-04-01 05:55:14: pid 12: LOG: signal_user1_to_parent_with_reason(4)
2022-04-01 05:55:14: pid 42: LOG: degenerate backend request for node_id: 0 from pid [42], will be handled by watchdog, which is building consensus for request
2022-04-01 05:55:14: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:55:14: pid 1: LOG: Pgpool-II parent process received inform quarantine nodes signal from watchdog
2022-04-01 05:55:14: pid 43: LOG: degenerate backend request for 1 node(s) from pid [43], is changed to quarantine node request by watchdog
2022-04-01 05:55:14: pid 43: DETAIL: watchdog is taking time to build consensus
2022-04-01 05:55:14: pid 43: LOG: signal_user1_to_parent_with_reason(0)
2022-04-01 05:55:14: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:55:14: pid 1: LOG: Pgpool-II parent process has received failover request
2022-04-01 05:55:14: pid 12: LOG: new IPC connection received
2022-04-01 05:55:14: pid 12: LOG: received the failover indication from Pgpool-II on IPC interface
2022-04-01 05:55:14: pid 12: LOG: received the failover indication from Pgpool-II on IPC interface, but only leader can do failover
2022-04-01 05:55:14: pid 1: LOG: starting quarantine. shutdown host 172.29.30.1(5432)
2022-04-01 05:55:14: pid 1: LOG: Restart all children
2022-04-01 05:55:14: pid 1: LOG: failover: set new primary node: -1
2022-04-01 05:55:14: pid 1: LOG: failover: set new main node: 1
2022-04-01 05:55:14: pid 81: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 81: DETAIL: restarting myself
2022-04-01 05:55:14: pid 82: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 82: DETAIL: restarting myself
2022-04-01 05:55:14: pid 89: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 89: DETAIL: restarting myself
2022-04-01 05:55:14: pid 90: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 90: DETAIL: restarting myself
2022-04-01 05:55:14: pid 12: LOG: new IPC connection received
2022-04-01 05:55:14: pid 12: LOG: remote node "172.29.30.2:5432 Linux 8045f8151440" is asking to inform about quarantined backend nodes
2022-04-01 05:55:14: pid 12: LOG: signal_user1_to_parent_with_reason(4)
2022-04-01 05:55:14: pid 12: LOG: received the failover indication from Pgpool-II on IPC interface
2022-04-01 05:55:14: pid 12: LOG: received the failover indication from Pgpool-II on IPC interface, but only leader can do failover
2022-04-01 05:55:14: pid 64: LOG: worker process received restart request
2022-04-01 05:55:14: pid 91: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 91: DETAIL: restarting myself
quarantine done. shutdown host 172.29.30.1(5432)2022-04-01 05:55:14: pid 1: LOG: quarantine done. shutdown host 172.29.30.1(5432)
2022-04-01 05:55:14: pid 83: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 83: DETAIL: restarting myself
2022-04-01 05:55:14: pid 92: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 92: DETAIL: restarting myself
2022-04-01 05:55:14: pid 100: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 100: DETAIL: restarting myself
2022-04-01 05:55:14: pid 93: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 93: DETAIL: restarting myself
2022-04-01 05:55:14: pid 101: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 101: DETAIL: restarting myself
2022-04-01 05:55:14: pid 94: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 94: DETAIL: restarting myself
2022-04-01 05:55:14: pid 102: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 102: DETAIL: restarting myself
2022-04-01 05:55:14: pid 95: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 95: DETAIL: restarting myself
2022-04-01 05:55:14: pid 105: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 105: DETAIL: restarting myself
2022-04-01 05:55:14: pid 96: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 96: DETAIL: restarting myself
2022-04-01 05:55:14: pid 106: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 106: DETAIL: restarting myself
2022-04-01 05:55:14: pid 97: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 97: DETAIL: restarting myself
2022-04-01 05:55:14: pid 112: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 112: DETAIL: restarting myself
2022-04-01 05:55:14: pid 98: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 98: DETAIL: restarting myself
2022-04-01 05:55:14: pid 107: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 107: DETAIL: restarting myself
2022-04-01 05:55:14: pid 103: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 103: DETAIL: restarting myself
2022-04-01 05:55:14: pid 111: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 111: DETAIL: restarting myself
2022-04-01 05:55:14: pid 104: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 104: DETAIL: restarting myself
2022-04-01 05:55:14: pid 99: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 99: DETAIL: restarting myself
2022-04-01 05:55:14: pid 108: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 108: DETAIL: restarting myself
2022-04-01 05:55:14: pid 85: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 85: DETAIL: restarting myself
2022-04-01 05:55:14: pid 84: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 84: DETAIL: restarting myself
2022-04-01 05:55:14: pid 88: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 88: DETAIL: restarting myself
2022-04-01 05:55:14: pid 86: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 86: DETAIL: restarting myself
2022-04-01 05:55:14: pid 87: LOG: failover or failback event detected
2022-04-01 05:55:14: pid 87: DETAIL: restarting myself
2022-04-01 05:55:15: pid 12: LOG: processing follow primary looking[acquire] request from remote node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:15: pid 12: LOG: signal_user1_to_parent_with_reason(2)
2022-04-01 05:55:15: pid 46: LOG: restart request received in pcp child process
2022-04-01 05:55:15: pid 1: LOG: PCP child 46 exits with status 0 in failover()
2022-04-01 05:55:15: pid 1: LOG: fork a new PCP child pid 113 in failover()
2022-04-01 05:55:15: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:55:15: pid 1: LOG: Pgpool-II parent process received inform quarantine nodes signal from watchdog
2022-04-01 05:55:15: pid 12: LOG: new IPC connection received
2022-04-01 05:55:15: pid 113: LOG: PCP process: 113 started
2022-04-01 05:55:15: pid 12: LOG: failover request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:15: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:55:15: pid 1: LOG: Pgpool-II parent process received sync backend signal from watchdog
2022-04-01 05:55:15: pid 12: LOG: new IPC connection received
2022-04-01 05:55:15: pid 1: LOG: leader watchdog has performed failover
2022-04-01 05:55:15: pid 1: DETAIL: syncing the backend states from the LEADER watchdog node
2022-04-01 05:55:15: pid 12: LOG: new IPC connection received
2022-04-01 05:55:15: pid 12: LOG: received the get data request from local pgpool-II on IPC interface
2022-04-01 05:55:15: pid 12: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:15: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:55:15: pid 1: LOG: leader watchdog node "172.29.30.2:5432 Linux 8045f8151440" returned status for 3 backend nodes
2022-04-01 05:55:15: pid 1: LOG: backend:2 is set to down status
2022-04-01 05:55:15: pid 1: DETAIL: backend:2 is DOWN on cluster leader "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:15: pid 1: LOG: primary node:1 on leader watchdog node "172.29.30.2:5432 Linux 8045f8151440" is different from local primary node:-1
2022-04-01 05:55:15: pid 1: LOG: primary node was changed after the sync from "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:15: pid 1: DETAIL: all children needs to be restarted
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 14 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 15 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 16 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 17 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 18 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 19 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 20 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 21 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 22 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 23 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 24 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 25 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 26 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 27 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 28 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 29 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 30 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 31 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 32 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 33 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 34 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 35 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 36 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 37 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 38 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 39 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 40 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 41 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 42 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 43 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 44 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 45 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: worker child process with pid: 64 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: fork a new worker child process with pid: 146
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 81 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 82 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 83 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 84 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 85 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 86 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 87 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 88 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 89 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 90 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 91 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 92 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 93 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 94 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 95 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 96 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 97 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 98 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 99 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 100 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 101 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 102 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 103 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 104 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 105 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 106 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 107 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 108 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 109 exits with status 0
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 111 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 112 exits with status 256
2022-04-01 05:55:15: pid 1: LOG: child process with pid: 110 exits with status 0
2022-04-01 05:55:15: pid 146: LOG: process started
2022-04-01 05:55:15: pid 12: LOG: new IPC connection received
2022-04-01 05:55:16: pid 61: LOG: request auto failback, node id:2
2022-04-01 05:55:16: pid 61: LOG: received failback request for node_id: 2 from pid [61]
2022-04-01 05:55:16: pid 12: LOG: new IPC connection received
2022-04-01 05:55:16: pid 12: LOG: failover request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:16: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:55:16: pid 61: LOG: failback request for node_id: 2 from pid [61], will be handled by watchdog
2022-04-01 05:55:16: pid 12: LOG: signal_user1_to_parent_with_reason(2)
2022-04-01 05:55:16: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:55:16: pid 1: LOG: Pgpool-II parent process received sync backend signal from watchdog
2022-04-01 05:55:16: pid 12: LOG: new IPC connection received
2022-04-01 05:55:16: pid 1: LOG: leader watchdog has performed failover
2022-04-01 05:55:16: pid 1: DETAIL: syncing the backend states from the LEADER watchdog node
2022-04-01 05:55:16: pid 12: LOG: new IPC connection received
2022-04-01 05:55:16: pid 12: LOG: received the get data request from local pgpool-II on IPC interface
2022-04-01 05:55:16: pid 12: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:16: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:55:16: pid 1: LOG: leader watchdog node "172.29.30.2:5432 Linux 8045f8151440" returned status for 3 backend nodes
2022-04-01 05:55:16: pid 1: LOG: backend:2 is set to UP status
2022-04-01 05:55:16: pid 1: DETAIL: backend:2 is UP on cluster leader "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:16: pid 1: LOG: No backend node was detached because of backend status sync from "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:16: pid 1: DETAIL: no need to restart children
2022-04-01 05:55:16: pid 146: LOG: worker process received restart request
2022-04-01 05:55:16: pid 1: LOG: worker child process with pid: 146 exits with status 256
2022-04-01 05:55:16: pid 1: LOG: fork a new worker child process with pid: 147
2022-04-01 05:55:16: pid 147: LOG: process started
2022-04-01 05:55:16: pid 12: LOG: new IPC connection received
2022-04-01 05:55:18: pid 12: LOG: remote node "172.29.30.2:5432 Linux 8045f8151440" is asking to inform about quarantined backend nodes
2022-04-01 05:55:18: pid 12: LOG: signal_user1_to_parent_with_reason(4)
2022-04-01 05:55:18: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:55:18: pid 1: LOG: Pgpool-II parent process received inform quarantine nodes signal from watchdog
2022-04-01 05:55:18: pid 12: LOG: signal_user1_to_parent_with_reason(2)
2022-04-01 05:55:18: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:55:18: pid 1: LOG: Pgpool-II parent process received sync backend signal from watchdog
2022-04-01 05:55:18: pid 12: LOG: new IPC connection received
2022-04-01 05:55:18: pid 1: LOG: leader watchdog has performed failover
2022-04-01 05:55:18: pid 1: DETAIL: syncing the backend states from the LEADER watchdog node
2022-04-01 05:55:18: pid 12: LOG: new IPC connection received
2022-04-01 05:55:18: pid 12: LOG: received the get data request from local pgpool-II on IPC interface
2022-04-01 05:55:18: pid 12: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:18: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:55:18: pid 1: LOG: leader watchdog node "172.29.30.2:5432 Linux 8045f8151440" returned status for 3 backend nodes
2022-04-01 05:55:18: pid 1: LOG: backend:2 is set to down status
2022-04-01 05:55:18: pid 1: DETAIL: backend:2 is DOWN on cluster leader "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:18: pid 1: LOG: 1 backend node(s) were detached because of backend status sync from "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:18: pid 1: DETAIL: restarting the children processes
2022-04-01 05:55:18: pid 1: LOG: Node 1 is not down (status: 1)
2022-04-01 05:55:18: pid 147: LOG: worker process received restart request
2022-04-01 05:55:18: pid 1: LOG: worker child process with pid: 147 exits with status 256
2022-04-01 05:55:18: pid 1: LOG: fork a new worker child process with pid: 148
2022-04-01 05:55:18: pid 148: LOG: process started
2022-04-01 05:55:18: pid 12: LOG: new IPC connection received
2022-04-01 05:55:19: pid 12: LOG: processing follow primary looking[release] request from remote node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:19: pid 12: LOG: signal_user1_to_parent_with_reason(2)
2022-04-01 05:55:19: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:55:19: pid 1: LOG: Pgpool-II parent process received sync backend signal from watchdog
2022-04-01 05:55:19: pid 12: LOG: new IPC connection received
2022-04-01 05:55:19: pid 1: LOG: leader watchdog has performed failover
2022-04-01 05:55:19: pid 1: DETAIL: syncing the backend states from the LEADER watchdog node
2022-04-01 05:55:19: pid 12: LOG: new IPC connection received
2022-04-01 05:55:19: pid 12: LOG: received the get data request from local pgpool-II on IPC interface
2022-04-01 05:55:19: pid 12: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:19: pid 12: DETAIL: waiting for the reply...
2022-04-01 05:55:19: pid 1: LOG: leader watchdog node "172.29.30.2:5432 Linux 8045f8151440" returned status for 3 backend nodes
2022-04-01 05:55:19: pid 1: LOG: backend:2 is set to UP status
2022-04-01 05:55:19: pid 1: DETAIL: backend:2 is UP on cluster leader "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:19: pid 1: LOG: No backend node was detached because of backend status sync from "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:19: pid 1: DETAIL: no need to restart children
2022-04-01 05:55:19: pid 148: LOG: worker process received restart request
2022-04-01 05:55:19: pid 1: LOG: worker child process with pid: 148 exits with status 256
2022-04-01 05:55:19: pid 1: LOG: fork a new worker child process with pid: 149
2022-04-01 05:55:19: pid 149: LOG: process started
2022-04-01 05:55:19: pid 12: LOG: new IPC connection received
2022-04-01 05:55:24: pid 12: LOG: new IPC connection received
2022-04-01 05:55:29: pid 12: LOG: read from socket failed, remote end closed the connection
2022-04-01 05:55:29: pid 12: LOG: client socket of 172.29.30.2:5432 Linux 8045f8151440 is closed
2022-04-01 05:55:29: pid 12: LOG: read from socket failed, remote end closed the connection
2022-04-01 05:55:29: pid 12: LOG: outbound socket of 172.29.30.2:5432 Linux 8045f8151440 is closed
2022-04-01 05:55:29: pid 12: LOG: remote node "172.29.30.2:5432 Linux 8045f8151440" is not reachable
2022-04-01 05:55:29: pid 12: DETAIL: marking the node as lost
2022-04-01 05:55:29: pid 12: LOG: remote node "172.29.30.2:5432 Linux 8045f8151440" is lost
2022-04-01 05:55:29: pid 12: LOG: watchdog cluster has lost the coordinator node
2022-04-01 05:55:29: pid 12: LOG: removing the remote node "172.29.30.2:5432 Linux 8045f8151440" from watchdog cluster leader
2022-04-01 05:55:29: pid 12: LOG: We have lost the cluster leader node "172.29.30.2:5432 Linux 8045f8151440"
2022-04-01 05:55:29: pid 12: LOG: watchdog node state changed from [STANDBY] to [JOINING]
2022-04-01 05:55:29: pid 12: LOG: watchdog node state changed from [JOINING] to [INITIALIZING]
2022-04-01 05:55:29: pid 12: LOG: new IPC connection received
2022-04-01 05:55:29: pid 12: LOG: new watchdog node connection is received from "172.29.30.2:54434"
2022-04-01 05:55:29: pid 12: LOG: new node joined the cluster hostname:"172.29.30.2" port:9009 pgpool_port:5432
2022-04-01 05:55:29: pid 12: DETAIL: Pgpool-II version:"4.3.1" watchdog messaging version: 1.2
2022-04-01 05:55:29: pid 12: LOG: The newly joined node:"172.29.30.2:5432 Linux 8045f8151440" had left the cluster because it was lost
2022-04-01 05:55:29: pid 12: DETAIL: lost reason was "NOT REACHABLE" and startup time diff = 353
2022-04-01 05:55:30: pid 12: LOG: watchdog node state changed from [INITIALIZING] to [STANDING FOR LEADER]
2022-04-01 05:55:32: pid 48: LOG: request auto failback, node id:0
2022-04-01 05:55:32: pid 48: LOG: received failback request for node_id: 0 from pid [48]
2022-04-01 05:55:32: pid 12: LOG: new IPC connection received
2022-04-01 05:55:32: pid 12: LOG: unable to process the failover request received on IPC interface
2022-04-01 05:55:32: pid 12: DETAIL: this watchdog node has not joined the cluster yet
2022-04-01 05:55:32: pid 12: HINT: try again in few seconds
2022-04-01 05:55:32: pid 12: NOTICE: IPC command returned error
2022-04-01 05:55:32: pid 12: NOTICE: error writing to IPC socket
2022-04-01 05:55:32: pid 48: ERROR: failback request for node_id: 0 from pid [48] is canceled by other pgpool
2022-04-01 05:55:34: pid 12: LOG: new IPC connection received
2022-04-01 05:55:35: pid 12: LOG: watchdog node state changed from [STANDING FOR LEADER] to [LEADER]
2022-04-01 05:55:35: pid 12: LOG: I am announcing my self as leader/coordinator watchdog node
2022-04-01 05:55:35: pid 12: LOG: I am the cluster leader node
2022-04-01 05:55:35: pid 12: DETAIL: our declare coordinator message is accepted by all nodes
2022-04-01 05:55:35: pid 12: LOG: setting the local node "172.29.30.3:5432 Linux 3a3112e1320b" as watchdog cluster leader
2022-04-01 05:55:35: pid 12: LOG: signal_user1_to_parent_with_reason(1)
2022-04-01 05:55:35: pid 12: LOG: I am the cluster leader node but we do not have enough nodes in cluster
2022-04-01 05:55:35: pid 12: DETAIL: waiting for the quorum to start escalation process
2022-04-01 05:55:35: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:55:35: pid 1: LOG: Pgpool-II parent process received watchdog state change signal from watchdog
2022-04-01 05:55:35: pid 12: LOG: new IPC connection received
2022-04-01 05:55:36: pid 12: LOG: adding watchdog node "172.29.30.2:5432 Linux 8045f8151440" to the standby list
2022-04-01 05:55:36: pid 12: LOG: quorum found
2022-04-01 05:55:36: pid 12: DETAIL: starting escalation process
2022-04-01 05:55:36: pid 12: LOG: escalation process started with PID:150
2022-04-01 05:55:36: pid 150: LOG: watchdog: escalation started
2022-04-01 05:55:36: pid 12: LOG: signal_user1_to_parent_with_reason(3)
2022-04-01 05:55:36: pid 12: LOG: adding watchdog node "172.29.30.1:5432 Linux ea684c11f759" to the standby list
2022-04-01 05:55:36: pid 1: LOG: Pgpool-II parent process received SIGUSR1
2022-04-01 05:55:36: pid 1: LOG: Pgpool-II parent process received watchdog quorum change signal from watchdog
2022-04-01 05:55:36: pid 12: LOG: new IPC connection received
2022-04-01 05:55:36: pid 1: LOG: watchdog cluster now holds the quorum
2022-04-01 05:55:36: pid 1: DETAIL: updating the state of quarantine backend nodes
2022-04-01 05:55:36: pid 12: LOG: new IPC connection received
2022-04-01 05:55:36: pid 12: LOG: watchdog escalation process with pid: 150 exit with SUCCESS.
2022-04-01 05:55:39: pid 12: LOG: new IPC connection received
2022-04-01 05:55:40: pid 12: LOG: new outbound connection to 172.29.30.2:9009
2022-04-01 05:55:44: pid 12: LOG: new IPC connection received
2022-04-01 05:55:47: pid 1: WARNING: child process with pid: 48 was terminated by segmentation fault
2022-04-01 05:55:49: pid 12: LOG: new IPC connection received
2022-04-01 05:55:54: pid 12: LOG: new IPC connection received
2022-04-01 05:55:59: pid 12: LOG: new IPC connection received
2022-04-01 05:56:04: pid 12: LOG: remote node "172.29.30.1:5432 Linux ea684c11f759" is shutting down
2022-04-01 05:56:04: pid 12: LOG: removing watchdog node "172.29.30.1:5432 Linux ea684c11f759" from the standby list
2022-04-01 05:56:04: pid 12: LOG: new IPC connection received
2022-04-01 05:56:06: pid 12: LOG: new watchdog node connection is received from "172.29.30.1:12934"
2022-04-01 05:56:06: pid 12: LOG: new node joined the cluster hostname:"172.29.30.1" port:9009 pgpool_port:5432
2022-04-01 05:56:06: pid 12: DETAIL: Pgpool-II version:"4.3.1" watchdog messaging version: 1.2
2022-04-01 05:56:06: pid 12: LOG: The newly joined node:"172.29.30.1:5432 Linux 44e516295170" had left the cluster because it was shutdown
2022-04-01 05:56:06: pid 12: LOG: new outbound connection to 172.29.30.1:9009
2022-04-01 05:56:07: pid 12: LOG: adding watchdog node "172.29.30.1:5432 Linux 44e516295170" to the standby list
2022-04-01 05:56:09: pid 12: LOG: new IPC connection received
2022-04-01 05:56:14: pid 12: LOG: new IPC connection received
2022-04-01 05:56:19: pid 12: LOG: new IPC connection received
2022-04-01 05:56:24: pid 12: LOG: new IPC connection received
2022-04-01 05:56:29: pid 12: LOG: new IPC connection received
2022-04-01 05:56:34: pid 12: LOG: new IPC connection received
2022-04-01 05:56:39: pid 12: LOG: new IPC connection received
2022-04-01 05:56:44: pid 12: LOG: new IPC connection received
2022-04-01 05:56:49: pid 12: LOG: new IPC connection received
2022-04-01 05:56:55: pid 12: LOG: new IPC connection received
2022-04-01 05:57:00: pid 12: LOG: new IPC connection received
2022-04-01 05:57:05: pid 12: LOG: new IPC connection received
2022-04-01 05:57:10: pid 12: LOG: new IPC connection received
2022-04-01 05:57:15: pid 12: LOG: new IPC connection received
2022-04-01 05:57:20: pid 12: LOG: new IPC connection received
2022-04-01 05:57:25: pid 12: LOG: new IPC connection received
2022-04-01 05:57:30: pid 12: LOG: new IPC connection received
2022-04-01 05:57:35: pid 12: LOG: new IPC connection received
2022-04-01 05:57:40: pid 12: LOG: new IPC connection received
2022-04-01 05:57:45: pid 12: LOG: new IPC connection received
2022-04-01 05:57:50: pid 12: LOG: new IPC connection received
2022-04-01 05:57:55: pid 12: LOG: new IPC connection received
2022-04-01 05:58:00: pid 12: LOG: new IPC connection received
2022-04-01 05:58:05: pid 12: LOG: new IPC connection received
2022-04-01 05:58:10: pid 12: LOG: new IPC connection received
2022-04-01 05:58:15: pid 12: LOG: new IPC connection received
2022-04-01 05:58:20: pid 12: LOG: new IPC connection received
2022-04-01 05:58:25: pid 12: LOG: new IPC connection received
2022-04-01 05:58:30: pid 12: LOG: new IPC connection received
2022-04-01 05:58:30: pid 113: LOG: forked new pcp worker, pid=157 socket=7
2022-04-01 05:58:30: pid 12: LOG: new IPC connection received
2022-04-01 05:58:30: pid 113: LOG: PCP process with pid: 157 exit with SUCCESS.
2022-04-01 05:58:30: pid 113: LOG: PCP process with pid: 157 exits with status 0
2022-04-01 05:58:31: pid 113: LOG: forked new pcp worker, pid=164 socket=7
2022-04-01 05:58:31: pid 113: LOG: PCP process with pid: 164 exit with SUCCESS.
2022-04-01 05:58:31: pid 113: LOG: PCP process with pid: 164 exits with status 0
2022-04-01 05:58:35: pid 12: LOG: new IPC connection received
2022-04-01 05:58:40: pid 12: LOG: new IPC connection received
2022-04-01 05:58:45: pid 12: LOG: new IPC connection received
2022-04-01 05:58:50: pid 12: LOG: new IPC connection received
2022-04-01 05:58:55: pid 12: LOG: new IPC connection received
2022-04-01 05:58:57: pid 12: LOG: read from socket failed, remote end closed the connection
2022-04-01 05:58:57: pid 12: LOG: client socket of 172.29.30.1:5432 Linux 44e516295170 is closed
2022-04-01 05:58:57: pid 12: LOG: remote node "172.29.30.1:5432 Linux 44e516295170" is shutting down
2022-04-01 05:58:57: pid 12: LOG: removing watchdog node "172.29.30.1:5432 Linux 44e516295170" from the standby list
2022-04-01 05:59:00: pid 12: LOG: new IPC connection received
2022-04-01 05:59:05: pid 12: LOG: new IPC connection received
2022-04-01 05:59:10: pid 12: LOG: new IPC connection received
2022-04-01 05:59:15: pid 12: LOG: new IPC connection received
2022-04-01 05:59:20: pid 12: LOG: new IPC connection received
2022-04-01 05:59:25: pid 12: LOG: new IPC connection received
2022-04-01 05:59:29: pid 12: LOG: new watchdog node connection is received from "172.29.30.1:59017"
2022-04-01 05:59:29: pid 12: LOG: new node joined the cluster hostname:"172.29.30.1" port:9009 pgpool_port:5432
2022-04-01 05:59:29: pid 12: DETAIL: Pgpool-II version:"4.3.1" watchdog messaging version: 1.2
2022-04-01 05:59:29: pid 12: LOG: The newly joined node:"172.29.30.1:5432 Linux 43a0ec8556bb" had left the cluster because it was shutdown
2022-04-01 05:59:29: pid 12: LOG: new outbound connection to 172.29.30.1:9009
2022-04-01 05:59:30: pid 13: LOG: informing the node status change to watchdog
2022-04-01 05:59:30: pid 13: DETAIL: node id :0 status = "NODE DEAD" message:"No heartbeat signal from node"
2022-04-01 05:59:30: pid 12: LOG: new IPC connection received
2022-04-01 05:59:30: pid 12: LOG: received node status change ipc message
2022-04-01 05:59:30: pid 12: DETAIL: No heartbeat signal from node
2022-04-01 05:59:30: pid 12: LOG: remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is lost
2022-04-01 05:59:30: pid 113: LOG: forked new pcp worker, pid=171 socket=7
2022-04-01 05:59:30: pid 12: LOG: new IPC connection received
2022-04-01 05:59:30: pid 113: LOG: PCP process with pid: 171 exit with SUCCESS.
2022-04-01 05:59:30: pid 113: LOG: PCP process with pid: 171 exits with status 0
2022-04-01 05:59:31: pid 12: LOG: new IPC connection received
2022-04-01 05:59:31: pid 113: LOG: forked new pcp worker, pid=178 socket=7
2022-04-01 05:59:32: pid 113: LOG: PCP process with pid: 178 exit with SUCCESS.
2022-04-01 05:59:32: pid 113: LOG: PCP process with pid: 178 exits with status 0
2022-04-01 05:59:36: pid 12: LOG: new IPC connection received
2022-04-01 05:59:41: pid 12: LOG: new IPC connection received
2022-04-01 05:59:41: pid 12: LOG: new outbound connection to 172.29.30.1:9009
2022-04-01 05:59:41: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:41: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:41: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:41: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:41: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:41: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:41: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:41: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:41: pid 12: LOG: new watchdog node connection is received from "172.29.30.1:62601"
2022-04-01 05:59:41: pid 12: LOG: new node joined the cluster hostname:"172.29.30.1" port:9009 pgpool_port:5432
2022-04-01 05:59:41: pid 12: DETAIL: Pgpool-II version:"4.3.1" watchdog messaging version: 1.2
2022-04-01 05:59:41: pid 12: LOG: The newly joined node:"172.29.30.1:5432 Linux 43a0ec8556bb" had left the cluster because it was lost
2022-04-01 05:59:41: pid 12: DETAIL: lost reason was "REPORTED BY LIFECHECK" and startup time diff = 0
2022-04-01 05:59:41: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:41: pid 12: DETAIL: only lifecheck process can mark this node alive again
2022-04-01 05:59:42: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:42: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:42: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:42: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:42: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:42: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:42: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:42: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:42: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:42: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:42: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:42: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:42: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:42: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:42: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:42: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:43: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 05:59:43: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 05:59:43: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:43: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:43: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:43: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:43: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:43: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:43: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:43: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:43: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:43: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:43: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:43: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:43: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:43: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:43: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:43: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:46: pid 12: LOG: new IPC connection received
2022-04-01 05:59:51: pid 12: LOG: new IPC connection received
2022-04-01 05:59:53: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:53: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:53: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:53: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:53: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:53: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:53: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:53: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:53: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:53: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:53: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:53: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:53: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:53: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:53: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:53: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:54: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 05:59:54: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 05:59:54: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:54: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:54: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:54: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:54: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:54: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:54: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:54: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:54: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:54: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:54: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:54: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:54: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 05:59:54: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 05:59:54: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 05:59:54: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 05:59:56: pid 12: LOG: new IPC connection received
2022-04-01 06:00:00: pid 117: LOG: new connection received
2022-04-01 06:00:00: pid 117: DETAIL: connecting host=tkh-app.tkh_network port=60142
2022-04-01 06:00:00: pid 117: LOG: selecting backend connection
2022-04-01 06:00:00: pid 117: DETAIL: failover or failback event detected, discarding existing connections
2022-04-01 06:00:00: pid 117: LOG: ParameterStatus message from backend: 1
2022-04-01 06:00:00: pid 117: DETAIL: parameter name: "application_name" value: "PostgreSQL JDBC Driver"
2022-04-01 06:00:01: pid 12: LOG: new IPC connection received
2022-04-01 06:00:04: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:04: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:04: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:04: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:04: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:04: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:04: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:04: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:04: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:04: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:04: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:04: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:04: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:04: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:04: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:04: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:05: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:00:05: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:00:05: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:05: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:05: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:05: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:05: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:05: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:05: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:05: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:05: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:05: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:05: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:05: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:05: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:05: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:05: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:05: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:06: pid 12: LOG: new IPC connection received
2022-04-01 06:00:11: pid 12: LOG: new IPC connection received
2022-04-01 06:00:15: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:15: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:15: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:15: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:15: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:15: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:15: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:15: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:15: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:15: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:15: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:15: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:15: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:15: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:15: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:15: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:16: pid 12: LOG: new IPC connection received
2022-04-01 06:00:16: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:00:16: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:00:16: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:16: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:16: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:16: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:16: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:16: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:16: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:16: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:16: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:16: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:16: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:16: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:16: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:16: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:16: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:16: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:17: pid 123: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 123: DETAIL: restarting myself
2022-04-01 06:00:17: pid 139: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 139: DETAIL: restarting myself
2022-04-01 06:00:17: pid 132: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 132: DETAIL: restarting myself
2022-04-01 06:00:17: pid 133: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 133: DETAIL: restarting myself
2022-04-01 06:00:17: pid 122: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 122: DETAIL: restarting myself
2022-04-01 06:00:17: pid 130: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 130: DETAIL: restarting myself
2022-04-01 06:00:17: pid 114: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 114: DETAIL: restarting myself
2022-04-01 06:00:17: pid 136: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 136: DETAIL: restarting myself
2022-04-01 06:00:17: pid 127: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 127: DETAIL: restarting myself
2022-04-01 06:00:17: pid 119: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 119: DETAIL: restarting myself
2022-04-01 06:00:17: pid 126: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 126: DETAIL: restarting myself
2022-04-01 06:00:17: pid 143: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 143: DETAIL: restarting myself
2022-04-01 06:00:17: pid 129: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 129: DETAIL: restarting myself
2022-04-01 06:00:17: pid 142: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 142: DETAIL: restarting myself
2022-04-01 06:00:17: pid 134: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 134: DETAIL: restarting myself
2022-04-01 06:00:17: pid 120: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 120: DETAIL: restarting myself
2022-04-01 06:00:17: pid 137: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 137: DETAIL: restarting myself
2022-04-01 06:00:17: pid 125: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 125: DETAIL: restarting myself
2022-04-01 06:00:17: pid 135: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 135: DETAIL: restarting myself
2022-04-01 06:00:17: pid 118: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 118: DETAIL: restarting myself
2022-04-01 06:00:17: pid 121: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 121: DETAIL: restarting myself
2022-04-01 06:00:17: pid 144: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 144: DETAIL: restarting myself
2022-04-01 06:00:17: pid 140: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 140: DETAIL: restarting myself
2022-04-01 06:00:17: pid 145: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 145: DETAIL: restarting myself
2022-04-01 06:00:17: pid 131: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 131: DETAIL: restarting myself
2022-04-01 06:00:17: pid 138: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 138: DETAIL: restarting myself
2022-04-01 06:00:17: pid 116: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 116: DETAIL: restarting myself
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 114 exits with status 256
2022-04-01 06:00:17: pid 124: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 124: DETAIL: restarting myself
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 179
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 116 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 180
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 118 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 181
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 119 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 182
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 120 exits with status 256
2022-04-01 06:00:17: pid 115: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 115: DETAIL: restarting myself
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 183
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 121 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 184
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 122 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 185
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 123 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 186
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 115 exits with status 256
2022-04-01 06:00:17: pid 128: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 128: DETAIL: restarting myself
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 187
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 124 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 188
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 125 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 189
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 126 exits with status 256
2022-04-01 06:00:17: pid 141: LOG: failover or failback event detected
2022-04-01 06:00:17: pid 141: DETAIL: restarting myself
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 190
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 127 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 191
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 128 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 192
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 129 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 193
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 130 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 194
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 131 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 195
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 132 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 196
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 133 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 197
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 134 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 198
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 135 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 199
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 136 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 200
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 137 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 201
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 138 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 202
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 139 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 203
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 140 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 204
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 141 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 205
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 142 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 206
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 143 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 207
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 144 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 208
2022-04-01 06:00:17: pid 1: LOG: child process with pid: 145 exits with status 256
2022-04-01 06:00:17: pid 1: LOG: fork a new child process with pid: 209
2022-04-01 06:00:21: pid 12: LOG: new IPC connection received
2022-04-01 06:00:26: pid 12: LOG: new IPC connection received
2022-04-01 06:00:26: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:26: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:26: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:26: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:26: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:26: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:26: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:26: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:26: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:26: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:26: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:26: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:26: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:26: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:26: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:26: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:27: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:00:27: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:00:27: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:27: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:27: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:27: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:27: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:27: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:27: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:27: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:27: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:27: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:27: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:27: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:27: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:27: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:27: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:27: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:30: pid 113: LOG: forked new pcp worker, pid=216 socket=7
2022-04-01 06:00:30: pid 12: LOG: new IPC connection received
2022-04-01 06:00:30: pid 113: LOG: PCP process with pid: 216 exit with SUCCESS.
2022-04-01 06:00:30: pid 113: LOG: PCP process with pid: 216 exits with status 0
2022-04-01 06:00:31: pid 12: LOG: new IPC connection received
2022-04-01 06:00:31: pid 113: LOG: forked new pcp worker, pid=222 socket=7
2022-04-01 06:00:31: pid 113: LOG: PCP process with pid: 222 exit with SUCCESS.
2022-04-01 06:00:31: pid 113: LOG: PCP process with pid: 222 exits with status 0
2022-04-01 06:00:36: pid 12: LOG: new IPC connection received
2022-04-01 06:00:37: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:37: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:37: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:37: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:37: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:37: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:37: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:37: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:37: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:37: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:37: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:37: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:37: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:37: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:37: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:37: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:38: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:00:38: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:00:38: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:38: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:38: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:38: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:38: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:38: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:38: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:38: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:38: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:38: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:38: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:38: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:38: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:38: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:38: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:38: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:41: pid 12: LOG: new IPC connection received
2022-04-01 06:00:46: pid 12: LOG: new IPC connection received
2022-04-01 06:00:48: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:48: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:48: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:48: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:48: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:48: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:48: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:48: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:48: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:48: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:48: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:48: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:48: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:48: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:48: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:48: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:50: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:00:50: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:00:50: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:50: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:50: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:50: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:50: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:50: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:50: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:50: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:50: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:50: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:50: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:50: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:50: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:00:50: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:00:50: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:00:50: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:00:51: pid 12: LOG: new IPC connection received
2022-04-01 06:00:56: pid 12: LOG: new IPC connection received
2022-04-01 06:01:00: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:00: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:00: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:00: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:00: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:00: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:00: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:00: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:00: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:00: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:00: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:00: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:00: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:00: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:00: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:00: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:01: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:01:01: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:01:01: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:01: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:01: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:01: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:01: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:01: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:01: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:01: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:01: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:01: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:01: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:01: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:01: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:01: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:01: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:01: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:01: pid 12: LOG: new IPC connection received
2022-04-01 06:01:06: pid 12: LOG: new IPC connection received
2022-04-01 06:01:11: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:11: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:11: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:11: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:11: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:11: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:11: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:11: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:11: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:11: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:11: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:11: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:11: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:11: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:11: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:11: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:11: pid 12: LOG: new IPC connection received
2022-04-01 06:01:12: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:01:12: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:01:12: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:12: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:12: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:12: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:12: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:12: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:12: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:12: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:12: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:12: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:12: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:12: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:12: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:12: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:12: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:12: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:16: pid 12: LOG: new IPC connection received
2022-04-01 06:01:22: pid 12: LOG: new IPC connection received
2022-04-01 06:01:22: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:22: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:22: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:22: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:22: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:22: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:22: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:22: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:22: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:22: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:22: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:22: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:22: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:22: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:22: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:22: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:23: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:01:23: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:01:23: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:23: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:23: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:23: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:23: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:23: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:23: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:23: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:23: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:23: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:23: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:23: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:23: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:23: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:23: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:23: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:27: pid 12: LOG: new IPC connection received
2022-04-01 06:01:30: pid 113: LOG: forked new pcp worker, pid=229 socket=7
2022-04-01 06:01:30: pid 12: LOG: new IPC connection received
2022-04-01 06:01:30: pid 113: LOG: PCP process with pid: 229 exit with SUCCESS.
2022-04-01 06:01:30: pid 113: LOG: PCP process with pid: 229 exits with status 0
2022-04-01 06:01:31: pid 113: LOG: forked new pcp worker, pid=237 socket=7
2022-04-01 06:01:32: pid 113: LOG: PCP process with pid: 237 exit with SUCCESS.
2022-04-01 06:01:32: pid 113: LOG: PCP process with pid: 237 exits with status 0
2022-04-01 06:01:32: pid 12: LOG: new IPC connection received
2022-04-01 06:01:33: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:33: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:33: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:33: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:33: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:33: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:33: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:33: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:33: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:33: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:33: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:33: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:33: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:33: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:33: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:33: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:34: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:01:34: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:01:34: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:34: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:34: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:34: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:34: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:34: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:34: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:34: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:34: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:34: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:34: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:34: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:34: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:34: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:34: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:34: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:37: pid 12: LOG: new IPC connection received
2022-04-01 06:01:42: pid 12: LOG: new IPC connection received
2022-04-01 06:01:44: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:44: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:44: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:44: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:44: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:44: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:44: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:44: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:44: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:44: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:44: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:44: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:44: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:44: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:44: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:44: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:45: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:01:45: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:01:45: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:45: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:45: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:45: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:45: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:45: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:45: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:45: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:45: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:45: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:45: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:45: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:45: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:45: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:45: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:45: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:47: pid 12: LOG: new IPC connection received
2022-04-01 06:01:52: pid 12: LOG: new IPC connection received
2022-04-01 06:01:55: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:55: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:55: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:55: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:55: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:55: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:55: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:55: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:55: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:55: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:55: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:55: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:55: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:55: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:55: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:55: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:56: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:01:56: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:01:56: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:56: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:56: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:56: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:56: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:56: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:56: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:56: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:56: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:56: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:56: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:56: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:56: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:01:56: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:01:56: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:01:56: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:01:57: pid 12: LOG: new IPC connection received
2022-04-01 06:02:02: pid 12: LOG: new IPC connection received
2022-04-01 06:02:06: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:06: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:06: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:06: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:06: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:06: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:06: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:06: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:06: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:06: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:06: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:06: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:06: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:06: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:06: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:06: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:07: pid 12: LOG: new IPC connection received
2022-04-01 06:02:07: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:02:07: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:02:07: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:07: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:07: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:07: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:07: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:07: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:07: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:07: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:07: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:07: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:07: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:07: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:07: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:07: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:07: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:07: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:12: pid 12: LOG: new IPC connection received
2022-04-01 06:02:17: pid 12: LOG: new IPC connection received
2022-04-01 06:02:17: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:17: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:17: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:17: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:17: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:17: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:17: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:17: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:17: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:17: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:17: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:17: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:17: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:17: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:17: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:17: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:18: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:02:18: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:02:18: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:18: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:18: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:18: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:18: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:18: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:18: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:18: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:18: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:18: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:18: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:18: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:18: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:18: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:18: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:18: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:22: pid 12: LOG: new IPC connection received
2022-04-01 06:02:27: pid 12: LOG: new IPC connection received
2022-04-01 06:02:28: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:28: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:28: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:28: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:28: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:28: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:28: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:28: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:28: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:28: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:28: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:28: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:28: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:28: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:28: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:28: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:29: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:02:29: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:02:29: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:29: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:29: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:29: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:29: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:29: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:29: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:29: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:29: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:29: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:29: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:29: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:29: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:29: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:29: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:29: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:30: pid 113: LOG: forked new pcp worker, pid=245 socket=7
2022-04-01 06:02:30: pid 12: LOG: new IPC connection received
2022-04-01 06:02:30: pid 113: LOG: PCP process with pid: 245 exit with SUCCESS.
2022-04-01 06:02:30: pid 113: LOG: PCP process with pid: 245 exits with status 0
2022-04-01 06:02:31: pid 113: LOG: forked new pcp worker, pid=253 socket=7
2022-04-01 06:02:31: pid 113: LOG: PCP process with pid: 253 exit with SUCCESS.
2022-04-01 06:02:31: pid 113: LOG: PCP process with pid: 253 exits with status 0
2022-04-01 06:02:32: pid 12: LOG: new IPC connection received
2022-04-01 06:02:37: pid 12: LOG: new IPC connection received
2022-04-01 06:02:39: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:39: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:39: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:39: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:39: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:39: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:39: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:39: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:39: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:39: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:39: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:39: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:39: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:39: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:39: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:39: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:40: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:02:40: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:02:40: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:40: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:40: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:40: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:40: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:40: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:40: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:40: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:40: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:40: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:40: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:40: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:40: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:40: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:40: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:40: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:42: pid 12: LOG: new IPC connection received
2022-04-01 06:02:47: pid 12: LOG: new IPC connection received
2022-04-01 06:02:50: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:50: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:50: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:50: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:50: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:50: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:50: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:50: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:50: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:50: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:50: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:50: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:50: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:50: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:50: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:50: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:51: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:02:51: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:02:51: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:51: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:51: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:51: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:51: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:51: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:51: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:51: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:51: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:51: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:51: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:51: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:51: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:02:51: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:02:51: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:02:51: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:02:52: pid 12: LOG: new IPC connection received
2022-04-01 06:02:57: pid 12: LOG: new IPC connection received
2022-04-01 06:03:01: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:01: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:01: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:01: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:01: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:01: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:01: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:01: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:01: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:01: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:01: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:01: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:01: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:01: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:01: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:01: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:02: pid 12: LOG: new IPC connection received
2022-04-01 06:03:02: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:03:02: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:03:02: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:02: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:02: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:02: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:02: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:02: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:02: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:02: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:02: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:02: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:02: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:02: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:02: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:02: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:02: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:02: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:07: pid 12: LOG: new IPC connection received
2022-04-01 06:03:12: pid 12: LOG: new IPC connection received
2022-04-01 06:03:12: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:12: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:12: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:12: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:12: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:12: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:12: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:12: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:12: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:12: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:12: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:12: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:12: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:12: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:12: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:12: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:13: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:03:13: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:03:13: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:13: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:13: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:13: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:13: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:13: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:13: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:13: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:13: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:13: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:13: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:13: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:13: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:13: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:13: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:13: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:17: pid 12: LOG: new IPC connection received
2022-04-01 06:03:22: pid 12: LOG: new IPC connection received
2022-04-01 06:03:23: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:23: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:23: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:23: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:23: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:23: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:23: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:23: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:23: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:23: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:23: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:23: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:23: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:23: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:23: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:23: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:24: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:03:24: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:03:24: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:24: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:24: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:24: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:24: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:24: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:24: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:24: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:24: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:24: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:24: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:24: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:24: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:24: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:24: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:24: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:27: pid 12: LOG: new IPC connection received
2022-04-01 06:03:30: pid 113: LOG: forked new pcp worker, pid=260 socket=7
2022-04-01 06:03:30: pid 12: LOG: new IPC connection received
2022-04-01 06:03:30: pid 113: LOG: PCP process with pid: 260 exit with SUCCESS.
2022-04-01 06:03:30: pid 113: LOG: PCP process with pid: 260 exits with status 0
2022-04-01 06:03:31: pid 113: LOG: forked new pcp worker, pid=267 socket=7
2022-04-01 06:03:31: pid 113: LOG: PCP process with pid: 267 exit with SUCCESS.
2022-04-01 06:03:31: pid 113: LOG: PCP process with pid: 267 exits with status 0
2022-04-01 06:03:32: pid 12: LOG: new IPC connection received
2022-04-01 06:03:35: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:35: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:35: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:35: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:35: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:35: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:35: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:35: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:35: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:35: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:35: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:35: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:35: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:35: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:35: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:35: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:36: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:03:36: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:03:36: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:36: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:36: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:36: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:36: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:36: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:36: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:36: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:36: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:36: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:36: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:36: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:36: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:36: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:36: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:36: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:38: pid 12: LOG: new IPC connection received
2022-04-01 06:03:43: pid 12: LOG: new IPC connection received
2022-04-01 06:03:46: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:46: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:46: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:46: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:46: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:46: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:46: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:46: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:46: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:46: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:46: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:46: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:46: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:46: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:46: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:46: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:47: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:03:47: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:03:47: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:47: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:47: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:47: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:47: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:47: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:47: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:47: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:47: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:47: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:47: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:47: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:47: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:47: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:47: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:47: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:48: pid 12: LOG: new IPC connection received
2022-04-01 06:03:53: pid 12: LOG: new IPC connection received
2022-04-01 06:03:57: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:57: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:57: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:57: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:57: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:57: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:57: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:57: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:57: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:57: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:57: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:57: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:57: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:57: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:57: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:57: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:58: pid 12: LOG: new IPC connection received
2022-04-01 06:03:58: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:03:58: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:03:58: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:58: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:58: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:58: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:58: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:58: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:58: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:58: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:58: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:58: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:58: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:58: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:03:58: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:03:58: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:03:58: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:03:58: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:03: pid 12: LOG: new IPC connection received
2022-04-01 06:04:08: pid 12: LOG: new IPC connection received
2022-04-01 06:04:08: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:08: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:08: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:08: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:08: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:08: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:08: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:08: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:08: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:08: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:08: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:08: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:08: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:08: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:08: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:08: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:09: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:04:09: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:04:09: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:09: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:09: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:09: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:09: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:09: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:09: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:09: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:09: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:09: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:09: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:09: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:09: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:09: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:09: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:09: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:13: pid 12: LOG: new IPC connection received
2022-04-01 06:04:18: pid 12: LOG: new IPC connection received
2022-04-01 06:04:19: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:19: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:19: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:19: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:19: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:19: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:19: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:19: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:19: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:19: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:19: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:19: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:19: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:19: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:19: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:19: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:20: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:04:20: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:04:20: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:20: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:20: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:20: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:20: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:20: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:20: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:20: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:20: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:20: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:20: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:20: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:20: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:20: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:20: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:20: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:23: pid 12: LOG: new IPC connection received
2022-04-01 06:04:28: pid 12: LOG: new IPC connection received
2022-04-01 06:04:30: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:30: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:30: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:30: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:30: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:30: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:30: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:30: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:30: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:30: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:30: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:30: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:30: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:30: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:30: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:30: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:30: pid 113: LOG: forked new pcp worker, pid=274 socket=7
2022-04-01 06:04:30: pid 12: LOG: new IPC connection received
2022-04-01 06:04:30: pid 113: LOG: PCP process with pid: 274 exit with SUCCESS.
2022-04-01 06:04:30: pid 113: LOG: PCP process with pid: 274 exits with status 0
2022-04-01 06:04:31: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:04:31: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:04:31: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:31: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:31: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:31: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:31: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:31: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:31: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:31: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:31: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:31: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:31: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:31: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:31: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:31: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:31: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:31: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:31: pid 113: LOG: forked new pcp worker, pid=281 socket=7
2022-04-01 06:04:31: pid 113: LOG: PCP process with pid: 281 exit with SUCCESS.
2022-04-01 06:04:31: pid 113: LOG: PCP process with pid: 281 exits with status 0
2022-04-01 06:04:33: pid 12: LOG: new IPC connection received
2022-04-01 06:04:38: pid 12: LOG: new IPC connection received
2022-04-01 06:04:41: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:41: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:41: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:41: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:41: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:41: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:41: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:41: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:41: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:41: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:41: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:41: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:41: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:41: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:41: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:41: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:42: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:04:42: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:04:42: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:42: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:42: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:42: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:42: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:42: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:42: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:42: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:42: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:42: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:42: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:42: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:42: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:42: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:42: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:42: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:43: pid 12: LOG: new IPC connection received
2022-04-01 06:04:48: pid 12: LOG: new IPC connection received
2022-04-01 06:04:52: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:52: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:52: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:52: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:52: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:52: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:52: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:52: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:52: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:52: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:52: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:52: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:52: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:52: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:52: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:52: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:53: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:04:53: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:04:53: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:53: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:53: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:53: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:53: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:53: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:53: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:53: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:53: pid 12: LOG: new IPC connection received
2022-04-01 06:04:53: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:53: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:53: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:53: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:53: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:04:53: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:04:53: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:04:53: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:04:58: pid 12: LOG: new IPC connection received
2022-04-01 06:05:03: pid 12: LOG: new IPC connection received
2022-04-01 06:05:03: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:03: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:03: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:03: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:03: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:03: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:03: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:03: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:03: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:03: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:03: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:03: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:03: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:03: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:03: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:03: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:04: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:05:04: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:05:04: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:04: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:04: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:04: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:04: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:04: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:04: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:04: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:04: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:04: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:04: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:04: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:04: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:04: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:04: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:04: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:08: pid 12: LOG: new IPC connection received
2022-04-01 06:05:13: pid 12: LOG: new IPC connection received
2022-04-01 06:05:14: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:14: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:14: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:14: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:14: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:14: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:14: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:14: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:14: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:14: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:14: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:14: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:14: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:14: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:14: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:14: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:15: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:05:15: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:05:15: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:15: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:15: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:15: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:15: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:15: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:15: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:15: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:15: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:15: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:15: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:15: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:15: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:15: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:15: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:15: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:18: pid 12: LOG: new IPC connection received
2022-04-01 06:05:23: pid 12: LOG: new IPC connection received
2022-04-01 06:05:25: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:25: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:25: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:25: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:25: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:25: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:25: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:25: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:25: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:25: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:25: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:25: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:25: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:25: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:25: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:25: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:26: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:05:26: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:05:26: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:26: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:26: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:26: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:26: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:26: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:26: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:26: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:26: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:26: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:26: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:26: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:26: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:26: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:26: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:26: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:28: pid 12: LOG: new IPC connection received
2022-04-01 06:05:30: pid 113: LOG: forked new pcp worker, pid=288 socket=7
2022-04-01 06:05:30: pid 12: LOG: new IPC connection received
2022-04-01 06:05:30: pid 113: LOG: PCP process with pid: 288 exit with SUCCESS.
2022-04-01 06:05:30: pid 113: LOG: PCP process with pid: 288 exits with status 0
2022-04-01 06:05:31: pid 113: LOG: forked new pcp worker, pid=296 socket=7
2022-04-01 06:05:31: pid 113: LOG: PCP process with pid: 296 exit with SUCCESS.
2022-04-01 06:05:31: pid 113: LOG: PCP process with pid: 296 exits with status 0
2022-04-01 06:05:33: pid 12: LOG: new IPC connection received
2022-04-01 06:05:36: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:36: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:36: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:36: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:36: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:36: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:36: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:36: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:36: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:36: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:36: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:36: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:36: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:36: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:36: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:36: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:37: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:05:37: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:05:37: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:37: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:37: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:37: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:37: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:37: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:37: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:37: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:37: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:37: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:37: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:37: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:37: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:37: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:37: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:37: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:38: pid 12: LOG: new IPC connection received
2022-04-01 06:05:43: pid 12: LOG: new IPC connection received
2022-04-01 06:05:47: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:47: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:47: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:47: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:47: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:47: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:47: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:47: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:47: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:47: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:47: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:47: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:47: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:47: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:47: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:47: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:48: pid 12: LOG: new IPC connection received
2022-04-01 06:05:48: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:05:48: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:05:48: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:48: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:48: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:48: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:48: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:48: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:48: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:48: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:48: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:48: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:48: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:48: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:48: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:48: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:48: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:48: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:53: pid 12: LOG: new IPC connection received
2022-04-01 06:05:58: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:58: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:58: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:58: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:58: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:58: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:58: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:58: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:58: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:58: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:58: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:58: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:58: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:58: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:58: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:58: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:58: pid 12: LOG: new IPC connection received
2022-04-01 06:05:59: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:05:59: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:05:59: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:59: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:59: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:59: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:59: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:59: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:59: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:59: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:59: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:59: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:59: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:59: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:05:59: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:05:59: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:05:59: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:05:59: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:03: pid 12: LOG: new IPC connection received
2022-04-01 06:06:09: pid 12: LOG: new IPC connection received
2022-04-01 06:06:09: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:09: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:09: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:09: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:09: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:09: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:09: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:09: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:09: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:09: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:09: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:09: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:09: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:09: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:09: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:09: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:11: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:06:11: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:06:11: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:11: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:11: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:11: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:11: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:11: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:11: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:11: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:11: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:11: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:11: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:11: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:11: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:11: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:11: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:11: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:14: pid 12: LOG: new IPC connection received
2022-04-01 06:06:19: pid 12: LOG: new IPC connection received
2022-04-01 06:06:21: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:21: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:21: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:21: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:21: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:21: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:21: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:21: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:21: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:21: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:21: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:21: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:21: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:21: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:21: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:21: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:22: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:06:22: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:06:22: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:22: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:22: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:22: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:22: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:22: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:22: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:22: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:22: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:22: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:22: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:22: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:22: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:22: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:22: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:22: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:24: pid 12: LOG: new IPC connection received
2022-04-01 06:06:29: pid 12: LOG: new IPC connection received
2022-04-01 06:06:30: pid 113: LOG: forked new pcp worker, pid=304 socket=7
2022-04-01 06:06:30: pid 12: LOG: new IPC connection received
2022-04-01 06:06:30: pid 113: LOG: PCP process with pid: 304 exit with SUCCESS.
2022-04-01 06:06:30: pid 113: LOG: PCP process with pid: 304 exits with status 0
2022-04-01 06:06:31: pid 113: LOG: forked new pcp worker, pid=312 socket=7
2022-04-01 06:06:32: pid 113: LOG: PCP process with pid: 312 exit with SUCCESS.
2022-04-01 06:06:32: pid 113: LOG: PCP process with pid: 312 exits with status 0
2022-04-01 06:06:32: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:32: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:32: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:32: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:32: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:32: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:32: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:32: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:32: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:32: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:32: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:32: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:32: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:32: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:32: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:32: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:33: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:06:33: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:06:33: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:33: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:33: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:33: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:33: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:33: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:33: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:33: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:33: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:33: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:33: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:33: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:33: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:33: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:33: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:33: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:34: pid 12: LOG: new IPC connection received
2022-04-01 06:06:39: pid 12: LOG: new IPC connection received
2022-04-01 06:06:43: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:43: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:43: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:43: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:43: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:43: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:43: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:43: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:43: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:43: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:43: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:43: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:43: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:43: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:43: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:43: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:44: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:06:44: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:06:44: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:44: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:44: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:44: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:44: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:44: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:44: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:44: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:44: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:44: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:44: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:44: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:44: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:44: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:44: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:44: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:44: pid 12: LOG: new IPC connection received
2022-04-01 06:06:49: pid 12: LOG: new IPC connection received
2022-04-01 06:06:54: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:54: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:54: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:54: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:54: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:54: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:54: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:54: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:54: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:54: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:54: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:54: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:54: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:54: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:54: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:54: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:54: pid 12: LOG: new IPC connection received
2022-04-01 06:06:55: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:06:55: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:06:55: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:55: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:55: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:55: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:55: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:55: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:55: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:55: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:55: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:55: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:55: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:55: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:55: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:06:55: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:06:55: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:06:55: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:06:59: pid 12: LOG: new IPC connection received
2022-04-01 06:07:04: pid 12: LOG: new IPC connection received
2022-04-01 06:07:05: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:05: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:05: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:05: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:05: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:05: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:05: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:05: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:05: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:05: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:05: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:05: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:05: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:05: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:05: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:05: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:06: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:07:06: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:07:06: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:06: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:06: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:06: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:06: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:06: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:06: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:06: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:06: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:06: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:06: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:06: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:06: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:06: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:06: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:06: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:09: pid 12: LOG: new IPC connection received
2022-04-01 06:07:14: pid 12: LOG: new IPC connection received
2022-04-01 06:07:16: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:16: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:16: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:16: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:16: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:16: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:16: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:16: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:16: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:16: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:16: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:16: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:16: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:16: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:16: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:16: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:17: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:07:17: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:07:17: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:17: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:17: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:17: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:17: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:17: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:17: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:17: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:17: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:17: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:17: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:17: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:17: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:17: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:17: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:17: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:19: pid 12: LOG: new IPC connection received
2022-04-01 06:07:24: pid 12: LOG: new IPC connection received
2022-04-01 06:07:27: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:27: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:27: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:27: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:27: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:27: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:27: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:27: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:27: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:27: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:27: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:27: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:27: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:27: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:27: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:27: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:28: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:07:28: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:07:28: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:28: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:28: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:28: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:28: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:28: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:28: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:28: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:28: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:28: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:28: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:28: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:28: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:28: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:28: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:28: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:29: pid 12: LOG: new IPC connection received
2022-04-01 06:07:30: pid 113: LOG: forked new pcp worker, pid=320 socket=7
2022-04-01 06:07:30: pid 12: LOG: new IPC connection received
2022-04-01 06:07:30: pid 113: LOG: PCP process with pid: 320 exit with SUCCESS.
2022-04-01 06:07:30: pid 113: LOG: PCP process with pid: 320 exits with status 0
2022-04-01 06:07:31: pid 113: LOG: forked new pcp worker, pid=328 socket=7
2022-04-01 06:07:32: pid 113: LOG: PCP process with pid: 328 exit with SUCCESS.
2022-04-01 06:07:32: pid 113: LOG: PCP process with pid: 328 exits with status 0
2022-04-01 06:07:34: pid 12: LOG: new IPC connection received
2022-04-01 06:07:38: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:38: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:38: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:38: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:38: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:38: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:38: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:38: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:38: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:38: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:38: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:38: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:38: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:38: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:38: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:38: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:39: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:07:39: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:07:39: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:39: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:39: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:39: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:39: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:39: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:39: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:39: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:39: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:39: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:39: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:39: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:39: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:39: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:39: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:39: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:39: pid 12: LOG: new IPC connection received
2022-04-01 06:07:44: pid 12: LOG: new IPC connection received
2022-04-01 06:07:49: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:49: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:49: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:49: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:49: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:49: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:49: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:49: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:49: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:49: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:49: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:49: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:49: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:49: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:49: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:49: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:49: pid 12: LOG: new IPC connection received
2022-04-01 06:07:50: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:07:50: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:07:50: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:50: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:50: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:50: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:50: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:50: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:50: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:50: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:50: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:50: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:50: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:50: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:50: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:07:50: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:07:50: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:07:50: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:07:54: pid 12: LOG: new IPC connection received
2022-04-01 06:07:59: pid 12: LOG: new IPC connection received
2022-04-01 06:08:00: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:00: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:00: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:00: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:00: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:00: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:00: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:00: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:00: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:00: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:00: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:00: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:00: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:00: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:00: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:00: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:01: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:08:01: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:08:01: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:01: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:01: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:01: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:01: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:01: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:01: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:01: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:01: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:01: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:01: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:01: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:01: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:01: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:01: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:01: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:04: pid 12: LOG: new IPC connection received
2022-04-01 06:08:09: pid 12: LOG: new IPC connection received
2022-04-01 06:08:11: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:11: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:11: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:11: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:11: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:11: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:11: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:11: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:11: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:11: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:11: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:11: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:11: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:11: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:11: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:11: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:12: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:08:12: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:08:12: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:12: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:12: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:12: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:12: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:12: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:12: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:12: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:12: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:12: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:12: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:12: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:12: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:12: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:12: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:12: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:14: pid 12: LOG: new IPC connection received
2022-04-01 06:08:19: pid 12: LOG: new IPC connection received
2022-04-01 06:08:22: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:22: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:22: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:22: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:22: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:22: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:22: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:22: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:22: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:22: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:22: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:22: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:22: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:22: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:22: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:22: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:23: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:08:23: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:08:23: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:23: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:23: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:23: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:23: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:23: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:23: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:23: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:23: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:23: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:23: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:23: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:23: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:23: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:23: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:23: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:25: pid 12: LOG: new IPC connection received
2022-04-01 06:08:30: pid 12: LOG: new IPC connection received
2022-04-01 06:08:30: pid 113: LOG: forked new pcp worker, pid=335 socket=7
2022-04-01 06:08:30: pid 12: LOG: new IPC connection received
2022-04-01 06:08:30: pid 113: LOG: PCP process with pid: 335 exit with SUCCESS.
2022-04-01 06:08:30: pid 113: LOG: PCP process with pid: 335 exits with status 0
2022-04-01 06:08:31: pid 113: LOG: forked new pcp worker, pid=342 socket=7
2022-04-01 06:08:31: pid 113: LOG: PCP process with pid: 342 exit with SUCCESS.
2022-04-01 06:08:31: pid 113: LOG: PCP process with pid: 342 exits with status 0
2022-04-01 06:08:34: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:34: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:34: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:34: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:34: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:34: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:34: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:34: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:34: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:34: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:34: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:34: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:34: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:34: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:34: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:34: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:35: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:08:35: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:08:35: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:35: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:35: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:35: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:35: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:35: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:35: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:35: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:35: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:35: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:35: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:35: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:35: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:35: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:35: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:35: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:35: pid 12: LOG: new IPC connection received
2022-04-01 06:08:40: pid 12: LOG: new IPC connection received
2022-04-01 06:08:45: pid 12: LOG: new IPC connection received
2022-04-01 06:08:45: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:45: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:45: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:45: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:45: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:45: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:45: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:45: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:45: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:45: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:45: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:45: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:45: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:45: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:45: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:45: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:46: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:08:46: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:08:46: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:46: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:46: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:46: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:46: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:46: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:46: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:46: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:46: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:46: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:46: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:46: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:46: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:46: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:46: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:46: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:50: pid 12: LOG: new IPC connection received
2022-04-01 06:08:55: pid 12: LOG: new IPC connection received
2022-04-01 06:08:56: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:56: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:56: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:56: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:56: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:56: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:56: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:56: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:56: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:56: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:56: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:56: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:56: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:56: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:56: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:56: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:57: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:08:57: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:08:57: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:57: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:57: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:57: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:57: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:57: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:57: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:57: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:57: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:57: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:57: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:57: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:08:57: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:08:57: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:08:57: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:08:57: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:00: pid 12: LOG: new IPC connection received
2022-04-01 06:09:05: pid 12: LOG: new IPC connection received
2022-04-01 06:09:07: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:07: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:07: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:07: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:07: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:07: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:07: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:07: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:07: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:07: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:07: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:07: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:07: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:07: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:07: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:07: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:08: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:09:08: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:09:08: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:08: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:08: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:08: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:08: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:08: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:08: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:08: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:08: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:08: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:08: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:08: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:08: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:08: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:08: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:08: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:10: pid 12: LOG: new IPC connection received
2022-04-01 06:09:15: pid 12: LOG: new IPC connection received
2022-04-01 06:09:18: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:18: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:18: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:18: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:18: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:18: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:18: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:18: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:18: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:18: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:18: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:18: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:18: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:18: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:18: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:18: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:19: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:09:19: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:09:19: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:19: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:19: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:19: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:19: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:19: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:19: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:19: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:19: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:19: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:19: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:19: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:19: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:19: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:19: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:19: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:20: pid 12: LOG: new IPC connection received
2022-04-01 06:09:25: pid 12: LOG: new IPC connection received
2022-04-01 06:09:29: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:29: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:29: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:29: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:29: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:29: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:29: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:29: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:29: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:29: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:29: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:29: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:29: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:29: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:29: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:29: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:30: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:09:30: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:09:30: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:30: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:30: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:30: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:30: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:30: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:30: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:30: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:30: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:30: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:30: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:30: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:30: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:30: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:30: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:30: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:30: pid 12: LOG: new IPC connection received
2022-04-01 06:09:31: pid 113: LOG: forked new pcp worker, pid=350 socket=7
2022-04-01 06:09:31: pid 12: LOG: new IPC connection received
2022-04-01 06:09:31: pid 113: LOG: PCP process with pid: 350 exit with SUCCESS.
2022-04-01 06:09:31: pid 113: LOG: PCP process with pid: 350 exits with status 0
2022-04-01 06:09:32: pid 113: LOG: forked new pcp worker, pid=357 socket=7
2022-04-01 06:09:32: pid 113: LOG: PCP process with pid: 357 exit with SUCCESS.
2022-04-01 06:09:32: pid 113: LOG: PCP process with pid: 357 exits with status 0
2022-04-01 06:09:35: pid 12: LOG: new IPC connection received
2022-04-01 06:09:40: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:40: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:40: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:40: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:40: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:40: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:40: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:40: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:40: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:40: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:40: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:40: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:40: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:40: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:40: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:40: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:40: pid 12: LOG: new IPC connection received
2022-04-01 06:09:41: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:09:41: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:09:41: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:41: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:41: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:41: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:41: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:41: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:41: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:41: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:41: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:41: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:41: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:41: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:41: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:41: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:41: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:41: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:45: pid 12: LOG: new IPC connection received
2022-04-01 06:09:50: pid 12: LOG: new IPC connection received
2022-04-01 06:09:51: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:51: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:51: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:51: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:51: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:51: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:51: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:51: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:51: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:51: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:51: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:51: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:51: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:51: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:51: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:51: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:52: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:09:52: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:09:52: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:52: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:52: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:52: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:52: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:52: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:52: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:52: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:52: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:52: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:52: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:52: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:52: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:09:52: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:09:52: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:09:52: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:09:55: pid 12: LOG: new IPC connection received
2022-04-01 06:10:00: pid 12: LOG: new IPC connection received
2022-04-01 06:10:02: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:02: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:02: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:02: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:02: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:02: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:02: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:02: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:02: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:02: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:02: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:02: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:02: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:02: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:02: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:02: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:03: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:10:03: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:10:03: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:03: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:03: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:03: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:03: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:03: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:03: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:03: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:03: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:03: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:03: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:03: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:03: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:03: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:03: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:03: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:05: pid 12: LOG: new IPC connection received
2022-04-01 06:10:10: pid 12: LOG: new IPC connection received
2022-04-01 06:10:13: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:13: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:13: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:13: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:13: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:13: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:13: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:13: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:13: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:13: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:13: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:13: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:13: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:13: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:13: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:13: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:14: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:10:14: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:10:14: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:14: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:14: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:14: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:14: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:14: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:14: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:14: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:14: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:14: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:14: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:14: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:14: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:14: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:14: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:14: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:15: pid 12: LOG: new IPC connection received
2022-04-01 06:10:20: pid 12: LOG: new IPC connection received
2022-04-01 06:10:24: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:24: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:24: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:24: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:24: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:24: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:24: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:24: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:24: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:24: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:24: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:24: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:24: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:24: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:24: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:24: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:25: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:10:25: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:10:25: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:25: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:25: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:25: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:25: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:25: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:25: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:25: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:25: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:25: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:25: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:25: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:25: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:25: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:25: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:25: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:26: pid 12: LOG: new IPC connection received
2022-04-01 06:10:30: pid 113: LOG: forked new pcp worker, pid=365 socket=7
2022-04-01 06:10:30: pid 12: LOG: new IPC connection received
2022-04-01 06:10:30: pid 113: LOG: PCP process with pid: 365 exit with SUCCESS.
2022-04-01 06:10:30: pid 113: LOG: PCP process with pid: 365 exits with status 0
2022-04-01 06:10:31: pid 12: LOG: new IPC connection received
2022-04-01 06:10:32: pid 113: LOG: forked new pcp worker, pid=373 socket=7
2022-04-01 06:10:32: pid 113: LOG: PCP process with pid: 373 exit with SUCCESS.
2022-04-01 06:10:32: pid 113: LOG: PCP process with pid: 373 exits with status 0
2022-04-01 06:10:35: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:35: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:35: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:35: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:35: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:35: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:35: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:35: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:35: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:35: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:35: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:35: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:35: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:35: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:35: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:35: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:36: pid 12: LOG: new IPC connection received
2022-04-01 06:10:36: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:10:36: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:10:36: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:36: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:36: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:36: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:36: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:36: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:36: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:36: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:36: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:36: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:36: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:36: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:36: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:36: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:36: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:36: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:41: pid 12: LOG: new IPC connection received
2022-04-01 06:10:46: pid 12: LOG: new IPC connection received
2022-04-01 06:10:46: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:46: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:46: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:46: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:46: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:46: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:46: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:46: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:46: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:46: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:46: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:46: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:46: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:46: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:46: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:46: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:47: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:10:47: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:10:47: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:47: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:47: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:47: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:47: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:47: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:47: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:47: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:47: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:47: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:47: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:47: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:47: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:47: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:47: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:47: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:51: pid 12: LOG: new IPC connection received
2022-04-01 06:10:56: pid 12: LOG: new IPC connection received
2022-04-01 06:10:57: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:57: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:57: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:57: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:57: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:57: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:57: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:57: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:57: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:57: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:57: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:57: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:57: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:57: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:57: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:57: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:58: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:10:58: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:10:58: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:58: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:58: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:58: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:58: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:58: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:58: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:58: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:58: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:58: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:58: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:58: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:10:58: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:10:58: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:10:58: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:10:58: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:11:01: pid 12: LOG: new IPC connection received
2022-04-01 06:11:06: pid 12: LOG: new IPC connection received
2022-04-01 06:11:08: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:11:08: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:11:08: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:11:08: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:11:08: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:11:08: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:11:08: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:11:08: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:11:08: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:11:08: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:11:08: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:11:08: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:11:08: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:11:08: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:11:08: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:11:08: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:11:09: pid 12: LOG: lost remote node "172.29.30.1:5432 Linux 43a0ec8556bb" is requesting to join the cluster
2022-04-01 06:11:09: pid 12: DETAIL: rejecting the request until life-check inform us that it is reachable again
2022-04-01 06:11:09: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:11:09: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:11:09: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:11:09: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:11:09: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:11:09: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:11:09: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:11:09: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:11:09: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:11:09: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:11:09: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:11:09: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:11:09: pid 12: LOG: we have received the NODE INFO message from the node:"172.29.30.1:5432 Linux 43a0ec8556bb" that was lost
2022-04-01 06:11:09: pid 12: DETAIL: we had lost this node because of "REPORTED BY LIFECHECK"
2022-04-01 06:11:09: pid 12: LOG: node:"172.29.30.1:5432 Linux 43a0ec8556bb" was reported lost by the lifecheck process
2022-04-01 06:11:09: pid 12: DETAIL: only life-check process can mark this node alive again
2022-04-01 06:11:11: pid 12: LOG: new IPC connection received
2022-04-01 06:11:16: pid 12: LOG: new IPC connection received
2022-04-01 06:11:21: pid 12: LOG: new IPC connection received
2022-04-01 06:11:26: pid 12: LOG: new IPC connection received
2022-04-01 06:11:30: pid 113: LOG: forked new pcp worker, pid=380 socket=7
2022-04-01 06:11:30: pid 12: LOG: new IPC connection received
2022-04-01 06:11:30: pid 113: LOG: PCP process with pid: 380 exit with SUCCESS.
2022-04-01 06:11:30: pid 113: LOG: PCP process with pid: 380 exits with status 0
2022-04-01 06:11:31: pid 12: LOG: new IPC connection received
2022-04-01 06:11:32: pid 113: LOG: forked new pcp worker, pid=387 socket=7
2022-04-01 06:11:36: pid 12: LOG: new IPC connection received
2022-04-01 06:11:37: pid 113: LOG: PCP process with pid: 387 exit with SUCCESS.
2022-04-01 06:11:37: pid 113: LOG: PCP process with pid: 387 exits with status 0
2022-04-01 06:11:41: pid 12: LOG: new IPC connection received
2022-04-01 06:11:46: pid 12: LOG: new IPC connection received
2022-04-01 06:11:51: pid 12: LOG: new IPC connection received
2022-04-01 06:11:56: pid 12: LOG: new IPC connection received
2022-04-01 06:12:01: pid 12: LOG: new IPC connection received
2022-04-01 06:12:06: pid 12: LOG: new IPC connection received
2022-04-01 06:12:11: pid 12: LOG: new IPC connection received
2022-04-01 06:12:14: pid 12: LOG: new watchdog node connection is received from "172.29.30.1:46811"
2022-04-01 06:12:14: pid 12: LOG: new node joined the cluster hostname:"172.29.30.1" port:9009 pgpool_port:5432
2022-04-01 06:12:14: pid 12: DETAIL: Pgpool-II version:"4.3.1" watchdog messaging version: 1.2
2022-04-01 06:12:14: pid 12: LOG: The newly joined node:"172.29.30.1:5432 Linux ea684c11f759" had left the cluster because it was lost
2022-04-01 06:12:14: pid 12: DETAIL: lost reason was "REPORTED BY LIFECHECK" and startup time diff = 765
2022-04-01 06:12:14: pid 12: LOG: read from socket failed with error :"Connection reset by peer"
2022-04-01 06:12:14: pid 12: LOG: client socket of 172.29.30.1:5432 Linux ea684c11f759 is closed
2022-04-01 06:12:14: pid 12: LOG: new outbound connection to 172.29.30.1:9009
2022-04-01 06:12:16: pid 12: LOG: new IPC connection received
2022-04-01 06:12:20: pid 12: LOG: adding watchdog node "172.29.30.1:5432 Linux ea684c11f759" to the standby list
2022-04-01 06:12:21: pid 12: LOG: new IPC connection received
2022-04-01 06:12:26: pid 12: LOG: new IPC connection received
2022-04-01 06:12:30: pid 13: LOG: informing the node status change to watchdog
2022-04-01 06:12:30: pid 13: DETAIL: node id :0 status = "NODE ALIVE" message:"Heartbeat signal found"
2022-04-01 06:12:30: pid 12: LOG: new IPC connection received
2022-04-01 06:12:30: pid 12: LOG: received node status change ipc message
2022-04-01 06:12:30: pid 12: DETAIL: Heartbeat signal found
2022-04-01 06:12:30: pid 12: LOG: remote node "172.29.30.1:5432 Linux ea684c11f759" became reachable again
2022-04-01 06:12:30: pid 12: DETAIL: requesting the node info
2022-04-01 06:12:30: pid 12: LOG: remote node "172.29.30.1:5432 Linux ea684c11f759" is reachable again
2022-04-01 06:12:30: pid 12: DETAIL: trying to add it back as a standby
2022-04-01 06:12:30: pid 113: LOG: forked new pcp worker, pid=394 socket=7
2022-04-01 06:12:30: pid 12: LOG: new IPC connection received
2022-04-01 06:12:30: pid 113: LOG: PCP process with pid: 394 exit with SUCCESS.
2022-04-01 06:12:30: pid 113: LOG: PCP process with pid: 394 exits with status 0
2022-04-01 06:12:31: pid 12: LOG: new IPC connection received
2022-04-01 06:12:31: pid 113: LOG: forked new pcp worker, pid=402 socket=7
2022-04-01 06:12:32: pid 113: LOG: PCP process with pid: 402 exit with SUCCESS.
2022-04-01 06:12:32: pid 113: LOG: PCP process with pid: 402 exits with status 0
2022-04-01 06:12:36: pid 12: LOG: new IPC connection received
2022-04-01 06:12:42: pid 12: LOG: new IPC connection received
2022-04-01 06:12:47: pid 12: LOG: new IPC connection received
2022-04-01 06:12:52: pid 12: LOG: new IPC connection received
2022-04-01 06:12:57: pid 12: LOG: new IPC connection received
2022-04-01 06:13:02: pid 12: LOG: new IPC connection received
2022-04-01 06:13:07: pid 12: LOG: new IPC connection received
2022-04-01 06:13:12: pid 12: LOG: new IPC connection received
2022-04-01 06:13:17: pid 12: LOG: new IPC connection received
2022-04-01 06:13:22: pid 12: LOG: new IPC connection received
2022-04-01 06:13:27: pid 12: LOG: new IPC connection received
2022-04-01 06:13:30: pid 113: LOG: forked new pcp worker, pid=410 socket=7
2022-04-01 06:13:30: pid 12: LOG: new IPC connection received
2022-04-01 06:13:30: pid 113: LOG: PCP process with pid: 410 exit with SUCCESS.
2022-04-01 06:13:30: pid 113: LOG: PCP process with pid: 410 exits with status 0
2022-04-01 06:13:31: pid 113: LOG: forked new pcp worker, pid=417 socket=7
2022-04-01 06:13:31: pid 113: LOG: PCP process with pid: 417 exit with SUCCESS.
2022-04-01 06:13:31: pid 113: LOG: PCP process with pid: 417 exits with status 0
2022-04-01 06:13:32: pid 12: LOG: new IPC connection received
2022-04-01 06:13:37: pid 12: LOG: new IPC connection received
2022-04-01 06:13:42: pid 12: LOG: new IPC connection received
2022-04-01 06:13:47: pid 12: LOG: new IPC connection received
More information about the pgpool-general
mailing list