Hello,
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
cheers
Michael
Am
Done : https://github.com/haproxy/haproxy/issues/278
--
Ionel GARDAIS
Tech'Advantage CIO - IT Team manager
- Mail original -
De: "Lukas Tribus"
À: "Ionel GARDAIS" , "Willy Tarreau"
Cc: "haproxy"
Envoyé: Lundi 16 Septembre 2019 11:20:00
Objet:
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:
>> Hello!
>>
>> On Mon, Sep 16, 2019 at 8:50 AM GARDAIS Ionel
>> wrote:
>>>
>>> Hi Lukas,
>>>
>>> Same with nbthread 1.
>>>
>>> I gave my first try to git bisect and it
Hi guys,
On Mon, Sep 16, 2019 at 11:20:00AM +0200, Lukas Tribus wrote:
> Hello!
>
> On Mon, Sep 16, 2019 at 8:50 AM GARDAIS Ionel
> wrote:
> >
> > Hi Lukas,
> >
> > Same with nbthread 1.
> >
> > I gave my first try to git bisect and it looks like the offending commit is
> > :
> >
> >
Hello!
On Mon, Sep 16, 2019 at 8:50 AM GARDAIS Ionel
wrote:
>
> 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
> commit
AIS" , "haproxy"
Envoyé: Dimanche 15 Septembre 2019 20:37:09
Objet: Re: Issue with checks after 2.0.6
Hello,
On Sat, Sep 14, 2019 at 4:58 PM GARDAIS Ionel
wrote:
> > What was the previous release that worked for you? 2.0.5 or something older?
>
> 2.0.5 worked well from t
Hello,
On Sat, Sep 14, 2019 at 4:58 PM GARDAIS Ionel
wrote:
> > What was the previous release that worked for you? 2.0.5 or something older?
>
> 2.0.5 worked well from the checks point of vue.
Ok, so this is a regression in 2.0.6.
Please try whether limiting the threads to 1 (global section:
;haproxy"
Envoyé: Samedi 14 Septembre 2019 14:16:30
Objet: Re: Issue with checks after 2.0.6
When you enable htx do you have the same problems?
Comment in `no option http-use-htx`
Regards Aleks
Sat Sep 14 14:12:30 GMT+02:00 2019 GARDAIS Ionel
:
> Also, haproxy and servers are on t
Hello,
On Sat, Sep 14, 2019 at 1:08 PM GARDAIS Ionel
wrote:
>
> Hi,
>
> I've just upgraded to 2.0.6 and all server checks went erratic.
> I had to disable checks for the servers to be reachable.
What was the previous release that worked for you? 2.0.5 or something older?
Thanks,
Lukas
, servers are not overloaded by other connections.
>
> --
> Ionel GARDAIS
> Tech'Advantage CIO - IT Team manager
>
> - Mail original -
> De: "Ionel GARDAIS"
> À: "Aleksandar Lazic"
> Cc: "haproxy"
> Envoyé: Samedi 14 Septembre 2019
ndar Lazic"
Cc: "haproxy"
Envoyé: Samedi 14 Septembre 2019 14:07:42
Objet: Re: Issue with checks after 2.0.6
Sure.
Note : as soon as I remove the check from the server line then 'systemctl
reload haproxy', access is OK.
# haproxy -vv
HA-Proxy version 2.0.6-1~bpo9+1 2019/09/14 - http
RDAIS" , "haproxy"
Envoyé: Samedi 14 Septembre 2019 13:12:49
Objet: Re: Issue with checks after 2.0.6
Hi.
Am 14.09.2019 um 13:08 schrieb GARDAIS Ionel:
> Hi,
>
> I've just upgraded to 2.0.6 and all server checks went erratic.
> I had to disable checks for the
Hi.
Am 14.09.2019 um 13:08 schrieb GARDAIS Ionel:
> Hi,
>
> I've just upgraded to 2.0.6 and all server checks went erratic.
> I had to disable checks for the servers to be reachable.
>
> The observed behavior was a flip-flap (but mostly down) of server availability
> with L4TOUT when the server
13 matches
Mail list logo
