#44047 [Com]: IIS Worker Process stopped working
ID: 44047 Comment by: satan at dclxvi dot nl Reported By: matthew dot horner at redprairie dot com Status: Open Bug Type: IIS related Operating System: Windows Vista PHP Version: 5.2.5 New Comment: to be clear, these are my settings: Recycle time is set to the default every 1740 minutes. Idle timeout is set to '0' Disable Overlapped Recycle is set to 'True' never had the error again... no horrible workarround whatsoever.. it's just that IIS7 is defaultly configured to run MS stuff like ASP.NET etc.. Previous Comments: ---- [2008-03-06 10:13:01] satan at dclxvi dot nl Also, I found out the solution that it won't error on recycle... go to the advanced settings of the appPool you are using and set "Disable Overlapped Recycle" to "True". PHP5 can't seam to run multiple instances so it errors out when it starts a new instance before it recycles the old.. And again with the idle timeout set to "0", it will still recycle.. -------------------- [2008-03-06 09:39:53] satan at dclxvi dot nl it will still recycle if you set it to 0, it just won't time out.. on higher traffic servers it will will never timeout and there's no problem there, is there? the recycling is another setting.. besides, this has little or nothing to do with php, as it also occurs after running asp.. [2008-03-04 15:25:29] nick at databasedevelopments dot com Same issue here on Vista Ultimate and PHP5.2.5 with IIS7 [2008-03-04 00:57:46] nonya at spam dot this Yea, that is a horrible idea. You are literally telling IIS to never clean it's caches or do garbage collection on the AppPools. I am sure that there are more critical consequences on high-volume web servers if you decide to do this. PHP just fix it [2008-03-03 13:52:11] matthew dot horner at redprairie dot com Setting the recycle time to 0 would not be considered a solution, but rather a workaround. The solution to the problem would require a code change. That change would resolve the issue, so that the workaround would not have to be applied. This change to standard code would also avoid changing standard configuration of the IIS server for _every_ instance that has a PHP 5 installation. The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/44047 -- Edit this bug report at http://bugs.php.net/?id=44047&edit=1
#44047 [Com]: IIS Worker Process stopped working
ID: 44047 Comment by: satan at dclxvi dot nl Reported By: matthew dot horner at redprairie dot com Status: Open Bug Type: IIS related Operating System: Windows Vista PHP Version: 5.2.5 New Comment: Also, I found out the solution that it won't error on recycle... go to the advanced settings of the appPool you are using and set "Disable Overlapped Recycle" to "True". PHP5 can't seam to run multiple instances so it errors out when it starts a new instance before it recycles the old.. And again with the idle timeout set to "0", it will still recycle.. Previous Comments: -------- [2008-03-06 09:39:53] satan at dclxvi dot nl it will still recycle if you set it to 0, it just won't time out.. on higher traffic servers it will will never timeout and there's no problem there, is there? the recycling is another setting.. besides, this has little or nothing to do with php, as it also occurs after running asp.. [2008-03-04 15:25:29] nick at databasedevelopments dot com Same issue here on Vista Ultimate and PHP5.2.5 with IIS7 [2008-03-04 00:57:46] nonya at spam dot this Yea, that is a horrible idea. You are literally telling IIS to never clean it's caches or do garbage collection on the AppPools. I am sure that there are more critical consequences on high-volume web servers if you decide to do this. PHP just fix it [2008-03-03 13:52:11] matthew dot horner at redprairie dot com Setting the recycle time to 0 would not be considered a solution, but rather a workaround. The solution to the problem would require a code change. That change would resolve the issue, so that the workaround would not have to be applied. This change to standard code would also avoid changing standard configuration of the IIS server for _every_ instance that has a PHP 5 installation. ---------------- [2008-03-02 12:27:34] satan at dclxvi dot nl lol, your test is the solution... where you set it idle time out to 1 to test it earlier, just set it to '0'. it will error out once more and the next time it starts it will stay on.. there is no problem with leaving it on.. The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/44047 -- Edit this bug report at http://bugs.php.net/?id=44047&edit=1
#44047 [Com]: IIS Worker Process stopped working
ID: 44047 Comment by: satan at dclxvi dot nl Reported By: matthew dot horner at redprairie dot com Status: Open Bug Type: IIS related Operating System: Windows Vista PHP Version: 5.2.5 New Comment: it will still recycle if you set it to 0, it just won't time out.. on higher traffic servers it will will never timeout and there's no problem there, is there? the recycling is another setting.. besides, this has little or nothing to do with php, as it also occurs after running asp.. Previous Comments: [2008-03-04 15:25:29] nick at databasedevelopments dot com Same issue here on Vista Ultimate and PHP5.2.5 with IIS7 [2008-03-04 00:57:46] nonya at spam dot this Yea, that is a horrible idea. You are literally telling IIS to never clean it's caches or do garbage collection on the AppPools. I am sure that there are more critical consequences on high-volume web servers if you decide to do this. PHP just fix it [2008-03-03 13:52:11] matthew dot horner at redprairie dot com Setting the recycle time to 0 would not be considered a solution, but rather a workaround. The solution to the problem would require a code change. That change would resolve the issue, so that the workaround would not have to be applied. This change to standard code would also avoid changing standard configuration of the IIS server for _every_ instance that has a PHP 5 installation. [2008-03-02 12:27:34] satan at dclxvi dot nl lol, your test is the solution... where you set it idle time out to 1 to test it earlier, just set it to '0'. it will error out once more and the next time it starts it will stay on.. there is no problem with leaving it on.. [2008-02-29 04:37:22] nonya at spam dot this To elaborate on Matthew, (Every PHP5\Vista\IIS7 machine I have every worked on does this; 20+ machines) The same error can be achieved back-to-back simply by running any PHP, which in turn will add 1 active application to the DefaultAppPool. This is visible in the IIS7 Manager. You can select the DefaultAppPool and click "Recycle...", wait 3-5 secs (because WerFault.exe kicks in, Windows Error Reporting Service) and you have a "IIS Worker Process has failed" message with the event in the windows event log the way Matt described which says the fault came from c:\windows\system32\ntdll.dll If the PHP dev guys are trying to recreate this issue, you need to be using Latest PHP5/IIS7/ISAPI-Configuration/Vista This has been going on since Vista RC1. Everyone who is not getting this error may not be complaining because the error doesn't seem to do major damage. The closest thing to a resolution I have seen since the release of Vista is to just adjust the timing of the automated recycle cycle. Since the error is only occurring during recycling, they have been scheduling 1 recycle per day, hence 1 crash per day. There are many, many, many, MANY forums and support threads with people having the same problem, they just aren't posting here. Here are a few: forums.techarena.in/showthread.php?t=686723 www.developersdex.com/asp/message.asp?p=592&r=6057007 www.issociate.de/board/post/468636/IIS_+_PHP_--_Worker_Process_alert_&_w3wp.exe_crash?.html forums.techarena.in/showthread.php?t=821723 groups.google.com/group/comp.lang.php/browse_thread/thread/93aef1ff2f0ba3b0 www.thescripts.com/forum/thread742344.html The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/44047 -- Edit this bug report at http://bugs.php.net/?id=44047&edit=1
#44047 [Com]: IIS Worker Process stopped working
ID: 44047 Comment by: satan at dclxvi dot nl Reported By: matthew dot horner at redprairie dot com Status: Open Bug Type: IIS related Operating System: Windows Vista PHP Version: 5.2.5 New Comment: lol, your test is the solution... where you set it idle time out to 1 to test it earlier, just set it to '0'. it will error out once more and the next time it starts it will stay on.. there is no problem with leaving it on.. Previous Comments: [2008-02-29 04:37:22] nonya at spam dot this To elaborate on Matthew, (Every PHP5\Vista\IIS7 machine I have every worked on does this; 20+ machines) The same error can be achieved back-to-back simply by running any PHP, which in turn will add 1 active application to the DefaultAppPool. This is visible in the IIS7 Manager. You can select the DefaultAppPool and click "Recycle...", wait 3-5 secs (because WerFault.exe kicks in, Windows Error Reporting Service) and you have a "IIS Worker Process has failed" message with the event in the windows event log the way Matt described which says the fault came from c:\windows\system32\ntdll.dll If the PHP dev guys are trying to recreate this issue, you need to be using Latest PHP5/IIS7/ISAPI-Configuration/Vista This has been going on since Vista RC1. Everyone who is not getting this error may not be complaining because the error doesn't seem to do major damage. The closest thing to a resolution I have seen since the release of Vista is to just adjust the timing of the automated recycle cycle. Since the error is only occurring during recycling, they have been scheduling 1 recycle per day, hence 1 crash per day. There are many, many, many, MANY forums and support threads with people having the same problem, they just aren't posting here. Here are a few: forums.techarena.in/showthread.php?t=686723 www.developersdex.com/asp/message.asp?p=592&r=6057007 www.issociate.de/board/post/468636/IIS_+_PHP_--_Worker_Process_alert_&_w3wp.exe_crash?.html forums.techarena.in/showthread.php?t=821723 groups.google.com/group/comp.lang.php/browse_thread/thread/93aef1ff2f0ba3b0 www.thescripts.com/forum/thread742344.html [2008-02-05 16:17:54] matthew dot horner at redprairie dot com I removed all extensions and re-tested with the same results. [2008-02-05 15:01:16] [EMAIL PROTECTED] Do you have any extensions loaded via php.ini or this is purely whats statically built into PHP? If you do have extensions can you disable them all and see if you can reproduce the problem. [2008-02-05 14:17:23] matthew dot horner at redprairie dot com I have tested with the latest and the crash is still occurring with the exact same stack trace. The build date of the current installation is Feb 5 2008 08:04:21. [2008-02-05 05:07:30] [EMAIL PROTECTED] Please try using this CVS snapshot: http://snaps.php.net/php5.2-latest.tar.gz For Windows (zip): http://snaps.php.net/win32/php5.2-win32-latest.zip For Windows (installer): http://snaps.php.net/win32/php5.2-win32-installer-latest.msi The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/44047 -- Edit this bug report at http://bugs.php.net/?id=44047&edit=1
