To troubleshoot server downtime using Check Host Pro (the Windows-service-based application developed by AB-Tools) or its web-based counterpart Check-Host.net, you must systematically isolate whether the outage is a global network failure, a specific application layer crash, or a localized routing error.
Here is a step-by-step guide to diagnosing server downtime using the core feature set of Check Host Pro. 1. Isolate the Layer of Failure
Before jumping to conclusions, use the protocol switching features in Check Host Pro to narrow down the problem layer.
Network Layer (Ping Check): Send ICMP packets to the server’s IP address. If you receive a 0/4 packets received error globally, the underlying server hardware is offline, or a strict firewall is completely dropping ICMP traffic.
Application Layer (HTTP Check): If the server responds to Pings but fails HTTP checks, the machine is online but the web server software (like Apache or Nginx) has crashed. Look for specific HTTP response headers like 500 Internal Server Error (backend app crash) or ⁄503 Service Unavailable.
Transport Layer (TCP / UDP Port Check): Test the exact port your service relies on (e.g., Port 22 for SSH, Port 443 for HTTPS, or Port 3306 for MySQL). If the connection returns Connection refused, the server is running but that specific daemon is dead. 2. Differentiate Local vs. Global Downtime
A major advantage of using Check-Host infrastructure is verifying if the server is down for everyone or just a subset of users. Check Host Pro 1.1.11 – AB-Tools.com
Leave a Reply