Hello, On 8 May 2018 02:32:01 CEST, Bill Waggoner <[email protected]> wrote: >Anyway, when the system boots haproxy fails to start. Unfortunately I >forgot to save the systemctl status message but the impression I get is >that it's starting too soon.
You can find all past logs of your service using `journalctl -u haproxy.service`. If journal persistence is off you'll not be able to look at logs sent before the last boot. -- Sent from my mobile. Please excuse my brevity.
