Re: SV: SV: Config will not start on 2.6.1 on Ubuntu 22.04

2022-07-09 Thread Willy Tarreau
On Sat, Jul 09, 2022 at 01:46:03PM +0200, Vincent Bernat wrote: > On 7/9/22 10:55, Willy Tarreau wrote: > > On Sat, Jul 09, 2022 at 12:03:02AM +0200, Vincent Bernat wrote: > > > The error when not running as root is expected. However, the fact it does > > > not work on boot, then works after is

Re: SV: SV: Config will not start on 2.6.1 on Ubuntu 22.04

2022-07-09 Thread Vincent Bernat
On 7/9/22 10:55, Willy Tarreau wrote: On Sat, Jul 09, 2022 at 12:03:02AM +0200, Vincent Bernat wrote: The error when not running as root is expected. However, the fact it does not work on boot, then works after is odd. Can you share a minimal configuration file which exhibits this issue?

Re: SV: SV: Config will not start on 2.6.1 on Ubuntu 22.04

2022-07-09 Thread Willy Tarreau
On Sat, Jul 09, 2022 at 12:03:02AM +0200, Vincent Bernat wrote: > The error when not running as root is expected. However, the fact it does > not work on boot, then works after is odd. Can you share a minimal > configuration file which exhibits this issue? That's very strange, it sounds as if the

Re: SV: SV: Config will not start on 2.6.1 on Ubuntu 22.04

2022-07-08 Thread Vincent Bernat
The error when not running as root is expected. However, the fact it does not work on boot, then works after is odd. Can you share a minimal configuration file which exhibits this issue? On 7/8/22 23:43, Henning Svane wrote: Hi Vincent And found out if I started the service manual with sudo

Re: SV: Config will not start on 2.6.1 on Ubuntu 22.04

2022-07-06 Thread Vincent Bernat
Running apparmor is not a problem per-se. It may be only if there is a profile preventing HAProxy to execute something. Try journalctl -k --grep haproxy to double-check. As I am unable to reproduce on a freshly installed Ubuntu VM, can you try to reproduce on a VM on your side? On 7/6/22