[icinga-checkins] icinga.org: icinga-core/mfriedrich/cgis: icinga.spec: add README. RHEL README.RHEL.idoutils to upstream, being installed as docs ( thx Michael Gruener, Stefan Marx) #2212 1/2

git at icinga.org git at icinga.org
Sat Feb 25 21:21:25 CET 2012


Module: icinga-core
Branch: mfriedrich/cgis
Commit: 2d7e66fdde0090af8da80f17ad132a0a04324197
URL:    https://git.icinga.org/?p=icinga-core.git;a=commit;h=2d7e66fdde0090af8da80f17ad132a0a04324197

Author: Michael Friedrich <michael.friedrich at univie.ac.at>
Date:   Sat Feb 25 01:24:37 2012 +0100

icinga.spec: add README.RHEL README.RHEL.idoutils to upstream, being installed as docs (thx Michael Gruener, Stefan Marx) #2212 1/2

revamped, and reworked a bit for proper upstream. also added detailed
instructions on idoutils postgresql setup, as well as upgrade hints.

refs #2212

---

 Changelog            |    1 +
 README.RHEL          |   76 ++++++++++++++++++++++++
 README.RHEL.idoutils |  157 ++++++++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 234 insertions(+), 0 deletions(-)

diff --git a/Changelog b/Changelog
index 61c35d7..fc46169 100644
--- a/Changelog
+++ b/Changelog
@@ -30,6 +30,7 @@ ENHANCEMENTS
 * icinga.spec: make aware of the change of idomod.o location and changed extension (now .so) #2350
 * icinga.spec: add "README LICENSE Changelog UPGRADING" to all packages as docs (thx Michael Gruener) #2212
 * icinga.spec: put module/idoutils/db into docs instead of manually copying to /etc/icinga/idoutils (thx Michael Gruener) #2357
+* icinga.spec: add README.RHEL README.RHEL.idoutils to upstream, being installed as docs (thx Michael Gruener, Stefan Marx) #2212
 
 FIXES
 * core: Plug some macro leaks triggered when sending notifications (Andreas Ericsson) #2109
diff --git a/README.RHEL b/README.RHEL
new file mode 100644
index 0000000..7d6fec5
--- /dev/null
+++ b/README.RHEL
@@ -0,0 +1,76 @@
+Introduction

+------------

+

+The packages are made as little dependend on each other as possible, to get the

+maximum flexibility in setting up distributed monitoring environments. This

+means, that you may have to install some additional packages manually. Yum is

+your friend.

+

+Recommended OS Installation

+---------------------------

+

+Repositories:

