Rails - Feb 2006 - Re: Manually running dispatch.fcgi fails (Please help!!)

I''m really lost on this issue.  Do I need to reinstall rails / gems?

The rest of my rails setup seems to be working.  I just can''t run
dispatch.fcgi.  (Details in original message below).

I have no idea how to troubleshoot this.  I''m not even positive it is
supposed to be runnable from the command line.  I found a
troubleshooting guide that implied it was supposed to work.

Ideas are very welcome.  FYI: I using SUSE 10.0 with self installed
rails and lighttpd.

Thanks
Greg

On 2/9/06, Greg Freemyer <greg.freemyer@gmail.com>
wrote:
> On 2/9/06, Jim Nachlin <jim@motionbox.com> wrote:
> > Greg Freemyer wrote:
> > > I''m a newbie trying to setup lighttpd.  It is failing
with error 500.
> > >
> > > I tried running dispatch.fcgi by hand and I''m getting:
> > >
> > > # ./dispatch.fcgi
> > >
> >
/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 ./dispatch.fcgi:24
> > >
> >
> >  From one noob to another, I think this may be a red herring.  What
does
> > your dispatch.fcgi look like?  What''s your environment?  I
was getting
> > this error as well, and I _believe_ it was because my dispatch.fcgi
did
> > not just say
> >
> > require ''fcgi_handler''
> >
> > , instead using
> >
> > require ''rubygems''
> > require_gem ''fcgi''
> >
>
> Ignoring comments my entire dispatch.fcgi file is:
>
> #!/usr/bin/ruby
> require File.dirname(__FILE__) + "/../config/environment"
> require ''fcgi_handler''
>
> RailsFCGIHandler.process!
>
> Can you run your dispatch.fcgi from the command line?
>
> Greg
> --
> Greg Freemyer
> The Norcross Group
> Forensics for the 21st Century
>

--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century

It''s my understanding that dispatch.fcgi isn''t runnable from
the command
line as it expects the process connecting to it to be speaking in
FCGI-language and you at the command line are not.

FYI, out of my many working FCGI setups, I''ve only ever gotten Error
500
when trying to run it via the command line - I don''t think it is
supposed to
work.

> From: Greg Freemyer <greg.freemyer@gmail.com>
> Reply-To: <rails@lists.rubyonrails.org>
> Date: Thu, 9 Feb 2006 19:03:13 -0500
> To: <rails@lists.rubyonrails.org>
> Subject: [Rails] Re: Manually running dispatch.fcgi fails (Please help!!)
> 
> I''m really lost on this issue.  Do I need to reinstall rails /
gems?
> 
> The rest of my rails setup seems to be working.  I just can''t run
> dispatch.fcgi.  (Details in original message below).
> 
> I have no idea how to troubleshoot this.  I''m not even positive it
is
> supposed to be runnable from the command line.  I found a
> troubleshooting guide that implied it was supposed to work.
> 
> Ideas are very welcome.  FYI: I using SUSE 10.0 with self installed
> rails and lighttpd.
> 
> Thanks
> Greg
> 
> On 2/9/06, Greg Freemyer <greg.freemyer@gmail.com> wrote:
>> On 2/9/06, Jim Nachlin <jim@motionbox.com> wrote:
>>> Greg Freemyer wrote:
>>>> I''m a newbie trying to setup lighttpd.  It is failing
with error 500.
>>>> 
>>>> I tried running dispatch.fcgi by hand and I''m getting:
>>>> 
>>>> # ./dispatch.fcgi
>>>> 
>>>
/usr/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_support/dependenc
>>> ies.rb:200:in
>>>> `const_missing'': uninitialized constant
RailsFCGIHandler (NameError)
>>>>         from ./dispatch.fcgi:24
>>>> 
>>> 
>>>  From one noob to another, I think this may be a red herring.  What
does
>>> your dispatch.fcgi look like?  What''s your environment?  I
was getting
>>> this error as well, and I _believe_ it was because my dispatch.fcgi
did
>>> not just say
>>> 
>>> require ''fcgi_handler''
>>> 
>>> , instead using
>>> 
>>> require ''rubygems''
>>> require_gem ''fcgi''
>>> 
>> 
>> Ignoring comments my entire dispatch.fcgi file is:
>> 
>> #!/usr/bin/ruby
>> require File.dirname(__FILE__) + "/../config/environment"
>> require ''fcgi_handler''
>> 
>> RailsFCGIHandler.process!
>> 
>> Can you run your dispatch.fcgi from the command line?
>> 
>> Greg
>> --
>> Greg Freemyer
>> The Norcross Group
>> Forensics for the 21st Century
>> 
> 
> 
> --
> Greg Freemyer
> The Norcross Group
> Forensics for the 21st Century
> _______________________________________________
> Rails mailing list
> Rails@lists.rubyonrails.org
> http://lists.rubyonrails.org/mailman/listinfo/rails

See my post in http://wiki.rubyonrails.com/rails/pages/FastCGI
about troubleshooting

HTH

On 2/10/06, HH <lists@lastonepicked.com> wrote:
> It''s my understanding that dispatch.fcgi isn''t runnable
from the command
> line as it expects the process connecting to it to be speaking in
> FCGI-language and you at the command line are not.
>
> FYI, out of my many working FCGI setups, I''ve only ever gotten
Error 500
> when trying to run it via the command line - I don''t think it is
supposed to
> work.
--
kamus online - http://kamus.landak.com/

On 2/9/06, HH <lists@lastonepicked.com> wrote:
> It''s my understanding that dispatch.fcgi isn''t runnable
from the command
> line as it expects the process connecting to it to be speaking in
> FCGI-language and you at the command line are not.
>
> FYI, out of my many working FCGI setups, I''ve only ever gotten
Error 500
> when trying to run it via the command line - I don''t think it is
supposed to
> work.
>
Thanks for the feedback.  I admit to getting frustrated on this issue.

Note that I''m not complaining about the error 500 at this point. 
I''m
complaining that dispatch.fcgi in pure standalone mode crashes within
a couple seconds.  The troubleshooting reference I read implied it
should at least run until a control-c killed it.

If indeed dispatch.fcgi should not run at all in standalone mode I can
live with that, but when I try to run lighttpd from the command line:
     I get nothing for a few seconds then a get a burst of error
messages identical to what I get when I run dispatch.fcgi from the
command line.
> >>>
/usr/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_support/dependenc
> >>> ies.rb:200:in
> >>>> `const_missing'': uninitialized constant
RailsFCGIHandler (NameError)
> >>>>         from ./dispatch.fcgi:24
> >>>>
After that if I do a ps -ef I see a collection of zombies and no live
dispatch.fcgi processes.

Something is definately wrong with my setup but I really don''t know
how to troubleshoot the  issue.

Can someone simply run dispatch.fcgi from there command line and tell
me what happens on a machine that is functioning fine?

Thanks
Greg
--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century

Thanks,

I thought the "Status: 500 Internal Server Error" was coming from the
webserver.

As I said before I get:
>/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 ./dispatch.fcgi:24
Your feedback clearly shows the above is wrong and not just an issue
with dispatch.fcgi dieing when it is run standalone from the command
line.

I looked in fcgi_handler.rb and it is declaring RailsFCGIHandler.

I''ve read about a ruby debugger.  Should I try to run dispatch.fcgi in
it and see what is happening?

Thanks
Greg

On 2/10/06, HH <lists@lastonepicked.com> wrote:
> Here''s what I get:
>
> [root@marge vegaslists]# ruby public/dispatch.fcgi
> Status: 500 Internal Server Error
>
>
> > From: Greg Freemyer <greg.freemyer@gmail.com>
> > Date: Fri, 10 Feb 2006 00:01:47 -0500
> > To: HH <lists@lastonepicked.com>
> > Cc: Rails <rails@lists.rubyonrails.org>
> > Subject: Re: [Rails] Re: Manually running dispatch.fcgi fails (Please
help!!)
> >
> > On 2/9/06, HH <lists@lastonepicked.com> wrote:
> >> It''s my understanding that dispatch.fcgi isn''t
runnable from the command
> >> line as it expects the process connecting to it to be speaking in
> >> FCGI-language and you at the command line are not.
> >>
> >> FYI, out of my many working FCGI setups, I''ve only ever
gotten Error 500
> >> when trying to run it via the command line - I don''t
think it is supposed to
> >> work.
> >>
> >
> > Thanks for the feedback.  I admit to getting frustrated on this issue.
> >
> > Note that I''m not complaining about the error 500 at this
point.  I''m
> > complaining that dispatch.fcgi in pure standalone mode crashes within
> > a couple seconds.  The troubleshooting reference I read implied it
> > should at least run until a control-c killed it.
> >
> > If indeed dispatch.fcgi should not run at all in standalone mode I can
> > live with that, but when I try to run lighttpd from the command line:
> >      I get nothing for a few seconds then a get a burst of error
> > messages identical to what I get when I run dispatch.fcgi from the
> > command line.
> >
> >>>>>
/usr/lib/ruby/gems/1.8/gems/activesupport-1.2.5/lib/active_support/depende
> >>>>> nc
> >>>>> ies.rb:200:in
> >>>>>> `const_missing'': uninitialized constant
RailsFCGIHandler (NameError)
> >>>>>>         from ./dispatch.fcgi:24
> >>>>>>
> >
> > After that if I do a ps -ef I see a collection of zombies and no live
> > dispatch.fcgi processes.
> >
> > Something is definately wrong with my setup but I really
don''t know
> > how to troubleshoot the  issue.
> >
> > Can someone simply run dispatch.fcgi from there command line and tell
> > me what happens on a machine that is functioning fine?
> >
> > Thanks
> > Greg
> > --
> > Greg Freemyer
> > The Norcross Group
> > Forensics for the 21st Century
>
>
>

--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century

On 2/9/06, Superbiji <superbiji@gmail.com> wrote:
> See my post in http://wiki.rubyonrails.com/rails/pages/FastCGI
> about troubleshooting
>
> HTH
That seems to be about apache/fcgi integration.  I''m trying to use
lighttpd so I''m not sure it is relevant?

Greg
--
Greg Freemyer
The Norcross Group
Forensics for the 21st Century