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,465,960
Community Members
 
Community Events
176
Community Groups

mysql is not connecting.

Could not create a connection to the database server. Attempted to reconnect 3 times. Giving up.

1 answer

0 votes

I'm afraid there's not a lot we can tell you here.

You have tagged this with Bitbucket Cloud, which implies that you have set up something on Bitbucket that is trying to connect to a database, but you have not told us what you have configured, so we don't know what you are trying to do (it's not the core of Bitbucket Cloud throwing this error, Cloud doesn't use MySQL)

If you've mis-categorised this, and you're actually on Bitbucket Server or Data Center, then the "what have you configured" question is still there, but it might also apply to the core installation - Bitbucket needs a database to store its data, and your error message could be coming from the installation itself.

So, can you tell us where you are actually getting this error message?  What are you doing that provokes it?

We can also start on an answer - the message really does mean that the service can't connect to the database - it's not running, it can't be reached over the network, or the credentials you've told it to use are wrong (unknown user, wrong password, don't have permission to use the database, etc)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events