So I made a build this morning with libslz and re-enabled compression
and within an hour we had the exit code 134 errors, so zlib does not
seem to be the problem here.
On 4/7/2018 00:30, Willy Tarreau wrote:
On Fri, Apr 06, 2018 at 03:52:33PM +0200, Robin Geuze wrote:
I was actually the one that had the hunch to disable compression. I
suspected that this was the issue because there was a bunch of "abort" calls
in include/common/hathreads.h" which is used by the compression stuff.
However I just noticed those aborts are actually only there if DEBUG_THREAD
is defined which it doesn't seem to be for our build. So basically, I have
no clue whatsoever why disabling compression fixes the bug.
At least I don't feel alone :-)
I can see next week if we can make a build with slz instead of zlib (we seem
to be linked against zlib/libz atm).
Thank you, I appreciate it!