[Nagios-users] check_nrpe issues
I have a remote Linux host (ubuntu), and the monitoring server is Redhat Linux Enterprise 4. I have disabled SSL for check_nrpe and when testing the connection to the remote host with the /usr/local/nagios/libexec/check_nrpe -H 192.168.0.1 command, I receive the following error: CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages. There are no firewalls in-between the monitoring server and the remote host, and the remote host can check itself and get the NRPE version number. Help is greatly appreciated as I am banging my head on this one :) -Izz - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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
Re: [Nagios-users] check_nrpe issues
Izz Abdullah schrieb: I have a remote Linux host (ubuntu), and the monitoring server is Redhat Linux Enterprise 4. I have disabled SSL for check_nrpe and when testing the connection to the remote host with the /usr/local/nagios/libexec/check_nrpe -H 192.168.0.1 command, I receive the following error: CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages. Hm, what helped me recently figuring out a 0 bytes-issue, was activating the debug in nrpe.cfg on the remote host and looking in the syslog. There I immediately found the error. (Missing utils.pm in perl-path). Greetz, Marcus - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ 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
