Service check based on check_modbus_fast_drycontact3 change to CRITICAL with status (null)
Problem
After changing the configuration or rebooting the SONARPLEX all service checks based on check_modbus_fast_drycontact3 change to CRITICAL with status (null)
Solution
One of these service checks may have Active Checks Enabled, you must first find out which ones do, change those and finally delete the old status to force a new execution for all drycontact checks.
Open your browser and access https://example.com:444/v1/*/local/services/?fields=checks_enabled,check_command (change accordingly to your environment)
The RESTFul API is only accessible with user admin and via the Administration Web Interface
- Now search for check_modbus_fast_drycontact3 and check if for all found services the check_enabled is set to 0
- Change the configuration (e.g. use SONARMANAGER) of all services where check_enabled was set to 1 and disable active service checks
Next you must delete the retention data which clears out old 'cached' status information and enables a fresh start for every service check.
Deleting the retention file leads to a flush of all status information, this will set every host and service object into state PENDING. This is expected and the objects will be checked during the normal check intervals and return into a non-PENDING state.
Deleting the retention file:
- Open the Administration Web Interface > Status > Monitor
- Choose
Delete state retention file (read online help before using), the Monitor process will be restarted automatically
The Monitor process and the MODBUS Daemon is restarted afterwards automatically.
Related articles
- style