Welcome to docs.opsview.com

Upgrading from Opsview Community

The following process outlines the steps for upgrading your Opsview Community system to Opsview Core.

Package version numbers for opsview-core and opsview-web will be of the form 3.YYYYMMDD.0.Z, but opsview-base and opsview-perl will be 4.X.Y.Z.

Planning your Upgrade

Hardware Requirements

The minimum hardware requirements have increased, partly due to using prefork mode by default for Opsview Web. See our recommended hardware documentation.

Bringing your Opsview software up to date

We recommend that you upgrade to Opsview Community 20120424 first, before upgrading to Opsview Core.

Features No Longer Available

Opsview Core has a different feature set to Opsview Community. If you want to retain the full feature set then we recommend that you upgrade to Opsview Pro or Opsview Enterprise.

Features no longer available with Opsview Core:
Feature Actions to remove feature usage
Data Warehouse (ODW) In System Preferences page: Select ODW tab and disable ODW import process
Distributed Monitoring In Monitoring Servers list page: Delete all slave systems
SNMP Trap Processing In Service Checks list page: Search for SNMP Traps and delete each service check with SNMP Trap processing. You will also need to reconfigure SNMP to not run the snmptrap2nagios script
Database on a Separate Server It is necessary to migrate the following databases back to the Opsview master server: Opsview and Runtime

Before you upgrade your system you must change your Opsview configuration so that these features are not in use. Otherwise the upgrade will fail.

You must install the opsview-compatibility-check package to ensure that your system is ready to accept Opsview Core. This is a manual step for Centos5, RHEL5, SLES11 and Solaris - please check the instructions below carefully.

Upgrading Opsview

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) and add the following line to it:

# Opsview packages
deb http://downloads.opsview.com/opsview-core/latest/apt <OS> main

Where:

  • OS is your distribution name, such as squeeze, lucid or hardy

For example:

deb http://downloads.opsview.com/opsview-core/latest/apt squeeze main

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.

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.

YUM for CentOS and RHEL

Remove Previous Repository Locations

As Opsview Core uses a new repository location, 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:

[opsview]
name = Opsview
baseurl = http://downloads.opsview.com/opsview-core/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

Updating the Package Lists

Update the repository information:

sudo yum clean all
sudo yum makecache

Install the Opsview Compatibility Check

Install the Opsview Compatibility Check, which will confirm that your existing system is ready to accept Opsview Core:

sudo yum install opsview-compatibility-check

If there are incompatibilities with the new Core software, you will need to resolve the configuration.

Upgrading Opsview

Upgrade the Opsview packages:

sudo yum install opsview opsview-core opsview-base opsview-perl opsview-web opsview-compatibility-check

SLES

Remove Previous Repository Locations

As Opsview Core uses a new 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 http://downloads.opsview.com/opsview-core/latest/yum/sles/11/<ARCH> 'Opsview'

where <ARCH> is one of

  • i386
  • x86_64

Updating the Package Lists

Then get the repository information:

zypper refresh

Install the Opsview Compatibility Check

Install the Opsview Compatibility Check, which will confirm that your existing system is ready to accept Opsview Core:

zypper install opsview-compatibility-check

If there are incompatibilities with the new Core software, you will need to resolve the configuration.

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 database upgrade tasks manually:

zypper remove opsview opsview-web opsview-core opsview-base opsview-perl
zypper install opsview
su - nagios -c /usr/local/nagios/installer/upgradedb.pl

Solaris

Retrieving the Packages

Download the packages below from http://downloads.opsview.com/opsview-core/latest/solaris/sol10n/<ARCH>

where <ARCH> is either amd64 or i386 depending on the architecture of your server.

Install the Opsview Compatibility Check

Install the Opsview Compatibility Check, which will confirm that your existing system is ready to accept Opsview Core:

pkgadd -d /path/to/package/opsview-compatibility-check*.pkg

If there are incompatibilities with the new Core software, you will need to resolve the configuration.

Upgrading Opsview

You will need to remove all the current packages and then install the new ones.

The correct order to remove the packages, using pkgrm, is:

  1. ALTovweb
  2. ALTovcore
  3. ALTovperl (or opsview-perl, from March 2012 onwards)
  4. ALTovbase

Example:

pkgrm ALTovweb
pkgrm ALTovcore
pkgrm ALTovperl
pkgrm ALTovbase

Note - Please positively acknowledge all on screen prompts asking you to confirm the removal of the packages.

The correct order of installing the new packages, using pkgadd, is

  1. apache2-modauthtkt-opsview
  2. opsview-perl
  3. opsview-base
  4. opsview-core
  5. opsview-web

Note - It will be necessary to unzip the packages first using gunzip.

Example:

pkgadd -d /path/to/package/apache2-modauthtkt-opsview-2.0.4rc3-sol10-i386_32.pkg
pkgadd -d /path/to/package/opsview-perl-4.0.0.660-sol10-i386_32.pkg
pkgadd -d /path/to/package/opsview-base-4.0.0.8489-sol10-i386_32.pkg
pkgadd -d /path/to/package/opsview-core-4.0.0.8489-sol10-i386.pkg
pkgadd -d /path/to/package/opsview-web-4.0.0.8489-sol10-i386.pkg

Note - Please enter 'all' when prompted to select the packages to process, then positively acknowledge all on screen prompts asking you to confirm the installation of the packages.

Upgrade Databases

Upgrade all the databases. Run as the nagios user:

/usr/local/nagios/installer/upgradedb.pl
Cron tab entry

Due to a bug in the Solaris packages, the nagios user's crontab may not have Opsview generated entries. Also, the opsview-agent will not be running.

Check the nagios user's crontab:

crontab -l nagios | grep OPSVIEW-START

If this returns with no lines, then you need to execute:

su - nagios
/usr/local/nagios/installer/postinstall

This will replace the crontab entries.

You will also need to start the agent:

/etc/init.d/opsview-agent 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 on 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.

MRTG or NMIS on Slave Servers

If you had MRTG or NMIS running on slave servers, you will lose historical information as this is stored on the slave servers. You will need to transfer the files manually if you want to retain this information.

Discussion

fzzzt, 2013/06/27 15:19

I followed this exactly for RHEL and after upgrading, everything seemed fine except one problem: The Opsview Data Warehouse service check was returning CRITICAL: (No output on stdout) stderr: execvp(/usr/local/nagios/libexec/check_odw_status, …) failed. errno is 2: No such file or directory. The file is no longer there.

Ton Voon, 2013/02/20 04:21

Thanks! Sorry, it's taken so long to fix this. We don't seem to get notifications when a new note is added - we'll sort that out.

scaldmaster, 2012/05/22 19:14

sudo yum install opsview-compatility-check should be: sudo yum install opsview-compatibility-check

Navigation
Print/export
Toolbox