systemctl Command: Manage systemd Services

Quick take: The systemctl command controls systemd services. Use systemctl status name to check a service, start/stop/restart to control it, and enable to start it automatically at boot. Most actions need sudo.

Introduction

The systemctl command is the control centre for systemd, the init system on nearly every modern Linux distribution. It starts and stops services, enables them to run at boot, shows their status and logs, and reloads their configuration — making it essential for managing web servers, databases, and any background service.

This guide covers the core service actions, enabling services at boot, checking status, and reloading configuration safely.

Syntax

The basic syntax of the systemctl command is:

systemctl [COMMAND] [SERVICE]

Common Options and Parameters

The most useful options and parameters for the systemctl command:

Practical Examples

Real systemctl commands you can run today:

# Check a service's status
systemctl status nginx
# Start and stop a service
sudo systemctl start nginx
# Restart after a config change
sudo systemctl restart nginx
# Reload without dropping connections
sudo systemctl reload nginx
# Enable a service to start at boot
sudo systemctl enable nginx
# Enable and start in one step
sudo systemctl enable --now nginx
# List all running services
systemctl list-units --type=service --state=running

Creating Your Own systemd Service

One of systemd's most useful features is how easily you can turn any script or program into a managed service that starts at boot and restarts on failure. You write a small unit file:

# /etc/systemd/system/myapp.service
[Unit]
Description=My App
After=network.target

[Service]
ExecStart=/usr/bin/node /srv/myapp/server.js
Restart=on-failure
User=myapp

[Install]
WantedBy=multi-user.target

Then reload systemd and enable it: sudo systemctl daemon-reload followed by sudo systemctl enable --now myapp. Your program now gets automatic startup, restart-on-crash, and centralised logging through journalctl — for free.

Inspecting Failed Services

When a service will not start, systemctl and journalctl together tell you why. Start with systemctl status name, which shows the current state and the last few log lines, then dig deeper with the journal.

# List everything that failed to start
systemctl --failed

# Full logs for one service since the last boot
journalctl -u myapp -b --no-pager

# Why did it exit? Check the result and exit code
systemctl status myapp

The --failed view is a fast health check for a whole machine, and pairing it with journalctl -u turns a vague “it won't start” into a specific error you can fix.

Tips and Best Practices

• enable --now starts a service immediately and enables it at boot in a single command.
• Prefer reload over restart when a service supports it — it applies config changes without dropping active connections.
• After editing a unit file, run sudo systemctl daemon-reload so systemd picks up the changes before you restart the service.

Final Thoughts

systemctl is the single command for managing services on modern Linux. Learn status, start/stop/restart, reload, and enable, and you can control any service and ensure it survives a reboot. Pair it with journalctl to read a service's logs when something goes wrong.