Opsview Knowledge Center

Known Issues

An overview of the known issues in this release of Opsview Monitor

The following issues have been identified to exist within Opsview Monitor:

Hard-coded database table names

Opsview Monitor 5.4.0 has some hard-coded database table names which will affect any customer that has renamed their Opsview or Runtime databases from the default.. This has been fixed in Opsview Monitor 5.4.1.

After upgrading to Opsview Monitor 5.4.1, the script cleanup_import must be run as the nagios user to ensure the import process can run as expected.

Pause During Upgrade Process

Sometimes the upgrade process can appear to hang with the following message:

[ ok ] Restarting web server: apache2 ... waiting .
Reloading Opsview Watchdog

This will resolve itself if you wait long enough (typically around 10 minutes), but can also be fixed by opening a second session onto the server and running the following command as the "nagios" or "root" user.

pkill -f starman

The upgrade process should then continue within 30 seconds.

Reporting and Chrome Users

There is a known issue with Jasper Reporting for users who are using Chrome and have upgraded from Windows 8 to Windows 10. A workaround for this is to use an alternative supported browser such as IE11 or Firefox.

RPM Upgrade Issues

RPM platforms have been found to hang on upgrade due to an issue with watchdog and the new timeseries packages. In order to resolve this, the upgrade steps in section Upgrading CentOS or RHEL systems to 5.3.x should be followed

Using an exclamation mark in host variable overrides

When using the ! character in host variable overrides you may see an error when the checks are run as scheduled, but works when using 'Troubleshoot'. This is a known problem which can be fixed by putting a \ character before the ! (i.e. it becomes \!)

Known Issues

An overview of the known issues in this release of Opsview Monitor