Page 1 of 2

NRPE agent on Solaris 10 server

Posted: Mon Apr 06, 2015 11:50 am
by krobertson71
We installed the NRPE agent for Solaris and are having quite a time with the SSL Handshake error. We have put in the two hosts that we want to communicate with the agent.

Server is running Solaris 10.

Only thing odd is where the installer is putting the plugins: /opt/nagios/libexec.

We are also getting the 'Could not complete SSL handshakre' locally when running ./check_nrpe -H localhost.


Here is a copy of our nrpe.cfg. Also no xinetd running.

Code: Select all

#############################################################################
# Sample NRPE Config File
# Written by: Ethan Galstad ([email protected])
#
# Last Modified: 11-23-2007
#
# NOTES:
# This is a sample configuration file for the NRPE daemon.  It needs to be
# located on the remote host that is running the NRPE daemon, not the host
# from which the check_nrpe client is being executed.
#############################################################################
 
 
# LOG FACILITY
# The syslog facility that should be used for logging purposes.
 
log_facility=daemon
 
 
 
# PID FILE
# The name of the file in which the NRPE daemon should write it's process ID
# number.  The file is only written if the NRPE daemon is started by the root
# user and is running in standalone mode.
 
pid_file=/var/run/nrpe.pid
 
 
 
# PORT NUMBER
# Port number we should wait for connections on.
# NOTE: This must be a non-priviledged port (i.e. > 1024).
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd
 
server_port=5666
 
 
 
# SERVER ADDRESS
# Address that nrpe should bind to in case there are more than one interface
# and you do not want nrpe to bind on all interfaces.
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd
 
#server_address=127.0.0.1
 
 
 
# NRPE USER
# This determines the effective user that the NRPE daemon should run as.
# You can either supply a username or a UID.
#
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd
 
nrpe_user=nagios
 
 
 
# NRPE GROUP
# This determines the effective group that the NRPE daemon should run as.
# You can either supply a group name or a GID.
#
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd
 
nrpe_group=nagios
 
 
 
# ALLOWED HOST ADDRESSES
# This is an optional comma-delimited list of IP address or hostnames
# that are allowed to talk to the NRPE daemon. Network addresses with a bit mask
# (i.e. 192.168.1.0/24) are also supported. Hostname wildcards are not currently
# supported.
#
# Note: The daemon only does rudimentary checking of the client's IP
# address.  I would highly recommend adding entries in your /etc/hosts.allow
# file to allow only the specified host to connect to the port
# you are running this daemon on.
#
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd
 
allowed_hosts=127.0.0.1,10.0.103.179,10.0.103.83
 
 
 
# COMMAND ARGUMENT PROCESSING
# This option determines whether or not the NRPE daemon will allow clients
# to specify arguments to commands that are executed.  This option only works
# if the daemon was configured with the --enable-command-args configure script
# option.
#
# *** ENABLING THIS OPTION IS A SECURITY RISK! ***
# Read the SECURITY file for information on some of the security implications
# of enabling this variable.
#
# Values: 0=do not allow arguments, 1=allow command arguments
 
dont_blame_nrpe=1
 
 
 
# COMMAND PREFIX
# This option allows you to prefix all commands with a user-defined string.
# A space is automatically added between the specified prefix string and the
# command line from the command definition.
#
# *** THIS EXAMPLE MAY POSE A POTENTIAL SECURITY RISK, SO USE WITH CAUTION! ***
# Usage scenario:
# Execute restricted commmands using sudo.  For this to work, you need to add
# the nagios user to your /etc/sudoers.  An example entry for alllowing
# execution of the plugins from might be:
#
# nagios          ALL=(ALL) NOPASSWD: /usr/lib/nagios/plugins/
#
# This lets the nagios user run all commands in that directory (and only them)
# without asking for a password.  If you do this, make sure you don't give
# random users write access to that directory or its contents!
 
# command_prefix=/usr/bin/sudo
 
 
 
# DEBUGGING OPTION
# This option determines whether or not debugging messages are logged to the
# syslog facility.
# Values: 0=debugging off, 1=debugging on
 
debug=0
 
 
 
# COMMAND TIMEOUT
# This specifies the maximum number of seconds that the NRPE daemon will
# allow plugins to finish executing before killing them off.
 
command_timeout=60
 
 
 
# CONNECTION TIMEOUT
# This specifies the maximum number of seconds that the NRPE daemon will
# wait for a connection to be established before exiting. This is sometimes
# seen where a network problem stops the SSL being established even though
# all network sessions are connected. This causes the nrpe daemons to
# accumulate, eating system resources. Do not set this too low.
 
connection_timeout=300
 
 
 
# WEEK RANDOM SEED OPTION
# This directive allows you to use SSL even if your system does not have
# a /dev/random or /dev/urandom (on purpose or because the necessary patches
# were not applied). The random number generator will be seeded from a file
# which is either a file pointed to by the environment valiable $RANDFILE
# or $HOME/.rnd. If neither exists, the pseudo random number generator will
# be initialized and a warning will be issued.
# Values: 0=only seed from /dev/[u]random, 1=also seed from weak randomness
 
#allow_weak_random_seed=1
 
 
 
# INCLUDE CONFIG FILE
# This directive allows you to include definitions from an external config file.
 
#include=<somefile.cfg>
include=/etc/nagios/nrpe/common.cfg
 
 
 
# INCLUDE CONFIG DIRECTORY
# This directive allows you to include definitions from config files (with a
# .cfg extension) in one or more directories (with recursion).
 
#include_dir=<somedirectory>
#include_dir=<someotherdirectory>
 
 
 
