How do I update the broker URL when installing a remote agent?

I'm attempting to install a remote agent by following the command below:

java -jar atlassian-bamboo-agent-installer-5.3.jar https://HOSTNAME/agentServer/

This starts the insall correctly and gets to the step where I need to approve access in bamboo.

However, after approving the agent I run into the following issue:

[AgentUuidInitializer] Found agent UUID '8e7a5935-414c-4a83-b292-6640864f0951' in temporary UUID file '/home/david/bamboo-agent-home/uuid-temp.properties'
INFO   | jvm 1    | 2014/03/11 15:54:41 | 2014-03-11 15:54:41,255 INFO [Thread-1] [AgentConfiguration] Setting UUID in main config file to '8e7a5935-414c-4a83-b292-6640864f0951'
INFO   | jvm 1    | 2014/03/11 15:54:41 | 2014-03-11 15:54:41,290 INFO [Thread-1] [BambooActiveMQConnectionFactory] Setting broker URL to 'failover:(tcp://localhost:54663?wireFormat.maxInactivityDuration=300000)?maxReconnectAttempts=10&initialReconnectDelay=15000'
INFO   | jvm 1    | 2014/03/11 15:54:41 | 2014-03-11 15:54:41,295 WARN [Thread-1] [BambooActiveMQConnectionFactory] Broker URI: tcp://localhost:54663?wireFormat.maxInactivityDuration=300000 is invalid: java.net.ConnectException: Connection refused
INFO   | jvm 1    | 2014/03/11 15:54:41 | 2014-03-11 15:54:41,371 INFO [Thread-1] [BambooActiveMQConnectionFactory] Setting broker URL to 'failover:(tcp://localhost:54663?wireFormat.maxInactivityDuration=300000)?maxReconnectAttempts=10&initialReconnectDelay=15000'
INFO   | jvm 1    | 2014/03/11 15:54:41 | 2014-03-11 15:54:41,372 WARN [Thread-1] [BambooActiveMQConnectionFactory] Broker URI: tcp://localhost:54663?wireFormat.maxInactivityDuration=300000 is invalid: java.net.ConnectException: Connection refused

I've tried updating bamboo-agent.cfg.xml to explicitly define the broker URL:

<property name="bamboo.jms.broker.client.uri">failover:(tcp://HOSTNAME:54663?wireFormat.maxInactivityDuration=300000)?maxReconnectAttempts=10&initialReconnectDelay=15000</property>
<property name="bamboo.jms.broker.uri">tcp://HOSTNAME:54663?wireFormat.maxInactivityDuration=300000</property>

Is there something else I'm missing?

Thanks,

David

4 answers

1 vote

It's a bug in the validation routine. It has been fixed in later version of Bamboo. You can ignore it unless your agent doesn't work.

I updated bamboo and I'm now using atlassian-bamboo-agent-installer-5.4.2.jar but I'm stil running into the same issue.

Any suggestions?

Try:

java -jar atlassian-bamboo-agent-installer-5.4.2.jar https://HOSTNAME/agentServer/ install

I ran that command which seems to just create the bamboo-agent-home directory.

Running 'start' afterwards doesn't start the agent either.

I am having the same problem too.

I have the same issue, too

I am seeing basically the same thing. I used a Fully qualified host name, actually an alias (A NAME) for the url when i installed the agent. But when i see it start, the JMS url is only includes the hostname of the server that is pointed to by the alias. That is just the hostname without the domain included. If it insists on resolving the alias, i definately still need a FQDM.

The agent uses broker client uri from server's bamboo.cfg.xml

I'm having the same problem with 5.5.0 and the broker url is not in bamboo.cfg.xml

My bamboo.cfg.xml does not have the client uri:

{code}

<?xml version="1.0" encoding="UTF-8" standalone="no"?>

<configuration>

<buildWorkingDirectory>/home/a_user/bamboo-agent-home/xml-data/build-dir</buildWorkingDirectory>

<agentUuid>"uuid-string"</agentUuid>

</configuration>

{code}

The config file on the server, not the one on the agent.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,786 views 0 6
Read article

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