Forum: Ruby Status: 500 Internal Server Error - A session_key is require

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
Greg H. (Guest)
on 2007-04-04 00:01
(Received via mailing list)

Anyone seen this error / have any suggestions here?

I basically did a "cap deploy" to dreamhost but I'm now getting this in
"production.log" when trying to run up the application.  The key things
changed in the deployment is that I:

a) When to rails v1.2.3 (well to revision 6419 really for completeness -
which I looked up to be v1.2.3)
b) I implemented the deployment technique from Mike C. at the bottom
section ("The Cadillac Approach") of,
  - checks out rails (rev 6419) to a shared area
  - then symlinks the app /vendor/rails directory to this area
  - basically allows capistrano to be run to update your application but
without having to put rails into the project to minimise checkout time

Any ideas?

(actually I'm not exactly sure with this approach what setting I should
in environment.rb for RAILS_GEM_VERSION - I've tried both commenting it
and setting it to '1.2.2' but I get the below error in both cases)

DISPATCHER FAILSAFE RESPONSE (has cgi) Tue Apr 03 12:33:37 -0700 2007
  Status: 500 Internal Server Error
  A session_key is required to write a cookie containing the session
Use config.action_controller.session = { :session_key =>
:secret => "some secret phrase" } in config/environment.rb

    /usr/lib/ruby/1.8/cgi/session.rb:273:in `new'











    /usr/lib/ruby/1.8/fcgi.rb:600:in `each_cgi'
    /usr/lib/ruby/1.8/fcgi.rb:597:in `each'
    /usr/lib/ruby/1.8/fcgi.rb:597:in `each_cgi'

Phillip G. (Guest)
on 2007-04-04 01:04
(Received via mailing list)
Greg H. wrote:
[SNIP rails problem]

The Rails folk are probably more experienced with all things Rails. ;)

Phillip "CynicalRyan" Gawlowski

Rule of Open-Source Programming #5:

A project is never finished.
Greg H. (Guest)
on 2007-04-04 04:56
(Received via mailing list)
oops - choose the wrong group by mistake
This topic is locked and can not be replied to.