IIS 7 and Above
Many php-cgi.exe processes
Last post Dec 19, 2014 05:10 AM by RobJansen
Dec 17, 2014 03:10 PM|RobJansen|LINK
Since a day or 2, my webserver running Windows Server 2012 R2 with IIS 8.5 spawns a large amount of php-cgi.exe processes.
The PHP version is 5.6.3 and has been updated since its release on windows.php.net and working great, until ~2 days ago.
Where it used to spawn about 5~6 of these processes before, it now opens 200+ sometimes and makes my opening a webpage on my server slow and sometimes even blocking access to RDP.
When using ''iisreset /restart'', the processes disappear, but not for long, it graduatly builds up again.
Not always will the webserver respond slow.
I have the settings at the default settings in the FastCGI Settings.
0 Max Instances, and 10000 of Instance Max. Requests (10000 for recycle also)
But interestingly these settings haven't been changed at all. They were the same before the problem started happening.
I have tried to lower the Instance Max. Requests and increasing the Max. Instances (but resulted in that the website sometimes stops responding at all, not even an HTTP error but just a time-out).
It isn't the PHP version itself, since I have installed via backup 5.5 and 5.4, and with them it also happens.
Is there some other settings that is causing it?
I don't want to do a iisreset /restart every 6 hours or so (have scheduled it for 01:00 each day) or reinstall the machine, since it means my website is offline for at least a day.
Could anyone help me?
If you need further information, please tell what you need.
Dec 18, 2014 07:13 AM|Pengzhen Song - MSFT|LINK
Please refer to the document which might help you
#Configure PHP Process Recycling Behavior
Dec 19, 2014 05:10 AM|RobJansen|LINK
Thanks, but I have already tried it.
It could also the a bug in PHP, since 5.6.4 has been released, I have just upgraded to it, and it seems to be working as it should before.
But I will keep an eye on it, and if it stay's good, you (or if I) can mark this as the answer as a faulty PHP 5.6.3 and you need to upgrade to 5.6.4.
It remains stable, so confirmed that this is a bug in PHP 5.6.3, I recommend upgrading to 5.6.4.