aproxy+h...@formilux.org" <haproxy@formilux.org>
> > Envoyé: Mardi 14 Février 2017 10:18:30
> > Objet: Re: ACL randomly failing
> >
> > On Tue, Feb 14, 2017 at 10:04:30AM +0100, Mathieu Poussin wrote:
> > > Ok I just found why, ports can be shared because
> De: "Willy Tarreau" <w...@1wt.eu>
> À: "Mathieu Poussin" <math...@lodgify.com>
> Cc: "Daniel Schneller" <daniel.schnel...@centerdevice.com>,
> "haproxy+h...@formilux.org" <haproxy@formilux.org>
> Envoyé: Mardi 14 Fé
On Tue, Feb 14, 2017 at 10:04:30AM +0100, Mathieu Poussin wrote:
> Ok I just found why, ports can be shared because of SO_REUSEADDR... What's a
> surprise :)
SO_REUSEPORT to be precise :-)
> Is there a way to force disable the use of this flag by HAProxy ?
We merged a patch for this recently,
Ok I just found why, ports can be shared because of SO_REUSEADDR… What’s a
surprise :)
Is there a way to force disable the use of this flag by HAProxy ?
> On 14 Feb 2017, at 09:58, Mathieu Poussin wrote:
>
> Hello Daniel.
>
> I just checked that and you are right.
> I
Hello Daniel.
I just checked that and you are right.
I had both the legacy haproxy 1.4 (/usr/sbin/haproxy) and the compiled 1.7
(/usr/local/sbin/haproxy) running for an unknown reason…
The most surprising thing is that they were both listening to the same ports…
Aren’t socket binding supposed
Mathieu,
I have often been fooled like this by multiple haproxy instances running at the
same time.
Whenever I had restarted them with config changes there were sometimes open
client connections keeping instances with older configs alive. Those would
respond to a random set of the
Hello.
I have setup HAProxy on our environment and I can see a very strange behaviour.
I have the following configuration (Just a part of it) :
global
chroot /var/lib/haproxy
user haproxy
group haproxy
daemon
tune.maxrewrite 4096
###
7 matches
Mail list logo