check_nrpe and check_disk mismatch

This forum is intended for the discussion of Nagios plugin development. Feature requests, patches, bug fixes, and all types of development-related discussions are welcome!

NOTE: The SourceForge.net nagiosplug-devel mailing list has been deprecated in favor of this forum in order to expedite support and provide additional features not available on the old mailing list.

check_nrpe and check_disk mismatch

Postby hemak88 » Sun Jul 15, 2018 6:04 am

Hi,

I face an issue that while checking the status of disks remotely from nagios server with command below and from nagios GUI, it gives incorrect status of disks and usage. Also it doesn't pick the threshold value set. This issue is shown by only one client server.
Code: Select all
# /usr/local/nagios/libexec/check_nrpe -H clientname -c check_disk


Given below is the output of the above command:
Code: Select all
[nagios@servername linux]# /usr/local/nagios/libexec/check_nrpe -H clientname-c check_disk
DISK CRITICAL - free space: / 30084 MB (11.09% inode=100%); /home 7455 MB (78.98% inode=100%);| /=240963MB;228442;242720;0;285553 /home=1984MB;7960;8458;0;9951
[nagios@servername linux]#


However, while checking disk status locally from nagios client server with below command, I get proper status.
Code: Select all
# /usr/local/nagios/libexec/check_disk -w 10% -c 5% -p /home -p /


Given below is the output of the above command:
Code: Select all
[nagios@clientname nagios]# /usr/local/nagios/libexec/check_disk -w 10% -c 5% -p /home -p /
DISK OK - free space: /home 7455 MB (78.98% inode=100%); / 30076 MB (11.09% inode=100%);| /home=1984MB;8955;9453;0;9951 /=240970MB;256997;271275;0;285553
[nagios@clientname nagios]#


Below is the entry added in /usr/local/nagios/etc/nrpe.cfg file in client server
Code: Select all
command[check_disk]=/usr/local/nagios/libexec/check_disk -w 10% -c 5% -p /home -p /


Below is the command definition in Nagios server:
Code: Select all
define service{
        use                             linux-service         ; Name of service template to use
        host_name                       nklipai01
        service_description             Root Partition
        check_command                   check_nrpe!check_disk!20%!10%!/
        }


I experience same issue of incorrect data for "number of procs" check in this server. Rest of all checks are fine for this server. I am not able to find any logs nor any clue of what the issue is. Kindly assist.
hemak88
 
Posts: 15
Joined: Wed Mar 29, 2017 2:31 am

Re: check_nrpe and check_disk mismatch

Postby npolovenko » Mon Jul 16, 2018 3:42 pm

@hemak88, Your nrpe command has hardcoded arguments:
Code: Select all
command[check_disk]=/usr/local/nagios/libexec/check_disk -w 10% -c 5% -p /home -p /


So the thresholds in your command definition are ignored:
Code: Select all
define service{
        use                             linux-service         ; Name of service template to use
        host_name                       nklipai01
        service_description             Root Partition
        check_command                   check_nrpe!check_disk!20%!10%!/
        }


You should change the nrpe command to look like this:
Code: Select all
command[check_disk]=/usr/local/nagios/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$


And then restart the nrpe daemon on the client server.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
npolovenko
Support Tech
 
Posts: 2109
Joined: Mon May 15, 2017 5:00 pm

Re: check_nrpe and check_disk mismatch

Postby hemak88 » Tue Jul 17, 2018 3:25 am

@npolovenko
I added below in nrpe.cfg file in the client server:
Code: Select all
command[check_disk]=/usr/local/nagios/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$


Below in the nagios server conf file of the client:
Code: Select all
define service{
        use                             linux-service         ; Name of service template to use
        host_name                       clientname
        service_description             Root Partition
        check_command                   check_nrpe!check_disk!10%!8%!/
        }


Restarted xinetd and nagios service. Still same result as below:
Code: Select all
[nagios@clientname ~]$ /usr/local/nagios/libexec/check_disk -w 10 -c 8 -p /
DISK OK - free space: / 29243 MB (10.78% inode=100%);| /=241803MB;285543;285545;0;285553
[nagios@clientname ~]$

