Hello,
Our travel agency is offering 50% Off on all Airlines & Hotel Bookings.
This offer is valid only for today.
Call Toll Free (855) 976-2535
Bobby
Travel Deals America
Thanks for your answer.
Interesting use case.
Regards
aleks
-- Originalnachricht --
Von: "Etienne Carrière"
An: "Aleksandar Lazic"
Cc: haproxy@formilux.org
Gesendet: 17.01.2018 23:28:40
Betreff: Re: [PATCH] Minor : Add a sampler to extract the microsecond
information of the hit date
Hi,
2018-01-17 20:47 GMT+01:00 Aleksandar Lazic :
(...)
> Sounds interesting.
> What use case have you in mind for this fetcher?
>
The use case is the following : we are using SPOE
(http://www.haproxy.org/download/1.8/doc/SPOE.txt) + SPO protocol in a
SaaS logic : Haproxy is in the customer office
Hi.
Any one any hints?
Regards
aleks
-- Originalnachricht --
Von: "Aleksandar Lazic"
An: "Adam Sherwood" ; haproxy@formilux.org
Gesendet: 15.01.2018 16:52:15
Betreff: Re[2]: How to parse custom PROXY protocol v2 header for custom
routing in HAProxy configuration?
Hi.
Follow up que
Hi.
-- Originalnachricht --
Von: "Etienne Carrière"
An: haproxy@formilux.org
Gesendet: 17.01.2018 14:02:40
Betreff: [PATCH] Minor : Add a sampler to extract the microsecond
information of the hit date
Hi,
I propose a patch to add a sampler that extract the microsecond part of
a hit
Ok I've tracked this problem down specifically to the usage of check tracking.
That is to say, the backend "example-api" is set to track the backend
"example-http". When that tracking is enabled and one of the servers in the
backend goes down then all of haproxy goes down and never recovers.
So
On Wed, Jan 17, 2018 at 05:43:02PM +0100, Olivier Houchard wrote:
> Ok you got me convinced, the attached patch don't check for duplicate
> cookies for disabled server, until we enable them.
I also prefer this approach.
> From cfc333d2b04686a3c488fdcb495cba64dbfec14b Mon Sep 17 00:00:00 2001
> Fr
On Wed, Jan 17, 2018 at 04:42:01PM +0100, Pierre Cheynier wrote:
> On 17/01/2018 15:56, Olivier Houchard wrote:
> >
> >> So, as a conclusion, I'm just not sure that producing this warning is
> >> relevant in case the IP is duplicated for several servers *if they are
> >> disabled*...
> > Or maybe w
Hi,
On 08/01/2018 14:32, Pierre Cheynier wrote:
> I retried this morning, I confirm that on 1.8.3, using
(...)
> I get RSTs (not seamless reloads) when I introduce the global/nbthread
> X, after a systemctl haproxy restart.
Any news on that ?
I saw one mworker commit ("execvp failure depending o
On 17/01/2018 15:56, Olivier Houchard wrote:
>
>> So, as a conclusion, I'm just not sure that producing this warning is
>> relevant in case the IP is duplicated for several servers *if they are
>> disabled*...
> Or maybe we should just advocate using 0.0.0.0 when we mean "no IP" :)
Not sure about t
On Wed, Jan 17, 2018 at 02:25:59PM +0100, Pierre Cheynier wrote:
> Hi,
>
> On 16/01/2018 18:48, Olivier Houchard wrote:
> >
> > Not really :) That's not a case I thought of.
> > The attached patch disables the generation of the dynamic cookie if the IP
> > is 0.0.0.0 or ::, so that it only gets ge
Hi,
On 16/01/2018 18:48, Olivier Houchard wrote:
>
> Not really :) That's not a case I thought of.
> The attached patch disables the generation of the dynamic cookie if the IP
> is 0.0.0.0 or ::, so that it only gets generated when the server gets a real
> IP. Is it OK with you ?
I'm not sure this
Hi,
I propose a patch to add a sampler that extract the microsecond part of a hit.
I had 2 ideas for implementation :
* The one in the attached patch which is a new sampler that return an
integer that is only the microsecond part of the timeval structure
* A new sampler that would return a string
Hello again!
Today I have also found another segfaults which occurred under heavy load
with nbthreads>1 on two haproxy-instances:
segfault at 0040 ip 5566f9ceb3af sp 7f98d0d569f8 error
7 in haproxy[5566f9be+169000]
and
segfault at fffe0040 ip 55bbf359d3af sp 000
Hi,
On 01/17/2018 10:16 AM, Christopher Faulet wrote:
> Le 16/01/2018 à 16:18, Lukas Tribus a écrit :
>> Hello Christopher,
>>
>>
>> On 16 January 2018 at 15:01, Bart Geesink
>> wrote:
>>> Hi,
>>>
>>> We have an issue in haproxy > 1.8 on CentOS when using SSL in the server
>>> configuration. Hapr
Hi!
I have multiple instances of haproxy=1.8-3 running with nbthreads=2 and
more. Those instances sometimes fail with an error like that in dmesg:
haproxy[22287]: segfault at 5574915aab8a ip 55828ce3adea sp
7ffc105c8fb0 error 6 in haproxy[55828cd2f000+169000]
Instances with no nbthreads-pa
Le 16/01/2018 à 16:18, Lukas Tribus a écrit :
Hello Christopher,
On 16 January 2018 at 15:01, Bart Geesink wrote:
Hi,
We have an issue in haproxy > 1.8 on CentOS when using SSL in the server
configuration. Haproxy sometimes logs a http status code "-1" followed
by the termination_state SDxx.
17 matches
Mail list logo