Linux Survival Basics
Read-onlyCheck If a Service Is Active
Full status output is noisy when a script, checklist, or quick human check only needs the current active state.
Command
systemctl is-active nginx
Before you run this
System impact: Read-only. Low when scoped to the shown target.
When not to use it: Do not use it as a replacement for endpoint checks, logs, or dependency checks.
Expected output
active
System impact
Read-only. Nothing changes. systemctl prints a compact state such as active, inactive, failed, or activating.
Recovery / rollback: no state is changed.
When to use it
Use in runbooks, smoke checks, and quick recovery validation after restarting a service.
When not to use it
Do not use it as a replacement for endpoint checks, logs, or dependency checks.
Watch this command run
Command transcript
This sanitized transcript shows the commands and output shape without exposing host details.
$ systemctl is-active nginx
active
$ systemctl status nginx --no-pager --lines=30
● nginx.service - A high performance web server
Loaded: loaded (/lib/systemd/system/nginx.service; enabled)
Active: active (running) since Thu 2026-06-25 14:12:10 CDT; 18min ago
Main PID: 842 (nginx)
Tasks: 3
Memory: 12.4M
Jun 25 14:12:10 vps nginx[842]: start worker processes
Jun 25 14:12:11 vps nginx[842]: ready for connections
View commands shown
These are the commands shown in the sanitized transcript.
Commands shown
systemctl is-active nginxsystemctl status nginx --no-pager --lines=30
next steps
Related commands
Inspect One Service Without Pager Traps
Make systemctl status safe for scripts, screenshots, and quick incident notes.
systemctl status nginx --no-pager --lines=30
Check Whether a Service Starts at Boot
Running now does not mean it will survive the next reboot.
systemctl is-enabled nginx
Read the Failure Cause in systemctl Status
The status page often tells you the failed startup step before you open every log.
systemctl status app-worker --no-pager --lines=50
Print the Exact systemd Exit Fields
Turn a noisy service failure into four fields you can paste into an incident note.
systemctl show app-worker --property=Result,ExecMainCode,ExecMainStatus,NRestarts --no-pager
Compare Failure Output With the Effective Unit
Put the failed step next to the unit config that created it.
systemctl status app-worker --no-pager --lines=50 && systemctl cat app-worker
Study mapping
Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.
Useful for
- LPIC-1 style command-line practice
- LFCS style performance tasks
- Linux+ style troubleshooting review
Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.