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

Q: A cron job configured to run every midnight is failing, but when you run the script manually as the same user, it works perfectly. Why?

This is almost always an environment variable issue.

#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: Cron environment variations, absolute paths.. 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: Cron environment variations, absolute paths.. I structure my answer around systematic triage first, root cause analysis second, and permanent remediation third."

1️⃣

Initial Diagnostics & Root Cause Analysis

This is almost always an environment variable issue.

  • The script should use absolute paths for every command (e.g., /usr/bin/curl instead of curl).
  • Alternatively, the crontab can explicitly source the environment at execution:
  • Any variables needed by the script should be explicitly exported at the top of the script.
2️⃣

Remediation & Permanent Safeguards

When a user logs in interactively, profiles like ~/.bashrc and /etc/profile are sourced, setting up $PATH, aliases, and application-specific variables. Cron executes with a heavily restricted, minimal environment (often just /usr/bin:/bin). To fix this: 0 0 * * * . /home/user/.bash_profile; /home/user/script.sh

💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: The script should use absolute paths for every command (e.g., /usr/bin/curl instead of curl).."
⚡ 60-Second Elevator Pitch Talking Points
  • The script should use absolute paths for every command (e.g., /usr/bin/curl instead of curl).
  • Alternatively, the crontab can explicitly source the environment at execution:
  • Any variables needed by the script should be explicitly exported at the top of the script.
⛔ 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 cron configured every 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 cron configured every 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 cron configured every 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 cron configured every 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 →