Service check timed out after 60.01 seconds
Posted: Wed Oct 10, 2018 5:18 pm
Hi Team,
Intermittently command check_oracle_health is throwing "Service check timed out after 60.01 seconds" error.
This could be happening because Oracle database is on high load and might be taking more than a minutes to respond to tablespace check query. I read in some forums and added "-t 300" to the command but we are still getting time outs in 1 minute.
- How to increase the timeout interval?
- How do we avoid getting alerts for timeout? We have a pooling cycle of 10 minutes and if issue persists for 10 minutes only than we need to receive alerts. But this case, alert comes in 1 minute and it's not a genuine alert too.
/usr/bin/env LD_LIBRARY_PATH=/usr/lib/oracle/12.1/client64/lib ORACLE_HOME=/usr/lib/oracle/12.1/client64 $USER1$/check_oracle_health $ARG1$
Where ARG1 is
-t 300 --connect 'XXXXXXX' --username 'nagios' --password 'XXXXXX' --mode tablespace-usage --warning 80 --critical 90
Intermittently command check_oracle_health is throwing "Service check timed out after 60.01 seconds" error.
This could be happening because Oracle database is on high load and might be taking more than a minutes to respond to tablespace check query. I read in some forums and added "-t 300" to the command but we are still getting time outs in 1 minute.
- How to increase the timeout interval?
- How do we avoid getting alerts for timeout? We have a pooling cycle of 10 minutes and if issue persists for 10 minutes only than we need to receive alerts. But this case, alert comes in 1 minute and it's not a genuine alert too.
/usr/bin/env LD_LIBRARY_PATH=/usr/lib/oracle/12.1/client64/lib ORACLE_HOME=/usr/lib/oracle/12.1/client64 $USER1$/check_oracle_health $ARG1$
Where ARG1 is
-t 300 --connect 'XXXXXXX' --username 'nagios' --password 'XXXXXX' --mode tablespace-usage --warning 80 --critical 90