Greetings, I tried to upgrade to JIRA 7 Software today from 6.4.6 + agile. In the end got error The following plugins are required by JIRA, but have not been started: * Gadget Directory Plugin (com.atlassian.gadgets.directory) * Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets) * Atlassian JIRA - Plugins - Issue Search (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 (com.atlassian.jira.rest) Things checked: * java version compatibility * all plugins are up to date prior to upgrade. Only third party I have is JIRA Client from almworks. * all steps in migration hub. * License for JIRA 6 valid until January 2016 Things tried: * increase -Datlassian.plugins.enable.wait=300 from original 60. Longer timeout wait did not help * increase memory limit to 1024 from original 768 * deleted plugin caches .bundled-plugins and .osgi-plugins * with and without apache proxy Log is huge so I hosted it at http://pastebin.com/im3tAWA1 Anything I missed in the upgrade process? Thanks.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira 7 upgrade Startup Failed

alextechadventures

Greetings,

I tried to upgrade to JIRA 7 Software today from 6.4.6 + agile. In the end got error

The following plugins are required by JIRA, but have not been started:

Gadget Directory Plugin (com.atlassian.gadgets.directory)
Atlassian JIRA - Plugins - Gadgets Plugin (com.atlassian.jira.gadgets)
Atlassian JIRA - Plugins - Issue Search (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 (com.atlassian.jira.rest)

Things checked:

java version compatibility
all plugins are up to date prior to upgrade. Only third party I have is JIRA Client from almworks.
all steps in migration hub.
License for JIRA 6 valid until January 2016

Things tried:

increase -Datlassian.plugins.enable.wait=300 from original 60. Longer timeout wait did not help
increase memory limit to 1024 from original 768
deleted plugin caches .bundled-plugins and .osgi-plugins
with and without apache proxy

Log is huge so I hosted it at http://pastebin.com/im3tAWA1

Anything I missed in the upgrade process? Thanks.

Accepted answers

alextechadventures

Got answer from Atlassian support. The problem is there are some dependencies that must have been optional in 6.4 that are now required in 7. If these dependencies have been disabled due to some temporary load issue in the past, the installer keeps their state as disabled but then cannot turn on after upgrade. To force turn them all back on execute

update pluginstate set pluginenabled='true';

in your database. Don't worry if there are incompatible plugins. JIRA 7 will disable them on startup and you can update them or disable again in control panel after it turns on.

All comments

Nic Brough -Adaptavist-

Well, you do have some problems with timeouts, and that would tempt me to increase the enable.wait to more than 300. You've got several addons as well, including large ones, so I'd also increase the memory to 1.5Gb.

However, the most important thing is the hideous error at the end that tells you it can't write to the disk

org.apache.catalina.startup.HostConfig.start Unable to create directory for deployment: /opt/atlassian/jira/conf/Catalina/localhost

You need to fix that and start again - check the permissions and disk space.

alextechadventures

Thanks for pointing that one out. Should have noticed it. Did not work, however. Giving it permissions to JIRA user only changes the last output lines to 2015-10-10 22:40:14,694 localhost-startStop-1 INFO [c.a.jira.startup.LauncherContextListener] Memory Usage: --------------------------------------------------------------------------------- Heap memory : Used: 304 MiB. Committed: 678 MiB. Max: 740 MiB Non-heap memory : Used: 188 MiB. Committed: 206 MiB. Max: 1264 MiB --------------------------------------------------------------------------------- TOTAL : Used: 493 MiB. Committed: 883 MiB. Max: 2004 MiB --------------------------------------------------------------------------------- 2015-10-10 22:40:15,053 localhost-startStop-1 ERROR [c.a.j.web.dispatcher.JiraWebworkActionDispatcher] ****************************************** JIRA startup failed, JIRA has been locked. ****************************************** 11-Oct-2015 08:59:14.869 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"] 11-Oct-2015 08:59:14.885 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 110407 ms 2015-10-11 08:59:15,850 Modification Check:thread-1 INFO [c.a.jira.startup.JiraStartupLogger] Gave it 600 seconds and 2048 memory. Disk has 33Gb free. Interesting that JIRA installer would not have all permissions correctly applied. Is that something worth reporting to official support/bug? There are no problems starting up 6.4 by restoring backup directories. There are a lot of useless looking plugins popping up indeed, such as trello import and similar, which I would disable on first opportunity.

Nic Brough -Adaptavist-

The permissions are not changed by the installer, that's a function of your OS setup. It just creates the directories you need in the home place you tell it to. The reason for startup failing isn't in the piece of log you've given us, so there's not much we can tell you.

Julian Radünz

I have exactly the same problem and have been trying the same things to solve it.

No success yet.

Neither increasing memory significantly nor atlassian.plugins.enable.wait increase helps.
Restoring the backup jira_server directory leads to a working JIRA 6.

Nic Brough -Adaptavist-

Well, the main error in the original question was actually that the disk permissions have been messed up outside JIRA. But, what are you trying to run here? Just an empty JIRA 7? Or an upgrade? If it's an upgrade, what does the log say about the upgrade process? If it's not, then what does the log say about the startup, how much memory have you got and what's the CPU like?

Julian Radünz

Hi Nic, it is an upgrade from JIRA 6.4. The JIRA log doesn't say anything about the upgrade process - I guess the upgrade part (database migration,...) starts after successful JIRA startup. CPU: 2 core RAM: 6 Gb JIRA Logfile: https://s3-eu-west-1.amazonaws.com/comoqm/catalina.out Installation logfile: https://s3-eu-west-1.amazonaws.com/comoqm/installation.log The Installation Log is showing an error at the end which seems to be related to the problem, but not sure what it means.

Nic Brough -Adaptavist-

I can't open those files, so I'm a bit stuck. On the memory, how much are you allocating to JIRA?

Neil Taylor

I had this issue; I tried the upgrade again and this time I disabled all plugins prior to upgrading and it worked like a charm - maybe try this is you haven't and you have the available backups to do this

alextechadventures

I want to try this. Of all the plugins listed in startup logs only a few are controllable through admin panel. Is it sufficient to disable just those or do I have to go deeper prior to upgrade?

Neil Taylor

I disabled just the user installed plugins - I didn't go into system plugins - basically just disabled what would get disabled if you put it into "Safe Mode" - good luck!

alextechadventures

No, didn't help. Disabled the 2 user installed plugins I had - Agile and Client - and put it to safe mode but those 5 built in plugins still do not want to turn on.

alextechadventures

update pluginstate set pluginenabled='true';

in your database. Don't worry if there are incompatible plugins. JIRA 7 will disable them on startup and you can update them or disable again in control panel after it turns on.

Julian Radünz

Nothing but this did help:

Set up a completely new machine "Sandbox"
Install empty JIRA 7. It starts successfully.
Copy DB from Prod JIRA to "Sandbox" JIRA
Point "Sandbox" JIRA to copied Prod DB
Upgrade task will be completed successfully
Shutdown, copy missing plugins to jira_home
Startup - everything works fine

Tchad Rogers

Thank you! This worked for me after days of pulling my hair out and restoring from backups several times!

Tim Smith

This worked for me too. Thank you, saved me a lot of time.

Dave Coleman

You are a lifesaver. Thanks.

unknown

I got the same Issue on our Testsystem.
We have Lizenz for JIRA and the JIRA Agile Plugin.

I tried many ways to update the system but every try I got the error that JIRA has been locked and could not start.

This Time I deinstalled the JIRA Agile Plugin and run the update.
Now I got JIRA Software installed

Mahantesh Chanapannavar

Whenever there is a reboot of JIRA server, the issue comes up - JIRA Startu Failed.

Majority times it will be with the statement "The following plugins are required by JIRA, but have not been started:" and I do the following things to make JIRA ON.

1. Stop the JIRA

2. Delete the "Pluggins" folder

3. Restart the JIRA and it works

Is there any permanent solution where in future, even if there is a restart/reboot of server pc, such errors or issues won't come up?

Nic Brough -Adaptavist-

When a computer starts up, it is thrashed to death by every service and program trying to start itself at the same time.

JIRA is now very heavy on starting itself, and the problem you're getting is almost certainly that it can't get all the resources it needs for a successful startup, because everything else on your server needs them too while booting.

Your starting options are

Get a more powerful server
Give JIRA more resources
Stagger the JIRA startup so that it only tries to start after the other things have mostly finished
Give JIRA more time to get started (change the "plugins wait" time as above)

I'd also do some housekeeping - check if your system really does need all the add-ons you have

Mahantesh Chanapannavar

Thank you Nic for the quick reply and the options to set.

I have set the wait time and will keep JIRA under observation. Lets see if it solves the issue or not.

Trupti Kamble

Hello,

I am facing same issue while upgrading from 7.3.6 to 7.10.2.

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

I tried all above solutions:

1. Removed .osgi and .bundled plugins

1. Increased memory by 1024 in setenv.sh

2. Added -Datlassian.plugins.enable.wait=300

3. Removed "Plugins" folder and did restart

4. Added

update pluginstate set pluginenabled='true'

Though it's not working.

Can somebody please save me?

Logs: 2019-03-05 15:21:37,098 JIRA-Bootstrap ERROR [c.a.plugin.manager.PluginEnabler] Unable to start the following plugins due to timeout while waiting for plugin to enable: com.atlassian.scala.plugins.scala-2.11-provider-plugin,com.atlassian.jira.plugins.jira-importers-github-plugin,com.atlassian.feedback.jira-feedback-plugin,com.atlassian.mywork.mywork-jira-provider-plugin,com.atlassian.jira.rest,com.atlassian.jirawallboard.atlassian-wallboard-plugin,com.atlassian.plugins.atlassian-awareness-capability,com.atlassian.jira.plugins.jira-transition-triggers-plugin,com.atlassian.plugins.jira-html5-attach-images,com.atlassian.gadgets.opensocial,com.atlassian.oauth.atlassian-oauth-service-provider-spi,com.atlassian.jira.jira-fileviewer-plugin,com.atlassian.troubleshooting.plugin-jira,tac.jira core.languages.ro_RO,com.atlassian.jira.plugins.jira-quicksearch-plugin,com.atlassian.plugins.atlassian-nps-plugin,tac.jira core.languages.ru_RU,com.atlassian.applinks.applinks-plugin,tac.jira core.languages.pt_BR,com.atlassian.labs.hipchat.hipchat-for-jira-plugin,tac.jira core.languages.da_DK,com.atlassian.oauth.admin,com.atlassian.jira.plugins.inline-create.jira-inline-issue-create-plugin,com.atlassian.upm.upm-application-plugin,com.atlassian.jira.jira-

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

jira-administration