com.atlassian.aws.AWSException: EC2 instance i-ea9ed400 in an unexpected state pending (0) for reason []

Atlassian JIRA | Martin Meinhold | 2 years ago
  1. 0

    Seen on the manage elastic instances page: {quote}Elastic Bamboo Error : EC2 Instance i-ea9ed400 is in an unrecognised state: UNKNOWN: Failure in EC2 instance i-ea9ed400. Attempting to terminate. {quote} I don't know what it means but it looks like something Bamboo should handle on its own - hence I've filed this bug report. Details stack trace from the system log entry is: {noformat} com.atlassian.aws.AWSException: EC2 instance i-ea9ed400 in an unexpected state pending (0) for reason [] at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.unexpectedStateException(RemoteEC2InstanceImpl.java:360) at com.atlassian.aws.ec2.EC2InstanceState.handleState(EC2InstanceState.java:207) at com.atlassian.aws.ec2.EC2InstanceState.access$100(EC2InstanceState.java:7) at com.atlassian.aws.ec2.EC2InstanceState$3.supervise(EC2InstanceState.java:75) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:503) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:39) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:112) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:83) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) {noformat} Happened on CBAC this morning (5.7.0 build 5714 - 05 Nov 14)

    Atlassian JIRA | 2 years ago | Martin Meinhold
    com.atlassian.aws.AWSException: EC2 instance i-ea9ed400 in an unexpected state pending (0) for reason []
  2. 0

    Seen on the manage elastic instances page: {quote}Elastic Bamboo Error : EC2 Instance i-ea9ed400 is in an unrecognised state: UNKNOWN: Failure in EC2 instance i-ea9ed400. Attempting to terminate. {quote} I don't know what it means but it looks like something Bamboo should handle on its own - hence I've filed this bug report. Details stack trace from the system log entry is: {noformat} com.atlassian.aws.AWSException: EC2 instance i-ea9ed400 in an unexpected state pending (0) for reason [] at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.unexpectedStateException(RemoteEC2InstanceImpl.java:360) at com.atlassian.aws.ec2.EC2InstanceState.handleState(EC2InstanceState.java:207) at com.atlassian.aws.ec2.EC2InstanceState.access$100(EC2InstanceState.java:7) at com.atlassian.aws.ec2.EC2InstanceState$3.supervise(EC2InstanceState.java:75) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:503) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:39) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:112) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:83) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) {noformat} Happened on CBAC this morning (5.7.0 build 5714 - 05 Nov 14)

    Atlassian JIRA | 2 years ago | Martin Meinhold
    com.atlassian.aws.AWSException: EC2 instance i-ea9ed400 in an unexpected state pending (0) for reason []
  3. 0

    I noticed the following exception in my logfile.. It doesnt appear to affect any other functionality, but you may want to clean this up {code} 2013-06-06 13:47:17,491 ERROR [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-10] [NamedThreadFactory] Uncaught exception in thread AtlassianEvent::0-BAM::EVENTS:pool-2-thread-10 java.lang.RuntimeException: com.atlassian.aws.AWSException: Could not create AWS account entity, no configuration details were found. Please configure you AWS credentials. at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:54) at com.atlassian.bamboo.event.spi.EventInvokerRunnable.run(EventInvokerRunnable.java:23) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at com.atlassian.bamboo.build.pipeline.concurrent.NamedThreadFactory$2.run(NamedThreadFactory.java:52) at java.lang.Thread.run(Unknown Source) Caused by: com.atlassian.util.concurrent.LazyReference$InitializationException: com.atlassian.aws.AWSException: Could not create AWS account entity, no configuration details were found. Please configure you AWS credentials. at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:152) at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:115) at com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:89) at com.atlassian.bamboo.agent.elastic.aws.AwsAccountBeanImpl.getAwsAccount(AwsAccountBeanImpl.java:92) at com.atlassian.bamboo.v2.events.HandleElasticInstancesFromPreviousSession.onServerStarted(HandleElasticInstancesFromPreviousSession.java:43) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:36) ... 5 more Caused by: com.atlassian.aws.AWSException: Could not create AWS account entity, no configuration details were found. Please configure you AWS credentials. at com.atlassian.bamboo.agent.elastic.aws.AwsAccountBeanImpl$1.create(AwsAccountBeanImpl.java:42) at com.atlassian.bamboo.agent.elastic.aws.AwsAccountBeanImpl$1.create(AwsAccountBeanImpl.java:34) at com.atlassian.util.concurrent.ResettableLazyReference$InternalReference.create(ResettableLazyReference.java:143) at com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:326) at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:146) ... 14 more {code}

    Atlassian JIRA | 4 years ago | Gary Donovan
    java.lang.RuntimeException: com.atlassian.aws.AWSException: Could not create AWS account entity, no configuration details were found. Please configure you AWS credentials.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    I noticed the following exception in my logfile.. It doesnt appear to affect any other functionality, but you may want to clean this up {code} 2013-06-06 13:47:17,491 ERROR [AtlassianEvent::0-BAM::EVENTS:pool-2-thread-10] [NamedThreadFactory] Uncaught exception in thread AtlassianEvent::0-BAM::EVENTS:pool-2-thread-10 java.lang.RuntimeException: com.atlassian.aws.AWSException: Could not create AWS account entity, no configuration details were found. Please configure you AWS credentials. at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:54) at com.atlassian.bamboo.event.spi.EventInvokerRunnable.run(EventInvokerRunnable.java:23) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at com.atlassian.bamboo.build.pipeline.concurrent.NamedThreadFactory$2.run(NamedThreadFactory.java:52) at java.lang.Thread.run(Unknown Source) Caused by: com.atlassian.util.concurrent.LazyReference$InitializationException: com.atlassian.aws.AWSException: Could not create AWS account entity, no configuration details were found. Please configure you AWS credentials. at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:152) at com.atlassian.util.concurrent.LazyReference.get(LazyReference.java:115) at com.atlassian.util.concurrent.ResettableLazyReference.get(ResettableLazyReference.java:89) at com.atlassian.bamboo.agent.elastic.aws.AwsAccountBeanImpl.getAwsAccount(AwsAccountBeanImpl.java:92) at com.atlassian.bamboo.v2.events.HandleElasticInstancesFromPreviousSession.onServerStarted(HandleElasticInstancesFromPreviousSession.java:43) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.atlassian.event.internal.SingleParameterMethodListenerInvoker.invoke(SingleParameterMethodListenerInvoker.java:36) ... 5 more Caused by: com.atlassian.aws.AWSException: Could not create AWS account entity, no configuration details were found. Please configure you AWS credentials. at com.atlassian.bamboo.agent.elastic.aws.AwsAccountBeanImpl$1.create(AwsAccountBeanImpl.java:42) at com.atlassian.bamboo.agent.elastic.aws.AwsAccountBeanImpl$1.create(AwsAccountBeanImpl.java:34) at com.atlassian.util.concurrent.ResettableLazyReference$InternalReference.create(ResettableLazyReference.java:143) at com.atlassian.util.concurrent.LazyReference$Sync.run(LazyReference.java:326) at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:146) ... 14 more {code}

    Atlassian JIRA | 4 years ago | Gary Donovan
    java.lang.RuntimeException: com.atlassian.aws.AWSException: Could not create AWS account entity, no configuration details were found. Please configure you AWS credentials.

    Root Cause Analysis

    1. com.atlassian.aws.AWSException

      EC2 instance i-ea9ed400 in an unexpected state pending (0) for reason []

      at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.unexpectedStateException()
    2. com.atlassian.aws
      RemoteEC2InstanceImpl$CatchingRunnableDecorator.run
      1. com.atlassian.aws.ec2.RemoteEC2InstanceImpl.unexpectedStateException(RemoteEC2InstanceImpl.java:360)
      2. com.atlassian.aws.ec2.EC2InstanceState.handleState(EC2InstanceState.java:207)
      3. com.atlassian.aws.ec2.EC2InstanceState.access$100(EC2InstanceState.java:7)
      4. com.atlassian.aws.ec2.EC2InstanceState$3.supervise(EC2InstanceState.java:75)
      5. com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:503)
      6. com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:39)
      7. com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:112)
      8. com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:83)
      8 frames
    3. Java RT
      Thread.run
      1. java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
      2. java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
      3. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
      4. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
      5. java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
      6. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
      7. java.lang.Thread.run(Thread.java:745)
      7 frames