Ok, I found the problem. My Gitliab setup was using a directory symlinked. I updated configuration by defining absolute directory instead (readlink -f /my/path/gitlab) and it solved problem
2014-04-28 10:48 GMT+02:00 Henri Gomez <[email protected]>: > No more luck with 6.8.1 > > I changed hook/update to !/usr/bin/ruby (as reported here > https://github.com/gitlabhq/gitlabhq/issues/3349) but problem persist. > > I'm using Ruby 1.9.3p392 (openSUSE 12.3) > > Any ideas ? > > > > 2014-04-28 10:25 GMT+02:00 Henri Gomez <[email protected]>: > > Same problem here with a fresh install of gitlab 6.7.5. >> I'm updating to 6.8.1 to see if it fix problem. >> >> >> 2014-04-21 1:50 GMT+02:00 Tom R <[email protected]>: >> >> Hi, >>> >>> I have recently installed the Gitlab master branch onto Ubuntu 14.04 >>> using the manual installation guide. I have setup an SSH key for the admin >>> user and have created a new project 'Test'. >>> >>> I can clone the repo OK: >>> >>> $ git clone [email protected]:repositories/tomr/test.git >>> Cloning into 'test'... >>> warning: You appear to have cloned an empty repository. >>> Checking connectivity... done. >>> >>> However I am unable to push to the repo: >>> >>> $ mkdir test >>> $ cd test/ >>> $ git init >>> Initialized empty Git repository in /Users/tomr/Desktop/test/.git/ >>> $ touch README >>> $ git add README >>> $ git commit -m 'first commit' >>> [master (root-commit) 85a17cf] first commit >>> 1 file changed, 0 insertions(+), 0 deletions(-) >>> create mode 100644 README >>> $ git remote add origin [email protected]:repositories/tomr/test.git >>> $ git push -u origin master >>> Counting objects: 3, done. >>> Writing objects: 100% (3/3), 211 bytes | 0 bytes/s, done. >>> Total 3 (delta 0), reused 0 (delta 0) >>> remote: GitLab: You are not allowed to access master! >>> remote: error: hook declined to update refs/heads/master >>> To [email protected]:repositories/tomr/test.git >>> ! [remote rejected] master -> master (hook declined) >>> error: failed to push some refs to '[email protected]: >>> repositories/tomr/test.git' >>> >>> Any help/pointers would be greatly appreciated and apologies if I'm >>> overlooking something obvious. >>> >>> contents of /home/git/gitlab-shell/config.yml: >>> >>> # GitLab user. git by default >>>> user: git >>>> # Url to gitlab instance. Used for api calls. Should end with a slash. >>>> gitlab_url: "https://gitlab.myserver.com/"; >>>> http_settings: >>>> # user: someone >>>> # password: somepass >>>> # ca_file: /etc/ssl/cert.pem >>>> # ca_path: /etc/pki/tls/certs >>>> self_signed_cert: false >>>> # Repositories path >>>> # Give the canonicalized absolute pathname, >>>> # REPOS_PATH MUST NOT CONTAIN ANY SYMLINK!!! >>>> # Check twice that none of the components is a symlink, including >>>> "/home". >>>> repos_path: "/home/git/repositories" >>>> # File used as authorized_keys for gitlab user >>>> auth_file: "/home/git/.ssh/authorized_keys" >>>> # Redis settings used for pushing commit notices to gitlab >>>> redis: >>>> bin: /usr/bin/redis-cli >>>> host: 127.0.0.1 >>>> port: 6379 >>>> # socket: /tmp/redis.socket # Only define this if you want to use >>>> sockets >>>> namespace: resque:gitlab >>>> # Log file. >>>> # Default is gitlab-shell.log in the root directory. >>>> # log_file: "/home/git/gitlab-shell/gitlab-shell.log" >>>> # Log level. INFO by default >>>> log_level: INFO >>>> # Audit usernames. >>>> # Set to true to see real usernames in the logs instead of key ids, >>>> which is easier to follow, but >>>> # incurs an extra API call on every gitlab-shell command. >>>> audit_usernames: false >>> >>> >>> envinfo: >>> >>> System information >>>> System: Ubuntu 14.04 >>>> Current User: git >>>> Using RVM: no >>>> Ruby Version: 1.9.3p484 >>>> Gem Version: 1.8.23 >>>> Bundler Version:1.6.2 >>>> Rake Version: 10.1.1 >>>> Sidekiq Version:2.17.0 >>>> GitLab information >>>> Version: 6.8.0.rc1 >>>> Revision: 2bfd95d >>>> Directory: /home/git/gitlab >>>> DB Adapter: mysql2 >>>> URL: https://gitlab.myserver.com >>>> HTTP Clone URL: https://gitlab.myserver.com/some-project.git >>>> SSH Clone URL: [email protected]:some-project.git >>>> Using LDAP: no >>>> Using Omniauth: no >>>> GitLab Shell >>>> Version: 1.9.1 >>>> Repositories: /home/git/repositories/ >>>> Hooks: /home/git/gitlab-shell/hooks/ >>>> Git: /usr/bin/git >>> >>> >>> gitlab check: >>> >>> Checking Environment ... >>> Git configured for git user? ... yes >>> Checking Environment ... Finished >>> Checking GitLab Shell ... >>> GitLab Shell version >= 1.9.1 ? ... OK (1.9.1) >>> Repo base directory exists? ... yes >>> Repo base directory is a symlink? ... no >>> Repo base owned by git:git? ... yes >>> Repo base access is drwxrws---? ... yes >>> Satellites access is drwxr-x---? ... yes >>> update hook up-to-date? ... yes >>> update hooks in repos are links: ... >>> tomr / Test ... repository is empty >>> Running /home/git/gitlab-shell/bin/check >>> Check GitLab API access: OK >>> Check directories and files: >>> /home/git/repositories: OK >>> /home/git/.ssh/authorized_keys: OK >>> Test redis-cli executable: redis-cli 2.8.4 >>> Send ping to 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 is disabled in config/gitlab.yml >>> Checking LDAP ... Finished >>> Checking GitLab ... >>> Database config exists? ... yes >>> Database is SQLite ... no >>> All 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: ... >>> tomr / Test ... yes >>> Projects have satellites? ... >>> tomr / Test ... can't create, repository is empty >>> Redis version >= 2.0.0? ... yes >>> Your git bin path is "/usr/bin/git" >>> Git version >= 1.7.10 ? ... yes (1.9.1) >>> Checking GitLab ... Finished >>> >>> -- >>> 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 [email protected]. >>> 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
