diff options
Diffstat (limited to 'doc/administration/troubleshooting/debug.md')
| -rw-r--r-- | doc/administration/troubleshooting/debug.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/administration/troubleshooting/debug.md b/doc/administration/troubleshooting/debug.md index 031f44b1f9f..aea891b8a77 100644 --- a/doc/administration/troubleshooting/debug.md +++ b/doc/administration/troubleshooting/debug.md @@ -45,7 +45,7 @@ session by running: ActiveRecord::Base.connection.execute('SET statement_timeout TO 0') ``` -Note that this change only affects the current Rails console session and will +This change only affects the current Rails console session and will not be persisted in the GitLab production environment or in the next Rails console session. @@ -213,7 +213,7 @@ downtime. Otherwise skip to the next section. exit ``` -Note that if the Puma process terminates before you are able to run these +If the Puma process terminates before you are able to run these commands, GDB will report an error. To buy more time, you can always raise the Puma worker timeout. For omnibus users, you can edit `/etc/gitlab/gitlab.rb` and increase it from 60 seconds to 600: @@ -285,5 +285,5 @@ The output in `/tmp/puma.txt` may help diagnose the root cause. ## More information -- [Debugging Stuck Ruby Processes](https://newrelic.com/blog/engineering/debugging-stuck-ruby-processes-what-to-do-before-you-kill-9/) +- [Debugging Stuck Ruby Processes](https://newrelic.com/blog/best-practices/debugging-stuck-ruby-processes-what-to-do-before-you-kill-9) - [Cheat sheet of using GDB and Ruby processes](gdb-stuck-ruby.txt) |