⚡ ~/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 83 of 135 in Linux & SRE
Senior DevOps / SRE [L2] Linux Linux / SRE — Scenario-Based Interview Questions Production Scenario [L2]
🎯 Target Role / Context: Linux Scenario #41 (L2) · Linux / SRE — Scenario-Based Interview Questions

Q: You need to run a long-lived background service that must automatically restart if it crashes. You also want to manage its lifecycle (start/stop/restart) from a single systemd unit file. How do you configure systemd for auto-restart, and what are the critical directives?

Modern Linux systems use systemd to manage services instead of SysVinit scripts. A systemd unit file (e.g., /etc/systemd/system/myapp.service) must configure restart behavior explicitly.

#Linux #L2 #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: Systemd service definition, restart policies, type directives.. 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: Systemd service definition, restart policies, type directives.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

Modern Linux systems use systemd to manage services instead of SysVinit scripts. A systemd unit file (e.g., /etc/systemd/system/myapp.service) must configure restart behavior explicitly.

  • Type=simple (default): The process runs in the foreground. Systemd considers the service active when the process starts.
  • Type=forking: The process daemonizes itself (old SysVinit behavior). Systemd waits for the parent to exit before considering it active.
  • Restart=on-failure: Automatically restart if the process exits with a non-zero exit code.
2️⃣

Remediation & Permanent Safeguards

Key directives: Example configuration: Then enable and start: systemctl daemon-reload && systemctl enable myapp && systemctl start myapp.

[Unit]
Description=My Critical Application
After=network.target

[Service]
Type=simple
ExecStart=/usr/local/bin/myapp
Restart=on-failure
RestartSec=5
StandardOutput=journal
StandardError=journal

[Install]
WantedBy=multi-user.target
  • RestartSec=5: Wait 5 seconds between restart attempts to avoid restart loops.
  • StandardOutput=journal and StandardError=journal: Capture all logs directly to journald (no separate log files needed).
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: Type=simple (default): The process runs in the foreground. Systemd considers the service active when the process starts.."
⚡ 60-Second Elevator Pitch Talking Points
  • Type=simple (default): The process runs in the foreground. Systemd considers the service active w...
  • Type=forking: The process daemonizes itself (old SysVinit behavior). Systemd waits for the parent...
  • Restart=on-failure: Automatically restart if the process exits with a non-zero exit code.
⛔ 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 need long lived 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 need long lived 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 need long lived 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 need long lived 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 →