If no application has been deployed on the corresponding Elastic Compute Service (ECS) instance, no service is affected. If any application has been deployed on the corresponding ECS instance, in the ECS instance list of the application, the Status column of the ECS instance turns to Agent Exception, and any commands such as deploy, start, and stop commands do not take effect for the ECS instance. (To view the ECS instance list of the application, perform the following steps: In the left-side navigation pane, choose Application Management > Applications. Click the corresponding application name. On the Application Details page, click the Instance Information tab. Then, you can view the ECS instance list.)
Log on to the ECS instance and run the following command to start Enterprise Distributed Application Service (EDAS) Agent: sudo -u admin /home/admin/edas-agent/bin/startup.sh. Check the cause for the abnormal exit of EDAS Agent:
- Check whether any error message is contained in /home/admin/edas-agent/logs/agent.log.
- Check whether the system memory is sufficient. If the system memory is insufficient, the out-of-memory (OOM) kill may be triggered. For more information, search for Linux OOM kill on the Internet. If OOM kill occurs, we recommend that you check the system memory usage and adjust the memory allocation policies.