If the Cloud Monitor agent that is installed on a host is in the Stopped state, Cloud Monitor cannot monitor the host. You must troubleshoot the stop of the Cloud Monitor agent and rerun the Cloud Monitor agent.
Issue
By default, the Cloud Monitor agent sends a heartbeat message to the Cloud Monitor server every 3 minutes. If the Cloud Monitor agent does not send heartbeat messages for 15 minutes, the host where the agent resides determines that the agent stops. The Cloud Monitor agent may automatically stop due to the following causes:
The Cloud Monitor agent cannot communicate with the Cloud Monitor server.
For more information about how to check the network, see Configure network settings.
The process of the Cloud Monitor agent exits.
For more information about how to handle an auto-exit of the Cloud Monitor agent process, see What do I do if the process of the CloudMonitor agent automatically exits?
If the Cloud Monitor agent still does not send heartbeat messages, perform the operations provided in the following sections.
Reinstall or upgrade the Cloud Monitor agent
If the Cloud Monitor agent runs normally before it stops, you can reinstall the agent and start it again. If you use the Cloud Monitor agent for Go or Java, upgrade it to the Cloud Monitor agent for C++ that has the latest version. Use one of the following methods to install or upgrade the Cloud Monitor agent:
(Recommended) Automatically install the CloudMonitor agent for C++
Install the CloudMonitor agent for C++ on a host by using a script
The Cloud Monitor agents for Go and Java are no longer maintained.
View the status and logs of the Cloud Monitor agent
You can only manage the Cloud Monitor agent by using an administrator account (the root user for Linux or the Administrator user for Windows). However, using an administrator account may introduce certain risks, such as system stability or data security issues. Proceed with caution.
You can view the status and logs of the Cloud Monitor agent to determine the cause of the abnormal stop. If the process of the Cloud Monitor agent exits, it may be caused by a bug of the Cloud Monitor agent. We recommend that you submit a ticket and do not perform troubleshooting until Alibaba Cloud engineers contact you.
View logs of the Cloud Monitor agent
Windows
Log on to the host on which you want to install the Cloud Monitor agent as an administrator.
Go to the C:\Program Files\Alibaba\cloudmonitor\local_data\logs directory that stores the logs of the Cloud Monitor agent.
Open the log file argusagent.log or argusagentd.log in Notepad or WordPad.
argusagentd.log: stores the logs generated by the Cloud Monitor agent about daemon processes. The logs contain information such as the startup and shutdown of monitoring processes.
argusagent.log: stores the operational logs of the Cloud Monitor agent.
Linux
Log on to the host on which you want to install the Cloud Monitor agent as a root user.
Run the following commands to view the logs of the Cloud Monitor agent:
cd /usr/local/cloudmonitor/local_data/logs
cat argusagent.log
cat argusagentd.log
argusagentd.log: stores the logs generated by the Cloud Monitor agent about daemon processes. The logs contain information such as the startup and shutdown of monitoring processes.
argusagent.log: stores the operational logs of the Cloud Monitor agent.
View the status of the Cloud Monitor agent
Windows
Log on to the host on which you want to install the Cloud Monitor agent as an administrator.
Open the Services window.
Press Win+R. In the Run dialog box, enter services.msc and click OK.
View the status of the argusagent service.
Linux
Log on to the host on which you want to install the Cloud Monitor agent as a root user.
Run the following command to view the status of the Cloud Monitor agent:
ps aux | grep argusagent | grep -v grep