Skip to content

Commit f99bb40

Browse files
WarheadsSEereadAlexandr Tanayno
committed
Merge branch 'docs-add-ssh-error-troubleshooting' into 'master'
Add section about troubleshooting SSH push/pull error See merge request https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/7534 Merged-by: Jason Plum <[email protected]> Approved-by: Evan Read <[email protected]> Approved-by: Jason Plum <[email protected]> Reviewed-by: Evan Read <[email protected]> Co-authored-by: Evan Read <[email protected]> Co-authored-by: Alexandr Tanayno <[email protected]>
2 parents 59cb03c + 668e97e commit f99bb40

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed

doc/troubleshooting.md

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1048,3 +1048,18 @@ net.core.somaxconn = 1024
10481048

10491049
You may experience timeouts or HTTP 502 errors and is recommended to increase this
10501050
value by updating the `puma['somaxconn']` variable in your `gitlab.rb`.
1051+
1052+
## `exec request failed on channel 0` or `shell request failed on channel 0` errors
1053+
1054+
When pulling or pushing by using Git over SSH, you might see the following errors:
1055+
1056+
- `exec request failed on channel 0`
1057+
- `shell request failed on channel 0`
1058+
1059+
These errors can happen if the number of processes from the `git` user is above the limit.
1060+
1061+
To try and resolve this issue:
1062+
1063+
1. Increase the `nproc` setting for the `git` user in the `/etc/security/limits.conf` file on the nodes where `gitlab-shell` is running.
1064+
Typically, `gitlab-shell` runs on GitLab Rails nodes.
1065+
1. Retry the pull or push Git command.

0 commit comments

Comments
 (0)