Enterprise Distributed Application Service:Error codes that may be returned in a change process

EDAS-10000 NO_SPACE_LEFT_ON_DISK

The disk space is used up.

Log on to the ECS instance and delete the logs.

EDAS-10001 STAR_AGENT_OFFLINE

StarAgent is offline.

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

EDAS-10002 Task timeout when running

Task execution timed out.

EDAS-10012 UNZIP_WAR_FAILED

Failed to unzip the WAR package by using the unzip command.

Check whether your WAR package can be decompressed successfully.

EDAS-10013 JAR_WAR_FAILED

The WAR package failed to be decompressed by using the JAR command. The Java Development Kit (JDK) is incorrectly installed or the JDK version in the operating system does not contain the JAR command.

Log on to the ECS instance as the 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 accessible from the Internet when you run the command.

EDAS-10014 WAR_URL_403

The WAR package failed to be downloaded because you are not authorized to access the WAR package.

EDAS-10015 WAR_URL_404

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

EDAS-10016 JAVA_PROCESS_ROOT

The application failed to be stopped because the application process was started under root permissions. EDAS does not have the permissions to manage the application.

Stop the application process as the root user and try again.

EDAS-10017 HOME_ADMIN_FILE_ROOT

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

Check whether the /home/admin/app or /home/admin/${tomcat-path} directory contains a file or directory that requires root permissions. If such a file or directory exists, manually restore the permissions of the file or directory to admin and try again.

EDAS-10020 SLB_NOT_ENOUGH_BALANCE

The Server Load Balancer (SLB) instance failed to be bound because your account balance is insufficient.

Ensure that your account balance is at least USD 10 to purchase the SLB instance.

EDAS-10021 SLB_BIND_ALREADY_HAVE_SERVICE

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

Unbind the existing SLB instance from the application in the EDAS console. Then, bind the required SLB instance to the application.

EDAS-10022 K8s_READINESS_ERROR

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

Check whether the related configurations are valid.

EDAS-10023 K8s_BACKOFF_RESTART

The application failed to start.

Check whether the image is valid.

EDAS-10024 K8s_LIVENESS_ERROR

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

Check whether the related configurations are valid.

EDAS-10025 PORT_CHECK_TIMEOUT

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

1. On the Applications page, find the application that is deployed in an ECS cluster, and click the application name. On the Basic Information tab, check the value of Application Port in the Application Settings section.
2. Log on to the ECS instance and run one of the following commands to check whether the port is enabled:
   • Method 1:

     netstat -lnp | grep port number

   • Method 2:

     ss -lnp | grep port number

3. If the port is not enabled, check whether an error is reported in the startup log of the application process and handle the error accordingly.

EDAS-10026 URL_CHECK_TIMEOUT

URL health check is 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.

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 STARAGENT_CMD_EXECUTE_TIMEOUT

The command execution timed out in the release process. The timeout period is 60 seconds. A timeout error occurs if the release command is not executed within 60 seconds.

• Retry the failed task in the EDAS console.
• If the error persists, join the DingTalk group (ID: 31723701) to obtain technical support.

EDAS-10028 PULL_WAR_TIMEOUT

When you use the URL of a custom WAR or JAR package to deploy an application, this error occurs if the pulling of the WAR or JAR package times out. The timeout period is 5 minutes.

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