NRPE: Unable to read output / check_qmaiq

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
dlambeth
Posts: 12
Joined: Fri Jun 27, 2014 1:22 pm
Contact:

NRPE: Unable to read output / check_qmaiq

Post by dlambeth »

"NRPE: Unable to read output check_qmailq"

I have been using Nagios and check_qmailq for a very long time, however I recently moved to another Linux (Gentoo) box and now the plug-in does not work. This Linux box is the exact same box of the others that are working, and everything is configured identically, so I'm scratching my head on this one. I have poured through every possible knowledge base and help thread I could find, but none of them has helped me thus far. No firewall running, that is not the issue. Permission are set correctly for the folders specified (nagios:nagios) and read/execute is set. All other plug-ins I'm using on that server work just fine, it's just the check_qmailq plugin. I don't use SUDO, so that is not the issue.

If I run this command on the troubled box, it works.
/usr/lib/nagios/plugins/check_qmailq -w 20 -c 30

Returns
QMAILQ OK - messages in queue: 1 messages in queue but not yet preprocessed: 0

However when I try to run this on the remote Nagios server to this box, I receive the following error.
/usr/lib/nagios/plugins/./check_nrpe -H 192.168.x.x -c check_qmailq

Returns
NRPE: Unable to read output

I've been struggling for two days with this issue, I've giving up trying to resolve this without some outside help. If anyone can help me, I will be in your debt forever. :)

I am appending the nrpe.cfg and the debug output. See below.

Code: Select all


---------------NRPE.CFG-------------------------------------------------------------------------------------------
#############################################################################
# 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=/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.5.0.0/16,192.168.1.0/24,192.168.100.0/24,192.168.116.0/24



# 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



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



# 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 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/lib/nagios/plugins/check_users -w 5 -c 10
command[check_load]=/usr/lib/nagios/plugins/check_load -w 15,10,5 -c 30,25,20
command[check_hda1]=/usr/lib/nagios/plugins/check_disk -w 20% -c 10% -p /dev/hda1
command[check_zombie_procs]=/usr/lib/nagios/plugins/check_procs -w 5 -c 10 -s Z
command[check_total_procs]=/usr/lib/nagios/plugins/check_procs -w 150 -c 200
command[check_qmailq]=/usr/lib/nagios/plugins/check_qmailq -w 20 -c 30

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

-----------------debug output messages----------------------------------------------------------------------------------
r 2 11:00:48 mail1 nrpe[1430]: Host is asking for command 'check_qmailq' to be run...
Mar 2 11:00:48 mail1 nrpe[1430]: Running command: /usr/lib/nagios/plugins/check_qmailq -w 20 -c 30
Mar 2 11:00:48 mail1 nrpe[1430]: Command completed with return code 2 and output:
Mar 2 11:00:48 mail1 nrpe[1430]: Sending response - bytes left: 27
Mar 2 11:00:48 mail1 nrpe[1430]: Return Code: 2, Output: NRPE: Unable to read output
Mar 2 11:00:48 mail1 nrpe[1430]: Connection from }▒▒▒{▒▒yG▒▒▒{▒▒^Y▒▒ closed.
Mar 2 11:03:33 mail1 nrpe[1532]: Connection from 192.168.x.x port 7115
Mar 2 11:03:33 mail1 nrpe[1532]: Host address is in allowed_hosts
Mar 2 11:03:33 mail1 nrpe[1532]: Handling the connection...
Mar 2 11:03:33 mail1 nrpe[1532]: Host is asking for command 'check_qmailq' to be run...
Mar 2 11:03:33 mail1 nrpe[1532]: Running command: /usr/lib/nagios/plugins/check_qmailq -w 20 -c 30
Mar 2 11:03:33 mail1 nrpe[1532]: Command completed with return code 2 and output:
Mar 2 11:03:33 mail1 nrpe[1532]: Sending response - bytes left: 27
Mar 2 11:03:33 mail1 nrpe[1532]: Return Code: 2, Output: NRPE: Unable to read output
Mar 2 11:03:33 mail1 nrpe[1532]: Connection from }▒▒▒{▒▒yG▒▒▒{▒▒^Y▒▒ closed.
------------------------------------------------------------------------------------------------------------------------
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: NRPE: Unable to read output / check_qmaiq

Post by hsmith »

dlambeth wrote: If I run this command on the troubled box, it works.
/usr/lib/nagios/plugins/check_qmailq -w 20 -c 30
What user are you running this as?
Former Nagios Employee.
me.
dlambeth
Posts: 12
Joined: Fri Jun 27, 2014 1:22 pm
Contact:

Re: NRPE: Unable to read output / check_qmaiq

Post by dlambeth »

Nagios, and I tried root as well. Same outcome.

Thanks,
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: NRPE: Unable to read output / check_qmaiq

Post by rkennedy »

When you are running /usr/lib/nagios/plugins/check_qmailq -w 20 -c 30 - what user are you running it as?

Also, what are the permissions of that file? ls -l /usr/lib/nagios/plugins/check_qmailq
Former Nagios Employee
dlambeth
Posts: 12
Joined: Fri Jun 27, 2014 1:22 pm
Contact:

Re: NRPE: Unable to read output / check_qmaiq

Post by dlambeth »

Hmm, when I try to run that command logged in as Nagios I get the following error, I think you pointed me in the right direction. I was running as root previously.


"Can't locate Nagios/Plugin/Getopt.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl5/5.16.3/i686-linux /usr/local/lib/perl5/5.16.3 /usr/lib/perl5/vendor_perl/5.16.3/i686-linux /usr/lib/perl5/vendor_perl/5.16.3 /usr/local/lib/perl5 /usr/lib/perl5/vendor_perl /usr/lib/perl5/5.16.3/i686-linux /usr/lib/perl5/5.16.3 .) at /usr/lib/nagios/plugins/check_qmailq line 11.
BEGIN failed--compilation aborted at /usr/lib/nagios/plugins/check_qmailq line 11."
dlambeth
Posts: 12
Joined: Fri Jun 27, 2014 1:22 pm
Contact:

Re: NRPE: Unable to read output / check_qmaiq

Post by dlambeth »

Permissions for that file are:

-rwxr-xr-x 1 nagios nagios 3076 Jul 2 2014 /usr/lib/nagios/plugins/check_qmailq
dlambeth
Posts: 12
Joined: Fri Jun 27, 2014 1:22 pm
Contact:

SOLVED!!!!! NRPE: Unable to read output / check_qmaiq

Post by dlambeth »

SOLVED:!!

The Getopt.pm file did not have "nagios" permissions on it. I did a search for "Getopt.pm" and once I determined the location I add nagios group to the permission of that folder and BAM! it works.

Thank you so much for pointing me in the right direction, you rock.

:mrgreen:
Locked