[JRASERVER-71060] Jira doesn't start using MySQL 5.7 and setting dbconfig.xml database type to mysql57

Type: Bug
Resolution: Invalid
Priority: High (View bug fix roadmap)
Fix Version/s: None
Affects Version/s: 8.8.0
Component/s: Environment - Database
Labels:

Introduced in Version:
8.08
Support reference count:
6
Symptom Severity:
Severity 2 - Major
UIS:
3
Bug Fix Policy:
View Atlassian Server bug fix policy

Issue Summary

Jira reports incorrectly that MySQL 5.7 database is MySQL 5.6 and won't start Jira when the dbconfig.xml has the database type set to mysql57.

Steps to Reproduce

Install MySQL 5.7 and set the following.

character_set_client utf8
character_set_connection utf8
character_set_database latin1
character_set_filesystem binary
character_set_results utf8
character_set_server latin1
character_set_system utf8
collation_connection utf8_general_ci
collation_database latin1_swedish_ci
collation_server latin1_swedish_ci
version 5.7.30-0ubuntu0.18.04.1

In the dbconfig.xml set the database type to mysql57
Set URL to change the character_endcoding to utf8mb4
Restart Jira

Expected Results

Jira will start and use the MySQL 5.7 database.

Actual Results

Jira won't start as a result of the default settings. with the URL set with character_endcoding= utf8mb4

2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] We've found an error in MySQL supported version!
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR      [c.a.jira.health.HealthChecks] 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.
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR      [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR      [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database.
    This could be because:
    	- Your database isn't running
    	- The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
    	- There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)
    
    There are several other solutions you can try, review our documentation, and see what works for you.

Old keeping for reference - Workaround

Currently, there is no known workaround.

If you change the dbconfig.xml to use the database type mysql rather than mysql57 Jira starts however you will get a collation warning by the health checker stating utf8mb4 is not a supported collation.

Note on Resolution

Steps to reproduce are not in sync with Atlassian guidelines how to configure MySql database.
- According to documentation page, https://confluence.atlassian.com/adminjiraserver088/installing-jira-applications/connecting-jira-applications-to-a-database/connecting-jira-applications-to-mysql-5-7 character_set_server variable should be set to utf8mb4, not latin1 like here.
We verified Jira 8.8.0 with MySql 5.7.24 running inside docker and MySql 5.7.30-0ubuntu0.16.04.1 running on Ubuntu using JDBC drivers 8.0.20 and 5.1.48. There were no problems connecting to and using that database.

relates to

JRASERVER-68926 MySQL 5.7 running utf8mb4_bin throws Health Check error

Closed

HL-1658 You do not have permission to view this issue

mentioned in: Page Failed to load; Page Failed to load; Page Failed to load

split to: HL-1607 Loading...

(1 split to)

Oleksandr Tkachenko made changes - 16/Jun/2023 3:21 PM

Remote Link

Original: This issue links to "HL-1658 (Bulldog)" [ 491243 ]

New: This issue links to "HL-1658 (JIRA Server (Bulldog))" [ 491243 ]

Andriy Yakovlev [Atlassian] made changes - 01/Dec/2021 1:36 PM

Affects Version/s

Original: 8.20.1 [ 97808 ]

Mahtab made changes - 30/Nov/2021 6:59 PM

Description

Original: h3. Issue Summary

Jira reports incorrectly that MySQL 5.7 database is MySQL 5.6 and won't start Jira when the dbconfig.xml has the database type set to mysql57.
h3. Steps to Reproduce
# Install MySQL 5.7 and set the following.
{panel}
character_set_client utf8
character_set_connection utf8
character_set_database latin1
character_set_filesystem binary
character_set_results utf8
character_set_server latin1
character_set_system utf8
collation_connection utf8_general_ci
collation_database latin1_swedish_ci
collation_server latin1_swedish_ci
version 5.7.30-0ubuntu0.18.04.1
{panel}

# In the dbconfig.xml set the database type to mysql57
# Set URL to change the character_endcoding to utf8mb4
# Restart Jira

h3. Expected Results

Jira will start and use the MySQL 5.7 database.
h3. Actual Results

Jira won't start as a result of the default settings. with the URL set with character_endcoding= utf8mb4
{noformat}
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] We've found an error in MySQL supported version!
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] 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.
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database.
    This could be because:
     - Your database isn't running
     - The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
     - There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)

    There are several other solutions you can try, review our documentation, and see what works for you.

{noformat}
h3. Old keeping for reference - Workaround

Currently, there is no known workaround.

If you change the dbconfig.xml to use the database type mysql rather than mysql57 Jira starts however you will get a collation warning by the health checker stating utf8mb4 is not a supported collation.
h3. Note on Resolution
* Steps to reproduce *are not in sync* with Atlassian guidelines how to configure MySql database.
** According to documentaion page [https://confluence.atlassian.com/adminjiraserver088/installing-jira-applications/connecting-jira-applications-to-a-database/connecting-jira-applications-to-mysql-5-7] {{character_set_server}} variable should be set to {{{}utf8mb4{}}}, (!) not _latin1_ like here.
* We verified Jira 8.8.0 with MySql 5.7.24 running inside docker and MySql 5.7.30-0ubuntu0.16.04.1 running on Ubuntu using JDBC drivers 8.0.20 and 5.1.48. (i) There were no problems connecting to and using that database.

New: h3. Issue Summary

Jira reports incorrectly that MySQL 5.7 database is MySQL 5.6 and won't start Jira when the dbconfig.xml has the database type set to mysql57.
h3. Steps to Reproduce
# Install MySQL 5.7 and set the following.
{panel}
character_set_client utf8
character_set_connection utf8
character_set_database latin1
character_set_filesystem binary
character_set_results utf8
character_set_server latin1
character_set_system utf8
collation_connection utf8_general_ci
collation_database latin1_swedish_ci
collation_server latin1_swedish_ci
version 5.7.30-0ubuntu0.18.04.1
{panel}

# In the dbconfig.xml set the database type to mysql57
# Set URL to change the character_endcoding to utf8mb4
# Restart Jira

h3. Expected Results

Jira will start and use the MySQL 5.7 database.
h3. Actual Results

Jira won't start as a result of the default settings. with the URL set with character_endcoding= utf8mb4
{noformat}
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] We've found an error in MySQL supported version!
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] 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.
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database.
    This could be because:
     - Your database isn't running
     - The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
     - There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)

    There are several other solutions you can try, review our documentation, and see what works for you.

{noformat}
h3. Old keeping for reference - Workaround

Currently, there is no known workaround.

If you change the dbconfig.xml to use the database type mysql rather than mysql57 Jira starts however you will get a collation warning by the health checker stating utf8mb4 is not a supported collation.
h3. Note on Resolution
* Steps to reproduce *are not in sync* with Atlassian guidelines how to configure MySql database.
** According to documentation page, [https://confluence.atlassian.com/adminjiraserver088/installing-jira-applications/connecting-jira-applications-to-a-database/connecting-jira-applications-to-mysql-5-7] {{character_set_server}} variable should be set to {{{}utf8mb4{}}}, (!) not _latin1_ like here.
* We verified Jira 8.8.0 with MySql 5.7.24 running inside docker and MySql 5.7.30-0ubuntu0.16.04.1 running on Ubuntu using JDBC drivers 8.0.20 and 5.1.48. (i) There were no problems connecting to and using that database.

Mahtab made changes - 30/Nov/2021 6:58 PM

Description

Original: h3. Issue Summary
Jira reports incorrectly that MySQL 5.7 database is MySQL 5.6 and won't start Jira when the dbconfig.xml has the database type set to mysql57.

h3. Steps to Reproduce
# Install MySQL 5.7 and set the following.
{panel}
character_set_client utf8
character_set_connection utf8
character_set_database latin1
character_set_filesystem binary
character_set_results utf8
character_set_server latin1
character_set_system utf8
collation_connection utf8_general_ci
collation_database latin1_swedish_ci
collation_server latin1_swedish_ci
version 5.7.30-0ubuntu0.18.04.1
{panel}

# In the dbconfig.xml set the database type to mysql57
# Set URL to change the character_endcoding to utf8mb4
# Restart Jira

h3. Expected Results
Jira will start and use the MySQL 5.7 database.

h3. Actual Results
Jira won't start as a result of the default settings. with the URL set with character_endcoding= utf8mb4
{noformat}
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] We've found an error in MySQL supported version!
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] 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.
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database.
    This could be because:
     - Your database isn't running
     - The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
     - There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)

    There are several other solutions you can try, review our documentation, and see what works for you.

