Re: haproxy and solarflare onload

2018-06-13 Thread Elias Abacioglu
Hi Emeric, On Tue, Jun 12, 2018 at 2:14 PM, Emeric Brun wrote: > > Yes, we are always interested testing hardware with our soft to advise the > end users if they could have some benefits. > But currently we are very busy and t thing we can't test your NIC before > the last quarter of year. > >

Re: Connections stuck in CLOSE_WAIT state with h2

2018-06-13 Thread Janusz Dziemidowicz
2018-06-13 19:14 GMT+02:00 Willy Tarreau : > On Wed, Jun 13, 2018 at 07:06:58PM +0200, Janusz Dziemidowicz wrote: >> 2018-06-13 14:42 GMT+02:00 Willy Tarreau : >> > Hi Milan, hi Janusz, >> > >> > thanks to your respective traces, I may have come up with a possible >> > scenario explaining the

Re: Connections stuck in CLOSE_WAIT state with h2

2018-06-13 Thread Willy Tarreau
On Wed, Jun 13, 2018 at 07:06:58PM +0200, Janusz Dziemidowicz wrote: > 2018-06-13 14:42 GMT+02:00 Willy Tarreau : > > Hi Milan, hi Janusz, > > > > thanks to your respective traces, I may have come up with a possible > > scenario explaining the CLOSE_WAIT you're facing. Could you please > > try the

Re: Connections stuck in CLOSE_WAIT state with h2

2018-06-13 Thread Janusz Dziemidowicz
2018-06-13 14:42 GMT+02:00 Willy Tarreau : > Hi Milan, hi Janusz, > > thanks to your respective traces, I may have come up with a possible > scenario explaining the CLOSE_WAIT you're facing. Could you please > try the attached patch ? Unfortunately there is no change for me. CLOSE_WAIT sockets

Haproxy health check interval value is not being respected

2018-06-13 Thread Adwait Gokhale
Hello, I have come across an issue with use of 'inter' parameter that sets interval between two consecutive health checks. When configured, I found that health checks are twice as aggressive than what is configured. For instance, when I have haproxy with 2 backends with 'default-server inter

mistake in email-alert to documentation

2018-06-13 Thread Filip Cornelissen | SkillSource
Found a mistake in the documentation.   see: http://cbonte.github.io/haproxy-dconv/1.9/configuration.html#4.2-email-alert%20to or: https://github.com/haproxy/haproxy/blob/master/doc/configuration.txt#L3515   the line: Also requires "email-alert mailers" and "email-alert to" to be set

Re: Connections stuck in CLOSE_WAIT state with h2

2018-06-13 Thread Willy Tarreau
Hi Milan, hi Janusz, thanks to your respective traces, I may have come up with a possible scenario explaining the CLOSE_WAIT you're facing. Could you please try the attached patch ? Thanks, Willy >From fc527303f1391849ae5880b304486e328010b5ff Mon Sep 17 00:00:00 2001 From: Willy Tarreau Date:

Re: haproxy with QAT requires root

2018-06-13 Thread Christian Braun
Hello Aleks, On 2018-06-12 13:05, Aleksandar Lazic wrote: > Hi. > > On 12/06/2018 12:58, Christian Braun wrote: >> Hello, >> >> i am testing haproxy with a QAT card (Intel QuickAssit-Technology). I >> am getting "SSL handshake failure" running haproxy with user nobody and >> ssl-engine qat. When