On Fri, Jun 22, 2018 at 07:03:36AM -0700, PGNet Dev wrote: > Hi > > On 6/21/18 10:50 PM, Willy Tarreau wrote:> Well, first please ensure you're > building latest fixes and not and old > > version otherwise you'll expose yourself to all these known and now fixed > > bugs : > > oops, missed that! :-/ > > switching to 'latest' in branch, v1.8.9, still see the same in "-vv" output, > > ldd `which haproxy` | egrep "ssl|crypto" > libssl.so.1.1 => /usr/local/openssl11/lib64/libssl.so.1.1 > (0x00007f6a21894000) > libcrypto.so.1.1 => /usr/local/openssl11/lib64/libcrypto.so.1.1 > (0x00007f6a213f9000) > > > haproxy -vv > HA-Proxy version 1.8.9-83616ec 2018/05/18 > Copyright 2000-2018 Willy Tarreau <wi...@haproxy.org> > > Build options : > TARGET = linux2628 > CPU = generic > CC = gcc > CFLAGS = -O2 -g -fno-strict-aliasing > -Wdeclaration-after-statement -fwrapv -fno-strict-overflow > -Wno-format-truncation -Wno-null-dereference -Wno-unused-label > OPTIONS = USE_OPENSSL=1 USE_SYSTEMD=1 USE_PCRE2=1 > USE_PCRE2_JIT=1 > > Default settings : > maxconn = 2000, bufsize = 16384, maxrewrite = 1024, > maxpollevents = 200 > > Built with OpenSSL version : OpenSSL 1.1.0h-fips 27 Mar 2018 > Running on OpenSSL version : OpenSSL 1.1.0h 27 Mar 2018 > ... > > > Again, not sure if it's a 'real' problem, or just a report artifact.
Did you try to disable or adjust the PCRE flags as I indicated in previous e-mail to see if it's the side effect ? Willy