# COMMAND DEFINITIONS
# Command definitions that this daemon will run.  Definitions
# are in the following format:
#
# command[<command_name>]=<command_line>
#
# When the daemon receives a request to return the results of <command_name>
# it will execute the command specified by the <command_line> argument.
#
# Unlike Nagios, the command line cannot contain macros - it must be
# typed exactly as it should be executed.
#
# Note: Any plugins that are used in the command lines must reside
# on the machine that this daemon is running on!  The examples below
# assume that you have plugins installed in a /usr/local/nagios/libexec
# directory.  Also note that you will have to modify the definitions below
# to match the argument format the plugins expect.  Remember, these are
# examples only!
 
 
# The following examples use hardcoded command arguments...
 
#command[check_users]=/opt/nagios/libexec/check_users -w 5 -c 10
#command[check_load]=/opt/nagios/libexec/check_load -w 15,10,5 -c 30,25,20
#command[check_hda1]=/opt/nagios/libexec/check_disk -w 20% -c 10% -p /dev/hda1
#command[check_zombie_procs]=/opt/nagios/libexec/check_procs -w 5 -c 10 -s Z
#command[check_total_procs]=/opt/nagios/libexec/check_procs -w 150 -c 200
 
 
# The following examples allow user-supplied arguments and can
# only be used if the NRPE daemon was compiled with support for
# command arguments *AND* the dont_blame_nrpe directive in this
# config file is set to '1'.  This poses a potential security risk, so
# make sure you read the SECURITY file before doing this.
 
#command[check_users]=/opt/nagios/libexec/check_users -w $ARG1$ -c $ARG2$
#command[check_load]=/opt/nagios/libexec/check_load -w $ARG1$ -c $ARG2$
#command[check_disk]=/opt/nagios/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
#command[check_procs]=/opt/nagios/libexec/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$

Re: NRPE agent on Solaris 10 server

Posted: Mon Apr 06, 2015 12:01 pm
by abrist
First, check to see if it was built without SSL support:

Code: Select all

./check_nrpe -H localhost -n
Next, are you using inetd or tcpwrappers (instead of xinetd)?

Re: NRPE agent on Solaris 10 server

Posted: Mon Apr 06, 2015 2:26 pm
by krobertson71
Info from Unix Admin.

--------------------------------------------
[root@xxxxxx libexec]# ./check_nrpe -H localhost -n
CHECK_NRPE: Received 0 bytes from daemon. Check the remote server logs for error messages.
[root@xxxxxxx libexec]#

inetd is running as is tcp-wrappers
both are builtin as part of Solaris

-------------------------------------------------------

SOrry about the choppy-ness. Had to cut out his name from the skype chat and the server name.

Re: NRPE agent on Solaris 10 server

Posted: Mon Apr 06, 2015 2:34 pm
by abrist
How do you normally restart the nrpe daemon? Do you have multiple daemons running?

Code: Select all

ps -aef | grep nrpe

Re: NRPE agent on Solaris 10 server

Posted: Mon Apr 06, 2015 2:54 pm
by krobertson71
Reply from Unix Admin

-------------------------------------

-bash-3.2$ ps -aef | grep nrpe
nagios 16257 1 0 12:10:43 ? 0:01 /opt/nagios/bin/nrpe -c /etc/nagios/nrpe.cfg -d
-bash-3.2$

sudo svcadm restart svc:/application/nagios/nrpe

------------------------------------

Turns out there will be a firewall issue. But still running the command locally is still producing errors.

Re: NRPE agent on Solaris 10 server

Posted: Tue Apr 07, 2015 9:36 am
by krobertson71
Any update on this issue or anything else I can provide?

Re: NRPE agent on Solaris 10 server

Posted: Tue Apr 07, 2015 9:45 am
by lmiltchev
# NOTE: This option is ignored if NRPE is running under either inetd or xinetd

allowed_hosts=127.0.0.1,10.0.103.179,10.0.103.83
inetd is running as is tcp-wrappers
both are builtin as part of Solaris
Do you have anything in "/etc/hosts.allow" or/and "/etc/hosts.deny"?

Can you run the following commands and show us the output:

Code: Select all

netstat -aln | grep 5666
cat /etc/inet/inetd.conf

Re: NRPE agent on Solaris 10 server

Posted: Tue Apr 07, 2015 10:33 am
by krobertson71
I have sent the request to the Unix admin team.

My question is thought,

If he is running the command locally ./check_nrep -H localhost and still getting the SSL handshake issue, how does making sure outside hosts have access going to fix this?

Re: NRPE agent on Solaris 10 server

Posted: Tue Apr 07, 2015 10:45 am
by lmiltchev
127.0.0.1 has to be allowed, otherwise you would get:

Code: Select all

CHECK_NRPE: Error - Could not complete SSL handshake.
On one of my test boxes I run NRPE under xinetd. If I don't allow 127.0.0.1 the local check fails:

Code: Select all

grep "only_from" /etc/xinetd.d/nrpe
only_from       = x.x.x.x

./check_nrpe -H localhost
CHECK_NRPE: Error - Could not complete SSL handshake.
If I add it to the config, the check starts working:

Code: Select all

grep "only_from" /etc/xinetd.d/nrpe
only_from       = 127.0.0.1 x.x.x.x

service xinetd restart
Stopping xinetd:                                           [  OK  ]
Starting xinetd:                                           [  OK  ]

./check_nrpe -H localhost
NRPE v2.15

Re: NRPE agent on Solaris 10 server

Posted: Wed Apr 08, 2015 10:47 am
by krobertson71
You can close. We switched to check_by_ssh.