All Products
Search
Document Center

Enterprise Distributed Application Service:How do I handle the agent exception thrown after the agent process stops running?

Last Updated:May 25, 2023

Problem description

After the agent process stops running, Agent Exception appears in the Status column of an Elastic Compute Service (ECS) instance on which an application is installed in the instance list for the application. At the meantime, you fail to perform operations, such as restarting the ECS instance, starting the application, or stopping the application. If no application is installed on the ECS instance after the agent process stops running, the instance runs as expected.

Solutions

  1. Log on to the ECS instance and run the following command to start the agent:

    sudo -u admin /home/admin/edas-agent/bin/startup.sh
    Note

    In most cases, you do not need to manually restart the agent. The system automatically starts the agent to run scheduled tasks that are configured in the system. You can run the crontab -l command to view the details of scheduled tasks.

  2. If the error persists, perform the following steps to troubleshoot the error:

    1. Check whether the system memory is sufficient. If the system memory is insufficient, the out-of-memory (OOM) killer mechanism may be triggered. For more information about how to resolve the issue, see Out-of-memory (OOM) killer triggered by low physical memory on the operating system.

    2. If the error persists, check the error messages are recorded in the /home/admin/edas-agent/logs/agent.log directory.