I already went back and forth between the 2 versions to confirm that it's still working fine in 1.6.4.
When I get home I will try to start haproxy in debug mode and I will try to strace it (any help on this would be appreciated). If all fails I will reboot the server in a non-grsec kernel (4.5.2 btw). Pe 13 mai 2016 6:51 p.m., "Willy Tarreau" <w...@1wt.eu> a scris: > On Fri, May 13, 2016 at 06:30:35PM +0300, Arthur ??i??eic?? wrote: > > Hi, > > > > 1.6.4 worked fine with the same config. > > > > I noticed this because I have the same port bound on 127.0.0.1 too and > > haproxy refused to start after upgrade. > > > > Another curious thing is that with haproxy bind on *two* ipv4 addresses I > > also see two *:143 in the 'ss' output. > > > > This is not specific to the listen directive. It happens on all ipv4 > > addresses with 'frontend' or 'listen' both TCP and HTTP. > > Thus it sounds like something changed in the address parser and affected > you. The problem is that I'm not seeing any such change. > > It would be interesting to try to rebuild 1.6.4 on the same machine to > see if it suddenly fails, possibly indicating something else has changed > (eg: libc update, build options, etc). > > Thanks > willy > >
