Mongrel won't start ... mongrel_rails (MissingSourceFile)

Hi All,

I’m a newbie and I’m soooo confused at the moment!

Here’s my setup:

  1. I’ve installed Ruby 1.8 on an Ubuntu 7.10 platform. I used apt to
    install that.

  2. I downloaded rubygems_1.1.1 and installed that (tar -xzf, then ruby
    setup.rb)

  3. I installed rails (gem install rails --include-dependencies)

  4. I installed mongrel (gem install mongrel --include-dependencies)

  5. I created a test dir (cd; rails mytest)

  6. I tried to start mongrel (cd mytest; ruby script/server)

I get a load error:

=> Booting Mongrel (use ‘script/server webrick’ to force WEBrick)
=> Rails 2.1.0 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
Exiting
/usr/lib/ruby/gems/1.8/gems/activesupport-2.1.0/lib/active_support/dependencies.rb:502:in
`load’: no such file to load – mongrel_rails (MissingSourceFile)

NOTE: I can start mongrel using /usr/bin/mongrel_rails and I get no
errors.

I put a puts $: statement at the end of config/boot.rb and indeed, the
path to the mongrel gem is missing. What’s up? Where/how do I fix
this?

Thanks in advance.

– David

Problem solved…

I had, at some previous time, loaded mongrel using apt. I uninstalled
it (using apt) but the /usr/local/lib/site_ruby mongrel files were still
there.

The require statement picked up the site_ruby version instead of the
/usr/lib/ruby/gems version. As soon as I renamed the files in
/usr/local/lib/site_ruby, things started working.

– DB

On Thu, 12 Jun 2008 22:37:35 +0200
David B. [email protected] wrote:

=> Booting Mongrel (use ‘script/server webrick’ to force WEBrick)
=> Rails 2.1.0 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server
Exiting
/usr/lib/ruby/gems/1.8/gems/activesupport-2.1.0/lib/active_support/dependencies.rb:502:in
`load’: no such file to load – mongrel_rails (MissingSourceFile)

Hmm, no idea since I don’t use Debian, but did you possibly install it
wrong or maybe install via ruby gems rather than apt-get? I’m not
sure, but if it’s debian they probably mess with the package layout so
you kind of are stuck using their package manager.


Zed A. Shaw