Detailed Installation Instructions
Last updated: October 17. 2016
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:
The installation is achieved in four steps:
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
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.
Here is an installation example:
root@linux# wget http://download.opensuse.org/tumbleweed/repo/oss/suse/x86_64/apache2-mod_fcgid-2.3.9-6.2.x86_64.rpm 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.
Here is an example for the installation on CentOS 5.10 with 32 Bit-architecture.
root@linux# rpm -Uvh https://dl.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm
On CentOS 5.X-Systems you additionally need the python-reportlab package, which can be manually-installed as below:
root@linux# rpm -Uvh http://mathias-kettner.de/download/python-reportlab-2.3-3.noarch.rpm
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:
root@linux# yum-config-manager --enable rhel-6-server-optional-rpms root@linux# subscription-manager repos --enable rhel-6-server-optional-rpms
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
Please note: On Red Hat Linux usually SELinux is enabled. That will prevent Check_MK from working correctly. You need to configure the local firewall - at least enable HTTP access or totally disable the firewall. Also disable SELinux or configure a appropriate SELinux policy for Check_MK.
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:
4. Package installation
4.1. Debian and Ubuntu
Firstly, install the gdebi (for Ubuntu this is included in its standard components) package:
root@linux# apt-get install gdebi-core
Afterwards install the Check_MK package with gdebi (for Ubuntu naturally not wheezy, but rather the appropriate package):
root@linux# gdebi omd-1.2.4p2.mmk_0.wheezy_amd64.deb
Finally, ensure that the Apache-Module mod_proxy and mod_proxy_http are activated. This is achieved with the following commands:
root@linux# a2enmod proxy_http root@linux# /etc/init.d/apache2 restart
For SLES use the zypper Tool with the install command:
root@linux# zypper install omd-1.2.4p2.mmk-sles11sp3-32.x86_64.rpm
4.3. Red Hat and CentOS
Here the installation is achieved with yum localinstall:
root@linux# yum localinstall --nogpgcheck omd-1.2.4p2.mmk-rh65-32.x86_64.rpm
5. Final Test
Following a successful installation of Check_MK and all dependencies, the command omd is available with which you can instal and manage Monitoring Instances. For checking purposes you can display the installed version with:
root@linux# omd version OMD - Open Monitoring Distribution Version 1.2.4p2