Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-11382

Bamboo throw exception to the log every minutes when Elastic configuration is not configure correctly

    XMLWordPrintable

Details

    Description

      Currently, Bamboo will throw the following error in the log:

      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)

      Steps to replicate the problem

      1. Install a new fresh Bamboo
      2. Login to Bamboo and direct your to Elastic configuration via Bamboo Administration >> Elastic Bamboo >> Configuration
      3. On the configuration page for elastic agent, do not fill in anything and just click on Save button
      4. The exception will be throw
      5. Disable the Elastic configuration

      Workaround

      1. Stop Bamboo
      2. Find the administration.xml via <bamboo home>\xml-data\configuration
      3. Delete the tag including everything in between the following tag: 
        <elasticConfig>
......
</elasticConfig>
      4. Save the changes and restart Bamboo server

      NOTE: Please backup your administration.xml before you proceed with the deletion

      Attachments

        Activity

          People

            Unassigned Unassigned
            zyap Zed Yap [Atlassian]
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: