Exception Info: System.AggregateException: One or more errors occurred. The semaphore has been disposed. about applicationinsights-snapshotcollector HOT 13 CLOSED

Sadly, this update caused some apps to fail on start up (FileNotFoundException for System.Text.Encodings.Web). As a rapid mitigation, we are rolling out another update (essentially rolling back to the previous DiagnosticServices site extension). Because that version includes SnapshotCollector 1.3.7.4, that means this issue will re-appear.

Obviously, we'll try and get a fix for the FileNotFoundException and SnapshotCollector 1.3.7.5 deployed safely as soon as we can.

from applicationinsights-snapshotcollector.

This should now be fixed (again!) in DiagnosticServices 3.11.2108.201

from applicationinsights-snapshotcollector.

The roll-out was paused for a week because of a regression in an unrelated payload. That was patched and restarted last week. We're currently holding waiting for confirmation that the patch is good. Assuming no further hold-ups, I expect the roll-out to complete this week. I know it's frustrating -- it's frustrating for me too.
The only workaround I can think of is to disable Snapshot Debugging altogether, but that's a bit drastic.

from applicationinsights-snapshotcollector.

The roll-out has completed (Deployed on 99.55% of all App Services worldwide at time of writing).

To check that you have the latest version, go to the Kudu endpoint "/DiagnosticServices"
e.g. if your site's URL is https://mysite.azurewebsites.net, then go to https://mysite.scm.azurewebsites.net/DiagnosticServices

You should see something like this at the top:
Diagnostic Services Status
✔️ Site Extension, version 3.11.2106.1101, is up to date.
✔️ Application Insights Profiler WebJob, version 2.6.2010.2703, is enabled.
✔️ Application Insights Snapshot Collector, version 1.3.7.5, is installed.

Screenshot below:

You may need to restart your site to pick up the latest version -- or just wait, because if you're experiencing this issue then your app has already shut down and it'll pick up the new version next time it starts.

from applicationinsights-snapshotcollector.

Yup, this is a known issue that was fixed in 1.3.7.5
If you're adding the SnapshotCollector via a nuget, please upgrade to that version.
If this is a "codeless" scenario in Azure App Service, we have an update in progress to upgrade everyone to 1.3.7.5.

from applicationinsights-snapshotcollector.

Thank you so very much!

from applicationinsights-snapshotcollector.

@pharring Sorry to address this issue again, but do you have any estimation in when the update is going to be available in codeless scenarios? Or maybe any link to track this situation? Thank you!

from applicationinsights-snapshotcollector.

It's a bit out of my hands. The bits were delivered to Azure App Service "Rapid Update" on June 14th.
I checked on it yesterday and it hadn't hit canary yet so I have pinged my contacts to ask for a status update.

from applicationinsights-snapshotcollector.

I got a status update. Unfortunately, we ran into a planned deployment freeze which runs until July 1st. The roll-out is currently scheduled to begin on July 2nd. However, I note that that's a Friday before the US 4th July holiday, so I have a strong suspicion it'll be deferred again by a few days. I'll update this issue as we learn more.

from applicationinsights-snapshotcollector.

Thank you @pharring for the notice! Just a side comment, It would be great to have a kind of a platform to track the versions in Azure btw 😝

from applicationinsights-snapshotcollector.

July 2nd roll-out has begun and it includes the updated Snapshot Collector 1.3.7.5. Historically, it has taken about 7 days to finish worldwide deployment, starting in canary regions. The 4th July US holiday may add a day or two to that. Also, there are quite a few other bits riding along with this payload, so the risk of stalls and roll-backs is somewhat higher.

from applicationinsights-snapshotcollector.

@pharring thanks for your information! We will keep awaiting for the deploy :)
We are still receiving some e-mails about the crash, is there any temporary solution that you know? Thank you and sorry!

from applicationinsights-snapshotcollector.

We're seeing the exact same problem with the same call stack in a "codeless" Azure App Service scenario. Thanks for confirming it's in the Azure bits and a rollout is pending, and for keeping us updated. I'll subscribe to this issue and continue to watch for further updates on the rollout.

from applicationinsights-snapshotcollector.