I had the same problem after upgrading from 2.0.5 to 2.0.6. I ignored
the mistake and rolled back. I thought the mistake was mine. I use the
self compiled versions only privately.
The logs, config and build-script are in the attachment. HAProxy runs on
a debian 9 VM
Same with nbthread 1.
I gave my first try to git bisect and it looks like the offending commit is :
ab160a47acde9dc9c341b328c8716a721a389ab4 is the first bad commit
Author: Willy Tarreau
Date: Thu Sep 5 17:38:40 2019 +0200
On Mon, Sep 16, 2019 at 8:50 AM GARDAIS Ionel
> Hi Lukas,
> Same with nbthread 1.
> I gave my first try to git bisect and it looks like the offending commit is :
> ab160a47acde9dc9c341b328c8716a721a389ab4 is the first bad commit
> If you're fine with having the address and port reported in a tooltip
> when you hover over the name, just enabling "stats show-legends" in the
> frontend which shows your stats will achieve this.
thanks for this hint. That works perfectly for me.
please see attached patch
From 5fa12aec93f1e8989e06628fc5e41fc2556f532b Mon Sep 17 00:00:00 2001
From: Ilya Shipitsin
Date: Mon, 16 Sep 2019 16:13:10 +0500
Subject: [PATCH] BUILD: CI: install golang-1.13 when building BoringSSL
scripts/build-ssl.sh | 4
1 file changed, 4 insertions(+)
Done : https://github.com/haproxy/haproxy/issues/278
Tech'Advantage CIO - IT Team manager
- Mail original -
De: "Lukas Tribus"
À: "Ionel GARDAIS" , "Willy Tarreau"
Envoyé: Lundi 16 Septembre 2019 11:20:00
Objet: Re: Issue with checks after 2.0.6
I have a question about HAProxy configuration. Maybe someone has a solution
I have a HAProxy (v2.0) load balancer in front of many web servers.
When I restart the web servers the TCP socket remains closed for a few
seconds (~10s). For this reason I would like to retry failed attempts
Created an issue: https://github.com/haproxy/haproxy/issues/277
пт, 6 сент. 2019 г. в 12:36, Максим Куприянов :
> Hi everybody!
> Any news on this issue? Maybe you need some more detailed info? I still
> getting these errors on instances with high request rates.
> чт, 29 авг. 2019 г. в
On Mon, Sep 16, 2019 at 11:20:00AM +0200, Lukas Tribus wrote:
> On Mon, Sep 16, 2019 at 8:50 AM GARDAIS Ionel
> > Hi Lukas,
> > Same with nbthread 1.
> > I gave my first try to git bisect and it looks like the offending commit is
> > :
Am 16.09.2019 um 12:21 schrieb Willy Tarreau:
> Hi guys,
> On Mon, Sep 16, 2019 at 11:20:00AM +0200, Lukas Tribus wrote:
>> On Mon, Sep 16, 2019 at 8:50 AM GARDAIS Ionel
>>> Hi Lukas,
>>> Same with nbthread 1.
>>> I gave my first try to git bisect and it
Mail list logo