JIRALockedError

JIRA Startup Failed. Plugins are failing to start. Running JIRA 5.2. Only change was switching network IP addresses. KB says to remover .jira-home.lock file. Atlassian JIRA service is using file so can't be removed. Stop service file disappears. Need help!!

3 answers

0 vote

You're trying to do too many things at once. Removing the lock file only applies in certain circumstances, and it doesn't sound like you're in one of them.

I'd try to start clean. Shut down Jira. Check it's all stopped with a basic ps -ef command (or digging through windows task manager if you're stuck with running it on windows). Then you can remove the lock file. At that point, I usually recommend moving all the logs out somewhere safe. Then restart it, and see what happens, and if it fails, you've got small, short clean logs to help you debug the problem (they're probably short enough to simply post here if you moved the old ones)

I am running it on windows. So when I shutdown the Atlassian JIRA service, the lock file disappears but then of course I can not use a browser to connect to JIRA without that service running. As soon as I start the service the lock file comes back. The service itself starts and stops cleanly. When trying to access JIRA through a webclient I get the following discription of errors:

The following plugins are required by JIRA, but have not been started:

Atlassian JIRA - Plugins - Project Config Plugin (com.atlassian.jira.jira-project-config-plugin)

Embedded Gadget Plugin (com.atlassian.gadgets.embedded)

Gadget Dashboard Plugin (com.atlassian.gadgets.dashboard)

Atlassian JIRA-Plugins-look and Feel Logo Upload Plugin (com.atlassian.jira.lookandfeel)

Opensocial Plugin (com.atlassian.gadgets.directory)

Atlassian JIRA-Plugins-Gadgest Plugin (com.atlassian.jira.gadgets)

The lock file is there explicitly to stop you running a second instance of Jira by accident. It disappears on shutdown to tell the next attempt to run that it is ok. The lock file sounds like it is working as intended.

The usual cause of this problem is virus scanners (windows AV has to be implemented in an appallingly bad way and it breaks all sorts of stuff. Sadly including Jira) or lack of resources.

Have a look through https://confluence.atlassian.com/display/JIRAKB/Troubleshooting+JIRA+Startup+Failed+Error

We found one more instance of the old IP address range that was keeping the plugins from starting up. I have since lost the exact location of the "hidden" instance. We used a search to find it.

I was facing this issue due to the unsupported JIRA version. I was testing on JIRA 6.4.9 and it was giving JIraLockedError. Wasn't working even after deleting lock files, .bundled-plugins/ folder and the .osgi-plugins/ as suggested, then i switched to lower JIRA version and it worked. 

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,210 views 13 19
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot