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

Q: The `journald` logs on a server are consuming excessive disk space. How do you configure log rotation and size limits for `systemd-journald`?

systemd-journald stores logs in binary format under /var/log/journal/ (persistent) or /run/log/journal/ (volatile, lost on reboot).

#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 journal management, log retention policies.. 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 journal management, log retention policies.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

systemd-journald stores logs in binary format under /var/log/journal/ (persistent) or /run/log/journal/ (volatile, lost on reboot).

  • SystemMaxUse=500M: Maximum total disk space the journal can use.
  • SystemKeepFree=1G: Always keep at least 1GB free on the partition.
  • SystemMaxFileSize=50M: Maximum size of individual journal files before rotation.
2️⃣

Remediation & Permanent Safeguards

To control disk usage, edit /etc/systemd/journald.conf: Key directives: Apply immediately: systemctl restart systemd-journald To manually vacuum old logs right now:

[Journal]
SystemMaxUse=500M
SystemKeepFree=1G
SystemMaxFileSize=50M
MaxRetentionSec=30day
  • MaxRetentionSec=30day: Delete entries older than 30 days.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: SystemMaxUse=500M: Maximum total disk space the journal can use.."
⚡ 60-Second Elevator Pitch Talking Points
  • SystemMaxUse=500M: Maximum total disk space the journal can use.
  • SystemKeepFree=1G: Always keep at least 1GB free on the partition.
  • SystemMaxFileSize=50M: Maximum size of individual journal files before rotation.
⛔ 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 journald logs server 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 journald logs 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.
  3. Exhausting open file descriptor allocations (ulimit -n) under intensive concurrent socket connections when configuring journald logs server 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 journald logs server 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 →