Jira Data Center startup fails with a message that required plugins are not started
Platform Notice: Data Center Only - This article only applies to Atlassian apps 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
If any bundled plugins are disabled in Jira application, then the following errors will be generated in atlassian-jira.log:
********************************************************************************
JIRA 4.3.4 build: 620 started. You can now access JIRA through your web browser.
********************************************************************************
2011-06-26 15:26:23,639 main FATAL [atlassian.jira.startup.JiraStartupLogger]
***********************************************************************************************************************
The following plugins are required by JIRA, but have not been started: FishEye Plugin (com.atlassian.jirafisheyeplugin)
***********************************************************************************************************************
2011-06-26 15:26:23,661 main FATAL [atlassian.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked.
2011-06-26 15:26:23,661 main INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] JIRA Scheduler not started: JIRA startup checklist failed.
2011-06-26 15:26:24,118 main FATAL [jira.web.dispatcher.JiraWebworkActionDispatcher]
******************************************
JIRA startup failed, JIRA has been locked.
******************************************Cause
The bundled-plugins are created as a default pack of plugins that are required for the Jira application to function properly. Disabling or uninstalling any bundled or core plugins, or their dependent plugins, can result in system errors due to unresolved dependencies or changes to the plugin load order. It is crucial to have all plugins in the bundled-plugins to be loaded when the Jira application is starting up. In some occasions, these plugins may not be useful for a user.
This relates to the following Jira application bug: JRASERVER-22633 - JIRA starts up in unworkable stage if core plugin is not started
There is also an Improvement request to better handle this scenario: JRASERVER-24968 - Exclude non critical plugins from being included the failed initiation check
Resolution
Always back up your data before making any database modifications. If possible, test any alter, insert, update, or delete SQL commands on a staging server first. Note that certain directory-related corrections might require stopping Jira to avoid further inconsistencies or data loss, and no alternatives for avoiding downtime currently exist.
Execute the SQL below to check for any disabled plugin(s):
SELECT * FROM pluginstate where pluginenabled = 'false';If this query does not return any rows, then the resolution outlined in this document is not applicable for your JIRA application instance. If there are valid rows returned, then please proceed to step number 2.
Enable any plugin(s) that is disabled using the SQL query below:
DELETE FROM pluginstate WHERE pluginkey='<pluginkey from query above>';ℹ️ If there are system plugins involved then these should be deleted from the table, ones that start with com.atlassian.%
DELETE FROM pluginstate WHERE pluginkey LIKE 'com.atlassian.%';Restart the Jira application. For clustered environments, follow a sequential node restart process: shut down all nodes, start each node one at a time, and allow it to fully initialize before starting the next node. This helps prevent file access conflicts and ensures proper plugin initialization.
Deleting Jira plugin cache on all the nodes and on the shared-home
If the above steps did not work , you can also try deleting Jira plugin cache on all the nodes and on the shared-home:
Delete JIRA_HOME/plugins/.bundled-plugins ( This folder will be re-created in the next start-up ) for each Node
Delete JIRA_HOME/plugins/.osgi-plugins ( This folder will be re-created in the next start-up ) for each Node
Delete SHARED_HOME/plugins/.bundled-plugins ( This folder will be re-created in the next start-up )
Delete SHARED_HOME/plugins/.osgi-plugins ( This folder will be re-created in the next start-up )
Delete the content of JIRA_INSTALL/work directory (only the content, keep the folder empty) for each Node
Delete the content of JIRA_INSTALL/temp directory (only the content, keep the folder empty) for each Node
Was this helpful?