FastCGI problems

Rails
1

I’m having a lot of problems with my Typo install. My fastcgi fails
horribly
after a reboot:

[13/Jan/2006:16:55:28 :: 19796] Dispatcher failed to catch: (Interrupt)
/usr/lib/ruby/site_ruby/1.8/fcgi.rb:597:in each' /usr/lib/ruby/site_ruby/1.8/fcgi.rb:597:ineach_cgi’
/usr/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:52:in
process!' /usr/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:22:inprocess!’
public/dispatch.fcgi:24
killed by this error
[13/Jan/2006:16:55:28 :: 19797] Dispatcher failed to catch: (Interrupt)
/usr/lib/ruby/site_ruby/1.8/fcgi.rb:597:in each' /usr/lib/ruby/site_ruby/1.8/fcgi.rb:597:ineach_cgi’
/usr/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:52:in
process!' /usr/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:22:inprocess!’
public/dispatch.fcgi:24
killed by this error

Does anyone have any clues? I must say that other typo users on that
server
are doubting Rails now, which I don’t really like…

2

On 1/13/06, Bart B. [email protected] wrote:

public/dispatch.fcgi:24
killed by this error
[13/Jan/2006:16:55:28 :: 19797] Dispatcher failed to catch: (Interrupt)
/usr/lib/ruby/site_ruby/1.8/fcgi.rb:597:in each' /usr/lib/ruby/site_ruby/1.8/fcgi.rb:597:in each_cgi’
/usr/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:52:in
process!' /usr/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:22:in process!’
public/dispatch.fcgi:24
killed by this error

Something is sending your FCGI procress a signal which there is no
handler for.

Does anyone have any clues? I must say that other typo users on that server
are doubting Rails now, which I don’t really like…

Rails mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails

–
Jon S.
[email protected]

3

Jon S. wrote:

/usr/lib/ruby/gems/1.8/gems/rails-1.0.0/lib/fcgi_handler.rb:22:in
public/dispatch.fcgi:24
killed by this error

Something is sending your FCGI procress a signal which there is no handler
for.

How should you debug those things? I have experience with Unix and
programming but I’ve never bumped into this kind of errors…