Jira won't start properly after upgrade from 8.15.0 to 8.19.0

[Andrew Howey]

This instance of Jira was flagged by Nessus as needing to be updated to remediate a potential vulnerability.  I went through the upgrade preliminary steps (backups, etc.)  then downloaded the 8.19.0 bin file and ran it.  After the update, when I run "service jira start", it seems to start, but when I try to log into Jira itself, it complains about "error in MySQL supported version".  

I've tried changing the "default_storage_engine" to mysql57 with no success.  I reverted it back to InnoDB, still with no success.  I don't know what else to do.

The database (MySQL 5.7.31) is on an AWS RDS instance.  The Jira host is running on Ubuntu 16.04.7 LTS

It's not feasible to roll back to 8.15.0, as Jira complains about a data version mismatch.

[Martin Bayer _MoroSystems_ s_r_o__]

HI @Andrew Howey , it is always good idea to check a atlassian-jira.log file. Did you check it? Can you share what errors/exceptions occured?

[Andrew Howey]

@Martin Bayer _MoroSystems_ s_r_o__ -- This is what I see in the atlassian-jira.log:

2021-09-02 16:21:32,903+0000 JIRA-Bootstrap ERROR      [c.a.config.bootstrap.DefaultAtlassianBootstrapManager] Could not successfully test your database:

at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:990)

2021-09-02 16:21:32,907+0000 JIRA-Bootstrap ERROR      [c.a.jira.health.MySQLHealthCheckTemplate] There is database configuration error!

at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:990)

2021-09-02 16:21:32,937+0000 JIRA-Bootstrap ERROR      [c.a.config.bootstrap.DefaultAtlassianBootstrapManager] Could not successfully test your database:

at com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:990)

2021-09-02 16:21:32,940+0000 JIRA-Bootstrap ERROR      [c.a.jira.health.HealthChecks] We've found an error in MySQL supported version!

2021-09-02 16:21:32,940+0000 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 different. Consider using MySQL 5.7 database type instead

2021-09-02 16:21:32,941+0000 JIRA-Bootstrap ERROR      [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database

2021-09-02 16:21:32,941+0000 JIRA-Bootstrap ERROR      [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database.

FWIW, our database is hosted on an AWS RDS instance.  I can connect to it from the command line.

[Andrew Howey]

Here is the version information as given by the database itself:

(jira@govcloud-jira-rds.cyx8nrstcyts.us-gov-west-1.rds.amazonaws.com) [govcloud_jira]> show variables like '%version%';
+-------------------------+-----------------------+
| Variable_name | Value |
+-------------------------+-----------------------+
| innodb_version | 5.7.31 |
| protocol_version | 10 |
| slave_type_conversions | |
| tls_version | TLSv1,TLSv1.1,TLSv1.2 |
| version | 5.7.31-log |
| version_comment | Source distribution |
| version_compile_machine | x86_64 |
| version_compile_os | Linux |
+-------------------------+-----------------------+

And here is the database connect string from the dbconfig.xml:

<url>jdbc:mysql://govcloud-jira-rds.cyx8nrstcyts.us-gov-west-1.rds.amazonaws.com:3306/govcloud_jira?useUnicode=true&amp;characterEncoding=UTF8&amp;sessionVariables=default_storage_engine=InnoDB</url>

[Martin Bayer _MoroSystems_ s_r_o__]

Hi @Andrew Howey you also need to use correct driver's version. Can you check against supported platforms page for your version?

https://confluence.atlassian.com/adminjiraserver/supported-platforms-938846830.html

[Andrew Howey]

Hi, @Martin Bayer _MoroSystems_ s_r_o__  -- The driver listed for Ubuntu (Connector/J 8.0.26) is for 18.04, 20.04, and 21.04.  My jira server is running on 16.04.  Can I use one of the drivers listed for 18.04?  If so, which one would be appropriate?

[Andrew Howey]

This is my OS information;

$ lsb_release -a

No LSB modules are available.

Distributor ID: Ubuntu

Description: Ubuntu 16.04.7 LTS

Release: 16.04

Codename: xenial

$ uname -a
Linux govcloud-jira-00.spop.gov.shn 4.4.0-1122-aws #136-Ubuntu SMP Tue Feb 16 22:44:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

[Martin Bayer _MoroSystems_ s_r_o__]

I'd try to use platform independent release 5.1.49

https://downloads.mysql.com/archives/get/p/3/file/mysql-connector-java-5.1.49.tar.gz

[John Carmichael]

I have the same issue 

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Codename: bionic

I tried the .48 and .49-bin.jar driver but it just wont connect and does not give any useful information in the logs.

SO post:  https://serverfault.com/questions/1076510/jira-upgrade-8-19-0-cannot-connect-to-mysql-5-7-35

Rolling back to jira 8.16.0

[John Carmichael]

.

[Andrew Howey]

Since my database is hosted on an AWS RDS instance, I was able to restore the most recent snapshot and roll back to 8.15.0 that way.

I'll have to revisit the upgrade to 8.19.0 after some consideration and planning.

Thanks @Martin Bayer _MoroSystems_ s_r_o__  for all your suggestions.  :)

[Guillaume TAILLIER]

Have you found a way to upgrade to the latest version?

[Rose Ridder]

8.19.0 introduced a new version of Java which caused a set of command line option errors. Have you checked the catalina.out log for the setup logs? If the issue is from the java update, it will reference encountering the unknown arguments in that log file. Then you have two options: ignoring those arguments by adjusting your setenv.sh file for the startup arguments (that's on the last line of the file), or you can update your java version.
Take a look at https://confluence.atlassian.com/jirakb/change-the-java-version-used-by-jira-server-765594330.html