View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000791Pgpool-IIBugpublic2023-03-24 18:242023-03-30 19:28
Reportersupakit.chavar Assigned Topengbo  
PrioritynormalSeverityminorReproducibilityunable to reproduce
Status assignedResolutionopen 
PlatformLinuxOSLinuxOS VersionCentOS 7
Product Version3.7.2 
Summary0000791: master watchdog has performed failover. but both node-0 (standby) and node-1 (primary) still alive.
Descriptionwe use Pgpool-II 3.7.2 for PostgreSQL 9.6 with below detail.

Pgpool-II 3.7.2 on centos 7
node0 as primary
node1 as standby

PostgreSQL 9.6 on centos 7
node0 as role standby
node1 as role primary.

The pgpool-ii 3.7.2 has performed failover but after check the DB it's still alive.

please see PGPOOL2SERVER.txt for more detail
Steps To Reproducecan't reproduce
TagsNo tags attached.

Activities

supakit.chavar

2023-03-24 18:24

reporter  

PGPOOL2SERVER.txt (22,707 bytes)    
Mar 23 09:25:01 PGPOOL2SERVER pgpool[9356]: [27039-1] 2023-03-23 09:25:01: pid 9356: LOG:  forked new pcp worker, pid=31533 socket=8
Mar 23 09:25:01 PGPOOL2SERVER pgpool[8091]: [8998-1] 2023-03-23 09:25:01: pid 8091: LOG:  new IPC connection received
Mar 23 09:25:01 PGPOOL2SERVER pgpool[9356]: [27040-1] 2023-03-23 09:25:01: pid 9356: LOG:  PCP process with pid: 31533 exit with SUCCESS.
Mar 23 09:25:01 PGPOOL2SERVER pgpool[9356]: [27041-1] 2023-03-23 09:25:01: pid 9356: LOG:  PCP process with pid: 31533 exits with status 0
Mar 23 09:25:01 PGPOOL2SERVER pgpool[9356]: [27042-1] 2023-03-23 09:25:01: pid 9356: LOG:  forked new pcp worker, pid=31539 socket=8
Mar 23 09:25:01 PGPOOL2SERVER pgpool[8091]: [8999-1] 2023-03-23 09:25:01: pid 8091: LOG:  new IPC connection received
Mar 23 09:25:01 PGPOOL2SERVER pgpool[9356]: [27043-1] 2023-03-23 09:25:01: pid 9356: LOG:  PCP process with pid: 31539 exit with SUCCESS.
Mar 23 09:25:01 PGPOOL2SERVER pgpool[9356]: [27044-1] 2023-03-23 09:25:01: pid 9356: LOG:  PCP process with pid: 31539 exits with status 0
Mar 23 09:29:18 PGPOOL2SERVER pgpool[8090]: [27991-1] 2023-03-23 09:29:18: pid 8090: LOG:  child process with pid: 23316 exits with status 256
Mar 23 09:29:18 PGPOOL2SERVER pgpool[8090]: [27992-1] 2023-03-23 09:29:18: pid 8090: LOG:  fork a new child process with pid: 32640
Mar 23 09:30:01 PGPOOL2SERVER pgpool[9356]: [27045-1] 2023-03-23 09:30:01: pid 9356: LOG:  forked new pcp worker, pid=300 socket=8
Mar 23 09:30:01 PGPOOL2SERVER pgpool[8091]: [9000-1] 2023-03-23 09:30:01: pid 8091: LOG:  new IPC connection received
Mar 23 09:30:01 PGPOOL2SERVER pgpool[9356]: [27046-1] 2023-03-23 09:30:01: pid 9356: LOG:  PCP process with pid: 300 exit with SUCCESS.
Mar 23 09:30:01 PGPOOL2SERVER pgpool[9356]: [27047-1] 2023-03-23 09:30:01: pid 9356: LOG:  PCP process with pid: 300 exits with status 0
Mar 23 09:30:01 PGPOOL2SERVER pgpool[9356]: [27048-1] 2023-03-23 09:30:01: pid 9356: LOG:  forked new pcp worker, pid=307 socket=8
Mar 23 09:30:01 PGPOOL2SERVER pgpool[8091]: [9001-1] 2023-03-23 09:30:01: pid 8091: LOG:  new IPC connection received
Mar 23 09:30:01 PGPOOL2SERVER pgpool[9356]: [27049-1] 2023-03-23 09:30:01: pid 9356: LOG:  PCP process with pid: 307 exit with SUCCESS.
Mar 23 09:30:01 PGPOOL2SERVER pgpool[9356]: [27050-1] 2023-03-23 09:30:01: pid 9356: LOG:  PCP process with pid: 307 exits with status 0
Mar 23 09:31:32 PGPOOL2SERVER pgpool[8090]: [27993-1] 2023-03-23 09:31:32: pid 8090: LOG:  child process with pid: 27730 exits with status 256
Mar 23 09:31:32 PGPOOL2SERVER pgpool[8090]: [27994-1] 2023-03-23 09:31:32: pid 8090: LOG:  fork a new child process with pid: 690
Mar 23 09:31:49 PGPOOL2SERVER pgpool[17874]: [27936-1] 2023-03-23 09:31:49: pid 17874: ERROR:  unable to flush data to frontend
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27995-1] 2023-03-23 09:34:17: pid 8090: LOG:  Pgpool-II parent process received sync backend signal from watchdog
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9002-1] 2023-03-23 09:34:17: pid 8091: LOG:  new IPC connection received
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27996-1] 2023-03-23 09:34:17: pid 8090: LOG:  master watchdog has performed failover
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27996-2] 2023-03-23 09:34:17: pid 8090: DETAIL:  syncing the backend states from the MASTER watchdog node
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9003-1] 2023-03-23 09:34:17: pid 8091: LOG:  new IPC connection received
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9004-1] 2023-03-23 09:34:17: pid 8091: LOG:  received the get data request from local pgpool-II on IPC interface
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9005-1] 2023-03-23 09:34:17: pid 8091: LOG:  get data request from local pgpool-II node received on IPC interface is forwarded to master watchdog node "pgpool1:5432 Linux T1VMPDLB05A"
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9005-2] 2023-03-23 09:34:17: pid 8091: DETAIL:  waiting for the reply...
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27997-1] 2023-03-23 09:34:17: pid 8090: LOG:  master watchdog node "pgpool1:5432 Linux T1VMPDLB05A" returned status for 2 backend nodes
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27998-1] 2023-03-23 09:34:17: pid 8090: LOG:  backend:0 is set to UP status
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27998-2] 2023-03-23 09:34:17: pid 8090: DETAIL:  backend:0 is UP on cluster master "pgpool1:5432 Linux T1VMPDLB05A"
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27999-1] 2023-03-23 09:34:17: pid 8090: LOG:  backend:1 is set to down status
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27999-2] 2023-03-23 09:34:17: pid 8090: DETAIL:  backend:1 is DOWN on cluster master "pgpool1:5432 Linux T1VMPDLB05A"
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [28000-1] 2023-03-23 09:34:17: pid 8090: LOG:  1 backend node(s) were detached because of backend status sync from "pgpool1:5432 Linux T1VMPDLB05A"
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [28000-2] 2023-03-23 09:34:17: pid 8090: DETAIL:  restarting the children processes
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [28001-1] 2023-03-23 09:34:17: pid 8090: LOG:  Node 0 is not down (status: 1)
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28002-1] 2023-03-23 09:34:18: pid 8090: LOG:  child process with pid: 29504 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28003-1] 2023-03-23 09:34:18: pid 8090: LOG:  fork a new child process with pid: 1438
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1438]: [28003-1] 2023-03-23 09:34:18: pid 1438: LOG:  failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1438]: [28003-2] 2023-03-23 09:34:18: pid 1438: DETAIL:  restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28004-1] 2023-03-23 09:34:18: pid 8090: LOG:  child process with pid: 1438 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28005-1] 2023-03-23 09:34:18: pid 8090: LOG:  fork a new child process with pid: 1440
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28006-1] 2023-03-23 09:34:18: pid 8090: LOG:  child process with pid: 26481 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28007-1] 2023-03-23 09:34:18: pid 8090: LOG:  fork a new child process with pid: 1441
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1441]: [28007-1] 2023-03-23 09:34:18: pid 1441: LOG:  failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1441]: [28007-2] 2023-03-23 09:34:18: pid 1441: DETAIL:  restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28008-1] 2023-03-23 09:34:18: pid 8090: LOG:  child process with pid: 1441 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28009-1] 2023-03-23 09:34:18: pid 8090: LOG:  fork a new child process with pid: 1442
Mar 23 09:34:18 PGPOOL2SERVER pgpool[17874]: [27937-1] 2023-03-23 09:34:18: pid 17874: LOG:  failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[17874]: [27937-2] 2023-03-23 09:34:18: pid 17874: DETAIL:  restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[30196]: [27986-1] 2023-03-23 09:34:18: pid 30196: LOG:  failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[30196]: [27986-2] 2023-03-23 09:34:18: pid 30196: DETAIL:  restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[30728]: [27988-1] 2023-03-23 09:34:18: pid 30728: LOG:  failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[30728]: [27988-2] 2023-03-23 09:34:18: pid 30728: DETAIL:  restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[32640]: [27992-1] 2023-03-23 09:34:18: pid 32640: LOG:  failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[32640]: [27992-2] 2023-03-23 09:34:18: pid 32640: DETAIL:  restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28010-1] 2023-03-23 09:34:18: pid 8090: LOG:  child process with pid: 30196 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28011-1] 2023-03-23 09:34:18: pid 8090: LOG:  fork a new child process with pid: 1451
Mar 23 09:34:18 PGPOOL2SERVER pgpool[28936]: [27982-1] 2023-03-23 09:34:18: pid 28936: LOG:  failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[28936]: [27982-2] 2023-03-23 09:34:18: pid 28936: DETAIL:  restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28012-1] 2023-03-23 09:34:18: pid 8090: LOG:  child process with pid: 17874 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28013-1] 2023-03-23 09:34:18: pid 8090: LOG:  fork a new child process with pid: 1453
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28014-1] 2023-03-23 09:34:18: pid 8090: LOG:  child process with pid: 30728 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28015-1] 2023-03-23 09:34:18: pid 8090: LOG:  fork a new child process with pid: 1454
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28016-1] 2023-03-23 09:34:18: pid 8090: LOG:  child process with pid: 28936 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28017-1] 2023-03-23 09:34:18: pid 8090: LOG:  fork a new child process with pid: 1456
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28018-1] 2023-03-23 09:34:18: pid 8090: LOG:  child process with pid: 32640 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28019-1] 2023-03-23 09:34:18: pid 8090: LOG:  fork a new child process with pid: 1457
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1440]: [28005-1] 2023-03-23 09:34:18: pid 1440: LOG:  RAW_MODE:0 REAL_MASTER_NODE_ID:0 pool_is_node_to_be_sent_in_current_query:1 my_backend_status:3
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1440]: [28006-1] 2023-03-23 09:34:18: pid 1440: ERROR:  unable to read message kind from backend
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1440]: [28006-2] 2023-03-23 09:34:18: pid 1440: DETAIL:  1 th backend is not valid
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28020-1] 2023-03-23 09:34:18: pid 8090: WARNING:  child process with pid: 1440 was terminated by segmentation fault
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28021-1] 2023-03-23 09:34:18: pid 8090: LOG:  fork a new child process with pid: 1458
Mar 23 09:34:19 PGPOOL2SERVER pgpool[30738]: [27990-1] 2023-03-23 09:34:19: pid 30738: LOG:  failback event detected
Mar 23 09:34:19 PGPOOL2SERVER pgpool[30738]: [27990-2] 2023-03-23 09:34:19: pid 30738: DETAIL:  restarting myself
Mar 23 09:34:19 PGPOOL2SERVER pgpool[8090]: [28022-1] 2023-03-23 09:34:19: pid 8090: LOG:  child process with pid: 30738 exits with status 256
Mar 23 09:34:19 PGPOOL2SERVER pgpool[8090]: [28023-1] 2023-03-23 09:34:19: pid 8090: LOG:  fork a new child process with pid: 1461
Mar 23 09:35:01 PGPOOL2SERVER pgpool[9356]: [27051-1] 2023-03-23 09:35:01: pid 9356: LOG:  forked new pcp worker, pid=1602 socket=8
Mar 23 09:35:01 PGPOOL2SERVER pgpool[8091]: [9006-1] 2023-03-23 09:35:01: pid 8091: LOG:  new IPC connection received
Mar 23 09:35:01 PGPOOL2SERVER pgpool[9356]: [27052-1] 2023-03-23 09:35:01: pid 9356: LOG:  PCP process with pid: 1602 exit with SUCCESS.
Mar 23 09:35:01 PGPOOL2SERVER pgpool[9356]: [27053-1] 2023-03-23 09:35:01: pid 9356: LOG:  PCP process with pid: 1602 exits with status 0
Mar 23 09:35:01 PGPOOL2SERVER pgpool[9356]: [27054-1] 2023-03-23 09:35:01: pid 9356: LOG:  forked new pcp worker, pid=1608 socket=8
Mar 23 09:35:01 PGPOOL2SERVER pgpool[8091]: [9007-1] 2023-03-23 09:35:01: pid 8091: LOG:  new IPC connection received
Mar 23 09:35:01 PGPOOL2SERVER pgpool[9356]: [27055-1] 2023-03-23 09:35:01: pid 9356: LOG:  PCP process with pid: 1608 exit with SUCCESS.
Mar 23 09:35:01 PGPOOL2SERVER pgpool[9356]: [27056-1] 2023-03-23 09:35:01: pid 9356: LOG:  PCP process with pid: 1608 exits with status 0
Mar 23 09:36:33 PGPOOL2SERVER pgpool[1457]: [28019-1] 2023-03-23 09:36:33: pid 1457: LOG:  RAW_MODE:0 REAL_MASTER_NODE_ID:0 pool_is_node_to_be_sent_in_current_query:1 my_backend_status:3
Mar 23 09:36:33 PGPOOL2SERVER pgpool[1457]: [28020-1] 2023-03-23 09:36:33: pid 1457: ERROR:  unable to read message kind from backend
Mar 23 09:36:33 PGPOOL2SERVER pgpool[1457]: [28020-2] 2023-03-23 09:36:33: pid 1457: DETAIL:  1 th backend is not valid
Mar 23 09:36:33 PGPOOL2SERVER pgpool[8090]: [28024-1] 2023-03-23 09:36:33: pid 8090: WARNING:  child process with pid: 1457 was terminated by segmentation fault
Mar 23 09:36:33 PGPOOL2SERVER pgpool[8090]: [28025-1] 2023-03-23 09:36:33: pid 8090: LOG:  fork a new child process with pid: 2041
Mar 23 09:38:12 PGPOOL2SERVER pgpool[27600]: [24088-1] 2023-03-23 09:38:12: pid 27600: LOG:  failback event detected
Mar 23 09:38:12 PGPOOL2SERVER pgpool[27600]: [24088-2] 2023-03-23 09:38:12: pid 27600: DETAIL:  restarting myself
Mar 23 09:38:12 PGPOOL2SERVER pgpool[30456]: [26068-1] 2023-03-23 09:38:12: pid 30456: LOG:  selecting backend connection
Mar 23 09:38:12 PGPOOL2SERVER pgpool[30456]: [26068-2] 2023-03-23 09:38:12: pid 30456: DETAIL:  failback event detected, discarding existing connections
Mar 23 09:38:12 PGPOOL2SERVER pgpool[24599]: [27424-1] 2023-03-23 09:38:12: pid 24599: LOG:  failback event detected
Mar 23 09:38:12 PGPOOL2SERVER pgpool[24599]: [27424-2] 2023-03-23 09:38:12: pid 24599: DETAIL:  restarting myself
Mar 23 09:38:12 PGPOOL2SERVER pgpool[8090]: [28026-1] 2023-03-23 09:38:12: pid 8090: LOG:  child process with pid: 27600 exits with status 256
Mar 23 09:38:12 PGPOOL2SERVER pgpool[8090]: [28027-1] 2023-03-23 09:38:12: pid 8090: LOG:  fork a new child process with pid: 2424
Mar 23 09:38:12 PGPOOL2SERVER pgpool[8090]: [28028-1] 2023-03-23 09:38:12: pid 8090: LOG:  child process with pid: 24599 exits with status 256
Mar 23 09:38:12 PGPOOL2SERVER pgpool[8090]: [28029-1] 2023-03-23 09:38:12: pid 8090: LOG:  fork a new child process with pid: 2425
Mar 23 09:38:12 PGPOOL2SERVER pgpool[30456]: [26069-1] 2023-03-23 09:38:12: pid 30456: LOG:  RAW_MODE:0 REAL_MASTER_NODE_ID:0 pool_is_node_to_be_sent_in_current_query:1 my_backend_status:3
Mar 23 09:38:12 PGPOOL2SERVER pgpool[30456]: [26070-1] 2023-03-23 09:38:12: pid 30456: ERROR:  unable to read message kind from backend
Mar 23 09:38:12 PGPOOL2SERVER pgpool[30456]: [26070-2] 2023-03-23 09:38:12: pid 30456: DETAIL:  1 th backend is not valid
Mar 23 09:38:12 PGPOOL2SERVER pgpool[8090]: [28030-1] 2023-03-23 09:38:12: pid 8090: WARNING:  child process with pid: 30456 was terminated by segmentation fault
Mar 23 09:38:12 PGPOOL2SERVER pgpool[8090]: [28031-1] 2023-03-23 09:38:12: pid 8090: LOG:  fork a new child process with pid: 2426
Mar 23 09:39:17 PGPOOL2SERVER pgpool[2426]: [28031-1] 2023-03-23 09:39:17: pid 2426: LOG:  RAW_MODE:0 REAL_MASTER_NODE_ID:0 pool_is_node_to_be_sent_in_current_query:1 my_backend_status:3
Mar 23 09:39:17 PGPOOL2SERVER pgpool[2426]: [28032-1] 2023-03-23 09:39:17: pid 2426: ERROR:  unable to read message kind from backend
Mar 23 09:39:17 PGPOOL2SERVER pgpool[2426]: [28032-2] 2023-03-23 09:39:17: pid 2426: DETAIL:  1 th backend is not valid
Mar 23 09:39:17 PGPOOL2SERVER pgpool[8090]: [28032-1] 2023-03-23 09:39:17: pid 8090: WARNING:  child process with pid: 2426 was terminated by segmentation fault
Mar 23 09:39:17 PGPOOL2SERVER pgpool[8090]: [28033-1] 2023-03-23 09:39:17: pid 8090: LOG:  fork a new child process with pid: 2732
Mar 23 09:39:18 PGPOOL2SERVER pgpool[8090]: [28034-1] 2023-03-23 09:39:18: pid 8090: LOG:  child process with pid: 23971 exits with status 256
Mar 23 09:39:18 PGPOOL2SERVER pgpool[8090]: [28035-1] 2023-03-23 09:39:18: pid 8090: LOG:  fork a new child process with pid: 2737
Mar 23 09:39:18 PGPOOL2SERVER pgpool[2737]: [28035-1] 2023-03-23 09:39:18: pid 2737: LOG:  failback event detected
Mar 23 09:39:18 PGPOOL2SERVER pgpool[2737]: [28035-2] 2023-03-23 09:39:18: pid 2737: DETAIL:  restarting myself
Mar 23 09:39:18 PGPOOL2SERVER pgpool[8090]: [28036-1] 2023-03-23 09:39:18: pid 8090: LOG:  child process with pid: 2737 exits with status 256
Mar 23 09:39:18 PGPOOL2SERVER pgpool[8090]: [28037-1] 2023-03-23 09:39:18: pid 8090: LOG:  fork a new child process with pid: 2738
Mar 23 09:39:18 PGPOOL2SERVER pgpool[23464]: [26878-1] 2023-03-23 09:39:18: pid 23464: LOG:  failback event detected
Mar 23 09:39:18 PGPOOL2SERVER pgpool[23464]: [26878-2] 2023-03-23 09:39:18: pid 23464: DETAIL:  restarting myself
Mar 23 09:39:18 PGPOOL2SERVER pgpool[8090]: [28038-1] 2023-03-23 09:39:18: pid 8090: LOG:  child process with pid: 23464 exits with status 256
Mar 23 09:39:18 PGPOOL2SERVER pgpool[8090]: [28039-1] 2023-03-23 09:39:18: pid 8090: LOG:  fork a new child process with pid: 2746
Mar 23 09:39:18 PGPOOL2SERVER pgpool[2738]: [28037-1] 2023-03-23 09:39:18: pid 2738: LOG:  RAW_MODE:0 REAL_MASTER_NODE_ID:0 pool_is_node_to_be_sent_in_current_query:1 my_backend_status:3
Mar 23 09:39:18 PGPOOL2SERVER pgpool[2738]: [28038-1] 2023-03-23 09:39:18: pid 2738: ERROR:  unable to read message kind from backend
Mar 23 09:39:18 PGPOOL2SERVER pgpool[2738]: [28038-2] 2023-03-23 09:39:18: pid 2738: DETAIL:  1 th backend is not valid
Mar 23 09:39:18 PGPOOL2SERVER pgpool[8090]: [28040-1] 2023-03-23 09:39:18: pid 8090: WARNING:  child process with pid: 2738 was terminated by segmentation fault
Mar 23 09:39:18 PGPOOL2SERVER pgpool[8090]: [28041-1] 2023-03-23 09:39:18: pid 8090: LOG:  fork a new child process with pid: 2747
Mar 23 09:40:01 PGPOOL2SERVER pgpool[9356]: [27057-1] 2023-03-23 09:40:01: pid 9356: LOG:  forked new pcp worker, pid=2874 socket=8
Mar 23 09:40:01 PGPOOL2SERVER pgpool[8091]: [9008-1] 2023-03-23 09:40:01: pid 8091: LOG:  new IPC connection received
Mar 23 09:40:01 PGPOOL2SERVER pgpool[9356]: [27058-1] 2023-03-23 09:40:01: pid 9356: LOG:  PCP process with pid: 2874 exit with SUCCESS.
Mar 23 09:40:01 PGPOOL2SERVER pgpool[9356]: [27059-1] 2023-03-23 09:40:01: pid 9356: LOG:  PCP process with pid: 2874 exits with status 0
Mar 23 09:40:01 PGPOOL2SERVER pgpool[9356]: [27060-1] 2023-03-23 09:40:01: pid 9356: LOG:  forked new pcp worker, pid=2880 socket=8
Mar 23 09:40:01 PGPOOL2SERVER pgpool[8091]: [9009-1] 2023-03-23 09:40:01: pid 8091: LOG:  new IPC connection received
Mar 23 09:40:01 PGPOOL2SERVER pgpool[9356]: [27061-1] 2023-03-23 09:40:01: pid 9356: LOG:  PCP process with pid: 2880 exit with SUCCESS.
Mar 23 09:40:01 PGPOOL2SERVER pgpool[9356]: [27062-1] 2023-03-23 09:40:01: pid 9356: LOG:  PCP process with pid: 2880 exits with status 0
Mar 23 09:41:32 PGPOOL2SERVER pgpool[28267]: [27980-1] 2023-03-23 09:41:32: pid 28267: LOG:  failback event detected
Mar 23 09:41:32 PGPOOL2SERVER pgpool[28267]: [27980-2] 2023-03-23 09:41:32: pid 28267: DETAIL:  restarting myself
Mar 23 09:41:32 PGPOOL2SERVER pgpool[15887]: [3732-1] 2023-03-23 09:41:32: pid 15887: LOG:  failback event detected
Mar 23 09:41:32 PGPOOL2SERVER pgpool[15887]: [3732-2] 2023-03-23 09:41:32: pid 15887: DETAIL:  restarting myself
Mar 23 09:41:32 PGPOOL2SERVER pgpool[1894]: [27066-1] 2023-03-23 09:41:32: pid 1894: LOG:  selecting backend connection
Mar 23 09:41:32 PGPOOL2SERVER pgpool[1894]: [27066-2] 2023-03-23 09:41:32: pid 1894: DETAIL:  failback event detected, discarding existing connections
Mar 23 09:41:32 PGPOOL2SERVER pgpool[8090]: [28042-1] 2023-03-23 09:41:32: pid 8090: LOG:  child process with pid: 28267 exits with status 256
Mar 23 09:41:32 PGPOOL2SERVER pgpool[8090]: [28043-1] 2023-03-23 09:41:32: pid 8090: LOG:  fork a new child process with pid: 3281
Mar 23 09:41:32 PGPOOL2SERVER pgpool[8090]: [28044-1] 2023-03-23 09:41:32: pid 8090: LOG:  child process with pid: 15887 exits with status 256
Mar 23 09:41:32 PGPOOL2SERVER pgpool[8090]: [28045-1] 2023-03-23 09:41:32: pid 8090: LOG:  fork a new child process with pid: 3282
Mar 23 09:41:32 PGPOOL2SERVER pgpool[1894]: [27067-1] 2023-03-23 09:41:32: pid 1894: LOG:  RAW_MODE:0 REAL_MASTER_NODE_ID:0 pool_is_node_to_be_sent_in_current_query:1 my_backend_status:3
Mar 23 09:41:32 PGPOOL2SERVER pgpool[1894]: [27068-1] 2023-03-23 09:41:32: pid 1894: ERROR:  unable to read message kind from backend
Mar 23 09:41:32 PGPOOL2SERVER pgpool[1894]: [27068-2] 2023-03-23 09:41:32: pid 1894: DETAIL:  1 th backend is not valid
Mar 23 09:41:32 PGPOOL2SERVER pgpool[8090]: [28046-1] 2023-03-23 09:41:32: pid 8090: WARNING:  child process with pid: 1894 was terminated by segmentation fault
Mar 23 09:41:32 PGPOOL2SERVER pgpool[8090]: [28047-1] 2023-03-23 09:41:32: pid 8090: LOG:  fork a new child process with pid: 3283
Mar 23 09:41:32 PGPOOL2SERVER pgpool[690]: [27994-1] 2023-03-23 09:41:32: pid 690: LOG:  failback event detected
Mar 23 09:41:32 PGPOOL2SERVER pgpool[690]: [27994-2] 2023-03-23 09:41:32: pid 690: DETAIL:  restarting myself
Mar 23 09:41:32 PGPOOL2SERVER pgpool[8090]: [28048-1] 2023-03-23 09:41:32: pid 8090: LOG:  child process with pid: 690 exits with status 256
Mar 23 09:41:32 PGPOOL2SERVER pgpool[8090]: [28049-1] 2023-03-23 09:41:32: pid 8090: LOG:  fork a new child process with pid: 3284
Mar 23 09:41:33 PGPOOL2SERVER pgpool[3283]: [28047-1] 2023-03-23 09:41:33: pid 3283: LOG:  RAW_MODE:0 REAL_MASTER_NODE_ID:0 pool_is_node_to_be_sent_in_current_query:1 my_backend_status:3
Mar 23 09:41:33 PGPOOL2SERVER pgpool[3283]: [28048-1] 2023-03-23 09:41:33: pid 3283: ERROR:  unable to read message kind from backend
Mar 23 09:41:33 PGPOOL2SERVER pgpool[3283]: [28048-2] 2023-03-23 09:41:33: pid 3283: DETAIL:  1 th backend is not valid
Mar 23 09:41:33 PGPOOL2SERVER pgpool[8090]: [28050-1] 2023-03-23 09:41:33: pid 8090: WARNING:  child process with pid: 3283 was terminated by segmentation fault
Mar 23 09:41:33 PGPOOL2SERVER pgpool[8090]: [28051-1] 2023-03-23 09:41:33: pid 8090: LOG:  fork a new child process with pid: 3298
Mar 23 09:42:00 PGPOOL2SERVER pgpool[16644]: [27930-1] 2023-03-23 09:42:00: pid 16644: LOG:  failback event detected
Mar 23 09:42:00 PGPOOL2SERVER pgpool[16644]: [27930-2] 2023-03-23 09:42:00: pid 16644: DETAIL:  restarting myself
Mar 23 09:42:00 PGPOOL2SERVER pgpool[8090]: [28052-1] 2023-03-23 09:42:00: pid 8090: LOG:  child process with pid: 16644 exits with status 256
Mar 23 09:42:00 PGPOOL2SERVER pgpool[8090]: [28053-1] 2023-03-23 09:42:00: pid 8090: LOG:  fork a new child process with pid: 3398
Mar 23 09:42:00 PGPOOL2SERVER pgpool[2746]: [28039-1] 2023-03-23 09:42:00: pid 2746: LOG:  RAW_MODE:0 REAL_MASTER_NODE_ID:0 pool_is_node_to_be_sent_in_current_query:1 my_backend_status:3
Mar 23 09:42:00 PGPOOL2SERVER pgpool[2746]: [28040-1] 2023-03-23 09:42:00: pid 2746: ERROR:  unable to read message kind from backend
Mar 23 09:42:00 PGPOOL2SERVER pgpool[2746]: [28040-2] 2023-03-23 09:42:00: pid 2746: DETAIL:  1 th backend is not valid
Mar 23 09:42:00 PGPOOL2SERVER pgpool[8090]: [28054-1] 2023-03-23 09:42:00: pid 8090: WARNING:  child process with pid: 2746 was terminated by segmentation fault
Mar 23 09:42:00 PGPOOL2SERVER pgpool[8090]: [28055-1] 2023-03-23 09:42:00: pid 8090: LOG:  fork a new child process with pid: 3401
PGPOOL2SERVER.txt (22,707 bytes)   

