Script monitorizare nagios

server de nsca ai instalat pe masina nagios? pe Debian pachetele sunt nsca si nsca-client.

incearca un telnet la masina nagios :5667. de asemenea, verifica si iptables sau firewall-ul daca nu cumva are blocat accesul spre acel port.

Pe serverul care genereaza logurile si pe care se executa si scriptul am instalat nsca-client. Ruleaza o distributie bazata pe Debian.
Pe serverul pe care ruleaza serverul nagios am instalat nagios-nsca.x86_64 : Nagios Service Check Acceptor (care a instalat oricum si clientul). Este o distributie bazata pe RedHat.
Serverele sunt in aceeasi retea.

root@minipc:~# telnet 10.5.5.8 5667
Trying 10.5.5.8...
Connected to 10.5.5.8.
Escape character is '^]'.

arata bine partea de retelistica.

poti sa afisezi te rog configuratia check-ului din nagios (define service...)

Iti dau paste la fisierele .cfg, asa cum le am eu:
baterie.cfg

define service{
	 use					 generic-service		 ; Inherit values from a template
	 host_name			 baterie	 ; The name of the host the service is associated with
	 service_description	 PING		 ; The service description
	 check_command		 check_ping!800.0,80%!1000.0,100%
	 normal_check_interval 5			 ; Check the service every 5 minutes under normal conditions
	 retry_check_interval 1			 ; Re-check the service every minute until its final/hard state is determined
	 notifications_enabled 1
	 }
define service{
	 use							 local-service		 ; Name of service template to use
	 host_name					 baterie
	 service_description			 Current Load
	 check_command				 check_local_load!5.0,4.0,3.0!10.0,6.0,4.0
	 }
define service{
	 use					 generic-service
	 host_name			 baterie
	 service_description	 Last file check
	 check_command		 check_nrpe_newest_file_age!10.5.5.33!check_newest_file_age
	 normal_check_interval 5
	 retry_check_interval 1
	 notifications_enabled 1
	 }
define service {
		 name										 passive-service				 ; The 'name' of this service template
		 use													 generic-service
		 active_checks_enabled		 0		 ; Active service checks are enabled
		 passive_checks_enabled		 1	 ; Passive service checks are enabled/accepted
		 check_freshness								 1
		 freshness_threshold					 120 ; The freshness threshold (in seconds) for this service. If you set this directive to a value of 0, Nagios will determine a freshness threshold to use automatically.
		 contact_groups								 admins
		 check_command						 check_dummy!0
		 register									 0				 ; DONT REGISTER THIS DEFINITION - ITS NOT A REAL SERVICE, JUST A TEMPLATE!
		 }
define service {
		 use				 passive-service
		 host_name			 baterie
		 service_description Status baterie
		 }

commands.cfg

define command{
		 command_name check_dummy
		 command_line $USER1$/check_dummy $ARG1$
		 }

/etc/nagios/nsca.cfg de pe serverul nagios nu este modificat in nici un fel.
/etc/send_nsca.cfg de pe serverul cu bateriile nu este modificat in nici un fel.

Mostra din csv:

