In the Registered Collectors table on the Configuration > Monitoring Collectors > Collectors page, you can see the Opsview version running on each collector.
The version number shown in in the Registered Collectors table is taken from the package version of the
If the Registered Collectors table shows your collector is running an older Opsview version than you expect, you should check each of the below.
Is the collector actually running the expected version?
Are all the Opsview packages on the collector updated for the expected Opsview version?
# Ubuntu/Debian: apt list --installed | grep opsview # CentOS/RHEL: yum list installed | grep opsview
Check the correct expected package versions for your Opsview release on this page.
If the packages do not match those of your expected Opsview release, install the correct packages on the collector using
opsview-scheduler package version match the release version?
The version shown in the Registered Collectors table is taken from the version of the installed
opsview-scheduler package. Some Opsview updates do not affect the
opsview-scheduler package so it may look like your collector has an older version because the
opsview-scheduler package version does not match the release version.
Check the correct expected
opsview-scheduler package version for your Opsview release on this page.
If the correct packages are installed and the version shown in the the Registered Collectors table does not match the installed
opsview-scheduler package, you should try restarting the
- Log in to the affected collector as
- Stop the
/opt/opsview/watchdog/bin/opsview-monit stop opsview-scheduler
- Wait for 60 seconds:
- Start the
/opt/opsview/watchdog/bin/opsview-monit start opsview-scheduler