Troubleshooting · Lesson 10 of 26 · 8 minutes

Troubleshooting checkpoint

Complete a focused triage loop.

Open the lab Course map

Mastery 0/3Run itExplain itApply it

learner@clairos:~ $

↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Your objectives

Hints are always available. Wrong turns never cost XP.

1
Check load
Run uptime.
Hint & worked example
Read simulated runtime and load information.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
uptime
```
Remember: Load average is not a direct CPU percentage.
2
Check service
Run systemctl status nginx.
Hint & worked example
Inspect or change a simulated systemd service. Status, active state, and unit configuration reveal different evidence.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
systemctl status nginx
```
Remember: A service can be active while an application endpoint is unhealthy; verify both layers.
3
Read recent logs
Run journalctl -u nginx -n 2.
Hint & worked example
Read the training journal by unit or a bounded line window.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
journalctl -u nginx -n 2
```
Remember: A relevant unit and time range are more useful than an unfiltered wall of logs.
4
Write triage note
Run printf triage-complete | tee lab/triage.txt.
Hint & worked example
Format data deliberately, including separators and final newlines. Copy a stream both to a file and standard output; -a appends.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
printf triage-complete | tee lab/triage.txt
```
Remember: A format string controls output; a newline is data, not an automatic guarantee. tee can overwrite a file even though the output is also visible on screen.

Understand the pattern

Junior operators build confidence by gathering evidence before changing systems.

uptime: Read simulated runtime and load information.
Load average is not a direct CPU percentage.
systemctl: Inspect or change a simulated systemd service. Status, active state, and unit configuration reveal different evidence.
A service can be active while an application endpoint is unhealthy; verify both layers.
journalctl: Read the training journal by unit or a bounded line window.
A relevant unit and time range are more useful than an unfiltered wall of logs.
printf: Format data deliberately, including separators and final newlines.
A format string controls output; a newline is data, not an automatic guarantee.
tee: Copy a stream both to a file and standard output; -a appends.
tee can overwrite a file even though the output is also visible on screen.

Worked example and expected result

$ uptime

 10:26:04 up 12 days,  4:18,  1 learner,  load average: 0.04, 0.03, 0.01

Exit status: 0. The command completed successfully in the training fixture.

$ systemctl status nginx

nginx.service - simulated nginx
   Loaded: loaded
   Active: active
   Notes: serving the simulated static learn site

Exit status: 0. The command completed successfully in the training fixture.

$ journalctl -u nginx -n 2

May 26 08:10:01 clairos-learn nginx[42]: started static training site
May 26 08:20:05 clairos-learn nginx[42]: access denied for /api/test by static rule

Exit status: 0. The command completed successfully in the training fixture.

$ printf triage-complete | tee lab/triage.txt

triage-complete

Exit status: 0. The command completed successfully in the training fixture.

Try a variation

Repeat this workflow in the sandbox with a different scratch filename. Keep the system fixtures unchanged and compare the observed output with your expectation before moving on.

Explain it

In “Troubleshooting checkpoint”, which interpretation is safe?A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.A service can be active while an application endpoint is unhealthy; verify both layers.

Apply it elsewhere

Before adapting the systemctl workflow from “Troubleshooting checkpoint” to another server, what should you do?Skip output inspection whenever the command is familiar.Confirm the current directory, target identity, permissions, and the installed command behavior first.Paste the training paths unchanged into production.

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Incident website down Try an incident drill

Anonymous lesson and mastery progress lasts for this session. Sign in to keep synced lesson XP between sessions; mastery stays device-local. No speed bonus, lost lives, or hint penalties.

Keep learning

GNU Coreutils manual · GNU Bash manual