Jira doesn't startup

[Bunty]

Hello All,

After stopping and restarting Jira, suddenly stopped working. Below error in the log file:

********************************************************************************************************************************************************************************************************
___ FAILED PLUGIN REPORT _____________________

1 plugin failed to load during JIRA startup.

'com.atlassian.plugins.atlassian-whitelist-api-plugin-4.0.5' - 'Atlassian Whitelist API Plugin' failed to load.
org.osgi.framework.BundleException: Bundle com.atlassian.plugins.atlassian-whitelist-api-plugin [139] cannot be started, since it is either starting or stopping.
Bundle com.atlassian.plugins.atlassian-whitelist-api-plugin [139] cannot be started, since it is either starting or stopping.

It was loaded from /jira/opt/atlassian/jira/atlassian-jira/WEB-INF/atlassian-bundled-plugins/atlassian-whitelist-api-plugin-4.0.5.jar
1 plugin are unaccounted for.
Unaccounted for plugins load as artifacts but fail to resolve into full plugins.

'com.atlassian.labs.hipchat.hipchat-for-jira-plugin' - 'HipChat for JIRA' is unaccounted for.

It was loaded from /jira/opt/atlassian/jira/atlassian-jira/WEB-INF/atlassian-bundled-plugins/hipchat-for-jira-plugin-7.10.3.jar

********************************************************************************************************************************************************************************************************

2019-10-11 19:04:35,284 JIRA-Bootstrap INFO [c.a.jira.startup.LauncherContextListener] Memory Usage:
---------------------------------------------------------------------------------
Heap memory : Used: 850 MiB. Committed: 1344 MiB. Max: 1994 MiB
Non-heap memory : Used: 310 MiB. Committed: 335 MiB. Max: 1264 MiB
---------------------------------------------------------------------------------
TOTAL : Used: 1160 MiB. Committed: 1678 MiB. Max: 3258 MiB
---------------------------------------------------------------------------------
2019-10-11 19:04:35,284 localhost-startStop-1 INFO [c.a.jira.startup.DefaultJiraLauncher] Stopping launchers
2019-10-11 19:04:35,574 localhost-startStop-1 INFO [c.a.plugin.manager.DefaultPluginManager] Preparing to shut down the plugin system
2019-10-11 19:04:36,024 Caesium-1-2 WARN [c.a.jira.scheduler.OfBizRunDetailsDao] Cannot record run details when the scheduling system is not started: jobId=data-provider-cleanup; runDetails=RunDetailsImpl[startTime=1570820675120,runOutcome=SUCCESS,durationInMillis=903,message=]
2019-10-11 19:04:36,080 localhost-startStop-1 INFO [c.a.plugin.manager.DefaultPluginManager] Shutting down the plugin system
2019-10-11 19:04:37,247 Gemini Blueprint context shutdown thread1 INFO [c.a.b.service.logging.LogSupport]

*********************************************************************************
Atlassian Bonfire v2.9.18.0 #00034 plugin stopped
*********************************************************************************

2019-10-11 19:04:37,785 Caesium-1-3 INFO [c.a.j.index.ha.DefaultIndexRecoveryManager] Latest index date: {2019-10-11 15:04:42}, Latest DB date: {2019-10-11 15:04:42}
2019-10-11 19:04:39,815 Gemini Blueprint context shutdown thread2 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.atlassian.jira.plugins.jira-dvcs-connector-plugin]
2019-10-11 19:04:40,884 Gemini Blueprint context shutdown thread2 INFO [c.atlassian.agile.support]

*********************************************************************************
Atlassian GreenHopper v7.12.0-DAILY20180906101548 #41d291e8587c10b9 built 2018-09-06T10:26:28.392Z - plugin stopping...
*********************************************************************************

2019-10-11 19:04:40,894 Caesium-1-3 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] getService bundle [com.marvelution.jira.plugins.jenkins]
2019-10-11 19:04:40,936 Gemini Blueprint context shutdown thread2 INFO [c.atlassian.agile.support]

*********************************************************************************
Atlassian GreenHopper v7.12.0-DAILY20180906101548 #41d291e8587c10b9 built 2018-09-06T10:26:28.392Z - plugin stopped
*********************************************************************************

2019-10-11 19:04:40,992 Gemini Blueprint context shutdown thread2 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.pyxis.greenhopper.jira]
2019-10-11 19:04:42,224 Gemini Blueprint context shutdown thread1 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.marvelution.jira.plugins.jenkins]
2019-10-11 19:04:42,424 Gemini Blueprint context shutdown thread2 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.radiantminds.roadmaps-jira]
2019-10-11 19:04:43,031 Caesium-1-3 WARN [c.a.jira.scheduler.OfBizRunDetailsDao] Cannot record run details when the scheduling system is not started: jobId=ecd558cb-712f-478a-9aaa-4ad755b65212; runDetails=RunDetailsImpl[startTime=1570820675237,runOutcome=SUCCESS,durationInMillis=7794,message=]
2019-10-11 19:04:46,348 localhost-startStop-1 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.onresolve.jira.groovy.groovyrunner]
2019-10-11 19:04:47,609 localhost-startStop-1 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.atlassian.jpo]
2019-10-11 19:04:47,825 localhost-startStop-1 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.atlassian.teams]
2019-10-11 19:04:49,407 Gemini Blueprint context shutdown thread1 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.atlassian.plugins.atlassian-whitelist-core-plugin]
2019-10-11 19:04:50,096 Gemini Blueprint context shutdown thread2 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] ungetService bundle [com.atlassian.jira.plugins.webhooks.jira-webhooks-plugin]
2019-10-11 19:04:55,173 Gemini Blueprint context shutdown thread1 DEBUG [c.a.activeobjects.osgi.ActiveObjectsServiceFactory] destroy
2019-10-11 19:04:57,072 Gemini Blueprint context shutdown thread2 INFO [c.a.j.plugins.monitor.MonitoringScheduler] Unscheduling metrics collector...
2019-10-11 19:04:57,072 Gemini Blueprint context shutdown thread2 INFO [c.a.j.plugins.monitor.MonitorLauncher] Stopped JIRA monitoring
2019-10-11 19:04:57,193 FelixStartLevel WARN [c.a.p.osgi.factory.OsgiBundlePlugin] Cannot disable Bundle 'rome.rome-1.0', not ACTIVE
2019-10-11 19:04:57,193 FelixStartLevel WARN [c.a.p.osgi.factory.OsgiBundlePlugin] Cannot disable Bundle 'org.osgi.service.cm-1.5.0.201505202024', not ACTIVE
2019-10-11 19:04:57,193 FelixStartLevel WARN [c.a.p.osgi.factory.OsgiBundlePlugin] Cannot disable Bundle 'org.apache.httpcomponents.httpcore-4.4.1', not ACTIVE
2019-10-11 19:04:57,195 FelixStartLevel WARN [c.a.p.osgi.factory.OsgiBundlePlugin] Cannot disable Bundle 'org.apache.httpcomponents.httpclient-4.5.5', not ACTIVE
[c.a.jira.startup.JiraStartupLogger]
2019-10-11 19:04:58,151 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,155 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,166 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,179 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,181 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,188 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,189 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,191 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,192 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,193 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,198 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,199 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,201 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,379 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,386 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,388 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service
2019-10-11 19:04:58,395 localhost-startStop-1 WARN [c.a.p.osgi.factory.OsgiBundlePlugin] OSGi container not running or undefined: Will not remove bundle listener and will not close package admin service

Added below parameter in setenv.sh and deleted .Osgi and .bundled plugins from the plugins folder then restarted still it is not up and running.

-Datlassian.plugins.enable.wait=300

Thanks in advance,

Mani

[Francesco R]

I had the same issue with Jira Core. The origin of my problem was a port already used. I had this trace before the one that @Bunty has given here.

[main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[localhost:8005]: java.net.BindException: Address already in use: NET_Bind

I changed the port number in server.xml file and all was ok.
The only thing I don't understand is why I anyway got the message

******************************************************************************************************************************
Jira 8.20.1 build: 820001 started. You can now access Jira through your web browser. Plugins and caches are being initialised.
******************************************************************************************************************************

before that Jira exits. I'd expect that Jira exits as it traces that the port is busy

[Andy Heinzer]

Hi,

Sorry to hear that you are having problems with starting Jira server here.  It looks like you have one or more system plugin in Jira that is failing to load on startup.  As such this can cause Jira to fail to start altogether or fail to work as expected.

I would recommend trying to follow through on the KB https://confluence.atlassian.com/jirakb/jira-startup-fails-with-message-that-required-plugins-are-not-started-254738702.html.  I suspect that this plugin could have become flagged in the database as disabled. If this happens Jira will never be able to startup successfully for some system plugins.

The only disabled plugins that should exist there are typically user installed plugins that a Jira administrator has told the application to disable.  However if Jira fails to start a plugin, it can flag such a plugin as disabled in an attempt to try to get the rest of the application up and running.

I would be interested to see what results you get back from the SQL query of

SELECT * FROM pluginstate where pluginenabled = 'false';

Clearing such entries from that table, then restarting Jira might be enough to get it up and running again.  However if this doesn't help then there might be sometime corrupted with that system plugin, in which case we might look into Installing Jira fresh in a new directory (the same version of Jira), and then migrating your data over to that installation.  In many cases this is less effort and higher success rate than investigating this kind of problem much further.

Please let me know the results of that SQL query if you are uncertain.

Cheers,

Andy

[sysops@altibox.no]

Hi, 
I have the same problem with jira and in the user-installed plugins list I can see a list of disabled plugins, which seems to be system plugins. 
I have done what you said,
stop the jira and delete the plugins from pluginstate tabel as below:

jiradcdb=# SELECT * FROM pluginstate where pluginenabled = 'false';

(7 rows)

jiradcdb=# DELETE FROM pluginstate WHERE pluginkey LIKE 'com.atlassian.%';
DELETE 11
jiradcdb=# SELECT * FROM pluginstate where pluginenabled = 'false';
pluginkey | pluginenabled
------------------------------------------------------------------------------+---------------
(3 rows)


start the jira agian, but the problem still exist. 

[sysops@altibox.no]

my problem is solved, the problem was not a correct permission for some plugins in Jira-shared-directory/plugins/installed-plugins. changing all the plugins ownership to jira user fixed the issue

sudo chown -R jira:jira Jira-shared-directory/plugins/installed-plugins