What Should I Do If the Agent Status Is Faulty?

The OS monitoring Agent sends a heartbeat message to Cloud Eye every minute. If Cloud Eye does not receive any heartbeat messages for 3 minutes, Agent Status is displayed as Faulty.

It may because:

• The domain name of the Agent cannot be resolved. Check whether the DNS server address is correct by referring to Modifying the DNS Server Address and Adding Security Group Rules (Linux). If yes, check whether the Agent is correctly configured by referring to (Optional) Manually Configuring the Agent (Linux).
• The account is in arrears.
• If the Agent process is faulty, restart it by following the instructions provided in Managing the Agent. If the restart fails, related files have been deleted by mistake. In this case, reinstall the Agent.
• The server time is inconsistent with the local standard time.
• The log path varies according to the Agent version.

  The log paths are as follows:

  • Linux:

    New version: /usr/local/uniagent/extension/install/telescope/log/ces.log

    Earlier version: /usr/local/telescope/log/ces.log

  • Windows:

    New version: C:\Program Files\uniagent\extension\install\telescope\log\ces.log

    Earlier version: C:\Program Files\telescope\log\ces.log