gitlabhq/gitlab-recipes

About gitlab-shell version and errors happening when double-check status.

zh-f opened this issue · 0 comments

zh-f commented

When I followed this recipe to installed gitlab-shell using this command:

sudo -u git -H bundle exec rake gitlab:shell:install[v2.1.0] REDIS_URL=unix:/var/run/redis/redis.sock RAILS_ENV=production

I had this problem when checked application status:

Check GitLab API access: /home/git/gitlab-shell/lib/gitlab_net.rb:122:in read': No such file or directory @ rb_sysopen - /home/git/gitlab-shell/.gitlab_shell_secret (Errno::ENOENT) from /home/git/gitlab-shell/lib/gitlab_net.rb:122:insecret_token'
from /home/git/gitlab-shell/lib/gitlab_net.rb:79:in get' from /home/git/gitlab-shell/lib/gitlab_net.rb:39:incheck'
from /home/git/gitlab-shell/bin/check:11:in `

I googled about this error, and changed version of gitlab-shell into [v2.0.1].
Now, there is no Check GitLab API access: /home/git/gitlab-shell/lib/gitlab_net.rb:122:in read': No such file or directory but I have this Check GitLab API access: FAILED. code: 301.

So I wonder is this version causing gitlab_net.rb:122...? About Check GitLab API access: FAILED. code: 301, I am stilling trying to figure it out. Hope someone can help a little bit. 😄

Oops, I see a PR [here}(https://github.com//pull/261). But the file has not changed yet. I create another PR #281