search

dotnet / aspire

An opinionated, cloud ready stack for building observable, production ready, distributed applications in .NET
https://learn.microsoft.com/dotnet/aspire
MIT License
3.65k stars 413 forks source link

`eventhubs-emulator` crashes on linux/helix #5371

Closed radical closed 1 day ago

radical commented 4 weeks ago

Starting mcr.microsoft.com/azure-messaging/eventhubs-emulator:latest on linux/helix fails. It fails on codespaces too.

fail: a.a.aaW[0]
      Emulator Start up probe Unsuccessful. MetadataStore Health status: Unhealthy BlobStore Health status: Unhealthy
fail: Microsoft.Extensions.Diagnostics.HealthChecks.DefaultHealthCheckService[103]
      Health check Emulator Health Check with status Unhealthy completed after 26546.109ms with message 'Emulator Start up probe Unsuccessful. MetadataStore Health status: Unhealthy BlobStore Health status: Unhealthy'
Retry 1 encountered an exception: Emulator Health Check failed.. Waiting 00:00:00 before next retry.
fail: a.a.aaW[0]
      Emulator Start up probe Unsuccessful. MetadataStore Health status: Unhealthy BlobStore Health status: Unhealthy
fail: Microsoft.Extensions.Diagnostics.HealthChecks.DefaultHealthCheckService[103]
      Health check Emulator Health Check with status Unhealthy completed after 27109.5539ms with message 'Emulator Start up probe Unsuccessful. MetadataStore Health status: Unhealthy BlobStore Health status: Unhealthy'
Retry 2 encountered an exception: Emulator Health Check failed.. Waiting 00:00:00 before next retry.
fail: a.a.aaW[0]
      Emulator Start up probe Unsuccessful. MetadataStore Health status: Unhealthy BlobStore Health status: Unhealthy
fail: Microsoft.Extensions.Diagnostics.HealthChecks.DefaultHealthCheckService[103]
      Health check Emulator Health Check with status Unhealthy completed after 26307.1877ms with message 'Emulator Start up probe Unsuccessful. MetadataStore Health status: Unhealthy BlobStore Health status: Unhealthy'
An error occurred: Emulator Health Check failed.

This needs to be investigated to see if it something in our setup or a bug with the docker image. Example of a failing build.

davidfowl commented 4 days ago

This is fixed now.

radical commented 1 day ago

This is fixed now.

Confirmed. Closing the issue.