For a client we’re running on an Umbraco 16 website on Umbraco Cloud. Last Tuesday we went live on production and yesterday evening our Umbraco instance restarted (question is why, but we’ve asked Umbraco Support to investigate that).
After the restart, the following error started flooding into our logs: System.IO.IOException: The process cannot access the file 'C:\\local\\Temp\\ExamineIndexes\\{instanceid}\\DeliveryApiContentIndex\\_207.fdt' because it is being used by another process.
Does anyone know why this would happen? Is it maybe because of the fact that the delivery api was rebuilding during the restart of the Umbraco environment or it is maybe something else?
Most importantly, does anyone know how we can prevent this from happening again?
A manual restart fixed the issue, but that’s not something that is a valid ‘solution’ for this problem. We would really like to prevent this from happening again.
These types of issues can occur for many reasons, unfortunately. To start I would do a health check on the site to ensure it doesn’t show any concerns (under Settings)
I assume if Umbraco support are on the case they would have had the most common settings enabled by default including all updates.
Is it maybe because of the fact that the delivery api was rebuilding during the restart of the Umbraco environment or it is maybe something else?
I do recall reading a while ago on Umbraco Cloud, this storage does take a while and can be recreated or locked during app restarts or deployments but again i would have thought this may have been listed in the logs.
You could try and rebuild the indexes (assuming you have no other custom logic surrounding this area) but unless something is highlighted in the logs and/or server logs it could be difficult to narrow down.