Nagios: Difference between revisions

From DWIKI
No edit summary
mNo edit summary
 
(32 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[http://www.nagios.org/ Homepage]
= Links =
* [http://www.nagios.org/ Homepage]
* http://www.nagiosexchange.org/ Nagios Exchange]
*[http://www.gentoo-wiki.info/HOWTO_Install_Nagios
* [http://www.totkat.org/pages/nconf_commands.shtml Configure nagios commands]
*ndoutils stores data in sql
*[http://sourceforge.net/projects/nagios-db/ Nagios-db  stores data in sql]
 
*[[nagiosgrapher]] (rather unfinished/poorly documented)
*[http://www.pnp4nagios.org/pnp/start pnp4nagios] ( for graphs )


there seem to be issues with check_procs on solaris, pst3 and config.h - #define PS_COMMAND are the keywords here
there seem to be issues with check_procs on solaris, pst3 and config.h - #define PS_COMMAND are the keywords here
=Plugins=
*[http://www.nagiosexchange.org/cgi-bin/page.cgi?g=1692.html;d=1 check software raid]
*[http://exchange.nagios.org/directory/Uncategorized/IPMI-Sensor-Monitoring-Plugin/details IPMI Sensor Monitoring Plugin]
= FAQ =
==Hosts or services simply not showing up==
Check if you have more than one instances of nagios running
==Debian complaining about rights on nagios.cmd==
dpkg-statoverride --update --add nagios www-data 2710 /var/lib/nagios2/rw
dpkg-statoverride --update --add nagios nagios 751 /var/lib/nagios2
==NRPE: Unable to read output==
*This could mean the plugins are not installed ( yes, on debian nrpe comes without those :)
==CHECK_NRPE: Error receiving data from daemon. ==
Possibly SSL version mismatch, try check_nrpe -n
==(No output returned from plugin) ==
Most likely ssl mismatch again. It can also mean you're using debian, where check_nrpe!check_something fails, since it expects one more argument. call 'check_nrpe_1arg' instead.
==Error: Could not stat() command file '/var/lib/nagios3/rw/nagios.cmd'!==
That's apache missing read rights to the path.
== Could not read request from client, bailing out==
Another rather useless message, it might mean one end is using ssl and other end not.
Check on your system that the nrpe2 agent is compiled with ssl support.
Example:
[my_monitored_host] # ldd /usr/local/sbin/nrpe2
/usr/local/sbin/nrpe2:
        libssl.so.5 => /usr/lib/libssl.so.5 (0x80063a000)
        libcrypto.so.5 => /lib/libcrypto.so.5 (0x800784000)
        libwrap.so.5 => /usr/lib/libwrap.so.5 (0x800a16000)
        libc.so.7 => /lib/libc.so.7 (0x800b1f000)
It is OK, while:
[my_monitored_host] # ldd /usr/local/sbin/nrpe2
/usr/local/sbin/nrpe2:
        libcrypto.so.5 => /lib/libcrypto.so.5 (0x800784000)
        libc.so.7 => /lib/libc.so.7 (0x800b1f000)
is NOT ok.
[[:Category:Monitoring]]

Latest revision as of 17:30, 12 May 2016

Links

there seem to be issues with check_procs on solaris, pst3 and config.h - #define PS_COMMAND are the keywords here

Plugins

FAQ

Hosts or services simply not showing up

Check if you have more than one instances of nagios running

Debian complaining about rights on nagios.cmd

dpkg-statoverride --update --add nagios www-data 2710 /var/lib/nagios2/rw
dpkg-statoverride --update --add nagios nagios 751 /var/lib/nagios2


NRPE: Unable to read output

  • This could mean the plugins are not installed ( yes, on debian nrpe comes without those :)

CHECK_NRPE: Error receiving data from daemon.

Possibly SSL version mismatch, try check_nrpe -n

(No output returned from plugin)

Most likely ssl mismatch again. It can also mean you're using debian, where check_nrpe!check_something fails, since it expects one more argument. call 'check_nrpe_1arg' instead.

Error: Could not stat() command file '/var/lib/nagios3/rw/nagios.cmd'!

That's apache missing read rights to the path.


Could not read request from client, bailing out

Another rather useless message, it might mean one end is using ssl and other end not. Check on your system that the nrpe2 agent is compiled with ssl support.

Example:

[my_monitored_host] # ldd /usr/local/sbin/nrpe2

/usr/local/sbin/nrpe2:

       libssl.so.5 => /usr/lib/libssl.so.5 (0x80063a000)
       libcrypto.so.5 => /lib/libcrypto.so.5 (0x800784000)
       libwrap.so.5 => /usr/lib/libwrap.so.5 (0x800a16000)
       libc.so.7 => /lib/libc.so.7 (0x800b1f000)

It is OK, while:

[my_monitored_host] # ldd /usr/local/sbin/nrpe2

/usr/local/sbin/nrpe2:

       libcrypto.so.5 => /lib/libcrypto.so.5 (0x800784000)
       libc.so.7 => /lib/libc.so.7 (0x800b1f000)

is NOT ok.


Category:Monitoring