On 22/11/2016 10:09 πμ, Jürgen Haas wrote: >> 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?
I don't know, but I think it is better to find out. But, it could be unrelated to the problem. > 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? > 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. Am I right? Cheers, Pavlos
signature.asc
Description: OpenPGP digital signature
