No firewall rules in play? eg. allowing connections from your Nagios server to
tcp-5666 and allowing the remove server to connect back to your nagios server?
Did you edit the nrpe.cfg file correctly and add the server to allowed_hosts?
Did you remember to restart NRPE after editing the config?
did you try actually issuing a check like "check_nrpe -H xxx.xxx.xxx.xxx -c
check_users" ?
--
Mat W. - http://www.techadre.com
Date: Mon, 26 Oct 2009 12:33:09 -0400
From: akpg...@gmail.com
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] CHECK_NRPE: Received 0 bytes from daemon.
Hi -
I have installed the NRPE and when trying to run the check_nrpe -H
xx.xx.xxx.xxx from the server where nagios is running , I am getting the
following error
CHECK_NRPE: Received 0 bytes from daemon.Check the remote server logs for error
messages.
Server1 : I set up NRPE and I have added /etc/services nrpe entry . , I have
enabled the service.
I have NRPE set up on an other server and it is running fine. I did follow the
same instructions. Not able to figure out what's wrong with configuration
Regards
_________________________________________________________________
Windows 7: I wanted more reliable, now it's more reliable. Wow!
http://microsoft.com/windows/windows-7/default-ga.aspx?h=myidea?ocid=PID24727::T:WLMTAGL:ON:WL:en-US:WWL_WIN_myidea:102009
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Nagios-users mailing list
Nagios-users@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