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

Closed
Open
Created Jan 22, 2013 by Administrator@rootOwner

Installation Issue: cannot load such file -- omniauth/google/oauth2

Created by: basepi

I have been following the following guide to install GitLab on my Ubuntu 12.04 server: https://github.com/gitlabhq/gitlabhq/blob/stable/doc/install/installation.md

Everything went fairly smoothly until it came to the "Initialise Database and Activate Advanced Features" section. When I tried to run the following command:

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

It reported rake aborted! cannot load such file -- omniauth/google/oauth2

The full trace is here: https://gist.github.com/4561706

I should add that I found a similar issue on the tracker: https://github.com/gitlabhq/gitlabhq/issues/1667

Adding the :require to the Gemfile did fix the oauth2 problem, but I ran into the same openssl issue that was reported there, but recompiling my ruby did not help in my case.

Assignee
Assign to
Time tracking