Project

General

Profile

Bitnami Stack and Upgrading

Added by Chris Nicola over 14 years ago

Is it possible to upgrade Redmine to the trunk when using the Bitnami stack. We use git and I would like to be able to use the branching features.

So far my attempts to upgrade following the Wiki instructions have failed. I can't access the site after restarting apache (though the db:migrate went fine).

Thanks,
Chris


Replies (7)

RE: Bitnami Stack and Upgrading - Added by Chris Nicola over 14 years ago

Here is my basic process:

- Install bitnami stack (0.8.4)
- Checkout trunk into a new folder
- Backup database and files folder
- Copy database.yml, email.yml to trunk folder
- Set RAILS_GEM_VERSION = '2.3.2' for environment.rb since that is what bitnami uses
- Run rake config/initializers/session_store.rb
- Run rake db:migrate RAILS_ENV="production"
- Copy bitnami related folders (redmine/conf, redmine/scripts) to the trunk folder
- Rename the original folder to .old and rename the trunk folder to /redmine/
- Restart the mongrel and apache services

When I try to access the site I get this error:

Proxy Error

The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /redmine/.

Reason: Error reading from remote server

RE: Bitnami Stack and Upgrading - Added by Chris Nicola over 14 years ago

Some more info:

C:\PROGRA~1\BitNami Redmine Stack\apps\redmine>ruby script/server -e production
=> Booting Mongrel
=> Rails 2.3.2 application starting on http://0.0.0.0:3000
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/activesupport
-2.3.2/lib/active_support/dependencies.rb:443:in `load_missing_constant': uninitialized constant ApplicationController (NameError)

I am going to try installing rails 2.2.2 specifically and cross my fingers.

RE: Bitnami Stack and Upgrading - Added by Chris Nicola over 14 years ago

Well I can get it started with ruby script/server -e production. I had to update the mysql gem.

However, the bitnami mogrel services do not work at all. The log shows the following:

  • Starting Mongrel listening at 0.0.0.0:3001
  • Starting Rails with production environment...
    C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require': no such file to load -- C:/Program Files/BitNami Redmine Stack/apps/redmine/vendor/rails/railties/lib/initializer (LoadError)
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
    from C:/Program Files/BitNami Redmine Stack/apps/redmine/config/boot.rb:45:in `load_initializer'
    from C:/Program Files/BitNami Redmine Stack/apps/redmine/config/boot.rb:38:in `run'
    from C:/Program Files/BitNami Redmine Stack/apps/redmine/config/boot.rb:11:in `boot!'
    from C:/Program Files/BitNami Redmine Stack/apps/redmine/config/boot.rb:109
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
    from C:/Program Files/BitNami Redmine Stack/apps/redmine/config/environment.rb:11
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:31:in `require'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/rails.rb:147:in `rails'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:113:in `cloaker_'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:149:in `call'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:149:in `listener'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:99:in `cloaker_'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:50:in `call'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/configurator.rb:50:in `initialize'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:84:in `new'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:84:in `run'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/../lib/mongrel/command.rb:212:in `run'
    from C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281
    from C:/Program Files/BitNami Redmine Stack/ruby/bin/mongrel_rails:19:in `load'
    from C:/Program Files/BitNami Redmine Stack/ruby/bin/mongrel_rails:19

RE: Bitnami Stack and Upgrading - Added by Chris Nicola over 14 years ago

Ok I think I have finally narrowed this down. I can start it myself just fine.

However, the bitnami service starter which runs the following script to install the service:

"C:\Program Files\BitNami Redmine Stack\ruby\bin\ruby.exe" "C:\Program Files\BitNami Redmine Stack\ruby\bin\mongrel_rails" service::install -N "redmineMongrel1" -p 3001 -e production -c "C:\Program Files\BitNami Redmine Stack\apps\redmine" --prefix /redmine -S "C:\Program Files\BitNami Redmine Stack\apps\redmine\scripts\mongrel_rails_envvars"
sc config redmineMongrel1 start= auto
net start redmineMongrel1 >NUL

Results in this:

  • Starting Mongrel listening at 0.0.0.0:3001
  • Starting Rails with production environment...
  • Mounting Rails at /redmine...
    !!! The bundled mysql.rb driver has been removed from Rails 2.2. Please install the mysql gem and try again: gem install mysql.
    C:!!! The bundled mysql.rb driver has been removed from Rails 2.2. Please install the mysql gem and try again: gem install mysql.
    C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mysql-2.7.1-x86-mswin32/ext/mysql.so: 126: The specified module could not be found. - C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mysql-2.7.1-x86-mswin32/ext/mysql.so (LoadError)

Obviously the mysql gem is installed since it works fine manually. Something is wrong with the way that service is set up.

RE: Bitnami Stack and Upgrading - Added by Chris Nicola over 14 years ago

Ok this post fixed my sql problem: http://forums.aptana.com/viewtopic.php?f=20&t=7563

Now I am starting up fine:
  • Starting Mongrel listening at 0.0.0.0:3001
  • Starting Rails with production environment...
  • Mounting Rails at /redmine...
  • Rails loaded.
  • Loading any Rails specific GemPlugins
  • Loading C:\Program Files\BitNami Redmine Stack/apps/redmine\scripts\mongrel_rails_envvars external config script
  • Signals ready. INT => stop (no restart).
  • Mongrel 1.1.5 available at 0.0.0.0:3001
  • Use CTRL-C to stop.
    l config script
  • Signals ready. INT => stop (no restart).
  • Mongrel 1.1.5 available at 0.0.0.0:3002
  • Use CTRL-C to stop.

But when I browse to the server:
Status: 500 Internal Server Error Content-Type: text/html
500 Internal Server Error

I must have made a mistake somewhere now. Even when I run script/server -e production I get that error.

RE: Bitnami Stack and Upgrading - Added by Chris Nicola over 14 years ago

w00t got it! I had cleaned it up earlier and for got to run rake config/initializers/session_store.rb again.

    (1-7/7)