When I make changes to a Linux server, restarting the affected service is often the fastest way to apply them. However, running the wrong command or restarting a service without checking its configuration can create unnecessary downtime.
The basic command is simple:
sudo systemctl restart service-name
Replace service-name with the actual unit you want to restart, such as nginx, apache2, httpd, mysql, or sshd. In this guide, I will show you how to restart a service, verify that it is running, inspect errors, and avoid common mistakes.
What Does the systemctl Restart Command Do?
The systemctl command controls services managed by systemd, the service manager used by most modern Linux distributions.
When you run:
sudo systemctl restart nginx
systemd stops the Nginx service and then starts it again. This process allows the application to load configuration changes, clear temporary problems, or recover from an unresponsive state.
A restart may briefly interrupt the service. For a web server, this could produce a short period when requests cannot be handled. That is why it is important to validate configuration files before restarting critical services.
Find the Correct Service Name First
A common reason a restart command fails is that the wrong service name was entered. Service names may also differ between Linux distributions.
For example, Apache is commonly called apache2 on Debian-based systems. On Red Hat-based systems, it is generally called httpd.
You can search installed service units with:
systemctl list-unit-files –type=service
To view currently loaded services, run:
systemctl list-units –type=service
You can narrow the results with grep:
systemctl list-units –type=service | grep -i nginx
Once you identify the correct unit, use its name in the restart command. Adding .service is optional in most cases, so nginx and nginx.service usually produce the same result.
Restart a Service Step by Step
Check Its Current Status
Before making changes, check whether the service is active, inactive, or already failing:
sudo systemctl status nginx
The output normally shows its current state, process ID, recent activity, and a few log entries.
You can request a shorter response with:
systemctl is-active nginx
Typical results include active, inactive, failed, or activating.
Restart the Service
Run the restart command after confirming the correct service name:
sudo systemctl restart nginx
A successful command normally produces no terminal output. Silence does not automatically confirm that the application is healthy, so verification is still required.
Verify the Restart
Check the status again:
sudo systemctl status nginx
You should see active (running) when the restart succeeds. For a script-friendly check, use:
systemctl is-active nginx
For network applications, you should also test the actual service. A running web server unit, for example, might still have an application-level or connectivity problem.
Common Restart Examples
To restart Nginx:
sudo systemctl restart nginx
To restart Apache on Fedora, Rocky Linux, AlmaLinux, or RHEL:
To restart Apache on Ubuntu or Debian:
sudo systemctl restart apache2
To restart Apache on Fedora, Rocky Linux, AlmaLinux, or RHEL:
sudo systemctl restart httpd
To restart MySQL:
sudo systemctl restart mysql
Some systems may use:
sudo systemctl restart mysqld
To restart the OpenSSH server, the unit may be named ssh or sshd:
sudo systemctl restart ssh
sudo systemctl restart sshd
Be careful when restarting SSH on a remote server. Keep the current session open, validate the configuration, and test a second connection before closing your existing terminal.
Restart Versus Reload
Restart and reload are not identical operations.
A restart stops and starts the process:
sudo systemctl restart nginx
A reload asks the running application to reread its configuration without fully stopping:
sudo systemctl reload nginx
Reloading may reduce interruption, but it works only when the service supports reload operations.
A useful alternative is:
sudo systemctl reload-or-restart nginx
This reloads the service when possible and restarts it when reload support is unavailable.
When to Use daemon-reload
The daemon-reload command is often confused with a service restart:
sudo systemctl daemon-reload
After editing a custom unit file, use:
sudo systemctl daemon-reload
sudo systemctl restart myapp.service
The first command reloads systemd’s definitions. The second restarts the application using the updated unit configuration.
Validate Configuration Before Restarting
A restart can cause a working service to fail when its configuration contains an error. Many applications provide validation commands.
For Nginx:
sudo nginx -t
For Apache:
sudo apachectl configtest
For OpenSSH:
sudo sshd -t
If validation reports an error, fix it before restarting. This small step is especially important for production servers and remote systems.
Fix a Service That Will Not Restart
Start by examining the full status output:
sudo systemctl status service-name
Then inspect recent logs:
sudo journalctl -u service-name –since “10 minutes ago”
For detailed errors related to a failed unit, run:
sudo journalctl -xeu service-name
Common causes include invalid configuration syntax, incorrect file permissions, missing directories, unavailable dependencies, port conflicts, and incorrect environment variables.
You can check whether another process is using a required port with:
sudo ss -lntp
After correcting the underlying issue, clear the failed state when necessary:
sudo systemctl reset-failed service-name
Then attempt the restart again.
Frequently Asked Questions
1. How do I use How to Restart Services Using Systemctl safely?
Check the current status, validate the application configuration, restart the correct unit, and verify both the service state and application response afterward.
2. Do I need sudo to restart a service?
Most system services require administrative privileges, so regular users generally need to place sudo before the command.
3. Does restarting a service enable it at boot?
No. Restarting affects the current session only. To enable a service at startup, run:
sudo systemctl enable service-name
To enable and start it immediately, use:
sudo systemctl enable –now service-name
4. Why does systemctl restart show no output?
A successful command commonly returns without a message. Use systemctl status, systemctl is-active, and application-level testing to confirm success.
The Final Command Check
I rely on How to Restart Services Using Systemctl as a simple workflow rather than a single command. I first confirm the unit name, check its current condition, validate configuration changes, restart it, and then verify the result.
That approach prevents many avoidable outages. When a restart fails, the status output and journalctl logs usually reveal the real cause. The restart command may be short, but careful verification is what makes Linux service management reliable.
Leave a Reply