Code: Select all
[nagios@nagiosserver~]$ /usr/local/nagios/libexec/check_nrpe -H clientname -c check_disk
DISK CRITICAL - free space: / 29237 MB (10.78% inode=100%); /home 7455 MB (78.98% inode=100%);| /=241810MB;228442;242720;0;285553 /home=1984MB;7960;8458;0;9951
[nagios@nagiosserver ~]$


No other clients added to this nagios server face the same issue.
hemak88
 
Posts: 15
Joined: Wed Mar 29, 2017 2:31 am

Re: check_nrpe and check_disk mismatch

Postby lmiltchev » Wed Jul 18, 2018 12:46 pm

When you test your command from the Nagios server, you are not passing arguments but you should, according to your command definition:
Code: Select all
command[check_disk]=/usr/local/nagios/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$


Try running:
Code: Select all
/usr/local/nagios/libexec/check_nrpe -H clientname -c check_disk -a 10 8 /


Did the output change?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
User avatar
lmiltchev
QA Manager
 
Posts: 10927
Joined: Mon May 23, 2011 12:15 pm

Re: check_nrpe and check_disk mismatch

Postby hemak88 » Wed Jul 18, 2018 11:45 pm

Below is the error:
Code: Select all
[nagios@servername~]$ /usr/local/nagios/libexec/check_nrpe -H clientname-c check_disk -a 10 8 /
NRPE: Command 'check_disk!10!8!/' not defined


Once again, configurations are as below:
In nagios server:
Code: Select all
define service{
        use                             linux-service         ; Name of service template to use
        host_name                       clientname
        service_description             Root Partition
        check_command                   check_nrpe!check_disk!10%!8%!/
        }


In nagios client nrpe.cfg
Code: Select all
command[check_disk]=/usr/local/nagios/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
hemak88
 
Posts: 15
Joined: Wed Mar 29, 2017 2:31 am

Re: check_nrpe and check_disk mismatch

Postby lmiltchev » Thu Jul 19, 2018 9:04 am

Did you restart NRPE daemon (or xinetd) on the client after making changes? In your first post you showed us that the check_disk command is indeed defined...
[nagios@servername~]$ /usr/local/nagios/libexec/check_nrpe -H clientname-c check_disk -a 10 8 /
NRPE: Command 'check_disk!10!8!/' not defined

Is this a typo? There should be a space between the clientname and the "-c" flag.

Also, you need to pass arguments after the "-a" flag, so the check_command in your service definition doesn't look right. Instead of this:
Code: Select all
check_command                   check_nrpe!check_disk!10%!8%!/

your should have this:
Code: Select all
check_command                   check_nrpe!check_disk!-a 10% 8% /


Can you show us how the check_nrpe command is defined on the nagios server?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
User avatar
lmiltchev
QA Manager
 
Posts: 10927
Joined: Mon May 23, 2011 12:15 pm

Re: check_nrpe and check_disk mismatch

Postby hemak88 » Wed Jul 25, 2018 12:15 am

>> Did you restart NRPE daemon (or xinetd) on the client after making changes?
Yes, I restarted xinetd service.

>> Is this a typo? There should be a space between the clientname and the "-c" flag.
It is a typo

>> Also, you need to pass arguments after the "-a" flag, so the check_command in your service definition doesn't look right. Instead of this:
I tried this way as well. Now I find this same issue emerging in all servers. Whatever parameters like "-x" or "-p" added to check disk is ignored

>> Can you show us how the check_nrpe command is defined on the nagios server?
Code: Select all
define command{
command_name check_nrpe
command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -t 60 -c $ARG1$
}
hemak88
 
Posts: 15
Joined: Wed Mar 29, 2017 2:31 am

Re: check_nrpe and check_disk mismatch

Postby lmiltchev » Wed Jul 25, 2018 12:30 pm

Can you post the nrpe.cfg file from the client machine?

