Simple hopefully, newbish question, but how come it's saying starting in Rails 2.2.2 when I'm using 2.3.2 ?

I’m trying to get this app I have (I actually started it over fresh) to start up with rails 2.3.2

rick- ~/projects/rails/hockey $ sudo gem install rails -v 2.3.2
Password:
Successfully installed rails-2.3.2

1 gem installed
rick- ~/projects/rails/hockey $ sudo rake rails:update
(in /Users/rick/projects/rails/hockey)

rick- ~/projects/rails/hockey $ ruby script/server
=> Booting Mongrel (use ‘script/server webrick’ to force WEBrick)

=> Rails 2.2.2 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server

** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with development environment…
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart).

** Rails signals registered. HUP => reload (without restart). It might not work well.
** Mongrel 1.1.5 available at 0.0.0.0:3000
** Use CTRL-C to stop.

my environment.rb file has

RAILS_GEM_VERSION = ‘2.3.2’ unless defined? RAILS_GEM_VERSION

and my bash_profile has
export RAILS_GEM_VERSION=2.3.2

Why does it say “Rails 2.2.2 application starting on http://0.0.0.0:3000

gem list shows:
rick- ~/projects/rails/hockey $ gem list --local rails

*** LOCAL GEMS ***

rails (2.3.2, 2.2.2, 2.1.1, 2.1.0)

Anything in ~projects/rails/hockey/vendor/rails? That will override
any gems you have installed.

-philip

I’m trying to get this app I have (I actually started it over fresh) to start up with rails 2.3.2

rick- ~/projects/rails/hockey $ sudo gem install rails -v 2.3.2
Password:
Successfully installed rails-2.3.2

1 gem installed
rick- ~/projects/rails/hockey $ sudo rake rails:update
(in /Users/rick/projects/rails/hockey)
rick- ~/projects/rails/hockey $ ruby script/server
=> Booting Mongrel (use ‘script/server webrick’ to force WEBrick)

=> Rails 2.2.2 application starting on http://0.0.0.0:3000
=> Call with -d to detach
=> Ctrl-C to shutdown server

** Starting Mongrel listening at 0.0.0.0:3000
** Starting Rails with development environment…
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart).

** Rails signals registered. HUP => reload (without restart). It might not work well.
** Mongrel 1.1.5 available at 0.0.0.0:3000
** Use CTRL-C to stop.

my environment.rb file has

RAILS_GEM_VERSION = ‘2.3.2’ unless defined? RAILS_GEM_VERSION

and my bash_profile has
export RAILS_GEM_VERSION=2.3.2

I would recommend removing the above environment variable from your

bash_profile.

Why does it say “Rails 2.2.2 application starting on http://0.0.0.0:3000

gem list shows:
rick- ~/projects/rails/hockey $ gem list --local rails

*** LOCAL GEMS ***

rails (2.3.2, 2.2.2, 2.1.1, 2.1.0)

What does ‘rails -v’ produce?

-Conrad

environment variable removed and no, nothing in vendor (except an empty plugins diretory) and yet still when it starts up it says 2.2.2

Ok now this is getting more frustrating. I did a gem cleanup and now I only have one version of rails installed:

gem list --local rails

*** LOCAL GEMS ***

rails (2.3.2)

But when I start the server it says:
ruby script/server
Missing the Rails 2.2.2 gem. Please gem install -v=2.2.2 rails, update your RAILS_GEM_VERSION setting in config/environment.rb for the Rails version you do have installed, or comment out RAILS_GEM_VERSION to use the latest version installed.

I’ve commented out the line in my environment.rb:
#RAILS_GEM_VERSION = ‘2.3.2’ unless defined? RAILS_GEM_VERSION

and it still gives me the same message

Even doing rake rails:update says:

(in /Users/rick/projects/rails/hockey)
Missing the Rails 2.2.2 gem. Please gem install -v=2.2.2 rails, update your RAILS_GEM_VERSION setting in config/environment.rb for the Rails version you do have installed, or comment out RAILS_GEM_VERSION to use the latest version installed.

I even tried just defining the version in the environment.rb without the unless RAILS_GEM_VERSION:
RAILS_GEM_VERSION = ‘2.3.2’

and still same error.

What is going on?

No clue what the deal was but as a last ditch windows type effort (on a Mac) I rebooted. Sure enough the server is starting up using 2.3.2 ! No clue what the heck made the difference rebooting. I was even trying in new terminal windows to make sure it wasn’t some residual thing sourced in memory.

Oh well, it’s working now. Thanks for the patience.