JIRA can't create a lock for your jira.home directory

Question

JIRA can't create a lock for your jira.home directory

cvandome opened this issue 7 years ago · 13 comments

Hello all,

I've a wired issue, my Jira setup mount a nfs volume for Jira Home, on the first start, files are written to NFS share with the right user (daemon or uid 1 on server side), the .lock_file is also written but Jira show me this error.

I don't understand, if someone could help me.

Here is the NFS Export line from the server:
/nfs/exports/jira-home 192.168.205.0/24(rw,async,no_subtree_check,no_root_squash)

Thanks !

Answer 1 · 2017-11-29T22:33:54.000Z

Don't know anything about NFS sorry, but what error does JIRA show?

Answer 2 · 2017-11-29T22:57:53.000Z

Thanks for reply, Jira show on the webui: JIRA can't create a lock for your jira.home directory

It's wired because when I look inside the NFS folder, I see that Jira can write in this folder.

Answer 3 · 2017-11-29T23:03:15.000Z

Just delete the existing lock if you are sure no other instances are using the home folder and restart Jira :-) it probably wasn’t deleted due to a hard shutdown or a backup of the home directory was made while JIRA was running. Kind regards, Martin Jensen

…

On 29 Nov 2017, at 23.57, Cédric Vandôme ***@***.***> wrote: Thanks for reply, Jira show on the webui: JIRA can't create a lock for your jira.home directory It's wired because when I look inside the NFS folder, I see that Jira can write in this folder. — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

Answer 4 · 2017-11-29T23:07:07.000Z

I've already tested this but no success :(

I'll continue to inspect and come back to post answer here, it can helps.

Best regards

Cédric Vandôme

Answer 5 · 2018-02-08T04:56:04.000Z

When I update docker image and restart ,I got "Setup: JIRA couldn't create the jira.home directory“ issue. try find the "lock" file to delete,I faild. where can I find it. can anyone help me? it drive me crazy .

Answer 6 · 2018-03-07T10:43:55.000Z

Same issue

Answer 7 · 2018-03-07T10:47:55.000Z

Problem solved by removing the symlink of indexes dir and re-put it in nfs in its own place , accepting the luncene warnings in jira to use nfs for indexes.

unlink /nfs/web-hx/coresrv/projects/jira/dev/jira_home/caches/indexes

Answer 8 · 2018-03-07T10:49:09.000Z

Can also be solved by running the container as previlged

Answer 9 · 2018-03-07T10:52:50.000Z

hello @iahmad-khan I've fixed issue with NFS config also, it's a NFS side issue

For help it works for me:

On every NFS client:
yum install nfs-utils nfs-utils-lib
systemctl enable rpcbind
systemctl enable nfs-lock
systemctl enable nfs-idmap
systemctl start rpcbind
systemctl start nfs-lock
systemctl start nfs-idmap

In each /etc/fstab client:
192.168.X.X:/nfs/exports /data nfs rw,sync,hard,intr 0 0

We can close this issue

Answer 10 · 2018-03-07T10:57:56.000Z

hi ,

I have already these packages installed and mount configured , but it stops working when i create a symlink for indexs directry to local file system , and permissions are granted to the user on that local directory where indexes are pointing to from nfs.

Answer 11 · 2018-03-07T10:58:55.000Z

so this problem occurs when we symlink indexs dir to local file system and keep the home dir on nfs

Answer 12 · 2018-03-07T11:01:36.000Z

sorry but each NFS probleme is very specific and is out of scope of this issue.

Good luck !

Answer 13 · 2018-03-07T21:41:10.000Z

If you're using latestthe UID has changed caused by moving to Alpine as base image