Managing systemd Services on Linux: Full Guide

On almost every modern Linux server, background processes such as web servers, databases and mail services run via systemd. With systemd you manage these services: starting, stopping, restarting, enabling automatic startup, and checking that everything is running smoothly. In this article you’ll learn the most important commands, how to check logs, and how to create your own service, so you can resolve issues yourself without immediately calling your hosting provider.

What is systemd and why is it important

Systemd is the init system that, on most Linux distributions (Ubuntu, Debian, CentOS, AlmaLinux), starts as the first process and then manages all other services. Think of the web server (LiteSpeed or Apache), the database server (MySQL/MariaDB), SSH and cron jobs. Each service runs as a unit, with a configuration file describing how and when the service should start.

The advantage of systemd is that you can manage all services with one consistent set of commands, regardless of which software is behind them. This makes management clear and predictable, whether on your own VPS or on a managed server.

Basic commands for managing services

All systemd commands run through systemctl. Below are the most important commands you need to manage a service, for example nginx, mariadb or sshd.

• systemctl status nginx – shows the current status of the service
• systemctl start nginx – starts the service
• systemctl stop nginx – stops the service
• systemctl restart nginx – fully restarts the service
• systemctl reload nginx – reloads the configuration without breaking connections
• systemctl enable nginx – ensures the service starts automatically when the server boots
• systemctl disable nginx – disables automatic startup

Most commands require root privileges, so use sudo before them if you’re not logged in as root.

Viewing logs and troubleshooting

When a service fails to start or stops unexpectedly, systemctl status often already gives a first clue. For more detailed logs, use journalctl, systemd’s central logging service.

• journalctl -u nginx – shows all log lines for the nginx service
• journalctl -u nginx -f – follows logs live, useful during testing
• journalctl -u nginx --since "1 hour ago" – filters by time
• journalctl -p err – shows only error messages from all services

If a service keeps crashing shortly after starting, check whether the configuration is valid (for example with nginx -t for nginx) before restarting the service. If you’re running on a server with Plesk, you can also view many of these statuses graphically via the Plesk panel, including restarting services without a terminal.

Creating your own systemd service

If you’re running your own application or script that always needs to stay active, you can create your own unit file for it. Create a file at /etc/systemd/system/myapp.service with at least the following content:

• [Unit] with a description and dependencies (such as network)
• [Service] with the command to start the application, the restart policy, and optionally the user the process should run as
• [Install] with the target (usually multi-user.target) so the service starts automatically on boot

After creating it, run systemctl daemon-reload so systemd recognizes the new file, and then systemctl enable --now myapp to start the service and enable it to start automatically.

If you’re managing multiple of your own services on a VPS, it’s worth setting a clear restart policy (Restart=on-failure), so the service recovers automatically after a crash. If you’re unsure about the right settings for your web hosting environment, check the knowledge base for more background information.