Add a documentation note for Windows Service (#26938)
Service may fail to start at boot time with timeout Resolves #26934 Co-authored-by: Nikolay Kobzarev <n.kobzarev@aeronavigator.ru>
This commit is contained in:
parent
a7d9a70552
commit
b3d88ada01
1 changed files with 9 additions and 0 deletions
|
@ -51,6 +51,15 @@ Open "Windows Services", search for the service named "gitea", right-click it an
|
||||||
"Run". If everything is OK, Gitea will be reachable on `http://localhost:3000` (or the port
|
"Run". If everything is OK, Gitea will be reachable on `http://localhost:3000` (or the port
|
||||||
that was configured).
|
that was configured).
|
||||||
|
|
||||||
|
## Service startup type
|
||||||
|
|
||||||
|
It was observed that on loaded systems during boot Gitea service may fail to start with timeout records in Windows Event Log.
|
||||||
|
In that case change startup type to `Automatic-Delayed`. This can be done during service creation, or by running config command
|
||||||
|
|
||||||
|
```
|
||||||
|
sc.exe config gitea start= delayed-auto
|
||||||
|
```
|
||||||
|
|
||||||
## Adding startup dependencies
|
## Adding startup dependencies
|
||||||
|
|
||||||
To add a startup dependency to the Gitea Windows service (eg Mysql, Mariadb), as an Administrator, then run the following command:
|
To add a startup dependency to the Gitea Windows service (eg Mysql, Mariadb), as an Administrator, then run the following command:
|
||||||
|
|
Loading…
Reference in a new issue