-
-
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
Gitea not starting as Windows service #6722
Comments
Windows should not check that RUN_USER. See gitea/modules/setting/setting.go Line 430 in 2262811
|
I think this condition is evaluating to false gitea/modules/setting/setting.go Line 431 in 2262811
I'm kinda new to Go and maybe I'm wrong, but I searched the code and i don't see any assignment to the variable isWindows, that was removed by #6095 |
Great catch, it looks as though If you are comfortable building Gitea yourself you could test to see if it fixes your issue (I'm thinking it probably will) |
This weekend I'll try to fix and built it, if everything works fine I'll submit the PR if someone won't have done it already (it should be my first contribution to gitea 💪). |
Signed-off-by: Nicola Scattaglia <[email protected]>
Signed-off-by: Nicola Scattaglia <[email protected]>
Log file is not created
Description
I upgraded from 5f4a40c to 2a0e86d (current master release), but when I restarted the service I got Error 1067. I tried lunching the exe from the command line and I got:
Expect user 'X' but current user is: Y
So I changed the RUN_USER to X inside app.ini, relaunched the exe from the cmd and gitea was up and running. But when I try to start gitea from the service (registered with nssm) I keep getting the same error 1067. Any idea of what might have changed?
The text was updated successfully, but these errors were encountered: