Linux31: Capstone: 3 A.M. Incident

A full end-to-end incident pulling together core investigation, permission remediation, process restart, and reporting

Objective

Learner can independently investigate, diagnose root cause, remediate permissions, and restore services

Mission

Monitoring alert: app-srv-03 is down. (1) Inspect logs at ~/cases/case-1042/logs/app-srv-03-service.log to identify root cause, (2) fix broken permissions on /etc/solvinme/app.conf using sudo chmod, (3) execute ~/cases/case-1042/restart-service.sh.

Commands you may need to solve this lab

tailgrepsudo chmod./restart-service.sh

Questions

1. What root cause was logged in app-srv-03-service.log?

2. Which exact permission fix allows the service to read the configuration file?

3. How do you verify the deployment-agent service process is running after executing restart-service.sh?

Machine Offline

Isolated container is offline

Click "Start Machine" to boot your sandbox instance and choose your preferred interface