[pgpool-general: 8401] Re: pgpool failing over on bad queries
Jon SCHEWE
jon.schewe at raytheon.com
Thu Sep 15 05:23:43 JST 2022
I switched streaming replication to not use SSL and this time it appears that the health check got the same SSL error.
2022-09-14 16:09:34.518: watchdog pid 938113: LOG: remote node "psql-03:9898 Linux psql-03" is asking to inform about quarantined backend nodes
2022-09-14 16:09:34.519: watchdog pid 938113: LOG: signal_user1_to_parent_with_reason(4)
2022-09-14 16:09:34.519: main pid 938106: LOG: Pgpool-II parent process received SIGUSR1
2022-09-14 16:09:34.519: main pid 938106: LOG: Pgpool-II parent process received inform quarantine nodes signal from watchdog
2022-09-14 16:09:34.981: health_check0 pid 938472: LOG: pool_ssl: "SSL_read": "no SSL error reported"
2022-09-14 16:09:34.981: health_check0 pid 938472: LOG: received degenerate backend request for node_id: 0 from pid [938472]
2022-09-14 16:09:34.981: watchdog pid 938113: LOG: new IPC connection received
2022-09-14 16:09:34.981: watchdog pid 938113: LOG: failover request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "psql-03:9898 Linux psql-03"
2022-09-14 16:09:34.981: watchdog pid 938113: DETAIL: waiting for the reply...
2022-09-14 16:09:34.983: health_check0 pid 938472: LOG: degenerate backend request for 1 node(s) from pid [938472], will be handled by watchdog
2022-09-14 16:09:34.984: health_check0 pid 938472: LOG: health check retrying on DB node: 0 (round:1)
2022-09-14 16:09:35.788: watchdog pid 938113: LOG: signal_user1_to_parent_with_reason(2)
2022-09-14 16:09:35.788: main pid 938106: LOG: Pgpool-II parent process received SIGUSR1
2022-09-14 16:09:35.788: main pid 938106: LOG: Pgpool-II parent process received sync backend signal from watchdog
2022-09-14 16:09:35.788: watchdog pid 938113: LOG: new IPC connection received
2022-09-14 16:09:35.788: main pid 938106: LOG: leader watchdog has performed failover
2022-09-14 16:09:35.788: main pid 938106: DETAIL: syncing the backend states from the LEADER watchdog node
2022-09-14 16:09:35.788: watchdog pid 938113: LOG: new IPC connection received
2022-09-14 16:09:35.788: watchdog pid 938113: LOG: received the get data request from local pgpool-II on IPC interface
2022-09-14 16:09:35.789: watchdog pid 938113: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to leader watchdog node "psql-03:9898 Linux psql-03"
2022-09-14 16:09:35.789: watchdog pid 938113: DETAIL: waiting for the reply...
2022-09-14 16:09:35.789: main pid 938106: LOG: leader watchdog node "psql-03:9898 Linux psql-03" returned status for 3 backend nodes
2022-09-14 16:09:35.789: main pid 938106: LOG: backend:0 is set to down status
2022-09-14 16:09:35.789: main pid 938106: DETAIL: backend:0 is DOWN on cluster leader "psql-03:9898 Linux psql-03"
2022-09-14 16:09:35.789: main pid 938106: LOG: 1 backend node(s) were detached because of backend status sync from "psql-03:9898 Linux psql-03"
2022-09-14 16:09:35.789: main pid 938106: DETAIL: restarting the children processes
2022-09-14 16:09:35.789: main pid 938106: LOG: Node 1 is not down (status: 1)
2022-09-14 16:09:35.790: sr_check_worker pid 940145: LOG: worker process received restart request
2022-09-14 16:09:35.799: main pid 938106: LOG: worker child process with pid: 940145 exits with status 256
2022-09-14 16:09:35.800: main pid 938106: LOG: fork a new worker child process with pid: 1148791
2022-09-14 16:09:35.800: sr_check_worker pid 1148791: LOG: process started
More information about the pgpool-general
mailing list