问题描述
我在 Azure 中将容器部署到我的应用服务时遇到问题.在发布管道中，我看到了以下错误
I am having trouble deploying container to my app service in Azure. In the release pipeline, I saw the following error
[调试][PUT]https://$iagadsca01-cac-app-salesforcedownstream-01:***@iagadsca01-cac-app-salesforcedownstream-01.scm.azurewebsites.net/api/deployments/16801603731950666[调试]无法解析响应:{}[调试]响应:未定义[调试]遇到可重试状态代码:503.消息:'服务暂时不可用'.
[debug][PUT]https://$iagadsca01-cac-app-salesforcedownstream-01:***@iagadsca01-cac-app-salesforcedownstream-01.scm.azurewebsites.net/api/deployments/16801603731950666[debug]Could not parse response: {}[debug]Response: undefined[debug]Encountered a retriable status code: 503. Message: 'Service Temporarily Unavailable'.
管道将重复上述 PUT 操作 20 分钟并最终超时.
The pipeline will repeat the the above PUT operation for 20 mins and times out eventually.
当我尝试为我的网络应用打开 Kudu 站点 (*.scm) 站点时，它只是给了我一个带有错误的空白页面
When I try to open the Kudu site (*.scm) site for my web app, it just gave me a blank page with error
服务不可用
我认为无论我的应用程序是否正在运行，scm 站点都应该启动?什么可能导致 scm 站点给出 Service Unavailable 错误?
I think the scm site should be up regardless my app is running or not? What could cause the scm site to give Service Unavailable error?
推荐答案
在我与 Teams 上的 MSFT 进行了一次支持电话后，这个问题现在得到了解决(我的雇主对 MSFT 有非常高水平的 SLA，在两小时后联系了我提交请求)，请在此处查看我的摘要:
This is now solved after I had a support call with MSFT on Teams (my employer has a very high level SLA with MSFT, I was contacted in two hrs after submitting a request), see my summary here:
支持工程师发现应用服务的 vNet 相关错误，并建议断开应用服务与 vNet 的连接.我们这样做了，问题就解决了——scm 站点不再抛出 503 错误.
The support engineer found errors related to vNet for the app service and suggested to disconnect the app service from the vNet. We did that and the issue was solved – the scm site is no longer throw 503 error.
我们再次启用了 vNet 连接，并且 scm 站点再次开始给出 503 错误.我们认为我们知道原因是 vNet.
We enabled vNet connection again, and scm site started to give 503 error again. We thought we know the cause is vNet.
然后我们保持 vNet 连接，并扩大应用服务计划并缩小规模——这将导致应用服务迁移到另一个 VM 实例.之后 - scm 继续工作！
Then we kept the vNet connected, and scaled up the app service plan and scaled back – this will cause the app service migrate to another VM instance. After that – the scm remained working!
所以我们不知道是不是 vNet 导致了问题.底层虚拟机可能搞砸了.
So we didn’t know if it is vNet which caused problem. The underlying VM probably messed up.
这篇关于为什么我的应用服务的 Kudu 站点显示 503 Service Unavailable的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！