Re: v1.9.6+HEAD: segfault in h1_skip_chunk_crlf

2019-04-19 Thread Christopher Faulet
Le 19/04/2019 à 11:40, William Dauchy a écrit : Hi, On Fri, Apr 19, 2019 at 6:26 AM Willy Tarreau wrote: Good catch but in my opinion we should instead fix the called function (h1_skip_chunk_crlf). h1_skip_chunk_size() properly deals with the case where start==stop, but h1_skip_chunk_crlf()

Re: [PATCH] wurfl device detection build fixes and dummy library

2019-04-19 Thread Paul Stephen Borile
Hi Willy, fine for me, thanks for the adjustments and no problem backporting this to 1.9. I also confirm that the contact email address is working correctly. Thanks! -Paul On Fri, Apr 19, 2019 at 4:46 PM Willy Tarreau wrote: > Hi Paul, > > On Thu, Apr 18, 2019 at 02:46:17PM +0200, Paul

Re: [PATCH] wurfl device detection build fixes and dummy library

2019-04-19 Thread Willy Tarreau
Sorry, with the patches this time. Willy >From 806aebcba5b7c5e3b780c63ff37a54b38a510e19 Mon Sep 17 00:00:00 2001 From: Willy Tarreau Date: Fri, 19 Apr 2019 16:12:08 +0200 Subject: [PATCH 07/13] WIP: wurfl: pass -fPIC when compiling --- contrib/wurfl/makefile | 3 +++ 1 file changed, 3

Re: [PATCH] wurfl device detection build fixes and dummy library

2019-04-19 Thread Willy Tarreau
Hi Paul, On Thu, Apr 18, 2019 at 02:46:17PM +0200, Paul Stephen Borile wrote: > please find attached to this email the 6 patches that cover various areas > of restyling of > the WURFL device detection feature for HAProxy. All patches can be back > ported to 1.9 if necessary. > Last patch is a

Re: [PATCH] Enable set-dst and set-dst-port at tcp-request content layer

2019-04-19 Thread Willy Tarreau
Hi Baptiste, On Fri, Apr 19, 2019 at 10:26:09AM +0200, Baptiste wrote: > For some reasons, 'tcp-request content' can't execute set-dst and > set-dst-port. > This patch fixes this issue. > Note that this patch will be useful for the do-resolve action. I was initially wondering when that could be

Re: [PATCH 1/1] REGTEST: Missing REQUIRE_VERSION declarations.

2019-04-19 Thread Willy Tarreau
On Fri, Apr 19, 2019 at 11:20:52AM +0200, flecai...@haproxy.com wrote: > From: Frédéric Lécaille > > checks/s1.vtc needs support for "srvrecord" which came with 1.8 version. > peers/s_basic_sync.vtc and s_tls_basic_sync.vtc need support for "server" > keyword usage in "peers" section which

Re: nmap showing internal IP disclosure of ELB and not the HAPROXY of port 80

2019-04-19 Thread Willy Tarreau
On Sat, Mar 09, 2019 at 11:20:41AM +0200, Ciprian Dorin Craciun wrote: > On Sat, Mar 9, 2019 at 10:45 AM DHAVAL JAISWAL wrote: > > frontend loadbalancer_mycom > > bind 10.100.22.30:80 > > mode http > > > > redirect scheme https if !{ ssl_fc } > > > If this line is the one that makes the

Re: [External] Re: QAT intermittent healthcheck errors

2019-04-19 Thread Marcin Deranek
Hi Emeric, On 4/18/19 4:35 PM, Emeric Brun wrote: An other interesting trace would be to perform a "show sess" command on a stucked process through the master cli. And also the "show fd" Here it is: show proc # 13409 master 0 1

Re: QAT intermittent healthcheck errors

2019-04-19 Thread Marcin Deranek
On 4/18/19 11:06 AM, Emeric Brun wrote: I think you can do that this way: Remove the option httchk (or prefix it by "no": "no option httchk " if it is configured into the defaults section and add the following 2 lines: option tcp-check tcp-check connect This shouldn't perform the handshake

Re: v1.9.6 socket unresponsive with high cpu usage

2019-04-19 Thread William Dauchy
On Fri, Apr 19, 2019 at 01:30:07PM +0200, Willy Tarreau wrote: > Note that with all the scheduling issues we've fixed over the last > days, there are multiple candidates which could cause this. Another > one was the lack of effect of the nice parameter which is normally > set on the CLI but the

Re: v1.9.6 socket unresponsive with high cpu usage

2019-04-19 Thread Willy Tarreau
Hi William, On Fri, Apr 19, 2019 at 11:05:51AM +, William Dauchy wrote: > Hi Willy, > > On Sat, Apr 13, 2019 at 08:01:53AM +0200, Willy Tarreau wrote: > > Did you issue one of the commands that tries to be alone, thus "show sess" > > or "show fd" ? It's possible that you were having only one

Re: v1.9.6 socket unresponsive with high cpu usage

2019-04-19 Thread William Dauchy
Hi Willy, On Sat, Apr 13, 2019 at 08:01:53AM +0200, Willy Tarreau wrote: > Did you issue one of the commands that tries to be alone, thus "show sess" > or "show fd" ? It's possible that you were having only one thread blocked > initially and that with the command that was waiting for all threads

Re: v1.9.6+HEAD: segfault in h1_skip_chunk_crlf

2019-04-19 Thread William Dauchy
Hi, On Fri, Apr 19, 2019 at 6:26 AM Willy Tarreau wrote: > Good catch but in my opinion we should instead fix the called function > (h1_skip_chunk_crlf). h1_skip_chunk_size() properly deals with the case > where start==stop, but h1_skip_chunk_crlf() says "If not enough data are > available, the

[PATCH 0/1] reg-tests fix.

2019-04-19 Thread flecaille
From: Frédéric Lécaille Hi ML, Here is a little patch to fix the reg tests with missing REQUIRE_VERSION declarations. Fred. Frédéric Lécaille (1): REGTEST: Missing REQUIRE_VERSION declarations. reg-tests/checks/s1.vtc | 1 + reg-tests/peers/s_basic_sync.vtc | 2 ++

[PATCH 1/1] REGTEST: Missing REQUIRE_VERSION declarations.

2019-04-19 Thread flecaille
From: Frédéric Lécaille checks/s1.vtc needs support for "srvrecord" which came with 1.8 version. peers/s_basic_sync.vtc and s_tls_basic_sync.vtc need support for "server" keyword usage in "peers" section which came with 2.0 version. --- reg-tests/checks/s1.vtc | 1 +

[PATCH] Enable set-dst and set-dst-port at tcp-request content layer

2019-04-19 Thread Baptiste
Hi, For some reasons, 'tcp-request content' can't execute set-dst and set-dst-port. This patch fixes this issue. Note that this patch will be useful for the do-resolve action. Baptiste From c384d381dbbfa0adae04137238b4fd11593bd2bf Mon Sep 17 00:00:00 2001 From: Baptiste Assmann Date: Thu, 18