> Yes, your assumption is correct. I've now added "localpeer" global
> option to the config to make this more robust/more independent from
the OS.
Glad to know you were able to work around it.
Thanks for confirming
Regards,
Aurelien
Am Mi., 1. März 2023 um 11:49 Uhr schrieb Aurelien DARRAGON <
adarra...@haproxy.com>:
> > In the HAProxy configuration i'm using the FQDN name, and it seems
> > HAProxy is just using the short hostname.
> This seems to be true indeed, "localpeer" default value is retrieved
> thanks to gethostname(
> In the HAProxy configuration i'm using the FQDN name, and it seems
> HAProxy is just using the short hostname.
This seems to be true indeed, "localpeer" default value is retrieved
thanks to gethostname() in haproxy
However, since no obvious changes around "localpeer" handling occurred
between 2.
Am Mi., 1. März 2023 um 10:49 Uhr schrieb Lukas Tribus :
> On Wed, 1 Mar 2023 at 10:09, bjun...@gmail.com wrote:
> >
> > Hi,
> >
> > i've upgraded from HAProxy 2.4.15 (OS: Ubuntu 18.04) to 2.4.22 (OS:
> Ubuntu 22.04). Now the stick-table synchronization between peers isn't
> working anymore.
> >
On Wed, 1 Mar 2023 at 10:09, bjun...@gmail.com wrote:
>
> Hi,
>
> i've upgraded from HAProxy 2.4.15 (OS: Ubuntu 18.04) to 2.4.22 (OS: Ubuntu
> 22.04). Now the stick-table synchronization between peers isn't working
> anymore.
>
> The peers listener is completely not existing (lsof output).
>
> H
Hi,
i've upgraded from HAProxy 2.4.15 (OS: Ubuntu 18.04) to 2.4.22 (OS: Ubuntu
22.04). Now the stick-table synchronization between peers isn't working
anymore.
The peers listener is completely not existing (lsof output).
HAProxy config:
peers LB
peer s017.domain.local 192.168.120.207:1234
6 matches
Mail list logo
