From: Ryan Davis Date: 2011-03-25T07:42:21+09:00 Subject: Re: Ruby corrupts after a period of time On Mar 24, 2011, at 12:08 , Chip Burke wrote: > unknown wrote in post #989053: >> On Thu, Mar 24, 2011 at 1:58 PM, Chip Burke >> wrote: >>> Ryan Davis wrote in post #988782: >>>> What C extensions might you have loaded? >>> >>> Forgive my ignorance as I am a syadmin and don't delve into those parts. >>> How can I find this information out? I am certain this is not a hardware >>> issue as this same problem has arisen on every box I have ever tried >>> this on. kk. no problem. Basically, are there any .so files in any of the lib dirs of the gems you've installed? What's this say? % gem env path then: % ls $(gem env path)/gems/*/lib/**/*.so In my case: % ls $(gem env path)/gems/*/lib/**/*.bundle /Library/Ruby/Gems/1.8/gems/nokogiri-1.4.4/lib/nokogiri/nokogiri.bundle /Library/Ruby/Gems/1.8/gems/sqlite3-1.3.3/lib/sqlite3/sqlite3_native.bundle > Install Fedora/CentOS. It has been a mixed bag thus far. Mostly x86_64 > systems. CentOS 5.3-5.5 or Fedora 8-13. > > Ruby 1.8.7 is installed via source. > ./configure --prefix=/usr > make > make install > > Gems then installed via #ruby setup.rb. I have always just grabbed the > latest/greatest gem version. 1.3.9, 1.6.2, etc > > Use gems to install passenger, rails, etc. > > 6 months later developer says "I gotta have 1.9.2!" > > Ok, now for 1.9.2 I follow the same procedures. > ./configure --prefix=/usr > make > make install > > And being that gems is included in 1.9x, I skip the gem install. Then > use gem to install rails etc. > > Everything works just peachy... gems install, apps run... then > mysteriously a day or so later everything curls up and dies like noted > above. % env | egrep "GEM|RUBY" In my case: 10006 % env | egrep "GEM|RUBY" GEM_PATH=/Library/Ruby/Gems/1.8 which can cause hell on wheels when I run ruby 1.9