Can't get remote bamboo agent to register, not sure what is missing

Question

connectivity back to master works on 443, 54663.  Agent doesn't show up in list of registered agents.

2019-09-03 10:17:25,635 DEBUG [AgentRunnerThread] [ExternalProcessImpl] ---------------------------
2019-09-03 10:17:25,635 DEBUG [AgentRunnerThread] [ExternalProcessImpl] End Process Debug Information
2019-09-03 10:17:25,635 DEBUG [AgentRunnerThread] [ExternalProcessImpl] ---------------------------
2019-09-03 10:17:25,645 INFO [AgentRunnerThread] [AgentRegistrationBean] Registering agent on the server,
2019-09-03 10:17:25,664 DEBUG [AgentRunnerThread] [TaskRunnerFactory] Initialized TaskRunnerFactory[ActiveMQ Task] using ExecutorService: java.util.concurrent.ThreadPoolExecutor@3e04f0b0[Running, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]
2019-09-03 10:17:25,677 DEBUG [AgentRunnerThread] [FailoverTransport] Reconnect was triggered but transport is not started yet. Wait for start to connect the transport.
2019-09-03 10:17:25,785 DEBUG [AgentRunnerThread] [FailoverTransport] Started unconnected
2019-09-03 10:17:25,785 DEBUG [AgentRunnerThread] [FailoverTransport] Waking up reconnect task
2019-09-03 10:17:25,787 DEBUG [ActiveMQ Task-1] [FailoverTransport] urlList connectionList:[tcp://BAMBOO_MASTER:54663?wireFormat.maxInactivityDuration=0], from: [tcp://BAMBOO_MASTER:54663?wireFormat.maxInactivityDuration=0]
2019-09-03 10:17:25,874 DEBUG [ActiveMQ Task-1] [FailoverTransport] Attempting 0th connect to: tcp://BAMBOO_MASTER:54663?wireFormat.maxInactivityDuration=0
2019-09-03 10:17:25,894 DEBUG [ActiveMQ Task-1] [WireFormatNegotiator] Sending: WireFormatInfo { version=12, properties=

{TcpNoDelayEnabled=true, SizePrefixDisabled=false, CacheSize=1024, ProviderName=ActiveMQ, StackTraceEnabled=true, PlatformDetails=JVM: 1.8.0_212, 25.212-b04, Oracle Corporation, OS: Linux, 3.10.0-957.21.3.el7.x86_64, amd64, CacheEnabled=true, TightEncodingEnabled=true, MaxFrameSize=9223372036854775807, MaxInactivityDuration=0, MaxInactivityDurationInitalDelay=10000, ProviderVersion=5.14.5}

, magic=[A,c,t,i,v,e,M,Q]}
2019-09-03 10:17:25,898 DEBUG [ActiveMQ Task-1] [FailoverTransport] Connection established
2019-09-03 10:17:25,899 INFO [ActiveMQ Task-1] [FailoverTransport] Successfully connected to tcp://BAMBOO_MASTER:54663?wireFormat.maxInactivityDuration=0
2019-09-03 10:17:25,945 DEBUG [ActiveMQ Transport: tcp://BAMBOO_MASTER/IP:54663@43920] [InactivityMonitor] Using min of local: WireFormatInfo { version=12, properties=

{TcpNoDelayEnabled=true, SizePrefixDisabled=false, CacheSize=1024, ProviderName=ActiveMQ, StackTraceEnabled=true, PlatformDetails=JVM: 1.8.0_212, 25.212-b04, Oracle Corporation, OS: Linux, 3.10.0-957.21.3.el7.x86_64, amd64, CacheEnabled=true, TightEncodingEnabled=true, MaxFrameSize=9223372036854775807, MaxInactivityDuration=0, MaxInactivityDurationInitalDelay=10000, ProviderVersion=5.14.5}

Daniel Santos_157bm4 · Answer

Hey @James Parsons Bamboo agents have two different protocols/channels when talking to the server. Firstly they talk to Bamboo through HTTP to ask about the broker details. Then when they have the broker configuration they try to connect using JMS through the address provided by the Bamboo server. Bamboo knows there is a new agent loading when it receives the first contact through HTTP. It means that your agents can reach the server through port 443, but somehow they are not able to establish the JMS connection after that. What I would check to move forward: * Ask your administrator for the broker URL configured in Bamboo server >> Admin >> Overview >> General configuration >> Broker configuration. The Broker URL should look like:nio://0.0.0.0:54663?wireFormat.maxInactivityDuration=300000 The Broker client URL should look like:failover:(tcp://:54663?wireFormat.maxInactivityDuration=300000)?initialReconnectDelay=15000&maxReconnectAttempts=10 * Check if your agent is able to reach the configured in the Broker client URL. This could be the reason your agent is not able to connect with the Bamboo server. The Broker address is what the remote agent will try o reach to establish the connection with the server. I hope this info helps you move you some steps forward.

James Parsons_30439f · Answer

Hi @Daniel Santos ,

1. agent was installed via jar file provided by the bamboo server team

( java -jar atlassian-bamboo-agent-installer-6.3.2.jar https://bamboo_server/agentServer)

2. I don't have access to the admin logs as the server is managed by another team and they push responsibility for remote agents back on you.  I have now learnt that the Bamboo server runs as a docker container on the Host.

3. the only reference to my agent they could see in their admin logs was (i've masked the fqdn and IP from the log entry) the following message type:

atlassian-bamboo.log.10:2019-09-03 06:18:58,213 INFO [http-apr-8085-exec-43] [RemoteAgentManagerImpl] A remote agent is loading on bamboo_agent_fqdn (IP).

atlassian-bamboo.log.10:2019-09-03 06:23:35,353 INFO [http-apr-8085-exec-82] [RemoteAgentManagerImpl] A remote agent is loading on bamboo_agent_fqdn (IP).

atlassian-bamboo.log.15:2019-09-03 00:17:10,045 INFO [http-apr-8085-exec-70] [RemoteAgentManagerImpl] A remote agent is loading on bamboo_agent_fqdn (IP).

4. As far as I am aware there aren't any other agents in the same network that are working.  Another team has a similar setup to mine and they are experiencing the same issue as me.  We are both in a remote network, but have burnt the firewall rules back to the bamboo server (port 443 and 54663).  According to the Admin team, they were able to resolve, ping and SSH to my agent server, I'm not aware of any other ports the bamboo server needs access to on the agent, but we are not blocking any ports inbound on the agent server.

thanks for your assistance.

Daniel Santos_157bm4 · Answer

Hi @James Parsons

I'm not able to tell you what is causing this issue only by checking the logs you shared. I'll need your help to provide me with some extra details.

This is what I would check if experiencing a similar issue:

* How the agent was installed?
If you did clone a different agent installation it could make two or more agents have the same agentUuid in bamboo-agent.cfg.xml. This would cause issues in the Bamboo UI when listing the agents.
* What are the messages you see in the Bamboo Admin >> Agents page?
I would gather those messages to compare with the agents and server logs.
* What are the server logs you see when these agent is not registering?
The server logs (<Bamboo_Home>/logs/atlassian-bamboo.log)will also help to see what is happening on server side when the registration fails.
I can see from the agent logs that it shows as successfully connected.
* Do you have other remote agents connecting to Bamboo (in the same network of this one)?
This would be important information to validate if this could be a Bamboo server configuration issue.

Those would be my first steps to investigate this issue.