Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums
  • Feature tour
    Feature tour

Content

You are here:
  1. Forums
  2. Support Installation & Updates

Failure running openproject-ce configure after upgrading from 4.2.6 to 4.2.7: Application.initialize!... rake aborted! ArgumentError: wrong number of arguments (0 for 1..2)

Added by John Digilio about 9 years ago

On RHEL 6 just tried to upgrade from 4.2.6 (which was working) to 4.2.7. Ran yum update and all went well, ran yum install openproject-ce and was told 4.2.7 was already installed. Running openproject-ce configure generates the error below. Any assistance would be appreciated. Thanks - John

Application.initialize!… rake aborted!
ArgumentError: wrong number of arguments (0 for 1..2)
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/activesupport-3.2.22/lib/active_support/cache/file_store.rb:19:in `initialize’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/activesupport-3.2.22/lib/active_support/cache.rb:69:in `new’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/activesupport-3.2.22/lib/active_support/cache.rb:69:in `lookup_store’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/railties-3.2.22/lib/rails/application/bootstrap.rb:54:in `block (2 levels) in module:Bootstrap’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/activesupport-3.2.22/lib/active_support/core_ext/kernel/reporting.rb:13:in `block in silence_warnings’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/activesupport-3.2.22/lib/active_support/core_ext/kernel/reporting.rb:24:in `with_warnings’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/activesupport-3.2.22/lib/active_support/core_ext/kernel/reporting.rb:13:in `silence_warnings’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/railties-3.2.22/lib/rails/application/bootstrap.rb:54:in `block in module:Bootstrap’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/railties-3.2.22/lib/rails/initializable.rb:30:in `instance_exec’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/railties-3.2.22/lib/rails/initializable.rb:30:in `run’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/railties-3.2.22/lib/rails/initializable.rb:55:in `block in run_initializers’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/railties-3.2.22/lib/rails/initializable.rb:54:in `each’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/railties-3.2.22/lib/rails/initializable.rb:54:in `run_initializers’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/railties-3.2.22/lib/rails/application.rb:136:in `initialize!’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/railties-3.2.22/lib/rails/railtie/configurable.rb:30:in `method_missing’
/opt/openproject-ce/config/environment.rb:35:in `block in <top (required)>’
/opt/openproject-ce/config/application.rb:43:in `block in bench’
/opt/openproject-ce/config/application.rb:42:in `bench’
/opt/openproject-ce/config/environment.rb:33:in `<top (required)>’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/activesupport-3.2.22/lib/active_support/dependencies.rb:251:in `require’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/activesupport-3.2.22/lib/active_support/dependencies.rb:251:in `block in require’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/activesupport-3.2.22/lib/active_support/dependencies.rb:236:in `load_dependency’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/activesupport-3.2.22/lib/active_support/dependencies.rb:251:in `require’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/railties-3.2.22/lib/rails/application.rb:103:in `require_environment!’
/opt/openproject-ce/vendor/bundle/ruby/2.1.0/gems/railties-3.2.22/lib/rails/application.rb:305:in `block (2 levels) in initialize_tasks’
Tasks: TOP => setting:set => environment
(See full trace by running task with —trace)


Replies (5)

RE: Failure running openproject-ce configure after upgrading from 4.2.6 to 4.2.7: Application.initialize!... rake aborted! ArgumentError: wrong number of arguments (0 for 1..2) - Added by Christian Ther about 9 years ago

I get the same error on Ubuntu 14.04.3 after the update to 4.2.7.
Regards Christian

RE: Failure running openproject-ce configure after upgrading from 4.2.6 to 4.2.7: Application.initialize!... rake aborted! ArgumentError: wrong number of arguments (0 for 1..2) - Added by Jonas Heinrich (Finn) about 9 years ago

Hi John,

there recently have been changes to the cache configuration. I’m gonna have a look at it now.

Best,

Jonas

RE: Failure running openproject-ce configure after upgrading from 4.2.6 to 4.2.7: Application.initialize!... rake aborted! ArgumentError: wrong number of arguments (0 for 1..2) - Added by Jonas Heinrich (Finn) about 9 years ago

This is the pr that should fix this problem: https://github.com/opf/openproject/pull/3571. I think we will release 4.2.8 this week (probably thursday) which will contain this fix.
As a workaround until then you could add this to your files manually. Do you need assistence on how to do that?

Best,

Jonas

RE: Failure running openproject-ce configure after upgrading from 4.2.6 to 4.2.7: Application.initialize!... rake aborted! ArgumentError: wrong number of arguments (0 for 1..2) - Added by Christian Ther about 9 years ago

Hello Jonas,
your workaround works for me! I adapted the file configuration.rb and rerun openproject-ce configure - the process ends successfully. After that OP starts without any error!
Thank you for your fast support.
Best regards
Christian

RE: Failure running openproject-ce configure after upgrading from 4.2.6 to 4.2.7: Application.initialize!... rake aborted! ArgumentError: wrong number of arguments (0 for 1..2) - Added by John Digilio about 9 years ago

Jonas,
The fix you provided worked for me as well. Thanks
-John

  • (1 - 5/5)
Loading...