Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Shared Home (jira.shared.home) always shows CLUSTER error during Troubleshooting

Sami Ahmed Shaik
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 30, 2021

Hello there,

 

I am trying to configure Jira DC in a test environment. I have followed all the instructions of mentioned in the Jira DC installation document. Following are the details and the issue I am facing

Configuration:

Node1: Windows Server 2016

Shared Home Folder: \\144.X.X.X\dcshared

 

Node2: Window Server 2016

Shared Home Folder: \\144.X.X.X\dcshared

 

Load Balancer:

Configured correctly without any issues

 

DCSHARED is an NFS shared folder (full read/write permissions) and accessible from both servers. 

 

Issue:

Both the nodes get boot up without any issues with clustering showing both nodes are ACTIVE

Clustering Status.PNG

But the TROUBLESHOOTING section shows problems with the

CLUSTERS SHARED Folder as follows

Shared Home.PNG

 

Even the moment when the Jira boots up, nodes create their own folder in a local drive with the shared folder name.

 

How to solve this issue? 

 

Regards,

Sami Ahmed Shaik.

 

 

3 answers

1 accepted

0 votes
Answer accepted
Jobin Kuruvilla [Adaptavist]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 3, 2011

Who can login to JIRA is driven by global permissions. But who sees what is driven by project permissions and this can be different for different projects.

Hopefully more restrictions on the latter will prevent your Anonymous access issue.

Ian Sherwood
October 3, 2011

Yes, it was under permissions. Thanks

0 votes
Ian Sherwood
October 3, 2011

The group "Anyone" was added to every permission in my system. Apparently this happened during an upgrade on Saturday. If you are receving an upgrade, be sure to check your permissions after the upgrade.

Jo-Anne MacLeod
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 3, 2011

You're on a hosted JIRA installation?

I take it that you just deleted the group?

Jo-Anne MacLeod
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 3, 2011

gross, but at least you know where the problem was. I think that I would have simply deleted the entire group rather than modify all of the permission schemes, especially as you weren't using it before.

Did you ask Atlassian about this change and why it was done?

Ian Sherwood
October 3, 2011

Yes, it's hosted. I removed the group from all places where it gave too much access (pretty much everywhere)

Ian Sherwood
October 3, 2011

I have a support ticket open and you can bet I'll be asking.

0 votes
Jo-Anne MacLeod
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
October 3, 2011

check your settings under the Global Settings to see if anything changed there.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events