Update from 8.12 to 8.13 damages the database connection settings

[cenglert]

Hi Atlassian-Community,

after the update from JIRA Software (Server) 8.12 to 8.13 my instance i no more able to connect its database.

The following error message appears:

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.)

Initially i tried to upgrade from 8.11 to 8.22 with the same result. I restored my backups several times and made my JIRA updates in smaller steps of releases. So i could find out, that the error apears between the update 8.12 to 8.13 release.

Database is up and running. A parallel Confluence (7.6.2) installation is still function, but has the same problems when a try to upgrade to very new release.

So i wonder, what has changed in the meantime, that the old database settings are no more working.

I tried to fix them with that documentation but the JDK and the config.sh script won´t work, too:
https://confluence.atlassian.com/adminjiraserver/tuning-database-connections-938846864.html

So i tried several things the last days and weeks now. My goal is to upgrade my system from 8.11 to the newest release (and later also for Confluence).

But i have problems to find a relevant document or technical paper, on what to look for.

Can you help me or do you have some tips or a clear upgrade documentation?

Best regards

Christian

[Robert Wen_Cprime_ · Accepted solution]

There's a note here about Jira not working with MySQL 5.7 community edition if Jira is using specific JRE versions.  You should probably check that out.

https://confluence.atlassian.com/adminjiraserver0813/supported-platforms-1027137429.html

[cenglert]

Hi together,

there is a little update from my side.

I additionally installed PhpMyAdmin to check and control the databases on a better
and more comfortable way.

Again, i can confirm, that i´m able to logon and connect to all databases, using all atlassian-based users (as i used before).

My confluence instance (on the same linux server) is still running and able to connect it´s database. Only the JIRA instance is not able to connect.

I tried to delete the dbconfig.xml and start the connection and re-configuration process again, on the JIRA startup interface. But when i type in the logon and connection credentials i and click to "test connection", i got the error message:
"No appropriate protocol (protocol is disabled or cipher suites are inappropriate)"

[Tim Perrault]

@cenglert 

Take a look at this KB Article it's for confluence, but I'm betting it's the same issue.

Thanks,

Tim

[Tim Perrault]

Hi @cenglert 

When you updated, did you re-apply modification and increase max-pool-size?

Some of the files we usually modify:

• server.xml
• dbconfig.xml
• jira-config.properties
• web.xml
• setenv.sh / setenv.bat (memory allocation and other JVM arguments)

I would make sure when you upgrade that the dbconfig.xml is updated to your needs.

Thanks,

Tim

[Robert Wen_Cprime_]

Hello @cenglert ! Welcome to the Atlassian Community!

One thing you didn't mention was what database are you using?

[cenglert]

Hi Wen, hi Tim,

i checked all files of these documentation... also again after the upgrade. i compared them with the old versions of the backup. The content seem to be exactly the same (checked it with "diff")

Only the setenv.sh hat one other memory allocation (the jvm maximimum memory allocation). All other lines and values were the same as before.

... especially the dbconfig.xml - absolutely nothing was changed!

About the database itself: it is a MySQL 5.7 Server on the localhost of the jira installation.

Do you need some more information?

Thank you for your help

Best regards

Christian

[Tim Perrault]

Can you login to the DB with the username and password listed in the dbconfig.xml directly to verify it's not user related?

It sounds like you upgrade and then when you start Jira it doesn't start correctly because it can't get to the database. If it can't get to the database then nothing on the database has changed. There is a connection issue somewhere.

[cenglert]

Hi Tim,

thanks for the good communication and the fast answers ;-)

Yes, i can connect and proove the db-connection manually via mysql on the terminal and also using the MySQL Workbench on a desktop.

The user credentials are still the same and still visible in the dbconfig.xml.

Best regards

Christian