Having problems with check_oracle_health

[mohan23]

Hi,

We have some severe problems with check_oracle_health especially with tablespace checks .We have recently upgraded oracle plugin to 3.2.2

[nagios@nagios var]$ /usr/bin/env LD_LIBRARY_PATH=/usr/lib/oracle/12.2/client64/lib ORACLE_HOME=/usr/lib/oracle/12.2/client64 /usr/local/nagios/libexec/check_oracle_health --connect 'ip address:1521/Instance name' --username 'xxxxxx' --password 'xxxxx' --mode tablespace-usage --name DBATOOLS --warning 85 --critical 90 --timeout 600
UNKNOWN - check_oracle_health timed out after 600 seconds
can some one help me to fix this?

[tgriep]

What was the version of the old plugin before the upgrade.
Did you typo the version number in the post.
The latest version is 3.1.2.2, can you verify that?


Did the old version of the plugin work for this check?

Quick thing to try, the plugin stores some temporary files when it runs so delete them and see if the plugin works.
Delete all of the files in this folder.

Code: Select all

/var/tmp/check_oracle_health

[mohan23]

Here is the version output

[nagios@nagioshost tmp]$ /usr/local/nagios/libexec/check_oracle_health -V
check_oracle_health (3.1.2.2)
This nagios plugin comes with ABSOLUTELY NO WARRANTY. You may redistribute
copies of this plugin under the terms of the GNU General Public License.
[nagios@lxappnagprd006 tmp]$

its almost taking more than 700 seconds to get table space check output, but global nagiosxi timeout is 120 seconds, can I increase nagiosxi global xi timeout to 700 or 800 seconds, if I increase nagiosxi global timeout to 800 seconds, is there any impact for all other service checks or to nagios.

[mcapra]

check_oracle_health can have excessively long runtimes. Historically, the recommendation to alleviate the problems you're facing has been to run this as a passive check:
https://support.nagios.com/forum/viewto ... 5&p=251254
https://support.nagios.com/forum/viewto ... 3&p=227255

For checks that run significantly longer than others, it's often best to break them out of the Nagios process rather than to change your main Nagios configs to accommodate the outlier(s).

More info on passive checks:
https://assets.nagios.com/downloads/nag ... ios-XI.pdf
https://assets.nagios.com/downloads/nag ... hecks.html

[lmiltchev]

Thank you, @mcapra!

@mohan23, let us know if using passive checks solves your issue.