# <a id="getting-started"></a> Getting Started
-This tutorial is a step-by-step introduction to installing Icinga 2 and
-available Icinga web interfaces. It assumes that you are familiar with
-the system you're installing Icinga 2 on.
-
-Details on troubleshooting problems can be found [here](8-troubleshooting.md#troubleshooting).
+This tutorial is a step-by-step introduction to installing [Icinga 2](2-getting-started.md#setting-up-icinga2)
+and [Icinga Web 2](2-getting-started.md#setting-up-icingaweb2).
+It assumes that you are familiar with the operating system you're using to install Icinga 2.
## <a id="setting-up-icinga2"></a> Setting up Icinga 2
Distribution | Repository
------------------------|---------------------------
- Debian | [Upstream](https://packages.debian.org/sid/icinga2), [debmon](http://debmon.org/packages/debmon-wheezy/icinga2), [Icinga Repository](http://packages.icinga.org/debian/)
- Ubuntu | [Upstream](https://launchpad.net/ubuntu/+source/icinga2), [Icinga PPA](https://launchpad.net/~formorer/+archive/ubuntu/icinga), [Icinga Repository](http://packages.icinga.org/ubuntu/)
+ Debian | [debmon](https://debmon.org/packages/debmon-jessie/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/)
RHEL/CentOS | [Icinga Repository](http://packages.icinga.org/epel/)
openSUSE | [Icinga Repository](http://packages.icinga.org/openSUSE/), [Server Monitoring Repository](https://build.opensuse.org/package/show/server:monitoring/icinga2)
SLES | [Icinga Repository](http://packages.icinga.org/SUSE/)
Packages for distributions other than the ones listed above may also be
available. Please contact your distribution packagers.
-### <a id="installing-requirements"></a> Installing Requirements for Icinga 2
+### <a id="package-repositories"></a> Package Repositories
You need to add the Icinga repository to your package management configuration.
Below is a list with examples for the various distributions.
Debian (debmon):
- # wget -O - http://debmon.org/debmon/repo.key 2>/dev/null | apt-key add -
- # echo 'deb http://debmon.org/debmon debmon-wheezy main' >/etc/apt/sources.list.d/debmon.list
+ # wget -O - https://debmon.org/debmon/repo.key 2>/dev/null | apt-key add -
+ # echo 'deb http://debmon.org/debmon debmon-jessie main' >/etc/apt/sources.list.d/debmon.list
# apt-get update
Ubuntu (PPA):
# add-apt-repository ppa:formorer/icinga
# apt-get update
-RHEL/CentOS:
+RHEL/CentOS 7:
- # rpm --import http://packages.icinga.org/icinga.key
- # wget http://packages.icinga.org/epel/ICINGA-release.repo -O /etc/yum.repos.d/ICINGA-release.repo
- # yum makecache
+ yum install https://packages.icinga.org/epel/7/release/noarch/icinga-rpm-release-7-1.el7.centos.noarch.rpm
-Fedora:
+RHEL/CentOS 6:
+
+ yum install https://packages.icinga.org/epel/6/release/noarch/icinga-rpm-release-6-1.el6.noarch.rpm
+
+RHEL/CentOS 5:
+
+ rpm -i http://packages.icinga.org/epel/5/release/noarch/icinga-rpm-release-5-1.el5.centos.noarch.rpm
+
+The packages for RHEL/CentOS depend on other packages which are distributed
+as part of the [EPEL repository](http://fedoraproject.org/wiki/EPEL). Please
+make sure to enable this repository by following
+[these instructions](http://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F).
+
+Fedora 23:
+
+ dnf install https://packages.icinga.org/fedora/23/release/noarch/icinga-rpm-release-23-1.fc23.noarch.rpm
+
+Fedora 22:
+
+ dnf install https://packages.icinga.org/fedora/22/release/noarch/icinga-rpm-release-22-1.fc22.noarch.rpm
- # wget http://packages.icinga.org/fedora/ICINGA-release.repo -O /etc/yum.repos.d/ICINGA-release.repo
- # yum makecache
+Fedora 21:
-SLES:
+ yum install http://packages.icinga.org/fedora/21/release/noarch/icinga-rpm-release-21-1.fc21.noarch.rpm
+
+SLES 11:
+
+ # zypper ar http://packages.icinga.org/SUSE/ICINGA-release-11.repo
+ # zypper ref
+
+The packages for SLES 11 depend on the `openssl1` package which is distributed
+as part of the [SLES 11 Security Module](https://www.suse.com/communities/conversations/introducing-the-suse-linux-enterprise-11-security-module/).
+
+SLES 12:
# zypper ar http://packages.icinga.org/SUSE/ICINGA-release.repo
# zypper ref
# zypper ar http://packages.icinga.org/openSUSE/ICINGA-release.repo
# zypper ref
-The packages for RHEL/CentOS depend on other packages which are distributed
-as part of the [EPEL repository](http://fedoraproject.org/wiki/EPEL). Please
-make sure to enable this repository by following
-[these instructions](http://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F).
-
### <a id="installing-icinga2"></a> Installing Icinga 2
You can install Icinga 2 by using your distribution's package manager
# apt-get install icinga2
-RHEL/CentOS/Fedora:
+RHEL/CentOS 5/6:
# yum install icinga2
-
-SLES/openSUSE:
-
- # zypper install icinga2
-
-On RHEL/CentOS and SLES you will need to use `chkconfig` and `service` to enable and start
-the `icinga2` service:
-
# chkconfig icinga2 on
# service icinga2 start
-RHEL/CentOS 7 and Fedora use [systemd](2-getting-started.md#systemd-service):
+RHEL/CentOS 7 and Fedora:
+ # yum install icinga2
# systemctl enable icinga2
# systemctl start icinga2
-Some parts of Icinga 2's functionality are available as separate packages:
+SLES/openSUSE:
+
+ # zypper install icinga2
+
+FreeBSD:
- Name | Description
- ------------------------|--------------------------------
- icinga2-ido-mysql | [DB IDO](2-getting-started.md#configuring-db-ido) provider module for MySQL
- icinga2-ido-pgsql | [DB IDO](2-getting-started.md#configuring-db-ido) provider module for PostgreSQL
+ # pkg install icinga2
### <a id="installation-enabled-features"></a> Enabled Features during Installation
* `notification` for sending notifications
* `mainlog` for writing the `icinga2.log` file
-You can verify that by calling `icinga2 feature list` [CLI command](5-cli-commands.md#cli-command-feature)
-to see which features are enabled and disabled.
+You can verify that by calling `icinga2 feature list`
+[CLI command](8-cli-commands.md#cli-command-feature) to see which features are
+enabled and disabled.
# icinga2 feature list
Disabled features: api command compatlog debuglog graphite icingastatus ido-mysql ido-pgsql livestatus notification perfdata statusdata syslog
------------------------------------|------------------------------------
/etc/icinga2 | Contains Icinga 2 configuration files.
/etc/init.d/icinga2 | The Icinga 2 init script.
- /usr/sbin/icinga2* | The Icinga 2 binary.
+ /usr/sbin/icinga2 | The Icinga 2 binary.
/usr/share/doc/icinga2 | Documentation files that come with Icinga 2.
/usr/share/icinga2/include | The Icinga Template Library and plugin command configuration.
/var/run/icinga2 | PID file.
/var/lib/icinga2 | Icinga 2 state file, cluster log, local CA and configuration files.
/var/log/icinga2 | Log file location and compat/ directory for the CompatLogger feature.
+FreeBSD uses slightly different paths:
+
+By default Icinga 2 uses the following files and directories:
+
+ Path | Description
+ ------------------------------------|------------------------------------
+ /usr/local/etc/icinga2 | Contains Icinga 2 configuration files.
+ /usr/local/etc/rc.d/icinga2 | The Icinga 2 init script.
+ /usr/local/sbin/icinga2 | The Icinga 2 binary.
+ /usr/local/share/doc/icinga2 | Documentation files that come with Icinga 2.
+ /usr/local/share/icinga2/include | The Icinga Template Library and plugin command configuration.
+ /var/run/icinga2 | PID file.
+ /var/run/icinga2/cmd | Command pipe and Livestatus socket.
+ /var/cache/icinga2 | status.dat/objects.cache, icinga2.debug files
+ /var/spool/icinga2 | Used for performance data spool files.
+ /var/lib/icinga2 | Icinga 2 state file, cluster log, local CA and configuration files.
+ /var/log/icinga2 | Log file location and compat/ directory for the CompatLogger feature.
+
## <a id="setting-up-check-plugins"></a> Setting up Check Plugins
Without plugins Icinga 2 does not know how to check external services. The
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.
-
-> **Note**
->
-> The `Nagios Plugins` project was renamed to `Monitoring Plugins`
-> in January 2014. At the time of this writing some packages are still
-> using the old name while some distributions have adopted the new package
-> name `monitoring-plugins` already.
+These plugins are required to make the [example configuration](4-configuring-icinga-2.md#configuring-icinga2-overview)
+work out-of-the-box.
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
-update the global `PluginDir` constant in your Icinga 2 configuration. This macro is used
-by the check command definitions contained in the Icinga Template Library to determine
-where to find the plugin binaries.
-
-Please refer to the [plugins](6-addons-plugins.md#plugins) chapter for details about how to integrate
-additional check plugins into your Icinga 2 setup.
-
-## <a id="configuring-icinga2-first-steps"></a> Configuring Icinga 2: First Steps
-
-### <a id="icinga2-conf"></a> icinga2.conf
-
-An example configuration file is installed for you in `/etc/icinga2/icinga2.conf`.
-
-Here's a brief description of the example configuration:
-
- /**
- * Icinga 2 configuration file
- * - this is where you define settings for the Icinga application including
- * which hosts/services to check.
- *
- * For an overview of all available configuration options please refer
- * to the documentation that is distributed as part of Icinga 2.
- */
-
-Icinga 2 supports [C/C++-style comments](10-language-reference.md#comments).
-
- /**
- * The constants.conf defines global constants.
- */
- include "constants.conf"
-
-The `include` directive can be used to include other files.
-
- /**
- * The zones.conf defines zones for a cluster setup.
- * Not required for single instance setups.
- */
- include "zones.conf"
-
- /**
- * The Icinga Template Library (ITL) provides a number of useful templates
- * and command definitions.
- * Common monitoring plugin command definitions are included separately.
- */
- include <itl>
- include <plugins>
-
- /**
- * The features-available directory contains a number of configuration
- * files for features which can be enabled and disabled using the
- * icinga2 feature enable / icinga2 feature disable CLI commands.
- * These commands work by creating and removing symbolic links in
- * the features-enabled directory.
- */
- include "features-enabled/*.conf"
-
-This `include` directive takes care of including the configuration files for all
-the features which have been enabled with `icinga2 feature enable`. See
-[Enabling/Disabling Features](5-cli-commands.md#features) for more details.
-
- /**
- * The repository.d directory contains all configuration objects
- * managed by the 'icinga2 repository' CLI commands.
- */
- include_recursive "repository.d"
-
-This `include_recursive` directive is used for discovery of services on remote clients
-and their generated configuration described in
-[this chapter](4-monitoring-remote-systems.md#icinga2-remote-monitoring-master-discovery-generate-config).
-
-
- /**
- * Although in theory you could define all your objects in this file
- * the preferred way is to create separate directories and files in the conf.d
- * directory. Each of these files must have the file extension ".conf".
- */
- include_recursive "conf.d"
-
-You can put your own configuration files in the [conf.d](2-getting-started.md#conf-d) directory. This
-directive makes sure that all of your own configuration files are included.
-
-> **Tip**
->
-> The example configuration is shipped in this directory too. You can either
-> remove it entirely, or adapt the existing configuration structure with your
-> own object configuration.
-
-### <a id="constants-conf"></a> constants.conf
-
-The `constants.conf` configuration file can be used to define global constants.
+OS/Distribution | Package Name | Repository | Installation Path
+-----------------------|--------------------|---------------------------|----------------------------
+RHEL/CentOS | nagios-plugins-all | [EPEL](http://fedoraproject.org/wiki/EPEL) | /usr/lib/nagios/plugins or /usr/lib64/nagios/plugins
+SLES/OpenSUSE | monitoring-plugins | [server:monitoring](https://build.opensuse.org/project/repositories/server:monitoring) | /usr/lib/nagios/plugins
+Debian/Ubuntu | nagios-plugins | - | /usr/lib/nagios/plugins
+FreeBSD | monitoring-plugins | - | /usr/local/libexec/nagios
+OS X | nagios-plugins | [MacPorts](http://www.macports.org), [Homebrew](http://brew.sh) | /opt/local/libexec or /usr/local/sbin
-By default, you need to make sure to set these constants:
-
-* The `PluginDir` constant must be pointed to your [check plugins](2-getting-started.md#setting-up-check-plugins) path.
-This constant is required by the shipped
-[plugin check command configuration](13-icinga-template-library.md#plugin-check-commands).
-* The `NodeName` constant defines your local node name. Should be set to FQDN which is the default
-if not set. This constant is required for local host configuration, monitoring remote clients and
-cluster setup.
-
-Example:
-
- /* The directory which contains the plugins from the Monitoring Plugins project. */
- const PluginDir = "/usr/lib64/nagios/plugins"
-
-
- /* The directory which contains the Manubulon plugins.
- * Check the documentation, chapter "SNMP Manubulon Plugin Check Commands", for details.
- */
- const ManubulonPluginDir = "/usr/lib64/nagios/plugins"
-
- /* Our local instance name. By default this is the server's hostname as returned by `hostname --fqdn`.
- * This should be the common name from the API certificate.
- */
- //const NodeName = "localhost"
-
- /* Our local zone name. */
- const ZoneName = NodeName
-
- /* Secret key for remote node tickets */
- const TicketSalt = ""
-
-The `ZoneName` and `TicketSalt` constants are required for remote client
-and distributed setups only.
-
-### <a id="conf-d"></a> The conf.d Directory
-
-This directory contains example configuration which should help you get started
-with monitoring the local host and its services. It is included in the
-[icinga2.conf](2-getting-started.md#icinga2-conf) configuration file by default.
-
-It can be used as reference example for your own configuration strategy.
-Just keep in mind to include the main directories in the
-[icinga2.conf](2-getting-started.md#icinga2-conf) file.
-
-You are certainly not bound to it. Remove it, if you prefer your own
-way of deploying Icinga 2 configuration.
-
-Further details on configuration best practice and how to build your
-own strategy is described in [this chapter](3-monitoring-basics.md#configuration-best-practice).
-
-Available configuration files shipped by default:
-
-* [hosts.conf](2-getting-started.md#hosts-conf)
-* [services.conf](2-getting-started.md#services-conf)
-* [users.conf](2-getting-started.md#users-conf)
-* [notifications.conf](2-getting-started.md#notifications-conf)
-* [commands.conf](2-getting-started.md#commands-conf)
-* [groups.conf](2-getting-started.md#groups-conf)
-* [templates.conf](2-getting-started.md#templates-conf)
-* [downtimes.conf](2-getting-started.md#downtimes-conf)
-* [timeperiods.conf](2-getting-started.md#timeperiods-conf)
-* [satellite.conf](2-getting-started.md#satellite-conf)
-
-#### <a id="hosts-conf"></a> hosts.conf
-
-The `hosts.conf` file contains an example host based on your
-`NodeName` setting in [constants.conf](2-getting-started.md#constants-conf). You
-can use global constants for your object names instead of string
-values.
-
-The `import` keyword is used to import the `generic-host` template which
-takes care of setting up the host check command to `hostalive`. If you
-require a different check command, you can override it in the object definition.
-
-The `vars` attribute can be used to define custom attributes which are available
-for check and notification commands. Most of the [Plugin Check Commands](13-icinga-template-library.md#plugin-check-commands)
-in the Icinga Template Library require an `address` attribute.
-
-The custom attribute `os` is evaluated by the `linux-servers` group in
-[groups.conf](2-getting-started.md#groups-conf) making the local host a member.
-
-The example host will show you how to
-
-* define http vhost attributes for the `http` service apply rule defined
-in [services.conf](2-getting-started.md#services-conf).
-* define disks (all, specific `/`) and their attributes for the `disk`
-service apply rule defined in [services.conf](2-getting-started.md#services-conf).
-* define notification types (`mail`) and set the groups attribute. This
-will be used by notification apply rules in [notifications.conf](notifications-conf).
-
-If you've installed [Icinga Web 2](2-getting-started.md#setting-up-icingaweb2) you can
-uncomment the http vhost attributes and relaod Icinga 2. The apply
-rules in [services.conf](2-getting-started.md#services-conf) will automatically
-generate a new service checking the `/icingaweb2` URI using the `http`
-check.
-
- /*
- * Host definitions with object attributes
- * used for apply rules for Service, Notification,
- * Dependency and ScheduledDowntime objects.
- *
- * Tip: Use `icinga2 object list --type Host` to
- * list all host objects after running
- * configuration validation (`icinga2 daemon -C`).
- */
-
- /*
- * This is an example host based on your
- * local host's FQDN. Specify the NodeName
- * constant in `constants.conf` or use your
- * own description, e.g. "db-host-1".
- */
-
- object Host NodeName {
- /* Import the default host template defined in `templates.conf`. */
- import "generic-host"
-
- /* Specify the address attributes for checks e.g. `ssh` or `http`. */
- address = "127.0.0.1"
- address6 = "::1"
-
- /* Set custom attribute `os` for hostgroup assignment in `groups.conf`. */
- vars.os = "Linux"
-
- /* Define http vhost attributes for service apply rules in `services.conf`. */
- vars.http_vhosts["http"] = {
- http_uri = "/"
- }
- /* Uncomment if you've sucessfully installed Icinga Web 2. */
- //vars.http_vhosts["Icinga Web 2"] = {
- // http_uri = "/icingaweb2"
- //}
-
- /* Define disks and attributes for service apply rules in `services.conf`. */
- vars.disks["disk"] = {
- /* No parameters. */
- }
- vars.disks["disk /"] = {
- disk_partitions = "/"
- }
-
- /* Define notification mail attributes for notification apply rules in `notifications.conf`. */
- vars.notification["mail"] = {
- /* The UserGroup `icingaadmins` is defined in `users.conf`. */
- groups = [ "icingaadmins" ]
- }
- }
-
-This is only the host object definition. Now we'll need to make sure that this
-host and your additional hosts are getting [services](2-getting-started.md#services-conf) applied.
-
-> **Tip**
->
-> If you don't understand all the attributes and how to use [apply rules](10-language-reference.md#apply)
-> don't worry - the [monitoring basics](3-monitoring-basics.md#monitoring-basics) chapter will explain
-> that in detail.
-
-#### <a id="services-conf"></a> services.conf
-
-These service [apply rules](10-language-reference.md#apply) will show you how to monitor
-the local host, but also allow you to re-use or modify them for
-your own requirements.
-
-You should define all your service apply rules in `services.conf`
-or any other central location keeping them organized.
-
-By default, the local host will be monitored by the following services
-
-Service(s) | Applied on host(s)
---------------------------------------------|------------------------
-`load`, `procs`, `swap`, `users`, `icinga` | The `NodeName` host only
-`ping4`, `ping6` | All hosts with `address` resp. `address6` attribute
-`ssh` | All hosts with `address` and `vars.os` set to `Linux`
-`http`, optional: `Icinga Web 2` | All hosts with custom attribute `http_vhosts` defined as dictionary
-`disk`, `disk /` | All hosts with custom attribute `disks` defined as dictionary
-
-The Debian packages also ship an additional `apt` service check applied to the local host.
-
-The command object `icinga` for the embedded health check is provided by the
-[Icinga Template Library (ITL)](13-icinga-template-library.md#icinga-template-library) while `http_ip`, `ssh`, `load`, `processes`,
-`users` and `disk` are all provided by the [Plugin Check Commands](13-icinga-template-library.md#plugin-check-commands)
-which we enabled earlier by including the `itl` and `plugins` configuration file.
-
-
-Example `load` service apply rule:
-
- apply Service "load" {
- import "generic-service"
-
- check_command = "load"
-
- /* Used by the ScheduledDowntime apply rule in `downtimes.conf`. */
- vars.backup_downtime = "02:00-03:00"
-
- assign where host.name == NodeName
- }
-
-The `apply` keyword can be used to create new objects which are associated with
-another group of objects. You can `import` existing templates, define (custom)
-attributes.
-
-The custom attribe `backup_downtime` is defined to a specific timerange string.
-This variable value will be used for applying a `ScheduledDowntime` object to
-these services in [downtimes.conf](2-getting-started.md#downtimes-conf).
-
-In this example the `assign where` condition is a boolean expression which is
-evaluated for all objects of type `Host` and a new service with name "load"
-is created for each matching host. [Expression operators](10-language-reference.md#expression-operators)
-may be used in `assign where` conditions.
-
-Multiple `assign where` condition can be combined with `AND` using the `&&` operator
-as shown in the `ssh` example:
-
- apply Service "ssh" {
- import "generic-service"
-
- check_command = "ssh"
-
- assign where host.address && host.vars.os == "Linux"
- }
-
-In this example, the service `ssh` is applied to all hosts having the `address`
-attribute defined `AND` having the custom attribute `os` set to the string
-`Linux`.
-You can modify this condition to match multiple expressions by combinding `AND`
-and `OR` using `&&` and `||` [operators](10-language-reference.md#expression-operators), for example
-`assign where host.address && (vars.os == "Linux" || vars.os == "Windows")`.
-
-
-A more advanced example is shown by the `http` and `disk` service apply
-rules. While one `apply` rule for `ssh` will only create a service for matching
-hosts, you can go one step further: Generate apply rules based on array items
-or dictionary key-value pairs.
-
-The idea is simple: Your host in [hosts.conf](2-getting-started.md#hosts-conf) defines the
-`disks` dictionary as custom attribute in `vars`.
-
-Remember the example from [hosts.conf](2-getting-started.md#hosts-conf):
-
- ...
-
- /* Define disks and attributes for service apply rules in `services.conf`. */
- vars.disks["disk"] = {
- /* No parameters. */
- }
- vars.disks["disk /"] = {
- disk_partition = "/"
- }
- ...
-
-
-This dictionary contains multiple service names we want to monitor. `disk`
-should just check all available disks, while `disk /` will pass an additional
-parameter `disk_partition` to the check command.
-
-You'll recognize that the naming is important - that's the very same name
-as it is passed from a service to a check command argument. Read about services
-and passing check commands in [this chapter](3-monitoring-basics.md#command-passing-parameters).
-
-Using `apply Service for` omits the service name, it will take the key stored in
-the `disk` variable in `key => config` as new service object name.
-
-The `for` keyword expects a loop definition, for example `key => value in dictionary`
-as known from Perl and other scripting languages.
-
-Once defined like this, the `apply` rule defined below will do the following:
-
-* only match hosts with `host.vars.disks` defined through the `assign where` condition
-* loop through all entries in the `host.vars.disks` dictionary. That's `disk` and `disk /` as keys.
-* call `apply` on each, and set the service object name from the provided key
-* inside apply, the `generic-service` template is imported
-* defining the [disk](13-icinga-template-library.md#plugin-check-command-disk) check command requiring command arguments like `disk_partition`
-* adding the `config` dictionary items to `vars`. Simply said, there's now `vars.disk_partition` defined for the
-generated service
-
-Configuration example:
-
- apply Service for (disk => config in host.vars.disks) {
- import "generic-service"
-
- check_command = "disk"
-
- vars += config
-
- assign where host.vars.disks
- }
-
-A similar example is used for the `http` services. That way you can make your
-host the information provider for all apply rules. Define them once, and only
-manage your hosts.
-
-Look into [notifications.conf](2-getting-started.md#notifications-conf) how this technique is used
-for applying notifications to hosts and services using their type and user
-attributes.
-
-Don't forget to install the [check plugins](2-getting-started.md#setting-up-check-plugins) required by
-the hosts and services and their check commands.
-
-Further details on the monitoring configuration can be found in the
-[monitoring basics](3-monitoring-basics.md#monitoring-basics) chapter.
-
-#### <a id="users-conf"></a> users.conf
+The recommended way of installing these standard plugins is to use your
+distribution's package manager.
-Defines the `icingaadmin` User and the `icingaadmins` UserGroup. The latter is used in
-[hosts.conf](2-getting-started.md#hosts-conf) for defining a custom host attribute later used in
-[notifications.conf](2-getting-started.md#notifications-conf) for notification apply rules.
+Debian/Ubuntu:
- object User "icingaadmin" {
- import "generic-user"
+ # apt-get install nagios-plugins
- display_name = "Icinga 2 Admin"
- groups = [ "icingaadmins" ]
+RHEL/CentOS:
- email = "icinga@localhost"
- }
+ # yum install nagios-plugins-all
- object UserGroup "icingaadmins" {
- display_name = "Icinga 2 Admin Group"
- }
+The packages for RHEL/CentOS depend on other packages which are distributed
+as part of the [EPEL repository](http://fedoraproject.org/wiki/EPEL). Please
+make sure to enable this repository by following
+[these instructions](http://fedoraproject.org/wiki/EPEL#How_can_I_use_these_extra_packages.3F).
+Fedora:
-#### <a id="notifications-conf"></a> notifications.conf
+ # dnf install nagios-plugins-all
-Notifications for check alerts are an integral part or your
-Icinga 2 monitoring stack.
+SLES/openSUSE:
-The shipped example defines two notification apply rules for hosts and services.
-Both `apply` rules match on the same condition: They are only applied if the
-nested dictionary attribute `notification.mail` is set.
+ # zypper install monitoring-plugins
-Please note that the `to` keyword is important in [notification apply rules](3-monitoring-basics.md#using-apply-notifications)
-defining whether these notifications are applies to hosts or services.
-The `import` keyword imports the specific mail templates defined in [templates.conf](2-getting-started.md#templates-conf).
+The packages for SLES/OpenSUSE depend on other packages which are distributed
+as part of the [server:monitoring repository](https://build.opensuse.org/project/repositories/server:monitoring).
+Please make sure to enable this repository beforehand.
-The `interval` attribute is not explicitly set - it [defaults to 30 minutes](12-object-types.md#objecttype-notification).
+FreeBSD:
-By setting the `user_groups` to the value provided by the
-respective [host.vars.notification.mail](2-getting-started.md#hosts-conf) attribute we'll
-implicitely use the`icingaadmins` UserGroup defined in [users.conf](2-getting-started.md#users-conf).
+ # pkg install monitoring-plugins
- apply Notification "mail-icingaadmin" to Host {
- import "mail-host-notification"
+Depending on which directory your plugins are installed into you may need to
+update the global `PluginDir` constant in your [Icinga 2 configuration](4-configuring-icinga-2.md#constants-conf).
+This constant is used by the check command definitions contained in the Icinga Template Library
+to determine where to find the plugin binaries.
- user_groups = host.vars.notification.mail.groups
+> **Note**
+>
+> Please refer to the [plugins](14-addons-plugins.md#plugins) chapter for details about how to integrate
+> additional check plugins into your Icinga 2 setup.
- assign where host.vars.notification.mail
- }
+## <a id="running-icinga2"></a> Running Icinga 2
- apply Notification "mail-icingaadmin" to Service {
- import "mail-service-notification"
+### <a id="init-script"></a> Init Script
- user_groups = host.vars.notification.mail.groups
+Icinga 2's init script is installed in `/etc/init.d/icinga2` (`/usr/local/etc/rc.d/icinga2` on FreeBSD) by default:
- assign where host.vars.notification.mail
- }
+ # /etc/init.d/icinga2
+ Usage: /etc/init.d/icinga2 {start|stop|restart|reload|checkconfig|status}
-More details on defining notifications and their additional attributes such as
-filters can be read in [this chapter](3-monitoring-basics.md#notifications).
+The init script supports the following actions:
-#### <a id="commands-conf"></a> commands.conf
+ 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.
-This is the place where your own command configuration can be defined. By default
-only the notification commands used by the notification templates defined in [templates.conf](2-getting-started.md#templates-conf).
+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.
-> **Tip**
->
-> Icinga 2 ships the most common command definitions already in the
-> [Plugin Check Commands](13-icinga-template-library.md#plugin-check-commands) definitions. More details on
-> that topic in the [troubleshooting section](8-troubleshooting.md#check-command-definitions).
+### <a id="systemd-service"></a> systemd Service
-You can freely customize these notification commands, and adapt them for your needs.
-Read more on that topic [here](3-monitoring-basics.md#notification-commands).
+Some distributions (e.g. Fedora, openSUSE and RHEL/CentOS 7) use systemd. The
+Icinga 2 packages automatically install the necessary systemd unit files.
-#### <a id="groups-conf"></a> groups.conf
+The Icinga 2 systemd service can be (re-)started, reloaded, stopped and also
+queried for its current status.
-The example host defined in [hosts.conf](hosts-conf) already has the
-custom attribute `os` set to `Linux` and is therefore automatically
-a member of the host group `linux-servers`.
+ # 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
+ 21727 /usr/sbin/icinga2 -c /etc/icinga2/icinga2.conf -d -e /var/log/icinga2/error.log -u icinga -g icinga --no-stack-rlimit
-This is done by using the [group assign](10-language-reference.md#group-assign) expressions similar
-to previously seen [apply rules](3-monitoring-basics.md#using-apply).
+ 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.
- object HostGroup "linux-servers" {
- display_name = "Linux Servers"
+The `systemctl` command supports the following actions:
- assign where host.vars.os == "Linux"
- }
+ 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`)
- object HostGroup "windows-servers" {
- display_name = "Windows Servers"
+Examples:
- assign where host.vars.os == "Windows"
- }
+ # systemctl enable icinga2
-Service groups can be grouped together by similar pattern matches.
-The [match() function](10-language-reference.md#function-calls) expects a wildcard match string
-and the attribute string to match with.
+ # systemctl restart icinga2
+ Job for icinga2.service failed. See 'systemctl status icinga2.service' and 'journalctl -xn' for details.
- object ServiceGroup "ping" {
- display_name = "Ping Checks"
+If you're stuck with configuration errors, you can manually invoke the
+[configuration validation](8-cli-commands.md#config-validation).
- assign where match("ping*", service.name)
- }
+### FreeBSD
- object ServiceGroup "http" {
- display_name = "HTTP Checks"
+On FreeBSD you need to enable icinga2 in your rc.conf
- assign where match("http*", service.check_command)
- }
+ # sysrc icinga2_enable=yes
- object ServiceGroup "disk" {
- display_name = "Disk Checks"
+ # service icinga2 restart
- assign where match("disk*", service.check_command)
- }
+## <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 and SUSE package `icinga2-common` installs these files into `/usr/share/doc/icinga2-common-[x.x.x]/syntax`
+(where `[x.x.x]` is the version number, e.g. `2.4.3` or `2.4.4`). Sources provide these files in `tools/syntax`.
+On Debian systems the `icinga2-common` package provides only the Nano configuration file (`/usr/share/nano/icinga2.nanorc`);
+to obtain the Vim configuration, please install the extra package `vim-icinga2`. The files are located in `/usr/share/vim/addons`.
-#### <a id="templates-conf"></a> templates.conf
+### <a id="configuration-syntax-highlighting-vim"></a> Configuration Syntax Highlighting using Vim
-All shipped example configuration objects use generic global templates by
-default. Be it setting a default `check_command` attribute in the `generic-host`
-templates for your hosts defined in [hosts.conf](2-getting-started.md#hosts-conf), or defining
-the default `states` and `types` filters for notification apply rules defined in
-[notifications.conf](2-getting-started.md#notifications-conf).
+Install the package `vim-icinga2` with your distribution's package manager.
+Debian/Ubuntu:
- template Host "generic-host" {
- max_check_attempts = 5
- check_interval = 1m
- retry_interval = 30s
+ $ apt-get install vim-icinga2 vim-addon-manager
+ $ vim-addon-manager -w install icinga2
+ Info: installing removed addon 'icinga2' to /var/lib/vim/addons
- check_command = "hostalive"
- }
+RHEL/CentOS/Fedora:
- template Service "generic-service" {
- max_check_attempts = 3
- check_interval = 1m
- retry_interval = 30s
- }
+ $ yum install vim-icinga2
-The `hostalive` check command is shipped with Icinga 2 in the
-[Plugin Check Commands](13-icinga-template-library.md#plugin-check-commands).
+SLES/openSUSE:
+ $ zypper install vim-icinga2
- template Notification "mail-host-notification" {
- command = "mail-host-notification"
+Ensure that syntax highlighting is enabled e.g. by editing the user's `vimrc`
+configuration file:
- states = [ Up, Down ]
- types = [ Problem, Acknowledgement, Recovery, Custom,
- FlappingStart, FlappingEnd,
- DowntimeStart, DowntimeEnd, DowntimeRemoved ]
+ $ vim ~/.vimrc
+ syntax on
- period = "24x7"
- }
+Test it:
- template Notification "mail-service-notification" {
- command = "mail-service-notification"
+ $ vim /etc/icinga2/conf.d/templates.conf
- states = [ OK, Warning, Critical, Unknown ]
- types = [ Problem, Acknowledgement, Recovery, Custom,
- FlappingStart, FlappingEnd,
- DowntimeStart, DowntimeEnd, DowntimeRemoved ]
+
- period = "24x7"
- }
-More details on `Notification` object attributes can be found [here](12-object-types.md#objecttype-notification).
+### <a id="configuration-syntax-highlighting-nano"></a> Configuration Syntax Highlighting using Nano
+Install the package `nano-icinga2` with your distribution's package manager.
-#### <a id="downtimes-conf"></a> downtimes.conf
+Debian/Ubuntu:
-The `load` service apply rule defined in [services.conf](2-getting-started.md#services-conf) defines
-the `backup_downtime` custom attribute.
+**Note:** The syntax files are installed with the `icinga2-common` package already.
-The [ScheduledDowntime](12-object-types.md#objecttype-scheduleddowntime) apply rule uses this attribute
-to define the default value for the time ranges required for recurring downtime slots.
+RHEL/CentOS/Fedora:
- apply ScheduledDowntime "backup-downtime" to Service {
- author = "icingaadmin"
- comment = "Scheduled downtime for backup"
+ $ yum install nano-icinga2
- ranges = {
- monday = service.vars.backup_downtime
- tuesday = service.vars.backup_downtime
- wednesday = service.vars.backup_downtime
- thursday = service.vars.backup_downtime
- friday = service.vars.backup_downtime
- saturday = service.vars.backup_downtime
- sunday = service.vars.backup_downtime
- }
+SLES/openSUSE:
- assign where service.vars.backup_downtime != ""
- }
+ $ zypper install nano-icinga2
+Copy the `/etc/nanorc` sample file to your home directory.
-#### <a id="timeperiods-conf"></a> timeperiods.conf
+ $ cp /etc/nanorc ~/.nanorc
-This file ships the default timeperiod definitions for `24x7`, `9to5`
-and `never`. Timeperiod objects are referenced by `*period`
-objects such as hosts, services or notifications.
+Include the `icinga2.nanorc` file.
+ $ vim ~/.nanorc
-#### <a id="satellite-conf"></a> satellite.conf
+ ## Icinga 2
+ include "/usr/share/nano/icinga2.nanorc"
-Ships default templates and dependencies for [monitoring remote clients](4-monitoring-remote-systems.md#icinga2-remote-client-monitoring)
-using service discovery and [config generation](4-monitoring-remote-systems.md#icinga2-remote-monitoring-master-discovery-generate-config)
-on the master. Can be ignored/removed on setups not using this features.
+Test it:
+ $ nano /etc/icinga2/conf.d/templates.conf
-Further details on the monitoring configuration can be found in the
-[monitoring basics](3-monitoring-basics.md#monitoring-basics) chapter.
+
-## <a id="configuring-db-ido"></a> Configuring DB IDO
+## <a id="setting-up-icingaweb2"></a> Setting up Icinga Web 2
-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.
+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.
-You only need to set up the IDO modules if you're using an external project which uses
-the IDO database.
+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.
There is a separate module for each database backend. At present support for
both MySQL and PostgreSQL is implemented.
-Icinga 2 uses the Icinga 1.x IDOUtils database schema. Icinga 2 requires additional
-features not yet released with older Icinga 1.x versions.
-
-> **Note**
->
-> Please check the [what's new](1-about.md#whats-new) section for the required schema version.
-
-### <a id="installing-database"></a> Installing the Database Server
-
-In order to use DB IDO you need to setup either [MySQL](2-getting-started.md#installing-database-mysql-server)
-or [PostgreSQL](2-getting-started.md#installing-database-postgresql-server) as supported database server.
+### <a id="configuring-db-ido-mysql"></a> Configuring DB IDO MySQL
#### <a id="installing-database-mysql-server"></a> Installing MySQL database server
# yum install mysql-server mysql
# chkconfig mysqld on
# service mysqld start
+ # mysql_secure_installation
-RHEL/CentOS 7 and Fedora 20 prefer MariaDB over MySQL:
+RHEL/CentOS 7 and Fedora:
# yum install mariadb-server mariadb
# systemctl enable mariadb
# systemctl start mariadb
+ # mysql_secure_installation
SUSE:
# chkconfig mysqld on
# service mysqld start
-RHEL based distributions do not automatically set a secure root password. Do that **now**:
-
- # /usr/bin/mysql_secure_installation
-
-#### <a id="installing-database-postgresql-server"></a> Installing PostgreSQL database server
-
-Debian/Ubuntu:
-
- # apt-get install postgresql
+FreeBSD:
-RHEL/CentOS 5/6:
+ # pkg install mysql56-server
+ # sysrc mysql_enable=yes
+ # service mysql-server restart
+ # mysql_secure_installation
- # yum install postgresql-server postgresql
- # chkconfig postgresql on
- # service postgresql start
-
-RHEL/CentOS 7 and Fedora 20 use [systemd](2-getting-started.md#systemd-service):
-
- # yum install postgresql-server postgresql
- # systemctl enable postgresql
- # systemctl start postgresql
-
-SUSE:
+#### <a id="installing-database-mysql-modules"></a> Installing the IDO modules for MySQL
- # zypper install postgresql postgresql-server
- # chkconfig postgresql on
- # service postgresql start
-
-### <a id="configuring-db-ido-mysql"></a> Configuring DB IDO MySQL
-
-First of all you have to install the `icinga2-ido-mysql` package using your
+The next step is to install the `icinga2-ido-mysql` package using your
distribution's package manager.
Debian/Ubuntu:
# zypper install icinga2-ido-mysql
+FreeBSD:
+On FreeBSD the IDO modules for MySQL are included with the icinga2 package
+and located at /usr/local/share/icinga2-ido-mysql/schema/mysql.sql
> **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.
+> 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.
#### <a id="setting-up-mysql-db"></a> Setting up the MySQL database
# mysql -u root -p
mysql> CREATE DATABASE icinga;
- GRANT SELECT, INSERT, UPDATE, DELETE, DROP, CREATE VIEW, INDEX, EXECUTE ON icinga.* TO 'icinga'@'localhost' IDENTIFIED BY 'icinga';
- quit
+ mysql> GRANT SELECT, INSERT, UPDATE, DELETE, DROP, CREATE VIEW, INDEX, EXECUTE ON icinga.* TO 'icinga'@'localhost' IDENTIFIED BY 'icinga';
+ mysql> quit
+
+
After creating the database you can import the Icinga 2 IDO schema using the
following command:
# mysql -u root -p icinga < /usr/share/icinga2-ido-mysql/schema/mysql.sql
-#### <a id="upgrading-mysql-db"></a> Upgrading the MySQL database
+#### <a id="enabling-ido-mysql"></a> Enabling the IDO MySQL module
-If you're upgrading an existing Icinga 2 instance you should check the
-`/usr/share/icinga2-ido-mysql/schema/upgrade` directory for an incremental schema upgrade file.
+The package provides a new configuration file that is installed in
+`/etc/icinga2/features-available/ido-mysql.conf`. You will need to
+update the database credentials in this file.
-> **Note**
->
-> If there isn't an upgrade file for your current version available there's nothing to do.
+All available attributes are explained in the
+[IdoMysqlConnection object](6-object-types.md#objecttype-idomysqlconnection)
+chapter.
-Apply all database schema upgrade files incrementially.
+You can enable the `ido-mysql` feature configuration file using
+`icinga2 feature enable`:
- # mysql -u root -p icinga < /usr/share/icinga2-ido-mysql/schema/upgrade/<version>.sql
+ # icinga2 feature enable ido-mysql
+ Module 'ido-mysql' was enabled.
+ Make sure to restart Icinga 2 for these changes to take effect.
-The Icinga 2 DB IDO module will check for the required database schema version on startup
-and generate an error message if not satisfied.
+After enabling the ido-mysql feature you have to restart Icinga 2:
+Debian/Ubuntu, RHEL/CentOS 6 and SUSE:
-**Example:** You are upgrading Icinga 2 from version `2.0.2` to `2.2.0`. Look into
-the *upgrade* directory:
+ # service icinga2 restart
- $ ls /usr/share/icinga2-ido-mysql/schema/upgrade/
- 2.0.2.sql 2.1.0.sql 2.2.0.sql
+RHEL/CentOS 7 and Fedora:
-There are two new upgrade files called `2.1.0.sql` and `2.2.0.sql`
-which must be applied incrementially to your IDO database.
+ # systemctl restart icinga2
+FreeBSD:
-#### <a id="installing-ido-mysql"></a> Installing the IDO MySQL module
+ # service icinga2 restart
-The package provides a new configuration file that is installed in
-`/etc/icinga2/features-available/ido-mysql.conf`. You will need to update the
-database credentials in this file.
-All available attributes are listed in the
-[IdoMysqlConnection object](12-object-types.md#objecttype-idomysqlconnection) configuration details.
+### <a id="configuring-db-ido-postgresql"></a> Configuring DB IDO PostgreSQL
-You can enable the `ido-mysql` feature configuration file using `icinga2 feature enable`:
+#### <a id="installing-database-postgresql-server"></a> Installing PostgreSQL database server
- # icinga2 feature enable ido-mysql
- Module 'ido-mysql' was enabled.
- Make sure to restart Icinga 2 for these changes to take effect.
+Debian/Ubuntu:
-After enabling the ido-mysql feature you have to restart Icinga 2:
+ # apt-get install postgresql
-Debian/Ubuntu, RHEL/CentOS 6 and SUSE:
+RHEL/CentOS 5/6:
- # service icinga2 restart
+ # yum install postgresql-server postgresql
+ # chkconfig postgresql on
+ # service postgresql start
-RHEL/CentOS 7 and Fedora 20:
+RHEL/CentOS 7:
- # systemctl restart icinga2
+ # yum install postgresql-server postgresql
+ # postgresql-setup initdb
+ # systemctl enable postgresql
+ # systemctl start postgresql
-### <a id="configuring-db-ido-postgresql"></a> Configuring DB IDO PostgreSQL
+SUSE:
+
+ # zypper install postgresql postgresql-server
+ # chkconfig postgresql on
+ # service postgresql start
+
+FreeBSD:
+
+ # pkg install postgresql93-server
+ # sysrc postgresql_enable=yes
+ # service postgresql start
+
+#### <a id="installing-database-postgresql-modules"></a> Installing the IDO modules for PostgreSQL
-First of all you have to install the `icinga2-ido-pgsql` package using your
+The next step is to install the `icinga2-ido-pgsql` package using your
distribution's package manager.
Debian/Ubuntu:
# zypper install icinga2-ido-pgsql
+FreeBSD:
+
+On FreeBSD the IDO modules for PostgreSQL are included with the icinga2 package
+and located at /usr/local/share/icinga2-ido-pgsql/schema/pgsql.sql
+
> **Note**
>
> Upstream Debian packages provide a database configuration wizard by default.
Set up a PostgreSQL database for Icinga 2:
# cd /tmp
- # sudo -u postgres psql -c "CREATE ROLE icinga WITH LOGIN PASSWORD 'icinga'";
+ # 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
> **Note**
>
-> Using PostgreSQL 9.x you can omit the `createlang` command.
+> When using PostgreSQL 9.x you can omit the `createlang` command.
+> Also it is assumed here that your locale is set to utf-8, you may run into
+> problems otherwise.
-Locate your pg_hba.conf (Debian: `/etc/postgresql/*/main/pg_hba.conf`,
+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
# IPv6 local connections:
host all all ::1/128 ident
- # /etc/init.d/postgresql restart
+ # service postgresql restart
-After creating the database and permissions you can import the Icinga 2 IDO schema
-using the following command:
+After creating the database and permissions you can import the Icinga 2 IDO
+schema using the following command:
# export PGPASSWORD=icinga
# psql -U icinga -d icinga < /usr/share/icinga2-ido-pgsql/schema/pgsql.sql
-#### <a id="upgrading-postgresql-db"></a> Upgrading the PostgreSQL database
-
-If you're updating an existing Icinga 2 instance you should check the
-`/usr/share/icinga2-ido-pgsql/schema/upgrade` directory for an incremental schema upgrade file.
+
-> **Note**
->
-> If there isn't an upgrade file for your current version available there's nothing to do.
-
-Apply all database schema upgrade files incrementially.
-
- # export PGPASSWORD=icinga
- # psql -U icinga -d icinga < /usr/share/icinga2-ido-pgsql/schema/upgrade/<version>.sql
-The Icinga 2 DB IDO module will check for the required database schema version on startup
-and generate an error message if not satisfied.
-
-**Example:** You are upgrading Icinga 2 from version `2.0.2` to `2.1.0`. Look into
-the *upgrade* directory:
-
- $ ls /usr/share/icinga2-ido-pgsql/schema/upgrade/
- 2.0.2.sql 2.1.0.sql 2.2.0.sql
-
-There are two new upgrade files called `2.1.0.sql` and `2.2.0.sql`
-which must be applied incrementially to your IDO database.
-
-
-#### <a id="installing-ido-postgresql"></a> Installing the IDO PostgreSQL module
+#### <a id="enabling-ido-postgresql"></a> Enabling the IDO PostgreSQL module
The package provides a new configuration file that is installed in
-`/etc/icinga2/features-available/ido-pgsql.conf`. You will need to update the
-database credentials in this file.
-All available attributes are listed in the
-[IdoPgsqlConnection object](12-object-types.md#objecttype-idopgsqlconnection) configuration details.
+`/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
+[IdoPgsqlConnection object](6-object-types.md#objecttype-idopgsqlconnection)
+chapter.
-You can enable the `ido-pgsql` feature configuration file using `icinga2 feature enable`:
+You can enable the `ido-pgsql` feature configuration file using
+`icinga2 feature enable`:
# icinga2 feature enable ido-pgsql
Module 'ido-pgsql' was enabled.
After enabling the ido-pgsql feature you have to restart Icinga 2:
-Debian/Ubuntu, RHEL/CentOS 6 and SUSE:
+Debian/Ubuntu, RHEL/CentOS 6, SUSE and FreeBSD:
# service icinga2 restart
-RHEL/CentOS 7 and Fedora 20:
+RHEL/CentOS 7 and Fedora:
# systemctl restart icinga2
-### <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.
-
-You can enable the External Command Pipe using the CLI:
-
- # icinga2 feature enable command
-
-After that you will have to restart Icinga 2:
-
-Debian/Ubuntu, RHEL/CentOS 6 and SUSE:
-
- # service icinga2 restart
-
-RHEL/CentOS 7 and Fedora 20:
-
- # systemctl restart icinga2
-
-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
-enable sending commands to Icinga 2 through your web interface:
-
- # usermod -a -G icingacmd www-data
-
-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`.
-
-Change "www-data" to the user you're using to run queries.
-
-> **Note**
->
-> Packages will do that automatically. Verify that by running `id <your-webserver-user>` and skip this
-> step.
-
-## <a id="setting-up-icinga2-user-interfaces"></a> Setting up Icinga 2 User Interfaces
-
-Icinga 2 can be used with [Icinga Web 2](2-getting-started.md#setting-up-icingaweb2), using
-DB IDO or Livestatus as preferred backend provider, next to the command pipe.
-
-Icinga 2 also is compatible with Icinga 1.x user interfaces
-[Classic UI 1.x](2-getting-started.md#installing-icinga-classic-ui) and [Icinga Web 1.x](2-getting-started.md#setting-up-icinga-web)
-by providing additional features required as backends.
-
-Some Icinga 1.x interface features will only work in a limited manner due to
-[compatibility reasons](9-migrating-from-icinga-1x.md#differences-1x-2), other features like the
-statusmap parents are available by dumping the host dependencies as parents.
-Special restrictions are noted specifically in the sections below.
+### <a id="icinga2-user-interface-webserver"></a> Webserver
-You can also use other user interface addons, if you prefer. Keep in mind
-that Icinga 2 core features might not be fully supported in these addons.
-
-> **Tip**
->
-> Choose your preferred interface. There's no need to install [Classic UI 1.x](2-getting-started.md#setting-up-icinga-classic-ui)
-> if you prefer [Icinga Web 1.x](2-getting-started.md#setting-up-icinga-web) or [Icinga Web 2](2-getting-started.md#setting-up-icingaweb2) for example.
-
-### <a id="icinga2-user-interface-requirements"></a> Requirements
-
-* Web server (Apache2/Httpd, Nginx, Lighttp, etc)
-* User credentials
-* Firewall ports (tcp/80)
+Debian/Ubuntu:
-The Debian, RHEL and SUSE packages for Icinga [Classic UI](2-getting-started.md#setting-up-icinga-classic-ui),
-[Web](2-getting-started.md#setting-up-icinga-web) and [Icingaweb 2](2-getting-started.md#setting-up-icingaweb2) depend on Apache2
-as web server.
+ # apt-get install apache2
-#### <a id="icinga2-user-interface-webserver"></a> Webserver
+RHEL/CentOS 6:
-Debian/Ubuntu packages will automatically fetch and install the required packages.
+ # yum install httpd
+ # chkconfig httpd on
+ # service httpd start
-RHEL/CentOS/Fedora:
+RHEL/CentOS 7/Fedora:
# yum install httpd
- # chkconfig httpd on && service httpd start
- ## RHEL7
- # systemctl enable httpd && systemctl start httpd
+ # systemctl enable httpd
+ # systemctl start httpd
SUSE:
# zypper install apache2
- # chkconfig on && service apache2 start
+ # chkconfig on
+ # service apache2 start
-#### <a id="icinga2-user-interface-firewall-rules"></a> Firewall Rules
+FreeBSD (nginx, but you could also use the apache24 package):
+
+ # pkg install nginx php56-gettext php56-ldap php56-openssl php56-mysql php56-pdo_mysql php56-pgsql php56-pdo_pgsql php56-sockets php56-gd pecl-imagick pecl-intl
+ # sysrc php_fpm_enable=yes
+ # sysrc nginx_enable=yes
+ # sed -i '' "s/listen\ =\ 127.0.0.1:9000/listen\ =\ \/var\/run\/php5-fpm.sock/" /usr/local/etc/php-fpm.conf
+ # sed -i '' "s/;listen.owner/listen.owner/" /usr/local/etc/php-fpm.conf
+ # sed -i '' "s/;listen.group/listen.group/" /usr/local/etc/php-fpm.conf
+ # sed -i '' "s/;listen.mode/listen.mode/" /usr/local/etc/php-fpm.conf
+ # service php-fpm start
+ # service nginx start
+
+### <a id="icinga2-user-interface-firewall-rules"></a> Firewall Rules
Example:
# firewall-cmd --add-service=http
# firewall-cmd --permanent --add-service=http
-### <a id="setting-up-icingaweb2"></a> Setting up Icinga Web 2
-
-Icinga Web 2 supports `DB IDO` or `Livestatus` as backends.
-
-Using DB IDO as backend, you need to install and configure the
-[DB IDO backend](2-getting-started.md#configuring-db-ido).
-Once finished, you can enable the feature for DB IDO MySQL:
-
- # icinga2 feature enable ido-mysql
-
-Furthermore [external commands](3-monitoring-basics.md#external-commands) are supported through the external
-command pipe.
-
- # icinga2 feature enable command
-
-In order for commands to work you will need to [setup the external command pipe](2-getting-started.md#setting-up-external-command-pipe).
-
-[Icinga Web 2](https://github.com/Icinga/icingaweb2) ships its own
-web-based setup wizard which will guide you through the entire setup process.
-
-Generate the Webserver configuration and a setup token using its local cli
-and proceed with the web setup when accessing `/icingaweb2` after reloading
-your webserver configuration.
-
-Please consult the [installation documentation](https://github.com/Icinga/icingaweb2/blob/master/doc/installation.md)
-shipped with `Icinga Web 2` for further instructions on how to install
-`Icinga Web 2` and to configure backends, resources and instances manually.
-
-Check the [Icinga website](https://www.icinga.org) for release announcements
-and packages.
-
-
-### <a id="setting-up-icinga-classic-ui"></a> Setting up Icinga Classic UI 1.x
-
-Icinga 2 can write `status.dat` and `objects.cache` files in the format that
-is supported by the Icinga 1.x Classic UI. [External commands](3-monitoring-basics.md#external-commands)
-(a.k.a. the "command pipe") are also supported. It also supports writing Icinga 1.x
-log files which are required for the reporting functionality in the Classic UI.
-
-#### <a id="installing-icinga-classic-ui"></a> Installing Icinga Classic UI 1.x
-
-The Icinga package repository has both Debian and RPM packages. You can install
-the Classic UI using the following packages:
-
- Distribution | Packages
- --------------|---------------------
- Debian | icinga2-classicui
- RHEL/SUSE | icinga2-classicui-config icinga-gui
-
-The Debian packages require additional packages which are provided by the
-[Debian Monitoring Project](http://www.debmon.org) (`debmon`) repository.
-
-`libjs-jquery-ui` requires at least version `1.10.*` which is not available
-in Debian 7 (Wheezy) and Ubuntu 12.04 LTS (Precise). Add the following repositories
-to satisfy this dependency:
-
- Distribution | Package Repositories
- ------------------------------|------------------------------
- Debian Wheezy | [wheezy-backports](http://backports.debian.org/Instructions/) or [debmon](http://www.debmon.org)
- Ubuntu 12.04 LTS (Precise) | [Icinga PPA](https://launchpad.net/~formorer/+archive/icinga)
-
-On all distributions other than Debian you may have to restart both your web
-server as well as Icinga 2 after installing the Classic UI package.
-
-Icinga Classic UI requires the [StatusDataWriter](3-monitoring-basics.md#status-data), [CompatLogger](3-monitoring-basics.md#compat-logging)
-and [ExternalCommandListener](3-monitoring-basics.md#external-commands) features.
-Enable these features and restart Icinga 2.
-
- # icinga2 feature enable statusdata compatlog command
-
-In order for commands to work you will need to [setup the external command pipe](2-getting-started.md#setting-up-external-command-pipe).
-
-#### <a id="setting-up-icinga-classic-ui-summary"></a> Setting Up Icinga Classic UI 1.x Summary
-
-Verify that your Icinga 1.x Classic UI works by browsing to your Classic
-UI installation URL:
-
- Distribution | URL | Default Login
- --------------|--------------------------------------------------------------------------|--------------------------
- Debian | [http://localhost/icinga2-classicui](http://localhost/icinga2-classicui) | asked during installation
- all others | [http://localhost/icinga](http://localhost/icinga) | icingaadmin/icingaadmin
-
-For further information on configuration, troubleshooting and interface documentation
-please check the official [Icinga 1.x user interface documentation](http://docs.icinga.org/latest/en/ch06.html).
-
-### <a id="setting-up-icinga-web"></a> Setting up Icinga Web 1.x
-
-Icinga 2 can write to the same schema supplied by `Icinga IDOUtils 1.x` which
-is an explicit requirement to run `Icinga Web` next to the external command pipe.
-Therefore you need to setup the [DB IDO feature](2-getting-started.md#configuring-db-ido) remarked in the previous sections.
-
-#### <a id="installing-icinga-web"></a> Installing Icinga Web 1.x
-
-The Icinga package repository has both Debian and RPM packages. You can install
-Icinga Web using the following packages (RPMs ship an additional configuration package):
-
- Distribution | Packages
- --------------|-------------------------------------------------------
- RHEL/SUSE | icinga-web icinga-web-{mysql,pgsql}
- Debian | icinga-web icinga-web-config-icinga2-ido-{mysql,pgsql}
-
-#### <a id="icinga-web-rpm-notes"></a> Icinga Web 1.x on RPM based systems
-
-Additionally you need to setup the `icinga_web` database and import the database schema.
-Details can be found in the package `README` files, for example [README.RHEL](https://github.com/Icinga/icinga-web/blob/master/doc/README.RHEL)
-
-The Icinga Web RPM packages install the schema files into
-`/usr/share/doc/icinga-web-*/schema` (`*` means package version).
-The Icinga Web dist tarball ships the schema files in `etc/schema`.
-
-On SuSE-based distributions the schema files are installed in
-`/usr/share/doc/packages/icinga-web/schema`.
-
-Example for RHEL and MySQL:
-
- # mysql -u root -p
-
- mysql> CREATE DATABASE icinga_web;
- GRANT SELECT, INSERT, UPDATE, DELETE, DROP, CREATE VIEW, INDEX, EXECUTE ON icinga_web.* TO 'icinga_web'@'localhost' IDENTIFIED BY 'icinga_web';
- quit
+FreeBSD:
+Please consult the [FreeBSD Handbook](https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/firewalls.html) how to configure one of FreeBSD's firewalls.
- # mysql -u root -p icinga_web < /usr/share/doc/icinga-web-<version>/schema/mysql.sql
-Icinga Web requires the IDO feature as database backend using MySQL or PostgreSQL.
-Enable that feature, e.g. for MySQL.
-
- # icinga2 feature enable ido-mysql
-
-If you've changed your default credentials you may either create a read-only user
-or use the credentials defined in the IDO feature for Icinga Web backend configuration.
-Edit `databases.xml` accordingly and clear the cache afterwards. Further details can be
-found in the [Icinga Web documentation](http://docs.icinga.org/latest/en/icinga-web-config.html).
-
- # vim /etc/icinga-web/conf.d/databases.xml
+### <a id="setting-up-external-command-pipe"></a> Setting Up External Command Pipe
- # icinga-web-clearcache
+Web interfaces and other Icinga addons are able to send commands to
+Icinga 2 through the external command pipe.
-Additionally you need to enable the `command` feature for sending [external commands](3-monitoring-basics.md#external-commands):
+You can enable the External Command Pipe using the CLI:
# icinga2 feature enable command
-In order for commands to work you will need to [setup the external command pipe](2-getting-started.md#setting-up-external-command-pipe).
-
-Then edit the Icinga Web configuration for sending commands in `/etc/icinga-web/conf.d/access.xml`
-(RHEL) or `/etc/icinga-web/access.xml` (SUSE) setting the command pipe path
-to the default used in Icinga 2. Make sure to clear the cache afterwards.
-
- # vim /etc/icinga-web/conf.d/access.xml
-
- <write>
- <files>
- <resource name="icinga_pipe">/var/run/icinga2/cmd/icinga2.cmd</resource>
- </files>
- </write>
-
- # icinga-web-clearcache
-
-> **Note**
->
-> The path to the Icinga Web `clearcache` script may differ. Please check the
-> [Icinga Web documentation](https://docs.icinga.org) for details.
-
-#### <a id="icinga-web-debian-notes"></a> Icinga Web on Debian systems
-
-Since Icinga Web `1.11.1-2` the IDO auto-configuration has been moved into
-additional packages on Debian and Ubuntu.
-
-The package `icinga-web` no longer configures the IDO connection. You must now
-use one of the config packages:
-
- - `icinga-web-config-icinga2-ido-mysql`
- - `icinga-web-config-icinga2-ido-pgsql`
-
-These packages take care of setting up the [DB IDO](2-getting-started.md#configuring-db-ido) configuration,
-enabling the external command pipe for Icinga Web and depend on
-the corresponding packages of Icinga 2.
-
-Please read the `README.Debian` files for details and advanced configuration:
-
- - `/usr/share/doc/icinga-web/README.Debian`
- - `/usr/share/doc/icinga-web-config-icinga2-ido-mysql/README.Debian`
- - `/usr/share/doc/icinga-web-config-icinga2-ido-pgsql/README.Debian`
-
-When changing Icinga Web configuration files make sure to clear the config cache:
-
- # /usr/lib/icinga-web/bin/clearcache.sh
-
-> **Note**
->
-> If you are using an older version of Icinga Web, install it like this and adapt
-> the configuration manually as shown in [the RPM notes](2-getting-started.md#icinga-web-rpm-notes):
->
-> `apt-get install --no-install-recommends icinga-web`
-
-#### <a id="setting-up-icinga-web-summary"></a> Setting Up Icinga Web 1.x Summary
-
-Verify that your Icinga 1.x Web works by browsing to your Web installation URL:
-
- Distribution | URL | Default Login
- --------------|-------------------------------------------------------------|--------------------------
- Debian | [http://localhost/icinga-web](http://localhost/icinga-web) | asked during installation
- all others | [http://localhost/icinga-web](http://localhost/icinga-web) | root/password
-
-For further information on configuration, troubleshooting and interface documentation
-please check the official [Icinga 1.x user interface documentation](http://docs.icinga.org/latest/en/ch06.html).
-
-
-### <a id="additional-visualization"></a> Additional visualization
-
-There are many visualization addons which can be used with Icinga 2.
-
-Some of the more popular ones are [PNP](6-addons-plugins.md#addons-graphing-pnp), [inGraph](6-addons-plugins.md#addons-graphing-pnp)
-(graphing performance data), [Graphite](6-addons-plugins.md#addons-graphing-pnp), and
-[NagVis](6-addons-plugins.md#addons-visualization-nagvis) (network maps).
-
-
-## <a id="configuration-tools"></a> Configuration Tools
-
-If you require your favourite configuration tool to export Icinga 2 configuration, please get in
-touch with their developers. The Icinga project does not provide a configuration web interface
-or similar.
-
-> **Tip**
->
-> Get to know the new configuration format and the advanced [apply](3-monitoring-basics.md#using-apply) rules and
-> use [syntax highlighting](2-getting-started.md#configuration-syntax-highlighting) in vim/nano.
-
-If you're looking for puppet manifests, chef cookbooks, ansible recipes, etc - we're happy
-to integrate them upstream, so please get in touch at [https://support.icinga.org](https://support.icinga.org).
-
-These tools are in development and require feedback and tests:
-
-* [Ansible Roles](https://github.com/Icinga/icinga2-ansible)
-* [Puppet Module](https://github.com/Icinga/puppet-icinga2)
-
-## <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.
+After that you will have to restart Icinga 2:
- $ cp /etc/nanorc ~/.nanorc
+Debian/Ubuntu, RHEL/CentOS 6 and SUSE:
- # mkdir -p /etc/nano
- # cp icinga2.nanorc /etc/nano/
+ # service icinga2 restart
-Then include the icinga2.nanorc file in your ~/.nanorc by adding the following line:
+RHEL/CentOS 7 and Fedora:
- $ vim ~/.nanorc
+ # systemctl restart icinga2
- ## Icinga 2
- include "/etc/nano/icinga2.nanorc"
+FreeBSD:
-Test it:
+ # service icinga2 restart
- $ nano /etc/icinga2/conf.d/templates.conf
+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
+enable sending commands to Icinga 2 through your web interface:
+ # usermod -a -G icingacmd www-data
-## <a id="running-icinga2"></a> Running Icinga 2
+FreeBSD:
+On FreeBSD the rw directory is owned by the group `www`. You do not need to add the
+user `icinga` to the group `www`.
-### <a id="init-script"></a> Init Script
+Debian packages use `nagios` as the default user and group name. Therefore
+change `icingacmd` to `nagios`.
-Icinga 2's init script is installed in `/etc/init.d/icinga2` by default:
+The webserver's user is different between distributions so you might have to
+change `www-data` to `wwwrun`, `www`, or `apache`.
- # /etc/init.d/icinga2
- Usage: /etc/init.d/icinga2 {start|stop|restart|reload|checkconfig|status}
+Change `www-data` to the user you're using to run queries.
- 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.
+You can verify that the user has been successfully added to the `icingacmd`
+group using the `id` command:
-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.
+ $ id <your-webserver-user>
-### <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.
+### <a id="installing-icingaweb2"></a> Installing Icinga Web 2
-The Icinga 2 systemd service can be (re)started, reloaded, stopped and also queried for its current status.
+Please consult the [installation documentation](https://github.com/Icinga/icingaweb2/blob/master/doc/02-Installation.md)
+for further instructions on how to install Icinga Web 2.
- # 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
- └─21727 /usr/sbin/icinga2 -c /etc/icinga2/icinga2.conf -d -e /var/log/icinga2/error.log -u icinga -g icinga --no-stack-rlimit
-
- 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`)
-
-If you're stuck with configuration errors, you can manually invoke the [configuration validation](5-cli-commands.md#config-validation).
-
- # systemctl enable icinga2
-
- # systemctl restart icinga2
- Job for icinga2.service failed. See 'systemctl status icinga2.service' and 'journalctl -xn' for details.
+## <a id="install-addons"></a> Addons
+A number of additional features are available in the form of addons. A list of
+popular addons is available in the
+[Addons and Plugins](14-addons-plugins.md#addons-plugins) chapter.
projects / icinga2 / blobdiff