Welcome to docs.opsview.com

Upgrading your Opsview System

This document covers upgrades from both Opsview Community 3.x and Opsview Enterprise 3.x

Planning your Upgrade

There are some manual steps required when upgrading from Opsview 3 to Opsview 4

Please be aware of the following:

  • You must install/upgrade the opsview-slave package on all Opsview slaves
  • You must upgrade all Opsview Modules to the latest version as part of your Opsview upgrade
  • The master will be made offline during the upgrade
  • Databases will be upgraded as usual
  • Opsview software will be automatically sent to slaves as usual
  • The upgrade will not do a reload of Opsview configuration automatically - you need to do this after activation
  • After the upgrade, Opsview will start monitoring with the previous configuration. Slaves will not be able to send results back to the master until an Opsview reload has been run
  • Opsview Web will not display any pages until activation is complete
  • After activation, you should initiate an Opsview reload. Connectivity to slaves will be re-established automatically

Bringing your Opsview software up to date

Enterprise Edition

If you are running a version of Opsview Enterprise older than 3.14.1 then we recommend that you upgrade to this release first, before upgrading to Opsview 4.

Community Edition

If you are running a version of Opsview Community older than 3.20120424, then contact us to help with upgrading.

You will need a valid Opsview Subscription before you can upgrade

To use Opsview 4 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.

Please ensure that the features provided by your Opsview 4 subscription match or exceed your current system, otherwise you will lose access to certain capabilities.

Feature What will happen if your subscription does not include a previously utilised feature
Hosts Limit Reload will fail with an error message
Data Warehouse The hourly imports will be quietly suppressed. As long as the feature is enabled within the next 7 days, imports will run and the availability and performance data will catchup
Distributed Monitoring Hosts and services monitored by the slave will not be enabled for monitoring. Downtimes, acknowledgements and comments associated to the host and services will be discarded
Slave Server Clustering Hosts and services monitored by this slave cluster will not be enabled for monitoring. Downtimes, acknowledgements and comments associated to the host and services will be discarded. If you have Distributed Monitoring, then you can manually split your cluster
SNMP Trap Processing SNMP traps will not be processed by Opsview on the master nor the slave

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

The minimum hardware requirements have increased, partly due to using prefork mode by default for Opsview Web. 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 for Opsview 4, 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 a new 'Dashboard' application, which uses its own database. This new database can be set up prior to the upgrade, otherwise the installation will create the database on the Opsview master server.

Decide on a password for the Dashboard database.

Set up the credentials for the new database, using the new password:

$ mysql -u root -p<MySQL root password>
mysql> CREATE DATABASE IF NOT EXISTS dashboard;
mysql> GRANT ALL ON dashboard.* TO dashboard@localhost IDENTIFIED BY '<Dashboard password>' WITH GRANT OPTION;
mysql> GRANT ALL ON dashboard.* TO dashboard@'%' IDENTIFIED BY '<Dashboard password>' WITH GRANT OPTION;

Enter the password into /usr/local/nagios/etc/opsview.conf:

$dashboard_dbpasswd = '<Dashboard password>';

Alternatively, one can put the Dashboard database on a remote server. In this case, configure access on it, as above, and enter the location of the database into /usr/local/nagios/etc/opsview.conf, like so:

$dashboard_dbhost = '192.168.11.65';
$dashboard_dbuser = 'dashboard';
$dashboard_dbpasswd = '<Dashboard password>';
$dashboard_db = 'dashboard';  
$dashboard_dbi = 'dbi:mysql';

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.

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

Edit the file /etc/apt/sources.list (or create a new file /etc/apt/sources.list.d/opsview.list)

Use this link below for further instructions: 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:

Removing libapache2-mod-auth-tkt-prefork ...
Action 'configtest' failed.
The Apache error log may have more information.
Your apache2 configuration is broken, so we're not restarting it for you.

This means that the previous package is being removed so Apache configurations including the AuthTkt will be invalid. However, Opsview will automatically install libapache2-mod-auth-tkt-prefork-opsview which provides the same capabilities so Apache will restart correctly afterwards.

If you see:

dpkg: warning: unable to delete old directory '/usr/local/nagios/perl/lib/Locale/Maketext/Extract/Plugin': Directory not empty

These can be ignored, as the new opsview-perl packages will relocate perl modules to /opt/opsview/perl. There maybe a lot of these messages but it is safe to ignore.

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.

Add the New Repository Location

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

Use this link below for further instructions: http://docs.opsview.com/doku.php?id=repositories

Updating the Package Lists

Update the repository information:

yum clean all
yum makecache

Upgrading Opsview

Upgrade the Opsview packages:

yum upgrade 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.

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 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

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 your OS and 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.

Activation and 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 the new images.

Congratulations on upgrading to Opsview 4!

Upgrading of Modules

The following modules must be upgraded:

Module Package name
Reports module opsview-reporting-module
Service Desk Connector module opsview-servicedesk-connector
Netaudit module opsview-rancid

There are no repository changes as all the software are now in the same repository as Opsview 4. You can upgrade via your OS package methods.

Navigation
Print/export
Toolbox