HELP! working refinery installation stopped working

[Fabio Barone]

Unfortunately, my working refinery 0.9.6.31 stopped working.

All happened after an announced rails upgrade by the hosting.
They suggested to do:

rake rails:freeze:edge RELEASE=2.3.5

to freeze our version of rails. Which I did. I have a rails directory in the vendor dir:

ls vendor
./  ../  plugins/  rails/

ls vendor/rails
./   actionmailer/  activemodel/   activeresource/  ci/   .gitignore  REVISION
../  actionpack/    activerecord/  activesupport/   doc/  railties/

After I did that I briefly tested the application and it was still working.
It stopped to work however yesterday.
My debugging session does show me that it stops working in the code block

Refinery::Initializer.run do |config|
  # Settings in config/environments/* take precedence over those specified here.
  # Application configuration should go into files in config/initializers
  # -- all .rb files in that directory are automatically loaded.
  # See Rails::Configuration for more options.

  config.action_controller.session = {
    :session_key => '_refinery_session',
    :secret      => 'bf2223bee2dda5ea0fd8925b4eca24c4e69d281498564307db13165a4cfd5fdac0ed93317c1577cd4a0d809cddaf8eecbc1ef1814131865faea6d3b4'
  }

end

The production.log does not show any entry.
I have no clue where else to look.

Unfortunately this is a troubled hosting we had anyway, hostmonster.com which uses apache with fastcgi.
I will suggest to change hosting, but that will require some time to set up (we were just handing over to the client; a new heroku set up would require a new S3 account for the client, etc.), so we would like to have the app back up first.

I have tried to unpack all gems into vendor/gems,
but no joy.

Any suggestions what else I could do?
Thanks very much for all help, really appreciated now...

P.S. This is the announced upgrade list:
ImageMagick 6.5.9-9 => 6.6.3-2
   rmagick 2.13.0 => 2.13.1
   actionmailer 2.3.5 => 2.3.8
   actionpack 2.3.5 => 2.3.8
   activerecord 2.3.5 => 2.3.8
   activeresource 2.3.5 => 2.3.8
   activesupport 2.3.5 => 2.3.8
   daemons 1.0.10 => 1.1.0
   rack 1.0.1 => 1.1.0
   rack-contrib 1.0.1 (new)
   rails 2.3.5 => 2.3.8
   tzinfo 0.3.18 => 0.3.22
   rubygems 1.3.5 => 1.3.7

[Philip Arndt]

That version of refinery should work fine with the versions you listed. What I would do in this situation is remove the vendored rails directory and tell it to use 2.3.8 instead.. I used 2.3.8 on a 0.9.6.30 project today!

Hope that helps!
>

[Fabio Barone]

Thanks Philip,

I had already tried that.
But nevertheless I am going down that path again, and my debugging now tells me:

    def load_rails_gem
      if version = self.class.gem_version
File.open("debug.log", 'w') {|f| f.write("loading version...." + version) }
        gem 'rails', version
File.open("debug.log", 'w') {|f| f.write("loaded version 2.3.5") }

I get a debug output

loading version...2.3.5

but then nothing else.
thus, gem 'rails', version
fails.

any suggestion????
I am guessing that 'gem' inside this ruby file is having a different gem_path.



2010/9/1 Philip Arndt <ph...@resolvedigital.co.nz>

That version of refinery should work fine with the versions you listed. What I would do in this situation is remove the vendored rails directory and tell it to use 2.3.8 instead.. I used 2.3.8 on a 0.9.6.30 project today!

Hope that helps!
>

--
You received this message because you are subscribed to the Google
Groups "Refinery CMS" group.
To post to this group, send email to refine...@googlegroups.com
To unsubscribe from this group, send email to
refinery-cms...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/refinery-cms?hl=en

http://www.refinerycms.com

[Philip Arndt]

Gutted. Can't think of other ways. Hope someone else can pick this up and figure it out. Fastcgi is hard. You may have to move to Heroku sooner than you wanted

[Fabio Barone]

OK, recommended to change hosting to my boss.

Here's how the app is loaded through fastcgi (for completion's sake):
-.htaccess loads dispatch.fcgi
- dispatch.fcgi loads config/environment.rb
- this one expands to config/application.rb
- where config/boot.rb is loaded

What I can't understand is that config/application.rb loads

gem 'rails'  inside config/boot.rb
which starts
Rails::Initializer.run(:set_load_path)

but later boots
Refinery::Initializer.run do |config|

that seems to me as things are tried to be loaded twice.

Nevertheless it was working before so I am clueless

2010/9/1 Philip Arndt <ph...@resolvedigital.co.nz>

Gutted. Can't think of other ways. Hope someone else can pick this up and figure it out. Fastcgi is hard. You may have to move to Heroku sooner than you wanted

--