Nagios NRPE add-on troubleshooting

1) ./configure fails with error “checking for SSL… configure: error: Cannot find ssl libraries”

This is mainly because configure script couldn’t find SSL library. Install OPENSSL library from here and install.

2) Error “” while compiling the NRPE.

This happens because gcc doesn’t link in the dynamic link loader in the program itself. You will need to supply the compiler and linker version (gcc –version and ld –version should work with GNU tools)
You have installed the statically linked version of openssl but still managed to get it linked to the dynamic link loader, which may or may not be present as a static library on your system. You may have to supply the libld as an extra argument to your LDFLAGS.

Use ./configure LDFLAGS=-ldl

3) after successful installation, error “CHECK_NRPE: Error – Could not complete SSL handshake.” comes while testing

1.Different versions. Make sure you are using the same version of the check_nrpe plugin and the NRPE daemon.
Newer versions of NRPE are usually not backward compatible with older versions.
2.SSL is disabled. Make sure both the NRPE daemon and the check_nrpe plugin were compiled with SSL support
and that neither are being run without SSL support (using command line switches).
3.Incorrect file permissions. Make sure the NRPE config file (nrpe.cfg) is readable by the user (i.e. nagios)
that executes the NRPE binary from inetd/xinetd.
4. Pseudo-random device files are not readable.Solaris 8 The files /devices/pseudo/random*
(linked through /dev/*random, and provided by Sun patch 112438) were not readable by the nagios
user I use to launch NRPE. Making the character devices world-readable solved it.”
5. Unallowed address. If you’re running the NRPE daemon under xinetd, make sure that you have a line in
the xinetd config file that say “only_from = xxx.xxx.xxx.xxx”, where xxx.xxx.xxx.xxx is the IP
address that you’re connected to the NRPE daemon from.

Be Sociable, Share!

•