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

Symptoms

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

Possible Causes

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

• The Agent status is abnormal.
• The agency is abnormal.
• Temporary AK/SK cannot be obtained due to incorrect route configurations.
• The network is not well connected.

Troubleshooting for 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

   If the following information is displayed, the telescope process is normal.

   Figure 1 Viewing the telescope process
   
   • If yes, go to 4.
   • If no, 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 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

   

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

   Check whether monitoring data can be reported.

   • 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.
10. Run the following command to check whether the DNS service is normal:

    ping ces.ae-ad-1.g42cloud.com

    • If yes, no further action is required.
    • If no, modify the Modifying the DNS Server Address and Adding Security Group Rules (Linux) or the Cloud Eye endpoint.
      

      For details about the Cloud Eye endpoint in each region, see Regions and Endpoints.

Troubleshooting for Windows

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

   If the processes in Figure 4 and Figure 5 are displayed, the telescope process is running.

   Figure 4 agent process (Windows)
   
   Figure 5 telescope process (Windows)
   
   • If yes, go to 4.
   • If no, go to 3.
3. Double-click start.bat to start the Agent.
4. Access http://169.254.169.254/openstack/latest/meta_data.json to 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 6 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

   

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

   Check whether monitoring data can be reported.

   • 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 bin/conf_ces.json file.

   {"Endpoint":"https://ces.ae-ad-1.g42cloud.com"}

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

   ping ces.ae-ad-1.g42cloud.com

   • If yes, no further action is required.
   • If no, modify the Modifying the DNS Server Address and Adding Security Group Rules (Linux) or the Cloud Eye endpoint.
     

     For details about the Cloud Eye endpoint in each region, see Regions and Endpoints.