RubyGems error after updating system - ruby-on-rails
When trying to launch the rails console after updating my ruby setup using 'sudo gem update --system', I then try execute the rails console by issuing rails c
I get this error:
Users/myusername/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in `to_specs': Could not find json (~> 1.4) amongst [Ascii85-1.0.1, abstract-1.0.0, actionmailer-3.1.1, actionmailer-3.1.0, actionmailer-3.0.9, actionmailer-3.0.5, actionmailer-3.0.3, actionpack-3.1.1, actionpack-3.1.0, actionpack-3.0.9, actionpack-3.0.5, actionpack-3.0.3, activemodel-3.1.1, activemodel-3.1.0, activemodel-3.0.10, activemodel-3.0.9, activemodel-3.0.5, activemodel-3.0.3, activerecord-3.1.1, activerecord-3.1.0, activerecord-3.0.9, activerecord-3.0.5, activerecord-3.0.3, activeresource-3.1.1, activeresource-3.1.0, activeresource-3.0.9, activeresource-3.0.5, activeresource-3.0.3, activesupport-3.1.1, activesupport-3.1.0, activesupport-3.0.10, activesupport-3.0.9, activesupport-3.0.5, activesupport-3.0.3, addressable-2.2.6, ansi-1.3.0, arel-2.2.1, arel-2.0.10, arel-2.0.9, arel-2.0.7, bcrypt-ruby-3.0.1, bcrypt-ruby-3.0.0, bcrypt-ruby-2.1.4, builder-3.0.0, builder-2.1.2, bundler-1.0.21, bundler-1.0.18, bundler-1.0.11, choices-0.2.4, cocaine-0.2.0, coffee-rails-3.1.1, coffee-rails-3.1.0, coffee-script-2.2.0, coffee-script-source-1.1.2, devise-1.4.8, devise-1.4.2, erubis-2.7.0, erubis-2.6.6, execjs-1.2.9, execjs-1.2.6, execjs-1.2.4, faraday-0.7.4, faraday-0.6.1, faraday_middleware-0.7.0, faraday_middleware-0.6.3, fastercsv-1.5.4, formtastic-2.0.2, formtastic-1.2.4, geocoder-1.0.4, geocoder-1.0.2, has_scope-0.5.1, hashie-1.1.0, hashie-1.0.0, heroku-2.7.0, hike-1.2.1, i18n-0.6.0, i18n-0.5.0, inherited_resources-1.3.0, inherited_resources-1.2.2, jquery-rails-1.0.16, jquery-rails-1.0.14, kaminari-0.12.4, launchy-2.0.5, libv8-3.3.10.2-x86_64-darwin-10, mail-2.3.0, mail-2.2.19, mail-2.2.15, mail-2.2.14, mechanize-2.0.1, mechanize-1.0.0, meta_search-1.1.1, meta_search-1.0.6, mime-types-1.16, multi_json-1.0.3, multi_xml-0.4.1, multi_xml-0.4.0, multi_xml-0.3.0, multi_xml-0.2.2, multipart-post-1.1.3, multipart-post-1.1.2, mysql-2.8.1, mysql2-0.3.7, mysql2-0.2.7, mysql2-0.2.6, net-http-digest_auth-1.1.1, net-http-persistent-2.1, net-http-persistent-2.0, net-http-persistent-1.9, nokogiri-1.5.0, nokogiri-1.4.4, orm_adapter-0.0.5, pdf-reader-0.10.0, pg-0.11.0, polyamorous-0.5.0, polyglot-0.3.2, polyglot-0.3.1, prawn-0.12.0, rack-1.3.4, rack-1.3.3, rack-1.3.2, rack-1.2.3, rack-1.2.2, rack-1.2.1, rack-cache-1.1, rack-cache-1.0.3, rack-mount-0.8.3, rack-mount-0.6.14, rack-mount-0.6.13, rack-ssl-1.3.2, rack-test-0.6.1, rack-test-0.5.7, rails-3.1.1, rails-3.1.0, rails-3.0.9, rails-3.0.5, rails-3.0.3, railties-3.1.1, railties-3.1.0, railties-3.0.9, railties-3.0.5, railties-3.0.3, rake-0.9.2, rake-0.8.7, rake-0.8.7, rash-0.3.1, rash-0.3.0, rdoc-3.10, rdoc-3.9.4, rdoc-3.9.2, responders-0.6.4, rest-client-1.6.7, rubygems-update-1.8.11, rubygems-update-1.8.10, rubygems-update-1.7.2, rubygems-update-1.7.1, rubygems-update-1.6.2, rubyzip-0.9.4, sass-3.1.10, sass-3.1.7, sass-rails-3.1.4, sass-rails-3.1.2, sass-rails-3.1.0, simple_oauth-0.1.5, sprockets-2.0.2, sprockets-2.0.0, sqlite3-1.3.4, term-ansicolor-1.0.6, therubyracer-0.9.4, thor-0.14.6, tilt-1.3.3, treetop-1.4.10, treetop-1.4.9, ttfunk-1.0.3, ttfunk-1.0.2, turn-0.8.2, twitter-1.7.1, twitter-1.4.1, tzinfo-0.3.30, tzinfo-0.3.29, tzinfo-0.3.26, tzinfo-0.3.24, uglifier-1.0.3, warden-1.0.6, warden-1.0.5, webrobots-0.0.12, webrobots-0.0.11] (Gem::LoadError)
from /Users/myusername/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:1932:in `block in traverse'
from /Users/myusername/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:1931:in `each'
from /Users/myusername/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:1931:in `traverse'
from /Users/myusername/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:465:in `block in find_in_unresolved_tree'
from /Users/myusername/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:463:in `reverse_each'
from /Users/myusername/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/specification.rb:463:in `find_in_unresolved_tree'
from /Users/myusername/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:47:in `require'
from /Users/myusername/.rvm/gems/ruby-1.9.2-p136/gems/railties-3.1.1/lib/rails/script_rails_loader.rb:1:in `<top (required)>'
from /Users/myusername/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require'
from /Users/myusername/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require'
from /Users/myusername/.rvm/gems/ruby-1.9.2-p136/gems/railties-3.1.1/lib/rails/cli.rb:2:in `<top (required)>'
from /Users/myusername/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require'
from /Users/myusername/.rvm/rubies/ruby-1.9.2-p136/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require'
from /Users/myusername/.rvm/gems/ruby-1.9.2-p136/gems/rails-3.1.1/bin/rails:7:in `<top (required)>'
from /Users/myusername/.rvm/gems/ruby-1.9.2-p136/bin/rails:19:in `load'
from /Users/myusername/.rvm/gems/ruby-1.9.2-p136/bin/rails:19:in `<main>'
Any ideas?
what do you get when you try to list your gems.. is json >= 1.4 there?
e.g.:
> gem list json
*** LOCAL GEMS ***
json (1.6.1, 1.5.4, 1.5.3, 1.5.1, 1.4.2)
json_pure (1.6.1, 1.5.4, 1.5.3)
if you use RVM gemsets, you may want to list them also, to check if your default gemset has changed:
rvm gemset list
EDIT: Mystery Solved! :-)
you accidentially installed your gems with sudo -- but you have RVM installed for your user account!
When you have RVM installed for an individual user, it's generally not a good idea to do sudo gem install ... , but you should install the gems just for the local user and let RVM manage them for whatever Ruby version you are using.
If you still install with sudo, RVM will not find the gems, because they are stored in a different location, outside of RVM, and not searched by RVM...! Looks like that's the case you experienced.
Check this RailsCast: http://railscasts.com/episodes/200-rails-3-beta-and-rvm
if you're using Rails:
- edit your Gemfile and add the json dependency , then run bundle install
if you're just using Ruby by itself, or an old version or Ruby:
- run gem install json in the shell
With newer Ruby versions you should not manually install the gems
Add gem "json", "~> 1.4" in your Gemfile and run bundle install
Also
You only use the sudo command during the install process. In Multi-User configurations, any operations which require sudo access must use the rvmsudo command which preserves the RVM environment and passes this on to sudo. There are very few cases where rvmsudo is required once the core install is completed, except for when updating RVM itself. There is never a reason to use sudo post-install. Once users added to the 'rvm' group have logged out, then back in to gain rvm group membership, rvmsudo should only be needed for updating RVM itself with
rvmsudo rvm get head
Please read the https://rvm.beginrescueend.com/support/troubleshooting/ page The installer page also details this for new installations. You will need to remove your existing installation and redo it in order to properly reconfigure the permissions. In the future, never user sudo when working on your RVM installation, except when installing. Any other commands will not require sudo use except for
rvmsudo rvm get head
to update your installation. If the users are properly placed in the rvm group as detailed on the site, you will have no need to use sudo at all, and rvmsudo only for updating.
Also, RVM does not manage the system installed ruby at all! We do provide the use of
rvm use system
in order to give a natural way to switch between RVM controlled rubies, and the system. Your package manager, or lack thereof for OS X, is responsible for managing your system installed ruby and is outside the control of RVM 100%.
Related
Running local server for Rails 2.3 app?
I am trying to run a Rails 2.3 app locally. script/server gives me these errors: bash: script/server: Permission denied bash: parse_git_branch: command not found script/server gives me the error: /Users/stevenbrooks1111/.rvm/rubies/ruby-1.9.3-p429/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require': cannot load such file -- initializer (LoadError) from /Users/stevenbrooks1111/.rvm/rubies/ruby-1.9.3-p429/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require' from /Users/stevenbrooks1111/Desktop/cssmixonline/cssweb/config/boot.rb:55:in `load_initializer' from /Users/stevenbrooks1111/Desktop/cssmixonline/cssweb/config/boot.rb:38:in `run' from /Users/stevenbrooks1111/Desktop/cssmixonline/cssweb/config/boot.rb:11:in `boot!' from /Users/stevenbrooks1111/Desktop/cssmixonline/cssweb/config/boot.rb:110:in `<top (required)>' from /Users/stevenbrooks1111/.rvm/rubies/ruby-1.9.3-p429/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from /Users/stevenbrooks1111/.rvm/rubies/ruby-1.9.3-p429/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:36:in `require' from script/server:2:in `<main>' bash: parse_git_branch: command not found Any ideas of how I can get this to run locally?
This question is what I've been doing for the past month. I would have loved to use Rails 4, but I know better than to try it! Install rvm or rbenv, then get into a server that correctly runs this app, and run ruby --version gem list > ~/myGems.txt Using rvm or rbenv, install the exact same version of Ruby. (Tip: whenever I say "exact same", you can fudge by bumping the revision. For example, given a gem with version 0.1.4, if it has subsequent versions 0.1.5, 0.1.6, and 0.2.0, you can bump to 0.1.6, if that will save you some grief. The revision numbers, 0.1.*, are supposed to be only bug fixes. But a minor version bump, 0.2.0, has higher odds of breaking things. I kept the same version of Ruby, but I bumped rails to 2.3.14.) Using rvm or rbenv, install the same version of Ruby as currently runs on this app's main server. Inside this Ruby environment (with both which ruby and ruby --version reporting the correct answers), install each gem in myGems.txt, like this: gem install --ignore-dependencies --no-rdoc --no-ri my_gem -v=0.1.4 The --ignore-dependencies is critical, because some gems from the Pleistocene Epoch, 2009, don't specify their dependencies' versions. When some dumb 2009 gem pulls in the 2013 rake, you will be utterly screwed, because reverting that rake is really hard. And don't forget to set the -v to the same value as myGems.txt reports! After all that, try simple rake commands like rake routes. Post any bugs you get as fresh questions, but remember to point out Rails 2.3 in the subject so nobody mis-answers with the modern fixes. And if this app has tests or specs, getting them running should be a top priority, so you can resume TDD, leaning on the tests to allow you to make sick changes.
everything working except rails. rails -v returns a long message. Gem::LoadError + other stuff
I'm so frustrated. I just wiped my computer clean for a new start, after trying for several days to get rails installed. I followed this tutorial http://www.moncefbelyamani.com/how-to-install-xcode-homebrew-git-rvm-ruby-on-mac/#step-4 It actually worked too, but when I woke up the next morning, I got this new "error" Everything seemed to be working. I installed xcode, homebrew first, and then installed RVM. and it all seems to be working. I have ruby 2.0.0, but when I type "rails -v" after installing I get the following: $ rails -v /Users/johncurry/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/dependency.rb:247:in `to_specs': Could not find minitest (~> 4.2) amongst [actionmailer-4.0.0, actionmailer-3.2.13, actionpack-4.0.0, actionpack-3.2.13, activemodel-4.0.0, activemodel-3.2.13, activerecord-4.0.0, activerecord-3.2.13, activerecord-deprecated_finders-1.0.3, activeresource-3.2.13, activesupport-4.0.0, activesupport-3.2.13, arel-4.0.0, arel-3.0.2, atomic-1.1.10, builder-3.1.4, builder-3.0.4, bundler-1.3.5, bundler-unload-1.0.1, erubis-2.7.0, hike-1.2.3, i18n-0.6.4, i18n-0.6.1, journey-1.0.4, json-1.8.0, mail-2.5.4, mime-types-1.23, multi_json-1.7.7, polyglot-0.3.3, rack-1.5.2, rack-1.4.5, rack-cache-1.2, rack-ssl-1.3.3, rack-test-0.6.2, rails-4.0.0, rails-3.2.13, railties-4.0.0, railties-3.2.13, rake-10.1.0, rdoc-3.12.2, rubygems-bundler-1.2.0, rubygems-update-1.8.24, rvm-1.11.3.8, sprockets-2.10.0, sprockets-2.2.2, sprockets-rails-2.0.0, thor-0.18.1, thread_safe-0.1.0, tilt-1.4.1, treetop-1.4.14, tzinfo-0.3.37] (Gem::LoadError) from /Users/johncurry/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:777:in `block in activate_dependencies' from /Users/johncurry/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:766:in `each' from /Users/johncurry/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:766:in `activate_dependencies' from /Users/johncurry/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:750:in `activate' from /Users/johncurry/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:780:in `block in activate_dependencies' from /Users/johncurry/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:766:in `each' from /Users/johncurry/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:766:in `activate_dependencies' from /Users/johncurry/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems/specification.rb:750:in `activate' from /Users/johncurry/.rvm/rubies/ruby-2.0.0-p247/lib/ruby/site_ruby/2.0.0/rubygems.rb:1232:in `gem' from /Users/johncurry/.rvm/gems/ruby-2.0.0-p247/bin/rails:18:in `<main>' from /Users/johncurry/.rvm/gems/ruby-2.0.0-p247/bin/ruby_noexec_wrapper:14:in `eval' from /Users/johncurry/.rvm/gems/ruby-2.0.0-p247/bin/ruby_noexec_wrapper:14:in `<main>' Please help. I've been trying for three days and even completely reset my computer. and I am so close. What do I need to do?
Ok, step back and take a deep breath. The tutorial kind of does a disservice because it doesn't show you the individual steps for RVM rubies, gems and gemsets, but rather does it in a single command. First, check which ruby(s) you have installed with this command rvm list this will print out what you have installed, like this ruby-1.9.3-p385 [ x86_64 ] ruby-1.9.3-p392 [ x86_64 ] =* ruby-2.0.0-p0 [ x86_64 ] # => - current # =* - current && default # * - default now it looks like you have 2.0.0, lets make it the default ruby rvm use 2.0.0 --default now lets create a gemset called rails-3.2.13, this is where we will install the rails gem rvm gemset create rails-3.2.13 lets make this gemset the currently used and default gemset rvm gemset use rails-3.2.13 --default time to install rails gem install rails -v 3.2.13 Now when you type rails -v it should show this version of rails. Also, because we set the default to ruby 2.0.0 and the gemset to rails-3.2.13, each time you open a new terminal it will be same ruby and rails version. Take a look at the RVM website and docs for the other thousand things rvm can do. Good luck
no such file to load -- initializer (LoadError)
I have following installed on ubuntu 12 ruby 1.9.2p320 Rails 3.2.6 Now I have old project which is developed into Rails 2 & Ruby 1.8.7 Problem: When i run below command under old project root directory ruby ./script/plugin install git://github.com/rails/rails_upgrade.git Following error comes Invalid gemspec in [/usr/local/rvm/gems/ruby-1.9.2-p320/specifications/ZenTest-4.9.1.gemspec]: Illformed requirement ["< 2.1, >= 1.8"] /usr/local/rvm/rubies/ruby-1.9.2-p320/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require': no such file to load -- initializer (LoadError) from /usr/local/rvm/rubies/ruby-1.9.2-p320/lib/ruby/site_ruby/1.9.1/rubygems/custom_require.rb:55:in `require' from /var/www/project/client/softwallet/config/boot.rb:54:in `load_initializer' from /var/www/project/client/softwallet/config/boot.rb:38:in `run' from /var/www/project/client/softwallet/config/boot.rb:11:in `boot!' from /var/www/project/client/softwallet/config/boot.rb:109:in `<top (required)>' from <internal:lib/rubygems/custom_require>:29:in `require' from <internal:lib/rubygems/custom_require>:29:in `require' from ./script/plugin:2:in `<main>'
Upgrading the old rails project to new one and getting the invalid gemspec problem. Then you have to do the following: Run gem update --system followed by bundle install. UPDATE: You are using the same old config/boot.rb from your older version of rails application. Do the following: 1) Create a new project directory. 2) Generate a new rails app (Of your new latest rails version) 3) Use boot.rb that is created by it.
This happens when you have incompatible version of the same gem already installed on your environment. To rectify, either you can uninstall and reinstall the gem or install the gem of the specific version. Make sure that you do a gem cleanup operation before doing so.
This is how my problem was solved . I was using RVM and if you have edited those .bashrc files then each time while you log in to the shell , do a /bin/bash --login . What this does is , it makes the command line take note of the rvm path you had set and installs them first . I did this on Ubuntu 12 and it did solve my issue , i don't think doing gem update --system is a good idea as it really kind of messes up the environment forcing one to do an rvm implode and install it all over again .
error sqlite3 requires Ruby version >= 1.9.1
I've used sqlite before. My friend sent me a skeleton rails app that I am trying to run. When I try to do "rails server" or "thin start" it says Could not find sqlite3-0.1.1 in any of the sources" I tried to do bundle install but it throws this error: Installing sqlite3 (0.1.1) /Library/Ruby/Site/1.8/rubygems/installer.rb:364:in ensure_required_ruby_version_met': sqlite3 requires Ruby version >= 1.9.1. (Gem::InstallError) from /Library/Ruby/Site/1.8/rubygems/installer.rb:135:ininstall' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/source.rb:96:in install' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/installer.rb:55:inrun' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/spec_set.rb:12:in each' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/spec_set.rb:12:ineach' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/installer.rb:44:in run' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/installer.rb:8:ininstall' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/cli.rb:225:in install' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/vendor/thor/task.rb:22:insend' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/vendor/thor/task.rb:22:in run' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/vendor/thor/invocation.rb:118:ininvoke_task' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/vendor/thor.rb:246:in dispatch' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/lib/bundler/vendor/thor/base.rb:389:instart' from /Library/Ruby/Gems/1.8/gems/bundler-1.0.12/bin/bundle:13 from /usr/bin/bundle:19:in `load' from /usr/bin/bundle:19 I don't know why it's trying to look in the 1.8 folder with Ruby 1.9.2 installed. What am I doing wrong?
Your bundle command is pointing to your system Ruby, type the following to see which Ruby your Bundler is pointed to: head -1 $(which bundle) Either that needs to be pointed at the Ruby you want to use and/or you need to use the Ruby you want to use to install the Bundler gem (which will put the right shebang line in your bundle executable).
How to get mongrel working with bundler?
Transitioning to bundler with an existing production setup. Naively with a gemfile and setup like: gem "rails", "2.3.8" gem "mongrel", git: "http://github.com/dynamix/mongrel.git" bundle install --path /mnt/app/shared/bundle Starting with bundle exec mongrel_rails start --environment=production ... results in /mnt/app/shared/bundle/ruby/1.9.1/gems/activesupport-2.3.8/lib/active_support/dependencies.rb:166:in `require': no such file to load -- /mnt/services/shared/bundle/ruby/1.9.1/gems/mongrel-1.2.0.beta.1/lib/mongrel/init.rb (MissingSourceFile) What to do?
To answer my own, since I couldn't find a correct solution elsewhere on the web for this scenario: The problem seems to be an interaction of bundler and mongrel's use of the gem_plugin. Yes, these may be on life support but unfortunately lots of people's production configs still depend on them. Seems that with mongrel --pre installed from the git source, it's looking in bundle/ruby/1.9.1/gems/mongrel_ instead of bundle/ruby/1.9.1/bundler/gems/mongrel_ which is where bundler is stashing the gem cloned from git. So the solution that worked for our config is to just symlink them: ln -s /mnt/app/shared/bundle/ruby/1.9.1/bundle/gems/mongrel* \ /mnt/app/shared/bundle/ruby/1.9.1/gems/mongrel-1.2.0.beta.1 This is clearly something simple that bundler could do automatically. Full trace of the exception was: /mnt/app/shared/bundle/ruby/1.9.1/gems/activesupport-2.3.8/lib/active_support/dependencies.rb:166:in `require': no such file to load -- /mnt/app/shared/bundle/ruby/1.9.1/gems/mongrel-1.2.0.beta.1/lib/mongrel/init.rb (MissingSourceFile) from /mnt/app/shared/bundle/ruby/1.9.1/gems/activesupport-2.3.8/lib/active_support/dependencies.rb:166:in `require' from /mnt/app/shared/bundle/ruby/1.9.1/gems/gem_plugin-0.2.3/lib/gem_plugin.rb:134:in `block in load' from /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/source_index.rb:241:in `each' from /usr/local/lib/ruby/site_ruby/1.9.1/rubygems/source_index.rb:241:in `each' from /mnt/services/shared/bundle/ruby/1.9.1/gems/gem_plugin-0.2.3/lib/gem_plugin.rb:112:in `load' from /mnt/app/shared/bundle/ruby/1.9.1/bundler/gems/mongrel-f3e69eb8e6fb/lib/mongrel/configurator.rb:231:in `load_plugins'