The Enterprise Distributed Application Service (EDAS) console relies on the EDAS Agent running on each application instance to relay commands. If the EDAS Agent process exits, the console cannot communicate with the instance, and operations have no effect.
This issue has been resolved in newer versions of EDAS Agent.
Symptom
You perform an operation on an application in the EDAS console, but the console does not respond. The operation has no visible effect.
Cause
The EDAS Agent process on the application instance has exited. The EDAS Agent mediates all commands between the EDAS console and the instance. When the agent is not running, the console has no channel to execute operations on that instance.
Solution
Step 1: Restart the EDAS Agent
Log on to the application instance.
Run the following command as the
adminuser:/home/admin/edas-agent/bin/startup.shReturn to the EDAS console and retry the operation.
Step 2: Reset the application instance
If restarting the EDAS Agent does not resolve the issue, reset the instance from the EDAS console:
Go to the Basic Information page of the application.
Click the Instance Information tab.
In the Actions column, click Reset for the affected instance.
Wait for the reset to complete, then retry the operation.