Mercurial repository reindex fail
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
Symptoms
Fisheye will fail to reindex Mercurial repository with the message "Repository index failed due to error" or "Unable to pull from repository" in the UI.
The following appears in the atlassian-fisheye-<date>.log:
1
2
3
2012-02-13 20:44:19,721 DEBUG [IncrementalPinger1 catch21] fisheye.app LoggingProcessMonitor-onAfterFinished - Finished process: hg --config ui.verbose=false pull https://bitbucket.org/rene/fsh5798/ took 3135ms
2012-02-13 20:44:19,722 INFO [IncrementalPinger1 catch21] fisheye.app LoggingProcessMonitor-onAfterFinished - Exception executing command "hg --config ui.verbose=false pull https://bitbucket.org/rene/fsh5798/ " Non-zero exit code: 1
com.atlassian.utils.process.ProcessException: Non-zero exit code: 1
Cause
Mercurial 2.1 has a bug that makes it incompatible with Fisheye.
Resolution
Install Mercurial 2.1.1 or later
Remember to restart Fisheye after upgrading Mercurial
Was this helpful?