[Pkg-haproxy-maintainers] Bug#726323: Bug#726323: haproxy doesn't start on boot due to missing IPv6 address on interface

Vincent Bernat bernat at debian.org
Mon Oct 14 17:54:21 UTC 2013

 ❦ 14 octobre 2013 16:07 CEST, Philipp Kolmann <philipp at kolmann.at> :

> * haproxy logs to a socket, rsyslogd provides. rsyslogd isn't running, when
>   haproxy is started per default. I needed to add $syslogto the Required-Start
>   section of the init.d file.

OK, we should add it.

> * haproxy doesn't start due to IPv6 host address not set when haproxy is starting.
>   I have IPv6 running in production and when haproxy tries to start, it needs
>   the host IPv6 address to configure the stick-table. This fails, and haproxy
>   fails to start.
>   my fast-solution is now to add a "sleep 10" to the top of the init.d file,
>   but I think a more proper solution would be better.
> Also I have changed to init.d file to source a second config file, where I have
> the config which both nodes share, so I can easily copy one file.
> If you need the config of the global file, please tell me.

Well, there is little we can do. I suppose the address is setup in
network/interfaces but not available until it passes the DAD check. With
IPv4, you could circumvent the problem by setting
net.ipv4.ip_nonlocal_bind but there is no such setting for IPv6 and
kernel maintainers do not want to have such a setting.
panic ("No CPUs found.  System halted.\n");
        2.4.3 linux/arch/parisc/kernel/setup.c
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-haproxy-maintainers/attachments/20131014/6bf8be55/attachment.sig>

More information about the Pkg-haproxy-maintainers mailing list