Closed mike-jewell closed 4 years ago
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
I've been facing the same problem as you do. Recently this problem has ocurred to one of my applications, then I've scaled up the ServicePlan and the application has back to life. Then I scaled it down and it still works. Today I've faced the same problem with other application and I'm still trying to find a way to solve the problem.
I believe this is a duplicate of https://github.com/dotnet/runtime/issues/37664
We have an Azure App Service which has 5 containers running. 3 are web apps, 2 are function apps. Things have been running fine, but we have recently upgraded the nuget and dotnet core containers used on 1 web app and 1 function app. Since then we have started to see this error.
As this is spread over 5 apps and also 5 different solutions I have no idea where to start on a repo to demonstrate this. The functions app has 35 functions mixed between queues, timers and container watches. I cannot configure the json watchwithin the function app as far as I am aware, and I haven't, but I am getting the following from the function app:
The web apps have been deliberately configured with:
.AddJsonFile("appsettings.json", optional: false, reloadOnChange: false)
As we have seen this before about 2 months ago. However I found that I had deployed a web app with
AddRazorRuntimeCompilation();
on which was cxausing the issue.The web app was also reporting the issue against the following stack trace:
Nothing else within the applications hosted on the server utilise filewatchers outside of external dependencies. We upgraded the nuget packages, and have now used the following across the 2 apps:
Beyond what I've provided I have no idea what else I can do to demonstrate the problem.
Configuration
dotnet core 3.1 mcr.microsoft.com/dotnet/core/aspnet:3.1.6-buster-slim mcr.microsoft.com/azure-functions/dotnet:3.0 (just reverted from mcr.microsoft.com/azure-functions/dotnet:3.0-appservice which was also a change to this release)
All docker images use:
ENV DOTNET_USE_POLLING_FILE_WATCHER true
Not sure if that is the correct way of implementing this...
Azure App Service Linux Docker
Regression?
I think its a regression. Prior to the upgrade we were on the 3.1.4 versions of the main microsoft packages. and we were on the 3.1.4 docker image for the web app.
area-System.IO