Uninitialized constant ActiveSupport::Cache (NameError)

Hi

After having updated some GEMS I get `load_missing_constant’:
uninitialized constant ActiveSupport::Cache (NameError) on starting
the server of a freshly generated rails project.

Before, I already had Rails 2.3.2 projects succesfully running, now
all of them generate this error.

These are my GEMS:
actionmailer (2.3.2, 2.2.2, 2.1.2, 2.1.1, 2.1.0)
actionpack (2.3.2, 2.2.2, 2.1.2, 2.1.1, 2.1.0)
activerecord (2.3.2, 2.2.2, 2.1.2, 2.1.1, 2.1.0)
activeresource (2.3.2, 2.2.2, 2.1.2, 2.1.1, 2.1.0)
activesupport (2.3.2, 2.2.2, 2.1.2, 2.1.1, 2.1.0)
bones (2.5.1, 2.5.0, 2.4.2, 2.4.0, 2.3.1, 2.1.1)
capistrano (2.5.5, 2.5.3, 2.5.2, 2.5.0)
cgi_multipart_eof_fix (2.5.0)
columnize (0.3.0, 0.2)
daemons (1.0.10)
fastthread (1.0.1)
fxri (0.3.7)
fxruby (1.6.19, 1.6.18, 1.6.17, 1.6.16)
gem_plugin (0.2.3)
highline (1.5.1, 1.5.0, 1.4.0)
hoe (2.0.0, 1.12.2, 1.11.0, 1.8.3, 1.8.2, 1.8.0)
htmlentities (4.0.0)
linecache (0.43)
log4r (1.0.5)
mini_magick (1.2.5, 1.2.3)
mongrel (1.1.5)
mongrel_cluster (1.0.5)
mongrel_service (0.3.4)
mysql (2.7.3)
needle (1.3.0)
net-scp (1.0.2, 1.0.1)
net-sftp (2.0.2, 2.0.1)
net-ssh (2.0.11, 2.0.9, 2.0.8, 2.0.6, 2.0.4)
net-ssh-gateway (1.0.1, 1.0.0)
newgem (1.4.1, 1.3.0, 1.2.3, 1.2.1, 1.2.0)
ptools (1.1.6)
rails (2.3.2, 2.2.2, 2.1.2, 2.1.1)
rake (0.8.7, 0.8.4, 0.8.3)
rcov (0.8.1.2.0)
RedCloth (4.1.9, 4.1.1)
restfulx (1.2.2, 1.2.1, 1.2.0)
rmagick (2.9.0)
rubigen (1.5.2, 1.4.0)
ruby-debug (0.10.3, 0.10.2)
ruby-debug-base (0.10.3, 0.10.2)
ruby-debug-ide (0.4.6, 0.4.5, 0.4.4, 0.4.3, 0.4.2, 0.3.1)
ruby-prof (0.7.3, 0.7.1, 0.7.0, 0.6.0)
rubyforge (1.0.3, 1.0.2, 1.0.1, 1.0.0)
rubygems-update (1.3.4, 1.3.3, 1.3.1, 1.3.0)
rubyist-aasm (2.0.5, 2.0.4, 2.0.2)
sources (0.0.1)
sqlite3-ruby (1.2.1)
syntax (1.0.0)
test-unit (2.0.2, 2.0.1, 2.0.0)
win32-api (1.4.2, 1.4.0, 1.3.0, 1.2.2, 1.2.1, 1.2.0)
win32-clipboard (0.5.1, 0.4.4)
win32-dir (0.3.4, 0.3.3, 0.3.2)
win32-eventlog (0.5.0)
win32-file (0.6.1, 0.6.0, 0.5.6)
win32-file-stat (1.3.3, 1.3.2)
win32-process (0.6.0, 0.5.9)
win32-sapi (0.1.4)
win32-service (0.6.1)
win32-sound (0.4.1)
windows-api (0.3.0, 0.2.4)
windows-pr (1.0.5, 1.0.2, 0.9.9, 0.9.8, 0.9.7, 0.9.6, 0.9.5, 0.9.4)

I’m on Windows Vista.

Any clue as how to solve this?

Thanks so much!

Wow, you have thousands of versions of the same libraries, why don’t
you start by deleting them?

gem clean

Should do it. Maybe you’re getting a conflict of old gems trying to
access new rails code.

Maurício Linhares
http://codeshooter.wordpress.com/ | http://twitter.com/mauriciojr

Thanks for the suggestion, but I was anxious cleaning all of them as I
use some old projects. But to get rid of all the fuzz I cleaned them.
So no I have:

actionmailer (2.3.2)
actionpack (2.3.2)
activerecord (2.3.2)
activeresource (2.3.2)
activesupport (2.3.2)
bones (2.5.1)
capistrano (2.5.5)
cgi_multipart_eof_fix (2.5.0)
columnize (0.3.0)
daemons (1.0.10)
fastthread (1.0.1)
fxri (0.3.7)
fxruby (1.6.19)
gem_plugin (0.2.3)
highline (1.5.1)
hoe (2.0.0)
htmlentities (4.0.0)
linecache (0.43)
log4r (1.0.5)
mini_magick (1.2.5)
mongrel (1.1.5)
mongrel_cluster (1.0.5)
mongrel_service (0.3.4)
mysql (2.7.3)
needle (1.3.0)
net-scp (1.0.2)
net-sftp (2.0.2)
net-ssh (2.0.11)
net-ssh-gateway (1.0.1)
newgem (1.4.1)
ptools (1.1.6)
rails (2.3.2)
rake (0.8.7)
rcov (0.8.1.2.0)
RedCloth (4.1.9)
restfulx (1.2.2)
rmagick (2.9.0)
rubigen (1.5.2)
ruby-debug (0.10.3)
ruby-debug-base (0.10.3)
ruby-debug-ide (0.4.6)
ruby-prof (0.7.3)
rubyforge (1.0.3)
rubygems-update (1.3.4)
rubyist-aasm (2.0.5)
sources (0.0.1)
sqlite3-ruby (1.2.1)
syntax (1.0.0)
test-unit (2.0.2)
win32-api (1.4.2)
win32-clipboard (0.5.1)
win32-dir (0.3.4)
win32-eventlog (0.5.0)
win32-file (0.6.1)
win32-file-stat (1.3.3)
win32-process (0.6.0)
win32-sapi (0.1.4)
win32-service (0.6.1)
win32-sound (0.4.1)
windows-api (0.3.0)
windows-pr (1.0.5)

But the error still remains.

Jan

On 10 jun, 17:24, Maurício Linhares [email protected]

Show the full backtrace of the error.

Maurício Linhares
http://codeshooter.wordpress.com/ | http://twitter.com/mauriciojr

Solved it!!

I just bluntly uninstalled lots of gems including the Rails
installations. And reinstalled the primary ones. Now it starts!

Thanks for your time!

Here it is:

=> Booting Mongrel
=> Rails 2.3.2 application starting on http://127.0.0.1:3020
E:/inet/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/
active_support/dependencies.rb:440:in load_missing_constant': uninitialized constant ActiveSupport::Cache (NameError) from E:/inet/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/ active_support/dependencies.rb:80:in const_missing’
from E:/inet/ruby/lib/ruby/gems/1.8/gems/rails-2.3.2/lib/
initializer.rb:435:in initialize_cache' from E:/inet/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/ active_support/core_ext/kernel/reporting.rb:11:in silence_warnings’
from E:/inet/ruby/lib/ruby/gems/1.8/gems/rails-2.3.2/lib/
initializer.rb:435:in initialize_cache' from E:/inet/ruby/lib/ruby/gems/1.8/gems/rails-2.3.2/lib/ initializer.rb:143:in process’
from E:/inet/ruby/lib/ruby/gems/1.8/gems/rails-2.3.2/lib/
initializer.rb:113:in send' from E:/inet/ruby/lib/ruby/gems/1.8/gems/rails-2.3.2/lib/ initializer.rb:113:in run’
from E:/Development/Rails/PhotoServer/config/environment.rb:9
from E:/inet/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
31:in gem_original_require' from E:/inet/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: 31:in require’
from E:/inet/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/
active_support/dependencies.rb:156:in require' from E:/inet/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/ active_support/dependencies.rb:521:in new_constants_in’
from E:/inet/ruby/lib/ruby/gems/1.8/gems/activesupport-2.3.2/lib/
active_support/dependencies.rb:156:in require' from E:/inet/ruby/lib/ruby/gems/1.8/gems/rails-2.3.2/lib/commands/ server.rb:84 from E:/inet/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb: 31:in gem_original_require’
from E:/inet/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:
31:in require' from ./script/server:3 from -e:2:in load’
from -e:2

Thanks

On 10 jun, 17:38, Maurício Linhares [email protected]