2014-05-04 11:25:12 +02:00
# <a id="getting-started"></a> Getting Started
This tutorial is a step-by-step introduction to installing Icinga 2 and
2015-01-26 14:40:27 +01:00
Icinga Web 2. It assumes that you are familiar with the operating system
you're using to install Icinga 2.
2014-05-23 01:01:06 +02:00
2014-05-04 11:25:12 +02:00
## <a id="setting-up-icinga2"></a> Setting up Icinga 2
2014-05-29 11:58:25 +02:00
First off you will have to install Icinga 2. The preferred way of doing this
2014-07-21 20:22:48 +02:00
is to use the official package repositories depending on which operating system
and distribution you are running.
2014-05-04 11:25:12 +02:00
2014-07-21 20:22:48 +02:00
Distribution | Repository
2014-05-04 11:25:12 +02:00
------------------------|---------------------------
2015-01-23 14:15:57 +01:00
Debian | [debmon ](http://debmon.org/packages/debmon-wheezy/icinga2 ), [Icinga Repository ](http://packages.icinga.org/debian/ )
Ubuntu | [Icinga PPA ](https://launchpad.net/~formorer/+archive/ubuntu/icinga ), [Icinga Repository ](http://packages.icinga.org/ubuntu/ )
2014-07-21 20:22:48 +02:00
RHEL/CentOS | [Icinga Repository ](http://packages.icinga.org/epel/ )
2015-01-21 08:01:49 +01:00
openSUSE | [Icinga Repository ](http://packages.icinga.org/openSUSE/ ), [Server Monitoring Repository ](https://build.opensuse.org/package/show/server:monitoring/icinga2 )
2014-07-21 20:22:48 +02:00
SLES | [Icinga Repository ](http://packages.icinga.org/SUSE/ )
Gentoo | [Upstream ](http://packages.gentoo.org/package/net-analyzer/icinga2 )
FreeBSD | [Upstream ](http://www.freshports.org/net-mgmt/icinga2 )
ArchLinux | [Upstream ](https://aur.archlinux.org/packages/icinga2 )
2014-05-04 11:25:12 +02:00
Packages for distributions other than the ones listed above may also be
2014-07-21 20:22:48 +02:00
available. Please contact your distribution packagers.
2014-05-04 11:25:12 +02:00
2015-02-12 10:29:21 +01:00
### <a id="package-repositories"></a> Package Repositories
2014-08-27 16:30:35 +02:00
You need to add the Icinga repository to your package management configuration.
Below is a list with examples for the various distributions.
Debian (debmon):
2014-09-04 17:02:30 +02:00
2014-08-27 16:30:35 +02:00
# wget -O - http://debmon.org/debmon/repo.key 2>/dev/null | apt-key add -
2015-01-23 09:39:17 +01:00
# echo 'deb http://debmon.org/debmon debmon-wheezy main' >/etc/apt/sources.list.d/debmon.list
2014-08-27 16:30:35 +02:00
# apt-get update
Ubuntu (PPA):
2014-09-04 17:02:30 +02:00
2014-08-27 16:30:35 +02:00
# add-apt-repository ppa:formorer/icinga
# apt-get update
RHEL/CentOS:
2014-09-04 17:02:30 +02:00
2014-08-27 16:30:35 +02:00
# rpm --import http://packages.icinga.org/icinga.key
2015-01-25 16:07:43 +01:00
# curl -o /etc/yum.repos.d/ICINGA-release.repo http://packages.icinga.org/epel/ICINGA-release.repo
2014-08-27 16:30:35 +02:00
# yum makecache
Fedora:
2014-09-04 17:02:30 +02:00
2015-01-25 16:07:43 +01:00
# rpm --import http://packages.icinga.org/icinga.key
# curl -o /etc/yum.repos.d/ICINGA-release.repo http://packages.icinga.org/fedora/ICINGA-release.repo
2014-08-27 16:30:35 +02:00
# yum makecache
2015-02-06 15:08:51 +01:00
SLES 11:
2015-02-03 13:23:50 +01:00
# zypper ar http://packages.icinga.org/SUSE/ICINGA-release-11.repo
# zypper ref
SLES 12:
2014-09-04 17:02:30 +02:00
2014-08-27 16:30:35 +02:00
# zypper ar http://packages.icinga.org/SUSE/ICINGA-release.repo
# zypper ref
2015-01-21 08:01:49 +01:00
openSUSE:
2014-09-04 17:02:30 +02:00
2014-08-27 16:30:35 +02:00
# zypper ar http://packages.icinga.org/openSUSE/ICINGA-release.repo
# zypper ref
The packages for RHEL/CentOS depend on other packages which are distributed
2014-05-04 11:25:12 +02:00
as part of the [EPEL repository ](http://fedoraproject.org/wiki/EPEL ). Please
2014-08-27 16:30:35 +02:00
make sure to enable this repository by following
2015-01-22 09:40:25 +01:00
[these instructions ](http://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F ).
2014-08-27 16:30:35 +02:00
### <a id="installing-icinga2"></a> Installing Icinga 2
2014-05-04 11:25:12 +02:00
You can install Icinga 2 by using your distribution's package manager
to install the `icinga2` package.
2014-08-27 16:30:35 +02:00
Debian/Ubuntu:
2014-09-04 17:02:30 +02:00
2014-08-27 16:30:35 +02:00
# apt-get install icinga2
2015-01-26 14:40:27 +01:00
RHEL/CentOS 5/6:
2014-09-04 17:02:30 +02:00
2014-08-27 16:30:35 +02:00
# yum install icinga2
# chkconfig icinga2 on
# service icinga2 start
2015-01-26 14:40:27 +01:00
RHEL/CentOS 7 and Fedora:
2014-05-04 11:25:12 +02:00
2015-01-26 14:40:27 +01:00
# yum install icinga2
2014-08-27 16:30:35 +02:00
# systemctl enable icinga2
# systemctl start icinga2
2015-01-26 14:40:27 +01:00
SLES/openSUSE:
# zypper install icinga2
2014-05-29 15:34:01 +02:00
### <a id="installation-enabled-features"></a> Enabled Features during Installation
The default installation will enable three features required for a basic
Icinga 2 installation:
* `checker` for executing checks
* `notification` for sending notifications
2014-11-02 21:46:02 +01:00
* `mainlog` for writing the `icinga2.log` file
2014-05-29 15:34:01 +02:00
2015-02-06 15:08:51 +01:00
You can verify that by calling `icinga2 feature list`
2015-02-11 11:51:58 +01:00
[CLI command ](8-cli-commands.md#cli-command-feature ) to see which features are
2015-02-06 15:08:51 +01:00
enabled and disabled.
2014-05-29 15:34:01 +02:00
2014-11-02 21:46:02 +01:00
# icinga2 feature list
Disabled features: api command compatlog debuglog graphite icingastatus ido-mysql ido-pgsql livestatus notification perfdata statusdata syslog
2014-05-29 15:34:01 +02:00
Enabled features: checker mainlog notification
2014-05-04 11:25:12 +02:00
2014-11-02 21:46:02 +01:00
2014-05-04 11:25:12 +02:00
### <a id="installation-paths"></a> Installation Paths
By default Icinga 2 uses the following files and directories:
Path | Description
------------------------------------|------------------------------------
/etc/icinga2 | Contains Icinga 2 configuration files.
/etc/init.d/icinga2 | The Icinga 2 init script.
2015-03-10 09:53:33 +01:00
/usr/sbin/icinga2 | The Icinga 2 binary.
2014-05-04 11:25:12 +02:00
/usr/share/doc/icinga2 | Documentation files that come with Icinga 2.
2014-05-10 18:23:08 +02:00
/usr/share/icinga2/include | The Icinga Template Library and plugin command configuration.
2014-05-04 11:25:12 +02:00
/var/run/icinga2 | PID file.
/var/run/icinga2/cmd | Command pipe and Livestatus socket.
2014-11-02 21:46:02 +01:00
/var/cache/icinga2 | status.dat/objects.cache, icinga2.debug files
2014-05-04 11:25:12 +02:00
/var/spool/icinga2 | Used for performance data spool files.
2014-11-02 21:46:02 +01:00
/var/lib/icinga2 | Icinga 2 state file, cluster log, local CA and configuration files.
2014-05-04 11:25:12 +02:00
/var/log/icinga2 | Log file location and compat/ directory for the CompatLogger feature.
2014-08-27 16:30:35 +02:00
## <a id="setting-up-check-plugins"></a> Setting up Check Plugins
Without plugins Icinga 2 does not know how to check external services. The
[Monitoring Plugins Project ](https://www.monitoring-plugins.org/ ) provides
an extensive set of plugins which can be used with Icinga 2 to check whether
services are working properly.
The recommended way of installing these standard plugins is to use your
distribution's package manager.
For your convenience here is a list of package names for some of the more
popular operating systems/distributions:
OS/Distribution | Package Name | Installation Path
-----------------------|--------------------|---------------------------
RHEL/CentOS (EPEL) | nagios-plugins-all | /usr/lib/nagios/plugins or /usr/lib64/nagios/plugins
Debian | nagios-plugins | /usr/lib/nagios/plugins
FreeBSD | nagios-plugins | /usr/local/libexec/nagios
OS X (MacPorts) | nagios-plugins | /opt/local/libexec
Depending on which directory your plugins are installed into you may need to
2015-02-11 11:51:58 +01:00
update the global `PluginDir` constant in your [Icinga 2 configuration ](5-configuring-icinga-2.md#constants-conf ).
2015-01-26 14:40:27 +01:00
This constant is used by the check command definitions contained in the Icinga Template Library
2015-01-23 14:15:57 +01:00
to determine where to find the plugin binaries.
2014-08-27 16:30:35 +02:00
2015-03-07 15:52:56 +01:00
Please refer to the [plugins ](13-addons-plugins.md#plugins ) chapter for details about how to integrate
2015-01-20 15:15:54 +01:00
additional check plugins into your Icinga 2 setup.
2014-08-27 16:30:35 +02:00
2015-01-26 14:40:27 +01:00
## <a id="running-icinga2"></a> Running Icinga 2
### <a id="init-script"></a> Init Script
Icinga 2's init script is installed in `/etc/init.d/icinga2` by default:
# /etc/init.d/icinga2
Usage: /etc/init.d/icinga2 {start|stop|restart|reload|checkconfig|status}
The init script supports the following actions:
Command | Description
--------------------|------------------------
start | The `start` action starts the Icinga 2 daemon.
stop | The `stop` action stops the Icinga 2 daemon.
restart | The `restart` action is a shortcut for running the `stop` action followed by `start` .
reload | The `reload` action sends the `HUP` signal to Icinga 2 which causes it to restart. Unlike the `restart` action `reload` does not wait until Icinga 2 has restarted.
checkconfig | The `checkconfig` action checks if the `/etc/icinga2/icinga2.conf` configuration file contains any errors.
status | The `status` action checks if Icinga 2 is running.
By default the Icinga 2 daemon is running as `icinga` user and group
using the init script. Using Debian packages the user and group are set to
`nagios` for historical reasons.
### <a id="systemd-service"></a> systemd Service
Some distributions (e.g. Fedora, openSUSE and RHEL/CentOS 7) use systemd. The
Icinga 2 packages automatically install the necessary systemd unit files.
2015-02-06 15:08:51 +01:00
The Icinga 2 systemd service can be (re-)started, reloaded, stopped and also
queried for its current status.
2015-01-26 14:40:27 +01:00
# systemctl status icinga2
icinga2.service - Icinga host/service/network monitoring system
Loaded: loaded (/usr/lib/systemd/system/icinga2.service; disabled)
Active: active (running) since Mi 2014-07-23 13:39:38 CEST; 15s ago
Process: 21692 ExecStart=/usr/sbin/icinga2 -c ${ICINGA2_CONFIG_FILE} -d -e ${ICINGA2_ERROR_LOG} -u ${ICINGA2_USER} -g ${ICINGA2_GROUP} (code=exited, status=0/SUCCESS)
Process: 21674 ExecStartPre=/usr/sbin/icinga2-prepare-dirs /etc/sysconfig/icinga2 (code=exited, status=0/SUCCESS)
Main PID: 21727 (icinga2)
CGroup: /system.slice/icinga2.service
2015-02-11 14:10:21 +01:00
21727 /usr/sbin/icinga2 -c /etc/icinga2/icinga2.conf -d -e /var/log/icinga2/error.log -u icinga -g icinga --no-stack-rlimit
2015-01-26 14:40:27 +01:00
Jul 23 13:39:38 nbmif icinga2[21692]: [2014-07-23 13:39:38 +0200] information/ConfigItem: Checked 309 Service(s).
Jul 23 13:39:38 nbmif icinga2[21692]: [2014-07-23 13:39:38 +0200] information/ConfigItem: Checked 1 User(s).
Jul 23 13:39:38 nbmif icinga2[21692]: [2014-07-23 13:39:38 +0200] information/ConfigItem: Checked 15 Notification(s).
Jul 23 13:39:38 nbmif icinga2[21692]: [2014-07-23 13:39:38 +0200] information/ConfigItem: Checked 4 ScheduledDowntime(s).
Jul 23 13:39:38 nbmif icinga2[21692]: [2014-07-23 13:39:38 +0200] information/ConfigItem: Checked 1 UserGroup(s).
Jul 23 13:39:38 nbmif icinga2[21692]: [2014-07-23 13:39:38 +0200] information/ConfigItem: Checked 1 IcingaApplication(s).
Jul 23 13:39:38 nbmif icinga2[21692]: [2014-07-23 13:39:38 +0200] information/ConfigItem: Checked 8 Dependency(s).
Jul 23 13:39:38 nbmif systemd[1]: Started Icinga host/service/network monitoring system.
The `systemctl` command supports the following actions:
Command | Description
--------------------|------------------------
start | The `start` action starts the Icinga 2 daemon.
stop | The `stop` action stops the Icinga 2 daemon.
restart | The `restart` action is a shortcut for running the `stop` action followed by `start` .
reload | The `reload` action sends the `HUP` signal to Icinga 2 which causes it to restart. Unlike the `restart` action `reload` does not wait until Icinga 2 has restarted.
status | The `status` action checks if Icinga 2 is running.
enable | The `enable` action enables the service being started at system boot time (similar to `chkconfig` )
Examples:
# systemctl enable icinga2
# systemctl restart icinga2
Job for icinga2.service failed. See 'systemctl status icinga2.service' and 'journalctl -xn' for details.
2015-02-06 15:08:51 +01:00
If you're stuck with configuration errors, you can manually invoke the
2015-02-11 11:51:58 +01:00
[configuration validation ](8-cli-commands.md#config-validation ).
2015-01-26 14:40:27 +01:00
2015-03-07 15:52:56 +01:00
## <a id="configuration-syntax-highlighting"></a> Configuration Syntax Highlighting
Icinga 2 ships configuration examples for syntax highlighting using the `vim` and `nano` editors.
The RHEL, SUSE and Debian package `icinga2-common` install these files into
`/usr/share/*/icinga2-common/syntax` . Sources provide these files in `tools/syntax` .
### <a id="configuration-syntax-highlighting-vim"></a> Configuration Syntax Highlighting using Vim
Create a new local vim configuration storage, if not already existing.
Edit `vim/ftdetect/icinga2.vim` if your paths to the Icinga 2 configuration
differ.
$ PREFIX=~/.vim
$ mkdir -p $PREFIX/{syntax,ftdetect}
$ cp vim/syntax/icinga2.vim $PREFIX/syntax/
$ cp vim/ftdetect/icinga2.vim $PREFIX/ftdetect/
Test it:
$ vim /etc/icinga2/conf.d/templates.conf
### <a id="configuration-syntax-highlighting-nano"></a> Configuration Syntax Highlighting using Nano
Copy the `/etc/nanorc` sample file to your home directory. Create the `/etc/nano` directory
and copy the provided `icinga2.nanorc` into it.
$ cp /etc/nanorc ~/.nanorc
# mkdir -p /etc/nano
# cp icinga2.nanorc /etc/nano/
Then include the icinga2.nanorc file in your ~/.nanorc by adding the following line:
$ vim ~/.nanorc
## Icinga 2
include "/etc/nano/icinga2.nanorc"
Test it:
$ nano /etc/icinga2/conf.d/templates.conf
2015-01-26 14:40:27 +01:00
## <a id="setting-up-the-user-interface"></a> Setting up Icinga Web 2
Icinga 2 can be used with Icinga Web 2 and a number of other web interfaces.
This chapter explains how to set up Icinga Web 2. The
2015-03-07 15:52:56 +01:00
[Alternative Frontends ](14-alternative-frontends.md#alternative-frontends )
2015-01-26 14:40:27 +01:00
chapter can be used as a starting point for installing some of the other web
interfaces which are also available.
2014-05-04 11:25:12 +02:00
2015-02-06 15:08:51 +01:00
The DB IDO (Database Icinga Data Output) modules for Icinga 2 take care of
exporting all configuration and status information into a database. The IDO
database is used by a number of projects including
[Icinga Web 2 ](2-getting-started.md#setting-up-icingaweb2 ), Icinga Reporting
or Icinga Web 1.x.
2014-11-15 15:10:22 +01:00
2015-01-20 15:15:54 +01:00
There is a separate module for each database backend. At present support for
2014-08-27 16:30:35 +02:00
both MySQL and PostgreSQL is implemented.
2015-01-23 14:15:57 +01:00
### <a id="configuring-db-ido-mysql"></a> Configuring DB IDO MySQL
2014-05-04 11:25:12 +02:00
2014-08-27 16:30:35 +02:00
#### <a id="installing-database-mysql-server"></a> Installing MySQL database server
2014-05-04 11:25:12 +02:00
2014-08-27 16:30:35 +02:00
Debian/Ubuntu:
2014-09-04 17:02:30 +02:00
2014-08-27 16:30:35 +02:00
# apt-get install mysql-server mysql-client
2014-05-04 11:25:12 +02:00
2014-08-27 16:30:35 +02:00
RHEL/CentOS 5/6:
2014-09-04 17:02:30 +02:00
2014-08-27 16:30:35 +02:00
# yum install mysql-server mysql
# chkconfig mysqld on
# service mysqld start
2015-01-26 14:40:27 +01:00
# mysql_secure_installation
2014-05-04 11:25:12 +02:00
2015-01-23 14:15:57 +01:00
RHEL/CentOS 7 and Fedora:
2014-09-04 17:02:30 +02:00
2014-08-27 16:30:35 +02:00
# yum install mariadb-server mariadb
2015-01-22 16:09:28 +01:00
# systemctl enable mariadb
# systemctl start mariadb
2015-01-26 14:40:27 +01:00
# mysql_secure_installation
2014-05-04 11:25:12 +02:00
2014-08-27 16:30:35 +02:00
SUSE:
2014-09-04 17:02:30 +02:00
2014-08-27 16:30:35 +02:00
# zypper install mysql mysql-client
# chkconfig mysqld on
# service mysqld start
2014-05-04 11:25:12 +02:00
2015-01-23 14:15:57 +01:00
#### <a id="installing-database-mysql-modules"></a> Installing the IDO modules for MySQL
2014-05-04 11:25:12 +02:00
2015-01-23 14:15:57 +01:00
The next step is to install the `icinga2-ido-mysql` package using your
2014-09-15 17:00:00 +02:00
distribution's package manager.
Debian/Ubuntu:
# apt-get install icinga2-ido-mysql
RHEL/CentOS:
# yum install icinga2-ido-mysql
SUSE:
# zypper install icinga2-ido-mysql
2014-08-27 16:30:35 +02:00
> **Note**
2014-05-04 11:25:12 +02:00
>
2015-01-25 16:07:43 +01:00
> The Debian/Ubuntu packages provide a database configuration wizard by
> default. You can skip the automated setup and install/upgrade the
> database manually if you prefer that.
2014-05-04 11:25:12 +02:00
#### <a id="setting-up-mysql-db"></a> Setting up the MySQL database
2014-09-15 17:00:00 +02:00
Set up a MySQL database for Icinga 2:
2014-05-04 11:25:12 +02:00
# mysql -u root -p
mysql> CREATE DATABASE icinga;
2014-09-15 17:00:00 +02:00
GRANT SELECT, INSERT, UPDATE, DELETE, DROP, CREATE VIEW, INDEX, EXECUTE ON icinga.* TO 'icinga'@'localhost' IDENTIFIED BY 'icinga';
2014-05-04 11:25:12 +02:00
After creating the database you can import the Icinga 2 IDO schema using the
following command:
2014-08-17 13:20:39 +02:00
# mysql -u root -p icinga < /usr/share/icinga2-ido-mysql/schema/mysql.sql
2014-05-04 11:25:12 +02:00
2014-08-27 16:30:35 +02:00
2015-01-23 14:15:57 +01:00
#### <a id="enabling-ido-mysql"></a> Enabling the IDO MySQL module
2014-05-04 11:25:12 +02:00
The package provides a new configuration file that is installed in
2015-01-25 16:07:43 +01:00
`/etc/icinga2/features-available/ido-mysql.conf` . You will need to
update the database credentials in this file.
All available attributes are explained in the
2015-02-11 11:51:58 +01:00
[IdoMysqlConnection object ](6-object-types.md#objecttype-idomysqlconnection )
2015-02-06 15:08:51 +01:00
chapter.
2014-05-04 11:25:12 +02:00
2015-02-06 15:08:51 +01:00
You can enable the `ido-mysql` feature configuration file using
`icinga2 feature enable` :
2014-05-04 11:25:12 +02:00
2014-10-14 18:32:15 +02:00
# icinga2 feature enable ido-mysql
2014-05-04 11:25:12 +02:00
Module 'ido-mysql' was enabled.
Make sure to restart Icinga 2 for these changes to take effect.
After enabling the ido-mysql feature you have to restart Icinga 2:
2014-09-04 17:02:30 +02:00
Debian/Ubuntu, RHEL/CentOS 6 and SUSE:
2014-08-27 16:30:35 +02:00
# service icinga2 restart
2014-05-04 11:25:12 +02:00
2015-01-23 14:15:57 +01:00
RHEL/CentOS 7 and Fedora:
2014-09-04 17:02:30 +02:00
2015-01-22 16:09:28 +01:00
# systemctl restart icinga2
2014-05-04 11:25:12 +02:00
2014-06-13 11:17:32 +02:00
### <a id="configuring-db-ido-postgresql"></a> Configuring DB IDO PostgreSQL
2014-05-04 11:25:12 +02:00
2015-01-23 14:15:57 +01:00
#### <a id="installing-database-postgresql-server"></a> Installing PostgreSQL database server
Debian/Ubuntu:
# apt-get install postgresql
RHEL/CentOS 5/6:
# yum install postgresql-server postgresql
# chkconfig postgresql on
# service postgresql start
RHEL/CentOS 7:
# yum install postgresql-server postgresql
# systemctl enable postgresql
# systemctl start postgresql
SUSE:
# zypper install postgresql postgresql-server
# chkconfig postgresql on
# service postgresql start
#### <a id="installing-database-postgresql-modules"></a> Installing the IDO modules for PostgreSQL
The next step is to install the `icinga2-ido-pgsql` package using your
2014-09-15 17:00:00 +02:00
distribution's package manager.
Debian/Ubuntu:
# apt-get install icinga2-ido-pgsql
RHEL/CentOS:
# yum install icinga2-ido-pgsql
SUSE:
# zypper install icinga2-ido-pgsql
2014-08-27 16:30:35 +02:00
> **Note**
>
> Upstream Debian packages provide a database configuration wizard by default.
> You can skip the automated setup and install/upgrade the database manually
> if you prefer that.
2014-05-04 11:25:12 +02:00
#### Setting up the PostgreSQL database
2014-09-15 17:00:00 +02:00
Set up a PostgreSQL database for Icinga 2:
2014-05-04 11:25:12 +02:00
# cd /tmp
# sudo -u postgres psql -c "CREATE ROLE icinga WITH LOGIN PASSWORD 'icinga'";
# sudo -u postgres createdb -O icinga -E UTF8 icinga
# sudo -u postgres createlang plpgsql icinga
2014-05-29 15:14:44 +02:00
> **Note**
>
2015-02-06 15:08:51 +01:00
> When using PostgreSQL 9.x you can omit the `createlang` command.
2014-05-29 15:14:44 +02:00
2014-05-04 11:25:12 +02:00
Locate your pg_hba.conf (Debian: `/etc/postgresql/*/main/pg_hba.conf` ,
RHEL/SUSE: `/var/lib/pgsql/data/pg_hba.conf` ), add the icinga user with md5
authentication method and restart the postgresql server.
# vim /var/lib/pgsql/data/pg_hba.conf
# icinga
local icinga icinga md5
host icinga icinga 127.0.0.1/32 md5
host icinga icinga ::1/128 md5
# "local" is for Unix domain socket connections only
local all all ident
# IPv4 local connections:
host all all 127.0.0.1/32 ident
# IPv6 local connections:
host all all ::1/128 ident
# /etc/init.d/postgresql restart
2015-02-06 15:08:51 +01:00
After creating the database and permissions you can import the Icinga 2 IDO
schema using the following command:
2014-05-04 11:25:12 +02:00
# export PGPASSWORD=icinga
2014-08-17 13:20:39 +02:00
# psql -U icinga -d icinga < /usr/share/icinga2-ido-pgsql/schema/pgsql.sql
2014-05-04 11:25:12 +02:00
2015-01-23 14:15:57 +01:00
#### <a id="enabling-ido-postgresql"></a> Enabling the IDO PostgreSQL module
2014-05-04 11:25:12 +02:00
The package provides a new configuration file that is installed in
2015-01-25 16:07:43 +01:00
`/etc/icinga2/features-available/ido-pgsql.conf` . You will need to update
the database credentials in this file.
All available attributes are explained in the
2015-02-11 11:51:58 +01:00
[IdoPgsqlConnection object ](6-object-types.md#objecttype-idopgsqlconnection )
2015-02-06 15:08:51 +01:00
chapter.
2014-05-04 11:25:12 +02:00
2015-02-06 15:08:51 +01:00
You can enable the `ido-pgsql` feature configuration file using
`icinga2 feature enable` :
2014-05-04 11:25:12 +02:00
2014-10-14 18:32:15 +02:00
# icinga2 feature enable ido-pgsql
2014-05-04 11:25:12 +02:00
Module 'ido-pgsql' was enabled.
Make sure to restart Icinga 2 for these changes to take effect.
After enabling the ido-pgsql feature you have to restart Icinga 2:
2014-09-04 17:02:30 +02:00
Debian/Ubuntu, RHEL/CentOS 6 and SUSE:
2014-08-27 16:30:35 +02:00
# service icinga2 restart
2014-05-04 11:25:12 +02:00
2015-01-23 14:15:57 +01:00
RHEL/CentOS 7 and Fedora:
2014-09-04 17:02:30 +02:00
2015-01-22 16:09:28 +01:00
# systemctl restart icinga2
2014-09-04 17:02:30 +02:00
2014-05-04 11:25:12 +02:00
2015-01-26 14:40:27 +01:00
### <a id="icinga2-user-interface-webserver"></a> Webserver
Debian/Ubuntu:
# apt-get install apache2
RHEL/CentOS 6:
# yum install httpd
# chkconfig httpd on
# service httpd start
RHEL/CentOS 7/Fedora:
# yum install httpd
# systemctl enable httpd
# systemctl start httpd
SUSE:
# zypper install apache2
# chkconfig on
# service apache2 start
### <a id="icinga2-user-interface-firewall-rules"></a> Firewall Rules
Example:
# iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
# service iptables save
RHEL/CentOS 7 specific:
# firewall-cmd --add-service=http
# firewall-cmd --permanent --add-service=http
2014-08-27 19:20:49 +02:00
### <a id="setting-up-external-command-pipe"></a> Setting Up External Command Pipe
Web interfaces and other Icinga addons are able to send commands to
Icinga 2 through the external command pipe.
2015-01-20 15:15:54 +01:00
You can enable the External Command Pipe using the CLI:
2014-08-27 19:20:49 +02:00
2014-10-14 18:32:15 +02:00
# icinga2 feature enable command
2014-08-27 19:20:49 +02:00
After that you will have to restart Icinga 2:
2014-09-04 17:02:30 +02:00
Debian/Ubuntu, RHEL/CentOS 6 and SUSE:
2014-08-27 19:20:49 +02:00
# service icinga2 restart
2015-01-23 14:15:57 +01:00
RHEL/CentOS 7 and Fedora:
2014-09-04 17:02:30 +02:00
2015-01-22 16:09:28 +01:00
# systemctl restart icinga2
2014-09-04 17:02:30 +02:00
2015-02-06 15:08:51 +01:00
By default the command pipe file is owned by the group `icingacmd` with
read/write permissions. Add your webserver's user to the group `icingacmd` to
2014-08-27 19:20:49 +02:00
enable sending commands to Icinga 2 through your web interface:
2014-11-05 18:15:06 +01:00
# usermod -a -G icingacmd www-data
2014-08-27 19:20:49 +02:00
2015-02-06 15:08:51 +01:00
Debian packages use `nagios` as the default user and group name. Therefore
change `icingacmd` to `nagios` .
The webserver's user is different between distributions so you might have to
change `www-data` to `wwwrun` , `www` , or `apache` .
2014-08-27 19:20:49 +02:00
Change "www-data" to the user you're using to run queries.
2015-02-06 15:08:51 +01:00
You can verify that the user has been successfully added to the `icingacmd`
group using the `id` command:
2015-01-25 16:07:43 +01:00
2015-02-06 15:08:51 +01:00
$ id < your-webserver-user >
2014-08-27 19:20:49 +02:00
2015-01-23 14:15:57 +01:00
2015-01-26 14:40:27 +01:00
### <a id="setting-up-icingaweb2"></a> Installing up Icinga Web 2
2015-01-23 14:15:57 +01:00
2015-02-06 15:08:51 +01:00
Please consult the [installation documentation ](https://github.com/Icinga/icingaweb2/blob/master/doc/installation.md )
for further instructions on how to install Icinga Web 2.
2015-01-23 14:15:57 +01:00
2015-01-26 14:40:27 +01:00
## <a id="install-addons"></a> Addons
2015-01-23 14:15:57 +01:00
2015-02-06 15:08:51 +01:00
A number of additional features are available in the form of addons. A list of
popular addons is available in the
2015-03-07 15:52:56 +01:00
[Addons and Plugins ](13-addons-plugins.md#addons-plugins ) chapter.