jira will not start - FATAL [atlassian.jira.upgrade.ConsistencyLauncher] A fatal error occured during initialisation. JIRA has been locked.

[Mike Fee]

We were experiencing peformance problems with JIRA (version 4.3.4) on Win 2003 server so we did the following:

1. Upped the RAM to 4GB from 1GB

2. Upped the CPUs to 2 from 1

3. Moved the paging file from C: to D: and made it system managed

4. Installed Windows Updates

Now JIRA will not load - the following extract from the error from the stdout log seems most relevant:

Any ideas?

2011-08-31 14:46:17,337 Finalizer WARN [core.entity.jdbc.SQLProcessor] Already closed.

2011-08-31 14:46:17,415 main INFO [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: [com.atlassian.gadgets.embedded, com.atlassian.gadgets.dashboard, com.atlassian.streams.streams-jira-plugin, com.atlassian.jira.gadgets, com.atlassian.jirafisheyeplugin, com.atlassian.gadgets.directory, com.atlassian.jira.rest, com.atlassian.gadgets.oauth.serviceprovider, com.atlassian.gadgets.opensocial], 57 seconds remaining

2011-08-31 14:46:18,525 main INFO [atlassian.plugin.util.WaitUntil] Plugins that have yet to be enabled: [com.atlassian.gadgets.directory], 56 seconds remaining

2011-08-31 14:46:20,728 main INFO [atlassian.plugin.loaders.ScanningPluginLoader] No plugins found to be deployed

2011-08-31 14:46:21,712 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. Unable to esablish a connection with the database. (Network error IOException: Connection refused: connect)

[Mike Fee · Accepted solution]

See my comment from Sep 03

[Mike Fee]

see previous comment for answer to this question

[Jobin Kuruvilla [Adaptavist]]

Well, the log says it is aDB connectivity issue!

Unable to esablish a connection with the database. (Network error IOException: Connection refused: connect)

Did you check that?

[Mike Fee]

Resolved by disabling the service called "Apache Tomcat 6", which was what was starting the previous version of JIRA and preventing the new version from loading. This only became apparent after rebooting the server - Apache service started first every time.