Patch #2815
closedInternal server error after updating to r2519
0%
Description
After updating to r2519 redmine stopped to work, the error message was HTTP 500, the relevant log excerpt is the following:
/!\ FAILSAFE /!\ Mon Feb 23 20:51:51 +0100 2009
Status: 500 Internal Server Error
A secret is required to generate an integrity hash for cookie session data. Use config.action_controller.session = { :session_key => "_myapp_session", :secret => "some secret phrase of at least 30 characters" } in config/environment.rb
/usr/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/session/cookie_store.rb:91:in `ensure_secret_secure'
/usr/lib/ruby/gems/1.8/gems/actionpack-2.2.2/lib/action_controller/session/cookie_store.rb:59:in `initialize'
/usr/lib/ruby/1.8/cgi/session.rb:279:in `new'
...
Based on error message I added the following line to environment.rb:
config.action_controller.session = { :session_key => "_myapp_session", :secret => "eiR0Eph9cein2ooreree3Aiya1ocho"}
I'm not sure, that it is the proper solution, but it is working for me.
Files
Updated by Jean-Baptiste Barth over 15 years ago
I think you've missed this news
Updated by Mihaly Nyeste over 15 years ago
- Status changed from New to Resolved
You're right I missed it, even it was right in front of my eyes...
Updated by Leandro Lucarella over 15 years ago
- Status changed from Closed to Reopened
I don't know if this is a plug-in issue or Redmine issue but I'm getting this error when using the BotsFilterPlugin. I've done all the upgrade steps (I'm on latest svn) and if I remove the plugin, it works great.
Updated by Jérémy Lal about 15 years ago
With redmine trunk 2886 and rails 2.2.3, if i simply add the bots filter plugin v1.01, it crashes (see attached stack trace),
if i remove it, it works ok.
My config/initializers/session_store.rb is properly set, and i can use redmine, login, without any trouble, except when
i add this plugin.
Updated by Jérémy Lal about 15 years ago
Setting in config/environment.rb :
config.action_controller.session_store = :active_record_store
fixes the issue, though i have no idea why.
Updated by Jérémy Lal about 15 years ago
forgot to mention that
rake db:sessions:create
rake db:migrate
shall be called for the previous line to work.
Updated by Jérémy Lal about 15 years ago
In fact it did not really fix the issue, it just hid it,
see issue #3969.
Updated by Jean-Philippe Lang about 15 years ago
- Status changed from Reopened to Closed
This is not reproductible with latest trunk and Rails 2.3.4.