Elastic Agent goes offline during a build

[James Gustard]

Hi,

I have set up an on demand build plan, with an elastic agent that starts up on demand when the bamboo build queue, using passive instance managment. I have run 3 builds and 2 of them have have failed with the error

[MY BUILD NAME]: Agent 'Elastic Agent on i-52e8c135' went offline while building JOB-12. The build results will not be saved.

I cant see any logs.

The agent should stay online until the build has finised and the idle time has passed, but it seem to just shut down randomly. How can I fix this?

[Przemek Bruski · Accepted solution]

Random agent shutdowns plaguing OnDemand users should be gone after the update performed last week.

[EddieW]

We're seeing this on our internal bamboo instance with remote agents. Is there a corresponding issue/fix in bamboo 5.x ?

[karthikys]

We are being hit by the same issue in Bamboo 5.4.1. Is there a fix ??

[Jonas]

We are seeing this on bamboo (server) ver 6.9.2, did anyone find a workaround for bamboo (non cloud). 

[Przemek Bruski]

What do agent build logs say while you can access them, do you have any exceptions in them? You may be affected by this bug.

[Matt Clarkson]

Przemek,

I am getting this as well. I just set up a Windows AMI for Bamboo AOD 4.1 and it randomly goes offline

Agent 'Elastic Agent on i-e8ace290' went offline while building TC-TESTS-WINDOWSSERVER2008R264BITCONFIGURATION-211. The build results did not finish.

How can I debug this and work out why my AMI is bombing out? Sometimes it works fine... :(

Here's the log file:

https://answers.atlassian.com/upfiles/TC-TESTS-WINDOWSSERVER2008R264BITCONFIGURATION-211_1.log

[Matt Clarkson]

This looks like it's happening because the build is stalling. this could be because I was running it on a Small instance...Lets try Large

[Frank Burns]

I am having similar issues.   They emanate in two ways:

1) 

20-Sep-2019 19:22:20	Data Send took: 0.185
20-Sep-2019 19:23:51	Agent 'Elastic Agent on i-0495c84735905d1b6' went offline while building MH3DBBT-WRL-LBM01-13. The results of that build will not be available.

2) Build triggered but not queued Reason for not building is unknown

This behavior is random.  Any help is appreciated

[karthikys]

We are being hit by the same issue in Bamboo 5.4.1. Is there a fix ??

[James Gustard]

I think the cause of this was very long builds, as our maven build was having to download the repository from scratch each time. I fixed this by adding EBS with a pre loaded maven repo, and setting up a Nexus repository running in the cloud , and pointing the settings.xml in the EBs to point at this repo, so that any extra artifacts needed can be downloaded quickly.

Our builds are running very fast and with no problems now.