Re: Restrict HAProxy stats page to a specific IP

Hi, On Mon, Jul 03, Kaushal Shriyan wrote: > Thanks for the email and it is working as expected. I will appreciate if > you let me know to allow multiple office IP address. > > For example http://IP1:1936 and http://IP2:1936 > > http://IP1:1936 -> http://192.168.1.10:1936 > http://IP2:1936 ->

[PATCH] DOC: fix references to the section about time format

Hi, Small patch updating configuration.txt stick table time format(section 2.4) cross references. -Jarno -- Jarno Huuskonen >From 32a999d2f41cf57eae479c6d4c6514a847d9d788 Mon Sep 17 00:00:00 2001 From: Jarno Huuskonen Date: Tue, 4 Jul 2017 10:35:12 +0300 Subject:

Re: Fix building haproxy with recent LibreSSL

On Tue, Jul 04, 2017 at 11:07:31AM +0300, Dmitry Sivachenko wrote: > On FreeBSD it does fix a build (though new warning appear which I can't > explain because of the lack of SSL knowledge): > > src/ssl_sock.c:803:2: warning: incompatible integer to pointer conversion > assigning to 'void

Re: Logging TLVs from PROXY protocol v2

Thanks Willy for responding. I’ll read over the code soon to see if it makes sense to expose some of the TLVs that aren’t already. I shared your residence to abuse the protocol and maintain transparency. My circumstance is that I have an environment of a very large enterprise inter-network

Re: Logging TLVs from PROXY protocol v2

On Mon, Jul 03, 2017 at 10:11:29PM +1000, Marc Boschma wrote: > Is there anyway to log details from the PROXY protocol version 2, such as > namespace or any other TLVs? Especially custom... > > On TLVs I'm looking at someway to pass through a unique ID across a series > of proxies. So being able

Re: Fix building haproxy with recent LibreSSL

> On 04 Jul 2017, at 11:04, Willy Tarreau wrote: > > Hi Dmitry, > > [CCing Bernard, the patch's author] > > On Mon, Jul 03, 2017 at 12:34:52AM +0300, Dmitry Sivachenko wrote: >> Hello, >> >> can you please take a look at proposed patch to fix build of haproxy with >> recent

Re: Fix building haproxy with recent LibreSSL

On Tue, Jul 04, 2017 at 11:12:20AM +0300, Dmitry Sivachenko wrote: > >> https://www.mail-archive.com/haproxy@formilux.org/msg25819.html > > > > > > Do you know if the patch applies to 1.8 (it was mangled so I didn't try). > > > Sorry, hit reply too fast: no, one chunk fails against 1.8-dev2

Re: Reg: HAProxy 1.6.12 on RHEL7.2 (MAXCONN in FRONT-END/LISTEN BLOCK)

Hi, On Tue, Jul 04, Igor Cicimov wrote: > On Tue, Jul 4, 2017 at 1:34 PM, Velmurugan Dhakshnamoorthy < > dvel@gmail.com> wrote: > > > Thanks much for detailed explanation. > > > > Once the limit of 100 sessions are reached, note we are talking about *100 > > sessions in Weblogic* and *NOT

Re: Fix building haproxy with recent LibreSSL

Hi Dmitry, [CCing Bernard, the patch's author] On Mon, Jul 03, 2017 at 12:34:52AM +0300, Dmitry Sivachenko wrote: > Hello, > > can you please take a look at proposed patch to fix build of haproxy with > recent version of LibreSSL? > >

Re: Logging TLVs from PROXY protocol v2

On Tue, Jul 04, 2017 at 07:17:05PM +1000, Marc Boschma wrote: > My circumstance is that I have an environment of a very large enterprise > inter-network with a large number of intranets (many with overlapping address > space) that need to be proxied through a series of proxies to a shared / >

Any more detail on the plan for multi-threading and or multi-process support?

It looks like some exciting stuff is on the way in haproxy-1.8-dev! Could I ask for a bit more detail on the plans for multi-threading or multi-process options? For the vast majority of HTTP applications, binding one cluster to one front end & process is fine. But for high traffic sites on newer

Re: Fix building haproxy with recent LibreSSL

> On 04 Jul 2017, at 11:04, Willy Tarreau wrote: > > Hi Dmitry, > > [CCing Bernard, the patch's author] > > On Mon, Jul 03, 2017 at 12:34:52AM +0300, Dmitry Sivachenko wrote: >> Hello, >> >> can you please take a look at proposed patch to fix build of haproxy with >> recent

Re: [PATCH] DOC: fix references to the section about time format

On Tue, Jul 04, 2017 at 10:50:59AM +0300, Jarno Huuskonen wrote: > Hi, > > Small patch updating configuration.txt stick table time format(section > 2.4) cross references. Applied, thank you Jarno! Willy

Re: ssl: crashing since 8d85aa (BUG/MAJOR: map: fix segfault ...)

Am 04.07.2017 um 23:18 schrieb Willy Tarreau: > On Tue, Jul 04, 2017 at 10:57:08PM +0200, Lukas Tribus wrote: >> The call trace doesn't really look different when I used -dM or >> -DDEBUG_MEMORY. >> >> I was able to get a different trace by actually connecting to a backend >> however, >>

Re: ssl: crashing since 8d85aa (BUG/MAJOR: map: fix segfault ...)

Hi Lukas, On Tue, Jul 04, 2017 at 09:56:09PM +0200, Lukas Tribus wrote: > Hi Emeric, > > > since 8d85aa4 ("BUG/MAJOR: map: fix segfault during 'show > map/acl' on cli") my setup crashes when a request comes in > going through SSL termination. > > memory corruption, invalid pointers, double

Re: ssl: crashing since 8d85aa (BUG/MAJOR: map: fix segfault ...)

Hi Willy, Am 04.07.2017 um 22:24 schrieb Willy Tarreau: > Hi Lukas, > > On Tue, Jul 04, 2017 at 09:56:09PM +0200, Lukas Tribus wrote: >> Hi Emeric, >> >> >> since 8d85aa4 ("BUG/MAJOR: map: fix segfault during 'show >> map/acl' on cli") my setup crashes when a request comes in >> going through

Re: ssl: crashing since 8d85aa (BUG/MAJOR: map: fix segfault ...)

On Tue, Jul 04, 2017 at 10:29:27PM +0200, Lukas Tribus wrote: > > On Tue, Jul 04, 2017 at 09:56:09PM +0200, Lukas Tribus wrote: > >> Hi Emeric, > >> > >> > >> since 8d85aa4 ("BUG/MAJOR: map: fix segfault during 'show > >> map/acl' on cli") my setup crashes when a request comes in > >> going

Re: ssl: crashing since 8d85aa (BUG/MAJOR: map: fix segfault ...)

Hi, Am 04.07.2017 um 22:35 schrieb Willy Tarreau: > > This one should theorically not be caused by an issue in the task scheduler, > unless we're reusing something already freed. We could retry it with -dM > and/or -DDEBUG_MEMORY to force earlier corruption to pop up. The call trace doesn't

Re: ssl: crashing since 8d85aa (BUG/MAJOR: map: fix segfault ...)

On Tue, Jul 04, 2017 at 10:57:08PM +0200, Lukas Tribus wrote: > The call trace doesn't really look different when I used -dM or > -DDEBUG_MEMORY. > > I was able to get a different trace by actually connecting to a backend > however, > (instead of showing an haproxy internal 403 error): (...)

ssl: crashing since 8d85aa (BUG/MAJOR: map: fix segfault ...)

Hi Emeric, since 8d85aa4 ("BUG/MAJOR: map: fix segfault during 'show map/acl' on cli") my setup crashes when a request comes in going through SSL termination. memory corruption, invalid pointers, double free is what haproxy randomly crashes with. Here 2 crashes with full backtrace: *** Error

Re: Any more detail on the plan for multi-threading and or multi-process support?

Hi Malcolm, On Tue, Jul 04, 2017 at 03:27:51PM +0100, Malcolm Turnbull wrote: > It looks like some exciting stuff is on the way in haproxy-1.8-dev! Let's hope so! > Could I ask for a bit more detail on the plans for multi-threading or > multi-process options? I'll respond myself so that it