Fisheye/Crucible repository index is corrupted

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptom 1

After a major Fisheye upgrade, from e.g. 2.3.6 to 2.7.15, Fisheye indexing job fails with this error:

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

Symptom 2

Crucible fails to index the SVN repository. And the following error message is appearing at UI when trying to start the repository:



In both of the cases above, the repository indexes have become corrupt.


The repository data has to be be re-indexed from scratch. To do so, please follow these steps:

  1. Shut down the Fisheye instance
  2. Delete the FISHEYE_INST/var/cache/MyRepoName directory
  3. Start 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.

Last modified on Jul 31, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.