azure-functions-host: AI (Internal): [Azure-Core] ERROR: Exception in Command Processing for EventSource Azure-Core: An instance of EventSource with Guid xxx already exists
We have multiple function apps that all started receiving this error in the logs starting around 1:00PM Central Time on 5/17.
AI (Internal): [Azure-Core] ERROR: Exception in Command Processing for EventSource Azure-Core: An instance of EventSource with Guid 44cbc7c6-6776-5f3c-36c1-75cd3ef19ea9 already exists.
At this point I am unsure if this error is negatively impacting the functions in any way, but I am investigating further.
We use functions quite a bit, and about half of them starting reporting this error at this time. Anecdotally it seems to be affecting our longer-running functions and not are shorter-running functions. This is affecting functions of multiple types: queue-triggered and timer-triggered functions, and http-triggered functions. We are not creating a new TelemetryClient anywhere in our code (https://github.com/microsoft/ApplicationInsights-dotnet/issues/1693) nor are we on a 2.x version of the function host (https://github.com/microsoft/ApplicationInsights-dotnet/issues/1029). We are not even explicitly installing Microsoft.Azure.WebJobs.Logging.ApplicationInsights in our .csproj files. The time these issues started does not line up with any deployment on our side.
- Timestamp: Started around 1:00PM Central Time on 5/17
- Function App version: ~3
- Function App name: multiple
- Region: US North Central
- Programming Language: dotnet core 3.1
- Consumption plan
Here are a few examples from Application Insights logs:
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 3
- Comments: 41 (9 by maintainers)
I just want to point out that my error is exactly the same as @MikePennington and @zhenyuan0502 - Even the EventSource GUID is the same. I’m not sure how that’s possible.
Hi @MikePennington, the issue was with the Azure.Core nuget package. Azure.Storage.Blobs and Azure.Identity internally depends on Azure.Core. Update Azure.Storage.Blobs and Azure.Identity with the latest version.
We are seeing this issue as well, including the exact same EventSource GUID in the error message. Like everyone else that has posted, we are not creating a TelemetryClient or TelemetryConfiguration. We are using an injected ILogger. Instances date back to 5/21 in multiple subscriptions and function application instances.
Sample recent instance: Invocation ID: ae22ece0-0b6c-4668-8544-96fbed1facb3 Timestamp: 2021-06-10T15:25:57.150962Z Function App version: ~3 Region: US Central Programming Language: dotnet core 3.1 Consumption plan
These are timer-triggered function apps.
Package references:
TL;DR: Me too!
Thank you for the details @ryanbowden , We will check the logs to understand the error and revert back the findings