Background : It's a common question as we can search at google "ping works but http does not"
ping is not a reliable test of network connectivity.
ping working just means enough of the IP stack is up to process ICMP Echo requests (that's not a huge portion of the system compared to what's required for SSH and web servers). We could have had what I call a "partial panic" (Kernel blew up, but the IP code kept running), run out of RAM, or our SSH/HTTPd processes could have fallen over for unspecified reasons.
Resources
My Question : Any command line tool for ping HTTP?
Answer
There's plenty of command line tools that are capable of being a command line HTTP or simple TCP client. netcat and telnet (and yes, nmap) can tell you if the TCP port is responding, and curl or wget can handle attempting a full HTTP request.
But why not get a real monitoring solution in place instead, if you're having problems with the service failing?
No comments:
Post a Comment