Welcome to docs.opsview.com

Upgrading from Opsview Core

Planning your Upgrade

Ensure that you are upgrading to the correct Pro / Enterprise release

Operating System support

Before upgrading please check your Operating System is supported by the latest version of Opview Pro / Enterprise. A list of supported Operating Systems can be found here

For help upgrading from an unsupported Operating System please contact the Opsview Customer Success Team

There are some manual steps required when upgrading from Opsview Core to Opsview Pro or Enterprise

Please be aware of the following:

  • The Opsview server will be made offline during the upgrade

You will need a valid Opsview Subscription before you can upgrade

To use Opsview Pro or Enterprise you will need a valid software key. You will receive your software key from Opsview when you purchase your Opsview subscription.

Please read our documentation on managing your Opsview subscription.

The repository location will be different, so you will need to amend your repository information - see instructions below based on your OS.

If you are planning on using distributed monitoring capabilities, please see our recommended hardware documentation.

Performance considerations relating to the new dashboard capability

Opsview's dashboard capability will potentially increase the quantity of API calls made to the Opsview system and therefore the overall load. On that basis we recommend that you undertake the following planning steps before upgrading your system:

  1. Baseline the performance of your Opsview Master server (and database server, if separate) to establish how well it is currently performing
  2. Read the hardware recommendations, especially in relation to system memory
  3. Decide whether the dashboard will only be adopted by existing Opsview users, or whether it will also be rolled out to new Opsview users. Increasing the number of users will have a proportionate affect on system load.

Please speak to our Support Team if you have any concerns

Upgrading Opsview

Create the Dashboard Database

Opsview 4 uses the new dashboard application, which requires its own database. You need to setup the access to this new database before the upgrade.

You can set a different password by adding below in the /usr/local/nagios/etc/opsview.conf file:

$dashboard_dbpasswd = "changeme";

Setup the credentials for the new database (using the same password as above):

mysql -u root -p<MYSQL ROOT PASSWORD>
mysql> CREATE DATABASE IF NOT EXISTS dashboard;
mysql> GRANT ALL ON dashboard.* TO dashboard@localhost IDENTIFIED BY 'changeme' WITH GRANT OPTION;
mysql> GRANT ALL ON dashboard.* TO dashboard@'%' IDENTIFIED BY 'changeme' WITH GRANT OPTION;

Stop Opsview on the master

su - nagios
/etc/init.d/opsview stop      # Stop Opsview on master

The next steps are based on your OS.

APT for Debian and Ubuntu

Remove Previous Repository Locations

Check /etc/apt/sources.list and all files in /etc/apt/sources.list.d. If there are any links to downloads.opsview.com, these need to be commented out.

You must disable any Opsview Core repositories, otherwise you may have mixed versions of opsview-base and opsview-perl which is unsupported.

Add the New Repository Signature

For security, this repository is gpg signed. Follow our instructions to add the key to your server.

Add the New Repository Location

Use this link below for further instructions on configuring your repo file:

http://docs.opsview.com/doku.php?id=repositories

Updating the Package Lists

When configuration is complete, update the repository information:

apt-get update

Upgrading Opsview

As root, run:

apt-get install opsview

Note: If you have changed your mysql root password, you will need to have it ready as you may be prompted for it.

Note: You may see lots of messages like:

dpkg: warning: unable to delete old directory '/usr/local/nagios/perl/lib/Perl6': Directory not empty

This is due to the relocation of the opsview-perl files. You can ignore these warnings.

Troubleshooting

If you see:

E: The method driver /usr/lib/apt/methods/https could not be found.

This is because the https transport is not available by default. Install it with:

apt-get install apt-transport-https

YUM for CentOS and RHEL

Remove Previous Repository Locations

As Opsview 4 uses a single repository, remove all previous Opsview repository information in /etc/yum.repos.d.

You must disable any Opsview Core repositories, otherwise you may have mixed versions of opsview-base and opsview-perl which is unsupported.

Add the New Repository Location

Create a new file in /etc/yum.repos.d/opsview.repo and add the following lines:

[opsview]
name = Opsview
baseurl = https://<USERNAME>:<PASSWORD>@downloads.opsview.com/opsview-commercial/latest/yum/<DIST>/<OS>/$basearch
enabled = 1
protect = 0
gpgcheck = 0

