Detailed Installation Instructions

This article describes how to install the Check_MK Monitoring System on an existing Linux system. To begin, you must have a functional and up to date Linux installation. The packages available with our subscription support the following Linux Distributions - in 32 and 64 Bit:

  • SuSE LINUX Enterprise Server (SLES) from Version 11
  • Red Hat Enterprise Linux (RHEL) from Version 5.5
  • CentOS from Version 5.5
  • Debian from Version 6.0
  • Ubuntu from Version 10.04

The installation is achieved in four steps:

  1. Preparing the Linux-Systems
  2. Setting-up the package sources
  3. Downloading the appropriate package from the subscription page
  4. Installation of the package

1. Installation and preparation of the Linux system

Depending on which Distribution you are installing, different steps are necessary for the preparation. For this reason we will assume that the Linux system, on which the Check_MK is to be installed, will be installed with the manufacturer's default settings and correctly-connected to the network, so that it is accessible via HTTP and SSH from your workplace.

1.1. Partitioning hard drive space

Check_MK stores its data under the /opt/omd physical path. If the system is to be used exclusively for Check_MK, the major part of the hard drive's free space should be available. In this case it is not essential, but very desirable, that /opt/omd, or /opt has its own partition.

1.2. SMTP for outgoing emails

If you wish to send Monitoring Alarms by email, then a correct configuration of the SMTP service is required. This is set up with the distribution's respective tool during the installation. Usually you define a Smarthost to which all emails are to be redirected.

1.3. Settings for the system time

In order for the monitoring server to have a correct system time, we strongly recommend setting up NTP. The hardware clock should be set to UTC. As soon as the server is taken into monitoring with Check_MK, NTP will ensure the correct time is used for all functions.

2. Setting up the package sources

Check_MK requires a number of software packages from your Linux distribution. Third party software is not required. In order that all necessary packages can be subsequently installed, a correct configuration of the software sources is necessary. The setup procedure varies depending on the Distribution being used.

2.1. Debian and Ubuntu

Here all package sources are already set up and no further steps are needed.

2.2. SLES 11

Unfortunately SUSE has some of its important packages on a separate DVD. This is labelled SUSE Linux Enterprise SDK. Install this as a second package source. Please don't confuse the SDK with DVD 2 of the normal installation DVD. This last contains the sofware's source codes and is not required. If you have a valid SLES subscription you can download the ISO image of the SDK from here

2.3. SLES 12

With SLES 12 some software components, eg. PHP, which is required by OMD, are stored in so-called Modules. In order to be able to access SLES 12's PHP packages, the following steps need to be taken:

Unfortunately two further required packages that must be manually-installed are not included. At present these can only be obtained from OpenSUSE-Repositories.

Download-URL Pakage Name (The last character is variable)
Download apache2-mod_fcgid-2.3.9-8.1.x86_64.rpm
Download python-reportlab-3.2.0-1.4.x86_64.rpm

Here is an installation example:

root@linux# wget
root@linux# zypper install apache2-mod_fcgid-2.3.9-4.1.x86_64.rpm

2.4. Red Hat and CentOS

With Red Hat and CENTOS the EPEL (Extra Packages for Enterprise Linux) repository must be set up as a package source.

Version Arch. Download-URL Package name (The last character is variable)
5.X i386 URL epel-release-5-4.noarch.rpm
5.X x64_64 URL epel-release-5-4.noarch.rpm
6.X i386 URL epel-release-6-8.noarch.rpm
6.X x64_64 URL epel-release-6-8.noarch.rpm
7.Xx64_64 URL epel-release-7-2.noarch.rpm

Here is an example for the installation on CentOS 5.10 with 32 Bit-architecture.

root@linux# rpm -Uvh

On CentOS 5.X-Systems you additionally need the python-reportlab package, which can be manually-installed as below:

root@linux# rpm -Uvh

In order to be able to use EPEL on RedHat, the package sources for optional RPMs (at least for RedHat 6) are required, if these haven't already been installed during the operating system installation. Without these sources the freeradius-utils, graphviz-gd, and php-mbstring package will be missing. This can be done, eg., with the following commands:

RedHat 6.X:

root@linux# yum-config-manager --enable rhel-6-server-optional-rpms
root@linux# subscription-manager repos --enable rhel-6-server-optional-rpms

