Nagios XI NRPE issue

[jwu]

Nagios XI server:
CentOS 6.4
64 bit
install VMWare image


Monitoring environment
Centos 6.4
64 bit
installed agent via instructions using /fullinstall
no special configurations

I'm having issues of monitoring the Linux server,
I have attached the one with SSL and one w/o SSL

in my client server, i'm getting messages in /var/log/messages
---
Jul 24 15:39:12 cvg-nagois-test xinetd[24807]: FAIL: nrpe address from=::ffff:10.1.100.21
Jul 24 15:39:12 cvg-nagois-test xinetd[9511]: EXIT: nrpe status=0 pid=24807 duration=0(sec)
Jul 24 15:39:19 cvg-nagois-test xinetd[9511]: START: nrpe pid=24808 from=::ffff:10.1.100.21
Jul 24 15:39:19 cvg-nagois-test xinetd[24808]: FAIL: nrpe address from=::ffff:10.1.100.21
Jul 24 15:39:19 cvg-nagois-test xinetd[9511]: EXIT: nrpe status=0 pid=24808 duration=0(sec)
---

my configuration file is already configured with allowed_hosts including the nagiosXi IP

one item to note is I can't locate the nrpe binary, not sure if that is a factor about this issue.

thanks

[lmiltchev]

Run the following commands on the client machine and show the output:

Code: Select all

netstat -at | grep nrpe
grep dont_blame_nrpe /usr/local/nagios/etc/nrpe.cfg
grep only_from /etc/xinetd.d/nrpe
service xinetd status

[slansing]

For the system showing the incomplete SSL handshake error, were you sure to compile NRPE with SSL support? Both of these issues are discussed in this document:

http://assets.nagios.com/downloads/nagi ... utions.pdf

[jwu]

Run the following commands on the client machine and show the output:

Code: Select all

netstat -at | grep nrpe
grep dont_blame_nrpe /usr/local/nagios/etc/nrpe.cfg
grep only_from /etc/xinetd.d/nrpe
service xinetd status

output below

tcp 0 0 *:nrpe *:* LISTEN

dont_blame_nrpe=1
# command arguments *AND* the dont_blame_nrpe directive in this

only_from = 10.2.0.162 127.0.0.1

xinetd (pid 9511) is running...

[jwu]

some more info, I checked the port and it's open
from Nagios XI Server to Remote Server
---
[root@cvglobal ~]# nmap 10.1.100.20 -p 5666