+* Fedora EPEL repository (http://fedoraproject.org/wiki/EPEL)

+* RHN Channel "Red Hat Optional Server" if using RHEL

+* Repoforge repository if needed (http://wiki.centos.org/AdditionalResources/Repositories/RPMForge)

+

+It is also recommended to switch SELinux to "disabled" or develop a proper policy

+for icinga et al (if you have it, share it ;-)).

+

+Order of Installation

+---------------------

+

+Keeping a certain order of installation will lead you to a working monitoring

+setup in a relatively short time. Use yum to pull the proper dependencies

+automatically.

+

+1. Install icinga

+

+2. Install the needed nagios-plugins (either Fedora EPEL repository or Repoforge

+   "yum search nagios-plugins" gives you a list)

+

+3. If you need or want the classic gui, install icinga-gui. If you want plain

+   monitoring with icinga core and configure everything else by hand, you are done.

+

+4. Optional: install icinga-idoutils. Icinga Data Output Utils are necessary for

+   various database backed guis such as Icinga Web or Icinga Reporting. IDOUtils

+   use the libdbi database abstraction layer and can use MySQL or Postgresql with

+   this package.

+

+4.1 Create the idoutils database. For details see the README.idoutils of the

+    icinga-idoutils package.

+    Detailed information can be found in the "Creation of Database and IDOUtils" section

+    in the official docs as well as the wiki howtos.

+    http://docs.icinga.org/latest/en/quickstart-idoutils.html

+    https://wiki.icinga.org/display/howtos/Setting+up+Icinga+with+IDOUtils

+

+5. Optional: install additional Icinga guis like Icinga Web or Icinga Reporting as well

+   as addons such as PNP4Nagios, Check_MK or NagVis. For a suggested list please

+   either consult the docs or the wiki, or ask community members at icinga-portal.org

+

+

+Troubleshooting

+---------------

+

+- check if you have set SELinux to "disabled" mode

+- check that your local firewall rules contain appropriate rules for the

+  webserver and non-local database-connections

+- start the components in the rigth order: database, ido2db, icinga, httpd

+- check if idomod loads correctly

+  (/var/log/icinga/icinga.log: idomod: Successfully connected to data sink)

+- check the httpd error.log, the icinga.log and the syslog

+- in case of possible bugs, turn on debugging and refer to the debug logs

+

+Recommended Reading

+-------------------

+

+http://docs.icinga.org

+http://wiki.icinga.org

+http://www.icinga-portal.org

+

+Suggestions and Bugreports

+--------------------------

+

+If you want to make suggestions for the way this software is packaged or want

+to report bugs related to the packaging of this software, please report to

+the Icinga bug tracker located at https://dev.icinga.org - Core

diff --git a/README.RHEL.idoutils b/README.RHEL.idoutils
new file mode 100644
index 0000000..13980f2
--- /dev/null
+++ b/README.RHEL.idoutils
@@ -0,0 +1,157 @@
+IDOUtils Notes for RHEL packages
+================================
+
+
+* IDOMOD Setup
+
+
+DO NOT EDIT icinga.cfg for broker_module entry!!! Icinga RPMs will use the
+/etc/icinga/modules/idoutils.cfg with the module definition automatically.
+Defining that twice can lead into unwanted errors!
+
+Verify that by looking into the modules/idoutils.cfg file
+
+# vim /etc/icinga/modules/idoutils.cfg
+
+Other event broker modules can be defined using this module definition as well.
+
+
+* IDO2DB Setup
+
+Edit your database credentials in ido2db.cfg ...
+
+# vim /etc/icinga/ido2db.cfg
+
+db_servertype=mysql
+#db_servertype=pgsql
+db_host=localhost
+db_port=3306
+#db_port=5432
+db_name=icinga
+db_prefix=icinga_
+db_user=icinga
+db_pass=icinga
+
+... and create the database like described below.
+
+=========
+= MySQL
+=========
+
+Create Database, User, Grants
+-----------------------------
+
+# mysql -u root -p
+
+mysql> CREATE DATABASE icinga;
+Query OK, 1 row affected (0.01 sec)
+
+mysql>  GRANT USAGE ON *.* TO 'icinga'@'localhost'
+          IDENTIFIED BY 'icinga'
+          WITH MAX_QUERIES_PER_HOUR 0
+          MAX_CONNECTIONS_PER_HOUR 0
+          MAX_UPDATES_PER_HOUR 0;
+
+mysql>  GRANT SELECT , INSERT , UPDATE , DELETE, DROP, CREATE VIEW
+          ON icinga.* TO 'icinga'@'localhost';
+
+mysql>  FLUSH PRIVILEGES;
+
+mysql> quit
+
+Import database schema
+----------------------
+
+# cd /usr/share/doc/icinga-idoutils/db/mysql
+# mysql -u root -p icinga < mysql.sql
+
+
+=============
+= Postgresql
+=============
+
+Create Database, User, Grants
+-----------------------------
+
+# su - postgres
+
+postgres:~$ psql template1
+template1=# create database icinga;
+template1=# \q
+
+postgres:~$ createlang plpgsql icinga
+
+postgres:~$ psql
+postgres=# create role icinga;
+postgres=# alter role icinga login;
+postgres=# grant all on database icinga to icinga;
+postgres=# \q
+
+Import database schema
+----------------------
+
+postgres:~$ cd /usr/share/doc/icinga-idoutils/db/pgsql
+postgres:~$ psql -U icinga -d icinga < pgsql.sql
+
+Setup trusted local icinga user
+-------------------------------
+
+Now that Postgresql does use a local user to be trusted (insecure, but good as startup),
+edit pg_hba.conf accordingly. See Postgresql Manual for a more advanced setup on user
+auth and privilegues.
+
+# vim /var/lib/pgsql/data/pg_hba.conf
+
+# TYPE  DATABASE    USER        CIDR-ADDRESS          METHOD
+
+# "local" is for Unix domain socket connections only
+local   all         all                               trust
+# IPv4 local connections:
+host    all         all         127.0.0.1/32          trust
+# IPv6 local connections:
+host    all         all         ::1/128               trust
+
+#icinga
+local    icinga     icinga                            trust
+
+and reload the Postgresql server.
+
+
+==========
+= Upgrade
+==========
+
+There is no db upgrade script like in Debian, so you need to keep track of that yourself.
+
+First, get the schema version
+
+# mysql -u root -p icinga
+
+mysql> SELECT * from icinga_dbversion;
++--------------+----------+---------+
+| dbversion_id | name     | version |
++--------------+----------+---------+
+|            1 | idoutils | 1.6.0   |
++--------------+----------+---------+
+1 row in set (0.01 sec)
+
+and then decide, what to do - based on the official upgrade docs:
+http://docs.icinga.org/latest/en/upgrading_idoutils.html
+
+Remember - the upgrade steps need to be applied incremential, version by version.
+
+e.g.
+# cd /usr/share/doc/icinga-idoutils/db/mysql/upgrade/
+# mysql -u root -p icinga < mysql-upgrade-1.7.0.sql
+
+
+===========
+= Advanced
+===========
+
+Advanced guides and upgrade information can be found in the docs and wiki:
+
+http://docs.icinga.org/latest/en/quickstart-idoutils.html
+http://docs.icinga.org/latest/en/upgrading_idoutils.html
+
+https://wiki.icinga.org/display/howtos/Setting+up+Icinga+with+IDOUtils+on+RHEL





More information about the icinga-checkins mailing list