> What do you mean by 'not operating at all'? It doesn't respond to requests.
> 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? It's a shared hosting environment like with the other HaProxy hosts as well, just that this one is running on Ubuntu 16 where the other run on Ubuntu 14. > Can you share your config/version/systemd settings for haproxy? This has happened last night with HaProxy 1.6.9 but I had seen that with a couple of earlier versions on that host too. The config of HaProxy is nothing special and again equal to the other hosts. For legacy reasons we are starting the process with initd like we did with the other OS versiopns for years before. Maybe we should switch to systemd here? COuld that cause something like this? > I haven't seen the above. Under which user do you run haproxy? It's the use haproxy which isn't causing any issue after restarting the process at all. Thanks Jürgen
