Hi Damien, On Fri, Jun 15, 2012 at 12:53:48PM +0100, Damien Churchill wrote: > Hi, > > In the documentation for 1.4.18 in the keyword matrix it states that > the bind configuration keyword is only valid within listen or frontend > sections. However I've created a backend section that not only allows > the keyword, but also creates a socket (which doesn't seem to respond > to any requests). Is this a bug or is it intentional? I've included > the backend snippet to look at. > > backend some-backend-name > balance roundrobin > timeout check 10000 > bind :1557 > > server localhost 127.0.0.1:80 weight 1 check inter 2000 fall 3 > option httpchk HEAD / HTTP/1.1\r\nHost:localhost
Huh! this is clearly a bug ! I confirm it's still present in 1.5-dev11. It's amazing nobody ever encountered it before! It's nasty because the connection is accepted to the listening port, but nothing is done on it (it's not polled), so the connection remains in CLOSE_WAIT when the client leaves. I also suspect that this would prevent a soft restart from doing its job. I have to fix this ! Thanks for this useful report ! Willy
