~.
for strictness
--
Ionel GARDAIS
Tech'Advantage CIO - IT Team manager
De: "Ionel GARDAIS"
À: "haproxy"
Envoyé: Vendredi 24 Janvier 2020 19:24:45
Objet: sticky session with cookie
Hi list,
I'm sorry if this question has already been asked but I don't see any answer to
it.
The
Hi list,
I'm sorry if this question has already been asked but I don't see any answer to
it.
The backend servers already set a cookie which value identifies it
(.)
Can haproxy archieve stickiness based on the value ?
Currently, I'm using
cookie AUTH_SESSION_ID prefix
server srv1
Hi,
FWIW, when I build for armhf (RaspberryPi 3b with Raspbian buster), I have to
add -latomic to the LD_FLAGS.
Ionel
- Mail original -
De: "Willy Tarreau"
À: " ???"
Cc: "haproxy"
Envoyé: Lundi 4 Novembre 2019 13:48:57
Objet: Re: arm64 builds?
Hi Ilya,
On Mon, Nov 04,
Hi Olivier,
As far as I can remember, 1.9 had a series of segfaults involving H2 and HTX,
patched from release to release.
[ http://www.haproxy.org/bugs/bugs-1.9.6.html |
http://www.haproxy.org/bugs/bugs-1.9.6.html ]
As a rule of thumb, I can only suggest you try with the latest 1.9 release
0:50
Objet: Re: Issue with HTX
Le 12/10/2019 à 14:23, GARDAIS Ionel a écrit :
> I might have been too enthusiast.
> haproxy is set as a TLS-endpoint thus the traces from the client-side are
> encrypted.
> The trace of the server side is plain text but as this is the client w
- Mail original -
De: "Willy Tarreau"
À: "Ionel GARDAIS"
Cc: "haproxy"
Envoyé: Samedi 12 Octobre 2019 06:20:40
Objet: Re: Issue with HTX
Hi Ionel,
On Fri, Oct 11, 2019 at 10:49:19PM +0200, GARDAIS Ionel wrote:
> Hi Willy,
>
> Got 2 tcpdump but I rea
Hi Willy,
Got 2 tcpdump but I really don't know where to start searching.
One is with HTX on the other HTX disabled.
May I send them to you ?
--
Ionel GARDAIS
Tech'Advantage CIO - IT Team manager
--
232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON
Capital EUR 219 300,00 - RCS Nanterre B 408
> Not for now, this requires the trace filters which are only planned but
> not yet available. Thus you'll have debugging enabled on the whole process
> at once. Can your reproduce this outside production ?
No.
But I can run tcpdump filtered on the backend's server IP and provide you with
a
rreau"
À: "Ionel GARDAIS"
Cc: "haproxy"
Envoyé: Mercredi 9 Octobre 2019 04:27:42
Objet: Re: Issue with HTX
Hi Ionel,
On Tue, Oct 08, 2019 at 03:33:16PM +0200, GARDAIS Ionel wrote:
> Hi,
>
> I'm facing a data corruption that seems related to HTX.
> Si
Hi,
I'm facing a data corruption that seems related to HTX.
Simply adding 'no option http-use-htx' solve the issue.
What kind of traces do you need to help diagnose the issue and how to collect
it ?
Thanks,
Ionel
--
232 avenue Napoleon BONAPARTE 92500 RUEIL MALMAISON
Capital EUR 219
Re: Issue with checks after 2.0.6
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 fi
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
;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
AIS
Tech'Advantage CIO - IT Team manager
- Mail original -
De: "Aleksandar Lazic"
À: "Ionel GARDAIS" , "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:
>
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
it depends on how haproxy is built (number of flags)
BQ_BEGIN
we use most of available options when testing on coverity
[ https://github.com/haproxy/haproxy/blob/master/.travis.yml#L8 |
https://github.com/haproxy/haproxy/blob/master/.travis.yml#L8 ]
can you share build command ? we may
> On Tue, Sep 10, 2019 at 08:29:38PM +0500, ??? wrote:
> > those findings are mostly mess (maybe, except few real bugs).
> > I do not mind sharing those findings with community, Willy ?
> > we need more manpower here.
>
> Oh no problem! I'm not the one asking to hide bugs, the more
Hi Leonardo,
What are you trying to achieve ?
What is your current setup ?
--
Ionel GARDAIS
Tech'Advantage CIO - IT Team manager
De: "BISSOLI Leonardo"
À: "haproxy"
Envoyé: Vendredi 30 Août 2019 17:05:57
Objet: HA-Proxy version 1.8.13 2018/07/30.
Hi All.
My name is Leonardo
Hi list,
We ran into an issue with haproxy 2.0.1 in front of SonarQube.
With HTX enabled, despite no errors being displayed either in haproxy nor
SonarQube, some but not all analysis failed.
>From SonarQube, debug shows protobuf requests
>(/sonarqube/api/rules/list.protobuf) failing and
19 matches
Mail list logo