[pgpool-general: 6052] "health check timer expired" on local machine

Bud Curly psyckow.prod at gmail.com
Fri Apr 27 04:23:52 JST 2018

Hi and thanks for your work.

I use pgpool2 3.7.2 (latest git) with 2 backend as master-slave mode with
native stream replication.

I think I have an issue concerning the health check process.

Since two days now I had two "health check timer expired" that appears
yersterday around 9 am and today around 8 pm.

The weird thing is... Pgpool and the backend in question are on the same
machine. This backend is the master. Here is the log :

2018-04-26 20:59:29: pid 2153:LOG:  failed to connect to PostgreSQL server
on "x.x.x.x:xxx" using INET socket
2018-04-26 20:59:29: pid 2153:DETAIL:  health check timer expired
2018-04-26 20:59:29: pid 2153:ERROR:  failed to make persistent db
2018-04-26 20:59:29: pid 2153:DETAIL:  connection to host:" x.x.x.x:xxx"
2018-04-26 20:59:29: pid 2153:LOG:  health check failed on node 0
2018-04-26 20:59:29: pid 2153:LOG:  received degenerate backend request for
node_id: 0 from pid [2153]
2018-04-26 20:59:29: pid 2104:LOG:  Pgpool-II parent process has received
failover request
2018-04-26 20:59:29: pid 2104:LOG:  starting degeneration. shutdown host
2018-04-26 20:59:29: pid 2104:LOG:  Restart all children

Despite the fact that these are on the same machine, I use public IP for
the backend0 and not, because of failover process that required
this ip.

Do you think this could be a problem from network conditions on the server
itself or an actual issue ?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20180426/160d0234/attachment.html>

More information about the pgpool-general mailing list