Problem:

The "Opsview - Housekeeping Monitor" service check is in WARNING/CRITICAL state 

Related to:

Nightly housekeeping of the Opsview databases is controlled by a cronjob that runs at 0311 (server time) under the "opsview" on the orchestrator. 

If you are seeing that the import_runtime (ODW Status) or "Opsview Housekeeping Status" service check is failing failing, then it may well be a conflict (database deadlock) between these two processes.

Example of errors seen

• Import Runtime Error: [FATAL] There are running dataloads - exiting
• ODW service check goes into non-OK state: ODW_STATUS WARNING or ODW_STATUS CRITICAL

Suggested solution(s):

• Update the opsview users cronjob for import_runtime to exclude (skip) 0304 
• For the purpose of this information, only the import_runtime cronjob is shown with the "-eu" command below, but there are many others within that output

~]# crontab -eu opsview
...
# 4 * * * * . /opt/opsview/coreutils/bin/profile && /opt/opsview/coreutils/bin/import_runtime -q
...

To implement the suggested solution update cronjob entry as per the below (0-2,5-23)

• Modify Import Runtime Crontab for Opsview

# crontab -eu opsview
4 0-2,4-23 * * * . /opt/opsview/coreutils/bin/profile && /opt/opsview/coreutils/bin/import_runtime -q

Related article(s):

• Opsview Data Warehouse (ODW)
• Opsview 6.x Release Notes, Opsview 6.x Known Issues, Upgrade Notes
• Support Policy, Supported Operating Systems

If you need further help:

• Please contact our support team via the chat service box on any of our websites or raise a support request.
  
• Make sure you provide us with:
  • Background of the issue or request.
  • Use cases, requirements, business impact, etc.
  • Encountered error messages.
  • Log files or diagnostic files.
  • Screenshots.
  • And other important information relevant to your inquiry.