nrpe on rhel 4 {Disarmed} {Fraud?}

[John Duraisw]

Marc,
I moved the other plugins from another server, and looks like something got
screwed during the transfer. I just recompiled all the nagios plugins on the
client server and things started working fine.

[root at nmsweb libexec]# ./check_nrpe -H 10.31.47.21 -c check_load
OK - load average: 0.00, 0.05, 0.02|load1=0.000;15.000;30.000;0;
load5=0.050;10.000;25.000;0;
load15=0.020;5.000;20.000;0;

Thanks,
-john

On Tue, Mar 11, 2008 at 12:27 PM, John Duraisw <john.duraiswamy at gmail.com>
wrote:

> Marc,
> This is what happens when I do that.
>
> [root at wsfs7-rhel libexec]# ./check_nrpe -H 127.0.0.1
> CHECK_NRPE: Error - Could not complete SSL handshake.
> [root at wsfs7-rhel libexec]# ./check_nrpe -H 127.0.0.1 -c check_load
> CHECK_NRPE: Error - Could not complete SSL handshake.
> [root at wsfs7-rhel libexec]# ./check_nrpe -H 127.0.0.1 -c check_load -n
> CHECK_NRPE: Received 0 bytes from daemon.  Check the remote server logs
> for error messages.
>
> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
> Mar 11 12:22:34 wsfs7-rhel nrpe[26314]: Host 127.0.0.1 is not allowed to
> talk to
>  us!
> Mar 11 12:22:43 wsfs7-rhel nrpe[26317]: Host 127.0.0.1 is not allowed to
> talk to
>  us!
> Mar 11 12:22:46 wsfs7-rhel nrpe[26320]: Host 127.0.0.1 is not allowed to
> talk to
> $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$
>
>
>
>
>
>
> On Tue, Mar 11, 2008 at 12:05 PM, Marc Powell <marc at ena.com> wrote:
>
> >
> >
> > > -----Original Message-----
> > > From: nagios-users-bounces at lists.sourceforge.net [mailto:nagios-users-
> > > bounces at lists.sourceforge.net] On Behalf Of John Duraisw
> > > Sent: Tuesday, March 11, 2008 10:52 AM
> > > To: nagios-users at lists.sourceforge.net
> > > Subject: [Nagios-users] nrpe on rhel 4 {Disarmed} {Fraud?}
> > >
> > > All,
> > > I have problems getting output check_nrpe from client machine. My
> > nagios
> > > server is Centos5 and the client server rhel 4 and I am having the
> > following
> > > issue. I am running the latest version of nrpe and also tried bunch of
> > other
> > > older version, still no luck. When I try to monitor other centos
> > server with
> > > the same config it works fine.
> > >
> > > [root at nmsweb libexec]# ./check_nrpe -H 10.31.47.21
> > > NRPE v2.10
> > > [root at nmsweb libexec]# ./check_nrpe -H 10.31.47.21 -c check_load
> > > NRPE: Unable to read output
> >
> > Run the check_load command as defined in nrpe.cfg on 10.31.47.21 as the
> > nagios user on 10.31.47.21 and see what it says.
> >
> > > [root at nmsweb libexec]# ./check_nrpe -H 10.31.47.21 -c check_lljfj
> > > NRPE: Command 'check_lljfj' not defined
> >
> > Define the command 'check_lljfj' in nrpe.cfg on 10.31.47.21.
> >
> > --
> > Marc
> >
> >
> > -------------------------------------------------------------------------
> > 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/
> > _______________________________________________
> > 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
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080311/8a2e89f8/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