[FIXED] Upgraded from Redmine 1.3.2 to 1.4.0 and now getting 500 Internal Server Error
Added by Deoren Moor over 12 years ago
I had a working Redmine 1.3.2 installation on:
- nginx 1.0.15
- Phusion Passenger 3.0.12
that was originally installed from a Subversion tag, and did the following to upgrade from 1.3.2 to 1.4.0 (via a script):
service nginx stop cd /opt/redmine svn sw http://redmine.rubyforge.org/svn/tags/1.4.0 rake db:migrate RAILS_ENV=production rake tmp:cache:clear rake tmp:sessions:clear chown -R www-data . service nginx start
At that point I noticed the messages regarding bundler and looked up the documentation to see what had changed. Okay, so bundler it is.
I created /opt/redmine/Gemfile.local with this content:
gem "passenger"
I ran bundle install --without development testing postgresql and it finished. Running bundle show gives this:
Gems included by the bundle: * actionmailer (2.3.14) * actionpack (2.3.14) * activerecord (2.3.14) * activeresource (2.3.14) * activesupport (2.3.14) * bundler (1.0.22) * coderay (1.0.6) * daemon_controller (1.0.0) * fastercsv (1.5.4) * fastthread (1.0.7) * i18n (0.4.2) * mysql (2.8.1) * net-ldap (0.3.1) * passenger (3.0.12) * rack (1.1.3) * rails (2.3.14) * rake (0.9.2.2) * rmagick (2.13.1) * ruby-openid (2.1.8) * sqlite3 (1.3.5) * tzinfo (0.3.33)
Running gem list gives the following:
*** LOCAL GEMS *** actionmailer (2.3.14) actionpack (2.3.14) activerecord (2.3.14) activeresource (2.3.14) activesupport (2.3.14) arel (3.0.1) builder (3.0.0) bundler (1.0.22) coderay (1.0.6) daemon_controller (1.0.0, 0.2.5) erubis (2.7.0) fastercsv (1.5.4) fastthread (1.0.7) hike (1.2.1) i18n (0.6.0, 0.4.2) journey (1.0.2) json (1.6.5) mail (2.4.1) metaclass (0.0.1) mime-types (1.17.2) mocha (0.10.5) multi_json (1.1.0) mysql (2.8.1) net-ldap (0.3.1) passenger (3.0.12) polyglot (0.3.3) rack (1.1.3, 1.1.2, 1.0.1) rack-cache (1.1) rack-ssl (1.3.2) rack-test (0.6.1) rails (2.3.14) rake (0.9.2.2, 0.8.7) rdoc (3.12, 3.9.2) rmagick (2.13.1) ruby-openid (2.1.8) rubygems-update (1.7.2) rubytree (0.8.2) spruz (0.2.2) sqlite3 (1.3.5) thor (0.14.6) tilt (1.3.3) treetop (1.4.10) tzinfo (0.3.33, 0.3.31, 0.3.30)
When I visit the site, the initial page shows fine (the one showing latest news and latest projects), but clicking on anything specific to a project (project index, news entry, whatever) gives the 500 error.
Here is an entry from production.log with the IP addresses changed to x.x.x.x
Processing IssuesController#index (for x.x.x.x at 2012-04-14 10:40:24) [GET] Parameters: {"action"=>"index", "controller"=>"issues"} NoMethodError (undefined method `multiple?' for #<IssueCustomField:0xd5c5f14>): app/models/custom_field.rb:132:in `order_statement' app/models/query.rb:59:in `initialize' app/models/query.rb:370:in `new' app/models/query.rb:370:in `available_columns' app/models/query.rb:367:in `collect' app/models/query.rb:367:in `available_columns' app/models/query.rb:401:in `sortable_columns' app/controllers/issues_controller.rb:59:in `index' passenger (3.0.12) lib/phusion_passenger/rack/request_handler.rb:96:in `process_request' passenger (3.0.12) lib/phusion_passenger/abstract_request_handler.rb:513:in `accept_and_process_next_request' passenger (3.0.12) lib/phusion_passenger/abstract_request_handler.rb:274:in `main_loop' passenger (3.0.12) lib/phusion_passenger/classic_rails/application_spawner.rb:321:in `start_request_handler' passenger (3.0.12) lib/phusion_passenger/classic_rails/application_spawner.rb:275:in `send' passenger (3.0.12) lib/phusion_passenger/classic_rails/application_spawner.rb:275:in `handle_spawn_application' passenger (3.0.12) lib/phusion_passenger/utils.rb:479:in `safe_fork' passenger (3.0.12) lib/phusion_passenger/classic_rails/application_spawner.rb:270:in `handle_spawn_application' passenger (3.0.12) lib/phusion_passenger/abstract_server.rb:357:in `__send__' passenger (3.0.12) lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop' passenger (3.0.12) lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously' passenger (3.0.12) lib/phusion_passenger/abstract_server.rb:180:in `start' passenger (3.0.12) lib/phusion_passenger/classic_rails/application_spawner.rb:149:in `start' passenger (3.0.12) lib/phusion_passenger/spawn_manager.rb:219:in `spawn_rails_application' passenger (3.0.12) lib/phusion_passenger/abstract_server_collection.rb:132:in `lookup_or_add' passenger (3.0.12) lib/phusion_passenger/spawn_manager.rb:214:in `spawn_rails_application' passenger (3.0.12) lib/phusion_passenger/abstract_server_collection.rb:82:in `synchronize' passenger (3.0.12) lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize' passenger (3.0.12) lib/phusion_passenger/spawn_manager.rb:213:in `spawn_rails_application' passenger (3.0.12) lib/phusion_passenger/spawn_manager.rb:132:in `spawn_application' passenger (3.0.12) lib/phusion_passenger/spawn_manager.rb:275:in `handle_spawn_application' passenger (3.0.12) lib/phusion_passenger/abstract_server.rb:357:in `__send__' passenger (3.0.12) lib/phusion_passenger/abstract_server.rb:357:in `server_main_loop' passenger (3.0.12) lib/phusion_passenger/abstract_server.rb:206:in `start_synchronously' passenger (3.0.12) helper-scripts/passenger-spawn-server:99 Rendering /opt/redmine_todo_whyaskwhy_org/public/500.html (500 Internal Server Error)
Thankfully I have a backup of the database and /opt/redmine prior to the upgrade, so reverting won't be too much of a hassle. Am I missing anything obvious? Thanks in advance for your help.
Replies (5)
RE: Upgraded from Redmine 1.3.2 to 1.4.0 and now getting 500 Internal Server Error
-
Added by Jean-Philippe Lang over 12 years ago
Looks like you forgot to migrate your database. A new attribute was added to custom fields in 1.4.0.
RE: Upgraded from Redmine 1.3.2 to 1.4.0 and now getting 500 Internal Server Error
-
Added by Deoren Moor over 12 years ago
Thanks for the reply. Wouldn't rake db:migrate RAILS_ENV=production do that? I'll run it again just to be sure.
RE: Upgraded from Redmine 1.3.2 to 1.4.0 and now getting 500 Internal Server Error
-
Added by Deoren Moor over 12 years ago
Well, that was it, even though I know I ran the command earlier via the script. Thanks Jean.
RE: [FIXED] Upgraded from Redmine 1.3.2 to 1.4.0 and now getting 500 Internal Server Error
-
Added by Jean-Philippe Lang over 12 years ago
Glad it worked. Maybe you didn't restart Redmine after running db:migrate the first time.
RE: [FIXED] Upgraded from Redmine 1.3.2 to 1.4.0 and now getting 500 Internal Server Error
-
Added by Deoren Moor over 12 years ago
Me too. Thanks again for your help.