If you cannot connect to a Lindorm instance, use the ping command on your ECS instance to test the network connection.
Procedure
-
Log on to your ECS instance and run the following command.
ping <host>Example:
ping ld-bp1mq0tdzbx1m****-proxy-lindorm-pub.lindorm.aliyuncs.comNote-
For host, use the endpoint obtained in Step 1. Do not include the port number.
-
This command works on both Windows and Linux.
-
-
Review the output. The following examples use a Lindorm time series engine endpoint.
-
Windows displays the test results after 4
pingattempts, as shown below.C:\Users\xxx>ping ld-bxxx-proxy-tsdb-pub.lindorm.rds.aliyuncs.com Pinging ld-bxxx-proxy-tsdb-pub.lindorm.rds.aliyuncs.com [xxx] with 32 bytes of data: Reply from xxx: bytes=32 time=51ms TTL=93 Reply from xxx: bytes=32 time=43ms TTL=93 Reply from xxx: bytes=32 time=46ms TTL=93 Reply from xxx: bytes=32 time=45ms TTL=93 Ping statistics for xxx: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milliseconds: Minimum = 43ms, Maximum = 51ms, Average = 46ms C:\Users\issuser>NoteIf you need to continuously test connectivity, use the
ping <host> -tcommand. -
After this command is run on a Linux system, it continuously sends
pingrequests. You can press Ctrl+C to stop the execution and view the statistics. An example is shown below.[root@iZbp1dcbb6ptxxx ~]# ping ld-bpxxx-proxy-tsdb-pub.lindorm.rds.aliyuncs.com PING ld-bxxx-proxy-tsdb-pub.lindorm.rds.aliyuncs.com (xxx) 56(84) bytes of data. 64 bytes from xxx (xxx): icmp_seq=1 ttl=95 time=3.43 ms 64 bytes from xxx (xxx): icmp_seq=2 ttl=95 time=3.43 ms 64 bytes from xxx (xxx): icmp_seq=3 ttl=95 time=3.45 ms 64 bytes from xxx (xxx): icmp_seq=4 ttl=95 time=3.46 ms 64 bytes from xxx (xxx): icmp_seq=5 ttl=95 time=3.47 ms 64 bytes from xxx (xxx): icmp_seq=6 ttl=95 time=3.42 ms 64 bytes from xxx (xxx): icmp_seq=7 ttl=95 time=3.44 ms 64 bytes from xxx (xxx): icmp_seq=8 ttl=95 time=3.49 ms 64 bytes from xxx (xxx): icmp_seq=9 ttl=95 time=3.45 ms ^C --- ld-bpxxx-proxy-tsdb-pub.lindorm.rds.aliyuncs.com ping statistics --- 9 packets transmitted, 9 received, 0% packet loss, time 8009ms rtt min/avg/max/mdev = 3.425/3.452/3.492/0.065 ms
-
Result analysis
-
A response to every request, as shown in the examples above, confirms that the connection is working correctly.
-
If you do not receive a response, it indicates a connection problem. Check the configurations of your ECS and Lindorm instances, such as their whitelist or security group settings. For more information, see Lindorm connection issues and solutions.