-
-
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
Data race when terminating the progress #27643
Comments
The graceful manager has some bugs (go-gitea#27643, go-gitea#28062). This is a preparation for further fixes.
The graceful manager has some bugs (go-gitea#27643, go-gitea#28062). This is a preparation for further fixes.
I don't know if it is the same or 'just' a related Problem, but I can't even start the server without getting this message.
This happens both with 1.21.1 (latest package of my distro [gentoo]) and 1.21.6.... |
Could you share your steps? Including the environment variables & config files, etc. ps: would you like try docker? Usually I recommend to use docker if it is possible. |
|
I think it's caused by the incorrect config. Please refer to your logs, there should be some error logs. ps: in some cause, if the panic occurs too quickly, maybe some logs could be missing. I would suggest to empty the app.ini and try to start a fresh installation. For example, on my side, when error occurs:
|
The warning concerning "Unknown cipher" looks interesting, would be nice if somewhere within the docs I could read how I have to put this.... And the error concerning the certificates doesn't happen for me, because obviously I have those files with the correct access rights at the specified locations.... |
Yup, it might not be related to "certificates", nor "Unknown cipher" , but I think it could be related some "incorrect config" (#27643 (comment)). Actually I think there is a bug when running the "install" page when there are errors in the config file. I would still suggest you to try to empty the app.ini and try to start a fresh installation, to see whether the problem still exists. |
And a temp fix (for the "panic"): -> Avoid unexpected panic in graceful manager #29629 |
There is a fundamental design problem of the "manager" and the "wait group". If nothing has started, the "Wait" just panics: sync: WaitGroup is reused before previous Wait has returned There is no clear solution besides a complete rewriting of the "manager" If there are some mistakes in the app.ini, end users would just see the "panic", but not the real error messages. A real case: #27643 This PR is just a quick fix for the annoying panic problem.
I'll try the fix as soon as I have hoghspeedvolume avaliable again.... |
It should have been fixed by : Refactor graceful manager, fix misused WaitGroup (#29738) Feel free to reopen if there is still any problem. |
Description
git brach: main
possible fix:
gitea/modules/graceful/manager.go:232
gitea/modules/graceful/manager_unix.go:280
Gitea Version
Gitea version development built with go1.21.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
ubuntu 22.04
Database
None
The text was updated successfully, but these errors were encountered: