On Tue, Nov 21, 2017 at 11:12:45AM +0100, Lukas Tribus wrote: > Hello, > > 2017-11-21 8:39 GMT+01:00 William Lallemand <wlallem...@haproxy.com>: > > That's not it, the hold-off timer is only a consequence of this > problem. I believe the notification does not work in my case, which is > why for systemd haproxy did not start correctly which is why systemd > continues to restart haproxy. > I found the root of the issue: the "daemon" keyword in the global > configuration section. We need to remove "daemon" from the > configuration for systemd to mode work correctly in notify mode. > > We can override the "daemon" keyword in the configuration by passing > -db to haproxy. Adding it to the unit file fixes the issue even if > they keyword is in the configuration (so we pass "-Ws -db" ). > > "-Ws -db" along with a note in the documentation that "daemon" may be > ignored in systemd mode seems like a good compromise here? I will send > an RFC patch shortly. >
You should never use systemd with the daemon mode, either in notify or default mode, it's not the recommended setup. I don't like the idea of the "daemon" keyword being ignored, however, we could exit with an error when we try to start with -Ws + -D or daemon. -- William Lallemand
