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

Bud Curly psyckow.prod at gmail.com
Fri Apr 27 17:44:03 JST 2018

 Thanks for your support :)

> Still I don't understand. Pgpool-II and PostgreSQL master are on thesame
machine, that means you could set like "backend_hostname0 = "".

Because I need the public address for pgpool_recovery() method to permit
online recovery from remote nodes. And pgPool like health_check
process use backend_hostname0
to do so.

The setting health_check_hostname0 doesn't exist but trough, this is not a

So according to the log, is the timeout error triggered by this
"health_check_timeout = 6" or this "connect_timeout = 10000" ?

I downed timeout to 2 seconds each and monitoring net paquets to find some
details... Keep you in touch

2018-04-27 3:15 GMT+02:00 Tatsuo Ishii <ishii at sraoss.co.jp>:

> > Pgpool-II health check process uses non-blocking socket for connecting
> > to PostgreSQL. After issuing connect system call it waits for its
> > completion using select system call with timeout: connect_timeout in
> > pgpool.conf (in your case 10 seconds). On the other hand health_check
> > timeout is 6 seconds. So after 6 seconds, an alarm interrupted the
> > select system call and it returned with errno == EINTR, then the log
> > emitted. Not sure why the connect system call did not respond for 6
> > seconds.
> >
> > That's all what I know from the log.
> If you want to make research on this, packet dump is required.
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20180427/365b182c/attachment-0001.html>

More information about the pgpool-general mailing list