>>> Are you sure the IPs configured in frontends are available during boot? >> >> Well, that's exactly what I don't know. Why shouldn't they? > > I don't know, but I think it is better to find out. But, it could be > unrelated to the problem.
Here is what is in the bootlog before the HaProxy service gets started. It's the same timestamp but I guess as it is there prior to starting HaProxy means that the networks was available when HaProxy started: Nov 21 23:35:40 ggate1 dhclient[2377]: DHCPREQUEST of 1.2.3.4 on eth0 to 255.255.255.255 port 67 (xid=0x60522c35) Nov 21 23:35:40 ggate1 ifup[1434]: DHCPREQUEST of 1.2.3.4 on eth0 to 255.255.255.255 port 67 (xid=0x60522c35) Nov 21 23:35:40 ggate1 ifup[1434]: DHCPOFFER of 1.2.3.4 from 109.239.48.251 Nov 21 23:35:40 ggate1 ifup[1434]: DHCPACK of 1.2.3.4 from 109.239.48.251 Nov 21 23:35:40 ggate1 dhclient[2377]: DHCPOFFER of 1.2.3.4 from 109.239.48.251 Nov 21 23:35:40 ggate1 dhclient[2377]: DHCPACK of 1.2.3.4 from 109.239.48.251 Nov 21 23:35:40 ggate1 dhclient[2377]: bound to 1.2.3.4 -- renewal in 17537 seconds. Nov 21 23:35:40 ggate1 ifup[1434]: bound to 1.2.3.4 -- renewal in 17537 seconds. Nov 21 23:35:40 ggate1 sh[2301]: ifup: interface eth0 already configured Nov 21 23:35:40 ggate1 systemd[1]: Started Raise network interfaces. The IP address (here 1.2.3.4 replaced it) is the one that is used for the bind in haproxy.cfg > If you use SysVinit then you don't need the systemd-wrapper. > If I understood you correctly you have the following setup > systemd->SysVinit init script->systemd-wrapper. We do have the haproxy start script in /etc/init.d and for the runlevels 2, 3, 4 and 5 a link is contained in their respective /etc/rc#.d/ directory. Jürgen
