Opsview Core Utils contains installation scripts (for example, database creation), upgrade scripts, command line tools and cron jobs. It requires opsview-core-libs and includes post install jobs for upgrading.
MariaDB or MySQLserver.
This component is deployed on the Master server when installing Opsview Monitor and must not be moved to another server.
Watchdog service files are now managed by the package manager, removing the package would leave the watchdog service file behind with a .save extension. Purging the package will remove it. The package manager managed config files are as follows
Watchdog service files are now managed by the package manager. When removing the package, if the files listed have been modified by the user before; they will be left behind after rpmsave extension has been added to them. When upgrading the package, if the files listed have been modified by the user before; the modified file on the disk will remain and the new config file from the upgrading package will be written to the disk with the rpmnew extension. Users will have to:
- Manually restore the file with the rpmsave extension.
- Rename the rpmnew to the config file name if they want to use the new config for the package.
As root, start, stop and restart the service using:
/opt/opsview/watchdog/bin/opsview-monit opsviewd <start|stop|restart>