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

HTTP Error 503.0 - Server has been shutdown The service is unavailable. Most likely causes: An invalid identity in the application pool could cause this error. The application pool is no longer running because of configuration or reaching application failure limits. The concurrent application request limit was reached. #41771

Closed
1 task done
smilingdassie opened this issue May 20, 2022 · 4 comments
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue.

Comments

@smilingdassie
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

I am hosting an asp.net core website on IIS having following recommended steps
It starts up fine and displays a list of inventory in an html table (jquery datatables)
being pulled from SQL server database and using Entity Framework. All good
BUT if I then refresh the same page once or twice or click the button to fetch the data again
"Service unavailable. 503.0. Server was shut down"
I have produced all the logs and none of them give an error besides a request and 503 response.
If I test using the kestrel URL I cannot reproduce the bug - so I don't think it's a code error.
Any ideas? Am I configuring something wrong? Where to look for answers?
Website in question is : https://stokseek.colms.net/
Thanks for any help!

Expected Behavior

I should be able to refresh the page as often as I want to without the service being shut down
In Kestrel on the server it all works fine
In IIS it breaks after a couple of refreshes

Steps To Reproduce

No response

Exceptions (if any)

No exceptions besides
"The service is unavailable."
"HTTP Error 503.0 - Server has been shutdown
The service is unavailable.

Most likely causes:
An invalid identity in the application pool could cause this error.
The application pool is no longer running because of configuration or reaching application failure limits.
The concurrent application request limit was reached."

.NET Version

.NET CORE 6.0

Anything else?

https://stokseek.colms.net/

@adityamandaleeka
Copy link
Member

Triage: That error message might have occurred for a number of reasons. Can you try the steps in https://docs.microsoft.com/en-us/aspnet/core/test/troubleshoot-azure-iis?view=aspnetcore-6.0#troubleshoot-on-iis to get more information?

@adityamandaleeka adityamandaleeka added the Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. label May 20, 2022
@ghost
Copy link

ghost commented May 20, 2022

Hi @smilingdassie. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

@ghost
Copy link

ghost commented May 24, 2022

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.

@ghost
Copy link

ghost commented May 30, 2022

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.

@ghost ghost closed this as completed Jun 2, 2022
@dotnet dotnet locked as resolved and limited conversation to collaborators Jul 2, 2022
@amcasey amcasey added area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions and removed area-runtime labels Aug 25, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue.
Projects
None yet
Development

No branches or pull requests

4 participants