【问题标题】:.NetCore App Engine Flex Deployment: Error Response: [4] App Engine Flexible timed out while configuring resources, internal operation.NetCore App Engine Flex 部署:错误响应:[4] App Engine Flexible 在配置资源时超时,内部操作
【发布时间】:2020-04-23 18:17:35
【问题描述】:

我收到了错误

错误响应:[4] App Engine Flexible 在配置时超时 资源、内部运作

在将 .NetCore 应用程序部署到我的 App Engine 时。 App Engine 目前位于亚洲南部。我还在美国东部使用 App Engine 创建了另一个项目。我收到错误

错误:(gcloud.app.deploy)内部:遇到内部错误。

在部署时。尝试部署 GCP 文档中指定的 Hello world 应用程序。它在部署时也遇到了同样的问题。我是不是错过了什么。我已更新 BACKEND_SEVICES 配额。之后只有我得到这个问题。还能够将版本视为服务。但没有实例处于活动状态。我无法激活任何其他版本。它也显示为内部错误。

这是我的 app.YAML

runtime: aspnetcore
env: flex
manual_scaling:
  instances: 1
resources:
  cpu: 1
  memory_gb: 0.5
  disk_size_gb: 10
beta_settings:
    cloud_sql_instances: "#########:#####-api-system=tcp:3306"

到昨天为止一切正常。从今天开始我会收到这个问题。

附加详细日志

