Commit 3a836687 authored by Ben Bodenmiller's avatar Ben Bodenmiller Committed by Rémy Coutable

use timeout as it appears in logs

parent 15af0a45
...@@ -62,7 +62,8 @@ sudo gitlab-ctl status ...@@ -62,7 +62,8 @@ sudo gitlab-ctl status
Notice that all services say `ok: run`. Notice that all services say `ok: run`.
Sometimes, components time out during the restart and sometimes they get stuck. Sometimes, components time out (look for `timeout` in the logs) during the
restart and sometimes they get stuck.
In that case, you can use `gitlab-ctl kill <service>` to send the `SIGKILL` In that case, you can use `gitlab-ctl kill <service>` to send the `SIGKILL`
signal to the service, for example `sidekiq`. After that, a restart should signal to the service, for example `sidekiq`. After that, a restart should
perform fine. perform fine.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment