IIS7 -FastCGI -PHP White Screen of Death

gusus — Sat, 07 Mar 2009 04:59:00 GMT

I am having an issue with IIS7 and PHP relating to clients receiving the white screen of death (blank page) after 90 seconds of processing. Standard php processing works fine.

The following are set in php.ini:

max_execution_time = 180
max_input_time = 180
memory_limit = 128M

In the FastCGI configuration on IIS I have the following:

ActivityTimeout 900
IdleTimeout 300
RequestTimeout 500

I have a simple page that runs through loop and sleeps every 15 seconds. If I set the max_execution_time to 30 seconds, I get the php execution time exceeded error as I should with two entries in the page. If I manually set_time_limit(0), it gives the white page of death. I have set php logging and nothing appears in the log. I intentionally put a syntax error to make sure and the syntax error was logged. In addition, I can set the ActivityTimeout to 10 and IIS gives me a 500 error telling me that the FastCGI process exceeded the configuration activity timeout.

The weird thing is the Failed Request Tracking show that the time taken was 30592 msec with a status of 200 (I assume success). However, the last entry in the request trace is "FASTCGI_WAITING_FOR_RESPONSE"...

Any ideas???

FastCGI Maximum ActivityTimeout

Gengar003 — Mon, 24 Nov 2008 18:14:17 GMT

Hello... on my IIS7 server, I have php implemented via fastCGI.

(Windows Server 2008 build 6001, IIS7 version 7.0.6)

Some of my scripts I need to run for extended periods of time, up to several hours.

While PHP itself has no qualms about this, IIS7's FastCGI "ActivityTimeout" setting refuses to allow itself to be set to more than 3600 seconds (1 hour).

This is inadequate. Using the management console, I cannot set the value to more than 3600, and when I edit the .xml file directly and restart the server, the .xml file is changed to contain 3600, instead of the value I chose.

What can I do to allow a php script to run for more than 3600 seconds (FastCGI's maximum ActivityTimeout)?

A good deal of the script in question's time is spent sleep()ing - is it possible to have FastCGI not count that time toward the activity timeout? Or is there a way to send IIS7 some "activity" from a php script, and thus re-set the timer?

Are there any updates or workarounds that will solve this for me?

Thanks in advance

Search results matching tag 'activitytimeout'

IIS7 -FastCGI -PHP White Screen of Death

FastCGI Maximum ActivityTimeout