I feel I should tap the screen and say "Is this on?" I just signed up for the list but the haproxy+help address didn't supply much info at all. SO I'll try this ...
I just moved my running haproxy instance over to a new Intel NUC box running Ubuntu Server 18.04. SO much faster that the Raspberry Pi that I was running on before. It's obviously not a "critical" system but it's important to me ... 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. What I think I narrowed it down to is in the systemd haproxy.service config it says After=network.service rsyslog.service I think that should be: Requires=network-online.target After=network-online.target rsyslog.service I've made that change but haven't tested it yet. Seems like a logical change to me. I'd appreciate any comments ... Bill Waggoner -- Bill Waggoner [email protected] {Even Old Dogs can learn new tricks!}
