Bamboo 2.2 : Troubleshooting Elastic Bamboo
This page last changed on Mar 09, 2009 by ukuhnhardt.
This page contains troubleshooting tips for configuring and using Elastic Bamboo. EBS Volumes and SnapshotsElastic Agent does not mount a Volume to my Elastic InstanceWhat happensWhen an Elastic Bamboo is configured to use an EBS snapshot the elastic agent will mount an EBS-volume that has been created before to the elastic instance. This volume will be populated with the contents of a snapshot. snapshot 1 ---- * Volume Your AWS account lets you limit the maximum number {N} of volumes available. If not enough volumes are available, i.e. are ready to mount, the elastic agent will not succeed to mount a volume to the elastic instance and will use the default bamboo agent home directory that will be empty after startup. The instance will still work but you will experience longer build times... Looking at your aws console will reveal some volumes that are linked to a snapshot but are not attached to an instance for example i-b626b6df:/dev/sdh (attached). You will have 'dangling' volumes associated with snapshots that are still 'in use' and cannot be used by other elastic instances.
DiagnosisAccess your elastic instance via ssh and view the /tmp/setupEbsSnapshot.log file for any details. SolutionFree up your accounts capacity by deleting some volumes that are not mounted to any active instance. |
![]() |
Document generated by Confluence on Mar 09, 2009 17:07 |