If you are looking at **upgrading/migrating** your current installation, please refer to [Before moving to Opsview Monitor 6.x](🔗) to see which page is better suited for your scenario.

## Overview

This page describes the procedure to undertake an automated fresh installation of the Opsview Monitor software, which is our recommended method.

A number of considerations:

  • The automated installation method will always install the latest available version of Opsview Monitor.

  • The automated installation method **assumes you have a new operating system installation** since the Opsview Monitor installation may overwrite or remove some existing packages and configuration(s).

  • Configure a hostname which can be resolved by the host's DNS settings, for example `opsview.example.com` should resolve to the IP of the server.

  • [6.6.5 onwards] The system python alternatives will be modified during deployment. Additionally. if `/usr/bin/python2` is not found (for Ubuntu 18, Centos 7, OL 7, and RHEL 7) or `/usr/bin/python3` is not found (for Ubuntu 20 and RHEL 8), then python 2 or 3 will be installed respectively.

We recommend you update your system to the latest OS packages before installing Opsview.

## Supported Operating systems

Please refer to [this page](🔗).

## Authorisation

Please ensure that any proxies are unset and Opsview addresses are whitelisted - [information here](🔗)

## Installation


  • -p: setup the admin password

  • -s: activate the software with the provided key

  • -y: skip any installation prompts

To learn about all the options available, you can check the help flag:

### Optional SHA256 checksum verification

You can also verify the script before running it by comparing the checksum you get with

Ensure the returned string matches the following:

You can then run the installation (and optionally provide the arguments):

## NGINX Change (SSL Certificates)

Nginx is designed to use only one file that is a combination of your SSL Certificate (server.crt, if you have not renamed it) and your IntermediateCA file. Therefore you need to combine the your SSL certificate file and the IntermediateCA.crt into one single concatenated file in order for Nginx to start successfully. If you find that your homepage/web-page isn't loading up correctly please consider this change may need to be made for Nginx to start (the Opsview component that starts Nginx is opsview-webserver):

Replace the below file names appropriately:

Now that this is complete, opsview-webserver should start without issue.

## Logging in

During the installation, a single administrative user will have been created. The credentials for this user are:

After the system is activated, carry out a reload by navigating to `Configuration => [System] => Apply Changes` and pressing the Apply Changes button.

## Problems with Installations

If you encounter any problems with the installation, it is safe to rerun the command again.

You are also able to continue the installation from a checkpoint for the following reasons:

  • Cancelled installations, which can be done by pressing CTRL+C

  • Failed installations, e.g. a network connection failure

The automated installation consists of four steps that can be partially executed:

Step nameDescriptionOutput from Automated Installation script
repoAdd Opsview package repository`[*] Adding the Opsview package repository`
bootInstall and configure our deploy tool`[*] Installing Opsview Deploy`
fireConfigure the firewall rules for the Web UI. For a full list of ports and extra manual firewall rules you need, see [List of Ports](🔗)`[*] Adding HTTP/HTTPS rules to the local firewall`
instUse the deploy tool to install Opsview`[*] Running Opsview Deploy`

With that in mind, we can then use the -A and -O flags to install up to a certain step or install only that step respectively. While the examples before would run all the four steps in order, this one would rerun all four steps:

This second example would just run the firewall step:

If you entered your software key incorrectly (which will fail at the _inst_ step), the command below will remove the incorrect key, re-create the configuration file and re-run the installation: