All Products
Search

This Product

    CloudMonitor:How do I troubleshoot an abnormal stop of the CloudMonitor agent?

    Document Center

    CloudMonitor:How do I troubleshoot an abnormal stop of the CloudMonitor agent?

    Last Updated:Jan 02, 2024

    If the CloudMonitor agent that is installed on a host is in the Stopped state, CloudMonitor cannot monitor the host. You must troubleshoot the stop of the CloudMonitor agent and rerun the CloudMonitor agent.

    Issue

    By default, the CloudMonitor agent sends a heartbeat message to the CloudMonitor server every 3 minutes. If the CloudMonitor agent does not send heartbeat messages for 15 minutes, the host where the agent resides determines that the agent stops. The CloudMonitor agent may automatically stop due to the following causes:

    If the CloudMonitor agent still does not send heartbeat messages, perform the operations provided in the following sections.

    Reinstall or upgrade the CloudMonitor agent

    If the CloudMonitor agent runs normally before it stops, you can reinstall the agent and start it again. If you use the CloudMonitor agent for Go or Java, upgrade it to the CloudMonitor agent for C++ that has the latest version. Use one of the following methods to install or upgrade the CloudMonitor agent:

    Note

    The CloudMonitor agents for Go and Java are no longer maintained.

    View the status and logs of the CloudMonitor agent

    Important You can manage the CloudMonitor agent only by using an administrator account. For Linux operating systems, use the root user account. For Windows operating systems, use the Administrator account. If you use an administrator account, certain risks may occur. For example, system stability or data security issues may occur. Proceed with caution.

    You can view the status and logs of the CloudMonitor agent to determine the cause of the abnormal stop. If the process of the CloudMonitor agent exits, it may be caused by a bug of the CloudMonitor agent. We recommend that you submit a ticket and do not perform troubleshooting until Alibaba Cloud engineers contact you.

    • View logs of the CloudMonitor agent

      • Windows

        1. Log on to the host on which you want to install the CloudMonitor agent as an administrator.

        2. Go to the C:\Program Files\Alibaba\cloudmonitor\local_data\logs directory that stores the logs of the CloudMonitor agent.

        3. Open the log file argusagent.log or argusagentd.log in Notepad or WordPad.

          • argusagentd.log: stores the logs generated by the CloudMonitor 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 CloudMonitor agent.

      • Linux

        1. Log on to the host on which you want to install the CloudMonitor agent as a root user.

        2. Run the following commands to view the logs of the CloudMonitor agent:

          cd /usr/local/cloudmonitor/local_data/logs

          cat argusagent.log

          cat argusagentd.log

          • argusagentd.log: stores the logs generated by the CloudMonitor 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 CloudMonitor agent.

    • View the status of the CloudMonitor agent

      • Windows

        1. Log on to the host on which you want to install the CloudMonitor agent as an administrator.

        2. Open the Services window.

          Press Win+R. In the Run dialog box, enter services.msc and click OK.

        3. View the status of the argusagent service.

      • Linux

        1. Log on to the host on which you want to install the CloudMonitor agent as a root user.

        2. Run the following command to view the status of the CloudMonitor agent:

          ps aux | grep argusagent | grep -v grep

    References