Jira fails to startup or create index snapshots when in clustered mode
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
When starting up Jira, or when an index snapshot is being created, Jira throws the following error message in its logs:
1
2
2022-11-13 10:34:57,481-0600 main ERROR [c.a.jira.startup.LauncherContextListener] Unable to start JIRA.
com.atlassian.jira.util.RuntimeIOException: java.io.IOException: Entry 'issues/_4_Lucene50_0.tip' closed at '40960' before the '165936' bytes specified in the header were written
Environment
Jira running in a Linux environment with SELinux enabled.
Diagnosis
Identify the mentioned error within the Jira logs.
Cause
This error comes from the Apache library, and occurs when the code attempts to close the file after writing it to the .tar archive when an index snapshot is being created.
If the autorelabel flag in SELinux isn't enabled, it causes the index file to close prematurely (before it finishes being written), which in turn triggers this error.
Solution
You can disable reindexing on startup to avoid this behavior by adding the following argument to Jira's startup parameters:
ℹ️ This needs to be added on a per-node basis and can be applied with a rolling restart.
1-Dcom.atlassian.jira.startup.allow.full.reindex=falseAlternatively, updating the autorelabel flag in SELinux and enabling it in permissive mode should allow index snapshots to be created successfully.
💡 More information on how to do this can be found here.
Was this helpful?