Skip to content
Clairos Learn

Server operations · Lesson 1 of 36 · 12 minutes

Server admin

Inspect simulated processes, services, and web server config like a cautious admin.

Mastery 0/3Run itExplain itApply it
learner@clairosSimulated Linux lab
learner@clairos:~ $
↑ history · Tab complete · Ctrl+C cancel · Esc, Tab to leaveExit 0

Understand the pattern

Inspection prevents blind service changes.

ps
Inspect a bounded snapshot of simulated processes.

A process being present does not prove that its service can handle requests.

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.

cat
Read one or more files to standard output without editing their contents.

Reading a source file should precede changing it; avoid printing real secrets.

Worked example and expected result
$ ps
PID  USER      COMMAND
1    root      systemd --simulated
42   www-data  nginx: static process
77   root      sshd: listener
108  learner   clairos-learn-terminal
126  root      cron

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.

$ cat /etc/nginx/sites-available/learn.conf
server {
  listen 443 ssl;
  server_name learn.clairos.ai;
  root /srv/www;
  location ^~ /api/learn/ { proxy_pass http://127.0.0.1:8010; }
  location ^~ /api/ { return 404; }
  add_header Content-Security-Policy "default-src 'self'; connect-src 'self'" always;
  # training config only
}

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 “Server admin”, which interpretation is safe?

Apply it elsewhere

Before adapting the systemctl workflow from “Server admin” to another server, what should you do?

Keep the momentum.

Complete the lab, then explain and apply the pattern.

Next: Service inspectionTry 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

  1. 01Service inspectionCompare simulated service status and journal output before taking action.Practice
  2. 02Nginx validationRead training nginx config and validate it without making real server changes.Practice
  3. 03Resource inspectionRead simulated disk, memory, uptime, and directory usage signals.Practice