Mission 359

Capstone multi-signal outage

Correlate service, config, journal, listener, and capacity evidence for an outage.

Capstone labs
8 minutes Capstone Lesson 359 of 360
systemctlnginxjournalctlssdf
Lesson 359 of 360 0/360 lessons 0/17 missions Capstone labs · 8 minutes
0%
Continue View profile
Ops lab terminal Training lab
New learnerrank 0XP 0%complete
learner@clairos:/home/learner $ Unix ops lab: type a command, press Enter
Instructions 8 minutes

Click any instruction for the command details, the why, and the common mistake to avoid.

Check service state

Run systemctl status nginx.

systemctl status nginx
Validate the configuration

Run nginx -t.

nginx -t
Read recent service evidence

Run journalctl -u nginx -n 2.

journalctl -u nginx -n 2
Check listeners

Run ss -tulpn.

ss -tulpn
Check capacity

Run df -h.

df -h
Lesson support

What to notice while you play.

Objective

Build repeatable confidence with running an end-to-end outage investigation.

Hint

Start with systemctl status nginx, inspect the result, then continue in order.

Why it matters

Running an end-to-end outage investigation helps operators explain what they know before they change anything.

Common mistakes
  • Skipping the output that proves running an end-to-end outage investigation.
  • Changing several things before recording a baseline.
Reference

Commands in this lesson.

systemctl status <service>

Inspect simulated service status.

journalctl -u <service>

Read simulated service journal entries.

nginx -t

Validate training nginx configuration.

ss|ip

Inspect simulated sockets and addresses.

ssh|scp|ssh-keygen

Practice SSH inspection and dry-run transfer shapes without network access.

df|du|free|uptime

Inspect training resource and system health.