mirror of
https://github.com/go-gitea/gitea.git
synced 2026-03-12 10:39:38 -05:00
Server freezes when transferring the ownership #4975
Closed
opened 2025-11-02 06:09:40 -06:00 by GiteaMirror
·
27 comments
No Branch/Tag Specified
main
release/v1.25
release/v1.24
release/v1.23
release/v1.22
release/v1.21
release/v1.20
release/v1.19
release/v1.18
release/v1.17
release/v1.16
release/v1.15
release/v1.14
release/v1.13
release/v1.12
release/v1.11
release/v1.10
release/v1.9
release/v1.8
v1.25.3
v1.25.2
v1.25.1
v1.25.0
v1.24.7
v1.25.0-rc0
v1.26.0-dev
v1.24.6
v1.24.5
v1.24.4
v1.24.3
v1.24.2
v1.24.1
v1.24.0
v1.23.8
v1.24.0-rc0
v1.25.0-dev
v1.23.7
v1.23.6
v1.23.5
v1.23.4
v1.23.3
v1.23.2
v1.23.1
v1.23.0
v1.23.0-rc0
v1.24.0-dev
v1.22.6
v1.22.5
v1.22.4
v1.22.3
v1.22.2
v1.22.1
v1.22.0
v1.23.0-dev
v1.22.0-rc1
v1.21.11
v1.22.0-rc0
v1.21.10
v1.21.9
v1.21.8
v1.21.7
v1.21.6
v1.21.5
v1.21.4
v1.21.3
v1.21.2
v1.20.6
v1.21.1
v1.21.0
v1.21.0-rc2
v1.21.0-rc1
v1.20.5
v1.22.0-dev
v1.21.0-rc0
v1.20.4
v1.20.3
v1.20.2
v1.20.1
v1.20.0
v1.19.4
v1.21.0-dev
v1.20.0-rc2
v1.20.0-rc1
v1.20.0-rc0
v1.19.3
v1.19.2
v1.19.1
v1.19.0
v1.19.0-rc1
v1.20.0-dev
v1.19.0-rc0
v1.18.5
v1.18.4
v1.18.3
v1.18.2
v1.18.1
v1.18.0
v1.17.4
v1.18.0-rc1
v1.19.0-dev
v1.18.0-rc0
v1.17.3
v1.17.2
v1.17.1
v1.17.0
v1.17.0-rc2
v1.16.9
v1.17.0-rc1
v1.18.0-dev
v1.16.8
v1.16.7
v1.16.6
v1.16.5
v1.16.4
v1.16.3
v1.16.2
v1.16.1
v1.16.0
v1.15.11
v1.17.0-dev
v1.16.0-rc1
v1.15.10
v1.15.9
v1.15.8
v1.15.7
v1.15.6
v1.15.5
v1.15.4
v1.15.3
v1.15.2
v1.15.1
v1.14.7
v1.15.0
v1.15.0-rc3
v1.14.6
v1.15.0-rc2
v1.14.5
v1.16.0-dev
v1.15.0-rc1
v1.14.4
v1.14.3
v1.14.2
v1.14.1
v1.14.0
v1.13.7
v1.14.0-rc2
v1.13.6
v1.13.5
v1.14.0-rc1
v1.15.0-dev
v1.13.4
v1.13.3
v1.13.2
v1.13.1
v1.13.0
v1.12.6
v1.13.0-rc2
v1.14.0-dev
v1.13.0-rc1
v1.12.5
v1.12.4
v1.12.3
v1.12.2
v1.12.1
v1.11.8
v1.12.0
v1.11.7
v1.12.0-rc2
v1.11.6
v1.12.0-rc1
v1.13.0-dev
v1.11.5
v1.11.4
v1.11.3
v1.10.6
v1.12.0-dev
v1.11.2
v1.10.5
v1.11.1
v1.10.4
v1.11.0
v1.11.0-rc2
v1.10.3
v1.11.0-rc1
v1.10.2
v1.10.1
v1.10.0
v1.9.6
v1.9.5
v1.10.0-rc2
v1.11.0-dev
v1.10.0-rc1
v1.9.4
v1.9.3
v1.9.2
v1.9.1
v1.9.0
v1.9.0-rc2
v1.10.0-dev
v1.9.0-rc1
v1.8.3
v1.8.2
v1.8.1
v1.8.0
v1.8.0-rc3
v1.7.6
v1.8.0-rc2
v1.7.5
v1.8.0-rc1
v1.9.0-dev
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.7.0-rc3
v1.6.4
v1.7.0-rc2
v1.6.3
v1.7.0-rc1
v1.7.0-dev
v1.6.2
v1.6.1
v1.6.0
v1.6.0-rc2
v1.5.3
v1.6.0-rc1
v1.6.0-dev
v1.5.2
v1.5.1
v1.5.0
v1.5.0-rc2
v1.5.0-rc1
v1.5.0-dev
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.4.0-rc3
v1.4.0-rc2
v1.3.3
v1.4.0-rc1
v1.3.2
v1.3.1
v1.3.0
v1.3.0-rc2
v1.3.0-rc1
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.2.0-rc3
v1.2.0-rc2
v1.1.4
v1.2.0-rc1
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.2
v1.0.1
v1.0.0
v0.9.99
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
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
Mirrored from GitHub Pull Request
No Label
type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/gitea#4975
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Originally created by @ghost on GitHub (Mar 1, 2020).
[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
@lafriks commented on GitHub (Mar 1, 2020):
@zeripath could be related to graceful stop
@zeripath commented on GitHub (Mar 2, 2020):
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:
We have to release v1.11.2 soon as we are getting more and more of these essentially duplicate issues.
@ghost commented on GitHub (Mar 2, 2020):
I will test it when 1.11.2 is released.
@lafriks commented on GitHub (Mar 4, 2020):
Closing as fixed, please reopen if v1.11.2 does not fix it
@ngugcx commented on GitHub (Mar 11, 2020):
Still encounter server freeze problem with v1.11.3 when transferring ownership.
No errors found in the log.
@zeripath commented on GitHub (Mar 11, 2020):
I suspect that this is because there is a deadlock being caused. It should be fixed in 1.12 due to us now using
BEGIN IMMEDIATEfor SQLite. Could you check on Master to see if it still happens. If it does not we can close this properly.@ghost commented on GitHub (Mar 11, 2020):
I couldn't reproduce the problem in the same repository with v1.11.2.
@zeripath commented on GitHub (Mar 11, 2020):
It will be an intermittent issue depending on if something locks a table in the intervening period.
@ngugcx commented on GitHub (Mar 11, 2020):
My environment:
Hardware: Virtualbox vm, 2g ram, 1 core.
OS: Ubuntu 18.04
Database: default sqlite
Gitea version: docker container, gitea/gitea:1.11.3, gitea/gitea:1.11.2, then gitrea/gitea:latest
Repo to transfer: There is only one repo, which has about 10,000 commits and size of 20MB.
I transferred the repo from one organization to another organization.
All failed with no errors in both container log and gitea log. The web page timeouted finally, and couldn't recover until restarted.
docker container log:
gitea log:
@ngugcx commented on GitHub (Mar 11, 2020):
docker-compose config:
@ngugcx commented on GitHub (Mar 12, 2020):
Tried with a small repo with only 46 commits and size of 155KB, nothing different happened.
@guillep2k commented on GitHub (Mar 12, 2020):
@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:
master(it can have other bugs, though).@ryanhalliday commented on GitHub (Apr 4, 2020):
Still not fixed as at v1.11.4 where #10368 appears to be merged.
@guillep2k commented on GitHub (Apr 4, 2020):
@ry167 Do you use SQLite as well?
@ryanhalliday commented on GitHub (Apr 4, 2020):
@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
@guillep2k commented on GitHub (Apr 4, 2020):
@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?
@ghost commented on GitHub (Apr 17, 2020):
Hello. I encountered this issue again in another repository. I can reproduce this issue 100% of the time.
@guillep2k
@lukeawyatt commented on GitHub (Apr 17, 2020):
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.
@guillep2k commented on GitHub (Apr 18, 2020):
@yasuokav That log is missing the rest of the goroutines. 🙁
@ghost commented on GitHub (Apr 18, 2020):
@guillep2k I can't find any other useful information.
@martinburger commented on GitHub (Apr 25, 2020):
I think I encountered the same issue. When I try to move a repository from organization
AtoB, the Gitea server just stalls. Thus, I have to restart Gitea. Please note that I am using latest version1.11.4andsqlite3as database type.During shutdown I get the following errors:
@nimo-labs commented on GitHub (Apr 25, 2020):
Same here, running 1.11.4 and SQLite on debian.
As soon as I try and transfer a repo from one organisation to another Gitea freezes.
Interestingly,
service gitea restartdoesn't work,service gitea stopalso doesn't work either. Howeverservice gitea stopfollowed byctrl-cfollowed bykill -9 'PID'finally leaves me in a position whereby I can restart the service.@zeripath commented on GitHub (Apr 26, 2020):
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:
3a. If the deadlocked xorm connection is broken - then the deadlocked request can end.
finishing - clearly in this case the server waitgroup counter is decremented quicker than the xorm connection releases and the request ends.
@ryanhalliday commented on GitHub (Jun 19, 2020):
Can confirm that this works in v1.11.7 - thanks!!
@firephreek commented on GitHub (Sep 14, 2020):
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.
@lunny commented on GitHub (Sep 14, 2020):
@firephreek Could you fire another issue?
@zeripath commented on GitHub (Sep 14, 2020):
b264c3039is 889 commits behind masterIt is 405 commits behind release/v1.12
and it is 343 commits behind v1.12.0
Please upgrade.