NRPE: Unable to read output

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
User avatar
tgriep
Madmin
Posts: 9177
Joined: Thu Oct 30, 2014 9:02 am

Re: NRPE: Unable to read output

Post by tgriep »

Is there a firewall on the server at IP address 168.162.97.143 blocking the Nagios server?

Can you login to the Nagios server as root, run the following and post the output?

Code: Select all

nmap 168.162.97.143 -p 7780
Be sure to check out our Knowledgebase for helpful articles and solutions!
Katya.Ailarov
Posts: 25
Joined: Wed Aug 17, 2016 5:29 am

Re: NRPE: Unable to read output

Post by Katya.Ailarov »

sorry i dont have this command intsall on my server.

please suggest other comand

Thank you vey much!
tmcdonald
Posts: 9117
Joined: Mon Sep 23, 2013 8:40 am

Re: NRPE: Unable to read output

Post by tmcdonald »

Are you able to install nmap on the Nagios server? It is very useful for troubleshooting.
Former Nagios employee
Katya.Ailarov
Posts: 25
Joined: Wed Aug 17, 2016 5:29 am

Re: NRPE: Unable to read output

Post by Katya.Ailarov »

i dont think it is the FW.

because i can telnet

-bash-4.1# telnet 168.162.97.143 5666
Trying 168.162.97.143...
Connected to 168.162.97.143.
Escape character is '^]'.
User avatar
mcapra
Posts: 3739
Joined: Thu May 05, 2016 3:54 pm

Re: NRPE: Unable to read output

Post by mcapra »

We would really need to see the nmap output. It could be that telnet requests are not filtered but others are (this is quite common). This would be presented in an nmap output.
Former Nagios employee
https://www.mcapra.com/
Katya.Ailarov
Posts: 25
Joined: Wed Aug 17, 2016 5:29 am

Re: NRPE: Unable to read output

Post by Katya.Ailarov »

-bash-4.1# nmap 168.162.97.143 -p 7780

Starting Nmap 6.47 ( http://nmap.org ) at 2017-03-16 07:51 EDT
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-servers
Nmap scan report for 168.162.97.143
Host is up (0.00032s latency).
PORT STATE SERVICE
7780/tcp open unknown

Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
-bash-4.1#
User avatar
mcapra
Posts: 3739
Joined: Thu May 05, 2016 3:54 pm

Re: NRPE: Unable to read output

Post by mcapra »

Just to clarify, which server is this: 10.146.1.37

Your original post doesn't describe this server:
1) Nagios server itself (ssbpops01_10.146.1.100)
2) Solaris remote host (Ssb-voor-01_168.162.97.143)
3) Solaris remote host (ssbpech01_10.146.1.38)
Can you run this command from the CLI of your Nagios Core (ssbpops01_10.146.1.100) machine:

Code: Select all

nmap 168.162.97.143 -p 5666
Since the nmap from your Nagios Core machine to 168.162.97.143 shows port 7780 as open, is there any particular reason you're running your JMX checks through NRPE when it appears as though you could be running check_jmx directly from the Nagios Core machine?

If that sounds reasonable, I would think you could run check_jmx from the Nagios Core machine like so:

Code: Select all

check_jmx -U service:jmx:rmi:///jndi/rmi://168.162.97.143:7780/jmxrmi -O jboss.system:type=ServerInfo -A TotalMemory -w 3247300864 -c 3251495168
And get results back.
Former Nagios employee
https://www.mcapra.com/
Katya.Ailarov
Posts: 25
Joined: Wed Aug 17, 2016 5:29 am

Re: NRPE: Unable to read output

Post by Katya.Ailarov »

nmap command from ssbpops01_10.146.1.100 (Nagios machine):

-bash-4.1# nmap 168.162.97.143 -p 5666

Starting Nmap 6.47 ( http://nmap.org ) at 2017-03-19 10:35 EDT
mass_dns: warning: Unable to determine any DNS servers. Reverse DNS is disabled. Try using --system-dns or specify valid servers with --dns-servers
Nmap scan report for 168.162.97.143
Host is up (0.00034s latency).
PORT STATE SERVICE
5666/tcp open nrpe

Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
-bash-4.1#

check_jmx from Nagios server itself (ssbpops01_10.146.1.100):
-bash-4.1# ./check_jmx -U service:jmx:rmi:///jndi/rmi://168.162.97.143:7780/jmxrmi -O jboss.system:type=ServerInfo -A TotalMemory -w 3247300864 -c 3251495168


JMX CRITICAL - Error opening RMI connection: Connection refused to host: 168.162.97.143; nested exception is:
java.net.ConnectException: Connection timed out (Connection timed out)
-bash-4.1# hostname
ssbpops01.ssb.sungard.com
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: NRPE: Unable to read output

Post by rkennedy »

The nmap against 168.x.x.x mentions that TCP is open, is UDP open as well or is it being blocked since it's a WAN address?

Please post the related configurations you're using on the client java application side so we can see how your JMX is setup.
Former Nagios Employee
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: NRPE: Unable to read output

Post by dwhitfield »

rkennedy wrote:The nmap against 168.x.x.x mentions that TCP is open, is UDP open as well or is it being blocked since it's a WAN address?
For clarity on this piece, run nmap -sU -p 5666 168.162.97.143.

Also, yes JMX configs would be great.
Locked