Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Cloud Eye/ FAQs/ Server Monitoring/ Agent Statuses/ What Can I Do If No Monitoring Data Is Displayed After One-Click Agent Restoration? (Old Agent)

What Can I Do If No Monitoring Data Is Displayed After One-Click Agent Restoration? (Old Agent)

Updated on 2024-01-11 GMT+08:00

Symptom

The Agent is running normally after being restored, but no monitoring data is generated.

Possible Causes

If no OS monitoring data is available for an ECS or BMS with the Agent installed, the possible causes are as follows:

  • There is a problem with the Agent process.
  • There is a problem with agency configurations.
  • Temporary AK/SK cannot be obtained due to incorrect route configurations.
  • The network is not well connected.

Check the Agent version.

  1. Log in to an ECS as user root.
  2. Run the following command to check the Agent version:

    if [[ -f /usr/local/uniagent/extension/install/telescope/bin/telescope ]]; then /usr/local/uniagent/extension/install/telescope/bin/telescope -v; elif [[ -f /usr/local/telescope/bin/telescope ]]; then echo "old agent"; else echo 0; fi

    • If old agent is displayed, the early version of the Agent is used.
    • If a version ID is returned, the new version of the Agent is used.
    • If 0 is returned, the Agent is not installed.

Procedure (Linux)

  1. Log in to the ECS or BMS as user root.
  2. Run the following command to check whether the telescope process is running:

    ps -ef |grep telescope

    The following information indicates that the telescope process is normal.

    Figure 1 Viewing the telescope processes

    • If the telescope process is normal, go to 4.
    • If the telescope process is abnormal, go to 3.
  3. Run the following command to start the Agent:

    /usr/local/telescope/telescoped start

  4. Run the following command to check whether an agency has been created for the server:

    curl http://169.254.169.254/openstack/latest/securitykey

    • If data is returned, the agency is normal and AK/SK can be obtained. No further action is required.
    • If the request fails or the following information is displayed, go to 5.
      Figure 2 Failing to obtain the AK/SK
  5. On the Cloud Eye console, choose Server Monitoring > Elastic Cloud Server, select the target ECS, and click Restore Agent Configurations.
    • If the problem is resolved, no further action is required.
    • Otherwise, go to 6.
  6. Run the following command to check the route:

    route -n

    The following information indicates that the route is normal.

    Figure 3 Normal route configuration-Linux
    • If the route is normal, no further action is required.
    • Otherwise, go to 7.
  7. If the route does not exist, run the following command to add a route:

    route add -host 169.254.169.254 gw 192.168.0.1

    NOTE:

    Replace 192.168.0.1 in the example command with the gateway of the server.

    Check whether monitoring data can be reported normally.

    • If yes, no further action is required.
    • If no, go to 8.
  8. Run the following command to open the telescope configuration file:

    cat /usr/local/telescope/bin/conf_ces.json

  9. Obtain the endpoint from the configuration file.
    Figure 4 Querying the telescope endpoint
  10. Run the following command to check whether the DNS service is normal:

    ping ces.cn-south-1.myhuaweicloud.com

    • If the network is normal, no further action is required.
    • Otherwise, modify the DNS server address or the Cloud Eye endpoint.
      NOTE:

      For details about Cloud Eye endpoints for each region, see Regions and Endpoints.

Procedure (Windows)

  1. Log in to the ECS or BMS as an administrator.
  2. Open the Task Manager and check whether the telescope process is running.

    If there are Figure 5 and Figure 6, the telescope process is running.

    Figure 5 agent process (Windows)
    Figure 6 telescope process (Windows)

    • If the telescope process is normal, go to 4.
    • If the telescope process is abnormal, go to 3.
  3. Double-click start.bat to start the Agent.
  4. Access http://169.254.169.254/openstack/latest/meta_data.json and check whether the agency has been created.
    • If the website is accessible, the agency is normal. No further action is required.
    • Otherwise, go to 6.
  5. Run the following command to check the route:

    route print

    The following information indicates that the route is normal.

    Figure 7 Normal route configuration-Windows
    • If the route is normal, no further action is required.
    • Otherwise, go to 7.
  6. If the route does not exist, run the following command to add a route:

    route add -host 169.254.169.254 gw 192.168.0.1

    NOTE:

    Replace 192.168.0.1 in the example command with the gateway of the server.

    Check whether monitoring data can be reported normally.

    • If yes, no further action is required.
    • If no, go to 7.
  7. Open the configuration file in bin/conf_ces.json in the directory where the telescope installation package is stored.
  8. Obtain the endpoint from the telescope configuration file.

    {"Endpoint":"https://ces.cn-north-4.myhuaweicloud.com"}

  9. Run the following command to check whether the DNS service is normal:

    ping ces.cn-north-4.myhuaweicloud.com

    • If the network is normal, no further action is required.
    • Otherwise, modify the DNS server address or the Cloud Eye endpoint.
      NOTE:

      For details about Cloud Eye endpoints for each region, see Regions and Endpoints.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback