Pgpool delegate IP is not reachable from the remote host

From: Mukesh Tanuku <mukesh(dot)postgres(at)gmail(dot)com>
To: pgpool-general(at)pgpool(dot)net, pgsql-general(at)lists(dot)postgresql(dot)org, "vijay(dot)postgres(at)gmail(dot)com" <vijay(dot)postgres(at)gmail(dot)com>, bharat(dot)hegde(dot)k(at)maersk(dot)com
Subject: Pgpool delegate IP is not reachable from the remote host
Date: 2024-06-19 02:50:59
Message-ID: CAJzgB-F0ej-1cD0whoGZohzd8Fdf=+OWuyEkDM1U+N5gst4Afg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bo Peng 2024-06-19 04:42:40 Re: [pgpool-general: 9132] Pgpool delegate IP is not reachable from the remote host
Previous Message Peter J. Holzer 2024-06-18 20:57:28 Re: Restore of a reference database kills the auto analyze processing.