Identifying the issue
From the alert, we can see that our monitoring system was unable to perform ICMP pings to our company blog server. The first thing we should do is determine whether or not we can ping the server:
$ ping blog.example.com PING blog.example.com (192.168.33.11): 56 data bytes 64 bytes from 192.168.33.11: icmp_seq=0 ttl=64 time=0.832 ms 64 bytes from 192.168.33.11: icmp_seq=1 ttl=64 time=0.382 ms 64 bytes from 192.168.33.11: icmp_seq=2 ttl=64 time=0.240 ms 64 bytes from 192.168.33.11: icmp_seq=3 ttl=64 time=0.234 ms ^C --- blog.example.com ping statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.234/0.422/0.832/0.244 ms
It seems that we are able to ping the server in question, ...
Get Red Hat Enterprise Linux Troubleshooting Guide now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
