Forum: Ruby on Rails What is supposed to happen when you run dispatch.fcgi?

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.
Pat M. (Guest)
on 2006-01-30 15:05
(Received via mailing list)
I've seen a number of posts where someone says, "What happens if you
just run dispatch.fcgi directly?"  Every time I do it, I get a "500:
internal server error" message.  I was just curious if that's what's
expected running it directly.  I assume so, because my apps all work
fine, but that's always bugged me.

Raghuraman Suraj (Guest)
on 2006-01-30 15:52
(Received via mailing list)
Dispather is used to call the rails handler which in turn will look into
the routes.rb & decide the controllers, action with what parameter, so
when u call the dispatch.fcgi directly, their are no parameters so it
will give a routing error & hence in deployment mode you will get page
not found, if ur not getting that error chk the server log.
Pat M. (Guest)
on 2006-01-30 16:14
(Received via mailing list)
baggio:~/work/teore-1_0 pergesu$ ./public/dispatch.fcgi
Status: 500 Internal Server Error
[30/Jan/2006:07:10:54 :: 6800] starting
[30/Jan/2006:07:10:55 :: 6800] terminated gracefully

Nothing in any other logs.
HH (Guest)
on 2006-01-30 19:47
(Received via mailing list)
Since you're not speaking to the dispatcher in the FCGI protocol, I
the 500 is normal.
Ezra Z. (Guest)
on 2006-01-30 19:59
(Received via mailing list)
On Jan 30, 2006, at 5:04 AM, Pat M. wrote:



	500 Internal Server error is the correct thing to see when you  run
dispatch.fcgi from the cli. It is expecting to be spoken to in the
fcgi protocol and when its not it will return a 500. Once and for all
running dispatch.fcgi from the cli will return a 500 error even when
your server is set up perfectly.

-Ezra Z.
Yakima Herald-Republic
This topic is locked and can not be replied to.