Simple automated installation
Overview Copied
This page describes the procedure to undertake an automated fresh installation of the Opsview Monitor software, which is our recommended method.
Note
If you are looking at upgrading or migrating your current installation, please refer to Migrating Opsview Monitor 6.x to see which page is better suited for your scenario.
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 configurations.
- 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. - 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, Debian 10, OL 8, and RHEL 8), then Python 2 or 3 will be installed respectively. - For RHEL 7/8/9 systems, ensure the subscription manager is configured to allow system repositories. Verify that the
disable_system_repos
option is set to0
in the/etc/dnf/plugins/subscription-manager.conf
file on each system. - The
root
user must be able to runsudo
without a password on all servers in the Opsview deployment. - Make sure you check the software requirements, particularly the hostname requirements.
Note
We recommend you update your system to the latest OS packages before installing Opsview Monitor.
Supported operating systems Copied
Please refer to the list of supported operating systems.
Authorisation Copied
Please ensure that any proxies are unset and Opsview addresses are whitelisted. For more information, see Planning your System.
Installation Copied
To install, run:
curl -sLo- https://deploy.opsview.com/6 | sudo bash -s -- -p PASSWORD -s SOFTWARE_KEY -y
- -p — set up 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:
curl -sLo- https://deploy.opsview.com/6 | sudo bash -s -- -h
Optional SHA256 checksum verification Copied
You can also verify the script before running it by comparing the checksum you get with:
curl -L https://deploy.opsview.com/6 > opsview_deploy
sha256sum opsview_deploy
Ensure the returned string matches the following:
cf820103be6235651c39039d2aa35b0a2dc3bf47af7fa1633fa7a6c34f3d3d39
You can then run the installation (and optionally provide the arguments):
sudo bash ./opsview_deploy -p PASSWORD -s SOFTWARE_KEY -y
NGINX change (SSL Certificates) Copied
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
is not 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
):
cd /opt/opsview/webapp/etc/ssl/
cp -p server.crt server.crt.backup
Replace the below file names appropriately:
cat SSL_Certificate_filename IntermediateCA.crt_filename > server.crt
Now that this is complete, opsview-webserver
should start without issue.
Logging in Copied
During the installation, a single administrative user will have been created. The credentials for this user are:
username: admin
password: <password supplied during installation>
After the system is activated, carry out a reload by navigating to Configuration > Apply Changes and click Apply Changes.
Problems with installations Copied
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, for example, a network connection failure.
The automated installation consists of four steps that can be partially executed:
Step name | Description | Output from Automated Installation script |
---|---|---|
repo | Add Opsview package repository. | [*] Adding the Opsview package repository |
boot | Install and configure our deploy tool. | [*] Installing Opsview Deploy |
fire | Configure the firewall rules for the Web UI. For a full list of ports and extra manual firewall rules, see Ports. | [*] Adding HTTP/HTTPS rules to the local firewall |
inst | Use 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:
curl -sLo- https://deploy.opsview.com/6 | sudo bash -s -- -A inst
This second example would just run the firewall step:
curl -sLo- https://deploy.opsview.com/6 | sudo bash -s -- -O fire
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:
sudo rm /opt/opsview/deploy/etc/user_vars.yml
curl -sLo- https://deploy.opsview.com/6 | sudo bash -s -- -p PASSWORD -s SOFTWARE_KEY -y -O boot,inst