Bamboo: remote agent can't connect to broker
Asked by Greg Hansen:

I'm on the machine where I'm trying to run the remote agent, logged in as root. I've downloaded the installer jar to the directory /root/bamboo-agent-home. I run the command:

java -jar atlassian-bamboo-agent-installer-5.4.2.jar [](http://BAMBOOHOST:8085/agentServer)<http://BAMBOOHOST:8085/agentServer>

and in the resulting display of information, at the end, I see:

INFO \| jvm 1 \| 2014/05/05 12:42:26 \| 2014-05-05 12:42:26,318 INFO \[Thread-1\] \[BambooActiveMQConnectionFactory\] Setting broker URL to 'failover:(tcp://[BAMBOOHOST](http://BAMBOOHOST:8085/agentServer):54663?wireFormat.maxInactivityDuration=300000)?initialReconnectDelay=15000\&maxReconnectAttempts=10'  
INFO \| jvm 1 \| 2014/05/05 12:42:26 \| 2014-05-05 12:42:26,335 WARN \[Thread-1\] \[BambooActiveMQConnectionFactory\] Broker URI: tcp://[BAMBOOHOST](http://BAMBOOHOST:8085/agentServer):54663?wireFormat.maxInactivityDuration=300000 is invalid: java.net.ConnectException: Connection refused  
INFO \| jvm 1 \| 2014/05/05 12:42:26 \| 2014-05-05 12:42:26,488 INFO \[Thread-1\] \[BambooActiveMQConnectionFactory\] Setting broker URL to 'failover:(tcp://[BAMBOOHOST:54663](http://BAMBOOHOST:8085/agentServer)?wireFormat.maxInactivityDuration=300000)?initialReconnectDelay=15000\&maxReconnectAttempts=10'  
INFO \| jvm 1 \| 2014/05/05 12:42:26 \| 2014-05-05 12:42:26,489 WARN \[Thread-1\] \[BambooActiveMQConnectionFactory\] Broker URI: tcp://[BAMBOOHOST](http://BAMBOOHOST:8085/agentServer):54663?wireFormat.maxInactivityDuration=300000 is invalid: java.net.ConnectException: Connection refused

I have temporarily disabled the firewalls between the two machines to try to get this sorted out. I can ping each machine from the other. Running on CentOS 5.8 on the remote agent machine (has to be that), CentOS 6.5 on the Bamboo host.

I can see messages in Bamboo, on the Agents page:

May 5, 2014 12:42:21 PM A remote agent is loading on REMOTEMACHINE (ITSCORRECTIP).

so some communication is occurring, just not that last step ....

Help?


Answers:
author: Greg Hansen
body: So I got it working, but not in the setup above. I moved to a different machine for the server, one where I could set up bamboo to be accessed using port 80 (note that in the above I was trying to use \<hostname\>:8085 in all the URLs), and then it was very easy.

So be sure you set it up that way! There seems to be an assumption in Bamboo that it will be addressed via port 80.

comments: author: Przemek Bruski
body: > There seems to be an assumption in Bamboo that it will be addressed via port 80.

Something must have been misconfigured. We make no such assumptions, in fact, our primary dogfooding server is running on 8085.


author: Greg Hansen
body: So I got it working, but not in the setup above. I moved to a different machine for the server, one where I could set up bamboo to be accessed using port 80 (note that in the above I was trying to use \<hostname\>:8085 in all the URLs), and then it was very easy.

So be sure you set it up that way! There seems to be an assumption in Bamboo that it will be addressed via port 80.


author: Greg Hansen
body: So I got it working, but not in the setup above. I moved to a different machine for the server, one where I could set up bamboo to be accessed using port 80 (note that in the above I was trying to use \<hostname\>:8085 in all the URLs), and then it was very easy.

So be sure you set it up that way!


author: Przemek Bruski
body: Can you reach the port 54663 on the server from the agent?

comments: author: Greg Hansen
body: Should I be able to telnet to it?

telnet HOST 54663  
Trying \<\<IPADDRESS_OF_HOST\>\>  
telnet: connect to address \<\<IPADDRESS_OF_HOST\>\>: Connection refused  
telnet: uable to connect to remote host: Connection refused.

I can telnet to port 80 on HOST from the remote machine. As noted, there are no firewalls active on either machine, and they are in the same subnet. I made sure bamboo is running on HOST. I made sure both /etc/hosts files are correct.

Is there some other way to tell if it can be reached?


author: Przemek Bruski
body: Yes, you should be able to telnet it (you've got the port number wrong in your example).

Check if the port is open on the server using netstat -l


author: Greg Hansen
body: Sorry, was copying from another screen. I've edited the comment to be correct.

There is no line showing port 54663 in the output of netstat -l. I have disabled the firewall completely using the "setup" command. Does this indicate that the port is not open? If so, how does one open it?


Tags: install

remote-agent