RAILS can't load Digest::MD5

[Ben Schumacher]

Hello-

I was trying to setup Rails for the first time following the tutorial
on the rubyonrails.org website and have run into a little snag. I have
my database setup and created my model and views... and I even got rake
to work successfully, but whenever I try to hit the website
(http://rails.benschumacher.com/friends/display), I'm getting this in
my error log:

/usr/local/lib/ruby/site_ruby/1.8/rubygems/loadpath_manager.rb:5:in
`require__': No such file to load -- digest/md5 (LoadError)
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/loadpath_manager.rb:5:in
`require'
from /usr/local/lib/ruby/1.8/pstore.rb:16
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/loadpath_manager.rb:5:in
`require__'
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/loadpath_manager.rb:5:in
`require'
from /usr/local/lib/ruby/1.8/cgi/session/pstore.rb:13
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/loadpath_manager.rb:5:in
`require__'
from
/usr/local/lib/ruby/site_ruby/1.8/rubygems/loadpath_manager.rb:5:in
`require'
from
/usr/local/lib/ruby/gems/1.8/gems/actionpack-0.8.5/lib/
action_controller/cgi_ext/cgi_ext.rb:3
... 11 levels...
from
/usr/home/staff/ben/src/amazonmonitor/public/../config/environments/
production.rb:1:in `require'
from
/usr/home/staff/ben/src/amazonmonitor/public/../config/environments/
production.rb:1
from
/usr/home/staff/ben/src/amazonmonitor/public/dispatch.cgi:3:in
`require'
from /usr/home/staff/ben/src/amazonmonitor/public/dispatch.cgi:3

So it appears that it can't load my Digest::MD5 module, but just to
test it myself, I tried it through irb:

$ irb
irb(main):001:0> require 'digest/md5'
=> true
irb(main):002:0> Digest::MD5.hexdigest('test')
=> "098f6bcd4621d373cade4e832627b4f6"
irb(main):003:0>

Anybody seen behavior like this before? I'm not currently running rails
under FastCGI, just standard CGI, but I don't think this should make a
difference. Any help would be appreciated.

Cheers,

Ben

 

[Ben Schumacher]

Consider this query officially withdrawn. It appears that when I
upgraded to 1.8 (I've had 1.6 installed for a couple years now), I must
have had my umask set in such a way that some of my lib directories
where created at 750... once I chmod'd 'em, everything is happy.