com.xerox.amazonws.ec2.EC2Exception: Client error : AWS was not able to validate the provided access credentials

Atlassian JIRA | Zed Yap [Atlassian] | 5 years ago
  1. 0

    Currently, Bamboo will throw the following error in the log: {code} 2012-04-01 09:12:23,024 INFO [TP-Processor3] [AccessLogFilter] arjans GET https://bamboo.luminis.net/rest/api/latest/server?_=1333264343127 362321kb 2012-04-01 09:12:27,195 ERROR [elastic-pool-3-thread-1] [EBSVolumeManagerImpl] Could not retrieve volume descriptions. com.xerox.amazonws.ec2.EC2Exception: Client error : AWS was not able to validate the provided access credentials at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2006) at com.xerox.amazonws.ec2.Jec2.describeVolumes(Jec2.java:1511) at com.atlassian.aws.ec2.EBSVolumeManagerImpl.run(EBSVolumeManagerImpl.java:67) at com.atlassian.aws.ec2.UpdateSchedulerImpl.run(UpdateSchedulerImpl.java:45) 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) {code} +Steps to replicate the problem+ # Install a new fresh Bamboo # Login to Bamboo and direct your to Elastic configuration via _Bamboo Administration >> Elastic Bamboo >> Configuration_ # On the configuration page for elastic agent, do not fill in anything and just click on Save button # The exception will be throw # Disable the Elastic configuration +Workaround+ # Stop Bamboo # Find the administration.xml via _<bamboo home>\xml-data\configuration_ # Delete the tag including everything in between the following tag: {code} <elasticConfig> ...... </elasticConfig> {code} # Save the changes and restart Bamboo server *NOTE:* Please backup your administration.xml before you proceed with the deletion

    Atlassian JIRA | 5 years ago | Zed Yap [Atlassian]
    com.xerox.amazonws.ec2.EC2Exception: Client error : AWS was not able to validate the provided access credentials
  2. 0

    Currently, Bamboo will throw the following error in the log: {code} 2012-04-01 09:12:23,024 INFO [TP-Processor3] [AccessLogFilter] arjans GET https://bamboo.luminis.net/rest/api/latest/server?_=1333264343127 362321kb 2012-04-01 09:12:27,195 ERROR [elastic-pool-3-thread-1] [EBSVolumeManagerImpl] Could not retrieve volume descriptions. com.xerox.amazonws.ec2.EC2Exception: Client error : AWS was not able to validate the provided access credentials at com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2006) at com.xerox.amazonws.ec2.Jec2.describeVolumes(Jec2.java:1511) at com.atlassian.aws.ec2.EBSVolumeManagerImpl.run(EBSVolumeManagerImpl.java:67) at com.atlassian.aws.ec2.UpdateSchedulerImpl.run(UpdateSchedulerImpl.java:45) 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) {code} +Steps to replicate the problem+ # Install a new fresh Bamboo # Login to Bamboo and direct your to Elastic configuration via _Bamboo Administration >> Elastic Bamboo >> Configuration_ # On the configuration page for elastic agent, do not fill in anything and just click on Save button # The exception will be throw # Disable the Elastic configuration +Workaround+ # Stop Bamboo # Find the administration.xml via _<bamboo home>\xml-data\configuration_ # Delete the tag including everything in between the following tag: {code} <elasticConfig> ...... </elasticConfig> {code} # Save the changes and restart Bamboo server *NOTE:* Please backup your administration.xml before you proceed with the deletion

    Atlassian JIRA | 5 years ago | Zed Yap [Atlassian]
    com.xerox.amazonws.ec2.EC2Exception: Client error : AWS was not able to validate the provided access credentials
  3. Speed up your debug routine!

    Automated exception search integrated into your IDE

  4. 0

    Continuous "Loading" for a profile with error in the settings

    YouTrack | 7 years ago
    jetbrains.buildServer.clouds.amazon.AmazonCloudException: Unable to perform operation: Failed to fetch images. Client error : The AMI ID 'ami-00cee674' does not exist Amazon cloud error: Client error : The AMI ID 'ami-00cee674' does not exist
  5. 0

    '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}

    Atlassian JIRA | 7 years ago | Krystian Nowak
    com.xerox.amazonws.ec2.EC2Exception: Client error : The volume 'vol-b48c62dd' is not 'attached'.

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.xerox.amazonws.ec2.EC2Exception

      Client error : AWS was not able to validate the provided access credentials

      at com.xerox.amazonws.ec2.Jec2.makeRequestInt()
    2. com.xerox.amazonws
      Jec2.describeVolumes
      1. com.xerox.amazonws.ec2.Jec2.makeRequestInt(Jec2.java:2006)
      2. com.xerox.amazonws.ec2.Jec2.describeVolumes(Jec2.java:1511)
      2 frames
    3. com.atlassian.aws
      UpdateSchedulerImpl.run
      1. com.atlassian.aws.ec2.EBSVolumeManagerImpl.run(EBSVolumeManagerImpl.java:67)
      2. com.atlassian.aws.ec2.UpdateSchedulerImpl.run(UpdateSchedulerImpl.java:45)
      2 frames
    4. Java RT
      Thread.run
      1. java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
      2. java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
      3. java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
      4. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
      5. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
      6. java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
      7. java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
      8. java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
      9. java.lang.Thread.run(Thread.java:662)
      9 frames