Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #1442

Closed
Open
Created Sep 12, 2012 by Administrator@rootOwner

Gitlab was unable to access your Gitolite system.

Created by: NeilBetham

I have just installed Gitlab from the guide in the repo and everything seems to work except for the Gitolite integration with Gitlab I have tried both running the application in a standalone mode and through Phusion Passenger to no avail. The git logs in Gitlab are less than helpful:

Logfile created on 2012-09-11 18:45:34 -0400 by logger.rb/31641 September 11, 2012 18:45 -> ERROR -> /home/gitlab/gitlab/tmp/gitlabhq-gitolite-1347403534/gitolite September 11, 2012 18:47 -> ERROR -> /home/gitlab/gitlab/tmp/gitlabhq-gitolite-1347403676/gitolite September 11, 2012 18:54 -> ERROR -> execution expired September 11, 2012 19:15 -> ERROR -> execution expired September 11, 2012 19:21 -> ERROR -> execution expired September 11, 2012 19:24 -> ERROR -> execution expired September 11, 2012 19:27 -> ERROR -> execution expired September 11, 2012 19:45 -> ERROR -> execution expired September 11, 2012 20:02 -> ERROR -> execution expired September 11, 2012 20:14 -> ERROR -> /home/gitlab/gitlab/tmp/gitlabhq-gitolite-1347408885/gitolite September 11, 2012 20:18 -> ERROR -> /home/gitlab/gitlab/tmp/gitlabhq-gitolite-1347409120/gitolite September 11, 2012 20:46 -> ERROR -> execution expired September 11, 2012 20:54 -> ERROR -> execution expired September 11, 2012 21:13 -> ERROR -> execution expired

Here is the output from the rake of app:status:

sudo -u gitlab bundle exec rake gitlab:app:status RAILS_ENV=production

Starting diagnostic config/database.yml............exists config/gitlab.yml............exists /home/git/repositories/............exists /home/git/repositories/ is writable?............YES remote: Counting objects: 12, done. remote: Compressing objects: 100% (8/8), done. remote: Total 12 (delta 1), reused 0 (delta 0) Receiving objects: 100% (12/12), done. Resolving deltas: 100% (1/1), done. Can clone gitolite-admin?............YES UMASK for .gitolite.rc is 0007? ............YES /home/git/share/gitolite/hooks/common/post-receive exists? ............YES

As for the operability of Gitolite, there seems to be no issues as far as I can tell:

sudo -u gitlab ssh -T git@localhost hello gitlab, this is gitolite v2.2.1-5-g8c4d1aa running on git 1.7.9.5 the gitolite config gives you the following access: R W gitolite-admin @R_ @W_ testing

Please let me know what else I can do to help solve this issue or what I am doing wrong.

Best Regards, Neil

Assignee
Assign to
Time tracking