Code: Select all
su nagios
/usr/lccal/nagios/libexec/check_ifx.sh /usr/informix hueynetNeed to Monitor Informix
Re: Need to Monitor Informix
Does the plugin work when you run it locally on 192.168.1.42? Can you run it as nagios user?
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
donnyforbes
- Posts: 357
- Joined: Tue Jun 13, 2017 2:17 pm
Re: Need to Monitor Informix
yes see below.
Code: Select all
[root@huey libexec]# ./check_ifx.sh /usr/informix hueynet
IBM Informix Dynamic Server Version 12.10.FC8W2WE -- On-Line (Prim) -- Up 05:54:29 -- 1034088 Kbytes
[root@huey libexec]#
Re: Need to Monitor Informix
You are running it as "root". Can you run it as nagios user?
Code: Select all
su nagios
/usr/local/nagios/libexec/check_ifx.sh /usr/informix hueynetBe sure to check out our Knowledgebase for helpful articles and solutions!
-
donnyforbes
- Posts: 357
- Joined: Tue Jun 13, 2017 2:17 pm
Re: Need to Monitor Informix
Here is the output...
In the XI I still see this? Why is that?
Code: Select all
[nagios@huey libexec]$ /usr/local/nagios/libexec/check_ifx.sh /usr/informix hueynet
IBM Informix Dynamic Server Version 12.10.FC8W2WE -- On-Line (Prim) -- Up 1 days 04:30:03 -- 1034088 Kbytes
You do not have the required permissions to view the files attached to this post.
Re: Need to Monitor Informix
Could you post the full nrpe.cfg file from the remote server so we can see all of the settings for the NRPE Agent?
Then, login to the XI GUI and go to the Core Config Manager Services menu, search for that check and when you find it, click on the floppy icon to view it's config and post that here as well.
Then, login to the XI GUI and go to the Core Config Manager Services menu, search for that check and when you find it, click on the floppy icon to view it's config and post that here as well.
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
donnyforbes
- Posts: 357
- Joined: Tue Jun 13, 2017 2:17 pm
Re: Need to Monitor Informix
nrpe.cfg
XI config file you have requested.
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.
#
# 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
# 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 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=/usr/local/nagios/etc/nrpe
# 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
# 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$ #command[check_informix]=/usr/local/nagios/libexec/check_informix.sh
command[check_http]=/usr/local/nagios/libexec/check_http
command[check_ifx]=/usr/lccal/nagios/libexec/check_ifx.sh $ARG1$
Code: Select all
###############################################################################
#
# Service configuration file
#
# Created by: Nagios Core Config Manager 2.6.7
# Date: 2017-07-12 08:53:28
# Version: Nagios 3.x config file
#
# --- DO NOT EDIT THIS FILE BY HAND ---
# Nagios CCM will overwrite all manual settings during the next update if you
# would like to edit files manually, place them in the 'static' directory or
# import your configs into the CCM by placing them in the 'import' directory.
#
###############################################################################
define service {
host_name huey.sg1.allamericanasphalt.com
service_description / Disk Usage
use xiwizard_nrpe_service
check_command check_nrpe!check_disk!-a '-w 20% -c 10% -p /'
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contacts nagiosadmin
_xiwizard linux-server
register 1
}
define service {
host_name huey.sg1.allamericanasphalt.com
service_description CPU Stats
use xiwizard_nrpe_service
check_command check_nrpe!check_cpu_stats!-a '-w 85 -c 95'
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contacts nagiosadmin
_xiwizard linux-server
register 1
}
define service {
host_name huey.sg1.allamericanasphalt.com
service_description infx online
use xiwizard_nrpe_service
display_name Infx
check_command check_nrpe!check_ifx!-a '/usr/informix hueynet'!!!!!!
initial_state c
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
notifications_enabled 1
contacts nagiosadmin
register 1
}
define service {
host_name huey.sg1.allamericanasphalt.com
service_description Load
use xiwizard_nrpe_service
check_command check_nrpe!check_load!-a '-w 15,10,5 -c 30,20,10'
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contacts nagiosadmin
_xiwizard linux-server
register 1
}
define service {
host_name huey.sg1.allamericanasphalt.com
service_description Memory Usage
use xiwizard_nrpe_service
check_command check_nrpe!check_mem!-a '-w 20 -c 10'
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contacts nagiosadmin
_xiwizard linux-server
register 1
}
define service {
host_name huey.sg1.allamericanasphalt.com
service_description Ping
use xiwizard_linuxserver_ping_service
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contacts nagiosadmin
_xiwizard linux-server
register 1
}
define service {
host_name huey.sg1.allamericanasphalt.com
service_description Service Status - OAT
use xiwizard_nrpe_service
display_name Infx
check_command check_http!!!!!!!!
initial_state c
max_check_attempts 5
check_interval 5
retry_interval 1
notification_interval 60
notification_period xi_timeperiod_24x7
notifications_enabled 1
contacts nagiosadmin
register 1
}
define service {
host_name huey.sg1.allamericanasphalt.com
service_description Swap Usage
use xiwizard_nrpe_service
check_command check_nrpe!check_swap!-a '-w 50% -c 20%'
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contacts nagiosadmin
_xiwizard linux-server
register 1
}
define service {
host_name huey.sg1.allamericanasphalt.com
service_description Users
use xiwizard_nrpe_service
check_command check_nrpe!check_users!-a '-w 5 -c 10'
max_check_attempts 5
check_interval 5
retry_interval 1
check_period xi_timeperiod_24x7
notification_interval 60
notification_period xi_timeperiod_24x7
contacts nagiosadmin
_xiwizard linux-server
register 1
}
###############################################################################
#
# Service configuration file
#
# END OF FILE
#
###############################################################################Re: Need to Monitor Informix
You are passing 2 arguments from the XI system but the NRPE Agent is setup for only one argument.
Edit the nrpe.cfg file and change the command from
to
Save the file and either restart xinetd or the NRPE daemon for the changes to take effect.
Edit the nrpe.cfg file and change the command from
Code: Select all
command[check_ifx]=/usr/lccal/nagios/libexec/check_ifx.sh $ARG1$Code: Select all
command[check_ifx]=/usr/lccal/nagios/libexec/check_ifx.sh $ARG1$ $ARG2$Be sure to check out our Knowledgebase for helpful articles and solutions!
-
donnyforbes
- Posts: 357
- Joined: Tue Jun 13, 2017 2:17 pm
Re: Need to Monitor Informix
did the following
sevice xinetd restart & service nrpe restart still seeing this below... Not sure if I am missing something or not.
Code: Select all
# 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$ #command[check_informix]=/usr/local/nagios/libexec/check_informix.sh
command[check_http]=/usr/local/nagios/libexec/check_http
command[check_ifx]=/usr/lccal/nagios/libexec/check_ifx.sh $ARG1$ $ARG2$
You do not have the required permissions to view the files attached to this post.
Re: Need to Monitor Informix
Login to the remote host and check the /var/log/messages file for any errors when the check it run and post the output here if you find any.
Then, run the following commands on the Nagios server and post the output.
Then, run the following commands on the Nagios server and post the output.
Code: Select all
/usr/local/nagios/libexec/check_nrpe -H huey.sg1.allamericanasphalt.com
/usr/local/nagios/libexec/check_nrpe -H huey.sg1.allamericanasphalt.com -c check_ifx
/usr/local/nagios/libexec/check_nrpe -H huey.sg1.allamericanasphalt.com -c check_ifx -a '/usr/informix hueynet'
/usr/local/nagios/libexec/check_nrpe -H huey.sg1.allamericanasphalt.com -c check_ifx -a /usr/informix hueynetBe sure to check out our Knowledgebase for helpful articles and solutions!
-
donnyforbes
- Posts: 357
- Joined: Tue Jun 13, 2017 2:17 pm
Re: Need to Monitor Informix
Output from the commands i ran as root and also tried as user nagios and got the same output.
From remote host
tail -f /var/log/messages
Code: Select all
[root@nag ~]# /usr/local/nagios/libexec/check_nrpe -H huey.sg1.allamericanasphalt.com
NRPE v2.15
[root@nag ~]# /usr/local/nagios/libexec/check_nrpe -H huey.sg1.allamericanasphalt.com -c check_ifx
NRPE: Unable to read output
[root@nag ~]# /usr/local/nagios/libexec/check_nrpe -H huey.sg1.allamericanasphalt.com -c check_ifx -a '/usr/informix hueynet'
NRPE: Unable to read output
[root@nag ~]# /usr/local/nagios/libexec/check_nrpe -H huey.sg1.allamericanasphalt.com -c check_ifx -a /usr/informix hueynet
NRPE: Unable to read output
tail -f /var/log/messages
Code: Select all
[root@huey etc]# tail -f /var/log/messages
Jul 12 10:30:01 huey systemd: Started Session 2613 of user root.
Jul 12 10:30:01 huey systemd: Starting Session 2613 of user root.
Jul 12 10:30:01 huey systemd: Started Session 2615 of user root.
Jul 12 10:30:01 huey systemd: Starting Session 2615 of user root.
Jul 12 10:30:01 huey systemd: Started Session 2612 of user root.
Jul 12 10:30:01 huey systemd: Starting Session 2612 of user root.
Jul 12 10:30:14 huey xinetd[21902]: START: nrpe pid=49724 from=::ffff:192.168.1.186
Jul 12 10:30:14 huey xinetd[21902]: EXIT: nrpe status=0 pid=49724 duration=0(sec)
Jul 12 10:30:29 huey xinetd[21902]: START: nrpe pid=50297 from=::ffff:192.168.1.186
Jul 12 10:30:30 huey xinetd[21902]: EXIT: nrpe status=0 pid=50297 duration=1(sec)
Jul 12 10:31:59 huey xinetd[21902]: START: nrpe pid=51765 from=::ffff:192.168.1.186
Jul 12 10:31:59 huey xinetd[21902]: EXIT: nrpe status=0 pid=51765 duration=0(sec)
Jul 12 10:32:24 huey xinetd[21902]: START: nrpe pid=52219 from=::ffff:192.168.1.186
Jul 12 10:32:24 huey xinetd[21902]: EXIT: nrpe status=0 pid=52219 duration=0(sec)
Jul 12 10:32:47 huey xinetd[21902]: START: nrpe pid=52258 from=::ffff:192.168.1.186
Jul 12 10:32:48 huey xinetd[21902]: EXIT: nrpe status=0 pid=52258 duration=1(sec)
Jul 12 10:33:04 huey xinetd[21902]: START: nrpe pid=52749 from=::ffff:192.168.1.186
Jul 12 10:33:05 huey xinetd[21902]: EXIT: nrpe status=0 pid=52749 duration=1(sec)
Jul 12 10:33:28 huey xinetd[21902]: START: nrpe pid=53203 from=::ffff:192.168.1.186
Jul 12 10:33:28 huey xinetd[21902]: EXIT: nrpe status=0 pid=53203 duration=0(sec)
Jul 12 10:33:30 huey xinetd[21902]: START: nrpe pid=53204 from=::ffff:192.168.1.186
Jul 12 10:33:31 huey xinetd[21902]: EXIT: nrpe status=0 pid=53204 duration=1(sec)
Jul 12 10:33:33 huey xinetd[21902]: START: nrpe pid=53208 from=::ffff:192.168.1.186
Jul 12 10:33:33 huey xinetd[21902]: EXIT: nrpe status=0 pid=53208 duration=0(sec)
Jul 12 10:33:38 huey xinetd[21902]: START: nrpe pid=53247 from=::ffff:192.168.1.186
Jul 12 10:33:38 huey xinetd[21902]: EXIT: nrpe status=0 pid=53247 duration=0(sec)
Jul 12 10:33:43 huey xinetd[21902]: START: nrpe pid=53250 from=::ffff:192.168.1.186
Jul 12 10:33:43 huey xinetd[21902]: EXIT: nrpe status=0 pid=53250 duration=0(sec)
Jul 12 10:34:14 huey xinetd[21902]: START: nrpe pid=53741 from=::ffff:192.168.1.186
Jul 12 10:34:15 huey xinetd[21902]: EXIT: nrpe status=0 pid=53741 duration=1(sec)
Jul 12 10:34:47 huey xinetd[21902]: START: nrpe pid=54231 from=::ffff:192.168.1.186
Jul 12 10:34:51 huey xinetd[21902]: START: nrpe pid=54241 from=::ffff:192.168.1.186
Jul 12 10:34:51 huey xinetd[21902]: EXIT: nrpe status=0 pid=54241 duration=0(sec)
Jul 12 10:34:52 huey xinetd[21902]: EXIT: nrpe status=0 pid=54231 duration=5(sec)