Require rubygems fails

All of a sudden one of my applications at Dreamhost has stopped working
Support there says they don't support "3rd party applications".

I suspect they've done some upgrade and its zapped things but they're
not handing out details.
This is the error I get.
Suggestions as the the most straight-forward way to address it?
Remember, I'm at a hosted site so I don't have control over /usr/bin or
/usr/lib/ruby

$ ./dispatch.fcgi
./../config/boot.rb:18:in `require': no such file to load -- rubygems
(LoadError)
  from ./../config/boot.rb:18
  from ./../config/environment.rb:8
  from ./dispatch.fcgi:21

Thanks

Check if you can require rubygems 'normally'
irb
require 'rubygems'

if that doesn't work then support should hear about it.
If it does, then you may need to try to setup your rails app from
scratch again (check for any directory settings, etc.).
Gl.
-roger

Anton Aylward wrote:

Anton Aylward wrote:

--
Echelon appears to work very much like a Web search engine, except that
instead of searching Web pages it searches through the world's phone and
data network traffic in real time.
  -- Ross Anderson, _Security Engineering_

In addition to Roger's suggestion, once you get it working, running:
"rake rails:freeze:gems"
should more properly safeguard you against server changes in the future

hth

ilan

Ilan Berci said the following on 15/02/08 02:10 PM:

In addition to Roger's suggestion, once you get it working, running:
"rake rails:freeze:gems"
should more properly safeguard you against server changes in the future

$ rake rails:freeze:gems
/home/antonaylward/bin/rake:9:in `require': no such file to load --
rubygems (LoadError)
        from /home/antonaylward/bin/rake:9

Hmm.
Reset PATH.
Got

/home/.jordana/antonaylward/typo/config/boot.rb:38:Warning: require_gem
is obsolete. Use gem instead.

Fixed that.
But I Still get

[ralphie]$ rake rails:freeze:gems
/usr/bin/rake:17:Warning: require_gem is obsolete. Use gem instead.

Does this mean that the system 'rake' is out of date?

The freeze seemed to settle on Rails-2.02
I don't think Typo likes that!

How would I freeze the gems to an earlier version?

After unfreezing the above I listed the gems to see which version of
rails there were. Only 2.02 and 1.2.6, so I tried

[ralphie]$ rake rails:freeze:edge TAG=rel_1.2.6

which now results in

./public/../config/boot.rb:16:in `require': no such file to load --
public/../config/../vendor/rails/railties/lib/initializer (LoadError)
        from ./public/../config/boot.rb:16
        from ./public/../config/environment.rb:8:in `require'
        from ./public/../config/environment.rb:8
        from ./public/dispatch.fcgi:21:in `require'
        from ./public/dispatch.fcgi:21

well,if you use the rvm to manage the ruby version,

you should modify them "dispatch.fcgi" "dispatch.cgi" "dispatch.rb"

change "#!/usr/bin/ruby" to "#!/usr/bin/env ruby"

I posted that message about 4.5 years ago.. way before rvm was even
around.

star star wrote in post #1068786: