Can't run rails server after accidentally running $ gem update --system

Question

I ran gem update --system thinking it would solve a problem I was having, and now I can't run rails server. It won't load and instead, I keep getting the following. Can someone tell me how to undo this and revert back to before I ran the update?

I've already ran git checkout, but the problem persists...

/usr/local/rvm/gems/ruby-1.9.3-p194@global/gems/bundler-1.1.5/lib/bundler/rubygems_integration.rb:187:in `stub_source_index170': uninitialized constant Gem::SourceIndex (NameError)
from /usr/local/rvm/gems/ruby-1.9.3-p194@global/gems/bundler-1.1.5/lib/bundler/rubygems_integration.rb:353:in `stub_rubygems'
from /usr/local/rvm/gems/ruby-1.9.3-p194@global/gems/bundler-1.1.5/lib/bundler/rubygems_integration.rb:250:in `replace_entrypoints'
from /usr/local/rvm/gems/ruby-1.9.3-p194@global/gems/bundler-1.1.5/lib/bundler/runtime.rb:14:in `setup'
from /usr/local/rvm/gems/ruby-1.9.3-p194@global/gems/bundler-1.1.5/lib/bundler.rb:107:in `setup'
from /usr/local/rvm/gems/ruby-1.9.3-p194@global/gems/rubygems-bundler-1.0.7/lib/rubygems-bundler/noexec.rb:66:in `setup'
from /usr/local/rvm/gems/ruby-1.9.3-p194@global/gems/rubygems-bundler-1.0.7/lib/rubygems-bundler/noexec.rb:78:in `<top (required)>'
from /usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:110:in `require'
from /usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:110:in `rescue in require'
from /usr/local/rvm/rubies/ruby-1.9.3-p194/lib/ruby/site_ruby/1.9.1/rubygems/core_ext/kernel_require.rb:35:in `require'
from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:9:in `<main>'

Do you need to upgrade bundler? – Peter Brown Feb 26 '13 at 00:30 — Peter Brown, Feb 26 '13 at 00:30

score 38 · Answer 1 · answered Mar 06 '13 at 13:49

38

I had the same issue today. Updating bundler to the latest version fixed the problem:

gem update bundler

And if you are running rbenv

rbenv rehash

answered Mar 06 '13 at 13:49

bbonamin

30,042
7
40
49

This worked for me after seeing a similar error when trying to coax RubyMine to debug a ruby script (error like: stub_source_index170': uninitialized constant Gem::SourceIndex (NameError)). Just gem update bundler fixed it. – Mason May 09 '13 at 02:43

score 15 · Accepted Answer · edited Feb 26 '13 at 13:37

15

Seems like the latest version of Rubygems is buggy.

You just have to revert back to an older version with the following command and everything should work fine :

gem update --system 1.8.24

edited Feb 26 '13 at 13:37

sevenseacat

24,699
6
63
88

answered Feb 26 '13 at 13:36

Daniel Ristic

710
6
16

2

Rather than downgrading rubygems, i think it's a better idea to update bundler per the other answer :) – Chris Jun 01 '13 at 00:48
2

I agree, that's why I up-voted the other answer! Should I edit mine as well? – Daniel Ristic Jun 03 '13 at 10:08
@DanielRistic, Doesn't matter. I tried bruno's first but didn't work out in my case. Yours worked like a charm. Upvoting both the answers and the question. – Shankar Narayana Damodaran Jun 04 '15 at 16:47

Can't run rails server after accidentally running $ gem update --system

2 Answers2

Linked