When you change an application in an Elastic Compute Service (ECS) cluster by using the Enterprise Distributed Application Service (EDAS) console, a change record is generated. This topic describes the error messages and error codes that may appear in a change process.

EDAS-10000

  • Error message

    EDAS-10000 NO_SPACE_LEFT_ON_DISK

  • Possible cause

    The disk space was full.

  • Solution

    Delete logs after you log on to the ECS instance.

EDAS-10001

  • Error message

    EDAS-10001 STAR_AGENT_OFFLINE

  • Possible cause

    StarAgent was offline.

  • Solution

    Log on to the ECS instance and run the sh /home/staragent/bin/staragentctl restart command to restart the agent.

EDAS-10002

  • Error message

    EDAS-10002 Task timeout when running

  • Possible cause

    A timeout error occurred when EDAS processed the task.

EDAS-10012

  • Error message

    EDAS-10012 UNZIP_WAR_FAILED

  • Possible cause

    The WAR package failed to be decompressed by using the unzip command. Check whether the WAR package is in a valid format and can be decompressed.

EDAS-10013

  • Error message

    EDAS-10013 JAR_WAR_FAILED

  • Possible cause

    The WAR package failed to be decompressed by using the JAR command. The JDK was incorrectly installed or the JDK version in the operating system did not contain the JAR command.

  • Solution

    Log on to the ECS instance as a root user. Run the yum install -y java-1.8.0-openjdk-devel or yum install -y java-1.7.0-openjdk-devel command based on the existing JDK version. Make sure that the ECS instance is available from the Internet when you run the command.

EDAS-10014

  • Error message

    EDAS-10014 WAR_URL_403

  • Possible cause

    The WAR package failed to be downloaded because you were not authorized.

EDAS-10015

  • Error message

    EDAS-10015 WAR_URL_404

  • Possible cause

    The WAR package failed to be downloaded because the WAR package was not found.

EDAS-10016

  • Error message

    EDAS-10016 JAVA_PROCESS_ROOT

  • Possible cause

    The application failed to be stopped because the application process was started under root permissions. You were not authorized to manage the application in EDAS.

  • Solution

    Stop the application process by using the root account and try again.

EDAS-10017

  • Error message

    EDAS-10017 HOME_ADMIN_FILE_ROOT

  • Possible cause

    The application failed to start because the tomcat directory or the application directory contains a file or directory that requires root permissions.

  • Solution

    Check whether the /home/admin/app or /home/admin/${tomcat-path} directory contains any files or directories that require root permissions. If any, manually restore the permissions of the files or directories to admin and try again.

EDAS-10020

  • Error message

    EDAS-10020 SLB_NOT_ENOUGH_BALANCE

  • Possible cause

    The Server Load Balancer (SLB) instance failed to be bound because your account balance was less than CNY 100, which is insufficient to purchase the SLB instance.

EDAS-10021

  • Error message

    EDAS-10021 SLB_BIND_ALREADY_HAVE_SERVICE

  • Possible cause

    The SLB instance failed to be bound to the application because the application has been bound to an SLB instance.

  • Solution

    Unbind the SLB instance with the application in the console. Then, bind the required SLB instance with the application.

EDAS-10022

  • Error message

    EDAS-10022 K8S_READINESS_ERROR

  • Possible cause

    The application failed to start because the readiness check failed within the specified period.

  • Solution

    Check whether the related configurations are valid.

EDAS-10023

  • Error message

    EDAS-10023 K8S_BACKOFF_RESTART

  • Possible cause

    The application failed to start.

  • Solution

    Check whether the image is valid.

EDAS-10024

  • Error message

    EDAS-10024 K8S_LIVENESS_ERROR

  • Possible cause

    The application failed to start because the liveness check failed within the specified period.

  • Solution

    Check whether the related configurations are valid.

EDAS-10025

  • Error message

    EDAS-10025 PORT_CHECK_TIMEOUT

  • Possible cause

    The port check timed out during application startup. The timeout period is five minutes. The port was not enabled within five minutes.

  • Solution

    Log on to the ECS instance to check whether the application port is enabled. If not, check whether an error is reported in the startup log of the application process, and troubleshoot the problem.

EDAS-10026

  • Error message

    EDAS-10026 URL_CHECK_TIMEOUT

  • Possible cause

    URL health check was enabled for the application, but the access check of the URL timed out during application startup. The timeout period is 30 minutes. A URL health check is successful only if the HTTP status code 200 is returned after you run the curl $URL command.

  • Solution

    Log on to the ECS instance and run curl -v $URL to check whether the URL configured for the application is accessible. If the URL is inaccessible, view the application logs and check whether the application process failed to start.

EDAS-10027

  • Error message

    EDAS-10027 STARAGENT_CMD_EXECUTE_TIMEOUT

  • Possible cause

    The command implementation timed out in the publishing process. The timeout period is 60 seconds. A timeout error occurs if the publishing command is not implemented within 60 seconds.

  • Solution
    • Retry the failed task in the EDAS console.
    • If the issue persists, submit a ticket.

EDAS-10028

  • Error message

    EDAS-10028 PULL_WAR_TIMEOUT

  • Possible cause

    When you used a custom WAR or JAR URL to deploy the application, this error occurred because the pulling of the WAR or JAR package timed out. The timeout period is five minutes.

  • Solution

    Make sure that the URL is valid. Log on to the ECS instance and run the wget command to download the URL and check whether the download can be completed within 5 minutes.