RoR Rails frozed to 2.0.2 but application seems to be ignoring frozen rails?

[capslock118]

Hi,

On my local test server I have an application running rails 2.0.2. I froze rails knowing that on hostmonster the application could not run (currently hostmonster is set at 2.2.2).

The application runs perfectly on my local test server. I Send the entire application to hostmonster in its own project directory, with rails 2.0.2 frozen, and the application fails to start (giving me its relevant error 'Application failed to start').

The additional drag is that no logs seem to be ..well...logging so I cant see what issue is being cause.

and yes, the environment.rb is set to 2.0.2.

What do you think is going on here? Why would this app work on my local server but not hostmonster even though the rails version is frozen?

Does hostmonster circumvent frozen apps and forces rails apps to use what is on the server? I am at a loss here. Ive tried to upload the site in multiple ways, one instance just vender/* and app/* and config/* and lib/*specific files were sent, another time I sent the entire app into a blank directory.

Please let me know if you know of anything I can check to fix this issue.

[capslock118]

Ive looked more into it and found I could run

ruby dispatch.cgi to force a command console run.

This is the error I get:


# ruby dispatch.cgi
./../config/../vendor/rails/railties/lib/initializer.rb:49:in `send': undefined method `install_gem_spec_stubs' for #<Rails::Initializer:0x7febbeaa20d8> (NoMethodError)
from ./../config/../vendor/rails/railties/lib/initializer.rb:49:in `run'
from ./../config/boot.rb:46:in `load_initializer'
from ./../config/boot.rb:38:in `run'
from ./../config/boot.rb:11:in `boot!'
from ./../config/boot.rb:109
from ./../config/environment.rb:11:in `require'
from ./../config/environment.rb:11
from dispatch.cgi:3:in `require'
from dispatch.cgi:3


does anyone have insight?