Welcome to docs.opsview.com

Installation Guide - RPM's

This guide is for users of RHEL5 or CentOS5 without direct access to the internet and is geared towards a base install (i.e. without any software groups installed).

Before you start

  • For supported CentOS/RHEL Linux releases, see our official platforms list
  • Please ensure perl 5.8.8-15 or newer is installed to resolve a performance problem

Planning

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

Security settings

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

Opsview servers should be located in a secure area of your network. If you allow Opsview to be available on a public network, we recommend a firewall to restrict access to various ports. See this page for ports used by Opsview.

If a firewall is active on the host then ports 80 should be opened up for access. In iptables this can be done by adding the following lines to /etc/sysconfig/iptables

  -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 80 -j ACCEPT

and then restarting iptables

/etc/init.d/iptables restart

Dependencies

From the OS installation media

Install the following packages from the OS installation media

  • acl
  • alsa-lib
  • apr
  • apr-util
  • audiofile
  • avahi
  • avahi-glib
  • chkfontpath
  • cups-libs
  • dbus
  • dbus-libs
  • esound
  • freetype
  • gamin
  • GConf2
  • gd
  • gdbm
  • ghostscript
  • ghostscript-fonts
  • giflib
  • gnome-keyring
  • gnome-mime-data
  • gnome-mount
  • gnome-vfs2
  • gtk2
  • httpd
  • java
  • jpackage-utils
  • libacl
  • libbonobo
  • libbonoboui
  • libcroco
  • libdaemon
  • libdbi
  • libfontenc
  • libFS
  • libgnome
  • libgnomecanvas
  • libgnomeui
  • libgsf
  • libIDL
  • libnotify
  • libpng
  • librsvg2
  • libsysfs
  • libtiff
  • libtool-ltdl
  • libusb
  • libvolume_id
  • libwnck
  • libXcursor
  • libXfont
  • libXpm
  • libXres
  • libxslt
  • libXtst
  • lm_sensors
  • mod_ssl
  • mrtg
  • mysql
  • mysql-server
  • net-snmp
  • net-snmp-libs
  • net-snmp-perl
  • net-snmp-utils
  • notification-daemon
  • ORBit2
  • pango
  • perl-Archive-Zip
  • perl-Compress-Zlib
  • perl-DBD-MySQL
  • perl-DBI
  • perl-HTML-Parser
  • perl-HTML-Tagset
  • perl-PerlIO-gzip
  • perl-IO-Socket-INET6
  • perl-IO-Socket-SSL
  • perl-libwww-perl
  • perl-Net-SSLeay
  • perl-Socket6
  • php
  • php-cli
  • php-common
  • php-mysql
  • php-pdo
  • pkgconfig
  • popt
  • postgresql-libs
  • rpm
  • rpmforge-release
  • rpm-libs
  • rpm-python
  • ruby
  • ruby-irb
  • ruby-libs
  • ruby-rdoc
  • shared-mime-info
  • startup-notification
  • ttmkfdir
  • urw-fonts
  • xorg-x11-fonts-Type1
  • xorg-x11-font-utils
  • xorg-x11-xfs

From RPMForge

Download the following packages appropriate for your OS/arch from http://packages.sw.be/ and install

  • lua
  • perl-rrdtool (located in the rrdtool directory)
  • rrdtool
  • tslib
  • directfb
  • libmcrypt
  • graphviz
  • perl-Compress-Raw-Zlib
  • perl-IO-Compress-Base
  • perl-IO-Compress-Zlib

These rpm's are best installed together due to the dependencies between them, such as (assuming the rpm's are in a directory by themselves)

yum localinstall *.rpm

Preparation

Navigate to https://downloads.opsview.com/k/<REPOSITORY_KEY>/opsview-commercial/latest/yum/rhel/ with your web browser, replacing <REPOSITORY_KEY> with your own key as described here, and download the following files appropriate for your system

opsview-base
opsview-perl
opsview-core
opsview-web
mod_auth_tkt_opsview
opsview-jasper
opsview-reporting-module

and transfer these to your Opsview server.

As root you should then install these packages by running

yum localinstall --nogpgcheck opsview-base* opsview-perl* opsview-core* opsview-web* opsview-reporting-module* opsview-jasper* mod_auth_tkt_opsview*

Installation

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 Opsview 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://your.server: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. Edit the apache configuration files and enable proxy_html

cd /etc/httpd/conf
vi httpd.conf
# Ensure the line "LoadModule proxy_http_module modules/mod_proxy_http.so" is uncommented

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

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

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 - click on the top right Administrator link to view and edit your profile.

Upgrading Opsview

Backups should be taken before upgrading Opsview.

Download and install the latest opsview rpm's as per the preparation section above

Navigation
Print/export
Toolbox