pengbo

2023-03-24 23:50

developer   ~0004310

Are you using 2 nodes?

node0: Pgpool-II (leader) PostgreSQL (standby)
node1: Pgpool-II (follower) POstgreSQ+ (primary)

It seems segmentation fault occurs. It may cause this issue.
-------------------
 was terminated by segmentation fault
-------------------

Pgpool-II 3.7.2 is very old and 3.7.x is EOL. Many bugs was fixed after 3.7.2, i recommend upgrading your pgpool version.

supakit.chavar

2023-03-27 10:51

reporter   ~0004317

before failover we has status as below in each node.

===================================
 node_id | hostname | port | status | lb_weight | role | select_cnt | load_balance_node | replication_delay
---------+----------+------+--------+-----------+---------+------------+-------------------+-------------------
 0 | db-a | 5432 | up | 0.500000 | standby | 21044342 | true | 0
 1 | db-b | 5432 | up | 0.500000 | primary | 413194070 | false | 1755349681646
(2 rows)


Refer to your advice. Could you please suggest version of Pgpool-II for PostgreSQL 9.6 ?

pengbo

2023-03-28 23:12

developer   ~0004333

If you are installing from RPM, we suggest that you upgrade to 3.7.21.
If you are installing from source code, you can use any version for PostgreSQL 9.6. I suggest the latest 4.4.x.

