nagios, check_mk, pnp4nagios, nagvis

Autre choix pour une petite installation de surveillance réseau.
Mix de plusieurs tuto, dont
http://blog.stefandanielschwarz.de/2010/01/howto-how-to-install-nagios-with.html
http://mathias-kettner.de/checkmk_windows.html
http://wiki.monitoring-fr.org/addons/check_mk/check_mk-install

Donc, en partant d'une installation Nagios tout neuve.

Update PHP (pour l'installation de pnp4nagios plus tard

Il faut update les paquets php de 5.1.6 a 5.2 en piochant dans les repos testing pour pnp4nagios.
http://wiki.centos.org/HowTos/PHP_5.1_To_5.2

php-eaccelerator.x86_64 0:5.1.6_0.9.5.2-4.el5.rf (j'ai été obligé de retirer celui ci pour proceder a l'update)

Donc, en suivant le tuto ici
http://wiki.centos.org/HowTos/PHP_5.1_To_5.2

This guide describes how to upgrade the standard PHP 5.1.x packages in CentOS 5.x 32-bit to the current development versions 5.2.x. These instructions were created using CentOS 5.3 32-bit and with the following PHP packages installed:

Code:

# rpm -qa |grep php

Citation :

php-common-5.1.6-15.el5.i386
php-cli-5.1.6-15.el5.i386
php-5.1.6-15.el5.i386
php-pdo-5.1.6-15.el5.i386
php-bcmath-5.1.6-15.el5.i386
php-ldap-5.1.6-15.el5.i386
php-devel-5.1.6-15.el5.i386
php-gd-5.1.6-15.el5.i386
php-xml-5.1.6-15.el5.i386
php-mbstring-5.1.6-15.el5.i386
php-mysql-5.1.6-15.el5.i386
php-dba-5.1.6-15.el5.i386

As long as you're using the standard PHP packages on your CentOS server you won't need to do anything extra. If you're using extra PHP packages that aren't part of the standard CentOS repositories (like php-mcrypt) you'll have to remove them or find updated versions of them.

Add the development repositories

First thing we need to do is add the development repositories to yum. When we add the development repository we're going to configure it so it only pulls PHP packages. To start we'll need create a new yum repository configuration file (use your favorite editor):

Code:

 # nano /etc/yum.repos.d/CentOS-Testing.repo

Copy/paste the following into this file:

Citation :

# CentOS-Testing:
# !!!! CAUTION !!!!
# This repository is a proving grounds for packages on their way to CentOSPlus and CentOS Extras.
# They may or may not replace core CentOS packages, and are not guaranteed to function properly.
# These packages build and install, but are waiting for feedback from testers as to
# functionality and stability. Packages in this repository will come and go during the
# development period, so it should not be left enabled or used on production systems without due
# consideration.
[c5-testing]
name=CentOS-5 Testing
baseurl=http://dev.centos.org/centos/$releasever/testing/$basearch/
enabled=1
gpgcheck=1
gpgkey=http://dev.centos.org/centos/RPM-GPG-KEY-CentOS-testing
includepkgs=php*

Make sure to remove any spaces at the start of each line, then save and close the file and you're done.

Update PHP packages

Before updating your PHP packages you'll want to get a list of what you currently have installed. To get a list of current PHP packages run the following:

Code:

# rpm -qa |grep php

Now you can use yum to update the PHP packages on your system:

Code:

 # yum update php-*

You should be shown a list of packages that are going to be updated. Compare it to the list of PHP packages on your system. Note any packages that are not in the list. You'll need to remove these packages or find updates for them because they won't work after you update to PHP 5.2.x. If that is acceptable type "y" to continue and let yum update the packages.

Once yum has completed restart Apache:

Code:

 # service httpd restart

Installation de check_mk

Téléchargez le fichier ici
http://mathias-kettner.de/check_mk_download.html

par exemple

Code:

wget http://mathias-kettner.de/download/check_mk-1.1.7i5.tar.gz

puis

Code:

tar xzf check_mk-1.1.7i5.tar.gz

Code:

cd check_mk-1.1.7i5

Si vous savez pas, faites "Entré" partout, c'est ce que j'ai fait^^

Code:

./setup.sh

Alors là, par sur du tout, je le fais en live, je corigerais après (y a qu'une ligne)

Code:

sed -i~ "s|/nagios/pnp/index.php?host=\$HOSTNAME\$&srv=\$SERVICEDESC\\$|/pnp4nagios/graph?host=\$HOSTNAME\$\&srv=\$SERVICEDESC\$' class='tips' rel='/pnp4nagios/popup?host=\$HOSTNAME\$\&srv=\$SERVICEDESC\$|;s|/nagios/pnp/index.php?host=\$HOSTNAME\\$|/pnp4nagios/graph?host=\$HOSTNAME\$\&srv=_HOST_' class='tips' rel='/pnp4nagios/popup?host=\$HOSTNAME\$\&srv=_HOST_|" /usr/share/doc/check_mk/check_mk_templates.cfg

permet de refaire l'install sans les (default) partout

Code:

rm  ~/.check_mk_setup.conf

puis restart httpd et nagios

Code:

service httpd restart
service nagios restart

ou

Code:

/etc/init.d/nagios restart
/etc/init.d/httpd restart

De la vous devriez avoir accès à la page www.l'adresseipserveur/check_mk/

Donc, à suivre pnp4nagios nagvis etc...

Now that check_mk is installed, we'll enable monitoring its own host by installing the check_mk agent. While the agent can be queried through various means, the regular way is by making it accessible through xinetd, so we install that first:

Code:

yum install xinetd

Then we only need to copy the agent script check_mk_agent.linux to /usr/bin/check_mk_agent and the xinetd configuration file xinetd.conf to /etc/xinetd.d/check_mk:

Code:

cp -p /usr/share/check_mk/agents/check_mk_agent.linux /usr/bin/check_mk_agent
cp -p /usr/share/check_mk/agents/xinetd.conf /etc/xinetd.d/check_mk
/etc/init.d/xinetd restart

Une petite vérification pour voir si le démon est en écoute sur le port 6556 par défaut.

Code:

netstat -ltn

Citation :

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:5666 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:6556 0.0.0.0:* LISTEN
tcp6 0 0 :::22 :::* LISTEN

Il reste à tester le démon en l'interrogeant avec check_mk

Code:

check_mk -I alltcp localhost

Le démon découvre alors les services associé à la machine

Citation :

No new checks of type oracle_asm_dg.
No new checks of type vms_md.
1 new checks written to /var/lib/check_mk/autochecks/cpu.loads-2009-04-28_10.00.58.cfg
No new checks of type lsi.disk.
No new checks of type statgrab_net.link.
No new checks of type statgrab_net.params.
No new checks of type oracle_tbs.
No new checks of type multipath.
1 new checks written to /var/lib/check_mk/autochecks/cpu.threads-2009-04-28_10.00.58.cfg
2 new checks written to /var/lib/check_mk/autochecks/diskstat-2009-04-28_10.00.58.cfg
No new checks of type winperf.cpuusage.
No new checks of type vms_sys.mem.
No new checks of type local.
No new checks of type statgrab_net.ctr.
No new checks of type lsi.array.
No new checks of type vms_df.
2 new checks written to /var/lib/check_mk/autochecks/df-2009-04-28_10.00.58.cfg
No new checks of type ipmi.
1 new checks written to /var/lib/check_mk/autochecks/mem.used-2009-04-28_10.00.58.cfg
1 new checks written to /var/lib/check_mk/autochecks/netif.params-2009-04-28_10.00.58.cfg
No new checks of type services.
No new checks of type tsm_stgpool.
No new checks of type winperf.diskstat.
No new checks of type vms_sys.util.
1 new checks written to /var/lib/check_mk/autochecks/netctr.combined-2009-04-28_10.00.58.cfg
No new checks of type md.
1 new checks written to /var/lib/check_mk/autochecks/kernel.util-2009-04-28_10.00.58.cfg
No new checks of type oracle_inst.
No new checks of type logwatch.
1 new checks written to /var/lib/check_mk/autochecks/netif.link-2009-04-28_10.00.58.cfg
No new checks of type oracle_asm_disk.
No new checks of type vms_netif.

L'installation est finie.

Installation de l'agent sous windows

Sous windows l'installation est vraiment triviale. A l'intérieur de l'archive “source” vous trouverez une archive agents.tar.gz. Il suffit d'extraire le contenu de l'archive et de transférer le fichier check_mk_agent.exe sur un serveur windows (par exemple dans le répertoire c:\check_mk.

L'invocation de check_mk en ligne de commande avec l'argument –help nous donne le résultat suivant :



L'installation en mode service se fait donc de la manière suivante :

Code:

check_mk_agent.exe install

Il ne reste plus qu'a démarrer le service grâce à la console de gestion des services windows (Menu démarrer → exécuter → services.msc).


Un petit test pour vérifier que tout se passe bien :

Code:

check_mk_agent.exe test

Utilisation

Code:

check_mk -nv localhost

Citation :

Getting info cpu from host localhost (127.0.0.1)
CPU load OK - 0.02
Number of threads OK - 76 threads
fs_/ OK - 4% used
fs_/boot OK - 15% used
Disk IO read OK - 0.0MB/s (in last 1240909505 secs)
Disk IO write OK - 0.0MB/s (in last 1240909505 secs)
CPU utilization OK - user: 0%, system: 0%, wait: 4%
Memory used OK - 31.3% of RAM (157 MB) used by processes
NIC eth0 counters OK - Receive: 0.00 MB/sec - Send: 0.00 MB/sec
NIC eth0 link OK - Link is up
NIC eth0 parameter OK - 1000Mb/s,Full,off
OK - Version 16, Successfully processed 11 host infos

Voici l'écran d'aide la commande check_mk

Citation :

Usage:

MAJOR MODES:

check_mk [-n] [-v] [-p] HOST [IPADDRESS] perform host checks
check_mk -S|-H output configuration files for Nagios
check_mk -C precompile host checks
check_mk -d HOSTNAME|IPADDRESS show plain information from agent
check_mk -I df [HOST1 HOST2...] Inventory of mounted partitions

OPTIONS:

-c FILE read config file FILE instead of /etc/check_mk/check_mk.cfg
-S output service configuration for Nagios
-H output host configuration for Nagios
-C, --compile precompile host checks (into /var/lib/check_mk/precompiled/)
-L list all available check types
-v, --verbose verbose output, for manual testing
--cache read info from cache file is present, use TCP only,
if no cache file present
--no-cache never use cached information (use *before* -I)
-p also show performance data (use with -v)
-n do not submit results to Nagios, do not save counters
-d just show ouput from agent, do not perform checks
-I type1,type2,.. make inventory of one or more checktypes.
Use '-L' or '-I list' for list of check types available
for inventory. Use '-I alltcp' for inventory on
all checks based on mknagios (and leave out SNMP)
--no-tcp for -I: only use cache files. Skipt hosts without
cache files.
--list-hosts [G1 G2 G3...] output all hostnames or only those
contained in one of a list of hostgroups

-h, --help print this help
-V, --version print version and exit

If called without options check_mk retrieves information about host
at IPADDRESS via TCP or SNMP and submits passive check results to
Nagios for all services configured in /etc/check_mk/check_mk.cfg for that host.

Intégration avec Nagios

Citation :

L'agent check_mk doit être installé sur chacune de vos machines.
Vous devrez créer l'utilisateur nagios pour pouvoir faire l'inventaire.

Code:

sudo adduser nagios

Citation :

Sur vos hôtes distants check_mk ne trouvera pas Nagios, répondez par défaut au question ce n'est pas grave, cette partie n'est utile que lors du poussage de la configuration.

Configuration

Sur le serveur Nagios configurer le fichier /etc/check_mk/main.mk

S'il n'y a que le serveur nagios, l'éditer comme ci-dessous :

Citation :

all_hosts = [ 'localhost' ]

Si d'autres hôtes viennent à être supervisés:

Citation :

all_hosts = [ 'localhost', 'hote-ubuntu' ]

Vous pouvez renseigner des noms mais il faut qu'il puisse répondre au ping avec ce nom sinon check_mk n'arrivera pas à faire la résolution de nom lors de l'inventaire.

Citation :

Petite astuce:
Si vous désirez des noms génériques, vous pouvez le faire en renseignant le fichier /etc/hosts de cette manière par exemple:

Extrait de /etc/hosts d'une ubuntu:

127.0.0.1 localhost

xx.xx.xx.xx dev-nagios.mon-domaine.net dev-nagios

# The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback

fe00::0 ip6-localnet

ff00::0 ip6-mcastprefix

ff02::1 ip6-allnodes

ff02::2 ip6-allrouters

ff02::3 ip6-allhosts

# Declaration de vos hotes supervises

yy.yy.yy.yy hote-ubuntu

Après ça le ping de hote-ubuntu répondra sous l'IP yy.yy.yy.yy

Inventaire

Nous allons réaliser un nouvel inventaire sur notre serveur nagios pour rapatrier les informations des hôtes supplémentaires.

check_mk -I alltcp

Citation :

cpu.loads 1 new checks

cpu.threads 1 new checks

df 6 new checks

diskstat nothing new

ipmi nothing new

kernel.util 1 new checks

local nothing new

logwatch nothing new

lsi.array nothing new

lsi.disk nothing new

md nothing new

mem.used 1 new checks

multipath nothing new

netctr.combined 1 new checks

netif.link nothing new

netif.params nothing new

nfsmounts nothing new

oracle_asm_dg nothing new

oracle_asm_disk nothing new

oracle_inst nothing new

oracle_tbs nothing new

services nothing new

statgrab_net.ctr nothing new

statgrab_net.link nothing new

statgrab_net.params nothing new

tsm_stgpool nothing new

vms_df nothing new

vms_md nothing new

vms_netif nothing new

vms_sys.mem nothing new

vms_sys.util nothing new

winperf.cpuusage nothing new

winperf.diskstat nothing new

Ensuite, vérifions si nous arrivons à récupérer les infos pour localhost et hote-ubuntu

Code:

check_mk -nv hote-ubuntu

Citation :

CPU load OK - 0.00

CPU utilization OK - user: 0%, system: 0%, wait: 1%

Memory used OK - 19.4% of RAM (23 MB) used by processes

NIC eth0 counters OK - Receive: 0.00 MB/sec - Send: 0.00 MB/sec

Number of threads OK - 31 threads

fs_/ OK - 34.2% used (0.2 of 0.5 GB), (levels at 80.0/90.0%)

fs_/boot OK - 25.6% used (0.1 of 0.2 GB), (levels at 80.0/90.0%)

fs_/opt OK - 12.5% used (0.0 of 0.2 GB), (levels at 80.0/90.0%)

fs_/tmp OK - 6.3% used (0.0 of 0.5 GB), (levels at 80.0/90.0%)

fs_/usr OK - 13.6% used (0.1 of 1.0 GB), (levels at 80.0/90.0%)

fs_/var OK - 23.0% used (0.2 of 1.0 GB), (levels at 80.0/90.0%)

OK - Agent Version 1.0.35, processed 11 host infos

Code:

check_mk -nv localhost

Citation :

CPU load OK - 0.00

CPU utilization OK - user: 3%, system: 1%, wait: 0%

Disk IO read OK - 0.0MB/s (in last 4 secs)

Disk IO write OK - 0.0MB/s (in last 4 secs)

Memory used OK - 14.0% of RAM (70 MB) used by processes

NIC eth0 counters OK - Receive: 0.00 MB/sec - Send: 0.00 MB/sec

Number of threads OK - 49 threads

fs_/ OK - 44.6% used (0.2 of 0.5 GB), (levels at 80.0/90.0%)

fs_/boot OK - 25.6% used (0.1 of 0.2 GB), (levels at 80.0/90.0%)

fs_/opt OK - 22.4% used (0.1 of 0.2 GB), (levels at 80.0/90.0%)

fs_/tmp OK - 6.3% used (0.0 of 0.5 GB), (levels at 80.0/90.0%)

fs_/usr OK - 33.7% used (0.3 of 1.0 GB), (levels at 80.0/90.0%)

fs_/var OK - 36.6% used (0.4 of 1.0 GB), (levels at 80.0/90.0%)

OK - Agent Version 1.0.35, processed 13 host infos

Intégration des check_mk's

Ensuite, ce qui nous intéresse est de pouvoir intégrer de manière simple ces résultats à Nagios.

check_mk -U

Citation :

Generating Nagios configuration for hosts...OK

Generating Nagios configuration for services...OK

Precompiling host checks...OK

Successfully created Nagios configuration file /opt/nagios/etc/objects/check_mk_objects.cfg.



Please make sure that file will be read by Nagios.

You need to restart Nagios in order to activate the changes.

L'option -U génére les déclarations d'hôtes et de services, vérifie la cohérence des infos et les poussent vers le répertoire /opt/nagios/etc/objects de votre serveur nagios.

Avant de redémarrer Nagios,

1) Nous avons réaliser ce test via un serveur nagios vierge
2) Penser à retirer les doublons car check_mk génère des timeperiods, contacts …

Deux options s'offrent à vous :

Soit vous retirez les fichiers de base de votre conf nagios pour laisser place à ceux de check_mk comme ceci :

Code:

vi /etc/nagios/nagios.cfg

Citation :

#cfg_file=/opt/nagios/etc/objects/commands.cfg

#cfg_file=/opt/nagios/etc/objects/contacts.cfg

#cfg_file=/opt/nagios/etc/objects/timeperiods.cfg

#cfg_file=/opt/nagios/etc/objects/templates.cfg

#cfg_file=/opt/nagios/etc/objects/localhost.cfg



# Definitions for monitoring a Windows machine

#cfg_file=/opt/nagios/etc/objects/windows.cfg



# Definitions for monitoring a router/switch

#cfg_file=/opt/nagios/etc/objects/switch.cfg

# Definitions for monitoring a network printer

#cfg_file=/opt/nagios/etc/objects/printer.cfg

#cfg_dir=/opt/nagios/etc/objects

After the scan, you can automatically add the newly discovered services to Nagios by running the following command:

Code:

check_mk -R

Citation :

Generating Nagios configuration...OK
Validating Nagios configuration...OK
Precompiling host checks...OK
Restarting Nagios...OK

Vous pouvez bien sûr tester votre configuration avec

Code:

/usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg

Pour finir redémarrer Nagios pour obtenir le résultat comme ci-dessous.


Récap:
A chaque fois que vous aurez un hôte à ajouter,

Installer l'agent check_mk sur votre hôte à superviser
Sur le serveur nagios:

Ajoutez le dans le main.mk
Refaire un inventaire sudo check_mk -I alltcp
Tester si vous arrivez à récupérer vos résultats
Repousser la conf avec l'option -U
Redémarrer Nagios

Y a vraiment beaucoup plus de lecture que de chose à faire, mais c'est bien, un tuto détaillé parfois.

La suite, pnp4nagios

D'abord

Code:

yum install rrdtool

puis

choper le fichier ici
http://sourceforge.net/projects/pnp4nagios/

Code:

wget  http://downloads.sourceforge.net/project/pnp4nagios/PNP-0.6/pnp4nagios-0.6.6.tar.gz?r=http%3A%2F%2Fsourceforge.net%2Fprojects%2Fpnp4nagios%2F

puis

Code:

tar xzf pnp4nagios-0.6.6.tar.gz

Code:

cd pnp4nagios-0.6.6

Code:

./configure
make all
sudo make fullinstall

fullinstall combines install, install-webconf, install-init, and install-config.

There are various modes of operation and quite complicated installation instructions posted on its official website, but a single command can set it up: (a voir)

