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
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?
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
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
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
On 7/6/22 00:37, Henning Svane wrote:
I get under load of haproxy the following problems for all frontends
What do you mean by "under load"?
Here are two of the errors
for frontend FrontEnd_Xmail_L7_IPv4: cannot bind socket (Permission
denied) for IPv4 number and port
and
for frontend
6 matches
Mail list logo
