2023-09-26 15:24:29.379: main pid 1156: LOG:  reaper handler: exiting normally
2023-09-26 15:24:29.433: main pid 1156: LOG:  reaper handler
2023-09-26 15:24:29.434: main pid 1156: LOG:  reaper handler: exiting normally
2023-09-26 15:24:37.313: main pid 1156: LOG:  reaper handler
2023-09-26 15:24:37.314: main pid 1156: LOG:  reaper handler: exiting normally
2023-09-26 15:24:39.443: main pid 1156: LOG:  reaper handler
2023-09-26 15:24:39.444: main pid 1156: LOG:  reaper handler: exiting normally
2023-09-26 15:24:47.921: [unknown] pid 76610: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:47.921: [unknown] pid 76610: DETAIL:  timed out. retrying...
2023-09-26 15:24:49.155: health_check0 pid 1968: LOG:  failed to connect to PostgreSQL server on "servdbmopp001:5432", timed out
2023-09-26 15:24:49.155: health_check0 pid 1968: LOG:  health check retrying on DB node: 0 (round:1)
2023-09-26 15:24:50.390: [unknown] pid 81085: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:50.390: [unknown] pid 81085: DETAIL:  timed out. retrying...
2023-09-26 15:24:50.791: [unknown] pid 77111: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:50.791: [unknown] pid 77111: DETAIL:  timed out. retrying...
2023-09-26 15:24:50.995: [unknown] pid 77951: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:50.995: [unknown] pid 77951: DETAIL:  timed out. retrying...
2023-09-26 15:24:51.395: child pid 89812: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:51.395: child pid 89812: DETAIL:  timed out. retrying...
2023-09-26 15:24:51.465: [unknown] pid 78977: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:51.465: [unknown] pid 78977: DETAIL:  timed out. retrying...
2023-09-26 15:24:52.265: [unknown] pid 69048: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:52.265: [unknown] pid 69048: DETAIL:  timed out. retrying...
2023-09-26 15:24:52.420: child pid 89822: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:52.420: child pid 89822: DETAIL:  timed out. retrying...
2023-09-26 15:24:52.588: [unknown] pid 76366: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:52.588: [unknown] pid 76366: DETAIL:  timed out. retrying...
2023-09-26 15:24:52.845: [unknown] pid 87565: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:52.845: [unknown] pid 87565: DETAIL:  timed out. retrying...
2023-09-26 15:24:52.865: child pid 89838: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:52.865: child pid 89838: DETAIL:  timed out. retrying...
2023-09-26 15:24:53.127: [unknown] pid 77145: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:53.127: [unknown] pid 77145: DETAIL:  timed out. retrying...
2023-09-26 15:24:53.344: [unknown] pid 83999: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:53.344: [unknown] pid 83999: DETAIL:  timed out. retrying...
2023-09-26 15:24:53.348: [unknown] pid 76428: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:53.348: [unknown] pid 76428: DETAIL:  timed out. retrying...
2023-09-26 15:24:54.045: [unknown] pid 77345: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:54.045: [unknown] pid 77345: DETAIL:  timed out. retrying...
2023-09-26 15:24:54.277: [unknown] pid 78066: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:54.277: [unknown] pid 78066: DETAIL:  timed out. retrying...
2023-09-26 15:24:54.345: [unknown] pid 89029: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:54.345: [unknown] pid 89029: DETAIL:  timed out. retrying...
2023-09-26 15:24:54.348: child pid 89741: LOG:  trying connecting to PostgreSQL server on "servdbmopp001:5432" by INET socket
2023-09-26 15:24:54.348: child pid 89741: DETAIL:  timed out. retrying...
2023-09-26 15:24:54.554: PostgreSQL JDBC Driver pid 75646: LOG:  received degenerate backend request for node_id: 0 from pid [75646]
2023-09-26 15:24:54.554: watchdog pid 1279: LOG:  watchdog received the failover command from local pgpool-II on IPC interface
2023-09-26 15:24:54.554: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from local pgpool-II on IPC interface
2023-09-26 15:24:54.554: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:24:54.554: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:24:54.554: PostgreSQL JDBC Driver pid 75646: LOG:  signal_user1_to_parent_with_reason(0)
2023-09-26 15:24:54.555: PostgreSQL JDBC Driver pid 75646: WARNING:  write on backend 0 failed with error :"Broken pipe"
2023-09-26 15:24:54.555: PostgreSQL JDBC Driver pid 75646: DETAIL:  while trying to write data from offset: 0 wlen: 5
2023-09-26 15:24:54.555: main pid 1156: LOG:  Pgpool-II parent process received SIGUSR1
2023-09-26 15:24:54.555: main pid 1156: LOG:  Pgpool-II parent process has received failover request
2023-09-26 15:24:54.555: watchdog pid 1279: LOG:  received the failover indication from Pgpool-II on IPC interface
2023-09-26 15:24:54.555: watchdog pid 1279: LOG:  watchdog is informed of failover start by the main process
2023-09-26 15:24:54.556: main pid 1156: LOG:  === Starting degeneration. shutdown host servdbmopp001(5432) ===
2023-09-26 15:24:54.558: PostgreSQL JDBC Driver pid 78780: LOG:  received degenerate backend request for node_id: 0 from pid [78780]
2023-09-26 15:24:54.558: watchdog pid 1279: LOG:  watchdog received the failover command from local pgpool-II on IPC interface
2023-09-26 15:24:54.559: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from local pgpool-II on IPC interface
2023-09-26 15:24:54.559: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:24:54.559: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:24:54.562: main pid 1156: LOG:  Restart all children
2023-09-26 15:24:54.564: main pid 1156: LOG:  find_primary_node_repeatedly: waiting for finding a primary node
2023-09-26 15:24:57.170: health_check0 pid 1968: LOG:  failed to connect to PostgreSQL server on "servdbmopp001:5432", getsockopt() failed
2023-09-26 15:24:57.170: health_check0 pid 1968: DETAIL:  Operation now in progress
2023-09-26 15:24:57.170: health_check0 pid 1968: LOG:  health check failed on node 0 (timeout:0)
2023-09-26 15:24:57.170: health_check0 pid 1968: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:24:57.238: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:24:57.238: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:24:57.238: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:24:57.238: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:24:57.238: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:01.438: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89910 socket=7
2023-09-26 15:25:01.469: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89913 socket=7
2023-09-26 15:25:01.473: pcp_main pid 41329: LOG:  PCP process with pid: 89913 exit with SUCCESS.
2023-09-26 15:25:01.473: pcp_main pid 41329: LOG:  PCP process with pid: 89913 exits with status 0
2023-09-26 15:25:01.485: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89916 socket=7
2023-09-26 15:25:01.488: pcp_main pid 41329: LOG:  PCP process with pid: 89916 exit with SUCCESS.
2023-09-26 15:25:01.488: pcp_main pid 41329: LOG:  PCP process with pid: 89916 exits with status 0
2023-09-26 15:25:01.496: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89921 socket=7
2023-09-26 15:25:01.499: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89922 socket=7
2023-09-26 15:25:01.501: pcp_main pid 41329: LOG:  PCP process with pid: 89910 exit with SUCCESS.
2023-09-26 15:25:01.502: pcp_main pid 41329: LOG:  PCP process with pid: 89910 exits with status 0
2023-09-26 15:25:01.509: pcp_main pid 41329: LOG:  PCP process with pid: 89921 exit with SUCCESS.
2023-09-26 15:25:01.509: pcp_main pid 41329: LOG:  PCP process with pid: 89921 exits with status 0
2023-09-26 15:25:01.509: pcp_main pid 41329: LOG:  PCP process with pid: 89922 exit with SUCCESS.
2023-09-26 15:25:01.509: pcp_main pid 41329: LOG:  PCP process with pid: 89922 exits with status 0
2023-09-26 15:25:01.511: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89929 socket=7
2023-09-26 15:25:01.520: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89931 socket=7
2023-09-26 15:25:01.525: pcp_main pid 41329: LOG:  PCP process with pid: 89931 exit with SUCCESS.
2023-09-26 15:25:01.526: pcp_main pid 41329: LOG:  PCP process with pid: 89931 exits with status 0
2023-09-26 15:25:01.532: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89932 socket=7
2023-09-26 15:25:01.542: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89933 socket=7
2023-09-26 15:25:01.545: pcp_main pid 41329: LOG:  PCP process with pid: 89933 exit with SUCCESS.
2023-09-26 15:25:01.545: pcp_main pid 41329: LOG:  PCP process with pid: 89933 exits with status 0
2023-09-26 15:25:01.566: pcp_main pid 41329: LOG:  PCP process with pid: 89929 exit with SUCCESS.
2023-09-26 15:25:01.566: pcp_main pid 41329: LOG:  PCP process with pid: 89929 exits with status 0
2023-09-26 15:25:01.593: pcp_main pid 41329: LOG:  PCP process with pid: 89932 exit with SUCCESS.
2023-09-26 15:25:01.593: pcp_main pid 41329: LOG:  PCP process with pid: 89932 exits with status 0
2023-09-26 15:25:01.605: pcp_main pid 41329: LOG:  forked new pcp worker, pid=89939 socket=7
2023-09-26 15:25:01.655: pcp_main pid 41329: LOG:  PCP process with pid: 89939 exit with SUCCESS.
2023-09-26 15:25:01.655: pcp_main pid 41329: LOG:  PCP process with pid: 89939 exits with status 0
2023-09-26 15:25:03.245: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:03.245: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:03.245: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:03.245: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:03.245: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:09.251: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:09.251: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:09.251: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:09.251: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:09.251: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:15.257: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:15.257: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:15.257: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:15.257: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:15.257: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:21.263: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:21.263: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:21.263: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:21.263: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:21.263: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:27.270: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:27.270: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:27.270: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:27.270: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:27.270: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:33.275: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:33.275: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:33.275: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:33.275: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:33.275: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:39.280: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:39.281: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:39.281: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:39.281: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:39.281: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:45.286: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:45.286: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:45.286: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:45.286: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:45.286: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:51.295: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:51.295: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:51.295: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:51.295: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:51.295: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:25:57.300: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:25:57.300: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:25:57.300: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:25:57.300: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:25:57.300: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:03.305: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:03.305: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:03.305: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:03.305: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:03.305: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:09.310: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:09.310: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:09.310: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:09.310: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:09.310: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:15.315: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:15.315: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:15.315: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:15.315: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:15.315: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:21.322: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:21.322: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:21.322: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:21.322: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:21.322: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:27.328: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:27.328: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:27.328: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:27.328: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:27.328: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:33.334: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:33.334: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:33.334: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:33.334: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:33.334: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:39.339: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:39.339: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:39.339: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:39.339: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:39.339: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:45.346: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:45.347: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:45.347: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:45.347: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:45.347: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:51.355: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:51.355: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:51.355: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:51.355: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:51.355: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:26:57.360: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:26:57.360: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:26:57.361: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:26:57.361: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:26:57.361: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:03.366: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:03.366: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:03.366: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:03.366: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:03.366: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:09.371: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:09.371: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:09.371: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:09.371: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:09.371: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:15.376: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:15.376: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:15.376: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:15.376: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:15.376: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:21.387: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:21.387: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:21.387: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:21.387: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:21.387: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:27.393: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:27.393: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:27.393: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:27.393: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:27.393: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:33.399: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:33.399: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:33.400: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:33.400: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:33.400: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:39.405: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:39.405: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:39.405: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:39.405: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:39.405: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:43.974: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90103 socket=7
2023-09-26 15:27:44.027: pcp_main pid 41329: LOG:  PCP process with pid: 90103 exit with SUCCESS.
2023-09-26 15:27:44.027: pcp_main pid 41329: LOG:  PCP process with pid: 90103 exits with status 0
2023-09-26 15:27:45.412: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:45.413: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:45.413: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:45.413: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:45.413: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:51.419: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:51.419: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:51.419: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:51.419: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:51.419: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:27:57.425: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:27:57.425: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:27:57.425: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:27:57.425: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:27:57.425: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:03.430: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:03.430: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:03.430: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:03.430: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:03.430: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:09.436: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:09.436: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:09.436: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:09.436: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:09.436: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:15.443: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:15.443: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:15.443: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:15.443: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:15.443: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:16.502: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:16.502: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:16.502: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:16.502: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:16.502: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:18.427: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90138 socket=7
2023-09-26 15:28:18.474: pcp_main pid 41329: LOG:  PCP process with pid: 90138 exit with SUCCESS.
2023-09-26 15:28:18.474: pcp_main pid 41329: LOG:  PCP process with pid: 90138 exits with status 0
2023-09-26 15:28:19.536: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:19.536: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:19.536: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:19.536: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:19.536: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:21.448: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:21.448: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:21.448: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:21.448: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:21.448: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:27.454: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:27.454: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:27.454: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:27.454: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:27.454: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:33.459: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:33.459: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:33.459: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:33.459: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:33.459: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:39.465: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:39.465: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:39.465: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:39.465: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:39.465: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:45.470: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:45.471: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:45.471: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:45.471: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:45.471: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:51.479: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:51.479: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:51.479: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:51.479: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:51.479: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:28:57.485: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:28:57.485: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:28:57.485: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:28:57.485: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:28:57.485: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:03.492: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:03.492: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:03.492: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:03.492: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:03.492: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:09.498: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:09.498: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:09.498: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:09.498: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:09.498: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:15.503: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:15.503: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:15.503: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:15.503: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:15.503: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:21.509: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:21.509: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:21.509: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:21.509: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:21.509: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:27.514: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:27.514: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:27.514: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:27.514: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:27.514: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:33.519: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:33.520: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:33.520: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:33.520: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:33.520: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:39.525: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:39.525: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:39.525: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:39.525: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:39.525: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:45.534: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:45.534: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:45.534: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:45.534: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:45.534: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:51.542: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:51.542: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:51.542: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:51.542: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:51.542: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:29:57.551: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:29:57.551: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:29:57.551: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:29:57.551: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:29:57.551: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:01.680: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90293 socket=7
2023-09-26 15:30:01.695: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90296 socket=7
2023-09-26 15:30:01.697: pcp_main pid 41329: LOG:  PCP process with pid: 90293 exit with SUCCESS.
2023-09-26 15:30:01.697: pcp_main pid 41329: LOG:  PCP process with pid: 90293 exits with status 0
2023-09-26 15:30:01.708: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90300 socket=7
2023-09-26 15:30:01.717: pcp_main pid 41329: LOG:  PCP process with pid: 90300 exit with SUCCESS.
2023-09-26 15:30:01.717: pcp_main pid 41329: LOG:  PCP process with pid: 90300 exits with status 0
2023-09-26 15:30:01.732: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90303 socket=7
2023-09-26 15:30:01.735: pcp_main pid 41329: LOG:  PCP process with pid: 90303 exit with SUCCESS.
2023-09-26 15:30:01.735: pcp_main pid 41329: LOG:  PCP process with pid: 90303 exits with status 0
2023-09-26 15:30:01.749: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90305 socket=7
2023-09-26 15:30:01.752: pcp_main pid 41329: LOG:  PCP process with pid: 90305 exit with SUCCESS.
2023-09-26 15:30:01.752: pcp_main pid 41329: LOG:  PCP process with pid: 90305 exits with status 0
2023-09-26 15:30:01.762: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90308 socket=7
2023-09-26 15:30:01.766: pcp_main pid 41329: LOG:  PCP process with pid: 90308 exit with SUCCESS.
2023-09-26 15:30:01.766: pcp_main pid 41329: LOG:  PCP process with pid: 90308 exits with status 0
2023-09-26 15:30:01.771: pcp_main pid 41329: LOG:  PCP process with pid: 90296 exit with SUCCESS.
2023-09-26 15:30:01.771: pcp_main pid 41329: LOG:  PCP process with pid: 90296 exits with status 0
2023-09-26 15:30:01.777: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90316 socket=7
2023-09-26 15:30:01.780: pcp_main pid 41329: LOG:  PCP process with pid: 90316 exit with SUCCESS.
2023-09-26 15:30:01.780: pcp_main pid 41329: LOG:  PCP process with pid: 90316 exits with status 0
2023-09-26 15:30:01.782: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90320 socket=7
2023-09-26 15:30:01.796: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90322 socket=7
2023-09-26 15:30:01.838: pcp_main pid 41329: LOG:  PCP process with pid: 90320 exit with SUCCESS.
2023-09-26 15:30:01.839: pcp_main pid 41329: LOG:  PCP process with pid: 90320 exits with status 0
2023-09-26 15:30:01.864: pcp_main pid 41329: LOG:  PCP process with pid: 90322 exit with SUCCESS.
2023-09-26 15:30:01.864: pcp_main pid 41329: LOG:  PCP process with pid: 90322 exits with status 0
2023-09-26 15:30:01.875: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90327 socket=7
2023-09-26 15:30:01.922: pcp_main pid 41329: LOG:  PCP process with pid: 90327 exit with SUCCESS.
2023-09-26 15:30:01.922: pcp_main pid 41329: LOG:  PCP process with pid: 90327 exits with status 0
2023-09-26 15:30:03.563: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:03.563: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:03.563: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:03.564: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:03.564: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:09.575: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:09.575: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:09.575: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:09.575: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:09.575: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:15.585: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:15.585: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:15.585: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:15.585: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:15.585: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:21.595: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:21.595: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:21.595: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:21.595: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:21.595: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:27.608: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:27.608: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:27.608: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:27.608: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:27.608: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:33.617: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:33.618: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:33.618: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:33.618: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:33.618: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:39.631: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:39.631: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:39.631: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:39.631: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:39.631: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:45.645: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:45.645: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:45.645: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:45.645: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:45.645: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:51.657: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:51.657: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:51.657: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:51.657: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:51.657: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:30:57.667: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:30:57.667: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:30:57.667: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:30:57.667: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:30:57.667: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:03.679: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:03.679: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:03.679: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:03.679: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:03.679: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:09.689: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:09.689: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:09.689: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:09.689: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:09.689: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:15.699: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:15.699: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:15.699: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:15.699: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:15.699: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:21.708: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:21.708: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:21.708: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:21.708: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:21.708: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:27.717: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:27.717: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:27.717: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:27.717: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:27.717: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:33.725: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:33.725: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:33.725: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:33.725: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:33.725: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:31:39.735: watchdog pid 1279: LOG:  watchdog received the failover command from remote pgpool-II node "servasmogp002:5432 Linux servasmogp002"
2023-09-26 15:31:39.735: watchdog pid 1279: LOG:  watchdog is processing the failover command [DEGENERATE_BACKEND_REQUEST] received from servasmogp002:5432 Linux servasmogp002
2023-09-26 15:31:39.735: watchdog pid 1279: LOG:  we have got the consensus to perform the failover
2023-09-26 15:31:39.735: watchdog pid 1279: DETAIL:  1 node(s) voted in the favor
2023-09-26 15:31:39.735: watchdog pid 1279: LOG:  invalid degenerate backend request, node id : 0 status: [3] is not valid for failover
2023-09-26 15:35:01.400: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90724 socket=7
2023-09-26 15:35:01.426: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90727 socket=7
2023-09-26 15:35:01.429: pcp_main pid 41329: LOG:  PCP process with pid: 90727 exit with SUCCESS.
2023-09-26 15:35:01.429: pcp_main pid 41329: LOG:  PCP process with pid: 90727 exits with status 0
2023-09-26 15:35:01.440: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90730 socket=7
2023-09-26 15:35:01.445: pcp_main pid 41329: LOG:  PCP process with pid: 90730 exit with SUCCESS.
2023-09-26 15:35:01.445: pcp_main pid 41329: LOG:  PCP process with pid: 90730 exits with status 0
2023-09-26 15:35:01.459: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90735 socket=7
2023-09-26 15:35:01.461: pcp_main pid 41329: LOG:  PCP process with pid: 90735 exit with SUCCESS.
2023-09-26 15:35:01.461: pcp_main pid 41329: LOG:  PCP process with pid: 90735 exits with status 0
2023-09-26 15:35:01.478: pcp_main pid 41329: LOG:  PCP process with pid: 90724 exit with SUCCESS.
2023-09-26 15:35:01.478: pcp_main pid 41329: LOG:  PCP process with pid: 90724 exits with status 0
2023-09-26 15:35:01.482: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90743 socket=7
2023-09-26 15:35:01.482: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90744 socket=7
2023-09-26 15:35:01.541: pcp_main pid 41329: LOG:  PCP process with pid: 90744 exit with SUCCESS.
2023-09-26 15:35:01.541: pcp_main pid 41329: LOG:  PCP process with pid: 90744 exits with status 0
2023-09-26 15:35:01.543: pcp_main pid 41329: LOG:  PCP process with pid: 90743 exit with SUCCESS.
2023-09-26 15:35:01.543: pcp_main pid 41329: LOG:  PCP process with pid: 90743 exits with status 0
2023-09-26 15:35:01.553: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90748 socket=7
2023-09-26 15:35:01.609: pcp_main pid 41329: LOG:  PCP process with pid: 90748 exit with SUCCESS.
2023-09-26 15:35:01.609: pcp_main pid 41329: LOG:  PCP process with pid: 90748 exits with status 0
2023-09-26 15:35:01.835: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90751 socket=7
2023-09-26 15:35:01.837: pcp_main pid 41329: LOG:  PCP process with pid: 90751 exit with SUCCESS.
2023-09-26 15:35:01.837: pcp_main pid 41329: LOG:  PCP process with pid: 90751 exits with status 0
2023-09-26 15:35:01.845: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90752 socket=7
2023-09-26 15:35:01.848: pcp_main pid 41329: LOG:  PCP process with pid: 90752 exit with SUCCESS.
2023-09-26 15:35:01.848: pcp_main pid 41329: LOG:  PCP process with pid: 90752 exits with status 0
2023-09-26 15:35:01.856: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90753 socket=7
2023-09-26 15:35:01.859: pcp_main pid 41329: LOG:  PCP process with pid: 90753 exit with SUCCESS.
2023-09-26 15:35:01.859: pcp_main pid 41329: LOG:  PCP process with pid: 90753 exits with status 0
2023-09-26 15:38:18.250: pcp_main pid 41329: LOG:  forked new pcp worker, pid=90956 socket=7
2023-09-26 15:38:18.315: pcp_main pid 41329: LOG:  PCP process with pid: 90956 exit with SUCCESS.
2023-09-26 15:38:18.315: pcp_main pid 41329: LOG:  PCP process with pid: 90956 exits with status 0
2023-09-26 15:40:01.304: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91146 socket=7
2023-09-26 15:40:01.353: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91150 socket=7
2023-09-26 15:40:01.357: pcp_main pid 41329: LOG:  PCP process with pid: 91150 exit with SUCCESS.
2023-09-26 15:40:01.357: pcp_main pid 41329: LOG:  PCP process with pid: 91150 exits with status 0
2023-09-26 15:40:01.367: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91153 socket=7
2023-09-26 15:40:01.371: pcp_main pid 41329: LOG:  PCP process with pid: 91153 exit with SUCCESS.
2023-09-26 15:40:01.371: pcp_main pid 41329: LOG:  PCP process with pid: 91153 exits with status 0
2023-09-26 15:40:01.382: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91158 socket=7
2023-09-26 15:40:01.384: pcp_main pid 41329: LOG:  PCP process with pid: 91146 exit with SUCCESS.
2023-09-26 15:40:01.384: pcp_main pid 41329: LOG:  PCP process with pid: 91146 exits with status 0
2023-09-26 15:40:01.387: pcp_main pid 41329: LOG:  PCP process with pid: 91158 exit with SUCCESS.
2023-09-26 15:40:01.387: pcp_main pid 41329: LOG:  PCP process with pid: 91158 exits with status 0
2023-09-26 15:40:01.394: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91165 socket=7
2023-09-26 15:40:01.405: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91167 socket=7
2023-09-26 15:40:01.465: pcp_main pid 41329: LOG:  PCP process with pid: 91165 exit with SUCCESS.
2023-09-26 15:40:01.465: pcp_main pid 41329: LOG:  PCP process with pid: 91165 exits with status 0
2023-09-26 15:40:01.474: pcp_main pid 41329: LOG:  PCP process with pid: 91167 exit with SUCCESS.
2023-09-26 15:40:01.474: pcp_main pid 41329: LOG:  PCP process with pid: 91167 exits with status 0
2023-09-26 15:40:01.487: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91172 socket=7
2023-09-26 15:40:01.556: pcp_main pid 41329: LOG:  PCP process with pid: 91172 exit with SUCCESS.
2023-09-26 15:40:01.556: pcp_main pid 41329: LOG:  PCP process with pid: 91172 exits with status 0
2023-09-26 15:40:01.991: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91174 socket=7
2023-09-26 15:40:01.995: pcp_main pid 41329: LOG:  PCP process with pid: 91174 exit with SUCCESS.
2023-09-26 15:40:01.995: pcp_main pid 41329: LOG:  PCP process with pid: 91174 exits with status 0
2023-09-26 15:40:02.007: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91175 socket=7
2023-09-26 15:40:02.010: pcp_main pid 41329: LOG:  PCP process with pid: 91175 exit with SUCCESS.
2023-09-26 15:40:02.010: pcp_main pid 41329: LOG:  PCP process with pid: 91175 exits with status 0
2023-09-26 15:40:02.023: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91176 socket=7
2023-09-26 15:40:02.026: pcp_main pid 41329: LOG:  PCP process with pid: 91176 exit with SUCCESS.
2023-09-26 15:40:02.026: pcp_main pid 41329: LOG:  PCP process with pid: 91176 exits with status 0
2023-09-26 15:45:01.139: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91564 socket=7
2023-09-26 15:45:01.143: pcp_main pid 41329: LOG:  PCP process with pid: 91564 exit with SUCCESS.
2023-09-26 15:45:01.143: pcp_main pid 41329: LOG:  PCP process with pid: 91564 exits with status 0
2023-09-26 15:45:01.151: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91565 socket=7
2023-09-26 15:45:01.154: pcp_main pid 41329: LOG:  PCP process with pid: 91565 exit with SUCCESS.
2023-09-26 15:45:01.154: pcp_main pid 41329: LOG:  PCP process with pid: 91565 exits with status 0
2023-09-26 15:45:01.164: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91566 socket=7
2023-09-26 15:45:01.166: pcp_main pid 41329: LOG:  PCP process with pid: 91566 exit with SUCCESS.
2023-09-26 15:45:01.166: pcp_main pid 41329: LOG:  PCP process with pid: 91566 exits with status 0
2023-09-26 15:45:02.078: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91582 socket=7
2023-09-26 15:45:02.103: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91585 socket=7
2023-09-26 15:45:02.106: pcp_main pid 41329: LOG:  PCP process with pid: 91585 exit with SUCCESS.
2023-09-26 15:45:02.106: pcp_main pid 41329: LOG:  PCP process with pid: 91585 exits with status 0
2023-09-26 15:45:02.116: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91588 socket=7
2023-09-26 15:45:02.119: pcp_main pid 41329: LOG:  PCP process with pid: 91588 exit with SUCCESS.
2023-09-26 15:45:02.119: pcp_main pid 41329: LOG:  PCP process with pid: 91588 exits with status 0
2023-09-26 15:45:02.130: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91593 socket=7
2023-09-26 15:45:02.133: pcp_main pid 41329: LOG:  PCP process with pid: 91593 exit with SUCCESS.
2023-09-26 15:45:02.133: pcp_main pid 41329: LOG:  PCP process with pid: 91593 exits with status 0
2023-09-26 15:45:02.146: pcp_main pid 41329: LOG:  PCP process with pid: 91582 exit with SUCCESS.
2023-09-26 15:45:02.146: pcp_main pid 41329: LOG:  PCP process with pid: 91582 exits with status 0
2023-09-26 15:45:02.154: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91601 socket=7
2023-09-26 15:45:02.157: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91602 socket=7
2023-09-26 15:45:02.214: pcp_main pid 41329: LOG:  PCP process with pid: 91602 exit with SUCCESS.
2023-09-26 15:45:02.214: pcp_main pid 41329: LOG:  PCP process with pid: 91602 exits with status 0
2023-09-26 15:45:02.215: pcp_main pid 41329: LOG:  PCP process with pid: 91601 exit with SUCCESS.
2023-09-26 15:45:02.215: pcp_main pid 41329: LOG:  PCP process with pid: 91601 exits with status 0
2023-09-26 15:45:02.225: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91607 socket=7
2023-09-26 15:45:02.285: pcp_main pid 41329: LOG:  PCP process with pid: 91607 exit with SUCCESS.
2023-09-26 15:45:02.285: pcp_main pid 41329: LOG:  PCP process with pid: 91607 exits with status 0
2023-09-26 15:48:18.106: pcp_main pid 41329: LOG:  forked new pcp worker, pid=91871 socket=7
2023-09-26 15:48:18.166: pcp_main pid 41329: LOG:  PCP process with pid: 91871 exit with SUCCESS.
2023-09-26 15:48:18.166: pcp_main pid 41329: LOG:  PCP process with pid: 91871 exits with status 0
2023-09-26 15:50:01.299: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92044 socket=7
2023-09-26 15:50:01.303: pcp_main pid 41329: LOG:  PCP process with pid: 92044 exit with SUCCESS.
2023-09-26 15:50:01.303: pcp_main pid 41329: LOG:  PCP process with pid: 92044 exits with status 0
2023-09-26 15:50:01.314: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92045 socket=7
2023-09-26 15:50:01.317: pcp_main pid 41329: LOG:  PCP process with pid: 92045 exit with SUCCESS.
2023-09-26 15:50:01.317: pcp_main pid 41329: LOG:  PCP process with pid: 92045 exits with status 0
2023-09-26 15:50:01.328: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92046 socket=7
2023-09-26 15:50:01.331: pcp_main pid 41329: LOG:  PCP process with pid: 92046 exit with SUCCESS.
2023-09-26 15:50:01.331: pcp_main pid 41329: LOG:  PCP process with pid: 92046 exits with status 0
2023-09-26 15:50:01.863: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92067 socket=7
2023-09-26 15:50:01.897: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92071 socket=7
2023-09-26 15:50:01.900: pcp_main pid 41329: LOG:  PCP process with pid: 92071 exit with SUCCESS.
2023-09-26 15:50:01.900: pcp_main pid 41329: LOG:  PCP process with pid: 92071 exits with status 0
2023-09-26 15:50:01.913: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92074 socket=7
2023-09-26 15:50:01.916: pcp_main pid 41329: LOG:  PCP process with pid: 92074 exit with SUCCESS.
2023-09-26 15:50:01.916: pcp_main pid 41329: LOG:  PCP process with pid: 92074 exits with status 0
2023-09-26 15:50:01.929: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92079 socket=7
2023-09-26 15:50:01.937: pcp_main pid 41329: LOG:  PCP process with pid: 92079 exit with SUCCESS.
2023-09-26 15:50:01.937: pcp_main pid 41329: LOG:  PCP process with pid: 92079 exits with status 0
2023-09-26 15:50:01.952: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92084 socket=7
2023-09-26 15:50:01.955: pcp_main pid 41329: LOG:  PCP process with pid: 92067 exit with SUCCESS.
2023-09-26 15:50:01.955: pcp_main pid 41329: LOG:  PCP process with pid: 92067 exits with status 0
2023-09-26 15:50:01.967: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92088 socket=7
2023-09-26 15:50:02.024: pcp_main pid 41329: LOG:  PCP process with pid: 92084 exit with SUCCESS.
2023-09-26 15:50:02.024: pcp_main pid 41329: LOG:  PCP process with pid: 92084 exits with status 0
2023-09-26 15:50:02.035: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92092 socket=7
2023-09-26 15:50:02.040: pcp_main pid 41329: LOG:  PCP process with pid: 92088 exit with SUCCESS.
2023-09-26 15:50:02.041: pcp_main pid 41329: LOG:  PCP process with pid: 92088 exits with status 0
2023-09-26 15:50:02.102: pcp_main pid 41329: LOG:  PCP process with pid: 92092 exit with SUCCESS.
2023-09-26 15:50:02.102: pcp_main pid 41329: LOG:  PCP process with pid: 92092 exits with status 0
2023-09-26 15:51:13.806: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92168 socket=7
2023-09-26 15:51:13.867: pcp_main pid 41329: LOG:  PCP process with pid: 92168 exit with SUCCESS.
2023-09-26 15:51:13.867: pcp_main pid 41329: LOG:  PCP process with pid: 92168 exits with status 0
2023-09-26 15:52:52.859: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92342 socket=7
2023-09-26 15:52:52.920: pcp_main pid 41329: LOG:  PCP process with pid: 92342 exit with SUCCESS.
2023-09-26 15:52:52.920: pcp_main pid 41329: LOG:  PCP process with pid: 92342 exits with status 0
2023-09-26 15:53:25.391: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92385 socket=7
2023-09-26 15:53:25.455: pcp_main pid 41329: LOG:  PCP process with pid: 92385 exit with SUCCESS.
2023-09-26 15:53:25.456: pcp_main pid 41329: LOG:  PCP process with pid: 92385 exits with status 0
2023-09-26 15:53:41.363: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92432 socket=7
2023-09-26 15:53:41.419: pcp_main pid 41329: LOG:  PCP process with pid: 92432 exit with SUCCESS.
2023-09-26 15:53:41.419: pcp_main pid 41329: LOG:  PCP process with pid: 92432 exits with status 0
2023-09-26 15:53:48.692: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92439 socket=7
2023-09-26 15:53:48.751: pcp_main pid 41329: LOG:  PCP process with pid: 92439 exit with SUCCESS.
2023-09-26 15:53:48.751: pcp_main pid 41329: LOG:  PCP process with pid: 92439 exits with status 0
2023-09-26 15:54:18.942: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92472 socket=7
2023-09-26 15:54:18.999: pcp_main pid 41329: LOG:  PCP process with pid: 92472 exit with SUCCESS.
2023-09-26 15:54:18.999: pcp_main pid 41329: LOG:  PCP process with pid: 92472 exits with status 0
2023-09-26 15:55:01.450: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92554 socket=7
2023-09-26 15:55:01.453: pcp_main pid 41329: LOG:  PCP process with pid: 92554 exit with SUCCESS.
2023-09-26 15:55:01.453: pcp_main pid 41329: LOG:  PCP process with pid: 92554 exits with status 0
2023-09-26 15:55:01.461: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92555 socket=7
2023-09-26 15:55:01.464: pcp_main pid 41329: LOG:  PCP process with pid: 92555 exit with SUCCESS.
2023-09-26 15:55:01.464: pcp_main pid 41329: LOG:  PCP process with pid: 92555 exits with status 0
2023-09-26 15:55:01.472: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92556 socket=7
2023-09-26 15:55:01.475: pcp_main pid 41329: LOG:  PCP process with pid: 92556 exit with SUCCESS.
2023-09-26 15:55:01.475: pcp_main pid 41329: LOG:  PCP process with pid: 92556 exits with status 0
2023-09-26 15:55:01.657: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92571 socket=7
2023-09-26 15:55:01.709: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92574 socket=7
2023-09-26 15:55:01.713: pcp_main pid 41329: LOG:  PCP process with pid: 92574 exit with SUCCESS.
2023-09-26 15:55:01.713: pcp_main pid 41329: LOG:  PCP process with pid: 92574 exits with status 0
2023-09-26 15:55:01.715: pcp_main pid 41329: LOG:  PCP process with pid: 92571 exit with SUCCESS.
2023-09-26 15:55:01.715: pcp_main pid 41329: LOG:  PCP process with pid: 92571 exits with status 0
2023-09-26 15:55:01.725: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92580 socket=7
2023-09-26 15:55:01.727: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92581 socket=7
2023-09-26 15:55:01.731: pcp_main pid 41329: LOG:  PCP process with pid: 92581 exit with SUCCESS.
2023-09-26 15:55:01.731: pcp_main pid 41329: LOG:  PCP process with pid: 92581 exits with status 0
2023-09-26 15:55:01.740: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92586 socket=7
2023-09-26 15:55:01.743: pcp_main pid 41329: LOG:  PCP process with pid: 92586 exit with SUCCESS.
2023-09-26 15:55:01.743: pcp_main pid 41329: LOG:  PCP process with pid: 92586 exits with status 0
2023-09-26 15:55:01.762: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92591 socket=7
2023-09-26 15:55:01.797: pcp_main pid 41329: LOG:  PCP process with pid: 92580 exit with SUCCESS.
2023-09-26 15:55:01.797: pcp_main pid 41329: LOG:  PCP process with pid: 92580 exits with status 0
2023-09-26 15:55:01.822: pcp_main pid 41329: LOG:  PCP process with pid: 92591 exit with SUCCESS.
2023-09-26 15:55:01.822: pcp_main pid 41329: LOG:  PCP process with pid: 92591 exits with status 0
2023-09-26 15:55:01.831: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92596 socket=7
2023-09-26 15:55:01.892: pcp_main pid 41329: LOG:  PCP process with pid: 92596 exit with SUCCESS.
2023-09-26 15:55:01.892: pcp_main pid 41329: LOG:  PCP process with pid: 92596 exits with status 0
2023-09-26 15:58:18.980: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92805 socket=7
2023-09-26 15:58:19.040: pcp_main pid 41329: LOG:  PCP process with pid: 92805 exit with SUCCESS.
2023-09-26 15:58:19.040: pcp_main pid 41329: LOG:  PCP process with pid: 92805 exits with status 0
2023-09-26 16:00:01.354: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92986 socket=7
2023-09-26 16:00:01.378: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92990 socket=7
2023-09-26 16:00:01.382: pcp_main pid 41329: LOG:  PCP process with pid: 92990 exit with SUCCESS.
2023-09-26 16:00:01.382: pcp_main pid 41329: LOG:  PCP process with pid: 92990 exits with status 0
2023-09-26 16:00:01.393: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92993 socket=7
2023-09-26 16:00:01.396: pcp_main pid 41329: LOG:  PCP process with pid: 92993 exit with SUCCESS.
2023-09-26 16:00:01.396: pcp_main pid 41329: LOG:  PCP process with pid: 92993 exits with status 0
2023-09-26 16:00:01.408: pcp_main pid 41329: LOG:  forked new pcp worker, pid=92998 socket=7
2023-09-26 16:00:01.412: pcp_main pid 41329: LOG:  PCP process with pid: 92998 exit with SUCCESS.
2023-09-26 16:00:01.412: pcp_main pid 41329: LOG:  PCP process with pid: 92998 exits with status 0
2023-09-26 16:00:01.427: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93003 socket=7
2023-09-26 16:00:01.432: pcp_main pid 41329: LOG:  PCP process with pid: 92986 exit with SUCCESS.
2023-09-26 16:00:01.432: pcp_main pid 41329: LOG:  PCP process with pid: 92986 exits with status 0
2023-09-26 16:00:01.442: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93007 socket=7
2023-09-26 16:00:01.494: pcp_main pid 41329: LOG:  PCP process with pid: 93003 exit with SUCCESS.
2023-09-26 16:00:01.494: pcp_main pid 41329: LOG:  PCP process with pid: 93003 exits with status 0
2023-09-26 16:00:01.505: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93011 socket=7
2023-09-26 16:00:01.513: pcp_main pid 41329: LOG:  PCP process with pid: 93007 exit with SUCCESS.
2023-09-26 16:00:01.513: pcp_main pid 41329: LOG:  PCP process with pid: 93007 exits with status 0
2023-09-26 16:00:01.574: pcp_main pid 41329: LOG:  PCP process with pid: 93011 exit with SUCCESS.
2023-09-26 16:00:01.574: pcp_main pid 41329: LOG:  PCP process with pid: 93011 exits with status 0
2023-09-26 16:00:01.615: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93014 socket=7
2023-09-26 16:00:01.619: pcp_main pid 41329: LOG:  PCP process with pid: 93014 exit with SUCCESS.
2023-09-26 16:00:01.619: pcp_main pid 41329: LOG:  PCP process with pid: 93014 exits with status 0
2023-09-26 16:00:01.629: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93015 socket=7
2023-09-26 16:00:01.631: pcp_main pid 41329: LOG:  PCP process with pid: 93015 exit with SUCCESS.
2023-09-26 16:00:01.631: pcp_main pid 41329: LOG:  PCP process with pid: 93015 exits with status 0
2023-09-26 16:00:01.641: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93016 socket=7
2023-09-26 16:00:01.644: pcp_main pid 41329: LOG:  PCP process with pid: 93016 exit with SUCCESS.
2023-09-26 16:00:01.644: pcp_main pid 41329: LOG:  PCP process with pid: 93016 exits with status 0
2023-09-26 16:00:23.530: pcp_main pid 41329: LOG:  forked new pcp worker, pid=93039 socket=7
2023-09-26 16:00:23.534: pcp_main pid 41329: LOG:  PCP process with pid: 93039 exit with SUCCESS.
2023-09-26 16:00:23.534: pcp_main pid 41329: LOG:  PCP process with pid: 93039 exits with status 0