nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Failure to startup JIRA aftering updating to JIRA 9.0 and MySQL 5.7

Christian Pickman

The other day I decided to update the installed version of JIRA from 8.22.3 to JIRA 9.0.0. Also, since I was getting warnings about not have a supported version of MySQL for a number of months, I also decided to update MySQL from 5.6 (unsupported) to 5.7 (Support). After running the update to JIRA from 8.22.3 to 9.0.0 I get the following message when JIRA starts up:

Database: JIRA couldn't connect to your database

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.

I've tried various possible solutions to resolve the issue but no luck. Here's the setup information I have when I user the 'version.sh' script:

Server startup logs are located in /opt/atlassian/jira/logs/catalina.out
Using CATALINA_BASE: /opt/atlassian/jira
Using CATALINA_HOME: /opt/atlassian/jira
Using CATALINA_TMPDIR: /opt/atlassian/jira/temp
Using JRE_HOME: /opt/atlassian/jira/jre/
Using CLASSPATH: /opt/atlassian/jira/bin/bootstrap.jar:/opt/atlassian/jira/bin/tomcat-juli.jar
Using CATALINA_OPTS:
Using CATALINA_PID: /opt/atlassian/jira/work/catalina.pid
NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
Server version: Apache Tomcat/9.0.62
Server built: Mar 31 2022 14:34:15 UTC
Server number: 9.0.62.0
OS Name: Linux
OS Version: 2.6.32-754.35.1.el6.x86_64
Architecture: amd64
JVM Version: 11.0.13+8
JVM Vendor: Eclipse Adoptium

...everything looks correct, so I must be missing something or need to update my configuration for it to load my instance of JIRA correctly like it did before the updating from version 8.x to 9.x. Any help would be greatly appreciated. Thank you in advance.

Accepted answers

All comments

Mirek

Maybe you can start troubleshooting by looking at this KB article and let us know what is the result of each check

https://confluence.atlassian.com/jirakb/resolve-database-connection-errors-during-jira-server-startup-872262124.html

Christian Pickman

Greetings, and thank you for this referenced article. I tried these steps before and tried them again and this is what I encountered.

1. Performed a ping of localhost, 127.0.0.1 and the static IP address and no issues encountered. No dropped packets.

2. Ran nmap and it would appear there's no issue with the ports assigned for accessing the instance of JIRA (8081) as well as for MySQL (3306):

Nmap scan report for localhost (127.0.0.1)
Host is up (0.0000090s latency).
Not shown: 985 closed ports
PORT STATE SERVICE
22/tcp open ssh
25/tcp open smtp
80/tcp open http
111/tcp open rpcbind
143/tcp open imap
443/tcp open https
465/tcp open smtps
587/tcp open submission
631/tcp open ipp
993/tcp open imaps
3052/tcp open powerchute
3306/tcp open mysql
6547/tcp open powerchuteplus
8081/tcp open blackice-icecap
10000/tcp open snet-sensor-mgmt

Nmap done: 1 IP address (1 host up) scanned in 0.09 seconds

3. The KB article references using Postgres to determine permissions are correct or not for the dbconfig.xml file. However, I am using MySQL and I am not seeing a method to check permissions on the dbconfig.xml file. The port referenced in my dbconfig.xml file is 3306 for mysql which it has always been, so I don't believe it's a port issue especially since nmap confirms that port 3306 is open.

Any other suggestions would be greatly appreciated. Thanks.

chihara_trqpd9

Check dbconfig.xml.

<database-type>mysql57</database-type>

Christian Pickman

When I update the <database-type> with 'mysql57' instead of just 'mysql', I get this error on reload of 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 different. Consider using MySQL 5.7 database type instead
See our documentation for more information on changing database type.

...though when I do a 'mysql -V' at the command line I get this:

mysql Ver 14.14 Distrib 5.7.38, for Linux (x86_64) using EditLine wrapper

Any thoughts on why I get this message from JIRA when I use the <database-type>mysql57</database-type> tag in the dbconfig.xml file? Thanks

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server