Hello There, Guest! Login Register
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Monitoring Linux Hosts with NRPE (Both NEMS 1.4.1 and 1.5)

#3
OK, moving to build 6 fixed that issue.  Thanks for the recommendation!!!

Now when I run (from my NEMS Server):

/usr/lib/nagios/plugins/check_nrpe -H 192.168.253.5 -c check_root

I get the follow error:  

CHECK_NRPE: Error - Could not connect to 192.168.253.5: Connection reset by peer

In Nagios, it shows:  

CHECK_NRPE: Error - Could not connect to 192.168.253.5. Check system logs on 192.168.253.5

I enabled the logging option in nrpe.cfg and restarted the service.

When I look at the log file under /usr/local/nagios/var/ it shows the following error:

[1552094679] CONN_CHECK_PEER: checking if host is allowed: 192.168.253.14 port 34029
[1552094679] Connection from 192.168.253.14 port 34029
[1552094679] is_an_allowed_host (AF_INET): is host >192.168.253.14< an allowed host >192.168.253.14<
[1552094679] is_an_allowed_host (AF_INET): is host >192.168.253.14< an allowed host >192.168.253.14<
[1552094679] Host 192.168.253.14 is not allowed to talk to us!
[1552094679] Connection from 192.168.253.14 closed.

It seems like check command is using a different port everytime Nagios (or I do via terminal) sends a check.

How do I get nrpe to use only port 5666?

Thanks!
 
Messages In This Thread
Monitoring Linux Hosts with NRPE (Both NEMS 1.4.1 and 1.5) - by amc_oldsarge - 02-24-2019, 09:25 PM
RE: Monitoring Linux Hosts with NRPE (Both NEMS 1.4.1 and 1.5) - by hellifiknow - 03-02-2019, 01:51 PM
RE: Monitoring Linux Hosts with NRPE (Both NEMS 1.4.1 and 1.5) - by amc_oldsarge - 03-08-2019, 09:37 PM
 
Forum Jump:

Users browsing this thread: 1 Guest(s)