1. Setting up the package sources
Checkmk 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 version of SLES being used.
1.1. SLES 11
Unfortunately SUSE has some of its important packages on a separate DVD. This is labelled SUSE Linux Enterprise SDK. Install this with YaST 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 directly from the SUSE website.
1.2. 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:
1.3. SLES 15
With SLES 15, in addition to the Web and Scripting Module, you also have to install the Development Tools Module and the SUSE Package Hub 15.
2. Download the appropriate packages
If you have a subscription, on your subscription downloads
page you will find a suitable RPM or DEB package for your distribution
for every available Checkmk-Version. For a free test or
small installtions of Checkmk you can use our free
Editions. these don't need in consequence any subscription. You are still
able to do an upgrade any time to go to on of the
Please consider when selecting a package:
- Firstly, choose a Checkmk-version, a distribution and a the version of this distribution.
- We recommend the latest stable version. If you need an older version anyway, you can find these in download archive at the of the page.
- The name and version of your distribution must be strictly identical.
- Choose one of the Editions. If you're unsure, you can get an overview to the differences of the editions.
After you downloaded the package to your machine, you need to copy the
file to the target Linux system where Checkmk needs to be installed. You can
do that for example with the programm WinSCP or – if you are able
to use ssh connections – with the commandline tool scp. In the
following example for the
root@linux# scp check-mk-raw-1.6.0p12-sles15-38.x86_64.rpm email@example.com:
3. Signed-package installation
All packages are signed using GnuPG. Through the use of this signature, on the one hand it can be verified whether the package really is from Checkmk, and 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 https://checkmk.com/support/Check_MK-pubkey.gpg
Alternatively, the key can also be obtained from gnupg.net:
root@linux# gpg --keyserver keys.gnupg.net --recv-keys 434DAC48C4503261 root@linux# gpg --armor --export 434DAC48C4503261 > 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 imported, you can verify the package can install it the usual way using zypper install afterwards:
root@linux# rpm -K check-mk-enterprise-1.6.0p12-sles15-38.x86_64.rpm check-mk-enterprise-1.6.0p12-sles15-38.x86_64.rpm: digests signatures OK root@linux# zypper install check-mk-enterprise-1.6.0p12-sles15-38.x86_64.rpm
4. Final test
After the successful installation of Checkmk, and all dependencies, you will have access to the omd command. 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.6.0p12.cee