⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Linux & SRE Interview Questions Scenario 44 of 135 in Linux & SRE
Junior / Associate DevOps [L1] Linux Linux / SRE — Scenario-Based Interview Questions Core Fundamentals [L1]
🎯 Target Role / Context: Linux Scenario #1 (L1) · Linux / SRE — Scenario-Based Interview Questions

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.

#Linux #L1 #SRE #Systems #Troubleshooting
🎙️ Candidate Opening & Architectural Context
""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.""
Advertisement
⚡ Recommended Practice Lab

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."

1️⃣

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 sshd running? systemctl status sshd
  • Check logs: journalctl -u sshd or /var/log/auth.log
  • Check firewall rules: iptables -L or ufw status
2️⃣

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.

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Is sshd running? systemctl status sshd."
⚡ 60-Second Elevator Pitch Talking Points
  • Is sshd running? systemctl status sshd
  • Check logs: journalctl -u sshd or /var/log/auth.log
  • Check firewall rules: iptables -L or ufw status
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. 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.
  2. 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.
  3. 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.
  4. 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).
Advertisement
Want more Linux & SRE scenarios?
Explore our complete collection of scenario-based Linux & SRE interview runbooks.
Browse All Linux & SRE Questions →