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

Why i am getting "StatusReason for not building is unknown"

After restart of Bamboo some of our agents went offline and some plans are failing with status "Reason for not building is unknown". What may be the possible cause of this problem and how can we fix it?

1 answer

0 votes

Hello @FaheemUllah,

That's really hard to say without any data at hand, it could practically be anything not even knowing what build you are running there.

As a first step, you should open your failing build logs and check out what warnings and error messages you spot there. They typically provide a first indication on what to look at next.

If the log messages are meaningful, you can directly act on them. Say the error claims something like "file missing", you may want to verify first if that file really exists, and if so, you may be concerned about the file's name or permissions on it.

If an error message is very specific you might google for it and check out user forums or Community sites to find out more about that.

Besides by creating a Bamboo Support Zip, you'll find your main Bamboo configuration files in that ZIP archive as well as your Bamboo Server log (atlassian-bamboo.log) and your Bamboo Tomcat log (catalina.out).

Additionally, for remote agents, you find agents logs here:

  • <Bamboo agent home directory>/atlassian-bamboo-agent.log
  • <Bamboo agent home directory>/logs/atlassian-bamboo.log

Your elastic Bamboo agent logs you would receive per SCP, as described among a lot of further elastic agent information given, in the following KB.

You can grep any of these logs, depending on where you expect the error to occur and being logged out to and look for e.g. "fatal", "exception", "error".

As you see, there are many options to fish for an error. However, you may post a found error message to this thread and we might come up with further ideas for you.

Thanks, Gerhard

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events