[pgpool-general: 9325] pgpool - FATAL: unable to read data from DB	node 0
    Mukesh Tanuku 
    mukesh.postgres at gmail.com
       
    Wed Jan 29 19:52:08 JST 2025
    
    
  
Hello Everyone,
I am seeing these messages in pgpool log
2025-01-29 06:52:46.705: sr_check_worker pid 404220: FATAL:  unable to read
data from DB node 0
2025-01-29 06:52:46.705: sr_check_worker pid 404220: DETAIL:  EOF
encountered with backend
2025-01-29 06:52:46.705: main pid 3598: LOG:  reaper handler
2025-01-29 06:52:46.706: main pid 3598: LOG:  reaper handler: exiting
normally
2025-01-29 06:52:46.706: sr_check_worker pid 404222: LOG:  process started
2025-01-29 06:52:46.709: sr_check_worker pid 404222: FATAL:  unable to read
data from DB node 0
2025-01-29 06:52:46.709: sr_check_worker pid 404222: DETAIL:  EOF
encountered with backend
2025-01-29 06:52:46.709: main pid 3598: LOG:  reaper handler
2025-01-29 06:52:46.709: main pid 3598: LOG:  reaper handler: exiting
normally
2025-01-29 06:52:46.709: sr_check_worker pid 404225: LOG:  process started
2025-01-29 06:52:46.712: sr_check_worker pid 404225: FATAL:  unable to read
data from DB node 0
2025-01-29 06:52:46.712: sr_check_worker pid 404225: DETAIL:  EOF
encountered with backend
what exactly this error means?
in pgpool.conf we set this below,
*sr_check_period = 10sr_check_user = 'monitor'*
at the same time im seeing this in postgresql log file :
2025-01-29 06:52:43.987 UTC [404104] FATAL:  remaining connection slots are
reserved for non-replication superuser connections
2025-01-29 06:52:46.557 UTC [404108] FATAL:  remaining connection slots are
reserved for non-replication superuser connections
2025-01-29 06:52:46.562 UTC [404110] FATAL:  remaining connection slots are
reserved for non-replication superuser connections
2025-01-29 06:52:46.566 UTC [404112] FATAL:  remaining connection slots are
reserved for non-replication superuser connections
2025-01-29 06:52:46.569 UTC [404114] FATAL:  remaining connection slots are
reserved for non-replication superuser connections
We haven't set any idle_session_timeout
or idle_in_transaction_session_timeout parameters in postgresql.conf file.
Can someone help me understanding on this issue.
Regards
Mukesh Tanuku
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20250129/0bd88a85/attachment.htm>
    
    
More information about the pgpool-general
mailing list