Hey Arie, You can download the command line tools from AWS to check the health of your balancers. http://developer.amazonwebservices.com/connect/entry.jspa?externalID=2536&categoryID=88
Also, I've noticed that Scalr only adds new instances to the ELB, so if the instance was around before the ELB was set up, you may need to terminate it and spin up a new one. Lastly, It would be helpful if Scalr gave the option to add/remove instances from the ELB, like it does for DNS zones. On Oct 10, 4:12 am, Arie Fishler <[email protected]> wrote: > Hi, > > It seems there is a real issue with the Elastic LB via scalr. I have farm > 1216 with 2 instances configured to use an Elastic LB. > > They are both live and healthy. I access them separately. I have elastic LB > access when both are up. I wanted to test the switch to another instance so > took the one I was connected to down. > > I waited and waited and waited and I have no more access through my app URL. > It looks like the other instance is not responding through the load > balancer. > > Is there a way to check the status of the ELB? I haven't seen something on > the AWS management console. There is no way for me to know what is the ELB > "seeing". Can it be that the other instance was not properly registered on > the ELB via scalr? > > Thanks, > Arie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
