[pgpool-general: 8040] Re: Problems with delegate_ip
imbacen at gmail.com
Thu Mar 3 21:10:00 JST 2022
IP assignment works fine.
Looks like the problem was that the IP I used was already assigned to a
different server which I did not know about.
While debugging, I also stumbled upon a linux setting
net.ipv4.ip_nonlocal_bind, this is used by tools like keepalived to
allow binding to IPs not yet assigned to interface.
But I think pgpool does not need it since it sets the IP before binding.
Finally, if you use DHCP, the selected IP must be excluded from the pool
or you need collision detection.
Best regards, cen
On 22. 02. 22 01:57, Bo Peng wrote:
> On Mon, 21 Feb 2022 11:53:34 +0100
> cen <imbacen at gmail.com> wrote:
>> Hi, I have a weird problem with delegate IP
>> I have two ubuntu 20.04 instances, 10.10.20.1/16 and 10.10.20.2/16.
>> I set the delegate IP to 10.10.30.211/24. After this, when master node
>> acquires the delegate IP, all dns resolution on master stops working.
>> DNS is on 10.10.30.10
>> I think it is because the DNS IP falls into the delegate IP range? I
>> tried to narrow the delegate IP range to /28 so it does not overlap with DNS
>> but then I started having weird problems with "connection refused"
>> (pgpool can be pinged via delegate IP but port is supposedly not
>> listening, even though if I check on master node it IS listening on
>> 0.0.0.0/0). Doing arping from client to master node makes the connection
>> work temporarily.
>> Could someone shed some light on how to set the delegate IP and netmask
> If you manually execute the commands specified in if_up_cmd and arping_cmd,
> can you set the delegate IP properly?
> You can specify any command in these parameters.
>> pgpool-general mailing list
>> pgpool-general at pgpool.net
More information about the pgpool-general