Nagios Support Forum

Okay, so the binary file has been moved to /usr/local/nagios/bin/nrpe.

After you run a check that fails to complete, is there anything notable in messages?
Does the binary exist in the new location? Let's do a library check against the nrpe binary (provided that it does exist):

1. # tail -n20 /var/log/messages
Jan 12 13:20:21 calendar-310-uaex-edu xinetd[44031]: START: nrpe pid=49889 from=::ffff:10.200.160.93
Jan 12 13:20:21 calendar-310-uaex-edu xinetd[44031]: EXIT: nrpe status=0 pid=49889 duration=0(sec)
Jan 12 13:20:33 calendar-310-uaex-edu xinetd[44031]: START: nrpe pid=49900 from=::ffff:10.200.160.93
Jan 12 13:20:33 calendar-310-uaex-edu xinetd[44031]: EXIT: nrpe status=0 pid=49900 duration=0(sec)
Jan 12 13:20:35 calendar-310-uaex-edu xinetd[44031]: START: nrpe pid=49916 from=::ffff:10.200.160.93
Jan 12 13:20:35 calendar-310-uaex-edu xinetd[44031]: EXIT: nrpe status=0 pid=49916 duration=0(sec)
Jan 12 13:20:39 calendar-310-uaex-edu xinetd[44031]: START: nrpe pid=49921 from=::ffff:10.200.160.93
Jan 12 13:20:44 calendar-310-uaex-edu xinetd[44031]: EXIT: nrpe status=0 pid=49921 duration=5(sec)
Jan 12 13:21:59 calendar-310-uaex-edu xinetd[44031]: START: nrpe pid=49974 from=::ffff:10.200.160.93
Jan 12 13:21:59 calendar-310-uaex-edu xinetd[44031]: EXIT: nrpe status=0 pid=49974 duration=0(sec)
Jan 12 13:22:29 calendar-310-uaex-edu xinetd[44031]: START: nrpe pid=50018 from=::ffff:10.200.160.93
Jan 12 13:22:29 calendar-310-uaex-edu xinetd[44031]: EXIT: nrpe status=0 pid=50018 duration=0(sec)
Jan 12 13:22:32 calendar-310-uaex-edu xinetd[44031]: START: nrpe pid=50034 from=::ffff:10.200.160.93
Jan 12 13:22:32 calendar-310-uaex-edu xinetd[44031]: EXIT: nrpe status=0 pid=50034 duration=0(sec)
Jan 12 13:22:45 calendar-310-uaex-edu xinetd[44031]: START: nrpe pid=50047 from=::ffff:10.200.160.93
Jan 12 13:22:45 calendar-310-uaex-edu xinetd[44031]: EXIT: nrpe status=0 pid=50047 duration=0(sec)
Jan 12 13:22:56 calendar-310-uaex-edu xinetd[44031]: START: nrpe pid=50051 from=::ffff:10.200.160.93
Jan 12 13:22:56 calendar-310-uaex-edu xinetd[44031]: EXIT: nrpe status=0 pid=50051 duration=0(sec)
Jan 12 13:23:25 calendar-310-uaex-edu xinetd[44031]: START: nrpe pid=50075 from=::ffff:10.200.160.93
Jan 12 13:23:25 calendar-310-uaex-edu xinetd[44031]: EXIT: nrpe status=0 pid=50075 duration=0(sec)

2. # ls -l /usr/local/nagios/bin/nrpe
-rwxrwxr-x. 1 nagios nagios 163132 Jan 12 11:34 /usr/local/nagios/bin/nrpe

3. # ldd /usr/local/nagios/bin/nrpe
linux-vdso.so.1 => (0x00007fff9ed8b000)
libssl.so.10 => /lib64/libssl.so.10 (0x00007fef8dd3b000)
libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007fef8d954000)
libnsl.so.1 => /lib64/libnsl.so.1 (0x00007fef8d73a000)
libc.so.6 => /lib64/libc.so.6 (0x00007fef8d37b000)
libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007fef8d12f000)
libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007fef8ce49000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007fef8cc45000)
libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007fef8ca13000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fef8c80e000)
libz.so.1 => /lib64/libz.so.1 (0x00007fef8c5f8000)
/lib64/ld-linux-x86-64.so.2 (0x00007fef8dfc2000)
libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007fef8c3e9000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007fef8c1e4000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fef8bfca000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fef8bdae000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fef8bb89000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007fef8b928000)
liblzma.so.5 => /lib64/liblzma.so.5 (0x00007fef8b703000)

Good, the file exists, permissions are proper, and all libraries are hooked up appropriately. Is this check still failing from the Nagios side of things as well?

It seems working now. This is great! Thank you so much!

BTW, I saw the status of Total processes is Critical. The message from Nagios Admin page is as follows:

Total Processes Critical 19d 19h 49m 31s 5/5 2016-01-13 08:51:16 PROCS CRITICAL: 271 processes

Is this something we need to fix?

Thanks again!

It depends on whether or not this is a normal number. We can adjust those values in the core configuration manager to be a better fit for your server than the generic number that we supply.

I re-configure this service, and changed "Monitor the servcie with this command" to check_nrpe!check_procs!-a '-w 150 -c 300'. Now its status is Warning. I guess it should be OK now.

Now, can we work on my second issue? How to migrate the clients from Nagios Core to XI? Thank you!

Since this thread is super bloated at this point, can I ask that you open another one for that issue? I want to make sure this one is as easy to follow for fellow forum users.

Thank you.

Definitely. I will open a new case for that.

I really appreciate your help on this case!

No problem, glad we got it working for you! This thread will be a great point of reference for future Oracle Linux NRPE issues.

I look forward to seeing your other thread, thanks!