Open videokojot opened 4 years ago
we are using .NET Core 2.2
What exact version of the runtime? This looks very similar to https://github.com/dotnet/corefx/issues/33844, which was fixed in .NET Core 2.2.1.
@stephentoub we are using
FROM mcr.microsoft.com/dotnet/core/sdk:2.2 AS build-restore
for build
and
FROM mcr.microsoft.com/dotnet/core/aspnet:2.2 AS runtime-image
for runtime
it seem that they are currently using 2.2.402 (sdk) and 2.2.7 (runtime img) according their docker files: https://github.com/dotnet/dotnet-docker/blob/master/2.2/sdk/stretch/amd64/Dockerfile and https://github.com/dotnet/dotnet-docker/blob/master/2.2/aspnet/stretch-slim/amd64/Dockerfile
We have run docker prune
only few days ago, so it is not possible, that there would be older version of 2.2. cached...
Thank you for looking into this.
Problem: We are running into unsolvable problem, our application is taken down by this exception (and thats everything we were able to log from it in
UnhandledException
event) and we do not know how to localize it. This is from our logs:Details: Some (maybe) relevant information:
mcr.microsoft.com/dotnet/core/aspnet:2.2
) managed by kubernetesreloadOnChange: true
for appsetting.jsonAlso if we run:
kubectl logs ${pod} --previous
we can see this:The result from:
kubectl logs $(kubectl get pods --selector=app=dataconnector -o=name) --previous
is the same as the logged exception except there is lineAborted (core dumped)
What we tried (nothing helped):
DOTNET_USE_POLLING_FILE_WATCHER=true
to our DockerfileI am not sure if it is belong here, but FileSystemWatcher.cs is from here, but it can be in coreclr (because of CancelationTokeSource.cs) or in apsnetcore...
Are you having any thoughts? Currently this is blocking us moving forward, as all of our microservice are dying unexpectedly...