L
Lachlann562
We have started encountering this error more frequently in our web service, we have noticed it is happening approximately 20 seconds after the recycle begins. In the application log we aren't seeing any major time gaps that would indicate the application is 'busy'. When this happens combined with another condition (file in use by another process) its causing the application to create a 0 byte file because IIS is terminating the 'bad' process before it manages to flush to the file which in turn is causing the next instance of the worker process to crash for some requests.
Our ping intervals are configured to the default (every 30 sec, 90 sec timeout) and the startup time is more than sufficient to support the process starting (we tried setting it to 30 minutes) but we continue to experience this issue. We don't know how to investigate what is causing it to go unhealthy as we don't see any red alerts in our logs to indicate major latency during the start.
I found some references to this error:
Event ID 5011 — IIS Application Pool Availability
but then there is a link to an article on how to debug it but that link is broken.
http://go.microsoft.com/fwlink/?linkid=103462
Any help would be appreciated, this has caused 2 outages for a major customer and there have been no environment/application configuration changes we are aware of and the service has been running pretty happily for over 5 months but has now had 2 failures in 2 days.
We are working to eliminate the 0 byte file issue, but we want to understand why IIS thinks its bad and terminating the process, especially since we've configured the timeouts large enough.
Continue reading...
Our ping intervals are configured to the default (every 30 sec, 90 sec timeout) and the startup time is more than sufficient to support the process starting (we tried setting it to 30 minutes) but we continue to experience this issue. We don't know how to investigate what is causing it to go unhealthy as we don't see any red alerts in our logs to indicate major latency during the start.
I found some references to this error:
Event ID 5011 — IIS Application Pool Availability
but then there is a link to an article on how to debug it but that link is broken.
http://go.microsoft.com/fwlink/?linkid=103462
Any help would be appreciated, this has caused 2 outages for a major customer and there have been no environment/application configuration changes we are aware of and the service has been running pretty happily for over 5 months but has now had 2 failures in 2 days.
We are working to eliminate the 0 byte file issue, but we want to understand why IIS thinks its bad and terminating the process, especially since we've configured the timeouts large enough.
Continue reading...