Web Load Balancing (apache+heartbeat+ldirector) : Unable to connect to real servers
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
After accessing my VIP first time following is the output:
root@loadb1:~# ipvsadm -Ln
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 67.23.10.160:80 rr
-> 10.176.46.93:80 Route 1 0 0
-> 10.176.46.92:80 Route 1 0 1
After 2nd access output is:
root@loadb1:~# ipvsadm -Ln
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 67.23.10.160:80 rr
-> 10.176.46.93:80 Route 1 0 1
-> 10.176.46.92:80 Route 1 0 1
That means ldirectord receiving http connections and sending them to real servers. I am unable to understand where is the problem ? can any body help me ?
Maybe silly question but did you configure the real servers (the apache nodes) to listen on the virtual IP on the loopback interface? If you didn't configure the nodes to listen on that IP than they will not accept connections from the load balancer. The IP gets send along in the HTTP header as far as I know and if the node doesn't listen on that IP than you get no response although the load balancer detects it as being 'alive'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.