Opsview Knowledge Center

Manual Installation

Learn how to manually install Opsview Monitor and its components via software repositories

We recommend that you follow the method follow procedure outlined in the Automated Installation, however, if this method is not suitable for you, in this section we describe the steps required to complete a manual installation of the Opsview Monitor software. It's important that you have reviewed section Prerequisites to ensure that any software and hardware dependencies, along with any limitations, are fully understood prior to installation.

Cancelling the Installation

You can abort the installation process at any time and manually remove any package installed during the process.

Continuing an Aborted Installation

You can continue an aborted installation. However, in this section, you will need to have an advanced understanding of GNU/Linux before considering this process. So, resuming an aborted installation is subject to the stage at which you terminated the installation. Naturally, error messages will be displayed when you recommence the installation, but follow these basic steps to ensure the Opsview Monitor installation continues successfully.

  • If any Opsview Monitor package is in a 'broken' state, then remove it;
  • If any other package us in a 'broken' state, then try to reinstall it, or consider just removing it;
  • Remove any Opsview databases installed in the process;
  • When your system is stable, run the installation process again since all files will be overwritten.

Ubuntu

In this section, we describe the requirements to complete the Opsview Monitor software installation for an Ubuntu platform. We recommend using a ‘netinst’ image for a new Ubuntu installation and using apt to install the Secure SHell (SSH) daemon. Other dependent packages shall be installed as part of the Opsview Monitor installation.

Importing Repository Signatures Ubuntu

Opsview packages are signed with a GNU Privacy Guard (GPG) key - the public key can be obtained and added to your server by using the following commands.

curl https://downloads.opsview.com/OPSVIEW-APT-KEY.asc | sudo apt-key add -

Alternatively, run the following which will manually add the Opsview public key:

cat <<EOF | sudo apt-key add -
-----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-----
EOF

Choosing Not to Use Opsviews Public Key - Ubuntu

If you have not imported the Opsview GPG key, you may be presented with an error message. You should note that the NO_PUBKEY section of this error message clearly indicates that your system does not have the public key for this repository and, as such, cannot verify its contents.

GPG error: https://downloads.opsview.com squeeze Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FB4C675977CB2CF6

You may also receive the error message shown below, although you can continue, we recommend that packages are verified prior to their import.

WARNING: The following packages cannot be authenticated!
opsview-perl opsview-base libapache2-mod-auth-tkt-prefork-opsview opsview-core opsview-web opsview
Install these packages without verification [y/N]?

Opsview Software Repositories - Ubuntu

All Opsview Monitor software that is downloaded from our package repository whether it's a trial or purchased subscription, requires a Repository Key, which is a 40 character alphanumeric string, e.g. '5bbd5667b498d81af9c2311d871858b26fe0024b'. The key is unique to your organization and in this section we describe how you can configure your system to access the repositories. Additionally, the Repository Key differs to your Software Key and should have been emailed to your designated subscription contact. So, start by creating a new file, /etc/apt/sources.list.d/opsview.list and add the line to it as below:

# Opsview Packages 
deb https://downloads.opsview.com/k/<REPOSITORY_KEY>/opsview-commercial/<OV_VERSION>/apt <OS> main

where:

<OV_VERSION> is the version of Opsview Monitor to install, such as 5, 5.0 or 5.0.1, depending on your needs.

<REPOSITORY_KEY> is your organization's Repository Key.

<OS> is your distribution name, such as trusty or precise, for example.

Updating the Package Lists - Ubuntu

Once your configuration is complete, you will need to update the repository information by using the command:

sudo apt-get update

However, if you receive the error message 'The method driver /usr/lib/apt/methods/https could not be found.', then you do not have the necessary transport methods installed. As such, you will need to install apt-transport-https:

sudo apt-get install apt-transport-https

Initiating the Install - Ubuntu

Following the successful configuration and update of your repository information, you can now proceed to install the most up-to-date Opsview software by using the command below command as the root user:

sudo apt-get install opsview

You will likely see the below message:

Setting up libruby1.9.1 (1.9.3.484-2ubuntu1.2) ...
Setting up ruby (1:1.9.3.4) ...
Setting up ruby1.9.1 (1.9.3.484-2ubuntu1.2) ...
Processing triggers for ureadahead (0.100.0-16) ...
Setting up opsview-core (5.0.0.25589-1trusty1)
ATTENTION! Please execute as root the following command to complete your installation/upgrade:  /usr/local/nagios/installer/postinstall_root -p MYSQL_ROOT_PASSWORD -h MYSQL_HOST -P MYSQL_PORT
Setting up opsview-web (5.0.0.25589-1trusty1) ...
Running common postinstall tasks
AuthTkt configuration file generated
Running postinstall_root
Enabling module proxy.
To activate the new configuration, you need to run:
service apache2 restart

You MUST run the ...'postinstall_root' script if this message shows. If you do not, Opsview Monitor will not start.

You can leave the 'MYSQL_HOST' and 'MYSQL_PORT' fields blank. In the 'MYSQL_ROOT_PASSWORD' field, enter the password specified during the MySQL installation.

During the installation process you may be prompted to enter the MySQL root password, which is required to set up the databases used by Opsview. Once completed the Opsview server will start to listen on TCP port 3000, which you will need to confirm before completing configuration of Apache.

Using Apache as a Proxy Server - Ubuntu

The commands here should be executed as root. The overall performance of Opsview Monitor will be significantly enhanced by using Apache at the front end.

Use Apache as the front end by executing these commands.

sudo cp /usr/local/nagios/installer/apache_proxy.conf /etc/apache2/sites-available/opsview.conf
sudo cd /etc/apache2/sites-available
sudo a2ensite opsview.conf
sudo a2dissite 000-default.conf

You will also need to install the Apache proxy_html module, by running the commands below, in order to use this configuration. More specifically, for Ubuntu, you can install the libapache2-mod-proxy-html package.

sudo apt-get install libapache2-mod-proxy-html
sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod proxy_html

You will then need to restart Apache, as shown below, after which you will be able to access Opsview Monitor via http://<ipaddress>. You will be required to activate your copy of Opsview Monitor using your Software Key.

sudo /etc/init.d/apache2 restart

Using HTTPS - Ubuntu

The process of creating the SSL certificates will not be documented here.

After transferring the server certification and key files to your Master server and installing them into the appropriate directory, create symlinks from the Opsview Monitor directory pointing to them (or copy them directly into the /usr/local/opsview-web/etc/ssl directory, called server.crt and server.key).

sudo ln -s /path/to/server.crt /usr/local/opsview-web/etc/ssl/server.crt
sudo ln -s /path/to/server.key /usr/local/opsview-web/etc/ssl/server.key

Then configure Apache using the supplied configuration file

sudo cp /usr/local/opsview-web/etc/apache_proxy_ssl.conf /etc/apache2/sites-available/opsview.conf
sudo a2ensite opsview.conf
sudo a2dissite 000-default.conf

You will also need to install extra modules, by running the commands below, in order to use this configuration. More specifically, for Ubuntu, you can install the libapache2-mod-proxy-html package.

sudo apt-get install libapache2-mod-proxy-html
sudo a2enmod ssl
sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod proxy_html

You will then need to restart Apache, after which you will be able to access Opsview Monitor via https://{hostname}. You will be required to activate your copy of Opsview Monitor using your Software Key.

sudo /etc/init.d/apache2 restart

Logging into Opsview - Ubuntu

Once Opsview Monitor has successfully installed, a single administrative user was created and the following default credentials are used to gain access to your account. Naturally, we strongly recommend changing this password immediately to prevent unauthorized access.

  • Username: admin
  • Password: initial

Debian

In this section, we describe the requirements to complete the Opsview Monitor software installation for a Debian platform.

Importing Repository Signatures Debian

Opsview packages are signed with aGNU Privacy Guard (GPG) key. The public key can be obtained and added to your server by using the command line, as shown in the example below:

curl https://downloads.opsview.com/OPSVIEW-APT-KEY.asc | sudo apt-key add -

Alternatively, you can copy and paste the public key by issuing the following command, and then pasting the public key (available below), where you must press [CTRL]+[D] twice at the end of the pasted key. Use the command below to allow the entry of the public key:

sudo apt-key add -

Next, copy the PGP Public Key Block text noted below and paste it into the terminal, followed by [CTRL]+[D] twice:

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

Choosing Not to Use Opsviews Public Key - Debian

If you have not imported the Opsview GPG key, you may be presented with an error message. You should note that the NO_PUBKEY section of this error message clearly indicates that your system does not have the public key for this repository and, as such, cannot verify its contents.

You may receive the following error message if you have not imported the public key.

GPG error: https://downloads.opsview.com squeeze Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY FB4C675977CB2CF6

You may also receive the error message shown below. Although you can continue, we recommend that packages are verified prior to their import.

WARNING: The following packages cannot be authenticated!
opsview-perl opsview-base libapache2-mod-auth-tkt-prefork-opsview opsview-core opsview-web opsview
Install these packages without verification [y/N]?

Opsview Software Repositories - Debian

All Opsview Monitor software that is downloaded from our package repository, whether it's a trial or purchased subscription, requires a Repository Key, which is a 40 character alphanumeric string, e.g. '5bbd5667b498d81af9c2311d871858b26fe0024b'. The key is unique to your organization and in this section we describe how you can configure your system to access the repositories. Additionally, the Repository Key differs to your Software Key and should have been emailed separately to your designated subscription contact. So, start by creating a new file, /etc/apt/sources.list.d/opsview.list and add the line to it as below:

# Opsview Packages
deb https://downloads.opsview.com/k/<REPOSITORY_KEY>/opsview-commercial/<OV_VERSION>/apt <OS> main

where:

<OV_VERSION> is the version of Opsview Monitor to install, such as 5, 5.0 or 5.0.1, depending on your needs.

<REPOSITORY_KEY> is your organization's Repository Key.

<OS> is your distribution name, such as jessie or wheezy, for example.

Updating the Package Lists - Debian

Once your configuration is complete, you will need to update the repository information by using the command:

sudo apt-get update

However, if you receive the error message 'The method driver /usr/lib/apt/methods/https could not be found.', then you do not have the necessary transport methods installed. As such, you will need to install apt-transport-https:

sudo apt-get install apt-transport-https

Initiating the Install - Debian

Following the successful configuration and update of your repository information, you can now proceed to install the most up-to-date Opsview Monitor software by using the command below as the root user:

sudo apt-get install opsview

You will likely see the below message:

Setting up libruby1.9.1 (1.9.3.484-2ubuntu1.2) ...
Setting up ruby (1:1.9.3.4) ...
Setting up ruby1.9.1 (1.9.3.484-2ubuntu1.2) ...
Processing triggers for ureadahead (0.100.0-16) ...
Setting up opsview-core (5.0.0.25589-1trusty1)
ATTENTION! Please execute as root the following command to complete your installation/upgrade:  /usr/local/nagios/installer/postinstall_root -p MYSQL_ROOT_PASSWORD -h MYSQL_HOST -P MYSQL_PORT
Setting up opsview-web (5.0.0.25589-1trusty1) ..
Running common postinstall tasks
AuthTkt configuration file generated
Running postinstall_root
Enabling module proxy.
To activate the new configuration, you need to run:
service apache2 restart

You MUST run the ...'postinstall_root' script if this message shows. If you do not, Opsview Monitor will not start.
During the installation process you may be prompted to enter the MySQL root password, which is required to set up the databases used by Opsview Monitor. Once completed the Opsview Monitor server will start to listen on TCP port 3000, which you will need to confirm before completing configuration of Apache.

Using Apache as a Proxy Server - Debian

The commands here should be executed as root. The overall performance of Opsview will be significantly enhanced by using Apache at the front end.

Using HTTP - Debian

Use Apache as the front end by executing these commands.

sudo cp /usr/local/nagios/installer/apache_proxy.conf /etc/apache2/sites-available/opsview.conf
sudo a2ensite opsview.conf
sudo a2dissite 000-default.conf

You will also need to install the Apache proxy_html module, by running the commands below, in order to use this configuration. More specifically, for Ubuntu, you can install the libapache2-mod-proxy-html package.

sudo apt-get install libapache2-mod-proxy-html
sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod proxy_html

You will then eed to restart Apache, as shown below, after which you will be able to access Opsview via http://<ipaddress>. You will be required to activate your copy of Opsview using your software key.

sudo /etc/init.d/apache2 restart

Using HTTPS - Debian

The process of creating the SSL certificates will not be documented here.

After transferring the server certification and key files to your Master server and installing them into the appropriate directory, create symlinks from the Opsview Monitor directory pointing to them (or copy them directly into the /usr/local/opsview-web/etc/ssl directory, called server.crt and server.key).

sudo ln -s /path/to/server.crt /usr/local/opsview-web/etc/ssl/server.crt
sudo ln -s /path/to/server.key /usr/local/opsview-web/etc/ssl/server.key

Then configure Apache2 using the supplied configuration file

sudo cp /usr/local/opsview-web/etc/apache_proxy_ssl.conf /etc/apache2/sites-available/opsview.conf
sudo a2ensite opsview.conf
sudo a2dissite 000-default.conf

You will also need to install extra modules, by running the commands below, in order to use this configuration. More specifically, for Ubuntu, you can install the libapache2-mod-proxy-html package.

sudo apt-get install libapache2-mod-proxy-html
sudo a2enmod ssl
sudo a2enmod proxy
sudo a2enmod proxy_http
sudo a2enmod proxy_html

You will then need to restart Apache, after which you will be able to access Opsview via https://{hostname}. You will be required to activate your copy of Opsview using your software key.

sudo /etc/init.d/apache2 restart

Logging into Opsview - Debian

Once Opsview has successfully installed, a single administrative user was created and the following default credentials are used to gain access to your account. Naturally, we strongly recommend changing this password immediately to prevent unauthorized access.

  • Username: admin
  • Password: initial

RHEL

In this section, we describe the requirements to complete the Opsview Monitor software installation for the RHEL platform.

The RHEL installation is dependent on the Java Development Kit (JDK) 1.6 or 1.7, which includes the Java Runtime Environment (JRE); the RPM must be java.

Note: You will need to modify your firewall to allow TCP port 80 to access the web interface for the RHEL7 distribution.

SELinux RHEL

Opsview is currently not compatible with Security-enhanced (SE) Linux extensions and, at this time, this must be disabled by editing /etc/selinux/config and updating the file with what is shown in the example below, and restarting your system.

Disable SELinux by updating the config file.

#This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#       enforcing - SELinux security policy is enforced.
#       permissive - SELinux prints warnings instead of enforcing.
#       disabled - SELinux is fully disabled.
SELINUX=disabled
# SELINUXTYPE= type of policy in use. Possible values are:
#       targeted - Only targeted network daemons are protected.
#       strict - Full SELinux protection.
# SELINUXTYPE=targeted

Red Hat Network Repositories

You will need to enable additional Red Hat repositories for some dependent software.

RHEL7

The Red Hat Enterprise Server 7 repositories must be enabled through your Red Hat Network (RHN) access. Here you need to log in to your account and select your RHEL7 system name. You will also need to modify your channel subscription to include, 'RHEL Server Optional (v7 for 64-bit)'. Alternatively, you can execute the command below on the server itself as root:

rhn-channel --add --channel="rhel-x86_64-server-optional-7"
-u rhn-username -p rhn-password

RHEL6

Likewise, the Red Hat Enterprise Server 6 repositories must also be enabled through your RHN access. Here you need to log in to your account and select your RHEL6 system name. You will also need to modify your channel subscription to include, 'RHEL Server Optional (v6 for 64-bit)'. Alternatively, you can execute the command below on the server itself as root:

rhn-channel --add
--channel="rhel-i386-server-optional-6" -u rhn-username -p
rhn-password

Opsview Software Repositories RHEL

All Opsview software that is downloaded from our package repository, whether it's a trial or purchased subscription, requires a Repository Key. This is a 40 character alphanumeric string, e.g. '5bbd5667b498d81af9c2311d871858b26fe0024b'. The key is unique to your organization and in this section we describe how you can configure your system to access the repositories. Additionally, the repository differs to your Software Key and should have been emailed separately to your designated subscription contact. Create a new file, /etc/yum.repos.d/opsview.repo and add the below lines to it:

[opsview]
name = Opsview
baseurl = https://downloads.opsview.com/k/<REPOSITORY_KEY>/opsview-commercial/<OV_VERSION>/yum/rhel/$releasever/$basearch
enabled = 1
protect = 0
gpgcheck = 0

where:

<REPOSITORY_KEY> is your organization's repository key.

<OV_VERSION> is the version of opsview to use, such as 5, 5.0 or 5.0.1, depending on your needs.

Initiating the Install - RHEL

Following the successful configuration and update of your repository information, you now proceed to install the most up-to-date Opsview software by running as 'root', the command below:

yum install opsview

Post-install Tasks - RHEL

Once the Opsview packages have been installed, you now need to configure Opsview and its databases, as outlined in the following sections.

Starting MySQL - RHEL

Ensure the MySQL root password has been set to a known value, as shown below:

mysqladmin -u root password <PASSWORD>

If you receive an error, such as "Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'", then mysql has not be started. To remedy this, start MySQL using the command "/etc/init.d/mysqld start".

You will also need to ensure that mysql is set to start at boot time with the command:

chkconfig --level 345 mysqld on

Completing the Installation - RHEL

As the root user, run the following command:

/usr/local/nagios/installer/postinstall_root -p '<MYSQL ROOT PASSWORD>'

This command will connect to the MySQL server, create the necessary users and databases, and then it will then start the Opsview Monitor daemons.

The daemons will take a few minutes to start up, but you can check on the process by running

su - nagios -c "/usr/local/nagios/bin/opsview_watchdog summary"

Once you have verified that each row says 'Monitored' in the 'Monitoring Status' column, you now complete the configuration of Apache.

Using Apache as a Proxy Server RHEL

The commands here should be executed as root. The overall performance of Opsview Monitor will be significantly enhanced by using Apache at the front end.

Using HTTP RHEL

Firstly, ensure the following line is uncommented in /etc/httpd/conf.modules.d/00-proxy.conf:

LoadModule proxy_http_module modules/mod_proxy_http.so

You may also need to uncomment the ' DocumentRoot' variable in file /etc/httpd/conf/httpd.conf'.

Now run the following command:

cp /usr/local/nagios/installer/apache_proxy.conf /etc/httpd/conf.d/opsview.conf

Edit the newly created opsview.conf file and uncomment the 2 'VirtualHost' lines.

Now, amend the Apache web server group membership to include nagcmd group, to ensure the apache user is correct for your web software:

usermod -G nagcmd apache

If you use a centralized user management system, you may need to amend /etc/group manually. You can also check if the permissions are set correctly using the command shown below and looking out for the nagcmd group:

id 'a apache

Finally, you can restart the Apache server, after which you will now be able to access Opsview Monitor via http://{hostipaddress}/:

systemctl restart httpd

Using HTTPS RHEL

The process of creating the SSL certificates will not be documented here.

After transferring the server certification and key files to your Master server and installing them into the appropriate directory, create symlinks from the Opsview Monitor directory pointing to them (or copy them directly into the /usr/local/opsview-web/etc/ssl directory, called server.crt and server.key).

sudo ln -s /path/to/server.crt /usr/local/opsview-web/etc/ssl/server.crt
sudo ln -s /path/to/server.key /usr/local/opsview-web/etc/ssl/server.key

As root, install the Apache SSL module:

sudo yum install mod_ssl

Ensure the following line is uncommented in /etc/httpd/conf.modules.d/00-proxy.conf:

LoadModule proxy_http_module modules/mod_proxy_http.so

You may also need to uncomment the ' DocumentRoot' variable in file /etc/httpd/conf/httpd.conf'.

Then configure Apache2 using the supplied configuration file:

cp /usr/local/opsview-web/etc/apache_proxy_ssl.conf /etc/httpd/conf.d/opsview.conf

Edit the newly created opsview.conf file and uncomment the 2 'VirtualHost' lines.

Now, amend the Apache web server group membership to include nagcmd group, to ensure the apache user is correct for your web software:

usermod -G nagcmd apache

If you use a centralized user management system, you may need to amend /etc/group manually. You can also check if the permissions are set correctly using the command shown below and looking out for the nagcmd group:

id 'a apache

Finally, you can restart the Apache server, after which you will now be able to access Opsview Monitor via http://{hostipaddress}/:

systemctl restart httpd

Logging into Opsview RHEL

Once Opsview has successfully installed, a single administrative user was created and the following default credentials are used to gain access to your account. Naturally, we strongly recommend changing this password immediately to prevent unauthorized access.

  • Username: admin
  • Password: initial

CentOS

In this section, we describe the requirements to complete the Opsview Monitor software installation for the CentOS platform.

Note: You will need to modify your firewall to allow TCP port 80 to access the web interface for the CentOS7 distribution.

The EPEL (Extra Packages for Enterprise Linux) repository needs to be set up to make available further necessary dependencies. You can you do this by installing the 'epel-release' package using yum (this package is available in the 'CentOS Extras repository', which is enabled by default):

yum install epel-release

SELinux CentOS

Opsview is currently not compatible with Security-enhanced (SE) Linux extensions and, at this time, this must be disabled by editing /etc/selinux/config and updating the file with what is shown in the example below, and restarting your system.

Disable SELinux by updating the config file.

#This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#       enforcing - SELinux security policy is enforced.
#       permissive - SELinux prints warnings instead of enforcing.
#       disabled - SELinux is fully disabled.
SELINUX=disabled
# SELINUXTYPE= type of policy in use. Possible values are:
#       targeted - Only targeted network daemons are protected.
#       strict - Full SELinux protection.
# SELINUXTYPE=targeted

Opsview Software Repositories CentOS

All Opsview software that is downloaded from our package repository, whether it's a trial or purchased subscription, requires a Repository Key. This is a 40 character alphanumeric string, e.g. '5bbd5667b498d81af9c2311d871858b26fe0024b'. The key is unique to your organization and in this section we describe how you can configure your system to access the repositories. Additionally, the repository differs to your Software Key and should have been emailed separately to your designated subscription contact. Create a new file, /etc/yum.repos.d/opsview.repo. Use copy and paste to place lines noted below into the new file:

[opsview]
name = Opsview
baseurl = https://downloads.opsview.com/k/<REPOSITORY_KEY>/opsview-commercial/<OV_VERSION>/yum/centos/$releasever/$basearch
enabled = 1
protect = 0
gpgcheck = 0

Where:

<REPOSITORY_KEY> is your organization's Repository Key.

<OV_VERSION> is the version of opsview to use, such as 5, 5.0 or 5.0.1, depending on your needs.

Following the successful configuration and update of your repository information, you now proceed to install the most up-to-date Opsview software by running as 'root', the command below:

yum install opsview

Initiating the Installation CentOS

Following the successful configuration and update of your repository information, you now proceed to install the most up-to-date Opsview software by running as 'root', the command below:

yum install opsview

Post-install Tasks CentOS

Once the Opsview packages have been installed, you now need to configure Opsview Monitor and its databases, as outlined in the following sections.

Mysql Tuning CentOS

Add these lines in the '[mysqld]' section of the my.cnf file

innodb_file_per_table=1 
innodb_flush_log_at_trx_commit=2

Starting MySQL CentOS

Ensure the MySQL root password has been set to a known value, as shown below:

mysqladmin -u root password <PASSWORD>

If you receive an error, such as "Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'", then mysql has not be started. To remedy this, use the appropriate command below:

CentOS 7

  1. Start the MariaDB database server

    systemctl start mariadb
    systemctl status mariadb
    
  2. You will also need to ensure that mysql is set to start at boot time with the command:

    systemctl enable mariadb
    

CentOS 6

  1. Start the MariaDB database server

    service mysqld start
    service mysqld status
    
  2. You will also need to ensure that mysql is set to start at boot time with the command:

    chkconfig mysqld on
    

Sudo Configuration Change CentOS

Amend your sudo configuration (using 'visudo') and comment out the line (by adding a # character at the start of the line):

Default requiretty

Completing the Installation CentOS

As the root user, run the following command:

/usr/local/nagios/installer/postinstall_root -p '<MYSQL ROOT PASSWORD>'

This command will connect to the MySQL server, create the necessary users and databases, and then it will then start the Opsview Monitor daemons.

The daemons will take a few minutes to start up, but you can check on the process by running

su - nagios -c "/usr/local/nagios/bin/opsview_watchdog summary"

Once you have verified that each row says 'Monitored' in the 'Monitoring Status' column, you now complete the configuration of Apache.

The commands here should be executed as root. The overall performance of Opsview Monitor will be significantly enhanced by using Apache at the front end.

Using Apache as a Proxy Server CentOS

The commands here should be executed as root. The overall performance of Opsview Monitor will be significantly enhanced by using Apache at the front end.

Using HTTP CentOS

Firstly, ensure the following line is uncommented in /etc/httpd/conf.modules.d/00-proxy.conf:

LoadModule proxy_http_module modules/mod_proxy_http.so

You may also need to uncomment the ' DocumentRoot' variable in file /etc/httpd/conf/httpd.conf'.

Now run the following command:

cp /usr/local/nagios/installer/apache_proxy.conf /etc/httpd/conf.d/opsview.conf

Edit the newly created opsview.conf file and uncomment the 2 'VirtualHost' lines.

Now, amend the Apache web server group membership to include nagcmd group, to ensure the apache user is correct for your web software:

usermod -G nagcmd apache

If you use a centralized user management system, you may need to amend /etc/group manually. You can also check if the permissions are set correctly using the command shown below and looking out for the nagcmd group:

id 'a apache

Finally, you can restart the Apache server, after which you will now be able to access Opsview Monitor via http://{hostipaddress}/:

systemctl restart httpd

Using HTTPS CentOS

The process of creating the SSL certificates will not be documented here.

After transferring the server certification and key files to your Master server and installing them into the appropriate directory, create symlinks from the Opsview Monitor directory pointing to them (or copy them directly into the /usr/local/opsview-web/etc/ssl directory, called server.crt and server.key).

sudo ln -s /path/to/server.crt /usr/local/opsview-web/etc/ssl/server.crt
sudo ln -s /path/to/server.key /usr/local/opsview-web/etc/ssl/server.key

As root, install the Apache SSL module:

sudo yum install mod_ssl

Ensure the following line is uncommented in /etc/httpd/conf.modules.d/00-proxy.conf:

LoadModule proxy_http_module modules/mod_proxy_http.so

You may also need to uncomment the 'DocumentRoot' variable in file /etc/httpd/conf/httpd.conf'.

Then configure Apache2 using the supplied configuration file:

cp /usr/local/opsview-web/etc/apache_proxy_ssl.conf /etc/httpd/conf.d/opsview.conf

Edit the newly created opsview.conf file and uncomment the 2 'VirtualHost' lines.

Now, amend the Apache web server group membership to include nagcmd group, to ensure the apache user is correct for your web software:

usermod -G nagcmd apache

If you use a centralized user management system, you may need to amend /etc/group manually. You can also check if the permissions are set correctly using the command shown below and looking out for the nagcmd group:

id 'a apache

Finally, you can restart the Apache server, after which you will now be able to access Opsview Monitor via https://{hostipaddress}/:

systemctl restart httpd

Logging into Opsview CentOS

Once Opsview has successfully installed, a single administrative user was created and the following default credentials are used to gain access to your account. Naturally, we strongly recommend changing this password immediately to prevent unauthorized access.

  • Username: admin
  • Password: initial

SLES

In this section, we describe the requirements to complete the Opsview Monitor software installation for the SUSE platform.

Opsview Software Repositories SLES

All Opsview Monitor software that is downloaded from our package repository, whether it's a trial or purchased subscription, requires a Repository Key. This is a 40 character alphanumeric string, e.g. 5bbd5667b498d81af9c2311d871858b26fe0024b. The key is unique to your organization and in this section we describe how you can configure your system to access the repositories. Additionally, the Repository Key differs to your Software Key and should have been emailed separately to your designated subscription contact. Enable the Extras repo, as shown below:

zypper mr -e nu_novell_com:SLES11-Extras

Next, use zypper to add the Opsview Monitor repository:

zypper addrepo https://downloads.opsview.com/k/<REPOSITORY_KEY>/opsview-commercial/<OV_VERSION>/yum/sles/11/x86_64 'Opsview Commercial'

Where:

<REPOSITORY_KEY> is your Repository Key.

<OV_VERSION> is the version of opsview to use, such as 5, 5.0 or 5.0.1, depending on your needs.

Initiating the Install SLES

Following the successful configuration and update of your repository information, you now proceed to install the most up-to-date Opsview Monitor software by using the following command as root:

zypper install opsview

Post-install Tasks SLES

Once the Opsview Monitor packages have been installed, you now need to configure Opsview Monitor and its databases, as outlined in the following sections.

Starting MySQL SLES

Ensure the MySQL root password has been set to a known value, as shown below:

mysqladmin -u root password <PASSWORD>

If you receive an error, such as "Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'", then mysql has not be started. To remedy this, start MySQL using the command "/etc/init.d/mysqld start".

You will also need to ensure that mysql is set to start at boot time with the command:

chkconfig --level 345 mysqld on

Setting up Nagios(R) Users Environment SLES

You will need to ensure that the Nagios(R) user's environment is set up correctly. Opsview Monitor will endeavor to set the correct profile, but you must check the following line is present in the profile script depending on your shell; for example, .profile for Bourne or Korn shell .bash_profile or .bashrc for bash shell:

test -f /usr/local/nagios/bin/profile && . /usr/local/nagios/bin/profile

The remaining steps should be undertaken as the Nagios(R) user. You should log out and then back in to ensure the profile is set up:

exit
su ' nagios

Set up MySQL Database Users SLES

In the example below, we show you how to set up the Opsview Monitor MySQL database users, along with their permissions:

/usr/local/nagios/bin/db_mysql -u root -p<MYSQL ROOT PASSWORD>

Install Required Databases SLES

Next, you need to install the required databases using the commands below:

/usr/local/nagios/bin/db_opsview db_install
/usr/local/nagios/bin/db_runtime db_install
/usr/local/nagios/bin/db_odw db_install
/usr/local/nagios/bin/db_dashboard db_install

Generate All The Configuration Files SLES

Next, you will need to generate all the necessary configuration files. To do this, run the command below:

/usr/local/nagios/bin/rc.opsview gen_config

Amending Watchdog Configuration SLES

There is an issue with SLES and watchdog - whereby it fails to detect that opsviewd is running and will keep on trying to start it, bringing opsviewadmd down with it. There is a workaround which requires changing the file:

/opt/opsview/watchdog/etc/services/opsview

under this section check process opsviewd and remove matching ^opsviewd$ and adding with pidfile /usr/local/nagios/var/opsview.pid

Then run:

/opt/opsview/watchdog/bin/opsview-monit reload

Then add the nagios user to the opsview group:

usermod -A opsview nagios

Then stop Opsview Monitor

/opt/opsview/watchdog/bin/opsview-monit -g opsview stop

Then restart Opsview Monitor

/opt/opsview/watchdog/bin/opsview-monit -g opsview start

Starting the Web Application Server SLES

Finally, you will need to start up the web application server using the commands below:

sudo /opt/opsview/watchdog/bin/opsview-monit start opsview-web

The Opsview Monitor server is now listening on TCP port 3000, which you can confirm using the command:

netstat -tulpn | grep 3000 
tcp 0  0  0.0.0.0:3000  0.0.0.0:* LISTEN  9413/starman worker

If you don't see a starman worker process, then the Opsview Monitor server is not listening. Once you have verified that your Opsview Monitor server is listening, you can now complete the configuration of Apache.

Using Apache as a Proxy Server SLES

The commands here should be executed as root. The overall performance of Opsview Monitor will be significantly enhanced by using Apache at the front end.

Firstly, use yast to enable the proxy modules in Apache. Start yast and 'Network Services => HTTP Server' followed by selecting the 'Server Modules' tab. Now enable 'proxy,' 'proxy_http' and 'proxy_connect'.

Now create the file /etc/httpd/conf/opsview.conf with the content that is shown blow:

<VirtualHost *>
Include /usr/local/opsview-web/etc/apache_proxy.conf
</VirtualHost>

Now, amend the Apache web server group membership to include nagcmd group; ensure the user 'wwwrun' is correct for your web software:

usermod -G nagcmd wwwrun

if you use a centralized user management system, you may need to amend /etc/group manually. You can also check if the permissions are set correctly using the command shown below and looking out for the nagcmd group:

run id wwwrun

Finally, you can restart the Apache server, as shown below, where you will now be able to access Opsview Monitor via http://<address>:

/etc/init.d/httpd restart

Logging into Opsview

Once Opsview has successfully installed, a single administrative user was created and the following default credentials are used to gain access to your account. Naturally, we strongly recommend changing this password immediately to prevent unauthorized access.

  • Username: admin
  • Password: initial

Manual Installation

Learn how to manually install Opsview Monitor and its components via software repositories