Hi, You definitively need to enable logs in your HAProxy configuration! How do you want to troubleshoot without it???
Are you sure haproxy is running and has bound port 80? I mean, maybe an other process has bound this port and is handling traffic instead of HAProxy. good luck On Mon, Dec 12, 2011 at 7:57 PM, Avinash <avinash.anan...@gmail.com> wrote: > Hi, > > We have a Linux machine on which are installed 2 servers (tomcat @ 8080, > lighthttpd @ 8081). I am using HAProxy ( @ 80 ) to perform domain base > routing to these servers. > > After a reboot, we restarted the apps(haproxy, lighthttpd, tomcat) and found > that haproxy is no longer able to perform routing. Before reboot things were > working fine and we did not perform any config/software changes from our > end. > > Here are our haproxy settings : > > frontend http_proxy > bind 10.211.154.49:80 > option forwardfor > acl is_resource hdr_dom(host) -i resource.qureka.com > acl is_app hdr_dom(host) -i www.qureka.com > use_backend resource_cluster if is_resource > use_backend app_cluster if is_app > > backend resource_cluster > server server1 127.0.0.1:8081 > > backend app_cluster > server server1 127.0.0.1:8080 > > Here are the logs on haproxy start : > Dec 11 12:56:43 localhost haproxy6655: Proxy http_proxy started. > Dec 11 12:56:43 localhost haproxy6655: Proxy resource_cluster started. > Dec 11 12:56:43 localhost haproxy6655: Proxy app_cluster started. > > Example url : > standalone lighthttp url > : http://resource.qureka.com:8081/qureka/static/1331/qRev/images/Processing.gifworking > lighthttpd through proxy > : http://resource.qureka.com/qureka/static/1331/qRev/images/Processing.gif not > working > > For reference, > > HAProxy is on port 80. > LightHttpd Server is on port 8081. > > HAproxy is supposed to forward request to light httpd if request contains > "resource.qureka.com". But that is not happening. It worked before the > reboot with the same config. Also since logging isn't happening, we are > clueless and are unable to move further to solve this issue. > > It would be great if we could get some help on how to troubleshoot this > issue further.
