On 20 Feb 2006, at 08:36, Simone F. wrote:
Have you done “gem install fcgi”?
Yes, I did this as well …
Simone
If you run “ruby dispatch.fcgi” directly from the command line you
should get “Status: 500 Internal Server Error.” due to the lack of a
webserver driving dispatch.fcgi.
If instead it blows up, you have a basic fcgi setup issue.
If you are getting the above, then I think you are having a website
configuration issue.
Greg
Greg F.
The Norcross Group
Forensics for the 21st Century
If you run “ruby dispatch.fcgi” directly from the command line you
should get “Status: 500 Internal Server Error.” due to the lack of a
webserver driving dispatch.fcgi.
This is what I do to debug a new application when I set it up and
something goes wrong. Normally a bit more verbose than looking in
apache logs
Hej, I create a new rails app on my system and that error disappeared
… but a new one came out
I know that on my mac some modules put themselves into
/usr/lib/ruby/site_ruby/1.8/…
but the main ruby install is in
/usr/lib/ruby/1.8
As its just a few extra modules in /site_ruby i have symlinked them
into the /1.8 folder.
Have a look in /usr/lib/ruby (or /usr/local/lib/ruby ) and see what
your setup is. Perhaps your app is looking in site_ruby but your ruby
install is in 1.8?
If you run “ruby dispatch.fcgi” directly from the command line you
should get “Status: 500 Internal Server Error.” due to the lack of a
webserver driving dispatch.fcgi.
If instead it blows up, you have a basic fcgi setup issue.
If you are getting the above, then I think you are having a website
configuration issue.
Hej, I create a new rails app on my system and that error disappeared
… but a new one came out
If you run “ruby dispatch.fcgi” directly from the command line you
should get “Status: 500 Internal Server Error.” due to the lack of a
webserver driving dispatch.fcgi.
If instead it blows up, you have a basic fcgi setup issue.
If you are getting the above, then I think you are having a website
configuration issue.
And what would that basic fcgi setup issue be?
When I run dispatch.fcgi or try to run the script from my browser this
appears in my apache error logs:
[notice] mod_fcgid: process
/usr/local/www/vhosts/shallotsanctuary.com/httpdocs/dispatch.fcgi(79949)
exit(communication error), terminated by calling exit(), return code:
120
