In this section, we describe the procedure to undertake an automated installation of the Opsview Monitor software, which is our recommended method. In the table below, we list the supported 64-bit platforms for our automated installation.
Note: 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).
- Set up the Opsview Monitor package repositories and additional repositories required by your system;
- Install and configure prerequisites;
- Configure your operating system in preparation for the Opsview Monitor installation;
- Update your installed packages to the latest version;
- Install Opsview Monitor and run post-installation tasks;
- Prompt you to install and configure any additional modules, such as Network Analyzer, Service Desk Connector or Reporting (This is subject to the type of Opsview Monitor subscription you have).
- Set up the admin user account.
In the first example below, we show the command that will initiate the automatic installation of the Opsview Monitor software where you will be prompted to provide your Software Key and your Repository Key. In the second example, we show the method used to provide the Software and Repository Keys via the command line.
Note: The automated installation method will always install the latest available version of Opsview Monitor.
Use the following command to install Opsview Monitor:
curl -L http://install.opsview.com | sudo bash -s --
Install Opsview Monitor with the Software and Repository Keys in the command line:
curl -L http://install.opsview.com | sudo bash -s -- -r <REPOSITORY_KEY> -e <SOFTWARE_KEY>
You may use wget instead as follows:
wget -O - http://install.opsview.com | sudo bash -s --
wget -O - http://install.opsview.com | sudo bash -s -- -r <REPOSITORY_KEY> -e <SOFTWARE_KEY>
During the installation, you will be prompted to set your password that will be used for both your web UI admin username and the MySQL root password, as shown in the example below. You can change your password at a later stage.
Please enter your desired Opsview admin and database root password:
Note: Spaces are not accepted characters when setting the password. You may see the message:
2015-10-07 11:43:50 Disabling interactive sudo restriction WARNING:Opsview uses sudo noninteractively, and your system was configured to require interactivity, so we've disabled it. To undo this, uncomment "Defaults requiretty" in /etc/sudoers. However, this will prevent Opsview from running. 2015-10-07 11:43:50 - Disabling SELinux 2015-10-07 11:43:51 - Upgrading your system
This is displayed as Opsview Monitor requires
defaults requiretty to be commented out in /etc/sudoers in order to manage the processes via Opsview Monitor Watchdog. If you are installing Opsview Monitor on a database that does not have a root password, you will be required to set one. This will then become both your MySQL root and admin account password. Incidentally, when installing only modules, the MySQL root password will not be changed.
Logging in Once Opsview has been successfully installed, a single administrative user has been created and the following default credentials are used to gain access to your account.
- Username: admin
- Password: as set earlier
You can choose to install Opsview Monitor modules individually or together by using the
-m flag in the command line, as shown in the example below. You will be prompted to install each module individually, if you have a subscription for them.
You can choose to install modules as shown below using curl:
curl –L http://install.opsview.com | sudo bash –s -- -m
To use wget instead:
wget -O - http://install.opsview.com | sudo bash –s -- -m
During the installation process for both Opsview Monitor and its modules, you will be asked if you wish to install a remote database, as we illustrate in the example below. Opsview Monitor and the modules are typically installed locally, but if you select to install on a remote database, you will need to provide connection information for the remote database.
However, if you wish the module databases to be installed separately from Opsview Monitor (local or remote) you will need to run the install command separately for each module. For further information about planning your database setup, refer to Section Databases
During the installation process, you will be asked if you wish to install a remote database:
Install Opsview using a remote database? [y/N]
For larger systems we recommend relocating the Opsview Data Warehouse (ODW) onto a remote server, which will help with overall performance. Nevertheless, if you wish to install the reports database onto an alternative server, the automated installation process will allow you to do this but, following installation, you will need to update the JasperServer configuration for generating reports (see the section below, 'Adding ODW connection').
If you have chosen to install the Reports database on an alternative server, you will need to update the JasperServer configuration to allow it to generate reports.
- Retrieve the password for ODW that's contained in /usr/local/nagios/etc/opsview.conf.
- Next, log in to JasperServer using an account that has REPORTADMIN privileges.
- Once logged in, locate Folders and right-click Data Sources.
- Now click Add Resource and then select Data Source, as shown below.
In the form shown below, you will need to update the fields with the following data:
- Type: JDBC Data Source
- JDBC Driver: com.mysql.jdbc.Driver
- URL: (if ODW resides on a different database server)
- Save Location: /datasources (example).
Now, click Test connection to ensure you have entered your connection details correctly. Finally, click Save to proceed.
You can abort the installation process at any time and manually remove any packages installed in the process.
To abort the installation, press 'CTRL' and 'C'.
To view which packages need to be manually removed, use your local package manager.
For example, on Ubuntu/Debian systems you could use the command:
dpkg -l | grep opsview
On RHEL/CentOS systems you could use:
rpm -qa | grep opsview
And then remove all opsview- packages.
You can continue an aborted installation; however, 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 re-commence the installation, but follow these basic steps to ensure the Opsview Monitor installation continues successfully.
- If any Opsview package is in a ‘broken’ state, then remove it;
- If any other package is 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.