Jira throws "Could not determine database type Unknown storage engine InnoDB" when starting

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Problem

When starting up Jira the following error appears when attempting to access the application:

(Auto-migrated image: description temporarily unavailable)

The following appears in the atlassian-jira.log:

1 org.ofbiz.core.util.GeneralRuntimeException: Could not determine database type. (Unknown storage engine 'InnoDB')

Environment

Jira Data Center with MySQL.

Cause

In this case, after updating the innodb_log_file_size there was a missed step(ie. removing the existing transaction logs) in the procedure causing problems when starting MySQL.

Resolution

For further explanation on common problems when setting the innodb_log_file_size, please read MySQL: Failed Registration of InnoDB as a Storage Engine.

ℹ️ Please refer to MySQL documentation for more details on InnoDB options and parameters: InnoDB Startup Options and System Variables

Updated on April 11, 2025

Still need help?

The Atlassian Community is here for you.