Jira startup log shows "IndexNotFoundException: no segments* file found" error for Zephyr Squad plugin.
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
Problem
During a Jira startup, the following error is thrown for JIRA-Bootstrap thread, specifically mentioning Zephyr Squad plugin.
1
2
3
4
5
6
7
JIRA-Bootstrap ERROR [c.a.jira.index.LuceneCorruptionChecker] Can't open index 'C:\Atlassian\Application Data\Jira\caches\indexesV2\plugins\JEEntity'. Reason:
org.apache.lucene.index.IndexNotFoundException: no segments* file found in MMapDirectory@C:\Atlassian\Application Data\Jira\caches\indexesV2\plugins\JEEntity lockFactory=org.apache.lucene.store.NativeFSLockFactory@XXXXXXXX: files: [schedule, write.lock]
at org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:670)
at org.apache.lucene.index.StandardDirectoryReader.open(StandardDirectoryReader.java:79)
at org.apache.lucene.index.DirectoryReader.open(DirectoryReader.java:63)
at com.atlassian.jira.index.LuceneCorruptionChecker.isIndexOpenable(LuceneCorruptionChecker.java:68)
...Symptoms
Even though the log shows such an error, the application is able to start and there is no missing functionality.
Cause
Looking at the files directory, the Zephyr plugin has a slightly different directory order for its indexing data.
Other user-installed plugins would have segments and write.lock files located directly under its plugin directory.
However, for Zephyr specifically, it adds a subdirectory called schedule and places segments files under its subdirectory.
As a result, when Jira is looking for the segments file under its directory, it won't find it and throwing the error.
Resolution
It is confirmed by the Smartbear team that the directory structure is expected, and the error can safely be ignored.
Was this helpful?