I checked your log again. It seems you are using raw mode.
If you are using PostgreSQL streaming replication, you need to set the following parameters in pgpool.conf:

---------------------------------------------
master_slave_mode = on
master_slave_sub_mode = 'stream'
---------------------------------------------

pengbo

2023-03-29 11:58

developer   ~0004335

I have checked your config files. The configuration are correct.

> The pgpool-ii 3.7.2 has performed failover but after check the DB it's still alive.

"The pgpool-ii 3.7.2 has performed failover" means pgpool leader <-> standby switchover?
How did you performed failover? Could you provide detailed steps?

supakit.chavar

2023-03-29 15:23

reporter   ~0004336

I did not perform failover but I said as same as the wording in PGPOOL2SERVER.txt .

and when pgpool-ii performed failover i checked log file in postgresql 9.6 db with same date/time but both DB still alive.

here is detail.

Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27995-1] 2023-03-23 09:34:17: pid 8090: LOG: Pgpool-II parent process received sync backend signal from watchdog
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9002-1] 2023-03-23 09:34:17: pid 8091: LOG: new IPC connection received
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27996-1] 2023-03-23 09:34:17: pid 8090: LOG: master watchdog has performed failover
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27996-2] 2023-03-23 09:34:17: pid 8090: DETAIL: syncing the backend states from the MASTER watchdog node
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9003-1] 2023-03-23 09:34:17: pid 8091: LOG: new IPC connection received
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9004-1] 2023-03-23 09:34:17: pid 8091: LOG: received the get data request from local pgpool-II on IPC interface
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9005-1] 2023-03-23 09:34:17: pid 8091: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to master watchdog node "pgpool1:5432 Linux T1VMPDLB05A"
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9005-2] 2023-03-23 09:34:17: pid 8091: DETAIL: waiting for the reply...
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27997-1] 2023-03-23 09:34:17: pid 8090: LOG: master watchdog node "pgpool1:5432 Linux T1VMPDLB05A" returned status for 2 backend nodes
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27998-1] 2023-03-23 09:34:17: pid 8090: LOG: backend:0 is set to UP status
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27998-2] 2023-03-23 09:34:17: pid 8090: DETAIL: backend:0 is UP on cluster master "pgpool1:5432 Linux T1VMPDLB05A"
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27999-1] 2023-03-23 09:34:17: pid 8090: LOG: backend:1 is set to down status
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27999-2] 2023-03-23 09:34:17: pid 8090: DETAIL: backend:1 is DOWN on cluster master "pgpool1:5432 Linux T1VMPDLB05A"
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [28000-1] 2023-03-23 09:34:17: pid 8090: LOG: 1 backend node(s) were detached because of backend status sync from "pgpool1:5432 Linux T1VMPDLB05A"
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [28000-2] 2023-03-23 09:34:17: pid 8090: DETAIL: restarting the children processes
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [28001-1] 2023-03-23 09:34:17: pid 8090: LOG: Node 0 is not down (status: 1)
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28002-1] 2023-03-23 09:34:18: pid 8090: LOG: child process with pid: 29504 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28003-1] 2023-03-23 09:34:18: pid 8090: LOG: fork a new child process with pid: 1438
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1438]: [28003-1] 2023-03-23 09:34:18: pid 1438: LOG: failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1438]: [28003-2] 2023-03-23 09:34:18: pid 1438: DETAIL: restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28004-1] 2023-03-23 09:34:18: pid 8090: LOG: child process with pid: 1438 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28005-1] 2023-03-23 09:34:18: pid 8090: LOG: fork a new child process with pid: 1440
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28006-1] 2023-03-23 09:34:18: pid 8090: LOG: child process with pid: 26481 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28007-1] 2023-03-23 09:34:18: pid 8090: LOG: fork a new child process with pid: 1441
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1441]: [28007-1] 2023-03-23 09:34:18: pid 1441: LOG: failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1441]: [28007-2] 2023-03-23 09:34:18: pid 1441: DETAIL: restarting myself

