Mirroring Error: commit-graph-chain.lock exists

Describe your question in as much detail as possible:

  • What are you seeing, and how does it differ from what you expect to see?

Mirroring from GitHub to GitLab fails with a git error:

2:Fetching remote upstream failed: warning: unable to find all commit-graph files
warning: unable to find all commit-graph files
fatal: Unable to create '/var/opt/gitlab/git-data/repositories/@hashed/6b/6f      /6b6fc6c389aef30b42394ea15f679f7cc672086dea22b4a88b84867f420a95dc.git/./objects/info/commit-graphs/commit-graph-chain.lock': File exists
  • What troubleshooting steps have you already taken? Can you link to any docs or other resources so we know where you have been?

Deleting and recreating the mirroring setting didn’t work and the config seems to be persisted as the “last successful update” time was the same before and after.

Is there any other fix for this besides trying to delete the entire repo and recreate it?

@austince This should have been taken care of with the introduction of this merge request, so it’s odd you’re still getting this. If you’re on GitLab.com would you mind submitting a support ticket? We’ll need to remove the lock file manually.

Hey Tristan,

Thanks for getting back to me. I opened a ticket and got it fixed by your team, so we’re all good! But yeah, not sure what caused it…

Best,
Austin

1 Like

Awesome, glad to hear you’re all set. :ok_hand:

Hi @Tristan,

I’m having the same issue in our GitLab repository where we are mirroring to GitHub. The error we get is:

2:Fetching remote upstream failed: Unable to create … commit-graph-chain.lock’: File exists. Another git process seems to be running in this repository, e.g. an editor opened by ‘git commit’. Please make sure all processes are terminated then try again. If it still fails, a git process may have crashed in this repository earlier: remove the file manually to continue.

How can I fix this?

Screenshot 2021-09-21 at 09.30.27
Screenshot 2021-09-21 at 09.30.35

Hey @vidar, that’s odd that you’re still seeing that. Would you mind opening a support ticket so we can take a look? Feel free to DM me the ticket number once you’ve opened it.