In this section, we describe post-upgrade instructions that are needed to be undertaken following your
Opsview Monitor upgrade.
the Apache configuration
The Apache configuration must be updated
to include Opsview Monitor's authentication ticket configuration to allow single
sign-on. Your Apache files could be located in /etc/httpd/conf.d or /etc/apache2/sites-enabled,
depending on your OS or how you have chosen to configure it. So, you should
manually merge the contents of /usr/local/nagios/installer/apache_proxy.conf
with the current Apache configuration file. Additionally, you should remove all
basic auth configuration since the single sign-on ticket can be used instead.
Now, you need to ensure that you have set
the TKTAuthSecret to match the $authtkt_shared_secret value in
Finally, restart apache.
A lock file, namely
/tmp/opsview4_upgrade_config_generation.lock, will be created as part of the
upgrade. However, this will be removed once Opsview Monitor has been activated and a
‘reload’ has been run. This is required so that you do not lose comments,
downtime or acknowledgements of existing objects. opsview-web will be started,
but pages will link to the activation screen.
Finally, activate your Opsview Monitor system. Note: You
may need to refresh your browser to bring in any new images and, when
activated, you can then reload Opsview Monitor.