Fix Systemctl Command Not Found on Linux

fix systemctl command not found
fix systemctl command not found

Getting greeted with the Systemctl: command not found error upon running the systemctl command on your Linux system is one of the most common problems. This issue is sorted out for most of the Linux versions but has been seen still occurring on the PCs running an older distribution of Linux.

The reason for the error is probably that the older version doesn’t support the systemctl command, leading the PC to display the Systemctl: command not error instead of executing the respective command.

Luckily, this issue is pretty common and can be fixed easily by following a couple of simple steps. But before that, let’s have a little deeper look at the systemctl and systemdcommands and also the exact cause of the error.

What are about Systemctl and Systemd?

The error message i.e. “Systemctl: command not found” is directly indicating that the Systemclt Linux command is involved, it is a good practice to get a little info about it to understand it better.

The systemctl is originally a command-line utility offered by Linux to control and monitor one other command-line utility called the systemd command-line utility. Additionally, the systemctl is also used by Linux to control and inspect the system manager along with the systemd utility.

The general syntax of the systemctl command:

systemctl [option] [name]

Coming to the systemd command-line utility, it is actually a bundle of libraries, utilities, and daemons used to control the programs that run when the Linux system, boots up. It also manages the proper initiation of things like starting a journal of system activity. All in all, this utility functions as the main management utility for most Linux-based operating systems.

What is causing the “Systemctl: command not found” error?

Though there can be other causes in most cases, this issue occurs while using an older version of the Linux operating system. A lot of older Linux distributions uses the SysV init instead of systemd. And since the systemd command-line utility is used to control and monitor the systemd command-line utility, the older versions of Linux are not able to execute the systemclt command.

Here is an example of what the error message looks like:

[email protected]:~$ sudo systemctl start ufw
[sudo] password for bhanu:
sudo: systemctl: command not found 
[email protected]:~$

In the above example, I have tried to start the Ubuntu firewall by using the systemctl command which leads me to the “systemctl: command not fount” error.

How to Fix the “Systemctl: command not found” Error

Well, what to do now, if you don’t want to shift to any other version of Linux but still want to rectify the issue? Fortunately, this is possible, and here’s how.

1. Replace “systemctl” with “Service” command

The first and most convenient way to solve this is to use the service command in place of the systemctl command.

The service command helps in executing the SystemV ini script, used by the older version of Linux OS. Hence if you are not willing to install the Systemd utility then you can go with the fix to get your work done. The service command gives good control to start, stop or restart any services and daemons on your Linux system.

In a nutshell, service and systemctl commands functions in the same fashion. The only difference is in their compatibility with the command utilities that are responsible for the proper functioning of your Linux-based system.

Here, is an example illustrating the service command.

General Syntax for the service command:

sudo service [service_name] [action]

In the above syntax, the [action] is for assigning the action i.e. start, stop, restart, or status to the desired Linux service, provided in place of the [service_name] space.

Let’s try running the same command to start the ufw service using the service command. So, the execution command will be:

sudo service ufw start

Upon running the above command, you should get the following output:

