A CloudMonitor agent connects to the server using the heartbeat mechanism at an interval of three minutes. If the CloudMonitor agent fails to respond to a heartbeat for five consecutive times (that is, within 15 minutes), the server registers the agent as stopped.
A CloudMonitor agent may have stopped due to the following two reasons:
- The agent fails to communicate with the CloudMonitor server.
- The CloudMonitor process is ended.
The agent fails to communicate with the CloudMonitor server
If the agent ran normally before the exception occurred, you can reinstall it.
The CloudMonitor process is ended
You can determine the reason why the agent has stopped by checking the CloudMonitor logs and agent running status to verify whether the CloudMonitor process ended due to a bug in CloudMonitor. To check the logs and agent running status, use the following steps according to your OS. If a bug is suspected as the cause, we recommend that you open a ticket for consultation.
- Check CloudMonitor logs.
- Linux: /usr/local/cloudmonitor/logs
- Windows: C:/Program Files/Alibaba/cloudmonitor/logs
- Check the agent running status.
sudo /usr/local/cloudmonitor/wrapper/bin/cloudmonitor.sh status
C:\"Program Files (x86)"\Alibaba\cloudmonitor\wrapper\bin\AppCommand.bat status
In Linux, you can run the
/usr/local/cloudmonitor/wrapper/bin/cloudmonitor.shcommand to view additional help information.