pengbo

2023-03-29 15:56

developer   ~0004337

Above is the log of pgpool standby node.
To find the cause of failover, could you share the log of pgpool leader node?

pengbo

2023-03-30 14:35

developer   ~0004339

I could not see any logs of failover in your log file.
I think master pgpool didn't perform failover.

> before failover we has status as below in each node.
>
> ===================================
> node_id | hostname | port | status | lb_weight | role | select_cnt | load_balance_node | replication_delay
> ---------+----------+------+--------+-----------+---------+------------+-------------------+-------------------
> 0 | db-a | 5432 | up | 0.500000 | standby | 21044342 | true | 0
> 1 | db-b | 5432 | up | 0.500000 | primary | 413194070 | false | 1755349681646
> (2 rows)

What is the status after failover you mentioned.

Also it is strange replication_delay of primary is greater than 0.

supakit.chavar

2023-03-30 19:28

reporter   ~0004342

I could not see any logs of failover in your log file.
I think master pgpool didn't perform failover. --> yes i not found any failover messages in T1VMPDLB05A_pgpool_20230323.zip but when i checked PGPOOL2SERVER.txt

i found the message related with failover as below.




Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27995-1] 2023-03-23 09:34:17: pid 8090: LOG: Pgpool-II parent process received sync backend signal from watchdog
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9002-1] 2023-03-23 09:34:17: pid 8091: LOG: new IPC connection received
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27996-1] 2023-03-23 09:34:17: pid 8090: LOG: master watchdog has performed failover
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27996-2] 2023-03-23 09:34:17: pid 8090: DETAIL: syncing the backend states from the MASTER watchdog node
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9003-1] 2023-03-23 09:34:17: pid 8091: LOG: new IPC connection received
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9004-1] 2023-03-23 09:34:17: pid 8091: LOG: received the get data request from local pgpool-II on IPC interface
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9005-1] 2023-03-23 09:34:17: pid 8091: LOG: get data request from local pgpool-II node received on IPC interface is forwarded to master watchdog node "pgpool1:5432 Linux T1VMPDLB05A"
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8091]: [9005-2] 2023-03-23 09:34:17: pid 8091: DETAIL: waiting for the reply...
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27997-1] 2023-03-23 09:34:17: pid 8090: LOG: master watchdog node "pgpool1:5432 Linux T1VMPDLB05A" returned status for 2 backend nodes
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27998-1] 2023-03-23 09:34:17: pid 8090: LOG: backend:0 is set to UP status
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27998-2] 2023-03-23 09:34:17: pid 8090: DETAIL: backend:0 is UP on cluster master "pgpool1:5432 Linux T1VMPDLB05A"
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27999-1] 2023-03-23 09:34:17: pid 8090: LOG: backend:1 is set to down status
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [27999-2] 2023-03-23 09:34:17: pid 8090: DETAIL: backend:1 is DOWN on cluster master "pgpool1:5432 Linux T1VMPDLB05A"
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [28000-1] 2023-03-23 09:34:17: pid 8090: LOG: 1 backend node(s) were detached because of backend status sync from "pgpool1:5432 Linux T1VMPDLB05A"
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [28000-2] 2023-03-23 09:34:17: pid 8090: DETAIL: restarting the children processes
Mar 23 09:34:17 PGPOOL2SERVER pgpool[8090]: [28001-1] 2023-03-23 09:34:17: pid 8090: LOG: Node 0 is not down (status: 1)
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28002-1] 2023-03-23 09:34:18: pid 8090: LOG: child process with pid: 29504 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28003-1] 2023-03-23 09:34:18: pid 8090: LOG: fork a new child process with pid: 1438
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1438]: [28003-1] 2023-03-23 09:34:18: pid 1438: LOG: failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1438]: [28003-2] 2023-03-23 09:34:18: pid 1438: DETAIL: restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28004-1] 2023-03-23 09:34:18: pid 8090: LOG: child process with pid: 1438 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28005-1] 2023-03-23 09:34:18: pid 8090: LOG: fork a new child process with pid: 1440
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28006-1] 2023-03-23 09:34:18: pid 8090: LOG: child process with pid: 26481 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28007-1] 2023-03-23 09:34:18: pid 8090: LOG: fork a new child process with pid: 1441
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1441]: [28007-1] 2023-03-23 09:34:18: pid 1441: LOG: failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1441]: [28007-2] 2023-03-23 09:34:18: pid 1441: DETAIL: restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28008-1] 2023-03-23 09:34:18: pid 8090: LOG: child process with pid: 1441 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28009-1] 2023-03-23 09:34:18: pid 8090: LOG: fork a new child process with pid: 1442
Mar 23 09:34:18 PGPOOL2SERVER pgpool[17874]: [27937-1] 2023-03-23 09:34:18: pid 17874: LOG: failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[17874]: [27937-2] 2023-03-23 09:34:18: pid 17874: DETAIL: restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[30196]: [27986-1] 2023-03-23 09:34:18: pid 30196: LOG: failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[30196]: [27986-2] 2023-03-23 09:34:18: pid 30196: DETAIL: restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[30728]: [27988-1] 2023-03-23 09:34:18: pid 30728: LOG: failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[30728]: [27988-2] 2023-03-23 09:34:18: pid 30728: DETAIL: restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[32640]: [27992-1] 2023-03-23 09:34:18: pid 32640: LOG: failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[32640]: [27992-2] 2023-03-23 09:34:18: pid 32640: DETAIL: restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28010-1] 2023-03-23 09:34:18: pid 8090: LOG: child process with pid: 30196 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28011-1] 2023-03-23 09:34:18: pid 8090: LOG: fork a new child process with pid: 1451
Mar 23 09:34:18 PGPOOL2SERVER pgpool[28936]: [27982-1] 2023-03-23 09:34:18: pid 28936: LOG: failback event detected
Mar 23 09:34:18 PGPOOL2SERVER pgpool[28936]: [27982-2] 2023-03-23 09:34:18: pid 28936: DETAIL: restarting myself
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28012-1] 2023-03-23 09:34:18: pid 8090: LOG: child process with pid: 17874 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28013-1] 2023-03-23 09:34:18: pid 8090: LOG: fork a new child process with pid: 1453
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28014-1] 2023-03-23 09:34:18: pid 8090: LOG: child process with pid: 30728 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28015-1] 2023-03-23 09:34:18: pid 8090: LOG: fork a new child process with pid: 1454
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28016-1] 2023-03-23 09:34:18: pid 8090: LOG: child process with pid: 28936 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28017-1] 2023-03-23 09:34:18: pid 8090: LOG: fork a new child process with pid: 1456
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28018-1] 2023-03-23 09:34:18: pid 8090: LOG: child process with pid: 32640 exits with status 256
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28019-1] 2023-03-23 09:34:18: pid 8090: LOG: fork a new child process with pid: 1457
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1440]: [28005-1] 2023-03-23 09:34:18: pid 1440: LOG: RAW_MODE:0 REAL_MASTER_NODE_ID:0 pool_is_node_to_be_sent_in_current_query:1 my_backend_status:3
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1440]: [28006-1] 2023-03-23 09:34:18: pid 1440: ERROR: unable to read message kind from backend
Mar 23 09:34:18 PGPOOL2SERVER pgpool[1440]: [28006-2] 2023-03-23 09:34:18: pid 1440: DETAIL: 1 th backend is not valid
Mar 23 09:34:18 PGPOOL2SERVER pgpool[8090]: [28020-1] 2023-03-23 09:34:18: pid 8090: WARNING: child process with pid: 1440 was terminated by segmentation fault


