ption
http-use-htx" in the global section the random 502's disappeared.
As we didn't have this option in 1.6 i guess we won't miss out much, but i
still don't understand why this goes wrong.
thank you for your swift response!
Yves
On Mon, Apr 27, 2020 at 2:10 PM Baptiste wrote:
> Hi,
&
Hi,
first, you need to set a global maxconn to 3000, otherwise it may be
limited by your system. In any case, the frontend maxconn will never be
reachable with your current config.
do you know if that happens on keep alive requests or if this happens on
the first request of the connection? Do you
Hi List,
we've recently upgraded our haproxy from 1.6 to 2.0.13 (and by now to
2.0.14).
After the upgrade our apache in front of the haproxy instance randomly
reports 502's. The requests that result in the 502 are not logged in the
haproxy log. It happens random and sporadically on requests
On 2019-07-22 13:05, Sander Klein wrote:
On 2019-07-22 10:59, Christopher Faulet wrote:
Le 20/07/2019 à 19:50, Sander Klein a écrit :
Sorry, I forgot to mention, I pushed another patch that may help you.
In HAProxy 2.0, it is the commit 0bf28f856 ("BUG/MINOR: mux-h1: Close
server connection if
On 2019-07-22 10:59, Christopher Faulet wrote:
Le 20/07/2019 à 19:50, Sander Klein a écrit :
Sorry, I forgot to mention, I pushed another patch that may help you.
In HAProxy 2.0, it is the commit 0bf28f856 ("BUG/MINOR: mux-h1: Close
server connection if input data remains in h1_detach()").
I
Le 20/07/2019 à 19:50, Sander Klein a écrit :
I just pathed up 2.0.2 and tested it. I still get 502's but a lot less.
I'm not sure if this is because I do less request/s or I hit something
else. The show errors show:
---
[20/Jul/2019:19:34:45.629] backend cluster1-xx (#11): invalid response
On 2019-07-19 14:05, Christopher Faulet wrote:
Le 19/07/2019 à 09:36, Sander Klein a écrit :
---
HTTP/1.1 200 OK
Server: nginx
Date: Fri, 19 Jul 2019 07:32:03 GMT
Content-Type: application/json; charset=UTF-8
Transfer-Encoding: chunked
Vary: Accept-Encoding
Vary:
Le 19/07/2019 à 09:36, Sander Klein a écrit :
The show errors:
---
Total events captured on [19/Jul/2019:08:34:25.093] : 31
[19/Jul/2019:08:34:23.405] backend cluster1-xx (#11): invalid response
frontend webservices (#18), server xxx (#2), event #30, src
x.x.x.x:63290
buffer starts at
Hi Lukas and Christopher,
I've combined the answer of your 2 mails.
On 2019-07-18 17:17, Lukas Tribus wrote:
Could be related to:
https://github.com/haproxy/haproxy/issues/176
Probably, but I'm not doing HTTP/1 and I have not found a request to
reproduce it with. It happens at random.
Le 18/07/2019 à 16:50, Sander Klein a écrit :
On 2019-07-18 09:15, Sander Klein wrote:
Hi,
Last night I tried upgrading from haproxy 1.9.8 to 2.0.2. After
upgrading I get random 502's and random instant 504's when visiting
pages.
Just tested with 'no option http-use-htx' in the defaults
Hello,
On Thu, 18 Jul 2019 at 16:51, Sander Klein wrote:
>
> On 2019-07-18 09:15, Sander Klein wrote:
> > Hi,
> >
> > Last night I tried upgrading from haproxy 1.9.8 to 2.0.2. After
> > upgrading I get random 502's and random instant 504's when visitin
On 2019-07-18 09:15, Sander Klein wrote:
Hi,
Last night I tried upgrading from haproxy 1.9.8 to 2.0.2. After
upgrading I get random 502's and random instant 504's when visiting
pages.
Just tested with 'no option http-use-htx' in the defaults section and
then my problems went away. Seems
Hi,
Last night I tried upgrading from haproxy 1.9.8 to 2.0.2. After
upgrading I get random 502's and random instant 504's when visiting
pages.
For the 502's I see the following in the log:
Jul 18 08:14:09 HOST haproxy[2003]: xxx:xxx:xxx:xxx:xxx::xxx
[18/Jul/2019:08:14:09.133] cluster1
13 matches
Mail list logo
