Fix Attachment Health Check Failures in Jira Data Center
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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
Summary
JIRA stores attachments on disk in $JIRA_HOME and also references them in the database. This health check confirms that the attachments are correctly working by checking that the most recent attachments can be found and are able to be opened.
Understanding the Results
✅
The latest attachment (<attachment>) for issue (<issue>) was found and can be used.
The health check was able to confirm that the most recent attachment can be found in the file system and database.
There were no attachments found.
No attachments have been recorded in JIRA.
⚠️
The latest attachment (< attachment> ) for issue (< issue> ) failed testing but the second most recently updated attachment (< attachment> ) for issue (< issue> ) is ok.
This may indicate a slow environment, or a problem in the JIRA configuration. The health check will look for previous attachments within a 30 second second window and if the previous attachment is healthy, return this warning.
❌
The attachment (< attachment> ) for issue (< issue> ) could not be read.
There may be some file system problems in your environment, an attachment has been recorded, but can not be accessed.
Missing some attachments due to upgrade by XML backup, refer to troubleshooting section for more details.
Solution
Most recent attachments can not be found.
Re-run the health check and confirm the problem still exists. If the issue does not still exist, you may be experiencing performance problems writing to your attachment storage location.
If the file continues to not exist, open the affected issue, and investigate if the attachment can be accessed. If not contact Atlassian Support for assistance.
Missing Attachments.
If you are observing frequent missing attachments or all attachments can't be accessed, check the configuration of your file system across all nodes in JIRA Data Center. If no configuration problem exists, use the guide below to confirm if the permissions of the file system are correct.
The file system permissions are not correct.
Go through the Actions in Jira server fails with FileNotFoundException in the Jira logs KB article to verify and/or fix the permissions.
Missing recent attachments due to Upgrade using XML backup
JIRA has been upgraded using XML backup, and the database backup is taken after the attached files backup, then it may refer to newer files that are not in the attachments folder as the files backup is taken before the database backup.
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.
In the event that the directory is reported as missing but does exist on the file system, including the results of the below SQL:
SELECT * FROM fileattachment;Please provide details of the affected file System location [directory] showing ownership. This can be achieved through the following steps:
Linux
ls -lahR [directory] | gzip -9 > fileListing.gzWindows Use the AccessEnum SysInternals tool by Microsoft to complete this task, and collect a screenshot showing the permissions of the Shared Directory being used.
Was this helpful?