Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

Rails Dependency Problem? Error "Can't activate rails... already activated"

#5266

I am in the process of updating my application from Rails 2.0.2 to 2.3.5. It is working in the new version in my development server but in production, starting the application fails with an error:

Command used to restart application:
$ ./script/process/reaper --action=kill --dispatcher=dispatch.fcgi Resulting Error:
/usr/lib/ruby/site_ruby/1.8/rubygems.rb:233:in activate': can't activate rails (= 2.0.2, runtime) for [], already activated rails-2.3.5 for [] (Gem::LoadError)

    from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:35:in `require'

Any ideas as to what might be causing this or what I should do to troubleshoot?

I have searched my own code and cannot find any dependencies on Rails version 2.0.2. I have also tried disabling all plugins and the error persists. What else can I check to determine what the problem may be?

Reported by katmann · August 1st, 2010 @ 06:14 PM

State: stale
Milestone: none
Assigned to: nobody
Importance: Low

Activity

  1. Ryan Bigg
    Ryan Bigg
    • State changed from new to needs-more-info
    • Importance changed from to Low

    Do you have vendor/rails installed? How about RAILS_GEM_VERSION in config/environment.rb?

    October 11th, 2010 @ 02:10 AM

  2. Ryan Bigg
    Ryan Bigg

    Automatic cleanup of spam.

    October 11th, 2010 @ 02:56 AM

  3. Ryan Bigg
    Ryan Bigg

    Automatic cleanup of spam.

    October 19th, 2010 @ 08:24 AM

  4. Santiago Pastorino
    Santiago Pastorino
    • State changed from needs-more-info to open

    This issue has been automatically marked as stale because it has not been commented on for at least three months.

    The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

    Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

    February 2nd, 2011 @ 04:48 PM

  5. Santiago Pastorino
    Santiago Pastorino
    • State changed from open to stale

    February 2nd, 2011 @ 04:48 PM

  6. bingbing