[email protected]:~$ sudo service ufw start
[email protected]:~$ sudo service ufw status
● ufw.service - Uncomplicated firewall
   Loaded: loaded (/lib/systemd/system/ufw.service; enabled; vendor preset: enab
   Active: active (exited) since Mon 2020-09-28 11:22:34 IST; 1h 5min ago
     Docs: man:ufw(8)
  Process: 333 ExecStart=/lib/ufw/ufw-init start quiet (code=exited, status=0/SU
 Main PID: 333 (code=exited, status=0/SUCCESS)

Sep 28 11:22:34 ubuntu systemd[1]: Started Uncomplicated firewall.
Warning: Journal has been rotated since unit was started. Log output is incomple

And as you can see in the above output, there is no error line “Systemctl: command not found“. This is because, in order to run the ubuntu firewall, the service command was used instead of the systemctl command.

Similarly, you can also run other services. Here’s one more example.

sudo service apache2 start

The resulting output:

[email protected]:~$ sudo service apache2 status
● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: 
  Drop-In: /lib/systemd/system/apache2.service.d
   Active: active (running) since Mon 2020-09-28 11:22:47 IST; 1h 16min ago
  Process: 1172 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCE
 Main PID: 1248 (apache2)
    Tasks: 55 (limit: 4456)
   CGroup: /system.slice/apache2.service
           ├─1248 /usr/sbin/apache2 -k start
           ├─1249 /usr/sbin/apache2 -k start
           └─1250 /usr/sbin/apache2 -k start

Sep 28 11:22:43 ubuntu systemd[1]: Starting The Apache HTTP Server...
Sep 28 11:22:47 ubuntu apachectl[1172]: AH00112: Warning: DocumentRoot [/var/www
Sep 28 11:22:47 ubuntu apachectl[1172]: AH00558: apache2: Could not reliably det
Sep 28 11:22:47 ubuntu systemd[1]: Started The Apache HTTP Server.

[email protected]:~$ 

In the second example, we used the same service command to start the apache2 utility. By using the status action, we have got the info of the current status of the apache2 utility on our Linux system whether the apache2 is running or is inactive.

In a similar fashion, you can also use the stop action to stop the apache2 service. Something like this:

[email protected]:~$ sudo service apache2 stop
[email protected]:~$ sudo service apache2 status
lines 1--1...skipping...
● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/apache2.service.d
   Active: inactive (dead) since Mon 2020-09-28 12:42:06 IST; 1s ago
  Process: 4928 ExecStop=/usr/sbin/apachectl stop (code=exited, status=0/SUCCESS)
  Process: 1172 ExecStart=/usr/sbin/apachectl start (code=exited, status=0/SUCCESS)
 Main PID: 1248 (code=exited, status=0/SUCCESS)

Sep 28 11:22:43 ubuntu systemd[1]: Starting The Apache HTTP Server...
Sep 28 11:22:47 ubuntu apachectl[1172]: AH00112: Warning: DocumentRoot [/var/www/html] does not exist
Sep 28 11:22:47 ubuntu apachectl[1172]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using ::1. Set the 'S
Sep 28 11:22:47 ubuntu systemd[1]: Started The Apache HTTP Server.

2. Check for the Systemd package

Sometimes, a simple installation of the system package may fix the issue. But prior to that, first, you’ll need to check the current installation status of the systemd package on your Linux system. To check for the same you can execute the following command:

sudo dpkg -l | grep systemd

If your system is already having a proper installation of the systemd utility, you will get an output like this:

[email protected]:~$ sudo dpkg -l | grep systemd
[sudo] password for bhanu: 
ii  dbus-user-session                             1.12.2-1ubuntu1.2                                amd64        simple interprocess messaging system (systemd --user integration)
ii  libnss-systemd:amd64                          237-3ubuntu10.42                                 amd64        nss module providing dynamic user and group name resolution
ii  libpam-systemd:amd64                          237-3ubuntu10.42                                 amd64        system and service manager - PAM module
ii  libsystemd0:amd64                             237-3ubuntu10.42                                 amd64        systemd utility library
ii  libsystemd0:i386                              237-3ubuntu10.42                                 i386         systemd utility library
ii  networkd-dispatcher                           1.7-0ubuntu3.3                                   all          Dispatcher service for systemd-networkd connection status changes
ri  python3-systemd                               234-1build1                                      amd64        Python 3 bindings for systemd
ii  systemd                                       237-3ubuntu10.42                                 amd64        system and service manager
ii  systemd-sysv                                  237-3ubuntu10.42                                 amd64        system and service manager - SysV links
[email protected]:~$

This kind of output indicates that the systemd is installed on your Linux system.

However, if it is not installed in your case, then execute the following commands to install same:

sudo apt-get update
sudo apt-get install systemd

In some cases, the issue still persists even after the installation. In such a case, you can try reinstalling the systemd utility by using the following command:

sudo apt-get install --reinstall systemd

Frequently Asked Questions (FAQs)

What is systemctl and what does it do?

Systemctl is a command-line tool that is used to control the system and service manager on Linux systems. This tool provides a simple and efficient way to manage and control the various services and processes running on your system.

Why is systemctl not found on some Linux systems?

The reason why systemctl is not found on some Linux systems is because it is not included in all distributions. For example, some distributions like Arch Linux and Gentoo Linux do not include systemctl by default. Instead, they use other tools to manage services and processes.

What can I do if systemctl is not found on my Linux system?

If systemctl is not found on your Linux system, you can follow the steps outlined in this article to fix the issue. This includes installing the systemd package and updating the PATH environment variable.

Can I run systemctl on any Linux distribution?

No, not all Linux distributions support systemctl. It is mainly used on systems that use the systemd system and service manager, such as Fedora, Red Hat Enterprise Linux, and Ubuntu.

Is it possible to use alternative tools to manage services and processes if systemctl is not available?

Yes, if systemctl is not available on your Linux system, you can use alternative tools to manage services and processes. Some common alternatives include init, upstart, and sysvinit. It is important to know the system and service manager used by your Linux distribution in order to use the appropriate tool for managing services and processes.

Bottom Line

So, this is how you can tackle the “Systemctl: command not found” error on your Linux PC. The sum up of this fixing guide concludes that the issue can be simply fixed by using the service command instead of systemctl or systemd.

This is because of the unsupported behavior of the older Linux distributions with the systemd command. You can also consider installing the systemd utility if it is not installed but supported by your Linux version.

Also Read:

Rate this post
Posted by
Bhanu Pratap

Hi! I am Bhanu Pratap, co-founder of Yorker Media Group. A die-heart fan of tech and keeps track of every little happening of the same. When not writing, I usually keep myself busy on YouTube making and exploring new and awesome tech content.

Leave a Reply

Your email address will not be published. Required fields are marked *