Re: Connections stuck in CLOSE_WAIT state with h2

Hi Olivier, On Wed, Jul 25, 2018 at 05:51:46PM +0200, Olivier Doucet wrote: > It seems I have the same issue as Milan : > We activated HTTP/2 on production a few weeks ago, and on some customers > (not all !) we can observe a very strange behaviour : it seems some > frontend sessions are not

Re: Connections stuck in CLOSE_WAIT state with h2

Hello, 2018-07-25 10:20 GMT+02:00 Willy Tarreau : > Hi Milan, > > On Wed, Jul 25, 2018 at 10:15:50AM +0200, Milan Petruzelka wrote: > > Now I'll add both patches (WIP-h2 and h2-error.diff) and give it a try in > > production. > > Thank you. At first I thought you still had the errors with them

Duplicate haproxy processes after setting server to MAINT via stats page

Hi,Running haproxy 1.5 under Ubuntu trusty as a service (service haproxy start/stop), I noticed that sometimes (not always) when I set a server to MAINT via the haproxy_stats page, I end up with duplicate haproxy processes. Any ideas? Has this problem been fixed in haproxy 1.8? Thank you in

Re: Configuring HAProxy session limits

Thanks for your response! It clarified alot.

Re: Issue with TCP splicing

On Wed, Jul 25, 2018 at 09:02:24AM -0400, Julien Semaan wrote: > Hi Olivier, > > Thanks for the time you're taking to check the issue. > > I'll get an environment back with TCP splicing enabled and I'll run it in > GDB and provide you a core dump > That would be great, thank you ! Olivier

Re: Issue with TCP splicing

Hi Olivier, Thanks for the time you're taking to check the issue. I'll get an environment back with TCP splicing enabled and I'll run it in GDB and provide you a core dump Best Regards, -- Julien Semaan jsem...@inverse.ca :: +1 (866) 353-6153 *155 ::www.inverse.ca Inverse inc. ::

Re: Issue with TCP splicing

Hi Julien, On Tue, Jul 24, 2018 at 01:29:49PM -0400, Julien Semaan wrote: > > Sorry, that was a "can" that really meant "can't" :) I can't reproduce it. >     Aw well, I was surprised it was so easy :) > yea, that would be too easy :) > > Can you try to upgrade to 1.8.12 ? A number of bugs

force-persist and use_server combined

Hi, I'd like to understand if I've made a mistake in configuration or there might be a bug in HAproxy 1.7.11. defaults section has "option redispatch". backend load_balancer mode http option httplog option httpchk HEAD /load_balance_health HTTP/1.1\r\nHost:\ foo.bar balance url_param

Re: [PATCH] MINOR: ssl: BoringSSL matches OpenSSL 1.1.0

Le 25 juil. 2018 à 10:34, Emmanuel Hocdet a écrit :Hi WillyLe 24 juil. 2018 à 18:59, Willy Tarreau a écrit :Hi Manu,On Mon, Jul 23, 2018 at 06:12:34PM +0200, Emmanuel Hocdet wrote:Hi Willy,This patch is necessary to build with current BoringSSL (SSL_SESSION is now

Re: [PATCH] MINOR: ssl: BoringSSL matches OpenSSL 1.1.0

Hi Willy > Le 24 juil. 2018 à 18:59, Willy Tarreau a écrit : > > Hi Manu, > > On Mon, Jul 23, 2018 at 06:12:34PM +0200, Emmanuel Hocdet wrote: >> Hi Willy, >> >> This patch is necessary to build with current BoringSSL (SSL_SESSION is now >> opaque). >> BoringSSL correctly matches OpenSSL

Re: Connections stuck in CLOSE_WAIT state with h2

Hi Milan, On Wed, Jul 25, 2018 at 10:15:50AM +0200, Milan Petruzelka wrote: > Now I'll add both patches (WIP-h2 and h2-error.diff) and give it a try in > production. Thank you. At first I thought you still had the errors with them applied and was despeared, now I understand there's still hope

Re: Connections stuck in CLOSE_WAIT state with h2

Hi Willy, On Tue, 24 Jul 2018 at 14:37, Willy Tarreau wrote: > So I'm having one update to emit the missing info on "show fd" (patch > merged > and pushed already, that I'm attaching here if it's easier for you) I've compiled version 1.8.12-12a4b5-16 with from Git and let it run overnight.