Bamboo losing connection to Stash Git repositories

I am experiencing intermittent loss of connection to git repositories from BAMBOO. the issue covers multiple repositories and seems random.

The error I get is: 

WARN [sshd-SshClient[3b7fd39]-nio2-thread-5] [AcceptAllServerKeyVerifier] Server at <Server Name edited>:7999 presented unverified RSA key: c3:9f:d7:74:41:d0:c6:a7:f4:6e:c6:6e:fc:08:69:87
2014-11-18 03:01:14,921 WARN [Connection monitoring thread - 44e155f7-f4ea-4a43-ba11-9f0885a16a8c] [SshProxyCommand] While connecting to [<Server Name edited>:7999]: Authenticating remote session failed

I can save the linked repositories after discovering the error. Next Builds seem fine. So the application links seem fine.

The funny thing is there are no changes to trigger a build when these errors occur. These builds are not using polling but are set up with "stash repository changes trigger build".

Does Bamboo check connections to git repositories even when there are no changes?

What could be the possible causes of this? Why does Bamboo throw this error when the build is not scheduled to be ran?

 

Any help would be appreciated!

1 answer

1 accepted

0 vote

Stash is sending remote events to Bamboo notifying it about things. For many reasons this may not work - wrong version of Bamboo or Stash, wrong configuration, finally some network issues.

Bamboo is pinging Stash server to know if remote events are functional. If they are not it will fallback to polling. This polling interval is not configurable. It will connect to repository to check it for changes.

From what you said it is possible that there is some network problem, remote events stop working for awhile, Bamboo switches to polling and it fails because of network problem.

Actually polling from time to time just to ensure everything is in sync is not a bad idea anyway. Depending on your Bamboo version there is a system property "bamboo.stash.repository.trigger.polling.interval"  that you can set to number of seconds to enforce polling interval for Stash Trigger no matter what.

"For many reasons this may not work - wrong version of Bamboo or Stash, wrong configuration, finally some network issues." Stash 2.12 vs Bamboo 5.6.1 - could this be a reason of such warnings?

Suggest an answer

Log in or Join to answer
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

698 views 0 4
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot