---
title: "Software requirements"
description: ""
url: "https://docs.itrsgroup.com/docs/opsview/6.11.7/prerequisites/software-requirements/index.html"
---
In this section, we look at the programs that are required for Opsview Monitor. The first part of this document covers required software and versions for any installation of Opsview Monitor, while the second part covers requirements for running the automatic installation script.

## Database software

For a list of supported databases in Opsview, see [Supported databases](https://docs.itrsgroup.com/docs/opsview/6.11.7/prerequisites/compatibility-matrix/supported-databases/index.html).

## OS configuration

### Hostname

The hostname and reverse name resolution for all Opsview servers must be in lowercase and only contain letters (a-z), numbers (0-9), and hyphens (-).

Use `hostnamectl` to set the hostname and ensure it matches the entries in `/etc/hosts` or your DNS (or other name resolving system).

All Opsview servers must have a Fully Qualified Domain Name (FQDN). If not, you may receive the error message: `"'opsview_host_domain' cannot be empty!"`.

### Time

All Opsview servers should have clocks correctly synchronised with a common time source (using `ntpd`, `chrony` or similar).

All Opsview servers should have an appropriate time zone set for the region it is in, and all nodes within an Opsview Collector Cluster should have the same time zone set.

This will avoid problems with out of sync schedules, such as a service check’s next scheduled check time not running when expected.

### Cron daemon

Opsview relies on the availability of cron to undertake several jobs for the *opsview* user. In the example below, we use the command here (for the Ubuntu platform) to determine the status of cron.

#### Checking cron is running

Use the following command to see if cron is running on the system, if it is it will return the *Process Identifier* (PID). In the example below, we can see that cron is running and has PID 857.

```yaml
$ sudo service cron status
cron start/running, process 857
```

If cron is not running on your system you can start it using the command below

```yaml
sudo service cron start
```

## Automated Installation

Some packages are required to be able to run the automated install script; these are listed below and must be installed before running the script.

Once called, the automated installation process will ensure that your system has the most up-to-date packages for your given platform.

### Java

Opsview Monitor Reporting Module requires Java version 8 To install this specific version, run the following commands as the root user:

#### RHEL/OL

```yaml
sudo yum install java-1.8.0-openjdk
/usr/sbin/alternatives --config java
```

and then select JDK 1.8.

### sudo

Opsview Monitor relies on the availability of sudo to allow users to execute programs with the security privileges of another user.

#### cURL

The Curl URL Request Library (cURL) is free and open software that compiles and runs across many operating systems. It's a command line tool and library that allows the transfer of data with a *Uniform Resource Locator* (URL) syntax and library; see [curl.haxx.se](http://curl.haxx.se/).

### lsb-release

Opsview Monitor relies on the availability of lsb-release to determine the Operating System and version when running the automatic install script.

## Installing packages

Packages can easily be installed on any of our supported Operating Systems using a package manager.

For Debian and Ubuntu apt-get can be used to install any of the above packages, for example:

```yaml
sudo apt-get install cron
```

For Red Hat and Oracle Linux, yum can be used to install any of the above packages, for example:

```yaml
sudo yum install cron
```


