Oracle Database monitoring

An open discussion forum for obtaining help with Nagios Core. Nagios Core users of all experience levels are welcome here. Subforum have been created for the discussion of Nagios Core and Nagios Plugin development.

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

Re: Oracle Database monitoring

Postby spatil32 » Fri Nov 22, 2019 4:23 am

Hi,

Thanks for reply.
I have changed the ownership of check_oracle file on Remote linux server to nagios:nagios. Please find below nrep.cfg file of Remote linux server. do i need to add check_oracle command in commands.cfg file. Can you provide the format.

nrpe.cfg file:

# 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/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,10.211.51.106



# 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_users]=/usr/local/nagios/libexec/check_users -w 5 -c 10
command[check_load]=/usr/local/nagios/libexec/check_load -w 5,5,5 -c 8,8,8
command[check_disk]=/usr/local/nagios/libexec/check_disk -w 20% -c 10% -p /*
command[check_swap]=/usr/local/nagios/libexec/check_swap -w 20 -c 10
command[check_oracle_pmon]=/usr/local/nagios/libexec/check_oracle --db SID
spatil32
 
Posts: 13
Joined: Fri Aug 23, 2019 6:37 am

Re: Oracle Database monitoring

Postby benjaminsmith » Fri Nov 22, 2019 5:23 pm

Hello,

That looks good. Did you restart the nrpe service on the remote host? What happens when you run the check command line on the Nagios server? Can you post the output error for us to review?
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
benjaminsmith
 
Posts: 1955
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: Oracle Database monitoring

Postby benjaminsmith » Fri Nov 22, 2019 5:43 pm

Hi @spatil32

Just like to add one more thing to verify on the remote host.

Let's run check command defined in your NRPE configuration file as nagios user on the remote host and if this is successful, then test from the Nagios server.

Code: Select all
su - nagios
/usr/local/nagios/libexec/check_oracle --db SID
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
benjaminsmith
 
Posts: 1955
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: Oracle Database monitoring

Postby spatil32 » Mon Nov 25, 2019 6:33 am

Hi,

Thanks for the reply.
I have logged in as nagios user and able to successfully run the check_oracle command on Remote Linux machine.
Only thing now remain is to restart nrpe on Remote linux machine.

I am hesitating to restart nrpe because it is running under xinetd so checking with the Unix team on this.
Will keep you updated.

Regards
SagarP
spatil32
 
Posts: 13
Joined: Fri Aug 23, 2019 6:37 am

Re: Oracle Database monitoring

Postby benjaminsmith » Mon Nov 25, 2019 3:31 pm

Hello SagarP,

Sounds good. We'll keep this open while we wait for your update.
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
benjaminsmith
 
Posts: 1955
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: Oracle Database monitoring

Postby spatil32 » Thu Nov 28, 2019 3:08 am

Hi Benjamin,

I have restarted the nrpe service on Remote Oracle server but still the same error

NRPE: Command 'command_name' not defined

I am sure this is something small which I am missing but not sure what it is . Kindly help to resolve this issue.

Thanks

SagarP
spatil32
 
Posts: 13
Joined: Fri Aug 23, 2019 6:37 am

Re: Oracle Database monitoring

Postby spatil32 » Thu Nov 28, 2019 8:58 am

hi,

Just when i checked, i found these many nrpe.cfg on the remote oracle server. How to find which one is used by Nagios server.

/install/nagios/Nagios64/etc/nrpe.cfg
/install/nagios/nrpe-2.8/sample-config/nrpe.cfg
/install/nagios/nrpe-2.8/sample-config/nrpe.cfg.in
/usr/local/nagios/etc/nrpe.cfg
/usr/local/nagios/etc/nrpe.cfg.save

Thanks

regards
SagarP
spatil32
 
Posts: 13
Joined: Fri Aug 23, 2019 6:37 am

Re: Oracle Database monitoring

Postby spatil32 » Fri Nov 29, 2019 6:57 am

Hi,

Can someone please check as I need to deploy this in production.
I have now reinstall nrpe agent on the remote oracle server but still gets the same error when check oracle status from Nagios server i.e

NRPE: Command 'command name' not defined.

Thanks.

regards
SagarP
spatil32
 
Posts: 13
Joined: Fri Aug 23, 2019 6:37 am

Re: Oracle Database monitoring

Postby benjaminsmith » Mon Dec 02, 2019 4:18 pm

Hi @SagarP,

Are you certain that you have modified the correct nrpe.cfg file (include_dir=/usr/local/nagios/etc/nrpe) ?

Are you able to run one of the other commands such as check_load or check_users successfully from 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
benjaminsmith
 
Posts: 1955
Joined: Wed Aug 22, 2018 4:39 pm
Location: saint paul

Re: Oracle Database monitoring

Postby spatil32 » Tue Dec 03, 2019 9:33 am

Hi Benjamin,

Issue finally got resolved. When xinetd was stop, I observed that nrpe process was still running. so I kill the nrpe process and started the xinetd service. Then the communication was OK from Nagios server.

Thanks for support. :)

Regards
SagarP
spatil32
 
Posts: 13
Joined: Fri Aug 23, 2019 6:37 am

PreviousNext

Return to Nagios Core

Who is online

Users browsing this forum: Google [Bot] and 13 guests

cron