哪些可能会导致“服务不可用503"?错误? [英] What possibilities can cause "Service Unavailable 503" error?
问题描述
我们有一个 ASP.NET MVC 应用程序部署到服务器，但是当对服务器的请求过多时，客户端只会收到503 服务不可用"错误.
但是，如果我将应用程序部署到另一台服务器(较低的硬件配置)，则一切正常，甚至可以很好地处理更多请求.
我的问题是什么可能的配置会导致以前的服务器抛出 503 错误?(这意味着请求没有到达我们的应用程序).
we have a asp.net MVC application deployed to a server, and but when there is too many request to the server, the client will just get a "503 service unavailable" error.
But if I deployed the application to another server ( lower hardware configuration ), everything worked fine, even more requests it can handle well.
My question is what possible configuration can cause the previous server to just throw out a 503 error ? (which means the requests didn't reach our application).
推荐答案
您的网页由应用程序池提供服务.如果您禁用/停止应用程序池，并且任何人尝试浏览该应用程序，您将获得服务不可用.它可能由于多种原因而发生...
Your web pages are served by an application pool. If you disable/stop the application pool, and anyone tries to browse the application, you will get a Service Unavailable. It can happen due to multiple reasons...
您的应用程序可能崩溃了[检查事件查看器，看看是否可以在应用程序/系统日志中找到事件日志]
Your application may have crashed [check the event viewer and see if you can find event logs in your Application/System log]
您的应用程序可能经常崩溃.如果应用程序池在 5 分钟内崩溃 5 次 [检查您的应用程序池设置是否快速失败]，则您的应用程序池已被 IIS 禁用，您最终会收到此消息.
Your application may be crashing very frequently. If an app pool crashes for 5 times in 5 minutes [check your application pool settings for rapid fail], your application pool is disabled by IIS and you will end up getting this message.
无论哪种情况，问题都在于您的工作进程失败，您应该从崩溃的角度对其进行故障排除.
In either case, the issue is that your worker process is failing and you should troubleshoot it from crash perspective.
什么是崩溃(技术上)...在 ASP.NET 中以及要做什么如果发生了怎么办?
这篇关于哪些可能会导致“服务不可用503"?错误?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
