Jira cannot be started due to fatal error occured during initialisation

sautaja
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 1, 2012

Greetings,

For some reason, the jira application cannot be started, I checked that a possible solution could be:

https://jira.atlassian.com/browse/JRA-19460

But I am fairly new to jira, what can I do to start jira again?

2012-01-02 08:27:54,175 main INFO [atlassian.plugin.loaders.ScanningPluginLoader] Plugin Unit: /opt/jira/plugins/.bundled-plugins/json-20070829-1.jar (1275241264000) created
2012-01-02 08:27:54,188 main INFO [atlassian.plugin.loaders.ScanningPluginLoader] Plugin Unit: /opt/jira/plugins/.bundled-plugins/nekohtml-1.9.12-1.jar (1275241266000) created
2012-01-02 08:27:54,221 main INFO [atlassian.plugin.loaders.ScanningPluginLoader] Plugin Unit: /opt/jira/plugins/.bundled-plugins/rome-1.0.jar (1275241266000) created
2012-01-02 08:27:54,231 main INFO [atlassian.plugin.loaders.ScanningPluginLoader] Plugin Unit: /opt/jira/plugins/.bundled-plugins/sal-api-2.0.17.jar (1275407340000) created
2012-01-02 08:27:54,314 main INFO [atlassian.plugin.loaders.ScanningPluginLoader] Plugin Unit: /opt/jira/plugins/.bundled-plugins/streams-jira-plugin-3.0.19.jar (1275241262000) created
2012-01-02 08:27:54,315 main INFO [atlassian.plugin.manager.DefaultPluginManager] Plugin com.atlassian.jira.plugin.ext.bamboo was marked to be removed on restart. Removing now.
2012-01-02 08:27:54,315 main INFO [atlassian.plugin.loaders.ScanningPluginLoader] Removed plugin com.atlassian.jira.plugin.ext.bamboo
2012-01-02 08:27:54,469 main FATAL [atlassian.jira.upgrade.ConsistencyLauncher] A fatal error occured during initialisation. JIRA has been locked.
com.atlassian.jira.InfrastructureException: Error occurred while starting Plugin Manager. null

2 answers

0 votes
Dave C
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 20, 2012

I realise this is an old answer, however this is one of the top Google results for this particular case.

This looks like it may relate to a known bug within the Universal Plugin Manager, as detailed within JRA-19460. Please review that issue to see if has helped.

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 1, 2012

What customisations have you done to it? What's the JVM and version of Jira? Are there other errors in the log? Has it run ok before, and if so, what have you changed between the last run and this one?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events