up vote 1 down vote favorite
1
share [g+] share [fb]

I am having problems configuring ELB for my servers.

I start 2 micro instances with the exact same conf and try to do Load Balancing. However they never pass the health check (HTTP port 80 path:"/").

  • Ping is ok on the website. So is telnet on 80.

How did the health check works? Am I doing anything really wrong?

EDIT:

  • Both Direct browser access and GET (via curl) works correctly (status 200)
link|improve this question
1  
I have the same problem. I just have it checking TCP:80 as an interim solution (which works fine). – datagramm Nov 24 '11 at 17:05
It worked! Thanks! But I still dont know how the health check works .. :( Can you write an answer so I can check it as accepted? – diegodias Nov 24 '11 at 17:25
feedback

4 Answers

up vote 1 down vote accepted

I have the same problem. I just have it checking TCP:80 as an interim solution (which works fine).

link|improve this answer
feedback
up vote 1 down vote

I've come to the conclusion that the response, apart from being a HTTP 200 response, must contain certain headers. I've had a HTTP 200 returned from my tomcat server running on the instance not work, but a static html page served by httpd (also returning a 200 code) work fine. Looking at the headers, one of the few differences was that the tomcat one didn't contain the content-type. Not sure why that would make a difference, though.

link|improve this answer
feedback
up vote 0 down vote

I assume it performs an HTTP GET request to the specified path "/", of each of the servers and looks for a successful HTTP response code (200). Can you successfully make a GET request to http://<backend_server_IP>:80/ via a browser (or CLI tool such as wget or curl).

If the request is served successfully, the second thing to ask is: have you configured your servers' security group so that access to port 80 is limited to a particular source address or subnet? If so, you need to add ELB's security group to the filter. The group is always called:

amazon-elb/amazon-elb-sg

So you can just add this under the 'Source' field in the Security Groups section of the AWS Console.

link|improve this answer
The port 80 is open to the world (0.0.0.0/0). Both direct browser access and curl works correctly (200) – diegodias Nov 24 '11 at 13:34
Are the webservers bound only to the public IP/domain? I assume ELB uses the internal (private) IPs so that no external bandwidth is used. Can you successfully make a request from one of your Amazon instances to http://<private_IP>:80/ If so then I'm out of ideas! – James Little Nov 24 '11 at 14:22
It was not accessible working with the internal IP. I changed it, its now working, but the health check still not passing. – diegodias Nov 24 '11 at 16:32
feedback
up vote 0 down vote

so i've just got the http check to work by pointing it at a static html file (as opposed to a php page).

'/' does not work despite it returning a valid http status when using curl, etc. '/file.html' does however pass the health check.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.