Welcome to docs.opsview.com

Installation Guide - Red Hat Enterprise Linux

Before you start

  • This page details manually installing Opsview on a Red Hat Enterprise Linux platform. Note that we recommend using our automated installation method instead.
  • For supported Red Hat Enterprise Linux releases please refer to platforms.
  • Please ensure perl 5.8.8-15.el5_2.1 or newer is installed to resolve a performance problem.


See our design notes for further information on planning for separate database servers, disk partitioning and security.


Opsview is not currently compatible with Security-Enhanced Linux extensions, this must be disabled.

Edit /etc/selinux/config and restart system:

# 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.
# SELINUXTYPE= type of policy in use. Possible values are:
#       targeted - Only targeted network daemons are protected.
#       strict - Full SELinux protection.
# SELINUXTYPE=targeted


There is a dependency on the Java JDK (rather than the SDK). The rpm must be java - if you are using jdk from the java website, you should rebuild the package by following the instructions here. Java is required for the PDF reports that Opsview can produce.



See the installation prerequisites information to setup users, groups and MySQL.

Our documentation refers to MySQL, but MariaDB is used for RHEL7

Network Ports

On RHEL7, you will need to amend the firewall to allow port 80 to access the web interface. See this page for details about the ports used by Opsview.


You only to include the RPMforge repositories for RHEL5

Opsview will need to have the RPMForge repository configured to install any necessary dependancies by downloading and installing the RPMForge release package (you may need to install wget first):

wget http://packages.sw.be/rpmforge-release/rpmforge-release-0.5.3-1.el5.rf.<ARCH>.rpm
rpm -Uhv rpmforge-release-0.5.3-1.el5.rf.<ARCH>.rpm

Where <ARCH> is either i386 or x86_64

If the site specified in the above wget is not available, there is a list of alternative sites to obtain the package on the RPMForge web site.

Red Hat repositories

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


The Red Hat Extra Server 7 repositories must be enabled via RHN.

  • Log in
  • Select RHEL7 system name
  • Alter channel subscription to include “RHEL Server Optional (v. 7 for xx-bit)”

Alternatively, you can run the command (depending on your architecture):

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


The Red Hat Optional Server 6 repositories must be enabled via RHN.

  • Log in
  • Select RHEL6 system name
  • Alter channel subscription to include “RHEL Server Optional (v. 6 for xx-bit)”

Alternatively, you can run the command (depending on your architecture):

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

Opsview repositories

Then, use your favourite editor to create the file /etc/yum.repos.d/opsview.repo Use this link below for further instructions:



Once the repositories have been updated to include the Opsview yum repository, the latest release of Opsview can be installed by running the following command as root.

yum install opsview

Note: if rrdtool is > 1.3, then you will also need to install

  • dejavu-lgc-fonts.

After the installation is complete

After the Opsview packages have been installed, it is necessary to configure Opsview and its databases.

1. Ensure the MySQL root password has been set to a known value:

mysqladmin -u root password {password}

If you get an error like:

error: 'Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'

Then mysql has not been started. Start it with

/etc/init.d/mysqld start

and ensure it is set to start at boot time with chkconfig –level 345 mysqld on.

See the Mysql setup page for more general mysql settings.

2. Ensure the nagios user's environment is set up correctly. Opsview will try to set the correct profile, but check that the following line is in the profile script, depending on your shell (e.g. .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

3. The rest of the steps should be performed as the nagios user

su - nagios

4. As of Opsview 4.6's “Security wallet” feature, all passwords on fresh installations are encrypted by default. You can view the encrypted values of these items by opening the opsview.conf file at the location below:

vi /usr/local/nagios/etc/opsview.conf

For more information regarding security wallet, click here: http://docs.opsview.com/doku.php?id=opsview4.6:securitywallet

5. Set up the Opsview mysql database users with the necessary permissions

/usr/local/nagios/bin/db_mysql -u root -p{mysql root password}

6. Install the required databases

/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

7. Generate all the necessary configuration files:

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

8. You can now start up the web application server:

/etc/init.d/opsview-web start

The Opsview server is now listening on port 3000, i.e. http://opsview.example.com:3000/

Using Apache as a proxy server

The performance of Opsview will be significantly improved by using Apache at the front end. All the following commands should be run as root.

1. Ensure the line “LoadModule proxy_http_module modules/mod_proxy_http.so” is uncommented in /etc/httpd/conf/httpd.conf.

2. Create /etc/httpd/conf.d/opsview.conf:

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

You may need to comment out the DocumentRoot variable in /etc/httpd/conf/httpd.conf.

3. Amend the apache web server user group membership to include nagcmd group

usermod -G nagcmd apache

Check to ensure the apache user is correct for your web software.

If you use a centralised user management system, you may need to amend /etc/group manually. To test that the permissions are set correctly, run id apache and look for the nagcmd group.

4. Restart Apache

/etc/init.d/httpd restart

You can now access Opsview at http://your.server/

Logging in

Once Opsview has been installed, a single administrative user will have been created. The credentials for this user are:

username: admin
password: initial

You should change this password to prevent unauthorised access to Opsview - this can be done from 'Administrator' link in the top right of the page.

See the quick start guide for an introduction to Opsview


Apache: 503 server temporarily unavailable

If you try to connect to: “http://your.server/” you may be greeted with a 503 server temporarily unavailable error. Go to the command line and enter:

setsebool -P httpd_can_network_connect=1

Try navigating to that address again.

Automatic dependencies

Yum should automatically work out all dependencies when installing Opsview, but in the event that installing the opsview package does not also bring in opsview-base, opsview-perl, etc then follow these steps

  • Ensure yum-updatesd-helper is not running
  • yum remove opsview
  • yum clean all
  • yum makecache

Running yum deplist opsview should now show the correct dependencies and allow opsview to be installed correctly.