Re[2]: FastCGI + Apache2 + php4fcgi

Hello Tom,

1) If it's because mod_fastcgi times out the php job before
it's done, and considers it dead, then you can probably
try two things:
  a. make your php finish in a shorter time, or
  b. change some mod_fastcgi parameters and rebuild it.
     e.g. you can try 60 with this one:

/*
 * The number of seconds an application has to have run without exiting
 * for the application to be considered no longer broken.
 */
#define RUNTIME_SUCCESS_INTERVAL 30  

-- 
Best regards,
Jack

Tuesday, September 27, 2005, 5:52:19 AM, you wrote:

TM> Hi Jack,

TM> Correct

TM> 1) The php 'crashes' because fastcgi is killing the process.
TM> Is there a way that fastcgi checks the process first (to see if its busy)
TM> before killing it :) 

TM> 2) Has no implication on my problem, my processes are running fine (i think
TM> ;-) My fastcgi is working fine all the time (just execpt when fastcgi is
TM> killing things to free resources)

TM> Best Regards,
TM> Tom

TM> -----Oorspronkelijk bericht-----
TM> Van: Jack [mailto:[email protected]] 
TM> Verzonden: maandag 26 september 2005 21:57
TM> Aan: Tom Myny
TM> CC: fastcgi-developers-xGejAJT2w6xVgU18Zptdi0EOCMrvLtNR@public.gmane.org
TM> Onderwerp: Re: [FASTCGI] FastCGI + Apache2 + php4fcgi

TM> Hello Tom,

TM> This is the reply of my question from jancha <[email protected]>
TM> It might have something to do with the problem you are having.

TM> ------------------- cut --------------------
TM> 1) "Internal Server Error" - you get such error displayed if the underlying
TM> program crashes for whatever reason.

TM> 2) Typically, if there are more than 3 crashes in 30secs, FastCGI puts a
TM> 600second delay before launching a new process. Theoretically, you can patch

TM> the fastcgi apache module. No other workaround for this.
TM> ------------------- cut --------------------

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/