Jira startup fails with message that required plugins are not started

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

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


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.


The bundled-plugins is created as a default pack of plugins that is required for JIRA application to function properly. In some occasions, these plugins may not be useful for a user. Nevertheless, it is crucial to have all plugins in the bundled-plugins to be loaded when JIRA application is starting up.

This relates to the following JIRA application bug:  JRA-22633 - Getting issue details... STATUS

There is also an Improvement request to better handle this scenario: JRA-24968 - Getting issue details... STATUS


Always back up your data before performing any modification to the database. If possible, try your modifications on a test server.

  1. 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.

  2. Enable any plugin(s) that is disabled using the SQL query below:

    DELETE FROM pluginstate WHERE pluginkey='<pluginkey from query above>';

    (info) 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.%';
  3. Restart JIRA application.
Last modified on Apr 13, 2020

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.