RedHat 7.X:

root@linux# yum-config-manager --enable rhel-7-server-optional-rpms
root@linux# yum-config-manager --enable rhel-7-server-extras-rpms
root@linux# subscription-manager repos --enable rhel-7-server-optional-rpms
root@linux# subscription-manager repos --enable rhel-7-server-extras-rpms

You get a list of all available package repositories with:

root@linux# subscription-manager repos --list

Important: Please note that on Red Hat and CentOS usually comes with SELinux and a local Firewall which you will need to configure. For first step you need to allow your web server to access the network interfaces:

root@linux# setsebool -P httpd_can_network_connect 1

As a second step you need to create a rule for your firewall and activate it:

root@linux# firewall-cmd --zone=public --add-service=http --permanent
root@linux# firewall-cmd --reload

3. Download the appropriate packages

If you have a subscription, in your subscription area you will find a suitable RPM or DEB package for your distribution for every available Check_MK-Version. For a free test version of Check_MK you can access our Demo Version. Later you can easily upgrade to the full version.

Please consider when selecting a package:

  • Firstly, choose a version of Check_MK. Unless otherwise indicated, we recommend the latest stable Version.
  • The name and Version of your Distribution must be identical.
  • The architecture (32 oder 64 Bit) must match.
  • We always recommend the Minimum-Package. Packages from the Full range include alternative software components, such as, eg. Icinga or Thruk, which we provide but do not support.

Load the package onto the Linux system where Check_MK is to be installed.

4. Package installation

4.1. Signed package installation

From Version 1.5.0i4 the packages for this version and for all daily builds are signed using GnuPG. Through the use of this signature, on the one hand it can be verified whether the package really is from Check_MK. On the other hand it can be verified that the package is complete.

So that these signed packages can be installed in the usual way, one time only you will need to import our public key so that the signature will be trusted. First load the key directly from our website:

root@linux# wget

Alternatively, the key can also be obtained from

root@linux# gpg --keyserver --recv-keys 434DAC48C4503261
root@linux# gpg --armor --export 434DAC48C4503261 > Check_MK-pubkey.gpg

Then import the key from the list of trusted signatures. Under Debian and Ubuntu the following command is required:

root@linux# apt-key add Check_MK-pubkey.gpg

For RPM-based systems (RHEL, CentOS, SLES) the rpm tool is required:

root@linux# rpm --import Check_MK-pubkey.gpg

Once the key has been installed the package can also be installed in the usual way.

4.2. Debian and Ubuntu

Next install the gdebi package on Debian (this is installed as standard in Ubuntu). This tool ensures that not only the package with the Check_MK Monitoring System, but that all of the dependencies are also correctly installed:

root@linux# apt-get install gdebi-core

Afterwards install the Check_MK-package with gdebi (the downloaded package here as well):

root@linux# gdebi check-mk-enterprise-1.4.0p24_0.stretch_amd64.deb

Important: Under Debian/Ubuntu there is no automatic verification of a package's signature. If required, you'll need to perform this yourself:

root@linux# dpkg-sig --verify check-mk-enterprise-1.4.0p24_0.stretch_amd64.deb

4.3. SLES

In SLES the zypper tool with the install command is used:

root@linux# zypper install --no-gpg-checks check-mk-enterprise-1.4.0p24_0.stretch_amd64.rpm

Important: When using one of Check_MK's signed packages, the --no-gpg-checks option should of course be omitted. Before an installation the signature can be verified as follows:

root@linux# rpm --checksig check-mk-enterprise-1.4.0p24_0.stretch_amd64.rpm

4.4. Red Hat and CentOS

Here the installation is performed with yum install:

root@linux# yum install --nogpgcheck check-mk-enterprise-1.4.0p24_0.stretch_amd64.rpm

Important: Here as well the signature verification option --nogpgcheck should not be supressed if a signed package from Check_MK is being installed. The package can be manually verified before installation using the same command as under SLES.

5. Final test

After the successful installation of Check_MK und all dependencies you will have access to the command omd. With this command you are able to create and manage monitoring sites. You can request the installed version to verify your installation:

root@linux# omd version
OMD - Open Monitoring Distribution Version 1.4.0p24.cee