use of NRPE without SSL

[stefano razzauti]

thank you a lot.
now the connection between nagios server and nrpe daemon on the client 
by nrpe work well.
Only one note: the connection goes well only if I run the daemon as a 
standalone daemon on the Solaris host.
While if I insert it in the inetd daemon when I try to connect the 
Solaris host from the nagios server I obtain:

nagios_server> check_nrpe -n -H solaris_host -c check_load
CHECK_NRPE: Received 0 bytes from daemon.  Check the remote server logs 
for error messages.

why this?

thanks again

stefano

Jeffery P. Humes wrote:

>I have provided a patch to the maintainer for this also.  when you call "nrpe" or "check_nrpe" you can provide the option "-n"
>to tell it not to use SSL for the connection.
>
>Here is the patch.  This patch only adds the usage statement for the -n option to nrpe/check_nrpe.  the option is available 
>even if you do not apply this patch.  You can still use the -n option without recompiling.
>
>
>
>-Jeff
>
>
>
> ###########################
> # Start patch
> ###########################
> diff -r -u nrpe-2.0.pristine/src/check_nrpe.c nrpe-2.0/src/check_nrpe.c
> --- nrpe-2.0.pristine/src/check_nrpe.c  2003-09-08 21:52:37.000000000 
> -0500
> +++ nrpe-2.0/src/check_nrpe.c   2004-03-11 18:29:36.000000000 -0600
> @@ -82,10 +82,11 @@
>  
>         if(result!=OK || show_help==TRUE){
>  
> -               printf("Usage: check_nrpe -H <host> [-p <port>] [-t 
> <timeout>] [-c <command>] [-a <arglist...>]\n");
> +               printf("Usage: check_nrpe -H <host> [-n] [-p <port>] 
> [-t <timeout>] [-c <command>] [-a <arglist...>]\n");
>                 printf("\n");
>                 printf("Options:\n");
>                 printf(" <host>     = The address of the host running 
> the NRPE daemon\n");
> +               printf(" -n         = No SSL\n");
>                 printf(" [port]     = The port on which the daemon is 
> running (default=%d)\n",DEFAULT_SERVER_PORT);
>                 printf(" [timeout]  = Number of seconds before 
> connection times out (default=%d)\n",DEFAULT_SOCKET_TIMEOUT);
>                 printf(" [command]  = The name of the command that the 
> remote daemon should run\n");
> diff -r -u nrpe-2.0.pristine/src/nrpe.c nrpe-2.0/src/nrpe.c
> --- nrpe-2.0.pristine/src/nrpe.c        2003-09-08 21:52:37.000000000 
> -0500
> +++ nrpe-2.0/src/nrpe.c 2004-03-11 18:38:37.000000000 -0600
> @@ -120,9 +120,10 @@
>  
>         else if(result!=OK || show_help==TRUE){
>  
> -               printf("Usage: nrpe -c <config_file> <mode>\n");
> +               printf("Usage: nrpe -n -c <config_file> <mode>\n");
>                 printf("\n");
>                 printf("Options:\n");
> +               printf("   -n          = No SSL\n");
>                 printf(" <config_file> = Name of config file to use\n");
>                 printf(" <mode>        = One of the following two 
> operating modes:\n"); 
>                 printf("   -i          =    Run as a service under 
> inetd or xinetd\n");
> ###########################
> # End patch
> ###########################
>
>
>-----------------------------------
>
>
>
>Hi,
>I compiled nrpe on a Sun Solaris host without SSL package and all goes 
>well, but when I tried to
>do a check_nrpe from the Nagios server (linux) through the Solaris one I 
>get the following error:
>
>CHECK_NRPE: Error - Could not complete SSL handshake.
>
>Is there possible to monitor remote host (with NRPE) without using SSL 
>on the remote host?
>
>thank in advance
>
>Stefano
>



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
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