1

At unexpected moments, we find this message in our Sitecore log: Hosting Environment Stop Requested : immediate=False

What is the best way to find out why this is happening?

It would be very useful if this log message was accompanied by the reason for the "request", but unfortunately it isn't. (And in our case, I think there's nothing going on with idle timeouts or changes in the file system.)

2
  • Is this related to IIS application pool recycling/shutting down? Oct 21, 2022 at 12:31
  • @MichaelWest, I don't think it is. We're hosting our platform as an App Service in Azure and we have set "Always on". Also, we're using the KeepAlive task just to be sure... That's why it would be so useful to see the reason for a "stop request". Currently, we can only guess.
    – Peter M.
    Oct 21, 2022 at 12:34

1 Answer 1

1

This error message is being generated by the ShutdownMonitor which is the manager that listens for Web App shutdown commands. When the webapp receives an instruction for shutting down, this monitor fires the Stop() method, which writes this error message.

Essentially, what's happening is that the Azure WebApp Service is attempting to do something that is about to cause the web application to recycle. As a result, this stop method is going to interrupt any indexing that is going on.

An Azure Webapp service can recycle for any number of reasons, some common ones are as follows:

  1. WebApp Service Host is being rebooted by Microsoft for Updates
  2. Enough Application Errors bubbled to the top of the WebApp stack to cause the AppService to recycle (this is the most common reason for WebApp reboots)
  3. A deployment occurred which will also recycle the AppService.

The indexing process can not ignore this request, because there are clean up actions that have to quickly be taken care of before the WebApp Service is rebooted. So the process ends all indexes, to allow for a safe WebApp Service reboot.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.