Hi Lukas, On Tue, Nov 21, 2017 at 01:12:10AM +0100, Lukas Tribus wrote: > 2017-11-20 15:58 GMT+01:00 Tim Düsterhus <[email protected]>: > > From: Tim Duesterhus <[email protected]> > > > > This patch adds support for `Type=notify` to the systemd unit. > > > > Supporting `Type=notify` improves both starting as well as reloading > > of the unit, because systemd will be let known when the action completed. > > I can't start haproxy anymore this way. > > I compiled with USE_SYSTEMD, updated the unit file with both changes, > and reloaded systemd (systemctl daemon-reload), but systemd aborts the > start for some reason: > > > Nov 21 00:46:20 www systemd[1]: Starting HAProxy Load Balancer... > Nov 21 00:46:20 www haproxy[814]: [WARNING] 324/004620 (814) : parsing > [/etc/haproxy/haproxy.cfg:118] : a 'http-request' rule placed after a > 'reqxxx' rule will still be processed before. > [...] > Nov 21 00:46:20 www haproxy[814]: Proxy port443 started. > Nov 21 00:46:20 www haproxy[814]: Proxy port443 started. > [...] > Nov 21 00:46:20 www systemd[1]: Started HAProxy Load Balancer. > Nov 21 00:46:20 www systemd[1]: haproxy.service: Service hold-off time > over, scheduling restart. > Nov 21 00:46:20 www systemd[1]: Stopped HAProxy Load Balancer. > Nov 21 00:46:20 www systemd[1]: haproxy.service: Start request > repeated too quickly. > Nov 21 00:46:20 www systemd[1]: Failed to start HAProxy Load Balancer. > > > Reverting back to "Type=forking" (while still using -Ws and > USE_SYSTEMD=1) works for me. This is ubuntu xenial (16.04) with > systemd 229. No multiprocess mode, no threading mode used. My > configuration does produce its fair share of config warnings though, > but that should not matter. Any troubleshooting advice for me here?
I really don't like this. My fears with becoming more systemd-friendly was that we'd make users helpless when something decides not to work just to annoy them, and this reports seems to confirm this feeling :-/ Tim, have you seen this message about a "hold-off timer over" being displayed at the same second as the startup message ? Isn't there a timeout setting or something like this to place in the config file ? And is there a way to disable it so that people with huge configs are still allowed to load them ? Regards, willy
