While the proxy processes apparently did stop, the pid 2215 process did not.
Running 'systemctl restart haproxy.service' afterwards killed both processes, and started a single fresh one with a new pid, which I think is correct behaviour. So this does indeed seem likely to be down to using 'service' here.
Never mind, here it is on Xenial:
https:/ /pastebin. ubuntu. com/p/3zbQdnTBt F/
There's nothing relevant to haproxy in syslog, but here's the relevant lines from /var/log/ haproxy. log:
https:/ /pastebin. ubuntu. com/p/HJT3WRc8D w/
While the proxy processes apparently did stop, the pid 2215 process did not.
Running 'systemctl restart haproxy.service' afterwards killed both processes, and started a single fresh one with a new pid, which I think is correct behaviour. So this does indeed seem likely to be down to using 'service' here.