-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Upgrade to Gitea 1.15.0 - service doesn't start WinSrv 2008R2 #16784
Comments
Did you follow the migration notes described in https://blog.gitea.io/2021/08/gitea-1.15.0-is-released? ..this looks quite similar to #16779, as the log does not contain any errors and fails to start after the update. |
Can you try just starting gitea from a command line and seeing if something is emitted there. |
Hello, in the meantime I figured out what was wrong. I had a "install-service"- script with "\" as folder dividers for the app.ini. This does not seem to work anymore. I changed my add service script and re-installed the service (remove & add again). This made my gitea server start again. Additionally I had an error in an template where I exchanged the gitea logo with our company logo and the new version did not find the "{{StaticUrlPrefix}}" variable anymore. I just deleted the template and now gitea seems to work again. Nevertheless, thanks you for the fast response; Sascha |
this is probably the root cause for the death. It causes an unguarded panic in a goroutine when the templates get compiled and kills the server. The panic would only get emitted on the console as it's completely unguarded and so its logging is made by the go runtime as it kills program - not our logging suite. |
[x]
):log.txt
Hi,
I tried updating from v1.14.6 to 1.15.0. After restarting the service I get an error 1067 from Services:
In the log files I could not see any error. Last entry finishes with:
[2 Cron: Check all repository statistics has finished 1629713364] - 1ms
I already switched log to "DEBUG".
KR,
Sascha
The text was updated successfully, but these errors were encountered: