In this section, we provide you with guidance, as to how to successfully upgrade your Opsview Core installation to Opsview Monitor. It's important that you have first reviewed Pre-requisites to ensure that any software and hardware dependencies, along with any limitations are fully understood prior to upgrade.
Most upgrade actions are managed during package installation, but there are certain pre and post-upgrade steps that require manual intervention.
Before you begin, you need to ensure you have a valid:
- Software key (Used to activate the Opsview Monitor software)
A valid subscription will provide you with a Software Key when you subscribe to Opsview Atom or make an Enterprise or Pro purchase, or you subscribe to an active Opsview Monitor 30-day Trial.
Please note, the Opsview Monitor server will be taken offline during the upgrade.
Opsview Monitor's dashboard capability may potentially expand the quantity of Application Programming Interface (API) calls made to the Opsview Monitor system and, in turn, increase the overall load. We recommend that you undertake the steps in the following list before upgrading your system.
- Baseline the performance of your Opsview Monitor master server and your database, if it is separate from the master, to establish how well it is currently performing;
- Review the hardware requirements and pay particular attention to the system memory requirements.
- You will need to establish if the dashboard will only be used by existing Opsview Monitor Users or if it will be rolled out to new Users. Naturally, increasing the number of Users who use your system will increase system load, which may have an impact on the overall performance.
If you have any specific concerns, please contact our Customer Success Team.
In this section, we describe several pre-upgrade steps that are needed to be undertaken prior to your Opsview Monitor upgrade.
Opsview Monitor 5.x includes new dashboard functionality, which requires its own database and, as such, you will need to set up the access to the new database prior to your upgrade. You can set an alternative password by adding the line, as shown in the example below, to the /usr/local/nagios/etc/opsview.conf file.
$dashboard_dbpasswd = "changeme";
Now, set up the credentials for the new database, as shown below, using the password you chose in 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;
In this section, we describe specific upgrade steps that are relevant to your distribution.
The following list describes several steps that are needed to complete the upgrade on Debian and Ubuntu distributions.
Check /etc/apt/sources.list and all the files in /etc/apt/sources.list.d: If there are any links to 'downloads.opsview.com,' then they will need to be commented out since all previous repository locations need to be removed. Note: You must disable any Opsview Core repositories, as failing to do so may result in your system having mixed versions of opsview-base and opsview-perl, which is not supported.
You will need to add the new Repository Signature and add the new location, as shown in the example below, where you will be prompted with further instructions.
Create a new file
/etc/apt/sources.list.d/opsview.list and add the following line to it:
# Opsview packages deb https://downloads.opsview.com/opsview-commercial/latest/apt <OS> main
- <OS> is your distribution name, such as squeeze, lucid, precise
When your configuration is complete, you will need to update the repository information:
Finally, upgrade Opsview Monitor and, as root, run the command, as shown in the example below:
If you have changed your MySQL root password, you will need to have at hand since you may be prompted for it. You may see messages as shown below. This is due to the relocated opsview-perl files and can be ignored:
dpkg: warning: unable to delete old directory '/usr/local/nagios/perl/lib/Perl6': Directory not empty
You may also see the message below:
The method driver /usr/lib/apt/methods/https could not be found.
This is because the https transport is not available by default, but it can be installed using the command, as shown below:
apt-get install apt-transport-https
The following list describes several steps that are needed to complete the upgrade on CentOS and RHEL distributions.
Check all files in /etc/yum.repos.d and ascertain if there are any links to 'downloads.opsview.com,' as they will need to be commented out since all previous repository locations need to be removed. Note: You must disable any Opsview Core repositories, as failing to do so may result in your system having mixed versions of opsview-base and opsview-perl, which is not supported.
You will need to create a new file, namely /etc/yum.repos.d/opsview.repo and add the lines as shown in RHEL or CentOS, below, depending on your platform.
[opsview] name = Opsview baseurl = https://downloads.opsview.com/opsview-commercial/latest/yum/rhel/$releasever/$basearch enabled = 1 protect = 0 gpgcheck = 0
[opsview] name = Opsview baseurl = https://downloads.opsview.com/opsview-commercial/latest/yum/centos/<OS>/$basearch enabled = 1 protect = 0 gpgcheck = 0
<OS> is '6'or '7'.
- When your configuration is complete, you will need to update the repository information, as shown in the example below:
yum clean all yum makecache
Finally, upgrade Opsview Monitor and, as root, run the command, as shown in the example below. If you have changed your MySQL root password, you will need to have it at hand since you may be prompted for it.
yum install opsview opsview-core opsview-base opsview-perl opsview-web
The following list describes several steps that are needed to complete the SLES distribution.
Check all files in /etc/zypp/repos.d and ascertain if there are any links to 'downloads.opsview.com,' as they will need to be commented out since all previous repository locations need to be removed. Note: You must disable any Opsview Core repositories, as failing to do so may result in your system having mixed versions of opsview-base and opsview-perl, which is not supported.
You will need to add the Opsview repository using the zypper command, as shown in the example below:
zypper addrepo https://downloads.opsview.com/opsview-commercial/latest/yum
<ARCH> is x86_64.
When your configuration is complete, you will need to refresh or update the repository information, as shown below:
Finally, due to the limitations of zypper you are unable to upgrade Opsview Monitor and, as such, you will have to remove the previous version and install newer versions. You will then have to run the post upgrade tasks manually, as shown below:
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-watchdog
Opsview Monitor packages are signed with the GNU Privacy Guard (GPG) for the Debian and Ubuntu repositories where the public key can be obtained and added to your server by using the command lines, as shown below:
curl https://downloads.opsview.com/OPSVIEW-APT-KEY.asc | sudo apt-key add -
Alternatively, copy and paste the key as shown below:
sudo apt-key add -
Next, copy and paste the text below:
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.10 (GNU/Linux) mQENBE+RJcUBCACufp+mfI70ZUTPx9gaebIQEpg11OGp0y068gB5UZzhZ+hf8T9p 0YYUgRQ4qv8VL+YY+mvqLcoISkBLvYE7NQWm7xCmKCLpR3rdO/f2T0qS8s2Cl1V9 QV+MtZD9DvgWtwXSJDf9Ne6qgayyhdazMFTV/4pxMkkfRG2jYixDwx4RlgvJ0fgK s9oS1REdXZ0LoNcwJ2eBqZljtXELUs38IYaoZNGAMzggTnfqxD0yV6NA87wxslpj Ek5Zx1IsPf87odMnDshynb/rJG20SqouEFBeGGIZg9mR6/1n05ht2C7UmxFXw3am w0eqAZ2Mv6gRQHrjeLy/N8a2/GCjN8iXW1D9ABEBAAG0T09wc3ZpZXcgUmVwb3Np dG9yaWVzIChodHRwczovL2Rvd25sb2Fkcy5vcHN2aWV3LmNvbSkgPHJlcG9zaXRv cmllc0BvcHN2aWV3LmNvbT6JATgEEwECACIFAk+RJcUCGwMGCwkIBwMCBhUIAgkK CwQWAgMBAh4BAheAAAoJEDJ8cM0PxphLo40H/3Mi6zSWT2Gs6/R2tBr893zxATmh Wp+VD9V9+i01dk5molEsetqwydj2IXIJWw3JIGODuRj8xzl8LW9vBNIxSOFtdml8 9VH5oEQdzsikLo69914PNRy5nXNMnH40weAkm5xCKH4a7qSWN37KIhHjS2ZDD89b UzIT82eBDdAFbUodNxLR9WSHTKISiAeRUkHGfJU8d2YLZCfzCvFR7c1uwzr3XC6p ORIK1yNu9dL3y2ZgjyTB2W1OR0XPGXCFOXOA5hIpGt4We1TcShEgOqpLzYYUlrmh VePUcjAqoA20JWttT5xOsJnnZqEJRTknnBKbDzZUtSqekjLBnqIXEE4I8kW5AQ0E T5ElxQEIAK65S8VDrha8j8H6zMLOSKT83mQf9fmouxzCtxqsfkjRik5/6ZRnYY6c k4DPj+2nN4hJNKa2VQ9f1qQTQ1Q/8AEhA/ljg8a9E8neClUyCfOq0HQ9TKlFbQN/ gdvEOdspyWSEJxbFCX/IQy1kDhMf1DJRpUKUU1gJUOQiHsobM9FMX9jf4at+N9qD i2N1tBlFK2v+T6du32Vfukxv56D+rozCr/EkJZmD6DT/enpQG6tK6+lhitmr1AgB kLegV9RIJWSulu08RqpBgXNV7Hru8EI/MZWfdzuasiXA3I+umjXoch8wuF8I5R0P GS25mit3DNs1o+6jV7TogsIv2PiC1ysAEQEAAYkBHwQYAQIACQUCT5ElxQIbDAAK CRAyfHDND8aYS9xmCACQUNq33dBrNQz5ggXLXeOfwEgzrDAcd1TeTn7bDF5viXiW EfoDw302jafYybtR4iojXC+r78EdEIPzPN21tUzN6o3HqZfgzDS0r7YBRsid/0x0 0Doc//ebZBJVMXe+MtzGYpkYQojSCYIS6WXdrRv/NRWlfMajqIkAliqggZFaRRuJ L1tszaI0+2Ep1I7I8TRlmhvmd6S6w12HZtaQGBzv9ylI23m5LbSsLDYrZtIqeRBo ucfnvywHuqgrgxgO+x8PRG7v7gfFT0QaJcWf6PwuxsqNsOq4UqZCRnfj3jg/aUoO JE37AT9NT+b06NS5cSJVhWfky4fblE9bhPxjLDOZ =HqD/ -----END PGP PUBLIC KEY BLOCK-----
Finally, press CTRL and D twice at the end of the pasted key.
In this section, we describe post-upgrade instructions that are needed to be undertaken following your Opsview Monitor upgrade.
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 /usr/local/nagios/etc/opsview.conf.
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.