When you deploy, start, scale out, or scale in an application in Enterprise Distributed Application Service (EDAS), the application's change log visualizes 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 click the application name to go to the Application Details page to View application changes, or locate the cause for the change failure.

  1. On the Application Details page, 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 you specified when deploying the application. If you have specified two batches of deployment, the page displays 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 locate the problem.

Troubleshooting for common application change exceptions

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

  • What can I do when failing to change an application due to an exception in the health check of the port?

    Possible causes are as follows:

    • Port 65000 that was to be occupied by an application was unavailable when the application started.
    • The Tomcat container did not start properly.

    Check whether the application logs contain the corresponding exception log. If yes, rectify the problem based on the exception log.

  • What can I do when failing 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 receiving HTTP response code 200. The health check of the URL fails if you receive other response codes, which are error codes, within the three-minute health check period.

    • If the application fails to start, view the log to check whether the application starts properly.
    • Check whether the URL is configured correctly.
    • 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 can I do when failing to change an application because the disk is full?

    If the disk is full, the application remains at a certain 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. This error message indicates that the disk is full. Generally, the disk is filled by business logs of the application. You must clear the application logs.

    • For an application deployed in an Elastic Compute Service (ECS) cluster, log on to the ECS console to clear logs from the disk.
    • For a Dockerized application deployed in a Swarm cluster, reset the application. After the application is reset, the container is stopped, deleted, and rebuilt. In this way, the disk space is freed up.