Starting Nmap 5.51 ( http://nmap.org ) at 2013-07-24 17:29 EDT
Nmap scan report for cvg-nagois-test.cvglobal.com (10.1.100.20)
Host is up (0.00027s latency).
PORT STATE SERVICE
5666/tcp open nrpe
MAC Address: 00:50:56:8A:63:45 (VMware)

Nmap done: 1 IP address (1 host up) scanned in 0.13 seconds
---
[root@cvglobal ~]# /usr/local/nagios/libexec/check_nrpe -H 10.1.100.20
CHECK_NRPE: Error - Could not complete SSL handshake.

is there the need to manually include enable-ssl in the install, the whole install process is scripted up,
I did try to check localhost
---
[root@cvglobal ~]# /usr/local/nagios/libexec/check_nrpe -H localhost
NRPE v2.12
---
not sure if this will make a difference or not

[lmiltchev]

Open the /etc/xinet.d/nrpe on the client in a text editor:

Code: Select all

vi /etc/xinet.d/nrpe

and add your Nagios XI server's IP:

only_from = 10.2.0.162 127.0.0.1 10.1.100.21

Restart the daemon:

Code: Select all

service xinetd restart

See if this is going to solve your issue.

[jwu]

the error message changed, I put a screenshot of the nagiosXI interface

here's the message I'm receiving on the client system logs
---
Jul 24 16:46:26 cvg-nagois-test xinetd[27241]: EXIT: nrpe status=0 pid=27569 duration=0(sec)
Jul 24 16:46:31 cvg-nagois-test xinetd[27241]: START: nrpe pid=27581 from=::ffff:10.1.100.21
Jul 24 16:46:31 cvg-nagois-test xinetd[27241]: START: nrpe pid=27582 from=::ffff:10.1.100.21
Jul 24 16:46:31 cvg-nagois-test xinetd[27241]: EXIT: nrpe status=0 pid=27582 duration=0(sec)
Jul 24 16:46:31 cvg-nagois-test xinetd[27241]: EXIT: nrpe status=0 pid=27581 duration=0(sec)
Jul 24 16:46:36 cvg-nagois-test xinetd[27241]: START: nrpe pid=27605 from=::ffff:10.1.100.21
Jul 24 16:46:36 cvg-nagois-test xinetd[27241]: EXIT: nrpe status=0 pid=27605 duration=0(sec)
Jul 24 16:46:37 cvg-nagois-test xinetd[27241]: START: nrpe pid=27637 from=::ffff:10.1.100.21
Jul 24 16:46:37 cvg-nagois-test nrpe[27637]: Error: Could not complete SSL handshake. 1
Jul 24 16:46:37 cvg-nagois-test xinetd[27241]: EXIT: nrpe status=0 pid=27637 duration=0(sec)
Jul 24 16:46:38 cvg-nagois-test xinetd[27241]: START: nrpe pid=27638 from=::ffff:10.1.100.21
Jul 24 16:46:38 cvg-nagois-test xinetd[27241]: EXIT: nrpe status=0 pid=27638 duration=0(sec)
Jul 24 16:46:45 cvg-nagois-test xinetd[27241]: START: nrpe pid=27641 from=::ffff:10.1.100.21
Jul 24 16:46:45 cvg-nagois-test xinetd[27241]: EXIT: nrpe status=0 pid=27641 duration=0(sec)
Jul 24 16:46:52 cvg-nagois-test xinetd[27241]: START: nrpe pid=27644 from=::ffff:10.1.100.21
Jul 24 16:46:57 cvg-nagois-test xinetd[27241]: EXIT: nrpe status=0 pid=27644 duration=5(sec)
Jul 24 16:46:58 cvg-nagois-test xinetd[27241]: START: nrpe pid=27666 from=::ffff:10.1.100.21
Jul 24 16:46:58 cvg-nagois-test xinetd[27241]: START: nrpe pid=27667 from=::ffff:10.1.100.21
Jul 24 16:46:58 cvg-nagois-test xinetd[27241]: EXIT: nrpe status=0 pid=27666 duration=0(sec)
Jul 24 16:46:58 cvg-nagois-test xinetd[27241]: EXIT: nrpe status=0 pid=27667 duration=0(sec)
Jul 24 16:47:12 cvg-nagois-test xinetd[27241]: START: nrpe pid=27680 from=::ffff:10.1.100.21
Jul 24 16:47:12 cvg-nagois-test xinetd[27241]: EXIT: nrpe status=0 pid=27680 duration=0(sec)
---

[lmiltchev]

Can you run one of the failing check from the command line and show the output? For example, it could be something like this:

Code: Select all

cd /usr/local/nagios/libexec
./check_nrpe -H <client_IP> -t 30 -c check_disk -a '-w 20% -c 10% -p /'

[jwu]

Can you run one of the failing check from the command line and show the output? For example, it could be something like this:

Code: Select all

cd /usr/local/nagios/libexec
./check_nrpe -H <client_IP> -t 30 -c check_disk -a '-w 20% -c 10% -p /'

[root@cvglobal ~]# /usr/local/nagios/libexec/check_nrpe -H 10.1.100.20 -t 30 -c check_disk -a '-w 20% -c 10% -p /'
DISK OK - free space: / 424322 MB (98% inode=99%);| /=6200MB;362845;408201;0;453557

I also tried

[root@cvglobal ~]# /usr/local/nagios/libexec/check_nrpe -H 10.1.100.20
NRPE v2.14

[jwu]

I have updates, this morning I went on and deleted my host and reconfigured it, it seems to be working now...

this was happening to me for Windows machine, will try to configure it again