Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

The Collation health check has failed even I have good collation in my DB

david_gianonatti August 21, 2019

Hi,

 

on health check I have this error message :

 

"The database collation 'utf8mb4_bin' and table collation 'utf8mb4_bin' are not supported by Jira"


But when I check resolution page : https://confluence.atlassian.com/jirakb/health-check-database-collation-in-mysql-943951422.html


It's written 

"For MySQL 5.7, the supported collation is utf8mb4_bin."


Thank you for your help

3 answers

0 votes
david_gianonatti August 31, 2019

I fixed the problem of collation, but my Jira is still crashing.

I open a new ticket

0 votes
david_gianonatti August 23, 2019

I would like to do it with keeping the current version

 

I created a new DB called jira2, I updated it in the dbconfig.xml 

But Jira can't connect to it, is anything I missed ?

Thank you

DPKJ
Community Champion
August 23, 2019

If you have GUI access to server, you can try <installation>/bin/config.sh or <installation>/bin/config.bat to test db connection and update it if required.

david_gianonatti August 23, 2019

Thank you for your help.

THis is what I got : 

/opt/atlassian/jira/bin# ./config.sh
No JRE_HOME or JAVA_HOME environment variable is set - attempting to just run java command
./check-java.sh: line 31: [: -ne: unary operator expected
./config.sh: line 41: java: command not found

DPKJ
Community Champion
August 23, 2019

You need to install Java and set Java Home environment variable to run this.

david_gianonatti August 23, 2019

I do not set Java Home environment variable, but seems to work.

I got this :

 

--- Database Selection ---
Database Type : MySQL
Instance : localhost:3306/jira
Connect As : root / *****

[H] H2 (not for production use)
* [M] MySQL 5.6
[N] MySQL 5.7+
[O] Oracle
[P] PostgreSQL
[S] SQL Server (MS-SQL)

 

Is it normal that MySQL 5.6 is selectionned ? Because I have a 5.7 version.

If not, should I reconfigure everything ? Or maybe I can I only switch from 5.6 to 5.7 directly ?

DPKJ
Community Champion
August 23, 2019

Please select MySQL 5.7.

Also this can be a reason of warning you were getting, because Jira support utf8mb4 only for MySQL 5.7 data source.

david_gianonatti August 23, 2019

Unfortunatly I still have the error message.

I will see if with this change, I will still have this Jira crash ...

Thank you again for your help

david_gianonatti August 27, 2019

I realized that I did not save changes ...

Now, this is what I have when loading Jira :

 

Database: We've found an error in MySQL supported version!
The database type in your dbconfig.xml is set up to MySQl 5.7+ and your MySQL version is 5.6 or lower. Consider using MySQL 5.6 database type instead
See our documentation for more information on changing database type.


I check 10 times on my terminal :

mysql -V
mysql Ver 14.14 Distrib 5.7.23, for Linux (x86_64) using EditLine wrapper

 

I really need help from the support ....

DPKJ
Community Champion
August 27, 2019

@david_gianonattithis seems very like a big issue.

I suggest you follow this guide - https://confluence.atlassian.com/adminjiraserver/connecting-jira-applications-to-mysql-5-7-966063305.html

And try to setup new Jira is any VM or other machine to verify where the problem is exactly.

You can also connect with Atlassian Support.

0 votes
DPKJ
Community Champion
August 21, 2019

What version of Jira and MySQL are you on?

david_gianonatti August 21, 2019

I'm on a 5.7.22 mysql server

About Jira, it's the 8.3.2 and I was on 6.x when the problem occurs. I updated to 8.2 in order to see if it will fix anything ...

DPKJ
Community Champion
August 21, 2019

Have you tried Jira restart? Error on my system disappeared after restart.

david_gianonatti August 21, 2019

I  have this error since months ... And I think it makes my Jira crashes.
So yes I restarted a lot Jira 

DPKJ
Community Champion
August 21, 2019

I think you need to connect with Atlassian Support.

Meanwhile you can try to, create a fresh database (with utf8mb4 collation type) and copy all data from old database to new, and check if this resolves your issue.

 

On my instance it got stuck at this after update  toJira 8.0.x and but when I updated to Jira 8.1.x it disappeared.

david_gianonatti August 21, 2019

I'm doing it, thank you
I'll let you know

Suggest an answer

Log in or Sign up to answer