Page 1 of 1

Monitoring Oracle DB using Nagios XI - error

Posted: Tue Oct 29, 2019 10:44 am
by NMFSTeam
We recently installed the Oracle Client/etc software on our Nagios XI system, so we can monitor our Oracle databases. When trying to use one of the wizards, received the following:

CRITICAL - cannot connect to server1:1521/db1. install_driver(Oracle) failed: Can't load '/usr/local/lib64/perl5/auto/DBD/Oracle/Oracle.so' for module DBD::Oracle: libclntsh.so.18.1: cannot open shared object file: No such file or direct

at (eval 19) line 3
Compilation failed in require at (eval 19) line 3.
Perhaps a required shared library or dll isn't installed where expected
at /usr/local/nagios/libexec/check_oracle_health line 6151

We are running Nagios XI on CentOS 6. We had trouble getting the latest version of the Oracle software working (19.3), so we uninstalled the 19.3 RPMs, and instead used the 18.5 RPMs.

Re: Monitoring Oracle DB using Nagios XI - error

Posted: Tue Oct 29, 2019 1:23 pm
by benjaminsmith
Hello @mblower,

This looks like a path error on the system. Please post the output of the following command.

Code: Select all

cat /usr/local/nagiosxi/etc/configwizards/oracle/oracle
Also, we have some troubleshooting tips ( See Common Problems) in the documentation.

How To Install & Configure The Oracle Client & Plugins

Re: Monitoring Oracle DB using Nagios XI - error

Posted: Tue Oct 29, 2019 4:56 pm
by NMFSTeam
That file had the wrong path, it had 19.3, which was removed during troubleshooting, and 18.5 was installed instead. I have updated the file. Do I need to restart Nagios or anything to have the change go in to effect?

Thanks.

Re: Monitoring Oracle DB using Nagios XI - error

Posted: Tue Oct 29, 2019 5:48 pm
by NMFSTeam
Looks like I spoke too soon, it's working now (sort of). We must have a firewall issue, because now it is saying it can't connect. I think you can close this issue, thank you for the help.

Re: Monitoring Oracle DB using Nagios XI - error

Posted: Wed Oct 30, 2019 9:18 am
by benjaminsmith
. I think you can close this issue, thank you for the help.
No problem. Good to hear it's working now.