You are not logged in.
After painlessly running gitlab since version 9 on Arch I upgraded to gitlab-shell 8.4.0 tonight any ssh connections are met with the following error:
ssh -T gitlab@******
Failed to read config, falling back to gitlab-shell-ruby
Failed to exec("gitlab-shell-ruby"): no such file or directory
The config is present where I would expect it to be and nothing was manually changed aside from the upgrade and system restart
Offline
Haha! Solved my issue
At some point in the past I set the gitlab user's shell in /etc/passwd to the path to the gitlab-shell executable. This worked for a long time until gitlab-shell 8.4.0, for whatever reason this upgrade broke that. I restored function by deleting the shell from /etc/passwd
Offline
The gitlab-shell in /etc/passwd was not set by you, but systemd-sysusers: https://git.archlinux.org/svntogit/comm … tlab-shell
To restore the original behaviour, set gitlab-shell-ruby instead of gitlab-shell as the shell in /etc/passwd. Since 8.4.0 this appeared in /etc/webapps/gitlab-shell/config.yml, though I have no idea how that is supposed to work or if the gitlab-shell reimplementation in Go is actually usable.
# Migration to Go: anything listed here has two implementations. Use these flags
# to try the new implementations out, or to revert to the old behaviour if there
# problems arise.
migration:
enabled: false
features: []
Offline
There is a problem with path resolution in go implementation. So it's not able to find config file or ruby executable.
Opened a merge request.
Offline
Please report a bug if there is a problem with the package.
Offline
There is a problem with path resolution in go implementation. So it's not able to find config file or ruby executable.
Opened a merge request.
There is no response from upstream yet.
Patch merged by Sven-Hendrik Haase in 8.4.0-2 (Archlinux package). (Works, thanks!)
We can mark this thread solved.
Offline