Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

https://dotneteng-status.azurewebsites.net is offline #5297

Closed
3 tasks
riarenas opened this issue Mar 24, 2025 · 5 comments
Closed
3 tasks

https://dotneteng-status.azurewebsites.net is offline #5297

riarenas opened this issue Mar 24, 2025 · 5 comments

Comments

@riarenas
Copy link
Member

https://dotneteng-status.azurewebsites.net is offline. Please investigate

Image

This is the resource group where this infra is located

Release Note Category

  • Feature changes/additions
  • Bug fixes
  • Internal Infrastructure Improvements

Release Note Description

@dougbu
Copy link
Member

dougbu commented Mar 24, 2025

might have same root cause as #4918 (he says hopefully)

@garath
Copy link
Member

garath commented Mar 24, 2025

might have same root cause as #4918 (he says hopefully)

I think this is a reasonable hope! But alas the root cause remains unknown.

@garath
Copy link
Member

garath commented Mar 25, 2025

And, speak of the devil, the Staging instance just went down.

@meghnave meghnave self-assigned this Mar 25, 2025
@meghnave
Copy link

Here's what I've found so far -

  1. The last deployment for both environments match with the times the errors started in each, so it looks related. And this seems unlike the flakiness that happens in that all requests since the deployments have been 503s.
  1. I'm seeing MI errors in staging that are causing the app to then not be able to access settings.json. I don't see a corresponding error in prod though.

Image

There's a few things to figure out here now - if switching deployments slots will work, if something about an MI has changed, figuring out somehow what exactly is failing.. to find the actual root cause but just wanted to post this as an update/notes.

@meghnave
Copy link

Redeployment in both environments worked for this - updated documentation to try redeploying in case of issues and have linked a created issue here that can help debugging in a small but meaningful way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants