Assuming the logging is set to information, have a look to see if there was a "Shutting Down" event logged. I've had the same issue on V8 sites where something has made the site think it's shutting down according to the logs. This results in examine manager shutting down and all the indexs becoming unavailable
I'm seeing the same thing, also on a v9 site in an Azure App Service. Examine shuts down and then you can't do any searches until you restart the app service.
Are you just restarting the app as part of your deployment process to get around this?
I still see it occasionally on some v9 sites (hosted in Azure) and we still just restart to fix it as needed.
However, it looks like it may of been fixed in the later versions. I haven't notice it after upgrading to v10 so my thought is that some of the other hosting enhancements in v10 may of addressed this issue.
Umbraco 9 on Azure throws Examine error: "this IndexWriter is closed"
Hi,
We're running a site in Azure and now we want to make use of Examine for searching items.
Following the documentation and put these settings in our appsettings.json file, see below:
So far so good.
After deploying to Azure we got an error on the Examine section:
When we take a look at our logs we see the following error:
We don't use loadbalancing and we have only 1 appdomain:
Does anyone know what's going on?
Hopefully someone can help us out :-)
Thanks in advance!
Kind regards,
Sander vd Pas iO
If you restart the site does it start working?
Assuming the logging is set to information, have a look to see if there was a "Shutting Down" event logged. I've had the same issue on V8 sites where something has made the site think it's shutting down according to the logs. This results in examine manager shutting down and all the indexs becoming unavailable
Hi Nik,
Thanks for your response.
After a restart it seems to work, but after a new deploy it throws the same error.
I can found in the logs several items with "Shutting down":
Should we restart the app every time after a deploy or is there another way to fix this?
Grtz, Sander
Were you able to figure anything out with this?
I'm seeing the same thing, also on a v9 site in an Azure App Service. Examine shuts down and then you can't do any searches until you restart the app service.
Are you just restarting the app as part of your deployment process to get around this?
Hi Kevin,
We didn't found a solution right now and the restart is not part of our deployment process yet. We still do this manually :-(
We're still in contact with Umbraco to found a solution.
We just encountered this exact error today and an app restart solved it.
Has Umbraco provided a solution or are people simply performing manual app restarts after each deployment?
I still see it occasionally on some v9 sites (hosted in Azure) and we still just restart to fix it as needed.
However, it looks like it may of been fixed in the later versions. I haven't notice it after upgrading to v10 so my thought is that some of the other hosting enhancements in v10 may of addressed this issue.
is working on a reply...