Unable to start JIRA. java.lang.NoClassDefFoundError: com/atlassian/jira/health/checks/database/MySq

[mitesupport]

When we are restarting the Atlassian JIRA We are unable to get the JIRA Service Desk to be started due to the below exception.

Unable to start JIRA.
java.lang.NoClassDefFoundError: com/atlassian/jira/health/checks/database/MySqlJdbcUrlHealthCheck
atcom.atlassian.jira.health.HealthCheckRegistrar.registerHealthChecks(HealthCheckRegistrar.java:51)
atcom.atlassian.jira.health.HealthChecks.runHealthChecks(HealthChecks.java:153)
atcom.atlassian.jira.health.HealthChecks.runHealthChecks(HealthChecks.java:66)
atcom.atlassian.jira.startup.BootstrapContainerLauncher.start(BootstrapContainerLauncher.java:32)
atcom.atlassian.jira.startup.DefaultJiraLauncher.preDbLaunch(DefaultJiraLauncher.java:117)
atcom.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:103)
atcom.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
atcom.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:102)
atcom.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
atjava.lang.Thread.run(Thread.java:748)
Caused by: java.lang.ClassNotFoundException: com.atlassian.jira.health.checks.database.MySqlJdbcUrlHealthCheck
atorg.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1364)
atorg.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1185)
... 10 more

[Nic Brough -Adaptavist-]

This means that either your Jira installation is damaged (missing/corrupt deployed files), you can't access the installation files (permissions on the file system?) or you are running with an unsupported version of Java.

In the first case, it might also be just a missing mysql driver, but there's not enough of the error message here to say that with any confidence.

Could you check:

• What version of Jira it is
• What version of Java it is running
• If the mysql driver file(s) are in the right place
• That the installation (and data) directories your Jira is in are all owned by the user running it

[mitesupport]

1. JIRA Version is 8.2.2.

2. Java Version is 1.8.0_121.

3. Our JIRA Service Desk is deployed on H2 Embedded Database and not on MySql database.Please send us that particular Jar file which it is looking for.

4. JIRA Installation Directory as well as JIRA Data directory has access to the User running it.

[Nic Brough -Adaptavist-]

Ah, there's another case that I suspect is happening here.

If you read further through the error, I suspect you'll find that there's a preceding error in it trying to look at your h2 database.  If it fails to do that, it then goes looking for healthchecks on other databases (such as mysql) and can then trigger errors such as this one.

I strongly suspect that your h2 database is corrupted and unreadable.

Could you read back through the log to where the errors first started to occur as it starts up and check to see if the first mention not being able to read the h2 database?

If it is that, then you'll need to get a clean install of Jira (ideally hook it up to a supported database) and restore from the last backup

[mitesupport]

Hi Team,

Getting this exception while trying to read the database which is in the dbconfig.xml.

The Database configured is H2Embeeded database.

Please see the exception which is occurring while connecting to the same database from the DBeaver Client.The size of the DB file is 24GB...

I am not able to track anywhere that it is trying to read the database file of H2, but while stopping the JIRA Service it is trying to read.

Pattern is it is checking the MYSQL Database file and stopping to start the JIRA since no database is available.But we have the H2 DB Configuration in the dbconfig.xml file.

We need the JIRA download for the 8.2.2 Version which we will cross check any jars are missing.

[Nic Brough -Adaptavist-]

You are "barking up the wrong tree" here. 

When you say "Pattern is it is checking the MYSQL Database file and stopping to start the JIRA since no database is available.But we have the H2 DB Configuration in the dbconfig.xml file."

That is not quite what it is doing.  As I said before, what it is doing it trying to read the H2 database, failing, and then moving on to do a general database health check, which is throwing the error about a missing mysql driver.

>We need the JIRA download for the 8.2.2 Version which we will cross check any jars are missing.

While you are missing the mysql driver jar, that is not the problem here.  You are missing it because you have to install it manually due to licence restrictions if you want to use MySQL for the database.   You didn't install it becuase you went with h2.  But you don't need it, and all it will do is remove the mysql driver error from the logs. 

The rest of your errors will still happen, and your Jira will still fail to work.  Just installing that driver is not going to fix your problem, you've got a broken h2 database and you need to fix that.

[mitesupport]

Can we have the Web-ex conference or Zoom Conference in order for me to show the exception and debug further. Video platform to fix the issue

[Nic Brough -Adaptavist-]

Um.

1. We're not support, we're a community of people talking about (and trying to help with) Atlassian stuff
2. A video conference is not going to help.  All you would get is someone repeating what has been said above

Your next steps are:

1. Add the mysql driver (please see the Jira installation documents for your version on how to do that). 

There's a 99.99% chance this will do nothing more useful than get rid of one error in the logs, your Jira is still going to fail because of the actual problem

2. Fix your H2 database, as it is damaged and that damage is making Jira fail