where:

  • <DIST> is either rhel or centos, depending on your distribution
  • <OS> is either 5 or 6 depending on your version of CentOS or RHEL
  • <USERNAME> and <PASSWORD> are the same credentials that you used to register with http://www.opsview.com

Updating the Package Lists

Update the repository information:

yum clean all
yum makecache

Upgrading Opsview

Upgrade the Opsview packages:

yum install opsview opsview-core opsview-base opsview-perl opsview-web

SLES

Remove Previous Repository Locations

As Opsview 4 uses a single repository, remove all previous repository information in /etc/zypp/repos.d.

You must disable any Opsview Core repositories, otherwise you may have mixed versions of opsview-base and opsview-perl which is unsupported.

Add the New Repository Location

Add the Opsview repository using the zypper command:

zypper addrepo https://<USERNAME>@downloads.opsview.com/opsview-commercial/latest/yum/sles/11/<ARCH> 'Opsview Commercial'

where <ARCH> is one of

  • i386
  • x86_64

and <USERNAME> is your Opsview.com user name.

Updating the Package Lists

Then get the repository information:

zypper refresh

You will be prompted for your password.

If you do not want to keep entering your password when performing zypper operations, you may add your password to the /etc/zypp/repos.d/Opsview Commercial.repo file. Edit the line so it includes your password. For example:

baseurl=https://username:password@downloads.opsview.com/opsview-commercial/latest/yum/sles/11/i386

Upgrading Opsview

Due to limitations in zypper, you cannot upgrade Opsview - you have to remove the previous version and install the newer versions. Because of this, you will also need to run the post upgrade tasks manually:

zypper remove opsview opsview-web opsview-core opsview-base opsview-perl
zypper refresh
zypper install opsview
su - nagios
/usr/local/nagios/installer/upgradedb.pl
/etc/init.d/opsview start
/etc/init.d/opsview-web start

Post Upgrade of Opsview

Security wallet

As of 4.6, users upgrading from Opsview Core will need to manually run:

nagios@ubuntu:~$ rc.opsview gen_config

In order to generate the security wallet database. If this is not done, the 'opsview' daemon will fail to start. You can confirm you are seeing this problem by tailing the nagiosd.log file:

root@ubuntu:/usr/local/nagios/var# tail -n4 nagios.log
[1424170482] opsview_notificationprofiles: OPSVIEW_NOTIFICATIONPROFILES 0.5 Copyright (C) 2003-2014 Opsview Limited. All rights reserved
[1424170482] Event broker module '/usr/local/nagios/bin/opsview_notificationprofiles.o' initialized successfully.
[1424170482] Failed to read Opsview SecureWallet database
[1424170482] Failed to spawn workers. Aborting

To remedy this, do a fullstop on opsview, then kill all opsview processes using the command:

root@ubuntu:/home/sam# pkill -u nagios

This will kill all the scripts such as ndologd, perfrrd, etc. Next, run the 'rc.opsview gen_config' command as the Nagios user. Finally, start the opsview, opsview-web and opsview-agent daemons (in that order). Everything should now spring into life.

Updating Apache Configuration

The Apache configuration must be updated to include Opsview's authentication ticket configuration to allow single sign on.

Your Apache files could be in /etc/httpd/conf.d, /opt/csw/apache2/etc/extra or /etc/apache2/sites-enabled, depending on your OS or how you have configured it.

You should manually merge the contents of /usr/local/nagios/installer/apache_proxy.conf with the current Apache configuration file. You should remove all basic auth configuration, as the single sign on ticket can be used instead.

Ensure you set the TKTAuthSecret to match with the $authtkt_shared_secret value in /usr/local/nagios/etc/opsview.conf.

If you have Nagvis configured to use htpasswd authentication, you will need to change to be based on the authtkt, otherwise the Opsview banner will think that you are not authenticated.

Restart apache.

Reloading

A lock file, /tmp/opsview4_upgrade_config_generation.lock, will be created as part of the upgrade. This will be removed after Opsview has been activated and a reload has been run. This is required so that you do not lose comments, downtimes or acknowledgements of existing objects.

Opsview Web will be started, but all pages will link to the activation screen.

Now you must activate your Opsview system.

Note: You may need to refresh your browser in order to bring in any new images.

When activated, you can then reload Opsview.

Congratulations on upgrading to Opsview 4!

Navigation
Print/export
Toolbox