Azure的网站/应用服务无法解释的502错误 [英] Azure WebSites / App Service Unexplained 502 errors
问题描述
我们有一个无状态（共享天青Redis的缓存）Web应用程序，我们希望通过Azure的自动缩放服务自动缩放。当我激活自动向外扩展，甚至当我启动3个固定情况下的Web应用程序，我得到相反的效果：响应时间成倍增加或我得到HTTP 502错误
We have a stateless (with shared Azure Redis Cache) WebApp that we would like to automatically scale via the Azure auto-scale service. When I activate the auto-scale-out, or even when I activate 3 fixed instances for the WebApp, I get the opposite effect: response times increase exponentially or I get Http 502 errors.
这发生了，我是否使用我们配置的流量管理器URL（对于单实例月工作的罚款）或本机URL（.azurewebsites.net）。难道这有什么做的流量管理器？如果是这样，我在哪里可以找到这种组合方式（已搜索）？我如何正确地利用汽车大规模交通管理器故障切换/ PERF？我试图把流量管理器在故障切换和表现模式，没有明显的影响。我可以通过私人渠道gladdly提供链接。
This happens whether I use our configured traffic manager url (which worked fine for months with single instances) or the native url (.azurewebsites.net). Could this have something to do with the traffic manager? If so, where can I find info on this combination (having searched)? And how do I properly leverage auto-scale with traffic-manager failovers/perf? I have tried putting the traffic manager in both failover and performance mode with no evident effect. I can gladdly provide links via private channels.
更新：的：我们纷纷转载现在的情况了周围的其他方式：在那里我们得到了频繁的5XX错误的帐户，我们已经删除了所有负载均衡服务器（每个应用程序现在只有一台服务器），问题就消失了。而且，在其他帐户，我们开始在3个服务器以平衡（无流量管理器配置），并很快得到了频繁的502和503显示瓶塞。
UPDATE: We have reproduced the situation now the "other way around": On the account where we were getting the frequent 5XX errors, we have removed all load balanced servers (only one server per app now) and the problem disappeared. And, on the other account, we started to balance across 3 servers (no traffic manager configured) and soon got the frequent 502 and 503 show stoppers.
相关这里假设：的https： //ask.auth0.com/t/health-checks-response-with-500-http-status/446/8
可能的原因是什么？任何考生？
Possibly the cause? Any takers?
更新的
UPDATE
恢复所有的WebApp单实例，以排除任何关系，负载均衡后，东西跑细了一段时间。然后相同的502的行为在所有服务器再现一段约在04.Jan.16 15分钟，然后又消失了。
After reverting all WebApps to single instances to rule out any relationship to load balancing, things ran fine for a while. Then the same "502" behavior reappeared across all servers for a period of approx. 15 min on 04.Jan.16 , then disappeared again.
更新的
UPDATE
问题时又出现在上08.Jan.16 12.55 UTC / GMT时间为10分钟，然后几分钟后再次消失了。检查日志文件现在更多的信息。
Problem reoccurred for a period of 10 min at 12.55 UTC/GMT on 08.Jan.16 and then disappeared again after a few min. Checking logfiles now for more info.
更新的
UPDATE
问题时又出现对19.Jan.16期为90分钟，在约11.00 UTC / GMT也.scm。页。这是一个名为dummy1015Web App中的帐户参考客户Web应用程序。 502 - Web服务器，而作为网关或代理服务器时收到了无效的响应。
Problem reoccurred for a period of 90 min at roughly 11.00 UTC/GMT on 19.Jan.16 also on .scm. page. This is the "reference-client" Web App on the account with a Web App named "dummy1015". "502 - Web server received an invalid response while acting as a gateway or proxy server."
推荐答案
我不认为流量管理器是这里的问题。由于流量管理器的工作原理在DNS级别，它不能是你所看到的5XX错误的来源。为了确认，我建议如下：
I don't think Traffic Manager is the issue here. Since Traffic Manager works at the DNS level, it cannot be the source of the 5XX errors you are seeing. To confirm, I suggest the following:
- 检查响应时间增加是从DNS查找或从Web请求来了。
- 介绍流量管理器，同时保持你的单个实例/非负载平衡设置和确认该问题不会再次出现
这将有助于确定问题是否涉及到交通管理器或负载平衡的一些其他方面。
This will help confirm if the issue relates to Traffic Manager or some other aspect of the load-balancing.
问候，
乔纳森Tuliani
项目经理
Azure的网络 - DNS和流量管理器
Jonathan Tuliani Program Manager Azure Networking - DNS and Traffic Manager
这篇关于Azure的网站/应用服务无法解释的502错误的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
