When you deploy, start, scale out, or scale in an application in Enterprise Distributed Application Service (EDAS), the change records of the application visualize the entire change process for you. You can view the progress of the change process. If the change process fails, you can check the failed step and the cause of the failure on the Change Details page.

Troubleshooting for change failures

After you change an application, you can go to the details page of the application to identify the cause of the change failure through the change process.

  1. On the details page of the application, click Change Logs in the left-side navigation pane.

    If a change fails, the Change Status column displays Execution failed.

  2. On the Change Logs page, find the log of the failed change and click View in the Actions column.
  3. On the Change Details page, find Batch: 1. This depends on the number of batches that you specify when you deploy the application. If you specify two batches of deployment, the page displays the Batch: 1 and Batch: 2 tabs. Click the failed stage, such as Deploy Application on the tab. You can view the specific log about the failed step on the right and troubleshoot the issue.

Troubleshooting for common application change exceptions

The following content describes how to identify and resolve several common application change exceptions through the change process.

  • What do I do if I fail to change an application due to an exception in the health check of the port?Cause
    • Port 65000 that is to be occupied by an application is unavailable when the application starts.
    • The Tomcat container fails to properly start.
    Solution

    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 have 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 return code 200. The health check of the URL fails if you receive response codes other than 200 within the 3-minute health check period.

    Solution
    • 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

    [EDAS-10000] No space left on disk 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 general scenarios, the disk is occupied by business logs of the application. In this case, clear the application logs.

    Solution
    • 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 rebuilt. This way, the disk space is released.