Project

General

Profile

Upgrade problem from 1.1.1 to 1.1.2

Added by T N about 13 years ago

Dear All,

I try to upgrade from 1.1.1 to 1.1.2 using svn. I perform the followig steps:
1) svn upgrade -r 5030 (5030 is the revision number of 1.1.2 - according to the changelog file)
2) I run rake db:migrate_plugins RAILS_ENV=production
3) restart of httpd

When I try to login I get the message:

Internal error

An error occurred on the page you were trying to access.
If you continue to experience problems please contact your redMine administrator for assistance.

Checking the production Log I get the message:

===========================================================
NameError (undefined local variable or method `salt' for #<User:0x2a999cda60>):
app/models/user.rb:210:in `check_password?'
app/models/user.rb:126:in `try_to_login'
app/controllers/account_controller.rb:147:in `password_authentication'
app/controllers/account_controller.rb:142:in `authenticate_user'
app/controllers/account_controller.rb:30:in `login'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/rack/request_handler.rb:92:in `process_request'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/abstract_request_handler.rb:207:in `main_loop'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/railz/application_spawner.rb:441:in `start_request_handler'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/railz/application_spawner.rb:381:in `handle_spawn_application'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/utils.rb:252:in `safe_fork'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/railz/application_spawner.rb:377:in `handle_spawn_application'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/abstract_server.rb:352:in `__send__'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/abstract_server.rb:352:in `main_loop'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/abstract_server.rb:163:in `start'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/railz/application_spawner.rb:222:in `start'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/spawn_manager.rb:253:in `spawn_rails_application'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/spawn_manager.rb:247:in `spawn_rails_application'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/abstract_server_collection.rb:80:in `synchronize'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/spawn_manager.rb:246:in `spawn_rails_application'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/spawn_manager.rb:145:in `spawn_application'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/spawn_manager.rb:278:in `handle_spawn_application'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/abstract_server.rb:352:in `__send__'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/abstract_server.rb:352:in `main_loop'
/usr/local/lib/ruby/gems/1.8/gems/passenger-2.2.15-apache-2.0/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously' ==========================================================

Rendering /home/www/redmine/public/500.html (500 Internal Server Error)

Does anyone know what I missed in the update ?

Cheers
Tommy


Replies (2)

RE: Upgrade problem from 1.1.1 to 1.1.2 - Added by Andreas R about 13 years ago

+1

look like salt was added in r4936

There is a migration function, the DB is migrated and the salt field filled.

I'm using unicorn_rails and get this error.

Funny Thing now is:
Using lighttpd and fastcgi works somewhat.
I still get lots of Basic Auth Popup with ask for a "Redmine Api" Login.

RE: Upgrade problem from 1.1.1 to 1.1.2 - Added by Andreas R about 13 years ago

Stupid me:
I started in DEVELOPMENT environment.
So migrating the right env solves the issue for me....

:(

    (1-2/2)