This uses the npcdmod.o module which makes additional, manual nagios.cfg changes unnecessary! Why isn't this properly documented in its official manual?

A special service to process performance data is required for this mode, so copy its configuration to the proper place:

Code:

cp -p /usr/local/pnp4nagios/etc/npcd.cfg-sample /usr/local/pnp4nagios/etc/npcd.cfg

Start it up

Code:

/etc/init.d/npcd start

Code:

service httpd restart

http://adresseipduserveur/pnp4nagios/

Code:

rm -f /usr/local/pnp4nagios/share/install.php

Pour l'instant vous obtenez une erreur, c'est normal, ya pas de perfdata, ça va venir !

mais d'abord, on va installer graphviz !!

Code:

wget http://www.graphviz.org/graphviz-rhel.repo

Code:

mv graphviz-rhel.repo /etc/yum.repos.d/

Code:

yum list available 'graphviz*'

Code:

yum install graphviz.x86_64

puis installation de Nagvis

Code:

wget https://sourceforge.net/projects/nagvis/files/NagVis%201.5/nagvis-1.5.1.tar.gz/download

Code:

tar xzf nagvis-1.5.1.tar.gz

Code:

cd nagvis-1.5.1

Code:

./install.sh -i mklivestatus -q

ensuite

Code:

service httpd restart