{noformat}

h3. Old keeping for reference - Workaround
Currently, there is no known workaround.

If you change the dbconfig.xml to use the database type mysql rather than mysql57 Jira starts however you will get a collation warning by the health checker stating utf8mb4 is not a supported collation.

h3. Note on Resulution
* Steps to reproduce *are not in sync* with Atlassian guidelines how to configure MySql database.
** According to documentaion page [https://confluence.atlassian.com/adminjiraserver088/installing-jira-applications/connecting-jira-applications-to-a-database/connecting-jira-applications-to-mysql-5-7] {{character_set_server}} variable should be set to {{utf8mb4}}, (!) not _latin1_ like here.
* We verified Jira 8.8.0 with MySql 5.7.24 running inside docker and MySql 5.7.30-0ubuntu0.16.04.1 running on Ubuntu using JDBC drivers 8.0.20 and 5.1.48. (i) There were no problems connecting to and using that database.

New: h3. Issue Summary

Jira reports incorrectly that MySQL 5.7 database is MySQL 5.6 and won't start Jira when the dbconfig.xml has the database type set to mysql57.
h3. Steps to Reproduce
# Install MySQL 5.7 and set the following.
{panel}
character_set_client utf8
character_set_connection utf8
character_set_database latin1
character_set_filesystem binary
character_set_results utf8
character_set_server latin1
character_set_system utf8
collation_connection utf8_general_ci
collation_database latin1_swedish_ci
collation_server latin1_swedish_ci
version 5.7.30-0ubuntu0.18.04.1
{panel}

# In the dbconfig.xml set the database type to mysql57
# Set URL to change the character_endcoding to utf8mb4
# Restart Jira

h3. Expected Results

Jira will start and use the MySQL 5.7 database.
h3. Actual Results

Jira won't start as a result of the default settings. with the URL set with character_endcoding= utf8mb4
{noformat}
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] We've found an error in MySQL supported version!
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] 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.
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database.
    This could be because:
     - Your database isn't running
     - The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
     - There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)

    There are several other solutions you can try, review our documentation, and see what works for you.

{noformat}
h3. Old keeping for reference - Workaround

Currently, there is no known workaround.

If you change the dbconfig.xml to use the database type mysql rather than mysql57 Jira starts however you will get a collation warning by the health checker stating utf8mb4 is not a supported collation.
h3. Note on Resolution
* Steps to reproduce *are not in sync* with Atlassian guidelines how to configure MySql database.
** According to documentaion page [https://confluence.atlassian.com/adminjiraserver088/installing-jira-applications/connecting-jira-applications-to-a-database/connecting-jira-applications-to-mysql-5-7] {{character_set_server}} variable should be set to {{{}utf8mb4{}}}, (!) not _latin1_ like here.
* We verified Jira 8.8.0 with MySql 5.7.24 running inside docker and MySql 5.7.30-0ubuntu0.16.04.1 running on Ubuntu using JDBC drivers 8.0.20 and 5.1.48. (i) There were no problems connecting to and using that database.

Mahtab made changes - 30/Nov/2021 6:39 PM

Affects Version/s

New: 8.20.1 [ 97808 ]

Andriy Yakovlev [Atlassian] made changes - 11/Dec/2020 10:03 AM

Link

New: This issue relates to ~~JRASERVER-68926~~ [ ~~JRASERVER-68926~~ ]

Andriy Yakovlev [Atlassian] made changes - 07/Jul/2020 12:08 PM

Description

Original: h3. Issue Summary
Jira reports incorrectly that MySQL 5.7 database is MySQL 5.6 and won't start Jira when the dbconfig.xml has the database type set to mysql57.

h3. Steps to Reproduce
# Install MySQL 5.7 and set the following.
{panel}
character_set_client utf8
character_set_connection utf8
character_set_database latin1
character_set_filesystem binary
character_set_results utf8
character_set_server latin1
character_set_system utf8
collation_connection utf8_general_ci
collation_database latin1_swedish_ci
collation_server latin1_swedish_ci
version 5.7.30-0ubuntu0.18.04.1
{panel}

# In the dbconfig.xml set the database type to mysql57
# Set URL to change the character_endcoding to utf8mb4
# Restart Jira

h3. Expected Results
Jira will start and use the MySQL 5.7 database.

h3. Actual Results
Jira won't start as a result of the default settings. with the URL set with character_endcoding= utf8mb4
{noformat}
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] We've found an error in MySQL supported version!
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] 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.
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database.
    This could be because:
     - Your database isn't running
     - The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
     - There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)

    There are several other solutions you can try, review our documentation, and see what works for you.

