Chapter 4: Linux Ops Refresh for DevOps
4.7 Worked triage story — peak traffic
Use this story in interviews. Names are practice only.
Priya gets a ping: badge API profile page times out at 13:10. She does not start by rewriting the API.
- SSH into the VM.
df -h—/is at 62%, not full. Disk is fine.systemctl status badge-api— Active: failed. Process is dead.journalctl -u badge-api -n 30 --no-pager— last line shows the app could not open a file after a bad deploy path.ss -tlnp— nothing on 8080. The shop counter is empty because the process died.- She fixes the path in the unit or app config (lab: correct the working directory),
sudo systemctl start badge-api,curl -I http://localhost:8080/health, then follows logs once more.
Notice what she skipped: VPC redesign, DNS lectures, inventing cloud prices. She operated the machine she already had from the AWS course.
Ravindra Bagale's Tip
Incident call madhe students thodach "network issue" mhanun close kartat. Teen checks (process, port, disk) + ek log line — he bolnya sathi ready theva. Dhyan rakho!
Practice task
Rewrite Priya's six steps as a checklist you will keep in your notes. Add one extra line: "If localhost curl works but phone browser fails, check Security Group / firewall next (AWS course)."