github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-13 19:37:47 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Unable to sync mirror repository #14374

New Issue
Closed
opened 2025-11-02 11:11:15 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 11:11:15 -06:00
Owner
Copy Link

Originally created by @zoumingzhe on GitHub (Apr 15, 2025).

Description

My mirror repository has been running for about three years, never had any problems.

Recently, I have noticed that my linux mirror repository has not been updated, and the last update was last week (April 9th). I did not see any errors in the logs!

I tried manually triggering synchronization, and now I can see the print information: "[E] Unable to push sync request for to the queue for pull mirror repo[4]. Error: already in queue".

My network is fine, I can access GitHub normally, and I can successfully create a new GitHub repository mirror.

Gitea Version

1.21.10 in dockerhub

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

Image

Image

Git Version

No response

Operating System

No response

How are you running Gitea?

podman-compose in CentOS Stream 9 with image tag is 1.21.10

Database

docker.io/library/mysql:8

Originally created by @zoumingzhe on GitHub (Apr 15, 2025). ### Description My mirror repository has been running for about three years, never had any problems. Recently, I have noticed that my linux mirror repository has not been updated, and the last update was last week (April 9th). I did not see any errors in the logs! I tried manually triggering synchronization, and now I can see the print information: "[E] Unable to push sync request for to the queue for pull mirror repo[4]. Error: already in queue". My network is fine, I can access GitHub normally, and I can successfully create a new GitHub repository mirror. ### Gitea Version 1.21.10 in dockerhub ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots ![Image](https://github.com/user-attachments/assets/dadf5a79-36b6-4cad-a09c-4eec023c3f60) ![Image](https://github.com/user-attachments/assets/475a6bf5-b352-4271-8560-35ae9953c716) ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? podman-compose in CentOS Stream 9 with image tag is 1.21.10 ### Database docker.io/library/mysql:8
GiteaMirror added the type/bug label 2025-11-02 11:11:15 -06:00
GiteaMirror commented 2025-11-02 11:11:16 -06:00
Author
Owner
Copy Link

@zoumingzhe commented on GitHub (Apr 15, 2025):

I upgraded Gitea to version 1.22.6, but the issue still persists.

From the monitoring data, it can be seen that the CPU usage and disk IO have significantly decreased in the past week:

Image

Image

It should be noted that there was no disk space available on April 4th, which happened to be a Chinese holiday. I expanded the disk and restarted the system after the holiday ended on April 9th. After the restart, the system successfully synchronized some mirror repositories.

@zoumingzhe commented on GitHub (Apr 15, 2025): I upgraded Gitea to version 1.22.6, but the issue still persists. From the monitoring data, it can be seen that the CPU usage and disk IO have significantly decreased in the past week: ![Image](https://github.com/user-attachments/assets/1b1c4c38-546b-414a-b3c8-90b6cf9e3eb1) ![Image](https://github.com/user-attachments/assets/d5cf7672-a260-46ca-8857-171669040aee) It should be noted that there was no disk space available on April 4th, which happened to be a Chinese holiday. I expanded the disk and restarted the system after the holiday ended on April 9th. After the restart, the system successfully synchronized some mirror repositories.
GiteaMirror commented 2025-11-02 11:11:16 -06:00
Author
Owner
Copy Link

@zoumingzhe commented on GitHub (Apr 15, 2025):

My synchronization time is set to 8 hours, while others are configured in mode with a minimum interval of 10 minutes.

@zoumingzhe commented on GitHub (Apr 15, 2025): My synchronization time is set to 8 hours, while others are configured in mode with a minimum interval of 10 minutes.
GiteaMirror commented 2025-11-02 11:11:16 -06:00
Author
Owner
Copy Link

@zoumingzhe commented on GitHub (Apr 15, 2025):

Image

@zoumingzhe commented on GitHub (Apr 15, 2025): ![Image](https://github.com/user-attachments/assets/ba1057c0-73c7-4d3f-9eb2-f358da5d73c5)
GiteaMirror commented 2025-11-02 11:11:16 -06:00
Author
Owner
Copy Link

@zoumingzhe commented on GitHub (Apr 15, 2025):

This is the monitoring of the mirror queue:
Image

@zoumingzhe commented on GitHub (Apr 15, 2025): This is the monitoring of the mirror queue: ![Image](https://github.com/user-attachments/assets/04d6ebbb-48e0-4d56-8ac8-0a7647bab976)
GiteaMirror commented 2025-11-02 11:11:16 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Apr 15, 2025):

Please upgrade to 1.23.7 and try again.

@lunny commented on GitHub (Apr 15, 2025): Please upgrade to 1.23.7 and try again.
GiteaMirror commented 2025-11-02 11:11:17 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Apr 15, 2025):

Click that "Remove All" button to clear the queue and retry.

See this: Broken queue causes various problems, need to report in self-check #33882

@wxiaoguang commented on GitHub (Apr 15, 2025): Click that "Remove All" button to clear the queue and retry. ---- See this: Broken queue causes various problems, need to report in self-check #33882
GiteaMirror commented 2025-11-02 11:11:17 -06:00
Author
Owner
Copy Link

@zoumingzhe commented on GitHub (Apr 15, 2025):

Click that "Remove All" button to clear the queue and retry.

See this: Broken queue causes various problems, need to report in self-check #33882

Thank you very much for your solution. Mirror synchronization has been restored.

Image

@zoumingzhe commented on GitHub (Apr 15, 2025): > Click that "Remove All" button to clear the queue and retry. > > See this: Broken queue causes various problems, need to report in self-check [#33882](https://github.com/go-gitea/gitea/issues/33882) Thank you very much for your solution. Mirror synchronization has been restored. <details> ![Image](https://github.com/user-attachments/assets/ab3eb5bb-f34f-492c-91fc-069b7175a3a1) </details>
GiteaMirror commented 2025-11-02 11:11:17 -06:00
Author
Owner
Copy Link

@zoumingzhe commented on GitHub (Apr 15, 2025):

close this issue

@zoumingzhe commented on GitHub (Apr 15, 2025): close this issue
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#14374
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?