-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Pull mirrors not syncing #19928
Pull mirrors not syncing #19928
Comments
- Always give a best-effort to fetching the repositories, if even that fails indeed give a disconnected mirror found error. - *Partially* resolves go-gitea#19928
- Always give a best-effort to fetching the repositories, if even that fails indeed give a disconnected mirror found error. - *Partially* resolves #19928 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
What's the left problem? @wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf |
Could you try on the latest commit? You'll see the repo you linked on try is now syncing |
@lunny on my instance, the Always try to fetch repo for mirrors patch hasn't solved the syncing issue.
@techknowlogick I have just rebuilt from latest commit, waiting for mirror cron to kick in (10 minutes). you are right, both of the linked mirrors on try are syncing, so I am full of hopes :) edit: so it doesn't appear to have done the trick.. my also, I seem to be missing the |
tl;dr - problem solved, it was a misconfiguration on my side.alright, it appears I had a misconfigured so I guess the lesson learnt is do not put stuff in I still recall seing instructions to do sth like that in the logs, though, but I might as remember it wrong. funnily enough, same thing/issue (mirror syncing issue) also hit anyway, thank you all for your time and for helping me out, you can consider this resolved (at least on my end). |
OK. Let's close this one and please feel free to reopen it if you think it's not resolved. |
- Always give a best-effort to fetching the repositories, if even that fails indeed give a disconnected mirror found error. - *Partially* resolves go-gitea#19928 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
- Always give a best-effort to fetching the repositories, if even that fails indeed give a disconnected mirror found error. - *Partially* resolves go-gitea#19928 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
Hello @wULLSnpAXbWZGYDYyhWTKKspEQoaYxXyhoisqHf, This is not related to your question, but I'm just wondering how you got your Gitea homepage to look the way it does. I can't get these strange "templates" working and I honestly can't see how you did it. Can you please attach the code for the homepage? Thanks in advance. |
hey there, the |
Description
mirrors ("pull" style mirrors, to be clear) on my instance have not been updating since about May 21 this year, which was ~3 weeks ago.
that is, (automated) syncing does not work for any user, not just my own.
mirroring is enabled globally in
app.ini
and mirror cron is set to run "@every 10m
", minimal interval on repos satisfied.it also doesn't matter whether the mirror is newly added or a year-old one.
I've got a dedicated
mirror
user onto which I transfer many of the mirroring duties and its activity graph as of today looks like this:if you're wondering why you're seeing sync activity after said date (or in users activity feed), it's because I went on and manually synced some of the repositories (a couple of times) myself (as an administrator...).
indeed, the blank squares could also mean that there was nothing to pull/sync, but considering the user syncs some ~150 (fairly busy upstream projects') repos, the most common sync interval being in the range of 15m-6h and considering the fact that before said date most of the squares were usually not empty, I'd say it looks like an issue with mirror syncing on Gitea's end.
further, I am not aware of any changes (on my part) that could have caused this, I am running pretty vanilla Gitea (custom logos, templates + css...), as I have been for a past couple of years (thank you very much!), mirroring simply stopped working reliably.
examples
I checked and noticed that mirrors on try.gitea.io have not been updating for some time either.
example 1
see, e.g. this repo, which is a mirror of this thing on GitHub.
kratos
- try.gitea.io screenshot:kratos
- Github screenshot:the most recent date that the said mirror on
try
has been updated is 3 weeks ago, while the GH upstream was updated ~2 days ago.I also don't suppose the (mirror) syncing interval on
try
is set to more than 3 weeks.example 2
another similar example is this (note - default branch changed here, but it does not matter) (upstream being here), which also appears to have stopped syncing ~3 weeks ago, despite the fact that upstream was updated ~2 days ago.
what I tried to "fix" this issue locally:
app.ini
- to no availapp.ini
- to no availI was kinda hoping someone else had this issue (not in a bad way) as well and reported it and it would have been fixed by some kind soul by now, but that did not happen so here we are :)
Gitea Version
1.17.0+dev-686-g2ae45cebb
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
pertinent logs
Screenshots
see above
Git Version
git version 2.36.0.rc2.482.g48e68dd0fd
Operating System
Arch Linux
How are you running Gitea?
fresh binary built from sources, run with:
systemd
.Database
SQLite
EDIT 2022-06-15T11:59+02:00: added pertinent logs
The text was updated successfully, but these errors were encountered: