nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bamboo Elastic Agent failed to connect

Sam_gnf66k

I'm trying to connect elastic agents to my Bamboo Server and the agent is stuck in a pending state.

Agent Logs

WARN [AgentRunnerThread] [ResourceResolver] Unable to find resource bamboo-capabilities.properties
INFO [AgentRunnerThread] [DefaultAgentCapabilityManagerImpl] Failed to load bamboo-capabilities.properties
WARN [AgentRunnerThread] [FailoverTransport] Transport (tcp://localhost:4527?wireFormat.maxInactivityDuration=300000) failed, attempting to automatically reconnect
java.io.IOException: Wire format negotiation timeout: peer did not send his wire format.
#011at com.sun.proxy.$Proxy40.registerAgent(Unknown Source) ~[?:?]
#011at com.atlassian.bamboo.agent.elastic.client.ElasticAgentRegistrationBean.registerAgent(ElasticAgentRegistrationBean.java:25) ~[atlassian-bamboo-agent-remote-9.0.1.jar:?]
WARN [ActiveMQ Task-2] [FailoverTransport] Failed to connect to [tcp://localhost:4527?wireFormat.maxInactivityDuration=300000] after: 1 attempt(s) with Wire format negotiation timeout: peer did not send his wire format., continuing to retry.

Bamboo Server

Broker client URL: failover:(tcp://ip_address:54663?wireFormat.maxInactivityDuration=300000&socket.verifyHostName=false)?initialReconnectDelay=15000&maxReconnectAttempts=10

Accepted answers

Eduardo Alvarenga

Hello @Sam

Welcome to the Atlassian Community!

Is the ip_address:54663 reachable from your Bamboo Server? It may also be the case of another process listening on port 54663 and preventing ActiveMQ from working.

Please check this KB article for more tips:

Bamboo Elastic Agents stuck on pending state with wire format negotiation timeout error

Cheers,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful--

All comments

Eduardo Alvarenga

Hello @Sam

Welcome to the Atlassian Community!

Is the ip_address:54663 reachable from your Bamboo Server? It may also be the case of another process listening on port 54663 and preventing ActiveMQ from working.

Please check this KB article for more tips:

Bamboo Elastic Agents stuck on pending state with wire format negotiation timeout error

Cheers,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful--

Sam_gnf66k

Hi Eduardo, thank you for the reply. What do you mean by ip_address is reachable from the Bamboo Server? Are you referring to Agent is able to ping the Bamboo Server? When I ran this command netstat -an | grep 54633 on Bamboo Server, I don't see anything that is LISTEN on that port. Also, I did try the fix in the KB article you sent with no luck.

Eduardo Alvarenga

Hello @Sam

ActiveMQ will listen to port TCP/54663 on every interface on the server by default. The "Broker Client URL" is the URL the Agents will connect to, whilst the "Broker URL" controls where Bamboo will listen to that service along with other options. It defaults to 0.0.0.0:54663, meaning every interface and every IP address.

Please validate that property as well.

Any changes to those properties require you to restart the complete application.

Regards,

Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful--

Sam_gnf66k

For the Broker URL: nio://0.0.0.0:54663?wireFormat.maxInactivityDuration=300000 and Broker client URL: failover:(tcp://192.168.5.8:54663?wireFormat.maxInactivityDuration=300000&socket.verifyHostName=false)?initialReconnectDelay=15000&maxReconnectAttempts=10

What I don't understand is why the agent is tying to connect to "tcp://localhost:4527"? Shouldn't it be connecting to port 54663?