Skip to content

GitLab

Closed
Created by Administrator@rootOwner

gitlab:setup fails from 'missing' pg bundle although Gemfile, contains pg. Same when using mysql. Complains mysql2 bundle is not install.

Closed

gitlab:setup fails from 'missing' pg bundle although Gemfile, contains pg. Same when using mysql. Complains mysql2 bundle is not install.

Created by: editstudio

Hi,

I have been trying to do a first time setup of gitlab on a freash 12.10 ubuntu install. Unfortunalty, I can only get as far as the step "Initialise Database and Activate Advanced Features", and after running the command:

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

Which results in the (full) response:

rake aborted!
Please install the postgresql adapter: `gem install activerecord-postgresql-adapter` (pg is not part of the bundle. Add it to Gemfile.)
/var/lib/gems/1.9.1/gems/bundler-1.2.3/lib/bundler/rubygems_integration.rb:147:in `block in replace_gem'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/connection_adapters/postgresql_adapter.rb:7:in `<top (required)>'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:251:in `require'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:251:in `block in require'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:236:in `load_dependency'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:251:in `require'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/connection_adapters/abstract/connection_specification.rb:50:in `resolve_hash_connection'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/connection_adapters/abstract/connection_specification.rb:41:in `resolve_string_connection'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/connection_adapters/abstract/connection_specification.rb:25:in `spec'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/connection_adapters/abstract/connection_specification.rb:130:in `establish_connection'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/railtie.rb:82:in `block (2 levels) in <class:Railtie>'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/lazy_load_hooks.rb:36:in `instance_eval'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/lazy_load_hooks.rb:36:in `execute_hook'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/lazy_load_hooks.rb:26:in `block in on_load'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/lazy_load_hooks.rb:25:in `each'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/lazy_load_hooks.rb:25:in `on_load'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activerecord-3.2.11/lib/active_record/railtie.rb:74:in `block in <class:Railtie>'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.11/lib/rails/initializable.rb:30:in `instance_exec'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.11/lib/rails/initializable.rb:30:in `run'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.11/lib/rails/initializable.rb:55:in `block in run_initializers'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.11/lib/rails/initializable.rb:54:in `each'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.11/lib/rails/initializable.rb:54:in `run_initializers'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.11/lib/rails/application.rb:136:in `initialize!'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.11/lib/rails/railtie/configurable.rb:30:in `method_missing'
/home/gitlab/gitlab/config/environment.rb:5:in `<top (required)>'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:251:in `require'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:251:in `block in require'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:236:in `load_dependency'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/activesupport-3.2.11/lib/active_support/dependencies.rb:251:in `require'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.11/lib/rails/application.rb:103:in `require_environment!'
/home/gitlab/gitlab/vendor/bundle/ruby/1.9.1/gems/railties-3.2.11/lib/rails/application.rb:297:in `block (2 levels) in initialize_tasks'
Tasks: TOP => gitlab:setup => environment
(See full trace by running task with --trace)

I do have the following lines in the Gemfile:

# Supported DBs
gem "mysql2", group: :mysql
gem "pg", group: :postgres

and bundler installed all dependencies successfully. I have not been able to figure out why it says pg is not part of the bundle. Has anyone had a similar problem?

  • Administrator
    Administrator @root ·
    Owner

    Created by: zzet

    please, read docs

    By Administrator on 2013-01-27T09:13:05 (imported from GitLab project)

  • Administrator
    Administrator @root ·
    Owner

    Created by: editstudio

    I did read them, and the troubleshooting, I must have missed something.

    Regardless, I did a bundle install without any parameters, then again with production options and it works.

    @zzet: if you could point out what I missed, I would greatly appreciate it :)

    By Administrator on 2013-01-27T09:26:12 (imported from GitLab project)

  • Administrator
    Administrator @root ·
    Owner

    Created by: editstudio

    Same problem came up when running

    sudo -u git -H bundle exec rake db:migrate RAILS_ENV=production

    following upgrade instructions. Still not sure why this happens. Can't find anything in the docs... Don't know why the message came back. Not very familiar with ruby and their gems so a point in the right direction would be highly appreciated.

    By Administrator on 2013-03-24T09:43:01 (imported from GitLab project)

  • Administrator
    Administrator @root ·
    Owner

    Created by: zzet

    @editstudio you need Grant privileges for user git to Gitlab database

    By Administrator on 2013-03-24T09:50:37 (imported from GitLab project)

  • Administrator
    Administrator @root ·
    Owner

    Created by: anibalpacheco

    I give up migration 4.2 to 5.0, same problem and tried everything, EVERITHING. I'll install 5 from scratch, thanks

    By Administrator on 2013-04-09T19:59:47 (imported from GitLab project)

  • Administrator
    Administrator @root ·
    Owner

    Created by: baubie

    Solved: Note to all others who find this, note the "--without" in the line. If you see postgresql then you are going forward WITHOUT postgresql. You with the --without line to have mysql in it.

    By Administrator on 2013-04-10T14:38:24 (imported from GitLab project)

  • Administrator
    Administrator @root ·
    Owner

    Created by: KristerV

    My fault was that I didn't read the instructions carefully enough. I had installed both MySQL and PostgreSQL, configured config/database.yml for postgre and tried to bundle excec for mysql.. man I wasted so much time thinking the guide was noob-proof :D

    By Administrator on 2013-12-04T18:03:38 (imported from GitLab project)

Please register or sign in to reply