[pgpool-general: 3323] Re: Watchdog - ifconfig up failed
c.affolter at stepping-stone.ch
Mon Dec 1 18:11:44 JST 2014
On 27.11.2014 17:38, Jérôme Schell wrote:
> Hello all,
> I am facing a strange problem with PGPool 3.3.4 in a 2 nodes cluster
> setup using the watchdog feature.
> It seems that when switching to master status the "ifconfig up" command
> always fails (exit status 127). When initially starting, the same
> command succeeds.
> I have tried several configurations:
> * Using "sudo" in the command with pgpool running as postgres user
> (running the command from the command line is ok)
> * Using direct command with pgpool running as root
> Everythime I stop the master Pgpool I get this log on the slave that
> takes over the delegate IP:
> Nov 27 16:13:34 db02 pgpool: wd_escalation: escalating to master
> Nov 27 16:13:34 db02 pgpool: exec_ifconfig: 'sudo /bin/ip addr
> add xxx.xxx.xxx.xxx/24 dev bond0' failed. exit status: 127
> Nov 27 16:13:34 db02 pgpool: wd_IP_up: ifconfig up failed
> Nov 27 16:13:34 db02 pgpool: wd_declare: send the packet to
> declare the new master
> Nov 27 16:13:34 db02 pgpool: wd_escalation: escalated to master
> pgpool with some errors
> Nov 27 16:13:34 db02 pgpool: exec_ping: succeed to ping
> The strange thing is that the IP is well assigned to the interface but
> the arping command is not run leaving the arp table of other hosts in
> bad state.
I'm facing the exact same issue with pgpool-II 3.4.0. Also using "sudo
/bin/ip ..." as the if_up_cmd/if_down_cmd command.
More information about the pgpool-general