NRPE Problems
Gregory Wong
gwong at wong-consulting.com
Sun Mar 2 07:24:58 CET 2008
Hi everyone. I just configured my Nagios box to start monitoring with NRPE.
When I run check_nrpe H 127.0.0.1 it resolves the NRPE version as expected.
Since my monitoring server is colocated and I plan to monitor hosts behind
firewalls I setup a test server behind my firewall at home for testing
purposes.
I have TCP/5666 forwarded to the internal IP address of my test server. That
same port is also open on my Nagios server as well. I am running NRPE on my
Windows server. The version of NRPE running can be found here:
http://tinyurl.com/24o3h3
When I run check_nrpe H <Home IP Address> I get a socket timeout error. I
did a netstat on both servers and it looks like there is a connection.
TCP gwong-srvr1:5666 gwong-srvr1:0 LISTENING
TCP gwong-srvr1:netbios-ssn gwong-srvr1:0 LISTENING
TCP gwong-srvr1:5666 <Nagios IP>:36422 CLOSE_WAIT
TCP gwong-srvr1:5666 <Nagios IP>:38766 CLOSE_WAIT
TCP gwong-srvr1:5666 <Nagios IP>:38907 CLOSE_WAIT
TCP gwong-srvr1:5666 <Nagios IP>:38909 CLOSE_WAIT
root at nagios:~# netstat -at | grep nrpe
tcp 0 0 *:nrpe *:* LISTEN
tcp 0 0 <Nagios IP>:38913 <Home IP>:nrpe ESTABLISHED
root at nagios:~# netstat -at | grep nrpe
tcp 0 0 *:nrpe *:* LISTEN
tcp 0 0 <Nagios IP>:38913 <Home IP>:nrpe FIN_WAIT2
Any ideas why this won¹t work?
Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080302/0da26bbc/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.
::: Messages without supporting info will risk being sent to /dev/null
More information about the Users
mailing list