Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

jira startup failed

System plugins failed to start: We haven't been able to start all the required system plugins

We couldn't start the following plugins:

  • Gadget Directory Plugin (
  • Atlassian Jira - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)
  • Atlassian Jira - Plugins - Global Issue Navigator (com.atlassian.jira.jira-issue-nav-plugin)
  • Atlassian JIRA - Plugins - Quick Edit Plugin (com.atlassian.jira.jira-quick-edit-plugin)
  • Atlassian Jira - Plugins - REST Plugin (



2 answers

1 accepted

0 votes
Answer accepted

@weeisc  This  is for sure as a result of  corrupted  plugin cache files  or corrupted  jar  files in the   bundled plugins folder.  To clear  plugin cache

Resolution 1

  1. Stop the JIRA instance
  2. Keep back up in case of JIRA_HOME/plugins/.bundled-plugins and JIRA_HOME/plugins/.osgi-plugins
  3. Delete JIRA_HOME/plugins/.bundled-plugins and JIRA_HOME/plugins/.osgi-plugins (just these two folders)
  4. Restart JIRA

if it does not work  then  try to fix corrupted jar files in bundled plugin folder.

Resoltion 2

This one  is a bit tricky

  1. Stop the JIRA instance
  2.  Keep back up(lets say some where not in the same bundled plugins folder) these plugins jar files  are  in <jira-install>/atlassian-jira/WEB-INF/atlassian-bundled-plugins
  3. Rename these jar files  for example jira-quick-edit-plugin.jar to jira-quick-edit-plugin0.jar
  4. Restart JIRA. If all is fine, then stop JIRA and rename it back as it was. Then start JIRA again.

I was able to fix my issue this way


Good luck!.

Thanks for your help

Moses Thomas Community Leader Nov 03, 2019

@weeisc You welcome !

Like oscarraygoza likes this

@Moses Thomas thanks works for me as well, but what is the reason behind it?

Moses Thomas Community Leader Jul 16, 2021

@Ahsan This reason is mentioned above in the answer ;)

Also , if it is a timeout issue - try increasing the time declared for starting plugins .

This can be defined in your jvm parameters.


Datlassian.plugins.enable.wait=500 ( or value as per your perusal - but i would say 500 is more than enough)

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you