Cause: This problem is caused by exit of the EDAS Agent process. It has been rectified in the latest version of EDAS Agent.
Solution: Log on to the customer's ECS instance and run the command /home/admin/edas-agent/bin/startup.sh as admin. If the application still cannot be operated, click Reset.