On 12/12/2014 07:16 AM, Vincent Bernat wrote:
❦ 12 décembre 2014 02:08 GMT, David Adams <[email protected]> :
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.
Your haproxy seems to crash while executing NSS-related code. ou can try
to remove the chroot directive and check if the problem still remains
after that.
Also, what is the content of your /etc/nsswitch.conf?
Exactly, i think Vincent is on the good way! i suspected openssl be
cause the code is full of 'abort()' calls.
Issue does not seem linked to syscall 'futex' but more on openssl trying
to (re-)open files after process have been chrooted and calling
'abort()' in failure case.
R,
Emeric
Emeric
