You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
after Bitbucket server upgrading from 6.8 to 7.6, the built-in SSH server began to fall every few days, that is, at some point the server stops responding to SSH requests to repositories, stops writing logs to the atlassian-bitbucket.log.
At the same time, the resources of the system work correctly and do not show the causes of problems.
The only thing we noticed is that network connections on port 7999 are clogged.
from the information that I have:
The problem of network connections is not regulated by the system in any way, and what should be looked at on the side of the application using this port.
Upsource is a smart code review tool and a repository browser that supports Git.
My guess is that he was opening too many ssh connections at the same time. It was his disabling that helped us stop the endless falls of the bitbucket
Disabling Upsource is answer to my question.
I can't explain it any other way. It was a very long time ago and was repeated on all versions from which it appeared, until the service I specified was turned off.
it was the into bitbucket ssh server that crashed and there was a long correspondence with support, which could not help in any way, a support ticket was maintained for a year and a half and ended in nothing.