Nagios Support Forum

How can we monitor Database (SQL/oracle) from Nagios

Here's the official documentation for monitoring:

• Microsoft SQL Server
• Oracle
• MySQL

I *think* there's also Configuration Wizards within the Nagios XI interface for all of the above.

Thanks for jumping in, Matt! There are indeed wizards for each of those products.

nagedre, do those docs answer your question?

Thanks @mcapra! Always helpful.

That's right, there are several configuration wizards in Nagios XI dedicated to Oracle monitoring. However, you'll need to follow the documentation to install the required dependencies before running.

Let us know if you need any assistance.

Let me go through the Docs mbellerue.
Thanks for sharing

Let me go through the Docs mbellerue.
Thanks for sharing

Sounds good. Just let us know if you need anything.

Hi Benjamin,

I tried to Install & Configure The Oracle Client & Plugins but here Iam struck with the command ./oracleinstall.sh , could you please verify this and updat eme what to do next on this.

root@hpsatvld5302:~ # cd /tmp
root@hpsatvld5302:/tmp # chmod +x oracleinstall.sh
root@hpsatvld5302:/tmp # ./oracleinstall.sh
#######################################
# #
# This is the installer script #
# for installing Oracle monitoring #
# libraries. #
# #
# Before you continue, be sure that #
# the oracle-basic, sqlplus and devel #
# are in the same directory as this #
# installer script. #
# #
#######################################
Loaded plugins: langpacks
UENG.2019.3.0.RHEL | 3.7 kB 00:00:00


One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
root@hpsatvld5302:/tmp #

Hello @nagedre,

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
root@hpsatvld5302:/tmp #

It looks like the server does not have access to the epel repository. Which operating system are you using? You can check which repositories are installed by running the following command in RHEL/CentOS systems. Please post the output for us to review. Thanks.

root@hpsatvld5302:~ # yum repolist -v
Not loading "rhnplugin" plugin, as it is disabled
Loading "langpacks" plugin
Adding en_US.UTF-8 to language list
Config time: 0.008
Yum version: 3.4.3
UENG.2019.3.0.RHEL | 3.7 kB 00:00:00


One of the configured repositories failed (Unknown),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
You have new mail in /var/spool/mail/root
root@hpsatvld5302:~ # date
Wed Nov 6 03:17:11 CST 2019
root@hpsatvld5302:~ #

The output messages suggest that either the server cannot connect to the internet to download other packages needed for the plugin or that the Redhat subscription is not enabled on the server which is causing the packages from downloading.

This message hints to that.
Not loading "rhnplugin" plugin, as it is disabled

You can run this to see if the server's subscription is enabled with Redhat. Subscribe to Redhat as it is needed.

Then clear out the yum cache by running this Try the oracleinstall.sh script again.