Bitbucket data center displays the message "Path does not correspond to a valid repository ID" when performing integrity checks.
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles 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:
On enabling the integrity check in the Bitbucket, the message "Path does not correspond to a valid repository ID." appears sometimes.
Environment:
Bitbucket Data Center 8.19.1.
Diagnosis:
The atlassian-bitbucket.log will have the following events when the debug logging is enabled.
2024-05-14 13:53:29,585 INFO [Caesium-1-1] c.a.s.i.i.DefaultIntegrityCheckReporter Started full integrity checking
2024-05-14 13:53:29,624 INFO [Caesium-1-1] c.a.s.i.i.DefaultIntegrityCheckEventService Auto-integrity checks started
2024-05-14 13:53:29,649 DEBUG [Caesium-1-1] c.a.s.i.i.DefaultIntegrityCheckReporter Integrity checks for repositories have started
2024-05-14 13:53:29,659 DEBUG [Caesium-1-1] c.a.s.i.i.DefaultIntegrityCheckReporter Path does not correspond to a valid repository ID. Path: /var/atlassian/application-data/bitbucket/shared/data/repositories/test_directoryCause:
- The Bitbucket Server repositories are located in <
BITBUCKET_HOME>/shared/data/repositories/<repository-id>directory. Bitbucket always gives the repository directory a unique number known as the repository id when a repository is created. - The message "c.a.s.i.i.DefaultIntegrityCheckReporter Path does not correspond to a valid repository ID." appears for the directory that Bitbucket does not consider as a repository directory when the integrity check is run. In this example, test_directory is not a valid Bitbucket repository directory, hence the message is logged by Integrity Checker.
Solution:
- Determine the cause of the problematic directory's existence within the <
BITBUCKET_HOME>/shared/data/repositories folder. Should it have been created by manual mistake, move it outside of the <BITBUCKET_HOME>directory. - In case of any confusion, kindly reach out to Atlassian support.