Error: Service check command...not defined anywhere!

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.
al_orange
Posts: 55
Joined: Mon Nov 23, 2015 7:27 pm

Re: Error: Service check command...not defined anywhere!

Post by al_orange »

Code: Select all

[root@XEN1 t]# ls /usr/lib
games    libmetrics.a   libmetrics.so    libmetrics.so.0.0.0  lsb    pm-utils   rpm       tcl8.4  xen
gcc-lib  libmetrics.la  libmetrics.so.0  locale               perl5  python2.4  syslinux  X11     yum-plugins
[root@XEN1 t]#

Code: Select all

[root@nagios etc]# ls /usr/lib
binfmt.d   grub        jvm-commmon  modules            sse2
cpp        java        jvm-exports  modules-load.d     sysctl.d
debug      java-1.5.0  jvm-private  polkit-1           systemd
dracut     java-1.6.0  kbd          python2.7          tmpfiles.d
firewalld  java-1.7.0  kdump        rpm                tuned
firmware   java-1.8.0  kernel       sendmail           udev
games      java-ext    locale       sendmail.postfix   x86_64-redhat-linux6E
gcc        jvm         modprobe.d   sendmail.sendmail  yum-plugins
[root@nagios etc]#
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: Error: Service check command...not defined anywhere!

Post by hsmith »

What's the output of ls -l /usr/local/nagios/etc/ ?
Former Nagios Employee.
me.
al_orange
Posts: 55
Joined: Mon Nov 23, 2015 7:27 pm

Re: Error: Service check command...not defined anywhere!

Post by al_orange »

hsmith wrote:What's the output of ls -l /usr/local/nagios/etc/ ?
On the main Nagios server:

Code: Select all

[root@nagios ~]# ls -l /usr/local/nagios/etc/
total 88
-rw-rw-r-- 1 nagios nagios 12267 Nov 11 15:39 cgi.cfg
-rw-r--r-- 1 root   root     358 Nov 24 15:41 commands.cfg
-rw-r--r-- 1 root   root    1095 Nov 25 11:40 hosts.cfg
-rw-r--r-- 1 root   root      50 Nov 11 15:42 htpasswd.users
-rw-r--r-- 1 root   root     501 Nov 23 15:20 linux-hosts.cfg
-rw-r--r-- 1 root   root     585 Nov 23 16:19 linux-services.cfg
-rw-rw-r-- 1 nagios nagios 44965 Nov 25 11:34 nagios.cfg
drwxrwxr-x 2 nagios nagios  4096 Dec 14 16:06 objects
-rw-rw---- 1 nagios nagios  1312 Nov 11 15:39 resource.cfg
-rw-r--r-- 1 root   root    1526 Nov 30 11:43 services.cfg

On the other host:

Code: Select all

[root@ora_linux7_xen2 ~]# ls -l /usr/local/nagios/etc/
total 16
-rw-r--r--. 1 root   root    357 Nov 24 10:18 commands.cfg
-rw-r--r--. 1 nagios nagios 8195 Nov 25 11:38 nrpe.cfg
User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: Error: Service check command...not defined anywhere!

Post by hsmith »

Can you post the commands.cfg and nrpe.cfg from the host?
Former Nagios Employee.
me.
al_orange
Posts: 55
Joined: Mon Nov 23, 2015 7:27 pm

Re: Error: Service check command...not defined anywhere!

Post by al_orange »

hsmith wrote:Can you post the commands.cfg and nrpe.cfg from the host?
commands.cfg

Code: Select all

##############################################################################
# NRPE CHECK COMMAND
# Command to use NRPE to check remote host systems
###############################################################################

define command{
        command_name check_nrpe
        command_line $USER1$/check_nrpe -H $HOSTADDRESS$ -c $ARG1$
        }


nrpe.cfg

Code: Select all

#############################################################################
# Sample NRPE Config File
# Written by: Ethan Galstad (nagios@nagios.org)
#
# 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,172.17.60.1



# 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=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 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_hda1]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /dev/hda1
command[check_zombie_procs]=/usr/local/nagios/libexec/check_procs -w 5 -c 10 -s Z
command[check_total_procs]=/usr/local/nagios/libexec/check_procs -w 150 -c 200
command[check_swap]=/usr/local/nagios/libexec/check_swap -w 20% -c 10%

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



User avatar
hsmith
Agent Smith
Posts: 3539
Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:

Re: Error: Service check command...not defined anywhere!

Post by hsmith »

What is the output of ls /usr/local/nagios/libexec/?
Former Nagios Employee.
me.
rkennedy
Posts: 6579
Joined: Mon Oct 05, 2015 11:45 am

Re: Error: Service check command...not defined anywhere!

Post by rkennedy »

I'd like to see if you have multiples of some files. Can you post the result of -

Code: Select all

ls -l /usr/local/nagios/etc/objects/
Also - looks like the permissions aren't proper on some of the files in your /usr/local/nagios/etc/ directory. Can you run the following -

Code: Select all

chown nagios:nagios /usr/local/nagios/etc/*
Former Nagios Employee
al_orange
Posts: 55
Joined: Mon Nov 23, 2015 7:27 pm

Re: Error: Service check command...not defined anywhere!

Post by al_orange »

hsmith wrote:What is the output of ls /usr/local/nagios/libexec/?

Code: Select all

[root@nagios ~]# ls /usr/local/nagios/libexec
check_nrpe  eventhandlers
al_orange
Posts: 55
Joined: Mon Nov 23, 2015 7:27 pm

Re: Error: Service check command...not defined anywhere!

Post by al_orange »

rkennedy wrote:I'd like to see if you have multiples of some files. Can you post the result of -

Code: Select all

ls -l /usr/local/nagios/etc/objects/

Also - looks like the permissions aren't proper on some of the files in your /usr/local/nagios/etc/ directory. Can you run the following -

Code: Select all

chown nagios:nagios /usr/local/nagios/etc/*
Done.
al_orange
Posts: 55
Joined: Mon Nov 23, 2015 7:27 pm

Re: Error: Service check command...not defined anywhere!

Post by al_orange »

[quote="rkennedy"]I'd like to see if you have multiples of some files. Can you post the result of -

Code: Select all

ls -l /usr/local/nagios/etc/objects/

Code: Select all

[root@nagios ~]# ls -l /usr/local/nagios/etc/objects/
total 60
-rw-r--r-- 1 root   root     338 Nov 23 15:49 command.cfg
-rw-rw-r-- 1 nagios nagios  8046 Nov 25 11:47 commands.cfg
-rw-rw-r-- 1 nagios nagios  2138 Nov 11 15:39 contacts.cfg
-rw-r--r-- 1 root   root       1 Nov 18 13:02 host1.cfg
-rw-rw-r-- 1 nagios nagios  5375 Nov 11 15:39 localhost.cfg
-rw-rw-r-- 1 nagios nagios  3096 Nov 11 15:39 printer.cfg
-rw-r--r-- 1 root   root    2950 Nov 24 15:56 service.cfg
-rw-rw-r-- 1 nagios nagios  3265 Nov 11 15:39 switch.cfg
-rw-rw-r-- 1 nagios nagios 10621 Nov 11 15:39 templates.cfg
-rw-rw-r-- 1 nagios nagios  3180 Nov 11 15:39 timeperiods.cfg
-rw-rw-r-- 1 nagios nagios  3991 Nov 11 15:39 windows.
Locked