This is definitely one of the more annoying parts of
setting up a Rails application.
The first thing I’d suggest is to make sure all your
permissions are correct on the server you’re uploading
to – correct owners, correct groups, log files
writable, scripts executable, /tmp directory free of
old session files belonging to the wrong user. If
that’s all kosher, here’s a way to find out exactly
what’s stopping your dispatcher.
Find your Dispatcher class in your Rails installation.
On my Debian system, it’s in
Then, find the dispatch method. You’ll find a place
where a block is passed to a function
‘failsafe_response’. Comment out that line and the
corresponding ‘end’ so that the process_with_exception
call is simply executed, not in a block. Save this
change then try running the dispatch.fcgi script
manually. It should spit out a useful error.
To be honest it’s a while since I’ve done this, so I
might have got some details wrong, but I reckon you
get the idea. The trick is to make the dispatcher
spit out a useful error message. Once you can do
that, you’re swimming.
(BTW – you should return the dispatcher to its
original state after you fix the problem.)
Hope that helps.
— Maarten H. email@example.com wrote:
Rails mailing list
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around