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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Bitbucket fails after SQL upgrade

We recently upgraded the SQL server that our Bitbucket application connects to. We upgraded to SQL 2019. Since then the Bitbucket application has been down. 

It was a challenge just getting it installed as I am not much of a Ubuntu admin, so I am pretty lost on this.

1 answer

0 votes
Aron Gombas _Midori_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 05, 2023

I think you should share more concrete details about the problem.

For example, if the symptom is that Bitbucket doesn't start up after the DB upgrade, then there should be an exception with a stack trace in the Bitbucket log. That would help tremendously to understand the problem and conclude on the next step.

So far the log states that it cannot connect to the DB server. However, I can connect to the DB server without issue using telnet from the BB server. The network team has looked for any possible blocks between the two servers, but they are not seeing any. 

When I check the status of BB on the server it shows as "active (exited)". We also see an odd error stating, su: user "username" does not exist or the user entry does not contain all the required fields." The odd thing is, the account is the account we used to completely setup the server.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events