Hi Stan, thanks a lot for your support !
Unfortunately, still no breakthrough ... all hooks are pointing to /opt/gitlab/embedded/service/gitlab-shell/hooks And also the config file /opt/gitlab/embedded/service/gitlab-rails/config/gitlab.yml doesn't show anything wrong. So, still an open issue for me ... Thanks, YenZi Am Freitag, 16. Oktober 2015 11:54:44 UTC-7 schrieb Stan Hu: > > The gitlab-shell path should be configured in > /opt/gitlab/embedded/service/gitlab-rails/config/gitlab.yml, but it should > have the right default. Have you checked the symlink in your repositories? > There may be a stale symlink from hooks to /home/git/gitlab-shell For > example, you can scan your repositories: > > find /var/opt/gitlab/git-data/repositories -name hooks | xargs ls -al > > On Fri, Oct 16, 2015 at 11:32 AM, yenzi <yen...@googlemail.com > <javascript:>> wrote: > >> Hi, >> >> ok, I got the git push to work now properly. The issue was, that I had a >> symlink in my path to git-data. I have fixed that, but still I am relying >> on the /opt/gitlab/embedded/service/gitlab-shell to >> /home/git/gitlab-shell. I have grep'ed through all config files to see if I >> can find that "/home/git/gitlab-shell" path, but could not find anything >> like that. >> So, at the end of the day I have gitlab working, but of course I would >> rather like to get rid of this symlink workaround as it might break on some >> upcoming upgrade. >> >> If you have any other hint where to look into, please let me know. >> >> Thanks, >> >> YenZi >> >> >> Am Donnerstag, 15. Oktober 2015 15:02:42 UTC-7 schrieb yenzi: >>> >>> Hi Stan, >>> >>> unfortunately, this didn't help. The only way I can get at least a git >>> pull to work is, when I symlink /opt/gitlab/embedded/service/gitlab-shell >>> to /home/git/gitlab-shell. But that workaround doesn't seem to work for a >>> git push. >>> >>> When I remove the symlink and call the 2 commands you proposed, it is >>> still looking for gitlab-shell in /home/git ... >>> >>> Please help. Thanks. >>> >>> YenZi >>> >>> >>> Am Mittwoch, 14. Oktober 2015 18:42:14 UTC-7 schrieb Stan Hu: >>>> >>>> The repositories have symlinks to the old gitlab-shell binary. Try to >>>> recreate the hooks: >>>> >>>> sudo -u git /opt/gitlab/embedded/service/gitlab-shell/bin/create-hooks >>>> >>>> Then run: >>>> >>>> sudo gitlab-rake gitlab:check >>>> >>>> >>>> >>>> On Wed, Oct 14, 2015 at 5:49 PM, yenzi <yen...@googlemail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> I have migrated our gitlab server to another machine. Gitlab was still >>>>> version 7.10 on the old machine installed from sources. So I set up a >>>>> 7.10 >>>>> server on the new machine (ubuntu) using the omnibus package. I created a >>>>> backup on the old machine and transformed the sql file from mysql to >>>>> postgresql and finally imported the backup successfully on the new >>>>> machine. >>>>> Then I have upgraded the gitlab version to 8.0.5. >>>>> >>>>> Everything is working on the Web side of things. But when I try to >>>>> clone a repository I get this error message : >>>>> >>>>> git clone g...@myserver.com:mygroup/myproject.git >>>>> >>>>> Cloning into 'myproject'... >>>>> >>>>> sh: 1: /home/git/gitlab-shell/bin/gitlab-shell: not found >>>>> >>>>> fatal: Could not read from remote repository. >>>>> >>>>> >>>>> >>>>> Please make sure you have the correct access rights >>>>> >>>>> and the repository exists. >>>>> >>>>> >>>>> I don't know why it tries to run gitlab-shell from the location when >>>>> it was installed on the old machine. >>>>> >>>>> >>>>> Any ideas ? >>>>> >>>>> >>>>> Thanks, >>>>> >>>>> >>>>> YenZi >>>>> >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "GitLab" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to gitlabhq+u...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/gitlabhq/aacaac25-9a05-4a4c-bb40-f5316652f9f1%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/gitlabhq/aacaac25-9a05-4a4c-bb40-f5316652f9f1%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >> You received this message because you are subscribed to the Google Groups >> "GitLab" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to gitlabhq+u...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/gitlabhq/bd160e25-53d2-41b0-b942-b7c8a410b2d2%40googlegroups.com >> >> <https://groups.google.com/d/msgid/gitlabhq/bd160e25-53d2-41b0-b942-b7c8a410b2d2%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/d7afdbb7-e35c-4f8a-bea1-63a6ee6aca9a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
