There's a sysctl for that, net.ipv4.ip_nonlocal_bind. On Thu, Aug 27, 2015, 5:49 PM Shawn Heisey <hapr...@elyograg.org> wrote:
> On 8/24/2015 12:06 PM, Dennis Jacobfeuerborn wrote: > > There is no need to run a full Pacemaker stack. Just run HAProxy on both > > nodes and manage the virtual ips using keepalived. > > All of my bind statements are applied to specific ip addresses, not > 0.0.0.0. > > If you try to start haproxy on a machine that is missing the address(es) > that you are binding to (which describes the standby server in a > redundant pair), it won't start. Public IP addresses redacted in the > following partial log: > > root@lb4:~# service haproxy start ; service haproxy stop > * Starting haproxy haproxy > [ALERT] 238/183842 (32404) : Starting frontend fe-spark-80: cannot bind > socket [RE.DAC.TED.78:80] > [ALERT] 238/183842 (32404) : Starting frontend fe-spark-443: cannot bind > socket [RE.DAC.TED.78:443] > > This is why I run redundant haproxy with a full pacemaker stack that > starts haproxy and the gratuitous arps *after* the address resources > have started. > > Thanks, > Shawn > > >
