Bamboo agents keep shutting down
Asked by Phill Price:

For some reason I have buids outstanding on a Bamboo Cloud account that were working fine up until 30 minutes ago. Now I have one instance in shutting down mode (still there) and manually starting others results in them shutting down.

No changes have been made to the instance start script, which worked up until now. Logs for each instance don't hang around to spot if somethings changed to stop them working.

```
Sep 23, 2015 4:28:43 PM Currently there are no agents that can build: NMP2-BUIL-JOB1. New elastic instance(s) will be started (providing the configuration allows it).Sep 23, 2015 4:28:43 PM 1 elastic instance(s) will be started for those builds that cannot be build on currently connected agents.Sep 23, 2015 4:28:43 PM Requested that new elastic instance be created for configuration: Amazon Linux stock image / ami-895b80e2Sep 23, 2015 4:28:44 PM Elastic instance [i-1f3316bc] transitioned from STARTING to IDENTIFIED.Sep 23, 2015 4:33:47 PM Elastic instance [i-1f3316bc] transitioned from IDENTIFIED to SHUTTING_DOWN.Sep 23, 2015 4:36:29 PM Elastic instance [i-1f3316bc] transitioned from SHUTTING_DOWN to TERMINATED.Sep 23, 2015 4:36:29 PM Detected that the elastic instance [i-1f3316bc] has been terminated.Sep 23, 2015 4:36:43 PM Currently there are no agents that can build: NMP2-BUIL-JOB1. New elastic instance(s) will be started (providing the configuration allows it).Sep 23, 2015 4:36:43 PM 1 elastic instance(s) will be started for those builds that cannot be build on currently connected agents.Sep 23, 2015 4:36:43 PM Requested that new elastic instance be created for configuration: Amazon Linux stock image / ami-895b80e2Sep 23, 2015 4:36:44 PM Elastic instance [i-8a012429] transitioned from STARTING to IDENTIFIED.Sep 23, 2015 4:41:47 PM Elastic instance [i-8a012429] transitioned from IDENTIFIED to SHUTTING_DOWN.Sep 23, 2015 4:51:22 PM Requested that new elastic instance be created for configuration: Amazon Linux stock image / ami-895b80e2Sep 23, 2015 4:51:22 PM Requested that new elastic instance be created for configuration: Amazon Linux stock image / ami-895b80e2Sep 23, 2015 4:51:23 PM Elastic instance [i-4a193ce9] transitioned from STARTING to IDENTIFIED.Sep 23, 2015 4:51:23 PM Elastic instance [i-1b193cb8] transitioned from STARTING to IDENTIFIED.Sep 23, 2015 4:55:23 PM Elastic instance [i-4a193ce9] transitioned from IDENTIFIED to SHUTTING_DOWN.Sep 23, 2015 4:55:43 PM Elastic instance [i-1b193cb8] transitioned from IDENTIFIED to SHUTTING_DOWN.Sep 23, 2015 4:56:10 PM Requested that new elastic instance be created for configuration: Amazon Linux stock image / ami-895b80e2Sep 23, 2015 4:56:10 PM Elastic instance [i-35e1c496] transitioned from STARTING to IDENTIFIED.Sep 23, 2015 4:57:23 PM Elastic instance [i-4a193ce9] transitioned from SHUTTING_DOWN to TERMINATED.Sep 23, 2015 4:57:23 PM Detected that the elastic instance [i-4a193ce9] has been terminated.Sep 23, 2015 4:57:23 PM Elastic instance [i-1b193cb8] transitioned from SHUTTING_DOWN to TERMINATED.Sep 23, 2015 4:57:23 PM Detected that the elastic instance [i-1b193cb8] has been terminated.Sep 23, 2015 4:58:11 PM Elastic instance [i-35e1c496] transitioned from IDENTIFIED to SHUTTING_DOWN.Sep 23, 2015 4:58:31 PM Elastic instance [i-35e1c496] transitioned from SHUTTING_DOWN to TERMINATED.Sep 23, 2015 4:58:31 PM Detected that the elastic instance [i-35e1c496] has been terminated.
```


Answers:
author: Andy Norris
body: I wonder if it might be an Amazon issue?

<http://status.aws.amazon.com/>


Tags: cloud