Also, run the following commands on the client and show the output:

Code: Select all
/usr/local/nagios/bin/nrpe -V
ps axuw | grep nrpe
netstat -at | grep nrpe
/usr/local/nagios/libexec/check_disk -w 10% -c 8% -p /
/usr/local/nagios/libexec/check_disk -V


How was NRPE installed on the client? What was the guide/tutorial/document that you followed?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.

Be sure to check out our Knowledgebase for helpful articles and solutions!
User avatar
lmiltchev
QA Manager
 
Posts: 10927
Joined: Mon May 23, 2011 12:15 pm

Re: check_nrpe and check_disk mismatch

Postby hemak88 » Thu Jul 26, 2018 7:13 am

>> Can you post the nrpe.cfg file from the client machine?
Code: Select all
#############################################################################
# Sample NRPE Config File
# Written by: Ethan Galstad (nagios@nagios.org)
#
# Last Modified: 2016-05-10
#
# 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



# 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



# 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=/usr/local/nagios/var/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



# LISTEN QUEUE SIZE
# Listen queue size (backlog) for serving incoming connections.
# You may want to increase this value under high load.

#listen_queue_size=5



# 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,localhost,<IPofnagiosserver>


# 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=0



# BASH COMMAND SUBTITUTION
# This option determines whether or not the NRPE daemon will allow clients
# to specify arguments that contain bash command substitutions of the form
# $(...).  This option only works if the daemon was configured with both
# the --enable-command-args and --enable-bash-command-substitution configure
# script options.
#
# *** ENABLING THIS OPTION IS A HIGH SECURITY RISK! ***
# Read the SECURITY file for information on some of the security implications
# of enabling this variable.
#
# Values: 0=do not allow bash command substitutions,
#         1=allow bash command substitutions

allow_bash_command_substitution=0



# 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



# 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



# WEAK 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



# SSL/TLS OPTIONS
# These directives allow you to specify how to use SSL/TLS.

# SSL VERSION
# This can be any of: SSLv2 (only use SSLv2), SSLv2+ (use any version),
#        SSLv3 (only use SSLv3), SSLv3+ (use SSLv3 or above), TLSv1 (only use
#        TLSv1), TLSv1+ (use TLSv1 or above), TLSv1.1 (only use TLSv1.1),
#        TLSv1.1+ (use TLSv1.1 or above), TLSv1.2 (only use TLSv1.2),
#        TLSv1.2+ (use TLSv1.2 or above)
# If an "or above" version is used, the best will be negotiated. So if both
# ends are able to do TLSv1.2 and use specify SSLv2, you will get TLSv1.2.

#ssl_version=SSLv2+

# SSL USE ADH
# This is for backward compatibility and is DEPRECATED. Set to 1 to enable
# ADH or 2 to require ADH. 1 is currently the default but will be changed
# in a later version.

#ssl_use_adh=1

# SSL CIPHER LIST
# This lists which ciphers can be used. For backward compatibility, this
# defaults to 'ssl_cipher_list=ALL:!MD5:@STRENGTH' in this version but
# will be changed to something like the example below in a later version of NRPE.

#ssl_cipher_list=ALL:!MD5:@STRENGTH
#ssl_cipher_list=ALL:!aNULL:!eNULL:!SSLv2:!LOW:!EXP:!RC4:!MD5:@STRENGTH

# SSL Certificate and Private Key Files

#ssl_cacert_file=/etc/ssl/servercerts/ca-cert.pem
#ssl_cert_file=/etc/ssl/servercerts/nagios-cert.pem
#ssl_privatekey_file=/etc/ssl/servercerts/nagios-key.pem

# SSL USE CLIENT CERTS
# This options determines client certificate usage.
# Values: 0 = Don't ask for or require client certificates (default)
#         1 = Ask for client certificates
#         2 = Require client certificates

#ssl_client_certs=0

# SSL LOGGING
# This option determines which SSL messages are send to syslog. OR values
# together to specify multiple options.

# Values: 0x00 (0)  = No additional logging (default)
#         0x01 (1)  = Log startup SSL/TLS parameters
#         0x02 (2)  = Log remote IP address
#         0x04 (4)  = Log SSL/TLS version of connections
#         0x08 (8)  = Log which cipher is being used for the connection
#         0x10 (16) = Log if client has a certificate
#         0x20 (32) = Log details of client's certificate if it has one
#         -1 or 0xff or 0x2f = All of the above

#ssl_logging=0x00



# INCLUDE CONFIG FILE
# This directive allows you to include definitions from an external config file.

#include=<somefile.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]=/usr/local/nagios/libexec/check_users -w 5 -c 10
command[check_load]=/usr/local/nagios/libexec/check_load -w 15,10,5 -c 30,25,20
command[check_disk]=/usr/local/nagios/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
#command[check_disk]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /
#command[check_zombie_procs]=/usr/local/nagios/libexec/check_procs -w 5 -c 10 -s Z
command[check_procs]=/usr/local/nagios/libexec/check_procs -w 150 -c 200
command[check_ssh]=/usr/local/nagios/libexec/check_ssh -H localhost
command[check_swap]=/usr/local/nagios/libexec/check_swap -w 20% -c 10%
command[check_ping]=/usr/local/nagios/libexec/check_ping -H localhost -w 2,2% -c 3,3%
#command[check_mysql]=/usr/local/nagios/libexec/check_mysql.pl
command[check_ntp]=/usr/local/nagios/libexec/check_ntp -H localhost
command[check_usercreation]=/usr/local/nagios/libexec/check_usercreation.sh
command[check_system_pp]=/usr/local/nagios/libexec/check_system_pp
command[check_chrony]=/usr/local/nagios/libexec/check_chrony.sh 1 2
command[check_iptables]=/usr/bin/sudo /usr/local/nagios/libexec/check_iptables.sh -H localhost
#command[check_mountpoints]=/usr/local/nagios/libexec/check_mountpoints.sh -f /proc/mounts /data
command[check_passwd_expiration]=/usr/bin/sudo /usr/local/nagios/libexec/check_paswd_expiry.sh root



# 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]=/usr/local/nagios/libexec/check_users -w $ARG1$ -c $ARG2$
#command[check_load]=/usr/local/nagios/libexec/check_load -w $ARG1$ -c $ARG2$
#command[check_disk]=/usr/local/nagios/libexec/check_disk -w $ARG1$ -c $ARG2$ -p $ARG3$
#command[check_procs]=/usr/local/nagios/libexec/check_procs -w $ARG1$ -c $ARG2$ -s $ARG3$


>> Also, run the following commands on the client and show the output:
Code: Select all
[root@client ~]# /usr/local/nagios/bin/nrpe -V

NRPE - Nagios Remote Plugin Executor
Copyright (c) 1999-2008 Ethan Galstad (nagios@nagios.org)
Version: 3.0.1
Last Modified: 09-08-2016
License: GPL v2 with exemptions (-l for more info)
SSL/TLS Available, OpenSSL 0.9.6 or higher required

***************************************************************
** POSSIBLE SECURITY RISK - TCP WRAPPERS ARE NOT AVAILABLE!  **
**      Read the NRPE SECURITY file for more information     **
***************************************************************

Usage: nrpe [-n] -c <config_file> [-4|-6] <mode>

Options:
-n               = Do not use SSL
-c <config_file> = Name of config file to use
-4               = use ipv4 only
-6               = use ipv6 only
<mode>           = One of the following operating modes:
   -i             =    Run as a service under inetd or xinetd
   -d             =    Run as a standalone daemon
   -d -s          =    Run as a subsystem under AIX
   -f             =    Don't fork() for systemd, launchd, etc.

Notes:
This program is designed to process requests from the check_nrpe
plugin on the host(s) running Nagios.  It can run as a service
under inetd or xinetd (read the docs for info on this), or as a
standalone daemon. Once a request is received from an authorized
host, NRPE will execute the command/plugin (as defined in the
config file) and return the plugin output and return code to the
check_nrpe plugin.

