gitlab_shell.rb:198:in `exec': No such file or directory - /home/git/gitlab-shell/bin/gitaly-upload-pack when git clone via ssh

Summary

/home/git/gitlab-shell/lib/gitlab_shell.rb:198:in `exec': No such file or directory - /home/git/gitlab-shell/bin/gitaly-upload-pack

when git clone via ssh

Steps to reproduce

  1. Install Gitlab CE from Source code using V11.2.3 refer to https://docs.gitlab.com/ee/install/installation.html.
  2. add ssh key in Gitlab
  3. git clone via ssh or git clone git@git.xxx.com:demo/example.git

What is the current bug behavior?

/home/git/gitlab-shell/lib/gitlab_shell.rb:198:in `exec': No such file or directory - /home/git/gitlab-shell/bin/gitaly-upload-pack (Errno::ENOENT)
	from /home/git/gitlab-shell/lib/gitlab_shell.rb:198:in `exec_cmd'
	from /home/git/gitlab-shell/lib/gitlab_shell.rb:163:in `process_cmd'
	from /home/git/gitlab-shell/lib/gitlab_shell.rb:56:in `exec'
	from /home/git/gitlab-shell/bin/gitlab-shell:24:in `'
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

What is the expected correct behavior?

can git clone via ssh

Relevant logs and/or screenshots


/home/git/gitlab-shell/lib/gitlab_shell.rb:198:in `exec': No such file or directory - /home/git/gitlab-shell/bin/gitaly-upload-pack (Errno::ENOENT)
	from /home/git/gitlab-shell/lib/gitlab_shell.rb:198:in `exec_cmd'
	from /home/git/gitlab-shell/lib/gitlab_shell.rb:163:in `process_cmd'
	from /home/git/gitlab-shell/lib/gitlab_shell.rb:56:in `exec'
	from /home/git/gitlab-shell/bin/gitlab-shell:24:in `'
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
System information
System:		Ubuntu 18.04
Current User:	git
Using RVM:	no
Ruby Version:	2.5.1p57
Gem Version:	2.7.6
Bundler Version:1.16.4
Rake Version:	12.3.1
Redis Version:	4.0.9
Git Version:	2.17.1
Sidekiq Version:5.1.3
Go Version:	go1.11 linux/amd64

GitLab information
Version:	11.2.3
Revision:	06cbee3bf9d
Directory:	/home/git/gitlab
DB Adapter:	postgresql
URL:		http://git.xxx.com
HTTP Clone URL:	http://git.xxx.com/some-group/some-project.git
SSH Clone URL:	git@git.xxx.com:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	no

GitLab Shell
Version:	8.1.1
Repository storage paths:
- default: 	/data/repo/git
Hooks:		/home/git/gitlab-shell/hooks
Git:		/usr/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


Checking GitLab Shell ...


GitLab Shell version >= 8.1.1 ? ... OK (8.1.1)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
2/1 ... ok
2/2 ... ok
2/3 ... ok
2/4 ... ok
2/5 ... ok
2/6 ... ok
2/7 ... ok
2/8 ... ok
2/9 ... ok
2/10 ... ok
3/11 ... ok
3/12 ... ok
3/13 ... ok
3/14 ... ok
3/15 ... ok
3/16 ... ok
4/17 ... ok
2/18 ... ok
4/20 ... ok
6/21 ... ok
6/22 ... ok
6/23 ... ok
6/24 ... ok
6/25 ... ok
6/26 ... ok
6/27 ... ok
Running /home/git/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK


Access to /home/git/.ssh/authorized_keys: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Sidekiq ...


Running? ... yes
Number of Sidekiq processes ... 1


Checking Sidekiq ... Finished


Reply by email is disabled in config/gitlab.yml
Checking LDAP ...


LDAP is disabled in config/gitlab.yml


Checking LDAP ... Finished


Checking GitLab ...


Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
Projects have namespace: ...
2/1 ... yes
2/2 ... yes
2/3 ... yes
2/4 ... yes
2/5 ... yes
2/6 ... yes
2/7 ... yes
2/8 ... yes
2/9 ... yes
2/10 ... yes
3/11 ... yes
3/12 ... yes
3/13 ... yes
3/14 ... yes
3/15 ... yes
3/16 ... yes
4/17 ... yes
2/18 ... yes
4/20 ... yes
6/21 ... yes
6/22 ... yes
6/23 ... yes
6/24 ... yes
6/25 ... yes
6/26 ... yes
6/27 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.5.1)
Git version >= 2.9.5 ? ... yes (2.17.1)
Git user has default SSH configuration? ... yes
Active users: ... 16


Checking GitLab ... Finished

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Edited by 🤖 GitLab Bot 🤖