Q: A critical web server is unresponsive, butping still works. SSH connection is refused. What could be the issue and how would you resolve it?
If ping works but ssh is refused, the server is up (network layer is fine) but the SSH daemon (sshd) is either down, rejecting connections (e.g., max connections reached, TCP wrappers), or a local firewall is blocking port 22.
Want to master this scenario in a live sandbox? The Linux Foundation's Certified System Administrator (LFCS) & SRE Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "During an on-call shift, our alerts triggered when a critical Linux production server exhibited this behavior. The interviewer is testing: Basic system troubleshooting, understanding of SSH vs. ICMP.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
If ping works but ssh is refused, the server is up (network layer is fine) but the SSH daemon (sshd) is either down, rejecting connections (e.g., max connections reached, TCP wrappers), or a local firewall is blocking port 22.
- Is
sshdrunning?systemctl status sshd - Check logs:
journalctl -u sshdor/var/log/auth.log - Check firewall rules:
iptables -Lorufw status
Remediation & Permanent Safeguards
To resolve: If physical or console access (like AWS Systems Manager or a hypervisor console) is available, I would log in and check: If it's an Out Of Memory (OOM) issue, sshd might have been killed by the OOM killer. I'd reboot the instance via the cloud provider console if no other access is possible to restore service, then investigate /var/log/messages after recovery.
- Is sshd running? systemctl status sshd
- Check logs: journalctl -u sshd or /var/log/auth.log
- Check firewall rules: iptables -L or ufw status
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Issuing immediate kill -9 (SIGKILL) commands rather than allowing graceful termination via kill -15 (SIGTERM) when configuring critical server unresponsive SIGKILL immediately halts execution without allowing processes to flush memory buffers, commit database transactions, or remove stale PID locks.
-
Overlooking file system inode exhaustion (df -i) when diagnosing 'No space left on device' errors when configuring critical server unresponsive
Millions of small files or unrotated session tokens can exhaust available file system inodes even when standard disk storage (
df -h) shows ample free space. - Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring critical server unresponsive Reaching file descriptor exhaustion throws 'Too many open files' errors, preventing services from accepting new TCP client socket connections.
-
Permitting defunct zombie processes to accumulate without fixing parent process SIGCHLD waitpid reaping when configuring critical server unresponsive
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).