Opsview Knowledge Center

Unknown and Stale Check Results

Resolve your Unknown and Stale Check Results with Opsview Monitor

Unknown/Stale Check Results

This occurs in a distributed environment if an Opsview Monitor Slave server has not sent results back to the Opsview Monitor Master server for longer than 30 minutes.

An Opsview Monitor Slave server problem should be alerted via the check_opsview_slave plugin. But if it is not resolved, then services monitored by this Opsview Monitor Slave server will start to go into UNKNOWN states after 30 minutes.

Note: The host will not be set into an UNKNOWN state.

If this situation occurs, it may be that:

  • The SSH connection from slave to master has failed and needs to be restarted by killing the process
  • Multiple Opsview Monitor Master servers are trying to connect to the same slave, e.g when Opsview is being used in a Disaster Recovery of High Availability configuration
  • The NRD process is not running on the master (only if all slaves are affected)
  • The Opsview Monitor Slave server has very high latency - check nagios.log and nagiostats output on the Opsview Monitor Slave server for the Active Service Latency values
  • Time is not synchronized between the master and slave. When you submit a result, there is a time associated with it. If the Opsview Monitor Slave server is ahead of time for the Opsview Monitor Master server, then the Opsview Monitor Slave server will mark the result back in time and then the Opsview Monitor Slave server will immediately mark it as stale.

Unknown and Stale Check Results

Resolve your Unknown and Stale Check Results with Opsview Monitor