Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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,459,360
Community Members
 
Community Events
176
Community Groups

Bamboo Server 6.2.2 SSH & SCP fail to connect most of the time

Edited

Hi,

I have 2 SSH and one SCP task in my deployment plan, all connecting to a server TJiraHost.ac.local on the local network using port 22. 

These tasks seem to fail 99% of the time and then occasionally they succeed.

Whats even more interesting is that whilst this is failing, if I manually SSH using putty from the box on which the Bamboo server is running to TJiraHost.ac.local on port 22 (using the same login details) the putty connection succeeds - every time.

Therefore, I know the hostname, port, username and password are correct, but I cannot figure out why Bamboo fails whilst putty succeeds.

At first I thought it may be related to the keep alive so I set this to 5s for each task and still faced the same issue.

Just for completeness, TJiraHost is running CentOS and the Bamboo server is a Windows server.  

1 answer

1 accepted

1 vote
Answer accepted

This ended up being purely a network based error.

Essentially, the builds were occurring 99% of the time on a remote agent, from which the SSH connections would also then be attempted. However, this remote agent was not able to see the deployment server due to subnet issues.

The other 1% of the time the SSH connections were made on the local agent (the machine from which I successfully tried SSH using putty). This local agent was able to see the deployment server as it had visibility of both of our subnets. This meant in these 1% of deployments the SSH tasks passed without issue.

I'm facing the similar issue. In my case I want to ssh to one of my EC2 instances on aws from Bamboo's local agent. Both are inside the same VPC. I can ssh to my EC2, if I'm logged into Bamboo's local agent. But, I want to achieve the same using ssh task in Bamboo. Do you think Imight also have an issue with the subnet's settings? How can I check that?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events