Get service status linux

10+ commands to list all systemctl services with status

In this tutorial I will share the commands which you can use to list systemctl services along with their state. You can use these methods in scripts to add service status checks to make sure service is in running or failed state.

Are you new to systemd and systemctl?

With RHEL/CentOS 7, now we have services based on systemd and the SysV scripts are deprecated. If you are new to systemd then I would suggest reading this another article where I have done 1:1 comparison between SysV and systemd services.

Now with systemd the traditional Linux commands such as chckconfig , service etc are not supported any more. Although you can still use these commands but they can be removed in upcoming releases.

For example, with RHEL/CentOS 6 we used to use chkconfig to enable or disable service at different run level. Now with RHEL 8 also I see we are allowed to use chkconfig

# chkconfig postfix on Note: Forwarding request to 'systemctl enable postfix.service'. Created symlink /etc/systemd/system/multi-user.target.wants/postfix.service → /usr/lib/systemd/system/postfix.service.

But the request is internally routed to systemctl . Similarly you can restart a service using traditional command i.e. service . For example, to restart sshd :

# service sshd restart Redirecting to /bin/systemctl restart sshd.service

This request was also transferred to systemctl .

So I hope you understood the point, at the time of writing this article with RHEL 8.1

# cat /etc/redhat-release Red Hat Enterprise Linux release 8.1 (Ootpa)

we are still allowed to use traditional SysV commands but it can be removed in any release now. So I would strongly recommend users to start using systemctl commands as they are very user friendly and powerful tool with the amount of options they support.

With systemd we have unit files which are further classified into service , socket , target etc. So you must be very clear on your requirement if you wish to list only services, or sockets or any other type of unit.

systemctl list unit files loaded in memory

List active unit files

First of all we will list all the unit files which are currently available in the memory of our Linux server. This command will list only the active units from the server’s memory:

List all the unit files

To list all the units independent of their state add » —all » to this command

As you can see now it is loading all the unit files including failed , inactive unit files

systemctl list installed unit files

Now list-units shows the list of units which are currently loaded in the memory but not necessarily installed on the server. To view the list of unit files which are currently installed on our server we use:

Here this command will show all the installed unit files independent of their state unlike list-units which shows only the active unit files. Adding —all with this command will have no advantage.

List type of unit files

There can be different types of unit files such as service, socket, mount etc. To further filter the unit files we can add type= argument with list-unit-files . The argument should be a comma-separated list of unit types.

systemctl list services

To list all the installed systemctl services from our Linux server:

# systemctl list-unit-files --type=service

This should give us a complete list of installed services (independent of it’s state)

systemctl list mount files

With systemd all the partitions and file system are mounted as part of mount type unit files. So we can also list all the mount type unit files available on our server using type=mount

# systemctl list-units --all --type=mount

We can further use this with different other type of unit files such as socket, target etc.

List state of services

To check if a service is enabled/disabled/static/indirect, you must use list-unit-files with systemctl while to check if a service is running/active/failed/dead etc then you must use systemctl list-units . To get complete list of supported options with list-units and —state , use systemctl —state=help

systemctl list enabled services

To list all the service unit files which are currently in enabled state use —state=enabled

# systemctl list-unit-files --type=service --state=enabled

systemctl list disabled services

We can provided multiple state type with —state= argument where individual state values will be comma separated. For example to list all the systemctl service which are either enabled or disabled

# systemctl list-unit-files --type=service --state=enabled,disabled

systemctl list running services

To list the running services we will use list-units in combination with —type=service and —state=running

# systemctl list-units --type=service --state=running

systemctl list failed services

To list failed services you can use —state=failed

# systemctl list-units --type=service --state=failed

OR alternatively we can directly use

Check service status of individual unit file

Now the above commands will give you the status of all the unit files which are installed or available on your server. To check the status of individual file we do not want to use those commands in combination with grep and other filter utility.

Now assuming I wish to check the status of sshd service. So I can use

which can give me a long list of output along with the actual status such as active, running loaded. Now these three states can also be grepped individually using the properties of a unit file

To check if a systemctl service is running or not use:

# systemctl show sshd --property=SubState SubState=running

To check if a service is active or inactive :

# systemctl show sshd --property=ActiveState ActiveState=active

# systemctl is-active sshd active

To check if a service is loaded or not:

# systemctl show sshd --property=LoadState LoadState=loaded

So we can individually grep the state of individual services using their properties. To list all the properties of a service you can use:

Conclusion

In this article we learned little bit more about systemd and systemctl unit files. I have explained about the different types of unit files and commands using which we can get the list of running services, sockets, targets etc with systemctl . We can also get individual status of services using the property of unit files which gives us much more control over the details of each service. We can use these properties in scripts for automation purpose.

Lastly I hope the steps from the article to list running services on Linux was helpful. So, let me know your suggestions and feedback using the comment section.

References

I have used below external references for this tutorial guide

Didn’t find what you were looking for? Perform a quick search across GoLinuxCloud

If my articles on GoLinuxCloud has helped you, kindly consider buying me a coffee as a token of appreciation.

For any other feedbacks or questions you can either use the comments section or contact me form.

Thank You for your support!!

Источник

How to Check Service Status in Linux

Systemd initialization system allows you not only to start and stop services but also to check their status and show information about them. Use the systemctl utility with the status command to get information about the service. For example, if you want to get the state of the Nginx web server, run this command:

sudo systemctl status nginx

Usually, the utility prints information with pagination because data does not fit the terminal window. If you want to disable pagination, use the —no-pager option:

sudo systemctl status nginx —no-pager

Let’s have a look at the information which is printed by this command:

• Loaded — the loaded value means that the unit file was loaded successfully. Here you can see other values, for example, masked, when the unit is masked or not-found when the requested unit does not exist. Also in this line, you can find the path to the unit file.
• Active — the current unit state and sub-state. If the unit is running you will see active (running) or inactive(dead) if nobody has started it since the last system boot. If something goes wrong, you will see the failed state.
• Docs — the name of man pages for the service.
• Process — service processes, their states, and exit codes.
• Main PID — identifier of the main service process.
• Tasks — number of tasks which are running for this service.
• Memory — reflects how much RAM is used.
• CPU — reflects the CPU usage.

If you want to get all possible values for the Loaded and Active fields, run this command:

After these information fields, you can see the service log. By default, it prints the last ten lines from the main service output. If you want to get more lines, use the —lines option. For example, use this command if you want to get the last 50 lines:

sudo systemctl status —lines=50 avahi-daemon

In rare cases, for example in no-pager mode, log lines may be ellipsized to fit the screen. You can use the -l or —full options to avoid this:

sudo systemctl -l status avahi-daemon —no-pager

If you want to get all available logs, you should use the journalctl command with the -u option and service name. For example:

journalctl -eu nginx.service

The output starts from the end. You can use the arrow keys on your keyboard to scroll logs. Also, you can view the service state change history using the journalctl command with the -xeu options. For example:

journalctl -xeu nginx.service

You can find more information about service management in the previous article.

Found a mistake in the text? Let me know about that. Highlight the text with the mistake and press Ctrl+Enter.

Источник