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

David Schlesinger March 11, 2014

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
Przemek Bruski
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 11, 2014

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.

David Schlesinger March 13, 2014

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?

Przemek Bruski
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 13, 2014

Try:

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

David Schlesinger March 13, 2014

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

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

David Le March 13, 2014

I am having the same problem too.

robin wang April 25, 2014

I have the same issue, too

0 votes
Brian Colfer May 26, 2014

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}

Przemek Bruski
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 27, 2014

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

0 votes
Brian Colfer May 20, 2014

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

0 votes
Dana Cleveland
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 6, 2014

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.

Przemek Bruski
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 6, 2014

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

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events