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

MySQL won't start after setting server character set to UTF-8

I'm following the instructions at to get a Crucible evaluation installation running with MySQL 5.7.29 on Windows Server 2012 R2. If I follow the step to edit my.ini to set character-set-server=utf8, then upon the next attempt to start MySQL, it gets stuck in the starting state, with no new messages in the .err file to indicate what is wrong. Doesn't use CPU or disk, just stuck. And even after killing it with task manager and removing the character-set-server=utf8 line from my.ini, the same thing happens. Once this change is made, it always gets stuck starting, and I have not found a fix. I tried uninstalling / reinstalling MySQL, and the same thing happened. So with the third installation, I'm leaving the server at latin1 and creating the fisheye database set to the latin1 character set (given the note in the above link that the db and server character sets must match), and hoping for the best ...

Are there updated instructions available for getting MySQL running with Crucible with a utf8 character set?

1 answer

0 votes

Hi @Michael Weber , 

Did you find some solution, please share ?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira

Online AMA this week: Your project management questions answered by Jira Design Lead James Rotanson

We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...

193 views 1 6
Read article

Atlassian Community Events