When the CloudMonitor agent on a host enters the Stopped state, CloudMonitor stops monitoring that host. Identify the cause and restart the agent.
Issue
The CloudMonitor agent sends a heartbeat to the CloudMonitor server every 3 minutes. If no heartbeat is received for 15 minutes, the agent is considered stopped. Possible causes:
-
The agent cannot communicate with the CloudMonitor server.
For more information about how to check the network, see Configure network settings for CloudMonitor.
-
The agent process exited.
For more information about how to handle an auto-exit of the Cloud Monitor agent process, see What do I do if the Cloud Monitor agent exits automatically?
If the agent still does not send heartbeats, try the following solutions.
Reinstall or upgrade the CloudMonitor agent
If the agent ran normally before it stopped, reinstall and restart it. If you use the Go or Java agent, upgrade to the latest CloudMonitor agent for C++:
-
(Recommended) Automatically install the CloudMonitor agent for C++
-
Install the CloudMonitor agent for C++ on a host by using a script
The CloudMonitor agents for Go and Java are no longer maintained.
View CloudMonitor agent status and logs
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.
Check the agent status and logs to determine the cause of the stop. If the agent process exited due to a bug, submit a ticket and wait for Alibaba Cloud engineers to contact you before troubleshooting.
-
View agent logs
-
Windows
-
Log on to the host as an administrator.
-
Go to the C:\Program Files\Alibaba\cloudmonitor\local_data\logs directory.
-
Open argusagent.log or argusagentd.log.
-
argusagentd.log: daemon process logs, including monitoring process startup and shutdown events.
-
argusagent.log: operational logs of the CloudMonitor agent.
-
-
-
Linux
-
Log on to the host as the root user.
-
Run the following commands to view agent logs:
cd /usr/local/cloudmonitor/local_data/logs
cat argusagent.log
cat argusagentd.log
-
argusagentd.log: daemon process logs, including monitoring process startup and shutdown events.
-
argusagent.log: operational logs of the CloudMonitor agent.
-
-
-
-
View agent status
-
Windows
-
Log on to the host as an administrator.
-
Open the Services window.
Press Win+R. In the Run dialog box, enter services.msc and click OK.
-
Check the status of the argusagent service.
-
-
Linux
-
Log on to the host as the root user.
-
Run the following command to check agent status:
ps aux | grep argusagent | grep -v grep
-
-