# Ruby 1.9.1-p129 and Rails 2.3.2

**URL:** <https://discuss.rubyonrails.org/t/ruby-1-9-1-p129-and-rails-2-3-2/43063>\
**Category:** rubyonrails-talk\
**Created:** [June 1, 2009, 3:32am UTC](https://discuss.rubyonrails.org/t/ruby-1-9-1-p129-and-rails-2-3-2/43063 "2009-06-01T03:32:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ZhayTee](https://avatars.discourse-cdn.com/v4/letter/z/ecc23a/32.png) [@ZhayTee](https://discuss.rubyonrails.org/u/ZhayTee)\
**Post date:** [June 1, 2009, 3:32am UTC](https://discuss.rubyonrails.org/t/ruby-1-9-1-p129-and-rails-2-3-2/43063/1 "2009-06-01T03:32:13Z")

</div>

Hi,

According to its release notes, Rails 2.3.2 should run fine on Ruby 1.9.1. Since I've read about substantial performance gains from 1.9, I decided to upgrade.

I built and installed Ruby 1.9.1-p129 on my server (Ubuntu 9.04, amd64 CPU) without any problems. Similarly, I was able to install Rails 2.3.2 via "gem" without any problems.

Unfortunately, Rails itself fails to function. Running the "rails" script fails with the following error:

\<internal:gem\_prelude\>:234:in `push\_gem\_version\_on\_load\_path': Could not find RubyGem activesupport (\>= 0) (Gem::LoadError)

And trying to require one of the component gems also fails, as follows:

irb(main):001:0\> require "activerecord" LoadError: no such file to load -- i18n/backend/simple &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;from /opt/ruby-1.9.1-p129/lib/ruby/gems/1.9.1/gems/ activerecord-2.3.2/lib/active\_record/i18n\_interpolation\_deprecation.rb: 5:in `require'

Installing the "i18n" gem merely causes further problems, as follows:

irb(main):001:0\> require 'activerecord' NoMethodError: undefined method `alias_method_chain' for I18n::Backend::Simple:Class &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;from /opt/ruby-1.9.1-p129/lib/ruby/gems/1.9.1/gems/ activerecord-2.3.2/lib/active_record/i18n_interpolation_deprecation.rb: 23:in `\<class:Simple\>'

What follows is a list of the installed gems on my system:

[zhaytee@orzhova] ~$ gem list \*\*\* LOCAL GEMS \*\*\* actionmailer (2.3.2) actionpack (2.3.2) activerecord (2.3.2) activeresource (2.3.2) activesupport (2.3.2) fastthread (1.0.7) i18n (0.1.0) passenger (2.2.2) pg (0.8.0) rails (2.3.2) rake (0.8.4)

Is Rails 2.3.2 simply not compatible with 1.9.1, despite what the release notes say? Any help would be greatly appreciated.

ZhayTee

---

<div class="post-metadata">

**Author:** ![11175](https://avatars.discourse-cdn.com/v4/letter/1/8edcca/32.png) [@11175](https://discuss.rubyonrails.org/u/11175)\
**Post date:** [July 3, 2009, 1:25pm UTC](https://discuss.rubyonrails.org/t/ruby-1-9-1-p129-and-rails-2-3-2/43063/2 "2009-07-03T13:25:32Z")

</div>

Steve, try freezing your rails gems before starting the server and let me know what happens.

---

<div class="post-metadata">

**Author:** ![George\_M\_Harkin](https://avatars.discourse-cdn.com/v4/letter/g/848f3c/32.png) [@George\_M\_Harkin](https://discuss.rubyonrails.org/u/George_M_Harkin)\
**Post date:** [July 15, 2009, 3:25pm UTC](https://discuss.rubyonrails.org/t/ruby-1-9-1-p129-and-rails-2-3-2/43063/3 "2009-07-15T15:25:30Z")

</div>

Hi ZhayTee,

It sounds like ruby 1.9.1 isn't being used to run your app. Make sure all symlinks to the ruby interpret point to 1.9. Also, you will need to reinstall gem with ruby 1.9.1 and then re-download and install the rails gems with the new gem install for 1.9.

Worked for us.

Cheers, George