Problem with Jira update 7.10.2 to 7.11.0

[IT DEPARTMENT]

Upgraded from Jira 7.10.2 to 7.11.0 and we keep getting this error:

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

We couldn't start the following plugins:

• 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)

We uninstalled and reinstalled several times to no avail.

We reverted back to Jira Core 7.10.2. and restored the DB backup and the HOME\JIRA\DATA backup and the same error keeps appearing.

We're running JIRA on Windows Server 2016 (as a service) and SQL Server 2016.

We have 3 third-party plugins: WorkLog, ICTIME, and Structure.

Our system is down now. Any workaround for this? Feedback and help is greatly appreciated.

[IT DEPARTMENT · Accepted solution]

I deleted the Plugins folder under

C:\Program Files\Atlassian\Application Data\JIRA\plugins

Restarted Jira, which automatically recreated this folder

then re-installed the 3 additional 3rd party plugins

All is well now. Thanks Manon and Danyal for your help.

[IT DEPARTMENT]

Just disabled the Jira service and attempted to launch it from the CMD Prompt as follows:

start-jira.bat /disablealladdons /disableaddons=com.atlassian.jira.jira-issue-nav-plugin:com.atlassian.jira.jira-quick-edit-plugin

JIRA still wants to load the two problematic add-on plugins.

I got the following error: in the Tomcat Java

2018-07-18 16:54:08,862 JIRA-Bootstrap INFO [c.a.plugin.manager.DefaultPluginManager] Plugin system earlyStartup ended
2018-07-18 16:54:08,919 JIRA-Bootstrap ERROR [c.a.jira.startup.SystemPluginsEnabledHealthCheck] We couldn't start the following plugins:
- 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)

2018-07-18 16:54:08,943 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] We haven't been able to start all the required system plugins
2018-07-18 16:54:08,943 JIRA-Bootstrap ERROR [c.a.jira.health.HealthChecks] We couldn't start the following plugins:
- 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)

2018-07-18 16:54:09,274 JIRA-Bootstrap INFO [c.a.j.c.cache.pauser.NonClusteredReplicationPauserManager] Non-clustered mode: ReplicationPauserManager implemented by NonClusteredReplicationPauserManager
2018-07-18 16:54:10,227 JIRA-Bootstrap INFO [c.a.j.config.database.SystemDatabaseConfigurationLoader] Reading database configuration from C:\Program Files\Atlassian\Application Data\JIRA\dbconfig.xml
2018-07-18 16:54:10,269 JIRA-Bootstrap INFO [c.a.j.instrumentation.external.DatabaseExternalGauges] Installing DBCP monitoring instruments: DatabaseExternalGauges.JiraDbcpInstruments[instruments=[DBCP_MAX, DBCP_ACTIVE, DBCP_IDLE],objectName=com.atlassian.jira:name=BasicDataSource]
2018-07-18 16:54:12,246 JIRA-Bootstrap ERROR [c.a.jira.startup.DefaultJiraLauncher] JIRA has failed to start because of the following errors: [(Event: Level = (EventLevel: fatal) , Key = (EventType: system-plugins) , Desc = We haven't been able to start all the required system plugins , Exception = We couldn't start the following plugins:<br/><ul><li>Atlassian Jira - Plugins - Global Issue Navigator (com.atlassian.jira.jira-issue-nav-plugin)</li><li>Atlassian JIRA - Plugins - Quick Edit Plugin (com.atlassian.jira.jira-quick-edit-plugin)</li></ul>)]
2018-07-18 16:54:12,257 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 335 MiB. Committed: 641 MiB. Max: 736 MiB
Non-heap memory : Used: 192 MiB. Committed: 210 MiB. Max: 1264 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 528 MiB. Committed: 851 MiB. Max: 2000 MiB
---------------------------------------------------------------------------------

[Danyal Iqbal]

Please insert the following into your JIRA application startup parameter using the methods mentioned here - Setting Properties and Options on Startup::

-Datlassian.plugins.enable.wait=300

(warning) Please restart the instance after adding the parameter in order to apply the changes to your JIRA applications.

+1 for support request.

[IT DEPARTMENT]

Thanks Danyal. I had added -Datlassian.plugins.enable.wait=300 through the Java config tool and the issue did not get resolved.

[Danyal Iqbal]

Did you increase the memory as well? Some plugins require too much memory.

-Restore a working backup, disable all addons, run the upgrade again. Activate each plugin one by one. Uninstall teh guilty party.

[IT DEPARTMENT]

Tried with 512 min and 1024 max and still the issue persists.

Also, I disabled the Security tool on the Server.

The working backup did not work either. It was 7.10.2 with the old DB and old DATA files from the ZIP backup did not work either.

How do you disable the Add-ons? Based on the docs, you cannot disable add-ons when running under Windows as a service. You cannot launch in Safe Mode. Would you please point me in the right direction for a way to disable add-ons?

[Manon Soubies-Camy]

Hello @IT DEPARTMENT,

Have you checked this thread: JIRA access problem after update? @Mizan suggestions should help you investigate:

• Seems like a memory issue , may i know if the file system has enough free space and what amount of heap is allocated to JIRA (i.e. the Xmx defined in <installation>/bin/setenv.sh)
• Try increasing the plugin wait time to 300 . (I thought this was fixed but this is still an open issue https://jira.atlassian.com/browse/JRASERVER-60212) https://confluence.atlassian.com/jirakb/jira-applications-system-plugin-timeout-while-waiting-for-add-ons-to-enable-212173447.html

Hope this helps,

- Manon

[IT DEPARTMENT]

Dear Manon,

Minimum memory is set to 384 and max to 1024 using the CONFIG tool in the BIN folder. Also, -Datlassian.plugins.enable.wait=300 was added to the startup options. The problem still persists.

Thanks.