Hi Rahul, On Mon, Sep 10, 2012 at 07:07:05PM +0530, Rahul Nair wrote: > Team, > > Sorry for troubling you guys again.... > Today while testing HAProxy+TPROXY setup I observed that few versions of > kernel was not compatible. > > In debug logs I got following errors: > [...] > 00000034:Apps-ssl.clicls[0017:0018] > 00000034:Apps-ssl.closed[0017:0018] > 00000035:Apps-ssl.accept(000d)=0017 from [xxx.xxx.xx.x:58617] > [ALERT] 252/021407 (3683) : Cannot bind to tproxy source address before > connect() for proxy Apps-ssl. Aborting. > [ALERT] 252/021407 (3683) : Cannot bind to tproxy source address before > connect() for proxy Apps-ssl. Aborting. > [ALERT] 252/021407 (3683) : Cannot bind to tproxy source address before > connect() for proxy Apps-ssl. Aborting. > [ALERT] 252/021407 (3683) : Cannot bind to tproxy source address before > connect() for proxy Apps-ssl. Aborting. > [...] > > *OS used: *Ubuntu 10.04 > > *On further investigation Following kernel versions are affected by the > compatibility issue:* > *2.6.32*-41-server > *2.6.32*-42-server > *2.6.35*-32-generic > *2.6.35*-32-generic > > *Following kernels are found compatible:* > *2.6.35*-22-server > *2.6.32*-24-server > *2.6.38*-15-server > > I prefer to use *2.6.38*-15-server, I will like to take advise of the group > if I am moving towards right direction.
This reminds me of older issues related to an address binding regression which used to affect listening addresses. Are the faulty kernels up to date or were there fixes available past the listed versions above ? Also, I have not experienced any issue with 2.6.32.59 nor with 2.6.35.14, so if your kernels are based on these, maybe it is an issue with the distro's kernel ? BTW, I'm assuming you're running your tests as root, since this is required for transparent binding. Regards, Willy
