Forge Home


installation and configuration of icinga2,icingaweb2 with postgres as a backend on centos


3,833 latest version

2.3 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.1.5 (latest)
  • 0.1.4 (deleted)
  • 0.1.3
  • 0.1.2
  • 0.1.1 (deleted)
  • 0.1.0 (deleted)
released Jul 19th 2019
This version is compatible with:
  • Puppet Enterprise 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 4.7.0 < 7.0.0

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'vikas24pandey-icinga', '0.1.5'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add vikas24pandey-icinga
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install vikas24pandey-icinga --version 0.1.5

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



vikas24pandey/icinga — version 0.1.5 Jul 19th 2019


Table of Contents

  1. Description
  2. Setup - The basics of getting started with icinga
  3. Setup requirements
  4. Beginning with icinga
  5. Troubleshooting


This module will help to install icinga on Main server where backend will be Postgres DB using Puppet modules. Here puppet master machine will push configruation on puppet agent and configure it with icinga which will act as ICINGA main server.


Setup Requirements Minimum two machine installed and configured with puppet

Beginning with icinga

  • After configuration on puppte master & agent .

  • do puppet agent -t on agent machine (This will fetch configuration from master and do the installation ).

  • now access your local ip or localhost https::///icingaweb2.

  • login through admin/icingaweb2 (This credential is stored in pgsql icingaweb2 database).


  • in case gui is not accessible. check httpd service

  • delete file rm -rf /etc/httpd/conf.d/Nginxicingaweb2.conf

  • do httpd -t (to check any further syntax error in httpd conf).

  • now restart httpd "systemctl restart httpd.service"

if gui is not able to login :

  1. check psql -U icingaweb2 -h localhost -d icingaweb2 -W
  2. enter password "icingaweb2"
  3. if its not able to login then check /var/lib/pgsql/data/pg_hba.conf
  4. make sure icinga user is added with md5
  5. now restart pgsql ( systemctl restart postgresql.service).
  6. again try "psql -U icingaweb2 -h localhost -d icingaweb2 -W" (Now you must be able to login in DB).

if stil there is error in login then

  1. openssl passwd -1 icingaweb2 (Note down hash key)
  2. go into database icingaweb2 => table (icingaweb_user)
  3. and update admin password with above generated key.

###Compatibility: OS => Centos (tested)

GIT link: