Hi,
I''ve downloaded the latest stabil Hieraki. I have ruby 1.8.2
(2004-12-25)
[i686-linux], the latest rails (and gems, too), Apache/1.3.33 (Unix) and
mod_fastcgi/mod_fastcgi-SNAP-0404142202. I''m successfully running Typo
(from SVN) as a FastCGI application.
Hieraki works well with "script/server", and works well as a .cgi
(just
very slow). My problem is, that it''s not working as a fastcgi
application.
Both the .htaccess and dispatch.fcgi files are the same as Typo''s
settings, and same as the original, downloaded version.
The exact problem is, that I get the 500 Application error page. From the
Apache log:
FastCGI: (dynamic) server ".../dispatch.fcgi" has failed to remain
running
for 30 seconds given 3 attempts, its restart interval has been backed off to
600 seconds
When I try to run dispatch.fcgi from the command line, I got no fatal
error, it just says, that has routing problems.
Any ideas, what should I check? I''m not familiar with the FastCGI
architecture, so I don''t know, if I should setup something per
application, or not, etc.
Bye,
Andras
ps: I''ve tried some other Rails applications, too, and - except Typo -
it''s the same problem with FCGI.
What do the other logs say? On 8/10/05, BÁRTHÁZI András <andras-UUlgSIbigNGT9ig0jae3mg@public.gmane.org> wrote:> Hi, > > I''ve downloaded the latest stabil Hieraki. I have ruby 1.8.2 (2004-12-25) > [i686-linux], the latest rails (and gems, too), Apache/1.3.33 (Unix) and > mod_fastcgi/mod_fastcgi-SNAP-0404142202. I''m successfully running Typo > (from SVN) as a FastCGI application. > > Hieraki works well with "script/server", and works well as a .cgi (just > very slow). My problem is, that it''s not working as a fastcgi application. > Both the .htaccess and dispatch.fcgi files are the same as Typo''s > settings, and same as the original, downloaded version. > > The exact problem is, that I get the 500 Application error page. From the > Apache log: > > FastCGI: (dynamic) server ".../dispatch.fcgi" has failed to remain running > for 30 seconds given 3 attempts, its restart interval has been backed off to > 600 seconds > > When I try to run dispatch.fcgi from the command line, I got no fatal > error, it just says, that has routing problems. > > Any ideas, what should I check? I''m not familiar with the FastCGI > architecture, so I don''t know, if I should setup something per > application, or not, etc. > > Bye, > Andras > > ps: I''ve tried some other Rails applications, too, and - except Typo - > it''s the same problem with FCGI. > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >
Hi, Joe Van Dyk wrote:> What do the other logs say?Which logs do you ask for? apache''s error log: FastCGI: comm with (dynamic) server ".../hieraki/public/dispatch.fcgi" aborted: (first read) idle timeout (30 sec) FastCGI: incomplete headers (0 bytes) received from server ".../hieraki/public/dispatch.fcgi" apache''s access log: ... "GET /frontpage/index HTTP/1.1" 500 ... apache''s central log: [warn] FastCGI: (dynamic) server ".../hieraki/public/dispatch.fcgi" has failed to remain running for 30 seconds given 3 attempts, its restart interval has been backed off to 600 seconds no production.log, fastcgi.crash.log not changes (I have one from the previous runs) Bye, Andras
On 10 Aug 2005, at 17:29, BÁRTHÁZI András wrote:> FastCGI: (dynamic) server ".../dispatch.fcgi" has failed to remain > running for 30 seconds given 3 attempts, its restart interval has > been backed off to 600 secondsI''m sorry that I can''t help you more than this (just a newbie atm), but I''ve also had the same problem on OS X.4.x, and the only way I''ve found to overcome it is restarting httpd or Apache. That has solved it for me each time, but not really why ;-) Kind regards, Mats ---- "TextMate, coding with an incredible sense of joy and ease" - www.macromates.com -
Hi Mats,>> FastCGI: (dynamic) server ".../dispatch.fcgi" has failed to remain >> running for 30 seconds given 3 attempts, its restart interval has >> been backed off to 600 seconds > > I''m sorry that I can''t help you more than this (just a newbie atm), but > I''ve also had the same problem on OS X.4.x, and the only way I''ve found > to overcome it is restarting httpd or Apache. That has solved it for me > each time, but not really why ;-)I''ve tried it w/o any effects. :) Bye, Andras
Hi,> Any ideas, what should I check? I''m not familiar with the FastCGI > architecture, so I don''t know, if I should setup something per > application, or not, etc.Hmm. It seems, that when I created production.log manually, it went to OK. Currently it''s running well. Strange. Bye, Andras
On 8/10/05, BÁRTHÁZI András <andras-UUlgSIbigNGT9ig0jae3mg@public.gmane.org> wrote:> Hi, > > > Any ideas, what should I check? I''m not familiar with the FastCGI > > architecture, so I don''t know, if I should setup something per > > application, or not, etc. > > Hmm. It seems, that when I created production.log manually, it went to > OK. Currently it''s running well. Strange.Yes, all the log files need to be writable (which means created) when using fastcgi, apparently.