Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Build Queue - refresh/restart builds?

After restarting bamboo, all of our local agents were offline. This resulted in a number of builds queuing with a status of "No agent can build this job".

Since restarting each agent, the build are still sitting in the queue with the error, no agents. New builds have since triggered, jumped the current queue and started running.


Is there a way to get bamboo to re-evaluate the queue to kick off these builds?

i'm looking for a way to kick these off without going into each build manually and re-running?




2 answers

1 accepted

Is there a way to get bamboo to re-evaluate the queue to kick off these builds?

Once the builds fall in this state unfortunately, each build will need to be cancelled and restarted manually

2 votes

Hi @Simon Hooper

I assuming you are not running Bamboo 6.10.2 or newer where agents disconnection caused by a server restart should be a lot less frequent due to the implementation of [BAM-18608] Increase the default time taken for the agents to reconnect in case the server is temporarily down.

I just ran a quick test and the best way to stop those builds is by restarting the server. A quick restart should not drop any agents even in your version.

I do recommend that you follow the workaround suggested in the following document to increase the time that your agents are able to reconnect after a server restart. That should save you from this situation next time you need to restart your server to do some maintenance. This is the document:

I hope that helps.

Hi Dan, yes we are running 6.10.2.


I believe that the bamboo host server was restarted due to a OS patch being applied. I'm not sure how long it was down however. Once the agents came back on line the builds in the queue did not resume.

To get these builds to work for my team i had to cancel and restart each build manually. Not ideal.


I'm not sure that Remote agent does not restart after server outage - Atlassian Documentation is related. The agents did come back on line and they serviced subsequent builds fine. It was the ones that were already in the queue that just seemed to never be evaluated again.

I would have assumed that once the agents reconnected they would proceed to work on the existing queue?

First of all, I'm sorry for the delay (vacation time).

@Simon Hooper, from what you say, I agree that the problem was not caused by the agents being offline, but there is a chance that scenario was triggered by the absence of agents online right after the Bamboo server was back.

I suggested that link as an attempt to reduce the possibilities of triggering this scenario.

I would have assumed that once the agents reconnected they would proceed to work on the existing queue?

Yes, we are on the same page. Unfortunately, the feature didn't work as we expected.

This type of problem is more complex to troubleshoot. We would need to check the logs from that event if you still have them (due to log rotation they could be lost already). 

Do you see any error messages in <Bamboo_Install>/logs/catalina.out (assuming you are running Bamboo on a Linux instance) ?

We have bamboo is running on windows.

I noted an error on one of the builds that failed to restart. Appears to be related to connecting to git.


Ill check with the services team to see if they take down the git server for patching also at these times.


My suspicion is this is just a timing issue with when each server is taken offline for patching. 

For everyone's benefit, we confirmed this was a timing issue with bitbucket being taken down for maintenance after a build had triggered. 

Like # people like this

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events