This project is archived and is in readonly mode.
Rails Dependency Problem? Error "Can't activate rails... already activated"
Reported by katmann | August 1st, 2010 @ 06:14 PM
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?
Comments and changes to this ticket
-
Ryan Bigg October 11th, 2010 @ 02:10 AM
- 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? -
-
-
Santiago Pastorino February 2nd, 2011 @ 04:48 PM
- 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.
-
Santiago Pastorino February 2nd, 2011 @ 04:48 PM
- State changed from “open” to “stale”
-
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
<h2 style="font-size: 14px">Tickets have moved to Github</h2>
The new ticket tracker is available at <a href="https://github.com/rails/rails/issues">https://github.com/rails/rails/issues</a>
Jeremy Kemper
katmann
Ryan Bigg