com.xerox.amazonws.ec2.EC2Exception

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • 've just switched from M6 to M7. I've spotted a problem that somehow M7 (compared to M6) seems too eagerly mark remote agents as "offline" and in result it shuts them down - about 5-10 per 4-5 hours. I've logged in to each of "offline" instances before they went down, but in elastic agent's logs there was nothing suspicious and it seems it was connecting fine with SSH tunnelled connection back to the master. Do you know if any additional functionality (apart from official fix for-s for M7 - [http://jira.atlassian.com/browse/BAM/fixforversion/14643]) were added so that they can introduce this kind of behaviour - compared to M6? I've noticed that if the elastic agent is marked as "offline" it happens just after a build is completed on this agent (of course it doesn't happen after every completed build). Nothing weird happened in Bamboo master's logs and the only sign of the node being put down is simply: {noformat} 2009-06-26 06:31:57,120 INFO [pool-2-thread-1] [ElasticInstanceManagerImpl] Elastic instance i-c3fedfaa transitioned from RUNNING to SHUTTING_DOWN. 2009-06-26 06:31:57,293 INFO [pool-2-thread-1] [RemoteEC2InstanceImpl] EC2 instance i-c3fedfaa transitioned from running (16) to shutting-down (32) 2009-06-26 06:32:15,333 INFO [pool-2-thread-3] [RemoteEC2InstanceImpl] EC2 instance i-c3fedfaa has terminated. 2009-06-26 06:32:15,333 INFO [pool-2-thread-3] [ElasticInstanceManagerImpl] Elastic instance i-c3fedfaa transitioned from SHUTTING_DOWN to TERMINATED. 2009-06-26 06:32:15,333 INFO [pool-2-thread-3] [ElasticInstanceManagerImpl] Detected that the elastic instance i-c3fedfaa has stopped. 2009-06-26 06:32:15,344 INFO [pool-2-thread-3] [ElasticInstanceManagerImpl] Elastic Agent "Elastic Agent on i-c3fedfaa" stopped on instance i-c3fedfaa 2009-06-26 06:32:15,345 INFO [pool-2-thread-3] [EBSVolumeSupervisorImpl] Deleting EBS volume vol-b48c62dd 2009-06-26 06:32:15,346 ERROR [pool-10-thread-1] [AgentOfflineEventListener] Elastic instance i-c3fedfaa does not exist 2009-06-26 06:32:15,412 WARN [pool-2-thread-3] [EBSVolumeImpl] Attempt to detach EBS volume vol-b48c62dd from EC2 instance i-c3fedfaa failed. Proceeding with deletion. com.xerox.amazonws.ec2.EC2Exception: Client error : The volume 'vol-b48c62dd' is not 'attached'. at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:1680) at com.xerox.amazonws.ec2.Jec2.detachVolume(Jec2.java:1569) at com.atlassian.aws.ec2.EBSVolumeImpl.delete(EBSVolumeImpl.java:38) at com.atlassian.bamboo.agent.elastic.server.EBSVolumeSupervisorImpl.purge(EBSVolumeSupervisorImpl.java:110) at com.atlassian.bamboo.agent.elastic.server.RemoteElasticInstanceImpl$1.ec2InstanceStateChanged(RemoteElasticInstanceImpl.java:291) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$4.run(RemoteEC2InstanceImpl.java:494) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:96) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.setState(RemoteEC2InstanceImpl.java:489) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.terminated(RemoteEC2InstanceImpl.java:325) at com.atlassian.aws.ec2.EC2InstanceState$3.supervise(EC2InstanceState.java:125) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:413) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:25) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:125) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:96) 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:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) {noformat}
    via by Krystian Nowak,
  • 've just switched from M6 to M7. I've spotted a problem that somehow M7 (compared to M6) seems too eagerly mark remote agents as "offline" and in result it shuts them down - about 5-10 per 4-5 hours. I've logged in to each of "offline" instances before they went down, but in elastic agent's logs there was nothing suspicious and it seems it was connecting fine with SSH tunnelled connection back to the master. Do you know if any additional functionality (apart from official fix for-s for M7 - [http://jira.atlassian.com/browse/BAM/fixforversion/14643]) were added so that they can introduce this kind of behaviour - compared to M6? I've noticed that if the elastic agent is marked as "offline" it happens just after a build is completed on this agent (of course it doesn't happen after every completed build). Nothing weird happened in Bamboo master's logs and the only sign of the node being put down is simply: {noformat} 2009-06-26 06:31:57,120 INFO [pool-2-thread-1] [ElasticInstanceManagerImpl] Elastic instance i-c3fedfaa transitioned from RUNNING to SHUTTING_DOWN. 2009-06-26 06:31:57,293 INFO [pool-2-thread-1] [RemoteEC2InstanceImpl] EC2 instance i-c3fedfaa transitioned from running (16) to shutting-down (32) 2009-06-26 06:32:15,333 INFO [pool-2-thread-3] [RemoteEC2InstanceImpl] EC2 instance i-c3fedfaa has terminated. 2009-06-26 06:32:15,333 INFO [pool-2-thread-3] [ElasticInstanceManagerImpl] Elastic instance i-c3fedfaa transitioned from SHUTTING_DOWN to TERMINATED. 2009-06-26 06:32:15,333 INFO [pool-2-thread-3] [ElasticInstanceManagerImpl] Detected that the elastic instance i-c3fedfaa has stopped. 2009-06-26 06:32:15,344 INFO [pool-2-thread-3] [ElasticInstanceManagerImpl] Elastic Agent "Elastic Agent on i-c3fedfaa" stopped on instance i-c3fedfaa 2009-06-26 06:32:15,345 INFO [pool-2-thread-3] [EBSVolumeSupervisorImpl] Deleting EBS volume vol-b48c62dd 2009-06-26 06:32:15,346 ERROR [pool-10-thread-1] [AgentOfflineEventListener] Elastic instance i-c3fedfaa does not exist 2009-06-26 06:32:15,412 WARN [pool-2-thread-3] [EBSVolumeImpl] Attempt to detach EBS volume vol-b48c62dd from EC2 instance i-c3fedfaa failed. Proceeding with deletion. com.xerox.amazonws.ec2.EC2Exception: Client error : The volume 'vol-b48c62dd' is not 'attached'. at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:1680) at com.xerox.amazonws.ec2.Jec2.detachVolume(Jec2.java:1569) at com.atlassian.aws.ec2.EBSVolumeImpl.delete(EBSVolumeImpl.java:38) at com.atlassian.bamboo.agent.elastic.server.EBSVolumeSupervisorImpl.purge(EBSVolumeSupervisorImpl.java:110) at com.atlassian.bamboo.agent.elastic.server.RemoteElasticInstanceImpl$1.ec2InstanceStateChanged(RemoteElasticInstanceImpl.java:291) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$4.run(RemoteEC2InstanceImpl.java:494) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:96) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.setState(RemoteEC2InstanceImpl.java:489) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.terminated(RemoteEC2InstanceImpl.java:325) at com.atlassian.aws.ec2.EC2InstanceState$3.supervise(EC2InstanceState.java:125) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:413) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:25) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:125) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:96) 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:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) {noformat}
    via by Krystian Nowak,
  • EBS volumes cannot be detached/deleted when instances are shut down by the cron scheduler. {panel} INFO | jvm 1 | 2009/08/24 07:40:00 | 2009-08-24 07:40:00,006 INFO [QuartzScheduler_Worker-6] [ElasticFunctionalityFacadeImpl] Adjusting elastic agents with schedule: com.atlassian.bamboo.agent.elastic.schedule.ElasticInstanceScheduleImpl@26e492[25886722,0 40 7 ? * MON-FRI,<null>,EQUALS,0,true] INFO | jvm 1 | 2009/08/24 07:40:00 | 2009-08-24 07:40:00,006 INFO [QuartzScheduler_Worker-6] [ElasticFunctionalityFacadeImpl] Adjusting all elastic instance... INFO | jvm 1 | 2009/08/24 07:40:00 | 2009-08-24 07:40:00,023 INFO [QuartzScheduler_Worker-6] [ElasticFunctionalityFacadeImpl] Attempting to shutdown 1 of 'Default' elastic instances INFO | jvm 1 | 2009/08/24 07:40:01 | 2009-08-24 07:40:01,264 INFO [BAM::Events:pool-1-thread-13] [ElasticInstanceManagerImpl] Elastic Agent "Elastic Agent on i-6ad13f02" stopped on instance i-6ad13f02 INFO | jvm 1 | 2009/08/24 07:40:01 | 2009-08-24 07:40:01,277 INFO [pool-3-thread-3] [ElasticInstanceManagerImpl] Elastic instance i-6ad13f02 transitioned from RUNNING to SHUTTING_DOWN. INFO | jvm 1 | 2009/08/24 07:40:01 | 2009-08-24 07:40:01,287 INFO [BAM::Events:pool-1-thread-7] [ElasticInstanceManagerImpl] Elastic Agent "Elastic Agent on i-6ad13f02" stopped on instance i-6ad13f02 INFO | jvm 1 | 2009/08/24 07:40:01 | 2009-08-24 07:40:01,632 INFO [pool-3-thread-3] [RemoteEC2InstanceImpl] EC2 instance i-6ad13f02 transitioned from running (16) to shutting-down (32) INFO | jvm 1 | 2009/08/24 07:40:01 | 2009-08-24 07:40:01,633 INFO [BAM::Events:pool-1-thread-7] [ElasticInstanceManagerImpl] Requested termination of elastic instance: i-6ad13f02 INFO | jvm 1 | 2009/08/24 07:40:01 | 2009-08-24 07:40:01,633 INFO [BAM::Events:pool-1-thread-13] [ElasticInstanceManagerImpl] Requested termination of elastic instance: i-6ad13f02 INFO | jvm 1 | 2009/08/24 07:40:25 | 2009-08-24 07:40:25,833 INFO [pool-3-thread-3] [RemoteEC2InstanceImpl] EC2 instance i-6ad13f02 has terminated. INFO | jvm 1 | 2009/08/24 07:40:25 | 2009-08-24 07:40:25,833 INFO [pool-3-thread-3] [ElasticInstanceManagerImpl] Elastic instance i-6ad13f02 transitioned from SHUTTING_DOWN to TERMINATED. INFO | jvm 1 | 2009/08/24 07:40:25 | 2009-08-24 07:40:25,833 INFO [pool-3-thread-3] [ElasticInstanceManagerImpl] Detected that the elastic instance i-6ad13f02 has stopped. INFO | jvm 1 | 2009/08/24 07:40:25 | 2009-08-24 07:40:25,836 INFO [pool-3-thread-3] [EBSVolumeSupervisorImpl] Deleting EBS volume vol-c90ffaa0 INFO | jvm 1 | 2009/08/24 07:40:26 | 2009-08-24 07:40:26,036 WARN [pool-3-thread-3] [EBSVolumeImpl] Attempt to detach EBS volume vol-c90ffaa0 from EC2 instance i-6ad13f02 failed. Proceeding with deletion. INFO | jvm 1 | 2009/08/24 07:40:26 | com.xerox.amazonws.ec2.EC2Exception: Client error : The volume 'vol-c90ffaa0' is not 'attached'. INFO | jvm 1 | 2009/08/24 07:40:26 | at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:1680) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.xerox.amazonws.ec2.Jec2.detachVolume(Jec2.java:1569) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.EBSVolumeImpl.delete(EBSVolumeImpl.java:38) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.bamboo.agent.elastic.server.EBSVolumeSupervisorImpl.purge(EBSVolumeSupervisorImpl.java:119) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.bamboo.agent.elastic.server.RemoteElasticInstanceImpl$1.ec2InstanceStateChanged(RemoteElasticInstanceImpl.java:307) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$4.run(RemoteEC2InstanceImpl.java:518) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:98) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.setState(RemoteEC2InstanceImpl.java:513) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.terminated(RemoteEC2InstanceImpl.java:346) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.EC2InstanceState$3.supervise(EC2InstanceState.java:125) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:437) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:25) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:127) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:98) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.lang.Thread.run(Thread.java:619) {panel}
    via by Ulrich Kuhnhardt [Atlassian],
  • EBS volumes cannot be detached/deleted when instances are shut down by the cron scheduler. {panel} INFO | jvm 1 | 2009/08/24 07:40:00 | 2009-08-24 07:40:00,006 INFO [QuartzScheduler_Worker-6] [ElasticFunctionalityFacadeImpl] Adjusting elastic agents with schedule: com.atlassian.bamboo.agent.elastic.schedule.ElasticInstanceScheduleImpl@26e492[25886722,0 40 7 ? * MON-FRI,<null>,EQUALS,0,true] INFO | jvm 1 | 2009/08/24 07:40:00 | 2009-08-24 07:40:00,006 INFO [QuartzScheduler_Worker-6] [ElasticFunctionalityFacadeImpl] Adjusting all elastic instance... INFO | jvm 1 | 2009/08/24 07:40:00 | 2009-08-24 07:40:00,023 INFO [QuartzScheduler_Worker-6] [ElasticFunctionalityFacadeImpl] Attempting to shutdown 1 of 'Default' elastic instances INFO | jvm 1 | 2009/08/24 07:40:01 | 2009-08-24 07:40:01,264 INFO [BAM::Events:pool-1-thread-13] [ElasticInstanceManagerImpl] Elastic Agent "Elastic Agent on i-6ad13f02" stopped on instance i-6ad13f02 INFO | jvm 1 | 2009/08/24 07:40:01 | 2009-08-24 07:40:01,277 INFO [pool-3-thread-3] [ElasticInstanceManagerImpl] Elastic instance i-6ad13f02 transitioned from RUNNING to SHUTTING_DOWN. INFO | jvm 1 | 2009/08/24 07:40:01 | 2009-08-24 07:40:01,287 INFO [BAM::Events:pool-1-thread-7] [ElasticInstanceManagerImpl] Elastic Agent "Elastic Agent on i-6ad13f02" stopped on instance i-6ad13f02 INFO | jvm 1 | 2009/08/24 07:40:01 | 2009-08-24 07:40:01,632 INFO [pool-3-thread-3] [RemoteEC2InstanceImpl] EC2 instance i-6ad13f02 transitioned from running (16) to shutting-down (32) INFO | jvm 1 | 2009/08/24 07:40:01 | 2009-08-24 07:40:01,633 INFO [BAM::Events:pool-1-thread-7] [ElasticInstanceManagerImpl] Requested termination of elastic instance: i-6ad13f02 INFO | jvm 1 | 2009/08/24 07:40:01 | 2009-08-24 07:40:01,633 INFO [BAM::Events:pool-1-thread-13] [ElasticInstanceManagerImpl] Requested termination of elastic instance: i-6ad13f02 INFO | jvm 1 | 2009/08/24 07:40:25 | 2009-08-24 07:40:25,833 INFO [pool-3-thread-3] [RemoteEC2InstanceImpl] EC2 instance i-6ad13f02 has terminated. INFO | jvm 1 | 2009/08/24 07:40:25 | 2009-08-24 07:40:25,833 INFO [pool-3-thread-3] [ElasticInstanceManagerImpl] Elastic instance i-6ad13f02 transitioned from SHUTTING_DOWN to TERMINATED. INFO | jvm 1 | 2009/08/24 07:40:25 | 2009-08-24 07:40:25,833 INFO [pool-3-thread-3] [ElasticInstanceManagerImpl] Detected that the elastic instance i-6ad13f02 has stopped. INFO | jvm 1 | 2009/08/24 07:40:25 | 2009-08-24 07:40:25,836 INFO [pool-3-thread-3] [EBSVolumeSupervisorImpl] Deleting EBS volume vol-c90ffaa0 INFO | jvm 1 | 2009/08/24 07:40:26 | 2009-08-24 07:40:26,036 WARN [pool-3-thread-3] [EBSVolumeImpl] Attempt to detach EBS volume vol-c90ffaa0 from EC2 instance i-6ad13f02 failed. Proceeding with deletion. INFO | jvm 1 | 2009/08/24 07:40:26 | com.xerox.amazonws.ec2.EC2Exception: Client error : The volume 'vol-c90ffaa0' is not 'attached'. INFO | jvm 1 | 2009/08/24 07:40:26 | at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:1680) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.xerox.amazonws.ec2.Jec2.detachVolume(Jec2.java:1569) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.EBSVolumeImpl.delete(EBSVolumeImpl.java:38) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.bamboo.agent.elastic.server.EBSVolumeSupervisorImpl.purge(EBSVolumeSupervisorImpl.java:119) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.bamboo.agent.elastic.server.RemoteElasticInstanceImpl$1.ec2InstanceStateChanged(RemoteElasticInstanceImpl.java:307) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$4.run(RemoteEC2InstanceImpl.java:518) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:98) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.setState(RemoteEC2InstanceImpl.java:513) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.terminated(RemoteEC2InstanceImpl.java:346) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.EC2InstanceState$3.supervise(EC2InstanceState.java:125) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:437) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:25) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:127) INFO | jvm 1 | 2009/08/24 07:40:26 | at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:98) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:181) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) INFO | jvm 1 | 2009/08/24 07:40:26 | at java.lang.Thread.run(Thread.java:619) {panel}
    via by Ulrich Kuhnhardt [Atlassian],
  • I tried to add node and got error like this. {noformat} Launching ami-1a077948 ERROR: Client error : The requested instance type's architecture (i386) does not match the architecture in the manifest for ami-1a077948 (x86_64) com.xerox.amazonws.ec2.EC2Exception: Client error : The requested instance type's architecture (i386) does not match the architecture in the manifest for ami-1a077948 (x86_64) at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2006) at com.xerox.amazonws.ec2.Jec2.runInstances(Jec2.java:573) at com.xerox.amazonws.ec2.Jec2.runInstances(Jec2.java:509) at com.xerox.amazonws.ec2.Jec2.runInstances(Jec2.java:463) at com.xerox.amazonws.ec2.Jec2.runInstances(Jec2.java:437) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:119) at hudson.plugins.ec2.EC2Cloud.doProvision(EC2Cloud.java:185) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:102) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:562) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:640) at org.kohsuke.stapler.MetaClass$7.doDispatch(MetaClass.java:242) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:562) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:640) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:478) at org.kohsuke.stapler.Stapler.service(Stapler.java:160) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:249) at winstone.RequestDispatcher.forward(RequestDispatcher.java:335) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86) at winstone.FilterConfiguration.execute(FilterConfiguration.java:195) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:195) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:195) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:195) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:244) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.lang.Thread.run(Thread.java:662) {noformat}
    via by Masaki Muranaka,
  • When using the ec2-plugin, we configured a connection to EC2 as well as a Eucalyptus cloud. When we tried some operations on the Eucalyptus cloud (specifically looking at logs of an instance or terminating an instance), we get an error; Jan 25, 2012 9:44:17 AM hudson.plugins.ec2.EC2Slave terminate WARNING: Failed to terminate EC2 instance: i-CCA241AF com.xerox.amazonws.ec2.EC2Exception: Client error : The instance ID 'i-cca241af' does not exist at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2359) at com.xerox.amazonws.ec2.Jec2.terminateInstances(Jec2.java:776) at hudson.plugins.ec2.EC2Slave.terminate(EC2Slave.java:95) at hudson.plugins.ec2.EC2Computer.doDoDelete(EC2Computer.java:103) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) Eucalyptus never generates this error message. I ran tests with euca2ools and typica to reproduce this error and supplying upper or lower case instance ids never caused this error to come back. Looking at the ec2-plugin code (EC2Cloud.java), there's a method get() which returns an EC2Cloud instance. The code will only retrieve a cloud of the class EC2Cloud which precluded having more than one cloud of that type registered. public static EC2Cloud get() { return Hudson.getInstance().clouds.get(EC2Cloud.class); } If the intention is to allow more than one cloud of a specific type to be used at the same time, this should be addressed.
    via by David Kavanagh,
  • Single EC2 error can disable a cloud image
    via by Unknown author,
    • com.xerox.amazonws.ec2.EC2Exception: Client error : The volume 'vol-b48c62dd' is not 'attached'. at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:1680) at com.xerox.amazonws.ec2.Jec2.detachVolume(Jec2.java:1569) at com.atlassian.aws.ec2.EBSVolumeImpl.delete(EBSVolumeImpl.java:38) at com.atlassian.bamboo.agent.elastic.server.EBSVolumeSupervisorImpl.purge(EBSVolumeSupervisorImpl.java:110) at com.atlassian.bamboo.agent.elastic.server.RemoteElasticInstanceImpl$1.ec2InstanceStateChanged(RemoteElasticInstanceImpl.java:291) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$4.run(RemoteEC2InstanceImpl.java:494) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:96) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.setState(RemoteEC2InstanceImpl.java:489) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.terminated(RemoteEC2InstanceImpl.java:325) at com.atlassian.aws.ec2.EC2InstanceState$3.supervise(EC2InstanceState.java:125) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.backgroundSupervise(RemoteEC2InstanceImpl.java:413) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl.access$300(RemoteEC2InstanceImpl.java:25) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$2.run(RemoteEC2InstanceImpl.java:125) at com.atlassian.aws.ec2.RemoteEC2InstanceImpl$CatchingRunnableDecorator.run(RemoteEC2InstanceImpl.java:96) 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:181) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:205) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    No Bugmate found.