time soc voltage current Vmin VminIndex Vmax VmaxIndex Tmin TminIndex Tmax TmaxIndex error high low mains
12:59:27 100 157.59 5 3.27 13 3.29 39 19 33 31 26 0 0 0 1
12:59:37 100 157.58 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
12:59:47 100 157.58 5 3.27 13 3.29 39 19 33 31 28 0 0 0 1
12:59:57 100 157.59 5 3.27 13 3.29 39 19 33 31 26 0 0 0 1
13:00:07 100 157.59 5 3.27 13 3.29 39 19 33 31 28 0 0 0 1
13:00:17 100 157.57 5 3.27 13 3.29 39 19 33 31 26 0 0 0 1
13:00:27 100 157.59 5 3.27 13 3.29 39 19 33 32 2 0 0 0 1
13:00:37 100 157.59 5 3.27 13 3.29 48 19 33 31 26 0 0 0 1
13:00:47 100 157.58 5 3.27 13 3.29 39 19 33 31 28 0 0 0 1
13:00:57 100 157.57 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:01:07 100 157.60 5 3.27 13 3.29 48 19 33 32 2 0 0 0 1
13:01:17 100 157.58 0 3.27 13 3.29 39 19 33 31 28 0 0 0 1
13:01:27 100 157.56 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:01:37 100 157.59 5 3.27 13 3.29 39 19 33 31 28 0 0 0 1
13:01:47 100 157.59 5 3.27 13 3.29 48 19 33 31 26 0 0 0 1
13:01:57 100 157.59 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:02:07 100 157.59 5 3.27 13 3.29 39 19 33 32 26 0 0 0 1
13:02:17 100 157.58 0 3.27 13 3.29 39 19 33 31 28 0 0 0 1
13:02:27 100 157.58 5 3.27 13 3.29 48 19 33 32 2 0 0 0 1
13:02:37 100 157.58 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:02:47 100 157.59 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:02:57 100 157.58 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:03:07 100 157.59 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:03:17 100 157.59 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:03:27 100 157.60 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:03:37 100 157.59 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:03:47 100 157.59 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:03:57 100 157.58 5 3.27 18 3.29 39 19 33 31 28 0 0 0 1
13:04:07 100 157.59 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:04:17 100 157.58 5 3.27 13 3.29 39 19 33 31 28 0 0 0 1
13:04:27 100 157.59 5 3.27 13 3.29 39 19 33 31 28 0 0 0 1
13:04:37 100 157.56 5 3.27 13 3.29 39 19 33 31 28 0 0 0 1
13:04:47 100 157.58 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:04:58 100 157.58 5 3.27 13 3.29 48 19 33 32 2 0 0 0 1
13:05:08 100 157.59 0 3.27 18 3.29 48 19 33 32 26 0 0 0 1
13:05:18 100 157.59 5 3.27 13 3.29 39 19 33 31 28 0 0 0 1
13:05:28 100 157.58 5 3.27 13 3.29 39 19 33 31 28 0 0 0 1
13:05:38 100 157.59 5 3.27 13 3.29 48 19 33 32 2 0 0 0 1
13:05:48 100 157.58 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:05:58 100 157.59 5 3.27 13 3.29 48 19 33 31 28 0 0 0 1
13:06:08 100 157.57 5 3.27 13 3.29 48 19 33 32 2 0 0 0 1
13:06:18 100 157.58 0 3.27 13 3.29 48 20 33 32 2 0 0 0 1
13:06:28 100 157.57 5 3.27 13 3.29 48 19 33 32 2 0 0 0 1
13:06:38 100 157.58 5 3.27 13 3.30 30 19 33 32 2 0 0 0 1
13:06:48 100 157.60 5 3.27 13 3.29 39 19 33 31 28 0 0 0 1

Edited by caracal, 07 August 2015 - 11:32.

ciudat, ca pare ok configuratia...

structura comenzii care trimite statusul la serverul nagios este urmatoarea (eu unul folosesc ; ca despartitor):

echo "<nume masina asa cum este configurata in nagios>;<nume check>;<status>;<mesaj de afisat in nagios>" | /usr/sbin/send_nsca -H <masina nagios> -d ';' -c /etc/send_nsca.cfg

in principiu nu-s prea multe de modificat in send_nsca.conf. trebuie avut grija ca modul de criptare sa fie acelasi in ambele parti.

cand se scrie un script pt passive check, ideea e ca in urma prelucrarii datelor sa ajungi la un <status>. status poate fi 0 (ok), 1 (warn), 2 (critical), 3 (unknown). mesajul de afisat il generezi in functie de necesitati. apoi se creeaza comanda cu structura complicata de mai sus si cam asta a fost tot

mai incearca manual inainte sa actualizezi statusul. mai verifica si generic service, poate a ramas ceva ciudat configurat acolo.

exemplele de configuratie date de mine sunt luate direct din prod si functioneaza.

Edited by mannes, 07 August 2015 - 15:41.

Nu reusesc! Ori sunt eu foarte incapabil, ori ceva nu merge asa cum ar trebui! Urmatoarea varianta e sa fac un NFS cu /data pe un alt server si sa incerc sa setez de acolo monitorizarea Ma gandesc sa nu fie vreo problema cu nagios (desi mai am monitorizarea cu ping-ul care merge, monitorizarea pentru file change...), dat fiind ca este un "minipc" care ruleaza o versiune Debian pe arhitectura arm v7. Revin cu detalii.
Iti multumesc mult inca o data!!

Dupa ceva timp...este gata Problema era versiunea diferita de nsca de pe server fata de cea de pe client. Si am modificat si scriptul putin pentru ca nu trimitea datele in formatul corespunzator. Acum este OK. Multumesc inca o data!