Service Check works from CLI but not GUI

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
ahoward12
Posts: 137
Joined: Thu Jan 05, 2017 10:24 am

Service Check works from CLI but not GUI

Post by ahoward12 »

Hey Gents,

I have a service check that works when I run it in the CLI as well as using the "> Run Check Command" in CCM. However, it doesn't work after I apply the configuration and try and it view it outside of CCM. Examples below, as I am out of ideas..

Code: Select all

[root@NAGIOS vmware]# /usr/local/nagios/libexec/check_esx3.pl -H "10.10.99.26" -f "/usr/local/nagiosxi/etc/components/vmware/vcsa_cafaroco_com_auth.txt" -l "VMFS" -s "Prod Servers" -c 5%:
CHECK_ESX3.PL OK - Storages : 'Prod Servers'(free)=440.70 GB (9.36%) | 'Prod Servers'=9.36%;;5:
As you can see from the attached screenshot it says incorrect username or password but it works from the authorization file when I use the CLI. I also verified the host "VCSA" does have the correct IP as well.

Any ideas? I have never had an issue so simple and weird as this..

Nagios XI 5.5.8
CentOS 6.8
VMware 6.5
You do not have the required permissions to view the files attached to this post.
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: Service Check works from CLI but not GUI

Post by cdienger »

Can you double check and share the configuration of these checks as seen in the CCM ? I wonder if the configuration isn't matching what is being run on the command line. My initial thought was that maybe it was due to permissions since running it from the cli as root is different from running it in the GUI(which uses nagios), but wasn't able to reproduce. It may be worth giving it a shot though. On the command line, switch to the nagios user first before running the plugin:

su - nagios
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
ahoward12
Posts: 137
Joined: Thu Jan 05, 2017 10:24 am

Re: Service Check works from CLI but not GUI

Post by ahoward12 »

Hey thanks for getting back to me. Ran the the check as nagios and it worked as well.

Code: Select all

[nagios@NAGIOS log]$ /usr/local/nagios/libexec/check_esx3.pl -H "vcsa.cafaroco.com" -f /usr/local/nagiosxi/etc/components/vmware/vcsa_cafaroco_com_auth.txt" -l "VMFS" -s "Prod Servers" -c 5%:
CHECK_ESX3.PL OK - Storages : 'Prod Servers'(free)=439.77 GB (9.34%) | 'Prod Servers'=9.34%;;5:
Now I was just beginning to start another thread when I am thinking I may have coinciding issues. My nagiosxi box itself is "sort of" denying its own service checks.

/var/log/messages shows me this: NAGIOS nagios: SERVICE NOTIFICATION: ahadm;Nagios XI;Memory Usage;CRITICAL;xi_service_notification_handler;(No output on stdout) stderr: connect to address 10.10.99.35 port 5666: Connection refused

and I get a text message every couple of minutes saying the above error. What is weird is I cannot even disable the notifications. It literally just does not let me. I click "disable notifications" and nothing happens. I am not sure if this is interfering with my checks or not.

Code: Select all

[root@NAGIOS log]# /usr/local/nagios/libexec/check_nrpe -H 127.0.0.1
connect to address 127.0.0.1 port 5666: Connection refused
connect to host 127.0.0.1 port 5666: Connection refused
Firewall is disabled [root@NAGIOS log]# service iptables status
iptables: Firewall is not running.


The service seems to be hosed..and I cannot start it. [root@NAGIOS log]# service nrpe status
Checking for nrpe daemon...nrpe dead but subsys locked


I am now down a rabbit hole. I apologize I didn't know this was going to turn into this. I can start another thread if you wish but I would be unwise to say these aren't related in one way or another. Added a picture of the check from ccm.

Here is my nrpe.cfg: (I removed a good bit of lines that were all commented out)

Code: Select all

# LOG FACILITY
# The syslog facility that should be used for logging purposes.

log_facility=daemon



# LOG FILE
# If a log file is specified in this option, nrpe will write to
# that file instead of using syslog.

#log_file=/usr/local/nagios/var/nrpe.log



# 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-privileged 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=10.10.99.35,127.0.0.1,::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=1



# BASH COMMAND SUBSTITUTION
# 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_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.
# If you are using openssl 1.1.0 or above, the SSLv2 options are not available.

#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' for < OpenSSL 1.1.0,
# and 'ssl_cipher_list=ALL:!MD5:@STRENGTH:@SECLEVEL=0' for OpenSSL 1.1.0 and
# greater.

#ssl_cipher_list=ALL:!MD5:@STRENGTH
#ssl_cipher_list=ALL:!MD5:@STRENGTH:@SECLEVEL=0
#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



# NASTY METACHARACTERS
# This option allows you to override the list of characters that cannot
# be passed to the NRPE daemon.

# nasty_metachars="|`&><'\\[]{};\r\n"

# The following examples use hardcoded command arguments...
# This is by far the most secure method of using NRPE

command[check_users]=/usr/local/nagios/libexec/check_users -w 5 -c 10
command[check_load]=/usr/local/nagios/libexec/check_load -r -w .15,.10,.05 -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

# 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=/usr/local/nagios/etc/nrpe
#include_dir=<someotherdirectory>
Let me know how you would like to proceed. Thanks!
You do not have the required permissions to view the files attached to this post.
ahoward12
Posts: 137
Joined: Thu Jan 05, 2017 10:24 am

Re: Service Check works from CLI but not GUI

Post by ahoward12 »

So, from my last post, there were so many minute things going wrong I just rebooted the entire box and everything is working now. Thread can be closed or deleted since it is basically null and void.
User avatar
cdienger
Support Tech
Posts: 5045
Joined: Tue Feb 07, 2017 11:26 am

Re: Service Check works from CLI but not GUI

Post by cdienger »

Reboot to the rescue :)
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Locked