Azure功能损坏：在运行时没有从visual studio，503完全部署 [英] Azure functions broken: not fully deploying from visual studio, 503 when running

问题描述

我在visual studio代码中有一堆javascript azure函数（所有这些函数最近都在使用），我想将它们推送到一个函数应用程序容器。

I have a bunch of javascript azure functions in visual studio code (all of which were working recently), I want to push them to a function apps container.

我创建了一个全新的容器来托管它们。我创建了一个httptrigger来测试新容器是否正常工作并运行它。这很好。我删除了httptrigger，认为容器是好的。

I created a brand new container to host them. I create an httptrigger to test that the new container is working and run it. That works fine. I delete the httptrigger thinking the container is good.

然后我尝试使用visual studio代码部署我的httptrigger函数，这需要几分钟。大约12"等待长时间运行......"完成后，输出窗口中没有报告错误，但功能只部分部署
（因为我有大约12个函数，但现在服务器上只有6个）。

I then try to deploy my httptrigger functions using visual studio code, it takes several minutes. About 12 "Waiting for long running..." When its finished there are no reported errors in the output window but the functions only partially deploy (as in I have about 12 functions, but only 6 are now on the server).

无论如何，它们都不起作用。我选择一个并打开它。我可以看到我的代码，但如果我按下运行，我会得到503状态（下图）。

Regardless, none of them work. I select one and open it. I can see my code but if I press run I get a 503 status (picture below).

知道可能出现什么问题或者我怎么能弄清楚出了什么问题？在我看过的任何日志中都没有看到任何真正有用的信息（但我不确定我是否找到了正确的日志）。

Any idea what might be going wrong or how I can figure out what is going wrong? Not seeing any really useful information in any of the logs I've looked at (but I'm not sure I'm finding the right logs).

推荐答案

Hi Desmarais，

我们无法看到任何显示503错误的图像/图片。  

HTTP 503基本上是服务不可用的。通常，如果容器无法启动，当您浏览应用程序
时将返回503状态。

如果容器从不启动

If Container Never Launches

首先要检查来自的docker.log LogFiles文件夹。 Docker日志将通过KUDU使用Bash或通过FTP在/ home / LogFiles目录中提供。 
您可以选中此项以验证
容器是否正确启动。

The first thing is to check the docker.log from the LogFiles folder. Docker logs will be available via KUDU using Bash or via FTP in the /home/LogFiles directory.  You can check this to verify that the container started correctly.

如果容器需要时间：

If Container Needs Time:

容器可能需要很长时间才能启动。如果一个容器需要安装很多组件，那么这个时间可以是几分钟。默认情况下，我们将在230秒后
启动时超时。

Containers might take a long time to launch. If a container requires the installation of a lot of components, that time can be several minutes. By default, we will time out on the launch after 230 seconds.

 

如果容器需要的时间超过默认值230秒，则可以配置
WEBSITES_CONTAINER_START_TIME_LIMIT 应用程序设置增加我们等待的时间。此属性的值以秒为单位。您可以将其配置为最多600秒。

If a container requires longer than the default 230 seconds, you can configure the WEBSITES_CONTAINER_START_TIME_LIMIT application setting to increase the time we wait. The value of this property is in seconds. You can configure it to a maximum of 600 seconds.

这篇关于Azure功能损坏：在运行时没有从visual studio，503完全部署的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！