Server operations · Lesson 2 of 36 · 9 minutes

Service inspection

Compare simulated service status and journal output before taking action.

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 nginx status
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.
2
Read nginx journal
Run journalctl -u nginx.
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
```
Remember: A relevant unit and time range are more useful than an unfiltered wall of logs.
3
Tail error log
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.

Understand the pattern

Service triage is a habit of status plus evidence.

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

$ 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

May 26 08:10:00 clairos-learn nginx[42]: configuration file syntax is ok
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.

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 “Service inspection”, 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 relevant unit and time range are more useful than an unfiltered wall of logs.

Apply it elsewhere

Before adapting the journalctl workflow from “Service inspection” 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: Nginx validation 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