Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,363,175
Community Members
 
Community Events
168
Community Groups

Authentication is failed from Elastic Bamboo instance to Elastic Agent

Deleted user Jul 12, 2018

Below is the error shown while connection from elastic bamboo instance to elastic agent(elastic agent is struck pending status for a long time), can someone please advise? Thanks.

2018-07-12 15:54:25,558 INFO [main] [ElasticAgentBootstrap] HTTP(S) tunnel: enabled
2018-07-12 15:54:25,558 INFO [main] [ElasticAgentBootstrap] JMS tunnel: enabled
2018-07-12 15:54:25,561 INFO [main] [ElasticAgentBootstrap] Starting tunnel server, waiting for 2 connections.
2018-07-12 15:54:26,050 INFO [main] [AgentBootstrap] Agent bootstrap using endpoint: httpst://127.0.0.1:46593/agentServer/
2018-07-12 15:54:26,055 INFO [main] [ElasticAgentBootstrap] Using tunnelling. Setting virtual host name to stage-bamboo.fitchratings.com
2018-07-12 15:54:26,058 INFO [main] [RemoteAgentHomeLocatorForBootstrap] Using agent home located at [/home/bamboo/bamboo-agent-home]
2018-07-12 15:54:26,058 INFO [main] [RemoteAgentHomeLocatorForBootstrap] Using agent home located at [/home/bamboo/bamboo-agent-home]
2018-07-12 15:54:26,059 INFO [main] [AgentUuidInitializer] Generating new UUID for this agent: 829e67f9-2cb9-42d9-be8c-5c6b3d31f89a
2018-07-12 15:54:26,067 INFO [main] [AgentContext] Requesting fingerprint, url: httpst://127.0.0.1:46593/agentServer/GetFingerprint.action?hostName=ip-10-129-11-180&agentType=elastic&fingerprint=2409681192100522816&instanceId=i-0ab81e201b7cbee4f&version=3&agentUuid=829e67f9-2cb9-42d9-be8c-5c6b3d31f89a
2018-07-12 15:54:26,067 INFO [main] [RemoteAgentHttpClientFactory] Creating a new HTTP client...
2018-07-12 15:54:26,075 INFO [main] [ElasticAgentSchemeRegistryFactory] Using tunnelling for HTTP(S). Registering 'httpt' and 'httpst' protocols.
2018-07-12 15:54:26,101 INFO [main] [AgentContext] Authenticating against Bamboo server at httpst://127.0.0.1:46593/agentServer/
2018-07-12 15:54:26,105 INFO [tunnelserver:26224-1-thread-3] [LocalAcceptor] Accepted a local connection on port 46593, tunnel age: 0s
2018-07-12 15:54:26,146 WARN [main] [ResponseProcessCookies] Invalid cookie header: "Set-Cookie: AWSALB=4j7q1pxWGYP2cNZpXe+Zcw4NSh0ztJRlONG5B/M0ZZ/1wKwU2RLj9lobG/O5Ocood0cEa5Fo2kEqu8je/yMREtIliMTcez1RW5jfI8LlMeslWcg70hUAnuAb5IKa; Expires=Thu, 19 Jul 2018 15:54:26 GMT; Path=/". Invalid 'expires' attribute: Thu, 19 Jul 2018 15:54:26 GMT
2018-07-12 15:54:26,147 ERROR [main] [AgentContext] An error has occurred when requesting fingerprint: HTTP/1.1 502 Bad Gateway
Exiting due to fatal exception.
com.atlassian.bamboo.agent.bootstrap.RemoteAgentHttpException: Response: [HTTP/1.1 502 Bad Gateway] received after fingerprint request.

1 answer

0 votes
Jeremy Owen Atlassian Team Jul 12, 2018

Hey Santosh,

So the tunnel client that Elastic Bamboo uses is trying to connect to the address that is configured as your Base URL at Bamboo Administration >> Overview >> General Configuration >> Base URL.

It looks like there is an AWS ALB at that address (judging by the cookie in the response) and that ALB is getting an invalid response from the backend application it's forwarding HTTP traffic to.

Assuming that the ALB is getting that invalid response from the Bamboo Server -- there should be more information in the Bamboo Server logs when the 502 gets logged agent side that might suggest what went wrong. You should tail them while the agent attempts to connect to see you can learn anything more. The log is located at:

  • <bamboo-home>/logs/atlassian-bamboo.log

Alternatively, you might want to consider bypassing the AWS ALB entirely and keep the traffic from the Elastic Agent that comes over the tunnel, local. Try the resolution in the below knowledge-base article and see if that helps:

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events