Updating service [default] (this may take several minutes)...|DEBUG: Operation [apps/**projectid**/operations/c46a17bd-d4a8-468f-b40b-47a7fdd03067] not complete. Waiting to retry.
Updating service [default] (this may take several minutes)...|DEBUG: Operation [apps/**projectid**/operations/c46a17bd-d4a8-468f-b40b-47a7fdd03067] not complete. Waiting to retry.
Updating service [default] (this may take several minutes)...\DEBUG: Operation [apps/**projectid**/operations/c46a17bd-d4a8-468f-b40b-47a7fdd03067] not complete. Waiting to retry.
Updating service [default] (this may take several minutes)...\DEBUG: Operation [apps/**projectid**/operations/c46a17bd-d4a8-468f-b40b-47a7fdd03067] not complete. Waiting to retry.
Updating service [default] (this may take several minutes)...-DEBUG: Operation [apps/**projectid**/operations/c46a17bd-d4a8-468f-b40b-47a7fdd03067] complete. Result: {
    "done": true,
    "error": {
        "code": 4,
        "message": "App Engine Flexible timed out while configuring resources, internal operation projects/**projectid**/regions/asia-south1/operations/700238de-3add-4281-80f8-6dc66948a715"
    },
    "metadata": {
        "@type": "type.googleapis.com/google.appengine.v1.OperationMetadataV1",
        "createVersionMetadata": {
            "cloudBuildId": "38b57f34-3b23-4484-9d69-0c581995947f"
        },
        "endTime": "2020-04-23T23:40:50.335Z",
        "insertTime": "2020-04-23T23:29:10.164Z",
        "method": "google.appengine.v1.Versions.CreateVersion",
        "target": "apps/**projectid**/services/default/versions/20200424t045856",
        "user": "eltuniverse@gmail.com"
    },
    "name": "apps/**projectid**/operations/c46a17bd-d4a8-468f-b40b-47a7fdd03067"
}
Updating service [default] (this may take several minutes)...failed.
DEBUG: (gcloud.app.deploy) Error Response: [4] App Engine Flexible timed out while configuring resources, internal operation projects/**projectid**/regions/asia-south1/operations/700238de-3add-4281-80f8-6dc66948a715
Traceback (most recent call last):
  File "C:\Google\CloudSDK\google-cloud-sdk\lib\googlecloudsdk\calliope\cli.py", line 983, in Execute
    resources = calliope_command.Run(cli=self, args=args)
  File "C:\Google\CloudSDK\google-cloud-sdk\lib\googlecloudsdk\calliope\backend.py", line 807, in Run
    resources = command_instance.Run(args)
  File "C:\Google\CloudSDK\google-cloud-sdk\lib\surface\app\deploy.py", line 111, in Run
    return deploy_util.RunDeploy(
  File "C:\Google\CloudSDK\google-cloud-sdk\lib\googlecloudsdk\command_lib\app\deploy_util.py", line 634, in RunDeploy
    deployer.Deploy(
  File "C:\Google\CloudSDK\google-cloud-sdk\lib\googlecloudsdk\command_lib\app\deploy_util.py", line 431, in Deploy
    self.api_client.DeployService(new_version.service, new_version.id,
  File "C:\Google\CloudSDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\app\appengine_api_client.py", line 204, in DeployService
    return operations_util.WaitForOperation(
  File "C:\Google\CloudSDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\app\operations_util.py", line 307, in WaitForOperation
    completed_operation = waiter.WaitFor(
  File "C:\Google\CloudSDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\util\waiter.py", line 261, in WaitFor
    operation = PollUntilDone(
  File "C:\Google\CloudSDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\util\waiter.py", line 322, in PollUntilDone
    operation = retryer.RetryOnResult(
  File "C:\Google\CloudSDK\google-cloud-sdk\lib\googlecloudsdk\core\util\retry.py", line 229, in RetryOnResult
    if not should_retry(result, state):
  File "C:\Google\CloudSDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\util\waiter.py", line 320, in _IsNotDone
    return not poller.IsDone(operation)
  File "C:\Google\CloudSDK\google-cloud-sdk\lib\googlecloudsdk\api_lib\app\operations_util.py", line 182, in IsDone
    raise OperationError(requests.ExtractErrorMessage(
googlecloudsdk.api_lib.app.operations_util.OperationError: Error Response: [4] App Engine Flexible timed out while configuring resources, internal operation projects/**projectid**/regions/asia-south1/operations/700238de-3add-4281-80f8-6dc66948a715
ERROR: (gcloud.app.deploy) Error Response: [4] App Engine Flexible timed out while configuring resources, internal operation projects/**projectid**/regions/asia-south1/operations/700238de-3add-4281-80f8-6dc66948a715

App.yaml

runtime: aspnetcore
env: flex
manual_scaling:
  instances: 1
resources:
  cpu: 1
  memory_gb: 0.5
  disk_size_gb: 10
beta_settings:
    cloud_sql_instances: "***projectid***:asia-south1:***dbname***=tcp:3306"

谢谢。

【问题讨论】:

    标签: google-app-engine .net-core google-cloud-platform app-engine-flexible


    【解决方案1】:

    建议在这种情况下获取更多详细信息。您可以使用:gcloud app deploy --verbosity=debug 进行部署,只是为了看看您是否可以检索到有关此的更多信息。

    这似乎是由于某些原因。我建议检查:

    1. 在某些情况下,运行此命令$ gcloud config set app/trigger_build_server_side false 很有用,以便在部署之前强制在客户端而不是服务器端(可能会以某种方式更改)管理建筑物。试试这个命令,然后重新部署。

    2. 您的应用程序配置可能发生的变化。查看您的app.yaml,检查不同的值。比较 4 月 22 日的版本和今天的版本。可以部署昨天的版本吗?

    3. 项目中与 App Engine 和 Compute Engine 关联的配额。请记住,App Engine Flex 最终会在虚拟机中运行。 Here 是一个类似的问题,与配额有关:In-use IP addresses。如果您看到任何配额已用完,您可以请求增加配额。

    4. 在某些情况下,这也可能与内部问题有关,在这种情况下,您应该在 GCP 中创建一个案例。 (让我们将此作为最终选项)

    5. 另外,您能否分享一下相关的详细日志?请务必不要分享任何敏感信息

    请让我知道您对此的发现。如果您可以共享两个版本(工作和不工作)的 app.yaml,那也很棒,以防上述不起作用。

    【讨论】:

    • 感谢您的详细帖子。附加详细日志和 App.yaml。 1)我认为云构建没有问题,因为版本正在发布,但没有生成实例。 2)App.yaml 没有变化 3)我也检查过。它也处于控制之中。我目前只消耗了 8 个中的 3 个。
    • 我强烈建议在 GCP 的公共问题跟踪器中提交错误。在那里,您可以共享敏感信息,例如您的项目 ID,他们可以提供进一步的帮助。 here 你会找到模板。请确保组件是:Public Trackers > Cloud Platform > Compute > App Engine > Private App Engine 问题。私有组件将使其仅对您和 Google 团队可见。
    猜你喜欢
    • 2020-10-09
    • 2019-04-11
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 1970-01-01
    • 2013-10-23
    • 1970-01-01
    • 2012-06-25
    相关资源
    最近更新 更多