"JIRA has been locked" error when starting Jira Server or Data Center
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
JIRA applications doesn't start. Logs contain:
****************************************************************************************************************************************************************
The jira.home directory '/mnt/jira/data' is already locked. Please see http://docs.atlassian.com/jira/docs-041/How+do+I+unlock+my+JIRA+home+directory%3F?clicked=jirahelp# for more information on locked jira.home directories.
****************************************************************************************************************************************************************
2010-10-01 18:13:54,211 main FATAL [atlassian.jira.startup.JiraStartupLogger] Startup check failed. JIRA will be locked.
2010-10-01 18:13:54,585 main FATAL [atlassian.jira.upgrade.ConsistencyLauncher] Not initializing JIRA, the startup checklist failed and JIRA has been locked.
2010-10-01 18:13:54,585 main FATAL [atlassian.jira.upgrade.UpgradeLauncher] Skipping, JIRA is locked.
2010-10-01 18:13:54,585 main INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] Starting the JIRA Scheduler....
2010-10-01 18:13:54,586 main INFO [atlassian.jira.scheduler.JiraSchedulerLauncher] Skipping JIRA Scheduler initialisation, JIRA is not ready.
2010-10-01 18:13:56,911 main WARN [jira.config.properties.ApplicationPropertiesImpl] Exception getting property 'jira.extension.container.provider' from database. Using default
2010-10-01 18:13:56,928 main WARN [jira.config.properties.ApplicationPropertiesImpl] Exception getting property 'jira.trustedapps.user.name.transformation.policy.class' from database. Using default
2010-10-01 18:13:57,465 main FATAL [webwork.dispatcher.ServletDispatcher]
******************************************
JIRA startup failed, JIRA has been locked.
******************************************
Cause
A JIRA application locking mechanism is preventing startup. This may be due to several causes:
- The JIRA application was shut down incorrectly, or failed to shut down.
- A second instance of a JIRA application, pointing to the same database, was started. This can happen in the case of a test instance of a JIRA application pointing to the production database.
- In rarer circumstances, especially after a plugin installation, JIRA applications can run out of PermGen memory on startup. See JIRA applications crash due to 'java.lang.OutOfMemoryError PermGen space error.
Resolution
Delete the JIRA application lock file. See How do I unlock my JIRA home directory? for instructions.
Last modified on Oct 30, 2024
Powered by Confluence and Scroll Viewport.