Offline/disabled agents in Bamboo

Hi all,

I have got following message under the requirement tab of a default job of the plan:

"This job can only be built by agents whose capabilities meet the 4 requirements below. 2 agents are capable of building this job. However, those agents are currently offline or disabled."

Can this create issues with bamboo in detecting a repository based trigger? I am able to run the plan manually but bamboo has stopped detecting triggers based on change in the repository after this problem. How can I resolve this issue?

Thanks

1 answer

This widget could not be displayed.

Hi Vidhi,

The repository will continue triggering as usual and Bamboo will detect them but, if there are no agents ready to take builds, the builds will be enqueued in order to be executed when an agent capable of running those builds is available.

The question is: if the 2 agents capable of running that plan are offline/disabled, how are you able to run that plan manually? There are some things you could initially check:

  • Could you please verify that you have configured your Bamboo broker URI to be the same as your Bamboo base URL is (under Administration >> General Configuration)? Please see your BAMBOO_HOME/bamboo.cfg.xml file to check your Broker URI:
    <property name="bamboo.jms.broker.client.uri">failover:(tcp://_bamboo_host_name_:54663?wireFormat.maxInactivityDuration=300000)?maxReconnectAttempts=10&initialReconnectDelay=15000</property>
    <property name="bamboo.jms.broker.uri">tcp://0.0.0.0:54663?wireFormat.maxInactivityDuration=300000</property>
  • Are you using any 3rd party plugins?
  • Is there a proxy server or a firewall between Bamboo server and the remote agent?
  • Also, try to specify the full explicit java path in your BAMBOO_AGENT_HOME/conf/wrapper.conf file:
    wrapper.java.command=_explicit_path_to_java_
  • If none of the above mentioned steps help, please drop your Bamboo remote agent directory, drop jms-store and caches directories from BAMBOO_HOME, restart your Bamboo server and try to install the remote agent from scratch using the jar file downloaded from Administration > Agents > Install Remote Agent page.

I hope this helps!

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

97 views 1 0
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you