On Aug 4, 2010, at 4:09 PM, Willy Tarreau wrote: > On Wed, Aug 04, 2010 at 09:40:35AM -0500, Nick Hilem wrote: >> The netstat only appears to show the latest HAProxy being run and the config >> file that I've been using is the one specified in the command. You were >> right that the errors above seem to indicate an older HAProxy not being shut >> down properly, but even if I ensure a full stop and removal of pid before >> issuing a start... that particular error goes away but the initial problem >> still persists. After doing some more digging, I've noticed that if I... >> curl http://localhost/ >> ...immediately after a restart/start it will go through successfully, but >> then subsequent calls and/or if I don't issue the command quick enough, will >> timeout. >> But the calls to... >> curl http://localhost:7000/ >> ...will still go through. So it appears as though it can bind, but then >> relinquishes control to something else? > > could you disable health checks ? I wonder if your "quick enough" above > means "before the first health check".
Not sure how to determine if it was before or not... but I disabled the health checks and it appears to respond the same. > Willy >
