-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
UpdatePublicKey: Failed to update public key: public key does not exist #2060
Comments
@gsantner The Are you sure there is a key with id 20 in the database (i.e. If for some reason you're not able to directly run the |
Sorry maybe I accidentally removed one during pasting to github. below is the export again. API: tried
It does, I directly accessed the database gitea is using. As said above, I can access/clone/push. But sometimes (multiple times a day, and often at CI) it just gives this error. The keys are correctly setted up at my clients.
|
@gsantner What is the value of The request |
I dont have any debugging tools or like that installed on the system. What shall I do, and where I can find the piece of information then? |
Btw: There is just one Gitea instance running on the system |
@gsantner From looking at the logs you've posted,
If neither of these reveal anything, then I'm stuck 😕 |
1 ) Well, it's localhost at a port yes, but apache is serving in front. (Which shouldn't matter anyway as I'm cloning via SSH)
|
Does in your app.ini config file has |
@lafriks Yep, under |
and it is not empty, right? (do not post it here just confirm it is not empty) |
of course it is there |
Could you reproduce that? Maybe take a look at the xorm.log? |
Yes, reproducible. serv.log.txt / xorm.log.txt. I deleted all logs before starting the script. Maybe some kind of race condition? Maybe related to a timestamp?
outputs: (59 clones out of 100 worked actually / loaded repo fully).
|
Thanks for detailed info, I will look into this |
@lafriks
In the Logs I can find |
@gsantner It works correctly wait before bash script finishes to execute and than check cloned repository count. Because at the end of git clone you have |
Thats what I tried too (before multiple script execution). fail2ban turned off. heres a log. I did check if some git is running too I tried the script too with 10 clones, that works. 100 may be a little heavy and unnatural, I'm just somewhat suprised it cannot be handled even if cloning is running from/to localhost. From the log: maybe an upstream bug in openssh? |
@gsantner try adding sleep before ls, might be that when scripts exits it child processes are also killed |
I did execute the commands manually after some time. as said, I'm sure no git clone was running. (At the multi-test two above yes, but not in the manual clones where the log comes from.)
[log.txt](https://github.com/go-gitea/gitea/files/1163090/log.txt)
Am 20. Juli 2017 18:18:31 MESZ schrieb Lauris BH <[email protected]>:
…
@gsantner try adding sleep before ls, might be that when scripts exits
it child processes are also killed
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
#2060 (comment)
--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
|
@gsantner I found out why are you having problem with 100 parallel clones. It is actually not a gitea fault but ssh servers anti ddos protection. By default ssh configuration has |
@lafriks Wow, thanks for finding that out 👍, and of course for fixing the bug |
[x]
):Description
Sometimes i'm not able to pull from gitea because of an
UpdatePublicKey
error. As also the CI service pulls from gitea repos, this creates a lot of build errors every day. The keys are all added to the gitea account and do have access to repos. I also deleted, readded the keys and did a (gite admin)-ssh key rewrite.gitea serv.log:
database entry (freshly added today):
client:
The text was updated successfully, but these errors were encountered: