/usr/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_support/dependencies.rb:200:in `const_missing'': uninitialized constant RailsFCGIHandler (NameError) from /var/rails/depot/public/dispatch.fcgi:24 I get the above log from my webserver running on apache+FastCGI Any help would be greatly appreciated, Mohammad
On 3/1/06, Mohammad Khan <beeplove@gmail.com> wrote:> /usr/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_support/dependencies.rb:200:in > `const_missing'': uninitialized constant RailsFCGIHandler (NameError) > from /var/rails/depot/public/dispatch.fcgi:24 > > I get the above log from my webserver running on apache+FastCGITry running dispatch.fcgi directly from the command line. It should generate something like "Error 500: Internal Server Error" If instead it blows up with a ruby dump you don''t have the ruby fcgi gem installed correctly. Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century
I forgot to install fcgi and fcgi.gem... after install them, I don''t see any output for ''ruby dispatch.fcgi'' But still have the following in my log: [Wed Mar 01 21:34:51 2006] [warn] FastCGI: server "/var/rails/depot/public/dispatch.fcgi" (pid 6975) terminated by calling exit with status ''0'' [Wed Mar 01 21:34:51 2006] [warn] FastCGI: server "/var/rails/depot/public/dispatch.fcgi" has failed to remain running for 30 seconds given 3 attempts, its restart interval has been backed off to 600 seconds Help me to understand above log message, please, Thanks, Mohammad On 3/1/06, Greg Freemyer <greg.freemyer@gmail.com> wrote:> On 3/1/06, Mohammad Khan <beeplove@gmail.com> wrote: > > /usr/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_support/dependencies.rb:200:in > > `const_missing'': uninitialized constant RailsFCGIHandler (NameError) > > from /var/rails/depot/public/dispatch.fcgi:24 > > > > I get the above log from my webserver running on apache+FastCGI > > Try running dispatch.fcgi directly from the command line. > > It should generate something like "Error 500: Internal Server Error" > > If instead it blows up with a ruby dump you don''t have the ruby fcgi > gem installed correctly. > > Greg > -- > Greg Freemyer > The Norcross Group > Forensics for the 21st Century > _______________________________________________ > Rails mailing list > Rails@lists.rubyonrails.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
On 3/1/06, Mohammad Khan <beeplove@gmail.com> wrote:> I forgot to install fcgi and fcgi.gem... after install them, > > I don''t see any output for ''ruby dispatch.fcgi'' > But still have the following in my log: > > [Wed Mar 01 21:34:51 2006] [warn] FastCGI: server > "/var/rails/depot/public/dispatch.fcgi" (pid 6975) terminated by > calling exit with status ''0'' > [Wed Mar 01 21:34:51 2006] [warn] FastCGI: server > "/var/rails/depot/public/dispatch.fcgi" has failed to remain running > for 30 seconds given 3 attempts, its restart interval has been backed > off to 600 seconds >Until you get dispatch.fcgi to properly fail in the absense of a webserver I would not even experiment with the webserver. Try to stop all apache / lighttpd webserver instances and then run "ruby dispatch.fcgi" again. AIUI, dispatch.fcgi should be attempting to connect to a socket that is provided by the now non-existent webserver. Since the socket does not have a listener it should error out with the "Error 500: Internal Server Error" message that I stated before. If dispatch.fcgi is simply exiting with no error message you still have something wrong in your fcgi setup that has nothing to do with apache/lighttpd. At that point you will need to be posting what env. (OS, distro, etc.) you are working with and what you did to get your fcgi setup going. Getting fcgi setup seems to be very specific to the OS and distro. I have only set it up once and that is on a Suse 10.0 setup, so I''m not sure I''m the one to help. FYI: AIUI, when things are working the webserver creates the sockets and establishes listens on them. Then the fcgi processes are started by the webserver in the background. They in turn connect to the sockets. The fcgi processes should be long lived (hours/days/weeks) and able to handle repeated requests for fcgi service from the webserver. Greg -- Greg Freemyer The Norcross Group Forensics for the 21st Century