Jira had problems starting up

Question

Caused by: java.nio.BufferUnderflowException at java.nio.Buffer.nextGetIndex(Buffer.java:506) at java.nio.HeapByteBuffer.getShort(HeapByteBuffer.java:310) at org.h2.mvstore.Page.read(Page.java:646) at org.h2.mvstore.Page.read(Page.java:194) at org.h2.mvstore.MVStore.readPage(MVStore.java:1830) at org.h2.mvstore.Page.getChildPage(Page.java:216) at org.h2.mvstore.Cursor.fetchNext(Cursor.java:150) at org.h2.mvstore.Cursor.next(Cursor.java:50) at org.h2.mvstore.MVStore.readFileHeader(MVStore.java:696) at org.h2.mvstore.MVStore.(MVStore.java:357) at org.h2.mvstore.MVStore$Builder.open(MVStore.java:2769) at org.h2.mvstore.db.MVTableEngine$Store.(MVTableEngine.java:162) at org.h2.mvstore.db.MVTableEngine.init(MVTableEngine.java:98) at org.h2.engine.Database.getPageStore(Database.java:2379) at org.h2.engine.Database.open(Database.java:666) at org.h2.engine.Database.openDatabase(Database.java:266) ... 41 more 2020-10-14 14:27:48,265 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] JIRA couldn't connect to your database 2020-10-14 14:27:48,265 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] 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. 2020-10-14 14:27:48,359 JIRA-Bootstrap INFO [c.a.jira.startup.JiraStartupLogger] Running JIRA startup checks. 2020-10-14 14:27:48,359 JIRA-Bootstrap FATAL [c.a.jira.startup.JiraStartupLogger] Startup check failed. JIRA will be locked. 2020-10-14 14:27:51,156 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage: --------------------------------------------------------------------------------- Heap memory : Used: 265 MiB. Committed: 638 MiB. Max: 2046 MiB Non-heap memory : Used: 40 MiB. Committed: 63 MiB. Max: 1536 MiB --------------------------------------------------------------------------------- TOTAL : Used: 305 MiB. Committed: 701 MiB. Max: 3582 MiB

Daniel Ebers · Answer

This is something what is regularly to be read here in community when using H2 databases. They seem to be sensible to hard shutdown and tend to go bust from time to time.

As per documentation (https://confluence.atlassian.com/adminjiraserver0713/connecting-jira-applications-to-a-database-964983091.html) the H2 database is only intended for evaluation purposes. You should migrate to a common database (PostgreSQL is a good example) as soon as you start to go into production.

For the current problem I cannot give you any thorough advise but to try to get the H2 database online somehow - or if present - to restore from a backup.
As soon as this is done I'd recommend considering switching to a different database. Please see this knowledge base article for more information:
https://confluence.atlassian.com/adminjiraserver0713/switching-databases-964983111.html#Switchingdatabases-differenttype

In case you have questions or specific obstacles during this journey I am sure somebody from Community will be happy to help.

Cheers,
Daniel

bill zeng · Answer

Actually This server is used for almost one year, it is working well.

but two days before , during the weekend, office got power trip.

On Monday , we power on the server and it got this problem.

So I don't think the dbconfig.xml is wrong as we used for quite long time and never change it.

if the user name and password wrong the description will be quite clear. the log will tell you cannot authorize ....

anyway I will compare xml again.

Dave Theodore [Coyote Creek Consulting] · Answer

Since you're using the h2 DB, I think this line contains your answer:

- The configuration of your dbconfig.xml file is incorrect (user, password, or database URL etc.)

It might be worth installing a fresh instance of Jira somewhere, connect it to h2, and then compare the dbconfig.xml file from that instance your production instance dbconfig.xml. Is your JIRA_HOME set to the right directory?