la vous devriez pouvoir visiter la page
http://adresseipduserveur/nagvis/

et tomber sur


Pour corriger ce problème qui est apparemment du au passage au php-5.2

il faut ouvrir le fichier php.ini

Code:

nano /etc/php.ini

et modifiier la ligne

Citation :

;date.timezone =

comme ceci (ou ajouter celle ci juste après)

Citation :

date.timezone = Europe/Paris

Code:

service httpd restart

et voila, nagvis (bon, curieusement chez moi ça marche pas, ca marchait avant que je delete tout ^^)
a suivre donc !

A oui, mais on a pas fini. il faut regler pvp4nagios pour les perfdatas

Plusieurs méthodes
http://docs.pnp4nagios.org/pnp-0.6/config

j'utilises le Synchronous Mode

The synchronous mode is the simplest way to integrate the data collector process_perfdata.pl into nagios. Every event will trigger an execution of process-service-perfdata.

Initially you have to enable processing of performance data in nagios.cfg. Please note that this directive might already exist in the config file. Default is “0”.

ligne 833 chez moi, ctrl +C vous donne la ligne

Citation :

process_performance_data=1

Data processing has to be disabled in the definition of every host or service whose performance data should NOT be processed.

Citation :

define service {
...
process_perf_data 0
...
}

