{"id":20113,"date":"2023-10-23T09:10:36","date_gmt":"2023-10-23T09:10:36","guid":{"rendered":"https:\/\/webhostinggeeks.com\/howto\/?p=20113"},"modified":"2023-10-23T09:12:03","modified_gmt":"2023-10-23T09:12:03","slug":"how-to-list-manage-and-troubleshoot-services-in-ubuntu","status":"publish","type":"post","link":"https:\/\/webhostinggeeks.com\/howto\/how-to-list-manage-and-troubleshoot-services-in-ubuntu\/","title":{"rendered":"How to List, Manage, and Troubleshoot Services in Ubuntu"},"content":{"rendered":"

\"How<\/p>\n

Ubuntu, a popular Linux distribution, offers a robust system for managing services. These services are background processes that start during boot or when manually invoked. They play a pivotal role in ensuring that the system runs smoothly, handling tasks like network management, logging, and more.<\/p>\n

For webmasters and administrators, understanding how to manage these services is crucial. Knowing how to list, manage, and troubleshoot these services can be the difference between a smoothly running server and one riddled with issues.<\/p>\n

Let’s get started.<\/p>\n

Understanding Systemd<\/h2>\n

Ubuntu has transitioned to using systemd as its init system. This means that systemd is responsible for bootstrapping the user space and managing system processes. Before diving into commands, it’s essential to understand this shift as most service management commands will revolve around the systemctl utility provided by systemd.<\/p>\n

When you boot up your Ubuntu server, the first process that runs is systemd. It’s responsible for initializing other services like the network manager, SSH daemon, and more. Think of systemd as the manager overseeing all other services on your system.<\/p>\n

Listing All Services<\/h2>\n

To list all services, whether active, inactive, or failed, use the following command:<\/p>\n

sudo systemctl list-units --type=service --all<\/pre>\n
This command provides a comprehensive list, showing the status of each service.<\/p>\n
For example:<\/p>\n
\r\n  apache2.service       loaded active running   The Apache HTTP Server\r\n  cron.service          loaded active running   Regular background program processing daemon\r\n  ssh.service           loaded active running   OpenBSD Secure Shell server\r\n  ...\r\n<\/pre>\n
Checking the Status of a Specific Service<\/h2>\n
If you want to check the status of a specific service, use:<\/p>\n
sudo systemctl status [service-name]<\/pre>\n
Replace [service-name] with the name of the service you’re interested in.<\/p>\n
For example:<\/p>\n
\r\n  ssh.service - OpenBSD Secure Shell server\r\n  Loaded: loaded (\/lib\/systemd\/system\/ssh.service; enabled; vendor preset: enabled)\r\n  Active: active (running) since Tue 2023-10-24; 1 day ago\r\n  ...\r\n<\/pre>\n
Starting and Stopping Services<\/h2>\n
To start a service:<\/p>\n
sudo systemctl start [service-name]<\/pre>\n
For example:<\/p>\n
\r\nsudo systemctl start apache2\r\n<\/pre>\n
The status should now show active (running).<\/p>\n
To stop a service:<\/p>\n
sudo systemctl stop [service-name]<\/pre>\n
For example:<\/p>\n
\r\nsudo systemctl stop apache2\r\n<\/pre>\n
After this, if you check the status, it should show inactive (dead).<\/p>\n
Enabling and Disabling Services at Boot<\/h2>\n
To ensure a service starts at boot:<\/p>\n
sudo systemctl enable [service-name]<\/pre>\n
For example, to ensure the Cron service starts at boot:<\/p>\n
\r\nsudo systemctl enable cron\r\n<\/pre>\n
\r\nSynchronizing state of cron.service with SysV service script with \/lib\/systemd\/systemd-sysv-install.\r\nExecuting: \/lib\/systemd\/systemd-sysv-install enable cron\r\n<\/pre>\n
To disable a service from starting at boot:<\/p>\n
sudo systemctl disable [service-name]<\/pre>\n
Troubleshooting Failed Services<\/h2>\n
If a service fails, you can inspect its logs using:<\/p>\n
sudo journalctl -u [service-name]<\/pre>\n
This command displays logs specific to the service, helping pinpoint issues.<\/p>\n
For example, if the Apache service fails to start, you can inspect its logs:<\/p>\n
sudo journalctl -u apache2<\/pre>\n
Oct 24 08:00:15 ubuntu-server apache2[1234]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message\r\n  ...\r\n<\/pre>\n
This log entry indicates an issue with the server’s domain name configuration in Apache.<\/p>\n
Commands Mentioned<\/h2>\n