diff options
Diffstat (limited to 'doc/administration/troubleshooting')
| -rw-r--r-- | doc/administration/troubleshooting/debug.md | 4 | ||||
| -rw-r--r-- | doc/administration/troubleshooting/postgresql.md | 2 | ||||
| -rw-r--r-- | doc/administration/troubleshooting/ssl.md | 2 |
3 files changed, 4 insertions, 4 deletions
diff --git a/doc/administration/troubleshooting/debug.md b/doc/administration/troubleshooting/debug.md index 295dab2be38..d0c1f3fa0ff 100644 --- a/doc/administration/troubleshooting/debug.md +++ b/doc/administration/troubleshooting/debug.md @@ -241,7 +241,7 @@ separate Rails process to debug the issue: app.get 'https://gitlab.com/gitlab-org/gitlab-foss/issues/1?private_token=123456' ``` -1. In a new window, run `top`. It should show this ruby process using 100% CPU. Write down the PID. +1. In a new window, run `top`. It should show this Ruby process using 100% CPU. Write down the PID. 1. Follow step 2 from the previous section on using gdb. ### GitLab: API is not accessible @@ -275,4 +275,4 @@ The output in `/tmp/unicorn.txt` may help diagnose the root cause. ## More information - [Debugging Stuck Ruby Processes](https://blog.newrelic.com/engineering/debugging-stuck-ruby-processes-what-to-do-before-you-kill-9/) -- [Cheatsheet of using gdb and ruby processes](gdb-stuck-ruby.txt) +- [Cheatsheet of using gdb and Ruby processes](gdb-stuck-ruby.txt) diff --git a/doc/administration/troubleshooting/postgresql.md b/doc/administration/troubleshooting/postgresql.md index 966db356849..8e7727ee214 100644 --- a/doc/administration/troubleshooting/postgresql.md +++ b/doc/administration/troubleshooting/postgresql.md @@ -111,7 +111,7 @@ statement_timeout = 15s idle_in_transaction_session_timeout = 60s ``` -Quoting from from issue [#1](https://gitlab.com/gitlab-org/gitlab/issues/30528): +Quoting from issue [#1](https://gitlab.com/gitlab-org/gitlab/issues/30528): > "If a deadlock is hit, and we resolve it through aborting the transaction after a short period, then the retry mechanisms we already have will make the deadlocked piece of work try again, and it's unlikely we'll deadlock multiple times in a row." diff --git a/doc/administration/troubleshooting/ssl.md b/doc/administration/troubleshooting/ssl.md index b66b6e8c90a..f230f047ded 100644 --- a/doc/administration/troubleshooting/ssl.md +++ b/doc/administration/troubleshooting/ssl.md @@ -50,7 +50,7 @@ If you have the problems listed above, add your certificate to `/etc/gitlab/trus Besides getting the errors mentioned in [Using an internal CA certificate with GitLab](ssl.md#using-an-internal-ca-certificate-with-gitlab), -your CI pipelines may stuck stuck in `Pending` status. In the runner logs you may see the below error: +your CI pipelines may get stuck in `Pending` status. In the runner logs you may see the below error: ```shell Dec 6 02:43:17 runner-host01 gitlab-runner[15131]: #033[0;33mWARNING: Checking for jobs... failed |