Haproxy1.6.8 crash

Help!
1

who can resolve this problem ?

00000004:lua.clihdr[000b:000c]: If-Modified-Since: Wed, 03 Aug 2016 10:05:28 GMT
haproxy: malloc.c:2842: mremap_chunk: Assertion `((size + offset) & (_rtld_global_ro._dl_pagesize - 1)) == 0’ failed.

sudo haproxy -vv
HA-Proxy version 1.6.8 2016/08/14
Copyright 2000-2016 Willy Tarreau willy@haproxy.org

Build options :
TARGET = linux26
CPU = generic
CC = gcc
CFLAGS = -O2 -g -fno-strict-aliasing -Wdeclaration-after-statement
OPTIONS = USE_LINUX_SPLICE=1 USE_LINUX_TPROXY=1 USE_CRYPT_H=1 USE_ZLIB=1 USE_VSYSCALL=1 USE_REGPARM=1 USE_OPENSSL=1 USE_LUA=1 USE_STATIC_PCRE=1 USE_PCRE_JIT=1 USE_TFO=1 USE_NS=1

Default settings :
maxconn = 2000, bufsize = 16384, maxrewrite = 1024, maxpollevents = 200

Encrypted password support via crypt(3): yes
Built with zlib version : 1.2.8
Compression algorithms supported : identity(“identity”), deflate(“deflate”), raw-deflate(“deflate”), gzip(“gzip”)
Built with OpenSSL version : OpenSSL 1.0.1f 6 Jan 2014
Running on OpenSSL version : OpenSSL 1.0.1f 6 Jan 2014
OpenSSL library supports TLS extensions : yes
OpenSSL library supports SNI : yes
OpenSSL library supports prefer-server-ciphers : yes
Built with PCRE version : 8.31 2012-07-06
PCRE library supports JIT : no (libpcre build without JIT?)
Built with Lua version : Lua 5.3.3
Built with transparent proxy support using: IP_TRANSPARENT IPV6_TRANSPARENT IP_FREEBIND
Built with network namespace support

Available polling systems :
epoll : pref=300, test result OK
poll : pref=200, test result OK
select : pref=150, test result OK
Total: 3 (3 usable), will use epoll.

2

Please share the configuration and some specifics about the crash (when does it crash? how does it crash? under load, or when a specific request comes in?).

Can you reliably reproduce the crash?

Please provide a backtrace, preferably without compiler optimizations:

  1. compile with CFLAGS="-O0 -g -fno-strict-aliasing -Wdeclaration-after-statement"
  2. enable coredumping: ulimit -c unlimited (before starting haproxy)
  3. reproduce the crash
  4. use gdb to provide a backtrace (“gdb haproxy core” and “bt full” in the gdb cli)

Please report those findings to the mailing list at haproxy at formilux dot org (no need to subscribe).

Thanks!