ELB with OutOfService instances

[Eliomar Gomes campos]

I'm trying to configure ELB, but the instances remain OutOfService. What procedure do I need to let them InService?

[root@frontend Downloads]# eulb-describe-instance-health loadbalancer

INSTANCE i-A05B431F OutOfService

INSTANCE i-B0223F33 OutOfService

follows the log:

root@ip-172-31-254-93 ~]# tail -16 /var/log/load-balancer-servo/servo.log

failed to query the elb service: BotoServerError: 403 Forbidden

<?xml version="1.0"?><Response><Errors><Error><Code>403 Forbidden</Code><Message>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:11</Message></Error></Errors><RequestID>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:11</RequestID></Response>

failed to find the loadbalancers

403 Forbidden

<?xml version="1.0"?><Response><Errors><Error><Code>403 Forbidden</Code><Message>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:11</Message></Error></Errors><RequestID>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:11</RequestID></Response>

failed to report the cloudwatch metrics: BotoServerError: 403 Forbidden

<?xml version="1.0"?><Response><Errors><Error><Code>403 Forbidden</Code><Message>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:11</Message></Error></Errors><RequestID>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:11</RequestID></Response>

403 Forbidden

<?xml version="1.0"?><Response><Errors><Error><Code>403 Forbidden</Code><Message>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:21</Message></Error></Errors><RequestID>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:21</RequestID></Response>

failed to query the elb service: BotoServerError: 403 Forbidden

<?xml version="1.0"?><Response><Errors><Error><Code>403 Forbidden</Code><Message>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:21</Message></Error></Errors><RequestID>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:21</RequestID></Response>

failed to find the loadbalancers

403 Forbidden

<?xml version="1.0"?><Response><Errors><Error><Code>403 Forbidden</Code><Message>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:21</Message></Error></Errors><RequestID>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:21</RequestID></Response>

failed to report the cloudwatch metrics: BotoServerError: 403 Forbidden

<?xml version="1.0"?><Response><Errors><Error><Code>403 Forbidden</Code><Message>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:21</Message></Error></Errors><RequestID>Message has expired (times in UTC): Timestamp=null Expires=null Deadline=2014-10-23T18:00:21</RequestID></Response>

[root@ip-172-31-254-93 ~]# 

[Tony Beckham]

Hello,

I would start by checking security group rules and connectivity to the instances themselves.

1. Do the security group(s) of the instances registered to the load balancer allow for the port that you are performing your healthcheck on?

2. Are you able to reach the instances that you are registering to the LB directly on the port and protocol for what your ELB healthcheck is configured?

3. Same question as #2 but can you reach the instances on the port and service that your listener is configured for? 

3. Can you show the outputs of "euca--describe--load-balancers loadbalancer --show-long" and "eulb-describe-instance-health loadbalancer --show-long"

--

Tony

--
You received this message because you are subscribed to the Google Groups "Eucalyptus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to euca-users+...@eucalyptus.com.
To post to this group, send email to euca-...@eucalyptus.com.
Visit this group at http://groups.google.com/a/eucalyptus.com/group/euca-users/.

[Steve Jones]

You might need to configure NTP for the ELB instances, see:

https://www.eucalyptus.com/docs/eucalyptus/4.0.2/index.html#troubleshooting-guide/ts_elb.html

Steve

[Sang-min Park]

Hello,

Like Steve said, configuring the NTP will solve the problem. 

You need to terminate the loadbalancer VM in order for the change to take effect.

[Eliomar Gomes campos]

\o/ \o/ \o/ \o/ \o/ \o/ \o/  InService !!!!

root@frontend log]# eulb-describe-instance-health loadbalancer

INSTANCE i-39203D2E InService

INSTANCE i-684145BE InService

I did $ euca-modify-property -p loadbalancing.loadbalancer_vm_ntp_server=192.168.0.2  (My NTP server)

Thank you everyone!!!