Text and logs · Lesson 10 of 38 · 7 minutes

Journal windows

Read only the last few simulated journal lines.

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
Recent nginx journal
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.
2
Recent nginx errors
Run tail -n 2 /var/log/nginx-error.log.
Hint & worked example
Show the end of an input; -n selects the number of lines.
The command outcome must match the task, including successful access or the explicitly requested failure.
```
tail -n 2 /var/log/nginx-error.log
```
Remember: This browser lab snapshots output; it does not keep a live tail -f stream.
3
Recent ssh journal
Run journalctl -u ssh -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 ssh -n 2
```
Remember: A relevant unit and time range are more useful than an unfiltered wall of logs.

Understand the pattern

Small windows reduce noise during incident triage.

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.
tail: Show the end of an input; -n selects the number of lines.
This browser lab snapshots output; it does not keep a live tail -f stream.

Worked example and expected result

$ 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.

$ tail -n 2 /var/log/nginx-error.log

May 26 08:10:01 [notice] nginx: using fake static configuration
May 26 08:20:05 [warn] nginx: /api/test returned 404 by design

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

$ journalctl -u ssh -n 2

May 26 08:18:33 clairos-learn sshd[118]: password authentication refused
May 26 08:21:44 clairos-learn sshd[141]: root login refused by policy

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 “Journal windows”, which interpretation is safe?This browser lab snapshots output; it does not keep a live tail -f stream.A command appearing in history proves it completed successfully.A successful first check guarantees that every dependent service is healthy.

Apply it elsewhere

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

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Kernel log basics 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