[pgpool-general: 7001] Re: failed to acquire the delegate IP address

[Wolf Schwurack]

I think I found the problem. The network guys changed database traffic on the network. So my setting for arping_cmd was using the wrong IP now.

From: "pgpool-general-bounces at pgpool.net" <pgpool-general-bounces at pgpool.net> on behalf of Wolfgang Schwurack <wolf at uen.org>
Date: Tuesday, April 21, 2020 at 9:33 AM
To: "pgpool-general at pgpool.net" <pgpool-general at pgpool.net>
Subject: [pgpool-general: 6998] failed to acquire the delegate IP address

I have been getting this error message a few months now on my production environment and have not been able to find out why. Even though I get the failed message when I check ifconfig the delegate IP is showing.

I have been comparing my dev setup to production but can find the any differences.

Do you have any idea on why this is happening or what I need to look for?

This is only happening on production, my other environments – dev and test show in the log file “successfully acquire the delegate IP:.”


2020-04-19 07:44:40: pid 11714: LOG:  failed to acquire the delegate IP address

2020-04-19 07:44:40: pid 11714: DETAIL:  'if_up_cmd' failed

2020-04-19 07:44:40: pid 11714: WARNING:  watchdog escalation failed to acquire delegate IP

I x out the IP addresses


eth0:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet XX.XX.XX.XXX  netmask 255.255.255.0  broadcast xx.xx.xx.xxx

        ether 00:50:56:b3:de:b2  txqueuelen 1000  (Ethernet)

Wolfgang Schwurack
Database/System Administrator
Utah Education Network
801-587-9444
wolf at uen.org<mailto:wolf at uen.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20200421/fb0f5a59/attachment.htm>