![[Note]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_tITsWGENcJIxP1sT8l1EBABDBa_IEeAf--ZDwsEymIsdcLyodPQzxio14h3RPNvykNGov55RLpYHMMzhfo7-S9oxkVO8L_L8vbz8DriQoP8w=s0-d) | Note |
|---|
Instead of installing Icinga from scratch you may want to use a package which might be available for your OS. Please take a look at the table of packages.
Please keep in mind that the upstream packages might be outdated so using backport packages is a way to get a recent version. Please take a look at wiki articles for detailed descriptions:
If you are planning to install from source then please use the official release tarball.
|
![[Important]](https://lh3.googleusercontent.com/blogger_img_proxy/AEn0k_uNQEmjrlPiCZNp-LC3ZBeL1DP7PZuD8HLuS6ok3t_gIFKgUdvbUX_PduMVBKiuKiVBmbyvOfbiI0NYW1pRHj_lB6Ez_VbUVy0Q-jrESeWCCmlqAIF5=s0-d) | Important |
|---|
Please don't use git snapshots unless you have an issue which might be solved in the current developer version.
|
This guide is intended to provide you with simple instructions on how to install Icinga from source (code) and have it monitoring your local machine within 20 minutes.
No advanced installation options are discussed here - just the basics that will work for most of the users who want to get started.
For instructions on how to install Icinga on FreeBSD please read
Icinga on FreeBSD instead.
Other distributions may inherit from these examples.
| Important |
|---|
If you are planning to use a database with IDOUtils, or wish to use the new web interface then please read Icinga with IDOUtils instead! |
What You'll End Up With
If you follow these instructions, here's what you'll end up with:
Icinga and the plugins will be installed underneath /usr/local/icinga
Icinga will be configured to monitor a few aspects of your local system (CPU load, disk usage, etc.)
The Icinga classic web interface will be accessible at http://localhost/icinga/ or http://yourdomain.com/icinga
During portions of the installation you'll need to have root access to your machine.
Make sure you've installed the following packages on your system before continuing.
Optional
At one time or another you may need to use SNMP-based checks so it is a good idea to install the required packages now. Otherwise some plugins are not compiled i.e. not available when you need them and it would require a recompile of the plugins.
You can install these packages by running the following commands (as root or using sudo).
| Note |
|---|
Unfortunately sometimes the names of packages change between different releases of the same distribution so if you get a message that one of the packages cannot be found then please use the search option of your package manager to get the new name:
yum search <package name> (Fedora/RHEL/CentOS)
apt-cache search <package name> (Debian/Ubuntu)
zypper search <package name> (openSuSE/SLES)
|
Fedora/RHEL/CentOS
#> yum install httpd gcc glibc glibc-common gd gd-devel
#> yum install libjpeg libjpeg-devel libpng libpng-devel
#> yum install net-snmp net-snmp-devel net-snmp-utils
| Note |
|---|
You may have to use libjpeg-turbo and libjpeg-turbo-devel instead
|
Debian/Ubuntu
#> apt-get install apache2 build-essential libgd2-xpm-dev
#> apt-get install libjpeg62 libjpeg62-dev libpng12 libpng12-dev
#> apt-get install snmp libsnmp5-dev
| Note |
|---|
The numbers <62/12> might differ, depending on your distribution
|
| Note |
|---|
Starting with Debian 6.0 / Ubuntu 10.10 the package is called libpng-12-0, the name of the dev-package hasn't changed.
|
openSuSE/SLES
Please use YaST to install at least the packages gd, gd-devel, libjpeg, libjpeg-devel, libpng, libpng-devel and, optionally, net-snmp, net-snmp-devel and perl-Net-SNMP.
Using zypper should work as well:
#> zypper install gd gd-devel libjpeg libjpeg-devel libpng libpng-devel
#> zypper install net-snmp net-snmp-devel perl-Net-SNMP
| Note |
|---|
Depending on the software selection during the installation of the OS you may need to install additional packages (i.e. apache2, gcc). The devel packages might be placed on the SDK DVDs.
|
2.3.4. Create Account Information
Become the root user.
$> su -l
Create a new icinga user account and give it a password:
#> /usr/sbin/useradd -m icinga
#> passwd icinga
On some distributions you'll need to add the group in a single step:
#> /usr/sbin/groupadd icinga
For sending commands from the classic web interface to Icinga, you'll need to create a new group icinga-cmd. Add the webuser and the Icinga user to this group:
#> /usr/sbin/groupadd icinga-cmd
#> /usr/sbin/usermod -a -G icinga-cmd icinga
#> /usr/sbin/usermod -a -G icinga-cmd www-data
(or www, wwwrun, apache, depending on the distribution)
| Note |
|---|
Some usermod-versions (e.g. in OpenSuSE 11 and SLES 11, resp.) are lacking the option -a. In this case please omit the option -a.
|
| Note |
|---|
Solaris only supports groupnames with max. 8 characters, please use icingcmd instead of icinga-cmd.
|
2.3.5. Download Icinga and the Plugins
Change to your local source directory i.e. /usr/src
#> cd /usr/src
2.3.6. Compile and install Icinga
Extract the Icinga source code tarball (or change directory to the GIT snapshot)
#> cd /usr/src/
#> tar xvzf icinga-1.11.tar.gz
#> cd icinga-1.11
Run the Icinga configure script. You will get help by using the --help flag.
| Note |
|---|
Starting with Icinga 1.9 the default has changed so you have to disable the compilation of IDOUtils explicitly.
|
#> ./configure --with-command-group=icinga-cmd --disable-idoutils
| Note |
|---|
Starting with Apache 2.4 the default web configuration folder changed from /etc/apache2/conf.d to /etc/apache2/conf-available so depending on your distribution (testing versions of Debian / Ubuntu) you might have to add this option to the call of configure
#> ./configure --with-httpd-conf=/etc/apache2/conf-available
|
Compile the Icinga source code. To see available options, only use "make".
#> make all
Install binaries, init script, sample config files, some eventhandlers, and set permissions on the external command directory.
#> make install
#> make install-init
#> make install-config
#> make install-eventhandlers
#> make install-commandmode
or shorter
#> make fullinstall
#> make install-config
| Note |
|---|
Starting with Icinga 1.5.0 make install-config is NOT included in make fullinstall anymore to avoid accidently overwriting of your config files.
|
| Note |
|---|
Starting with Icinga 1.7.0 make install-eventhandlers will install some event handler routines. To prevent undesired behaviour it is only included when you use make fullinstall.
|
Don't start Icinga yet - there's still more that needs to be done...
2.3.7. Customise Configuration
Sample configuration files have been installed by using
#> make install-config
into /usr/local/icinga/etc/. You'll need to make just one change before you proceed...
Edit the /usr/local/icinga/etc/objects/contacts.cfg config file with your favourite editor and change the email address associated with the icingaadmincontact definition to the address you'd like to use for receiving alerts.
#> vi /usr/local/icinga/etc/objects/contacts.cfg
2.3.8. Configure the Classic Web Interface
Icinga ships with the Classic Web Interface ("the CGIs") which can be installed via
#> make cgis
#> make install-cgis
#> make install-html
Install the Icinga Classic web config file in the Apache conf.d directory (conf-available starting with Apache 2.4).
#> make install-webconf
| Note |
|---|
Starting with Icinga 1.9 the command 'make install-webconf-auth' additionally installs the file htpasswd.users which contains credentials for the user icingaadmin so you can skip the following step. The password is icingaadmin.
|
| Note |
|---|
Starting with Apache 2.4 (testing versions of Debian / Ubuntu) you have to enable the configuration
#> a2enconf icinga
|
Create an icingaadmin account for logging into the Icinga classic web interface. If you want to change it later, use the same command. Remember the password you assign to this account - you'll need it later.
#> htpasswd -c /usr/local/icinga/etc/htpasswd.users icingaadmin
If you want to change it later or want to add another user, use the following command:
#> htpasswd /usr/local/icinga/etc/htpasswd.users <USERNAME>
| Note |
|---|
Depending on your distribution/Apache-version you may have to use htpasswd2 instead.
|
Reload/Restart Apache to make the new settings take effect.
2.3.9. Compile and Install the Monitoring Plugins
Extract the plugins source code tarball.
#> cd /usr/src
#> tar xvzf nagios-plugins-1.5.tar.gz
#> cd nagios-plugins-1.5
Compile and install the plugins by changing install directory to /usr/local/icinga
#> ./configure \
--prefix=/usr/local/icinga --with-cgiurl=/icinga/cgi-bin \
--with-nagios-user=icinga --with-nagios-group=icinga
#> make
#> make install
2.3.10. Adjusting the SELinux settings
RHEL and derived distributions like Fedora and CentOS are shipped with activated SELinux (Security Enhanced Linux) running in "enforcing" mode. This may lead to "Internal Server Error" messages when you try to invoke the Icinga-CGIs.
Check if SELinux runs in enforcing mode
#> getenforce
Set SELinux in "permissive" mode
#> setenforce 0
To make this change permanent you have to adjust this setting in /etc/selinux/config and restart the system.
Instead of deactivating SELinux or setting it into permissive mode you can use the following commands to run the CGIs in enforcing/targeted mode. Thesemanage command will automatically add entries to /etc/selinux/targeted/contexts/files/file_contexts.local.
#> semanage fcontext -a -t httpd_sys_script_exec_t '/usr/local/icinga/sbin(/.*)?'
#> semanage fcontext -a -t httpd_sys_content_t '/usr/local/icinga/share(/.*)?'
#> semanage fcontext -a -t httpd_sys_rw_content_t '/usr/local/icinga/var(/.*)?'
Once you have defined the necessary contexts you have to apply the settings:
#> chcon -R /usr/local/icinga/sbin
#> chcon -R /usr/local/icinga/share
#> chcon -R /usr/local/icinga/var/rw
Add Icinga to the list of system services and have it automatically start when the system boots (make sure you have installed the init script before).
Fedora/RHEL/CentOS/openSuSE
#> chkconfig --add icinga
#> chkconfig icinga on
Debian/Ubuntu
#> update-rc.d icinga defaults
Verify the sample Icinga configuration files.
#> /usr/local/icinga/bin/icinga -v /usr/local/icinga/etc/icinga.cfg
Instead of specifying the paths to binary and config file you can issue
#> /etc/init.d/icinga show-errors
which results in an OK message if everything is fine or several lines which show the location of the error(s).
If there are no errors, start Icinga.
Fedora/RHEL/CentOS/Ubuntu
#> service icinga start
Debian/openSuSE
#> /etc/init.d/icinga start
2.3.12. Login to the Classic Web Interface
You should now be able to access the Icinga classic web interface at the URL below. You'll be prompted for the username ( icingaadmin) and password you specified earlier.
http://localhost/icinga/
or
http://yourdomain.com/icinga/
Click on the "Service Detail" navbar link to see details of what's being monitored on your local machine. It will take a few minutes for Icinga to check all the services associated with your machine.
2.3.13. Other Modifications
Make sure your system's firewall rules are configured to allow access to the web server if you want to access the Icinga classic interface remotely.
#> iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
Setting up your mail transfer agent (MTA) like exim, sendmail or postfix to allow Icinga sending notification emails won't be explained here.
Congratulations! You successfully installed Icinga. Your journey into monitoring has just begun.
You'll no doubt want to monitor more than just your local machine, so check out the chapter on
"Getting Started" about "Monitoring ..."
http://docs.icinga.org/latest/en/quickstart-icinga.html