{noformat}

h3. Workaround
Currently, there is no known workaround.

If you change the dbconfig.xml to use the database type mysql rather than mysql57 Jira starts however you will get a collation warning by the health checker stating utf8mb4 is not a supported collation.

New: h3. Issue Summary
Jira reports incorrectly that MySQL 5.7 database is MySQL 5.6 and won't start Jira when the dbconfig.xml has the database type set to mysql57.

h3. Steps to Reproduce
# Install MySQL 5.7 and set the following.
{panel}
character_set_client utf8
character_set_connection utf8
character_set_database latin1
character_set_filesystem binary
character_set_results utf8
character_set_server latin1
character_set_system utf8
collation_connection utf8_general_ci
collation_database latin1_swedish_ci
collation_server latin1_swedish_ci
version 5.7.30-0ubuntu0.18.04.1
{panel}

# In the dbconfig.xml set the database type to mysql57
# Set URL to change the character_endcoding to utf8mb4
# Restart Jira

h3. Expected Results
Jira will start and use the MySQL 5.7 database.

h3. Actual Results
Jira won't start as a result of the default settings. with the URL set with character_endcoding= utf8mb4
{noformat}
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] We've found an error in MySQL supported version!
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] 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.
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database
2020-04-27 08:39:23,137-0700 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database.
    This could be because:
     - Your database isn't running
     - The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)
     - There is a network issue between JIRA and your database (e.g. firewall, database doesn't allow remote access etc.)

    There are several other solutions you can try, review our documentation, and see what works for you.

{noformat}

h3. Old keeping for reference - Workaround
Currently, there is no known workaround.

If you change the dbconfig.xml to use the database type mysql rather than mysql57 Jira starts however you will get a collation warning by the health checker stating utf8mb4 is not a supported collation.

h3. Note on Resulution
* Steps to reproduce *are not in sync* with Atlassian guidelines how to configure MySql database.
** According to documentaion page [https://confluence.atlassian.com/adminjiraserver088/installing-jira-applications/connecting-jira-applications-to-a-database/connecting-jira-applications-to-mysql-5-7] {{character_set_server}} variable should be set to {{utf8mb4}}, (!) not _latin1_ like here.
* We verified Jira 8.8.0 with MySql 5.7.24 running inside docker and MySql 5.7.30-0ubuntu0.16.04.1 running on Ubuntu using JDBC drivers 8.0.20 and 5.1.48. (i) There were no problems connecting to and using that database.

Mikolaj Rydzewski (Inactive) made changes - 07/Jul/2020 10:01 AM

Resolution		New: Invalid [ 6 ]
Status	Original: In Progress [ 3 ]	New: Closed [ 6 ]

Mikolaj Rydzewski (Inactive) made changes - 03/Jul/2020 11:46 AM

Status

Original: Short Term Backlog [ 12074 ]

New: In Progress [ 3 ]

Mikolaj Rydzewski (Inactive) made changes - 03/Jul/2020 11:46 AM

Assignee

New: Mikolaj Rydzewski [ mrydzewski ]

Assignee:: Mikolaj Rydzewski (Inactive)

Reporter:: Eric Storch (Inactive)

Affected customers:: 4 This affects my team

Watchers:: 18 Start watching this issue

Created:: 18/May/2020 3:47 PM

Updated:: 16/Jun/2023 3:21 PM

Resolved:: 07/Jul/2020 10:01 AM

Jira Data Center

Details

Description

Issue Summary

Steps to Reproduce

Expected Results

Actual Results

Old keeping for reference - Workaround

Note on Resolution

Attachments

Issue Links

Forms

Activity

People

Dates