Hi guys,
On Thu, Feb 22, 2018 at 04:20:07PM +0100, Tim Düsterhus wrote:
> Frank,
>
> Am 22.02.2018 um 15:33 schrieb Frank Schreuder:
> >> Code 134 implies the worker was killed with SIGABRT. You could check
> >> whether there is a core dump.
> >
> > I don't have any core dumps.
>
> Check whether coredumps are enabled using `ulimit -c`, often they are
> disabled by default, because they could contain sensitive information.
> After the next crash you should be able to retrieve a backtrace using
> gdb. Possibly recompile haproxy with debug symbols for it to be useful.
If it happens quickly, another option might be to attach gdb to the
process after it is started. But with multiple processes it's not very
convenient.
A few more things on the core dumps :
- they are ignored if you have a chroot statement in the global section
- you need not to use "user/uid/group/gid" otherwise the system also
disables core dumps
There are very few abort() calls in the code :
- some in the thread debugging code to detect recursive locks ;
- one in the cache applet which triggers on an impossible case very
likely resulting from cache corruption (hence a bug)
- a few inside the Lua library
- a few in the HPACK decompressor, detecting a few possible bugs there
Except for Lua, all of them were added during 1.8, so depending on what the
configuration uses, there are very few possible candidates.
Cheers,
Willy
