Q: An incident occurred where a server ran out of memory, but the `oom-killer` didn't trigger, causing a complete kernel hang (hard lockup). How do you configure the kernel to automatically panic and reboot if this happens again?
If the system becomes completely unresponsive in a hard lockup or OOM stall, manual intervention is slow. I would configure the kernel to panic and automatically reboot.
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: Sysctl tuning, kernel panic parameters, high availability recovery.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."
Initial Diagnostics & Root Cause Analysis
If the system becomes completely unresponsive in a hard lockup or OOM stall, manual intervention is slow. I would configure the kernel to panic and automatically reboot. This allows auto-scaling groups or load balancers to immediately replace or re-route traffic from the failed node.
kernel.panic = 10(Reboot 10 seconds after a panic)vm.panic_on_oom = 1(Panic if the kernel hits an unresolvable OOM state, rather than trying to kill processes if the killer is disabled or failing)kernel.hung_task_panic = 1(Panic if tasks are hung for too long, like theDstate lockups).
Remediation & Permanent Safeguards
Using sysctl: These settings are added to /etc/sysctl.conf to persist across reboots, forcing the system to "fail fast" and rely on infrastructure redundancy.
- kernel.panic = 10 (Reboot 10 seconds after a panic)
- vm.panic_on_oom = 1 (Panic if the kernel hits an unresolvable OOM state, rather than trying to ki...
- kernel.hung_task_panic = 1 (Panic if tasks are hung for too long, like the D state lockups).
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 incident occurred server 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 incident occurred server
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 incident occurred server 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 incident occurred server
Zombie processes consume process table entries; accumulating zombies can exhaust the system maximum PID limit (
pid_max).