Nick, try rather: $ curl 10.202.197.103:7000 $ curl 10.208.202.70:7000 You are not using localhost:7000 in your config, but web02:7000 and web01:7000 instead.
Anze On Tuesday 03 August 2010, Willy Tarreau wrote: > Hi Nick, > > On Mon, Aug 02, 2010 at 11:13:29PM -0500, Nick Hilem wrote: > > I have HAProxy, 1.3.15, on the frontend of a few Ubuntu 9.04 instances > > with the following haproxy.cfg that are distributing to a couple > > apache/passenger instances. My problem is that if I... curl > > http://localhost/ > > It sits for awhile then returns a 504 Gateway Timeout. However if I... > > curl http://localhost:7000/ > > Which passenger is listening on, it returns fairly quickly with the page > > I would expect to see. > > That's kinda weird. One (unlikely) possibility would be that the server > responds differently when it does not see its port in the request. Could > you force it to see if it changes anything : > > curl -H "Host: localhost" http://localhost:7000/ > curl -H "Host: localhost:7000" http://localhost/ > > > I've also included the lsof results and hosts file on web01, everything > > is the same on web02. Anyone have any guess as to why my haproxy and > > passenger setup aren't talking to each other? Is my haproxy.cfg file > > misconfigured somehow? > > No, it looks fine. You don't even have "option httpclose", so that > means that the connection passes unmodified. > > Please run it in debug mode if you can (using -d) and check the output > for request/responses. Maybe we'll see something odd, but I have no > idea what. > > Also you could try to switch to "mode tcp" and see if that changes > anything. If so, that means that it blocks in the HTTP protocol. If > it does not work either, then it will be more likely a problem > handling the Host header. > > Regards, > Willy >
