Published on: September 30, 2014 by Arnold Pablo
Scenario:
While running bundle install, the ruby fails.
# bundle install
Fetching gem metadata from http://rubygems.org/.Unfortunately, a fatal error has occurred. Please see the Bundler
troubleshooting documentation at http://bit.ly/bundler-issues. Thanks!
/usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/fetcher.rb:174:in `load’: marshal data too short (ArgumentError)
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/fetcher.rb:174:in `fetch_dependency_remote_specs’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/fetcher.rb:132:in `fetch_remote_specs’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/fetcher.rb:70:in `specs’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/source.rb:234:in `block in remote_specs’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/source.rb:232:in `each’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/source.rb:232:in `remote_specs’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/source.rb:165:in `fetch_specs’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/source.rb:70:in `specs’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/lazy_specification.rb:53:in `__materialize__’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/spec_set.rb:86:in `block in materialize’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/spec_set.rb:83:in `map!’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/spec_set.rb:83:in `materialize’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/definition.rb:127:in `specs’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/definition.rb:122:in `resolve_remotely!’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/installer.rb:48:in `run’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/installer.rb:12:in `install’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/cli.rb:220:in `install’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/vendor/thor/task.rb:22:in `run’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/vendor/thor/invocation.rb:118:in `invoke_task’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/vendor/thor.rb:263:in `dispatch’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/lib/bundler/vendor/thor/base.rb:386:in `start’
from /usr/local/rvm/gems/ruby-1.9.3-p194/gems/bundler-1.1.5/bin/bundle:13:in `<top (required)>’
from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/bundle:19:in `load’
from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/bundle:19:in `<main>’
from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:in `eval’
from /usr/local/rvm/gems/ruby-1.9.3-p194/bin/ruby_noexec_wrapper:14:in `<main>’
Solution
This is because the user’s spec files was corrupted. All I had to do was to remove the .gem folder found in the home directory of the user and run the bundle install again.
Category : Howtos, Linux, Troubleshooting
Technology always fascinated me and continues to do so. I started my career back in 2004 as a Junior System Admin and worked in various capacities both in technical and managerial roles. I love to experiment and try out new OSS projects and in free time, go for cycling to the interiors of God's own country, Kerala!
Add new commentSIGN IN