JIRA FAILING TO START

[Richard de Breyn]

I was busy with an upgrade when the SSH connection dropped. Since then, I get this:

An existing index lock was found.

An index lock file was found unexpectedly. This occurs either because JIRA was not cleanly shutdown or because there is another instance of this JIRA installation currently running. Please ensure that no other instance of this JIRA installation is running and then remove the following lock file(s) and restart JIRA:

UtilConcurrentLock{lock=true, fullLockName=/var/atlassian/application-data/jira/caches/indexes/issues/write.lock}

Once JIRA restarts please reindex your data to ensure that indexes are up to date.

Do not delete the lock file(s) if there is another JIRA running with the same index directory, instead cleanly shutdown the other instance.

The referred to file does not exist. And I only have one instance going. And I've cleared out that directory, but nothing. Refuses to start.

[Mirek]

So you are facing this

https://confluence.atlassian.com/jirakb/jira-does-not-start-due-to-index-lock-file-s-224402146.html

Please check your directory for lock files when you start JIRA, find it, stop JIRA and remove the lock file.

[Richard de Breyn]

Yes, except there are not files

[Richard de Breyn]

What's in that directory is:
total 16
drwxr-xr-x 2 jira root 4096 Apr 26 12:46 ./
drwxr-xr-x 7 jira root 4096 Nov 8 2016 ../
-rw-r----- 1 root root 32 Apr 26 12:46 segments_1
-rw-r----- 1 root root 20 Apr 26 12:46 segments.gen

[Nic Brough -Adaptavist-]

That's the index directory, the lock file is usually in the directory above, the jira-home directory

[Richard de Breyn]

Even if I clear the lock file, it goes back to:
An existing index lock was found.

An index lock file was found unexpectedly. This occurs either because JIRA was not cleanly shutdown or because there is another instance of this JIRA installation currently running. Please ensure that no other instance of this JIRA installation is running and then remove the following lock file(s) and restart JIRA:

UtilConcurrentLock{lock=true, fullLockName=/var/atlassian/application-data/jira/caches/indexes/issues/write.lock}

Once JIRA restarts please reindex your data to ensure that indexes are up to date.

Do not delete the lock file(s) if there is another JIRA running with the same index directory, instead cleanly shutdown the other instance.

[Nic Brough -Adaptavist-]

Stop Jira as normal, then check that it is genuinely shut down on the command line.

ps -ef | grep -i jira

should tell you the details of any running Jira systems.  I usually repeat it for Java as well, in case it's got a different name or location. After you've done that and you are 100% sure Jira is not running, then delete the lock file and start it again.  If you get the error again, then there's something very broken in your installation.

[Richard de Breyn]

Exactly as you've posted above I've been doing for almost 2 hours. With variations.

Something very broken... I can confirm that.

[Richard de Breyn]

What concerns me is the location the message refers to. It's not the standard Jira lock file, but an indexing lock file.

[Nic Brough -Adaptavist-]

The lock file for the application is the usual culprit, but yes, it can sometimes leave the index lock too.

Next trick is to ask the os what might be locking it all.  This can be a bit slow and it may not give us an answer but try

lsof | grep "/var/atlassian/application-data/jira"

[Richard de Breyn]

Thanks for suggestion. But don't think it's inline. In above case, it'll look for open files. But this lock file is a physical file that is somewhere that needs to be deleted.

I fixed it!

I removed all 3rd party plugins. [https://community.atlassian.com/t5/Questions/JIRA-Startup-failed/qaq-p/108708]

I removed all lock files I could find

I removed .bundled-plugins and .osgi-plugins from installed-plugins

Restarted, updated a few settings and et voila!

Thanks guys, for all the assist. Was about to find a lessor product.