On Fri, May 13, 2016 at 10:09:04PM +0300, Arthur ??i??eic?? wrote: > I will attach 2 traces, for 1.6.4 and for 1.6.5.
So indeed in your traces, we see that 1.6.5 does bind(port=443, addr=0.0.0.0) while 1.6.4 has the correct address. At this point your kernel is innocent. I don't see what could cause this in haproxy and I can't reproduce it. Thus I'd really favor the switch to gcc 6 as a primary cause. I fear that we'll discover something not fun... Willy
