-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Server freezes when transferring the ownership #10549
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
Comments
@zeripath could be related to graceful stop |
I suspect that is likely due to the (already fixed in master and release/v1.11) critical issue with deadlock when growing worker pools. Either:
[queue]
BLOCK_TIMEOUT=0
We have to release v1.11.2 soon as we are getting more and more of these essentially duplicate issues. |
I will test it when 1.11.2 is released. |
Closing as fixed, please reopen if v1.11.2 does not fix it |
Still encounter server freeze problem with v1.11.3 when transferring ownership. |
I suspect that this is because there is a deadlock being caused. It should be fixed in 1.12 due to us now using |
I couldn't reproduce the problem in the same repository with v1.11.2. |
It will be an intermittent issue depending on if something locks a table in the intervening period. |
My environment: I transferred the repo from one organization to another organization. docker container log:
gitea log:
|
docker-compose config:
|
Tried with a small repo with only 46 commits and size of 155KB, nothing different happened. |
@ngugcx We think it's a locking problem that surfaced after we moved a lot of code to background. If it is in fact that problem, it will be fixed by #10368. Unfortunately, there's no workaround for it other than:
|
Still not fixed as at v1.11.4 where #10368 appears to be merged. |
@ry167 Do you use SQLite as well? |
@guillep2k Yep I do. If you think its potentially not to do with that I could try changing database type? Happy to help debug in any way |
@ry167 SQLite allows only one session at a time to hold the database for writing. It's essentially mono-session for writing. That caused us more than one headache in the past, especially since 1.11 introduced background queues to resolve some tasks. If you had been using another kind of database, then we would have known that this is not an SQLite-related issue and we need to look elsewhere for the cause. This doesn't mean this is an SQLite lock issue; only that it's still likely. The changes introduced in #10493 (#10368) aimed to reduce that problem to only edge cases. As for helping us debugging 😄, maybe you could follow the instructions in this comment and let us know the results? |
Hello. I encountered this issue again in another repository. I can reproduce this issue 100% of the time.
|
I can reproduce this as well. This issue has been present for me since version 1.11. My environment is Docker/Sqlite with only me as a user. |
@yasuokav That log is missing the rest of the goroutines. 🙁 |
@guillep2k I can't find any other useful information.
|
I think I encountered the same issue. When I try to move a repository from organization During shutdown I get the following errors:
|
Same here, running 1.11.4 and SQLite on debian. Interestingly, |
So the panic is because of the forced shutdown during deadlock - in particular during Hammer. It's not the cause but a symptom - and doesn't really provide much more information. The reason why the panic occurs is as follows:
|
Can confirm that this works in v1.11.7 - thanks!! |
Currently using 1.12.0+dev-89-gb264c3039 in a docker container (gitea/gitea:latest) and I'm experiencing this issue when transferring repositories between Organizations. I seem to be able to transfer from User to Org and vice versa as a workaround. |
@firephreek Could you fire another issue? |
b264c30 is 889 commits behind master It is 405 commits behind release/v1.12 and it is 343 commits behind v1.12.0 Please upgrade. |
[x]
):When I restart the frozen server:
Description
Today I encountered a strange bug. When I transfer a mirror repository, the server freezes until I manually restart it.
I checked the console and log and I don't see any error or warning.
When I re-migrated the same repository from Github and try to transfer it, it succeeded. But the problem with the old repository persisted.
Screenshots
The text was updated successfully, but these errors were encountered: