I ran strace on it just before CRASHTIME. It stopped on cue, with an exit code
of 134.
The strace output is here: haproxy strace - Pastebin.com
As you'll see, it looks very strange - immediately after a series of futex
calls (I've no idea of their significance, only noting that they don't appear
in the strace at other times) then system returns a number of "No such file or
directory" errors on a variety of system files, despite them being present
before and after.
Despite setting the ulimit in the session before starting haproxy no coredump
was generated.
I notice I can deploy haproxy without futex support. Is that worth a try?
Many thanks to all those helping me sort this out.
On Thursday, 11 December 2014, 17:45, Lukas Tribus <[email protected]>
wrote:
> I will do next time. And yes, was planning to run strace.
>
> Do I need to recompile to enable coredumps?
No, you just adjust ulimit before you start, and make
sure you didn't strip (as in the command strip) the
executable.
Then check the core with:
gdb path/to/the/binary path/to/the/core
and to something like
bt
or bt full
(within gdb).
Regards,
Lukas
