Managing System Services with systemctl

1. What is a Service?

On a Linux server, many programs run silently in the background, waiting for requests or performing scheduled tasks. These background processes are called services or daemons. Examples include:

• sshd: The SSH daemon that listens for your remote login connections.
• nginx or apache2: Web servers that listen for browser requests to serve web pages.
• cron: A service that runs scheduled jobs.

The program responsible for starting, stopping, and supervising all these services (and the entire system after the kernel boots) is called the init system. For nearly all modern Linux distributions, the init system is systemd. And the primary tool we use to talk to systemd is systemctl.

To learn a bit more about the role of systemd, let's turn to a helpful article.

2. Getting a Service to Manage

To make this lesson practical, you'll need a service to manage. Let's install the Apache web server, a very common service. Use the apt command you learned in the previous lesson.

Open your terminal and run:
sudo apt update
sudo apt install apache2

Once it's installed, Apache is running as a service on your system, managed by systemd. Now, let's learn how to control it.

3. The Core systemctl Commands

We'll now walk through the essential systemctl commands. These six actions—status, start, stop, restart, enable, and disable—form the bedrock of service management in Linux.

The following video gives a fantastic, hands-on demonstration of these core commands.

Let's break down those key commands with some explanations.

Checking a Service's Status

This is your first step in any troubleshooting scenario. The status command gives you a complete snapshot of a service.

systemctl status apache2.service

(Note: systemd is smart enough that you can usually leave off the .service suffix, but it's good practice to be explicit.)

The output tells you:

• Loaded: If systemd found the service's configuration file.
• Active: The most important line. It shows if the service is active (running), inactive (dead), or failed.
• Enabled / Disabled: Whether the service is configured to start automatically on boot.
• Logs: The most recent log entries from the service, which are invaluable for debugging.

Controlling the Current Session: start, stop, restart

These commands affect the service right now, but they don't change what happens on the next reboot. All these commands require sudo because you're changing the state of the system.

• To start a service:
  sudo systemctl start apache2

• To stop a service:
  sudo systemctl stop apache2

• To stop and then start a service:
  sudo systemctl restart apache2

You typically restart a service after you've changed its configuration file, so it can re-read the new settings.

Controlling Boot Behavior: enable and disable

These commands determine whether a service starts automatically when the server boots up. This is critical for ensuring essential services are always available after a reboot or planned maintenance.

• To make a service start at boot:
  sudo systemctl enable apache2

• To prevent a service from starting at boot:
  sudo systemctl disable apache2

Crucial Point: disable does not stop a service that is currently running. Likewise, enable does not start a service that is currently stopped. These commands only affect boot-time behavior.

A very useful shortcut exists to enable and start a service in one go:
sudo systemctl enable --now apache2

This is perfect for when you've just installed a new service and want it running immediately and permanently.

For a quick reference, this Red Hat article provides a concise summary of these commands.

4. Your Turn: Hands-On Practice

Time to use your "katana." Let's apply these commands to the apache2 service you installed.

1. Check the initial state: After installation, Ubuntu typically starts and enables services. Let's verify.
   systemctl status apache2
   Is it active? Is it enabled?

2. Stop the service: Let's take the web server offline.
   sudo systemctl stop apache2

3. Verify it's stopped:
   systemctl status apache2
   The status should now say inactive (dead). If you open a web browser in your VM and go to http://localhost, it should fail to connect.

4. Start the service: Bring it back online.
   sudo systemctl start apache2
   Check the status again and try the browser. It should work now.

5. Disable the service: Configure the server so Apache won't start on the next boot.
   sudo systemctl disable apache2
   Check the status. The service should still be active (running), but the "Loaded" line should now say disabled.

6. Enable the service: Set it back to normal behavior.
   sudo systemctl enable apache2
   Verify with status that it now says enabled.

Conclusion

Excellent work. You now have the fundamental commands to control any service on a modern Linux system. This is a non-negotiable skill for anyone in a sysadmin or data center role, and you can now confidently speak to how and why you would use these commands.

Key Takeaways:

• systemd is the init system that manages services on modern Linux.
• systemctl is the command-line tool you use to interact with systemd.
• status is your go-to command for diagnostics.
• start / stop / restart control the service in the current session.
• enable / disable control the service's behavior at boot time.
• The --now flag is a convenient shortcut to enable and start a service simultaneously.

In our next lesson, we will build directly on this. Now that you can manage a web service, we'll learn how to configure a static IP address for your Linux server. This will ensure that other computers on the network can reliably find and communicate with your services.