Since Nagios 3.x it is possible to deactivate the export of environment variables (as part of optimizing the system for maximum performance). Unfortunately this directive has to be enabled to use the synchronous mode. So either you use the default value (which means that the export is enabled) or you define the variable in nagios.cfg

Citation :

enable_environment_macros=1

Additionally the command to process performance data is to be specified in nagios.cfg

Citation :

service_perfdata_command=process-service-perfdata

Starting with Nagios 3.0 it may be useful to enable processing of performance data for hosts as well. Due to changed host check logic Nagios 3 now performs regularly scheduled host checks.

Citation :

host_perfdata_command=process-host-perfdata

Nagios has to be notified about the referenced commands as well. If you used the quickstart installation guides for Nagios you can modify the definitions in commands.cfg. You can see that calling process_perfdata.pl doesn't require any arguments apart from specifing the option -d ( DATATYPE ) if you want to process performance data resulting from host checks.

Code:

define command {
      command_name    process-service-perfdata
      command_line    /usr/bin/perl /usr/local/pnp4nagios/libexec/process_perfdata.pl
}

define command {
      command_name    process-host-perfdata
      command_line    /usr/bin/perl /usr/local/pnp4nagios/libexec/process_perfdata.pl -d HOSTPERFDATA
}

Note process_perfdata.pl cannot be started under control of ePN ( embedded Perl Nagios ). Therefore the script is explicitly called using /usr/bin/perl ( or where you perl binary is located ). If you use Nagios 3.x or do not use ePN there is no need to specify /usr/bin/perl

Ça devrait être fini, pensez à faire des restart httpd nagios ou autres si ça va pas, et sinon STFW !