[root@client ~]# ps axuw | grep nrpe
nagios    1117  0.0  0.0  39684  2144 ?        Ss   Jul05   0:26 /usr/local/nagios/bin/nrpe -c /usr/local/nagios/etc/nrpe.cfg -f
root     48220  0.0  0.0 103324   900 pts/0    S+   16:03   0:00 grep nrpe
[root@client ~]# netstat -at | grep nrpe
tcp        0      0 *:nrpe                      *:*                         LISTEN
tcp        0      0 *:nrpe                      *:*                         LISTEN
[root@client ~]# /usr/local/nagios/libexec/check_disk -w 10% -c 8% -p /
DISK OK - free space: / 29649 MB (10.93% inode=100%);| /=241397MB;256997;262708;0;285553
[root@client ~]# /usr/local/nagios/libexec/check_disk -V
check_disk v2.2.1 (nagios-plugins 2.2.1)
[root@nklipai01 ~]#


>> How was NRPE installed on the client? What was the guide/tutorial/document that you followed?
I downloaded nrpe and nagios plugins from nagios website and followed steps below:
Code: Select all
Upload nrpe and nagios plugin tar files to /usr/local/src/
- Install packages
   # yum install gcc glibc glibc-common gd gd-devel make net-snmp openssl-devel openssl unzip xinetd
- Untar files and get inside nrpe folder
   # unzip nagios-plugins-2.2.1.zip ; tar -xvf nrpe-3.0.1.tar
- # cd nagios-plugins-2.2.1 ; chmod +x configure; ./configure ; make; make install
- # cd ../; cd nrpe-3.0.1;  ./configure
- # make all
- # useradd nagios
- # make install ; make install-plugin ; make install-daemon; make install-config ; make install-inetd; make install-init
- Move all plugin scripts from /usr/local/src to /usr/local/nagios/libexec
   # cd ..; mv check_* /usr/local/nagios/libexec/ ; rm -rf nagios-plugins-2.2.1.zip nrpe-3.0.1.tar
- # chown nagios.nagios /usr/local/nagios/ ; cd  /usr/local/nagios/; chown -R nagios.nagios /usr/local/nagios/libexec
- # chmod +x libexec/check_chrony.sh; chmod +x libexec/check_iptables.sh; chmod +x libexec/check_mountpoints.sh; chmod +x libexec/check_paswd_expiry.sh; chmod +x libexec/check_system_pp; chmod +x libexec/check_usercreation.sh
- # vi /etc/xinetd.d/nrpe  >> Add contents from another server to this file
- # vi /etc/services   >> Add “nrpe             5666/tcp    #nagios nrpe”
- # vi /usr/local/nagios/etc/nrpe.cfg
   allowed_hosts=127.0.0.1,localhost,<ipofnagiosserver>
- Add commands to be checked at the end of the nrpe.cfg
- # service xinetd restart
- verify service is running
   # netstat -at | grep nrpe
hemak88
 
Posts: 15
Joined: Wed Mar 29, 2017 2:31 am

Re: check_nrpe and check_disk mismatch

Postby scottwilkerson » Thu Jul 26, 2018 10:32 am

hemak88 wrote:>> Did you restart NRPE daemon (or xinetd) on the client after making changes?
Yes, I restarted xinetd service.


Based on the following
hemak88 wrote:
Code: Select all
[root@client ~]# ps axuw | grep nrpe
nagios    1117  0.0  0.0  39684  2144 ?        Ss   Jul05   0:26 /usr/local/nagios/bin/nrpe -c /usr/local/nagios/etc/nrpe.cfg -f


nrpe is running as the nrpe service and not under xinetd any longer
run
Code: Select all
service nrpe restart
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
User avatar
scottwilkerson
DevOps Engineer
 
Posts: 12053
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises

Next

Return to Nagios Plugin Development

Who is online

Users browsing this forum: No registered users and 4 guests