All Repositories Appear Empty After an Upgrade
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
No content in the configured repositories after an upgrade. Clicking on one of the repositories gives "Fatal: Not a git repository" on screen error.
Following error reported in the logs:
1
2
3
2013-03-26 11:47:06,976 ERROR [localhost-startStop-1] c.a.s.c.u.DefaultPluginUpgradeManager Upgrade error: Unexpected exception caught during plugin upgrade: com.atlassian.bitbucket.exception.ServerException: An error occurred while executing an external process: '/usr/local/bin/git config --replace-all http.receivepack true' exited with code 255 saying: error: could not lock config file .git/config: No such file or directory
at com.atlassian.bitbucket.internal.scm.git.GitCommandExitHandler.evaluateThrowable(GitCommandExitHandler.java:116)
at com.atlassian.bitbucket.internal.scm.git.GitCommandExitHandler.onError(GitCommandExitHandler.java:159)
Cause
The .git/config file could not be located successfully.
Resolution
Ensure that the .git/config file is correctly configured and that Bitbucket Server has been unzipped correctly into BITBUCKET_HOME and BITBUCKET_INSTALL directory.
Was this helpful?