• Community
  • Products
  • Bamboo
  • Questions
  • Getting the exception "Elastic Bamboo Error : EC2 Instance i-84c0a7e6 is in an unrecognised state: UNKNOWN: Failure in EC2 instance i-84c0a7e6. Attempting to terminate.

Getting the exception "Elastic Bamboo Error : EC2 Instance i-84c0a7e6 is in an unrecognised state: UNKNOWN: Failure in EC2 instance i-84c0a7e6. Attempting to terminate.

Venkat Raman January 3, 2012

We have a build plan that has been configured and it ran successfully. Now it is throwing the below exception and the instances has got terminated.

What could be the reason and how should we address the same.

com.xerox.amazonws.ec2.EC2Exception: The host did not accept the connection within timeout of 30000 ms

at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2012)

at com.xerox.amazonws.ec2.Jec2.describeInstances(Jec2.java:691)

at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.describeInstance(RemoteEC2InstanceImpl.java:292)

at com.atlassian.aws.ec2.EC2InstanceState$2.supervise(EC2InstanceState.java:77)

at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:441)

at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:25)

at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:127)

at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:98)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)

at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)

at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

at java.lang.Thread.run(Thread.java:662)

Caused by: org.apache.commons.httpclient.ConnectTimeoutException: The host did not accept the connection within timeout of 30000 ms

at org.apache.commons.httpclient.protocol.ControllerThreadSocketFactory.createSocket(ControllerThreadSocketFactory.java:96)

at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:127)

at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)

at org.apache.commons.httpclient.MultiThreadedHttpConnectionManager$HttpConnectionAdapter.open(MultiThreadedHttpConnectionManager.java:1321)

at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:386)

at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:170)

at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)

at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)

at com.xerox.amazonws.common.AWSQueryConnection.makeRequest(AWSQueryConnection.java:403)

at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2004)

... 16 more

1 answer

0 votes
James Dumay
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 5, 2012

That might be a bug. Could you file an issue with our support team? They can help you to try to fix this.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events