×
![]()
Back to Opsview FAQ
Nightly Housekeeping kills "Import Runtime"
Problem Copied
The “Opsview - Housekeeping Monitor” service check is in WARNING/CRITICAL state
Related to Copied
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 WARNINGorODW_STATUS CRITICAL
Suggested solution(s) Copied
- 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
| Warning: If the scripts hasn’t run for a long time, you should disable them in crontab before running them manually, then re-enable them after. This prevents duplicate processes while they catch up. - Adding a hash, as per the below will perform this “disable” action |
~]# 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) Copied
- Opsview Data Warehouse (ODW)
- Opsview 6.x Release Notes, Opsview 6.x Known Issues, Upgrade Notes
- Support Policy, Supported Operating Systems
["Geneos"]
["FAQ"]