Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
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
  • #5820

Closed
Open
Created 11 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

rake aborted! wrong number of arguments (0 for 1..3)

Closed

rake aborted! wrong number of arguments (0 for 1..3)

Created by: fraywing

Hey there!

I'm having a weird issue, I'm running Ubuntu with Apache, I already have the Mysql DB created, the user is has correct permissions, and have followed the specs for the official install to the tee.

I'm able to access the login page on the dashboard on my server, but when I try to create the default admin credentials using:

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

I'm greeted with an error, below i'll paste the entirety of the --trace'd log:

    == Seed from /home/git/gitlab/db/fixtures/production/001_admin.rb
    rake aborted!
    wrong number of arguments (0 for 1..3)
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:46:in `eval'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:14:in `block in logger'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/relation.rb:241:in `block in scoping'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/scoping.rb:98:in `with_scope'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/relation.rb:241:in `scoping'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/relation/delegation.rb:14:in `logger'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/explain.rb:26:in `logging_query_plan'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/relation.rb:159:in `to_a'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/relation/finder_methods.rb:159:in `all'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/querying.rb:5:in `all'
    /home/git/gitlab/app/services/system_hooks_service.rb:9:in `execute_hooks'
    /home/git/gitlab/app/services/system_hooks_service.rb:3:in `execute_hooks_for'
    /home/git/gitlab/app/observers/system_hook_observer.rb:5:in `after_create'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activemodel-3.2.16/lib/active_model/observing.rb:231:in `update'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/observer.rb:114:in `block (2 levels) in define_callbacks'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.16/lib/active_support/callbacks.rb:492:in `_run__920756296428933787__create__1882536836677963513__callbacks'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.16/lib/active_support/callbacks.rb:405:in `__run_callback'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.16/lib/active_support/callbacks.rb:385:in `_run_create_callbacks'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.16/lib/active_support/callbacks.rb:81:in `run_callbacks'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/callbacks.rb:268:in `create'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/persistence.rb:348:in `create_or_update'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/callbacks.rb:264:in `block in create_or_update'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.16/lib/active_support/callbacks.rb:436:in `_run__920756296428933787__save__1882536836677963513__callbacks'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.16/lib/active_support/callbacks.rb:405:in `__run_callback'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.16/lib/active_support/callbacks.rb:385:in `_run_save_callbacks'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activesupport-3.2.16/lib/active_support/callbacks.rb:81:in `run_callbacks'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/callbacks.rb:264:in `create_or_update'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/persistence.rb:84:in `save'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/validations.rb:50:in `save'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/attribute_methods/dirty.rb:22:in `save'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/transactions.rb:259:in `block (2 levels) in save'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/transactions.rb:313:in `block in with_transaction_returning_status'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/connection_adapters/abstract/database_statements.rb:192:in `transaction'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/transactions.rb:208:in `transaction'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/transactions.rb:311:in `with_transaction_returning_status'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/transactions.rb:259:in `block in save'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/transactions.rb:270:in `rollback_active_record_state!'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/transactions.rb:258:in `save'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:483:in `block in save'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:502:in `block (2 levels) in around_save'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:150:in `block in run_actions'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:170:in `catch_exceptions'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:148:in `run_actions'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:133:in `run_callbacks'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:212:in `run_callbacks'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:63:in `block (2 levels) in perform'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:63:in `catch'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:63:in `block in perform'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:186:in `within_transaction'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/transition_collection.rb:62:in `perform'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:502:in `block in around_save'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:530:in `block in transaction'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/connection_adapters/abstract/database_statements.rb:192:in `transaction'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/transactions.rb:208:in `transaction'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:529:in `transaction'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:501:in `around_save'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/state_machine-1.2.0/lib/state_machine/integrations/active_record.rb:483:in `save'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/persistence.rb:45:in `create'
    (eval):1:in `block (2 levels) in run_file'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:46:in `eval'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:46:in `block (2 levels) in run_file'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:58:in `block in open'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:57:in `open'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:57:in `open'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:36:in `block in run_file'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/connection_adapters/abstract/database_statements.rb:192:in `transaction'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/activerecord-3.2.16/lib/active_record/transactions.rb:208:in `transaction'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:35:in `run_file'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:26:in `block in run'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:25:in `each'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/seed-fu/runner.rb:25:in `run'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/seed-fu.rb:29:in `seed'
    /home/git/gitlab/vendor/bundle/ruby/2.0.0/gems/seed-fu-2.3.0/lib/tasks/seed_fu.rake:36:in `block (2 levels) in <top (required)>'
    /home/git/gitlab/lib/tasks/gitlab/setup.rake:18:in `setup_db'
    /home/git/gitlab/lib/tasks/gitlab/setup.rake:4:in `block (2 levels) in <top (required)>'
    Tasks: TOP => db:seed_fu

Any ideas why this is happening? I'm banging my head trying to figure this ok, I've googled it a million times and haven't seen anything quite like it.

Thank you!

Linked issues
0


  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: dblessing

    I have seen this a couple of times in the past day or 2 when using the dev VM. I got past it somehow but unfortunately I'm not exactly sure how - it may have been just by starting over. Are you working from master?

    By Administrator on 2013-12-11T04:06:03 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: fraywing

    Yes I'm working from master, which sucks.

    Is there at all any possible way you could attempt to conjure up from the recesses of your soul what you did to fix it?

    or do you think you really just started over?

    it's really hard to identify why the command is breaking, I've seen others that are similar but are more obvious. (404s etc)

    By Administrator on 2013-12-11T05:25:26 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: jvanbaarsen

    Can you try to run sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production

    Or does that command also break?

    By Administrator on 2013-12-11T10:13:24 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: fraywing

    Hey there! Here is the output, look good?

    Checking Environment ...
    
    Git configured for git user? ... yes
    Has python2? ... yes
    python2 is supported version? ... yes
    
    Checking Environment ... Finished
    
    Checking GitLab Shell ...
    
    GitLab Shell version >= 1.7.9 ? ... OK (1.7.9)
    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
    update hook up-to-date? ... yes
    update hooks in repos are links: ... can't check, you have no projects
    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
            /usr/bin/redis-cli: OK
    gitlab-shell self-check successful
    
    Checking GitLab Shell ... Finished
    
    Checking Sidekiq ...
    
    Running? ... yes
    Number of Sidekiq processes ... 1
    
    Checking Sidekiq ... Finished
    
    Checking GitLab ...
    
    Database config exists? ... yes
    Database is SQLite ... no
    All migrations up? ... yes
    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: ... can't check, you have no projects
    Projects have satellites? ... can't check, you have no projects
    Redis version >= 2.0.0? ... yes
    Your git bin path is "/usr/local/bin/git"
    Git version >= 1.7.10 ? ... yes (1.8.4)
    
    Checking GitLab ... Finished

    By Administrator on 2013-12-11T16:33:30 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: jvanbaarsen

    pff weird 😞 Looks ok to me..Is there a reason you're working from master?

    By Administrator on 2013-12-11T19:29:55 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: fraywing

    Yeah, 'cause I'm an idiot :-( Its alllll good though, I restarted like @bke-drewb suggested and it's automagically fixed.. D'oh!

    Thanks!

    Also for those in the future who have my issue... here is the link I followed.. it's an alternative tutorial:

    https://gist.github.com/jniltinho/5565590

    By Administrator on 2013-12-11T19:39:32 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: iCodr8

    Thanks to @jvanbaarsen ! I had the same Problem and your command helped me to find out that my gitlab-shell was not correctly installed. sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production

    By Administrator on 2014-06-21T21:58:41 (imported from GitLab project)

  • Administrator
    Administrator @root · 11 years ago
    Owner

    Created by: jvanbaarsen

    @iCodr8 Glad i could been of help :)

    By Administrator on 2014-06-22T09:18:47 (imported from GitLab project)

  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
0 Assignees
Assign to
Milestone
No milestone
None
None
Time tracking
Due date
None
None
0
Labels
None
Assign labels
  • No matching results
  • Manage project labels
Confidentiality
Not confidential

You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

Lock issue
Unlocked
participants
Reference:

Menu

Projects Groups Snippets
Help