[pgpool-general: 9132] Pgpool delegate IP is not reachable from the remote host

Mukesh Tanuku mukesh.postgres at gmail.com
Wed Jun 19 11:50:59 JST 2024


Hello everyone.

We have a pgpool & postgres setup made as per the given example
<https://www.pgpool.net/docs/latest/en/html/example-cluster.html>

We haven't configured the *if_up_cmd, if_down_cmd & **arping_cmd* in
pgpool.conf
(we commented it out on purpose). We enabled the *delegate_ip* and assigned
a unused IP.

While we bringing up the pgpool the log shows VIP is successfully UP via
if_up_cmd, how is this happening? any default way is considering the
if_up_cmd to bring the VIP?



*2024-06-18 08:27:02.735: watchdog_utility pid 102493: LOG:  successfully
acquired the delegate IP:"10.127.1.20"2024-06-18 08:27:02.735:
watchdog_utility pid 102493: DETAIL:  'if_up_cmd' returned with
success2024-06-18 08:27:02.735: watchdog pid 102378: LOG:  watchdog
escalation process with pid: 102493 exit with SUCCESS.*

NOTE: We run into some situation so that we disabled the if_* commands in
the configuration and started pgpool, but VIP is getting acquired by the
leader pgpool node even the if_* commands are not used in pgpool.conf file.

Can anyone explain how the VIP works in pgpool watchdog

Thank you
Regards
Mukesh Tanuku
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20240619/cbd7fcfb/attachment.htm>


More information about the pgpool-general mailing list