unfortunately after Mar 23 09:34:18 i did not capture screen of "pcp_node_info" command result. so i can't provide this info to you. sorry for this.

Based on our pgpool-ii version 3.7.2 is quite old. and installed with RPM. I will apply 3.7.21. any progress i will inform you.

Issue History

Date Modified Username Field Change
2023-03-24 18:24 supakit.chavar New Issue
2023-03-24 18:24 supakit.chavar File Added: PGPOOL2SERVER.txt
2023-03-24 23:50 pengbo Note Added: 0004310
2023-03-24 23:50 pengbo Assigned To => pengbo
2023-03-24 23:50 pengbo Status new => feedback
2023-03-27 10:51 supakit.chavar Note Added: 0004317
2023-03-27 10:51 supakit.chavar Status feedback => assigned
2023-03-28 23:12 pengbo Note Added: 0004333
2023-03-28 23:12 pengbo Status assigned => feedback
2023-03-29 10:26 supakit.chavar Status feedback => assigned
2023-03-29 11:58 pengbo Note Added: 0004335
2023-03-29 15:23 supakit.chavar Note Added: 0004336
2023-03-29 15:56 pengbo Note Added: 0004337
2023-03-30 14:35 pengbo Note Added: 0004339
2023-03-30 19:28 supakit.chavar Note Added: 0004342