Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to sync push mirror repo when repo is mirror repo #26059

Closed
hiifong opened this issue Jul 22, 2023 · 3 comments
Closed

Failed to sync push mirror repo when repo is mirror repo #26059

hiifong opened this issue Jul 22, 2023 · 3 comments
Labels

Comments

@hiifong
Copy link
Member

hiifong commented Jul 22, 2023

Description

Mirror repo from github to self-hosted gitea, and then add a push mirror for this repo. When the sync button is clicked, Error is displayed, and the mouse is placed on Error to display git cat-file --batch-check --batch-all-object [/data/gitea/data/gitea-repositories/mirrors/linux.git]: context deadline exceeded -

git cat-file --batch-check --batch-all-object [/data/gitea/data/gitea-repositories/mirrors/linux.git]: context deadline exceeded - 

image

View Notice Details
Jul 22, 2023, 10:38 PM GMT+8
Failed to update mirror repository '/data/gitea/data/gitea-repositories/mirrors/linux.git': fatal: Unable to create '/data/gitea/data/gitea-repositories/mirrors/linux.git/./objects/info/commit-graphs/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.

image

Gitea Version

v1.20+

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

./gitea web

Database

MySQL

@hiifong
Copy link
Member Author

hiifong commented Jul 22, 2023

Maybe the repo is too big

@cassiozareck
Copy link
Contributor

cassiozareck commented Jul 22, 2023

Im not a maintainer neither a experienced Gitea contributor. But I'm trying to figure out what it may be. I found 2 reasons

  1. By some reason gitea is spawning two git instances at same time in the same repository, creating this lock file that is giving the error
  2. The time was exceeded. Do it last more than 5 minutes? If so probably it exceeded the timeout. If you're self-hosting gitea by yourself maybe you can try to extend this timeout in own app.ini configuration file under Git properties

Its not clear for me what exactly what happen when timeout is exceeded but I'll search more

@lunny
Copy link
Member

lunny commented Jun 13, 2024

Duplicate of #22578

@lunny lunny marked this as a duplicate of #22578 Jun 13, 2024
@lunny lunny closed this as not planned Won't fix, can't repro, duplicate, stale Jun 13, 2024
@go-gitea go-gitea locked as resolved and limited conversation to collaborators Sep 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants