When you deploy, start, scale out, or scale in an application in Enterprise Distributed Application Service (EDAS), the Change Records page visualizes the entire change process of the application for you. You can view the status of the change process. If a change fails, you can check the failed step and the cause of the failure on the Change Details page.
Troubleshoot change failures
After you change an application, you can go to the details page of the application to identify the cause of a change failure by using the change process.
On the application details page, click Change Records in the left-side navigation pane.
If a change fails, the Change Status column displays Execution failed.
On the Change Records page, find the change record of the failed change and click View in the Actions column.
In the Batch 1 Change tab of the Change Details page, click the step where the failure occurred, such as Deploy. If you configured more than one batch when you deployed your application, the EDAS console displays more than one tab, such as the Batch 1 Change tab and the Batch 2 Change tab. On the right of the Batch 1 Change or Batch 2 Change tab, view the specific log of the failed step and troubleshoot the failure.
Troubleshoot exceptions of common application changes
The following section describes how to use the change process to troubleshoot some frequently encountered exceptions when you change applications.
What do I do if I fail to change an application due to a port health check failure?
Causes
When the application is started, port 65000 that is required for the application is unavailable.
The Tomcat container fails to start as expected.
Solutions
Check whether the application logs contain the exception log.
What do I do if I fail to change an application due to a URL health check failure?
If you configured a health check URL, the URL is checked when the application starts. You cannot proceed with the application deployment process before you receive HTTP status code 200. The health check of the URL fails if you receive an HTTP status code other than 200 within the health check period (three minutes).
Solutions
If the application fails to start, view the log to check whether the application properly starts.
Check whether the correct URL is configured.
Ensure that no blocker is configured for the application to block requests from the HTTP health check URL.
After the preceding troubleshooting, deploy the application again.
What do I do if I fail to change an application because the disk is full?
If the disk is full, the application remains at a stage for a long time in the change process.
Error message
The [EDAS-10000] disk has no space available. or No space left on device. Free space (for /home/admin) in bytes: 0exit 1. The error message indicates that the disk is full. In most cases, the disk is occupied by business logs of the application. In this case, clear the application logs.
Solutions
For an application that is deployed in an Elastic Compute Service (ECS) cluster, log on to the ECS console to clear logs from the disk.
For a Docker application that is deployed in a Swarm cluster, reset the application. After the application is reset, the container is stopped, deleted, and then rebuilt. This way, the disk space is released.
What do I do if a change failure occurs due to a missing service-linked role?
Causes
The service-linked role AliyunServiceRoleForAutoScaling is not assigned to your Alibaba Cloud account. The service-linked role grants Auto Scaling the permissions to access other Alibaba Cloud services such as ECS and Virtual Private Cloud (VPC).
Solutions
Assign the service-linked role AliyunServiceRoleForAutoScaling to your Alibaba Cloud account in the Auto Scaling console.