Am Tue, 30 Jul 2013 21:40:34 +0200 schrieb Lukas Tribus <[email protected]>:
> Hi Rainer! > > > > I'm using haproxy on FreeBSD 9.1-amd64 inside a VMware VM. > > > > I realized that when I have a situation where all servers in a > > backend are down, haproxy crashes: > > Jul 30 08:03:52 px2-bla kernel: pid 58816 (haproxy), uid 80: > > exited on signal 11 (core dumped) > > > > pkg info|grep haproxy > > haproxy-1.4.24 The Reliable, High Performance > > can you post the output of "haproxy -vv"? (px2-bla </root>) 0 # haproxy -vv HA-Proxy version 1.4.24 2013/06/17 Copyright 2000-2013 Willy Tarreau <[email protected]> Build options : TARGET = freebsd CPU = generic CC = cc CFLAGS = -O2 -pipe -fno-strict-aliasing -DFREEBSD_PORTS OPTIONS = USE_STATIC_PCRE=1 Default settings : maxconn = 2000, bufsize = 16384, maxrewrite = 8192, maxpollevents = 200 Encrypted password support via crypt(3): yes Available polling systems : kqueue : pref=300, test result OK poll : pref=200, test result OK select : pref=150, test result OK Total: 3 (3 usable), will use kqueue. > > > After some tinkering, I got a core-dump out of it: > > The core-dump doesn't look very useful, seems like the debugging > symbols where stripped. > > > Could you recompile haproxy with the following CFLAGS: > make CFLAGS="-g -O0" TARGET=[...] > > and regenerate the core-dump. The GDB output should be more > informative then. > > If the executable comes from a packaging system (ports?), you may be > able to use a debug-package instead of recompiling haproxy (although > compiler optimization may obfuscate the backtrace). I'll look into it. It's created by our poudriere package-building system. Regards, Rainer
