Hi Sasha,
so the crash happens sporadically after hours of production traffic? Or
does it crash right away after you start it?
You are saying this started with 1.6.4, what was the version you used
before and that worked fine? 1.6.3?
Before starting haproxy, enable core dumping like this:
ulimit -c unlimited
Confirm its unlimited (right before starting haproxy from this shell):
ulimit -c
Disabling compiler optimizations will make sure the generated coredump
is as meaningful as possible, you can do it like this:
make clean; make CFLAGS="-O0 -g -fno-strict-aliasing
-Wdeclaration-after-statement" TARGET=linux2628 USE_ZLIB=1 USE_OPENSSL=1
USE_PCRE=1
But be advised that there will be performance/cpu impact, so you better
monitor it.
When you have a coredump, you can provide a backtrace with gdb like this:
gdb <haproxy-executable> <coredump>
and issuing a "bt full"
Regards,
Lukas
