grandmaster/check_systemd_needrestart repository overview

⁠About

The check plugin check_systemd_needrestart monitors whether any systemd services should be restarted due to updated software packages.

To check whether a non-container host should be rebooted, use this plugin together with check_linux_newkernel⁠.

⁠Demonstration

1. $ docker run -itp 8080:80 grandmaster/check_systemd_needrestart
2. Open http://localhost:8080⁠ and navigate to the (only) service

⁠Usage

The plug-and-play Linux binaries⁠ don't take any CLI arguments or environment variables.

⁠Legal info

To print the legal info, execute the plugin in a terminal:

$ ./check_systemd_needrestart

In this case the program will always terminate with exit status 3 ("unknown") without actually checking anything.

⁠Testing

If you want to actually execute a check inside a terminal, you have to connect the standard output of the plugin to anything other than a terminal – e.g. the standard input of another process:

$ ./check_systemd_needrestart |cat

In this case the exit code is likely to be the cat's one. This can be worked around like this:

bash $ set -o pipefail
bash $ ./check_systemd_needrestart |cat

⁠Actual monitoring

Just integrate the plugin into the monitoring tool of your choice like any other check plugin. (Consult that tool's manual on how to do that.) It should work with any monitoring tool supporting the Nagio$ check plugin API⁠.

The only limitation: check_systemd_needrestart must be run on the host to be checked for any services to be restarted – either with an agent of your monitoring tool or by SSH. Otherwise it will check the host your monitoring tool runs on for any services to be restarted.

⁠Icinga 2

This repository ships the check command definition⁠ as well as a service template⁠ and host example⁠ for Icinga 2⁠.

The service definition will work in both correctly set up Icinga 2 clusters⁠ and Icinga 2 instances not being part of any cluster as long as the hosts⁠ are named after the endpoints⁠.