yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
0b3a43371a4bcc99577594de0a685249d676a567
doc-exports/docs/ces/umn/ces_faq_0025.html
qiujiandong1 c1d4f578e7 CES UMN 20250530 version 
Reviewed-by: Rumpler, Mihály <mihaly.rumpler@t-systems.com>
Co-authored-by: qiujiandong1 <qiujiandong1@huawei.com>
Co-committed-by: qiujiandong1 <qiujiandong1@huawei.com>
2025-11-18 06:22:57 +00:00

3.1 KiB
Raw Blame History

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 three consecutive minutes, Agent Status is displayed as Faulty.

It may because:

  • 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 accidentally. In this case, reinstall the Agent.
  • The server time is inconsistent with the local standard time.
  • The Agent is incorrectly configured. Check whether the DNS server address is correct. If it is, check the Agent configurations by referring to Modifying the DNS Server Address and Adding Security Group Rules (Linux) and (Optional) Manually Configuring the Agent on a Linux Server.
  • Specific causes are logged. You can check the log file for the cause. The log path varies with the Agent version.

    The log paths are as follows:

    • Linux:

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

      Early Agent version: /usr/local/telescope/log/ces.log

    • Windows:

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

      Earlier version: path where the Agent installation package is decompressed. For example, if the decompression path is D:\Agent, the log path is D:\Agent\telescope_windows_amd64\log\ces.log.

Parent topic: Server Monitoring