Jira Doesn't start

Question

Jira doesnt startup. I see the below on logs.

java.lang.IllegalStateException: Reading from cache:nio:/var/atlassian/application-data/jira/database/h2db.mv.db failed; file length 100139008 read length 76
8 at 100198358 [1.4.185/1]

2020-03-23 00:26:58,282 JIRA-Bootstrap ERROR [c.a.config.bootstrap.DefaultAtlassianBootstrapManager] Could not successfully test your database:
org.h2.jdbc.JdbcSQLException: General error: "java.lang.IllegalStateException: Reading from cache:nio:/var/atlassian/application-data/jira/database/h2db.mv.db failed; f
ile length 100139008 read length 768 at 100198358 [1.4.185/1]" [50000-185]

2020-03-23 00:26:58,400 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database
2020-03-23 00:26:58,400 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA failed to establish a connection to your database.

2020-03-23 00:26:58,405 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks.
2020-03-23 00:26:58,405 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. JIRA will be locked.

Nic Brough -Adaptavist- · Answer

I am really sorry, but this usually means that your h2 database has failed.

h2 is not intended to be used as a real database, it's just for dev/test/play and should never be used for any system you want to keep as a working system (even UAT or longer-term test systems).  It does not scale, and is know to fail catastrophically in some cases.

I would definitely check for a backup and restore that to a supported database (PostGreSQL and MySQL are supported, free, and low enough on resources that you can usually run them locally on the same machine as Jira)

Petter Gonçalves · Answer

Hello @HARISH KUMAR SIVAKUMAR

Thank you for the details provided.

While you check on option 3, I will keep searching for other possibilities that could be causing the error.

HARISH KUMAR SIVAKUMAR · Answer

Thanks for the response.

I Use Jira's embedded Database.

Yes, the application was up and running for three months. No updates on Jira / DB was done.

Let me check the option 3