HealthCheck: Shared Home
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
Overview
This check tests that each node in the cluster is using the same shared home, by reading & writing to/from a node status file in the shared home directory with relevant metadata in it.
Understanding the Results
| Icon | Result | What this means |
|---|---|---|
 | The health check passed successfully. | There are no problems with the node status file or shared home configuration. |
 | Node <node> is not using the correct shared home <shared-home>. | The JIRA shared home is incorrectly configured for the reported node. |
| Node <node> is not actively using shared home <shared-home>. Last update was <seconds> ago. | The reported node has not made any changes to the shared home directory within the reported number of seconds. |
Troubleshooting
| Problem | Suggestion |
|---|---|
| The node is not using the correct shared home. | Check the cluster.properties file in each node's |
| The node is reporting a failure, however the cluster.properties file is correctly configured. |
|
There are exceptions thrown around permission denied errors in the JIRA logs. | Run through the Actions in Jira server fails with FileNotFoundException in the Jira logs KB article to verify the permissions are correctly set. |
Providing Information to Support
In case you are unable to troubleshoot and fix the problem by yourself, please create a support ticket at support.atlassian.com and attach the following information to the ticket:
- Take a Screenshot of the Health Check results.
- Collect a Support ZIP from each of the Data Centre nodes.
- Any collected information from the suggestions in this document.