ssh - Gitlab not push branch, Access denied? -
ssh - Gitlab not push branch, Access denied? -
befor update gitlab v7, pushed branch. - access denied:
class="lang-bash prettyprint-override">$ git force origin my_branch access denied. fatal: not read remote repository. please create sure have right access rights , repository exists.
when check ssh_key, gitlab know me:
class="lang-bash prettyprint-override">$ ssh -t git@github.lcl.loc welcome gitlab, nikolay nozdrin-plotnitsky!
gitlab check: $ sudo -u git -h bundle exec rake gitlab:check rails_env=production instance method "lock!" defined in activerecord::base, utilize generic helper instead or set statemachine::machine.ignore_method_conflicts = true. checking environment ...
class="lang-bash prettyprint-override">git configured git user? ... yes checking environment ... finished checking gitlab shell ... gitlab shell version >= 1.9.6 ? ... ok (2.0.1) repo base of operations directory exists? ... yes repo base of operations directory symlink? ... no repo base of operations owned git:git? ... yes repo base of operations access drwxrws---? ... yes satellites access drwxr-x---? ... yes update hook up-to-date? ... no not find /home/git/gitlab-shell/hooks/update seek fixing it: check hooks_path in config/gitlab.yml check gitlab-shell installation more info see: doc/install/installation.md in section "gitlab shell" update hooks in repos links: ... can't check because of previous errors running /home/git/gitlab-shell/bin/check check gitlab api access: ok check directories , files: /home/git/repositories: ok /home/git/.ssh/authorized_keys: ok test redis-cli executable: redis-cli 2.4.14 send ping redis server: pong gitlab-shell self-check successful checking gitlab shell ... finished checking sidekiq ... running? ... yes number of sidekiq processes ... 1 checking sidekiq ... finished checking ldap ... ldap disabled in config/gitlab.yml checking ldap ... finished checking gitlab ... database config exists? ... yes database sqlite ... no migrations up? ... yes database contains orphaned usersgroups? ... no gitlab config exists? ... yes gitlab config outdated? ... no log directory writable? ... yes tmp directory writable? ... yes init script exists? ... yes init script up-to-date? ... yes projects have namespace: ... lpo / mkzd ... yes projects have satellites? ... lpo / mkzd ... yes redis version >= 2.0.0? ... yes git bin path "/usr/bin/git" git version >= 1.7.10 ? ... yes (1.7.10) checking gitlab ... finished $ sudo -u git -h bundle exec rake gitlab:env:info rails_env=production instance method "lock!" defined in activerecord::base, utilize generic helper instead or set statemachine::machine.ignore_method_conflicts = true. scheme info system: debian 7.4 current user: git using rvm: no ruby version: 2.1.2p95 gem version: 2.2.2 bundler version:1.7.4 rake version: 10.3.2 sidekiq version:2.17.0 gitlab info version: 7.0.0 revision: de9bf7d directory: /home/git/gitlab db adapter: mysql2 url: https://github.lcl.loc/gitlab http clone url: https://github.lcl.loc/gitlab/some-project.git ssh clone url: git@github.lcl.loc:some-project.git using ldap: no using omniauth: no gitlab shell version: 2.0.1 repositories: /home/git/repositories/ hooks: /home/git/gitlab-shell/hooks/ git: /usr/bin/git
what problem?
help me! , sorry english
as in issue 8106, must check nature of ssh key (personal key, or deploy one)
sometime, removing key straight server ~git/authorized_keys
can help (as in this issue): regenerate new one.
as asked in issue 8260, @ gitlab checks:
cd /home/git/gitlab sudo -u git -h bundle exec rake gitlab:check rails_env=production
the op confirms the issue resolved in gitlab 7.4+ (7.4.2). (following upgrade process "from 6.x or 7.x 7.4")
ssh gitlab
Comments
Post a Comment