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
  • #1038

Closed
Open
Created Jul 04, 2012 by Administrator@rootOwner

gitolite timeout

Created by: wafcio

I run

$ bundle exec rake gitlab:app:setup RAILS_ENV=production --trace

and I got error like this:

== Seed from /home/gitlab/gitlab/db/fixtures/production/001_admin.rb

Administrator account created:

[email protected] password......5iveL!fe ** Invoke gitlab:app:enable_automerge (first_time) ** Invoke environment ** Execute gitlab:app:enable_automerge rake aborted! gitolite timeout /home/gitlab/gitlab/lib/gitlab/gitolite.rb:50:in rescue in configure' /home/gitlab/gitlab/lib/gitlab/gitolite.rb:36:inconfigure'

I use installation instruction for stable version.

First time when I tried install gitlab everything were ok, but when I try push fresh repo to server git user want type password. This is really strange.

When I am logged as gitlab user I can clone admin repo without any problems. So gitolite works ok. It should be some bug in rake task, or install guide.

Assignee
Assign to
Time tracking