Fisheye/Crucible repository index is corrupted
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
Symptom 1
After a major Fisheye upgrade, from e.g. 2.3.6 to 2.7.15, Fisheye indexing job fails with this error:
1
2
3
2012-08-09 15:55:38,002 WARN - Found a file revision without a path in changeset 40
2012-08-09 15:55:38,004 ERROR - Problem processing revisions from repo MyRepoName due to class java.lang.NullPointerException - null
java.lang.NullPointerException
Symptom 2
Crucible fails to index the SVN repository. And the following error message is appearing at UI when trying to start the repository:
And,
Cause
In both of the cases above, the repository indexes have become corrupt.
Resolution
The repository data has to be be re-indexed from scratch. To do so, please follow these steps:
Shut down the Fisheye instance
Delete the
FISHEYE_INST/var/cache/MyRepoNamedirectoryStart the Fisheye instance again
Please replace MyRepoName in step 2 by the name of the problematic repository.
Please note:
If this is a huge repository, Fisheye may take a while to finish re-indexing it from scratch. See this document on how to avoid long reindex times when upgrading.
Was this helpful?