Welcome to docs.opsview.com

This is an old revision of the document!

Installation Guide - SUSE Linux Enterprise Server

Before you start

  • For supported SUSE Linux Enterprise Server releases please refer to platforms.

Unless otherwise stated, all commands should be performed as the root user.

There is a known issue with SLES11 SP3 (and SP2) where a Perl module hangs. This affects the installation of Opsview.

To see the problem, install opsview-perl and run:

perl -I/opt/opsview/perl/lib/perl5 -MLWPx::TimedHTTP -e 0

This appears to be a conflict with libopenssl version 0.9.8j in SLES11 SP3. To resolve this, install updated security packages. For a 32-bit system:

zypper modifyrepo --enable nu_novell_com:SLES11-Extras
curl \
  -LO ftp://ftp.pbone.net/mirror/ftp5.gwdg.de/pub/opensuse/repositories/security:/fips/SLE_11/i586/libopenssl-fips_0_9_8-0.9.8r-3.2.i586.rpm \
  -LO ftp://ftp.pbone.net/mirror/ftp5.gwdg.de/pub/opensuse/repositories/security:/fips/SLE_11/i586/openssl-0.9.8r-3.1.i586.rpm
rpm -U --force openssl-0.9.8r-3.1.i586.rpm libopenssl-fips_0_9_8-0.9.8r-3.2.i586.rpm
zypper remove libopenssl0_9_8

For a 64-bit system:

zypper modifyrepo --enable nu_novell_com:SLES11-Extras
curl \
  -LO ftp://ftp.pbone.net/mirror/ftp5.gwdg.de/pub/opensuse/repositories/security:/fips/SLE_11/x86_64/libopenssl-fips_0_9_8-0.9.8r-3.2.x86_64.rpm \
  -LO ftp://ftp.pbone.net/mirror/ftp5.gwdg.de/pub/opensuse/repositories/security:/fips/SLE_11/x86_64/openssl-0.9.8r-3.1.x86_64.rpm
rpm -U --force openssl-0.9.8r-3.1.x86_64.rpm libopenssl-fips_0_9_8-0.9.8r-3.2.x86_64.rpm
zypper remove libopenssl0_9_8

Thanks to Oliver Gorwits for the report and original workaround.


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



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


If you haven't already done so, enable the Extras repository:

zypper modifyrepo --enable nu_novell_com:SLES11-Extras

And add the Opsview repository.


Once the repositories have been updated to include the Opsview repository, the latest release of Opsview can be installed:

zypper install opsview

When 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 and ensure it will start at boot time:

    service mysql restart
    chkconfig --add mysql

    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):
    . /usr/local/nagios/bin/profile
  3. The remaining steps should be performed as the nagios user:
    su - nagios
  4. Set up the Opsview MySQL database users with the necessary permissions:
    /usr/local/nagios/bin/db_mysql -u root -p<mysql root password>
  5. Install the 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
  6. Generate all necessary configuration files:
    /usr/local/nagios/bin/rc.opsview gen_config
  7. You can now start up the web application server:
    service opsview-web start

The Opsview server is now listening on port 3000, ie. http://localhost: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 the root user.

  1. Using YAST, enable the proxy modules in Apache:
    1. Start yast2
    2. Select Network Services, then HTTP Server
    3. If the wizard starts, navigate to the last step and choose HTTP Server Expert Configuration
    4. Select the Server Modules tab, and enable proxy and proxy_http
  2. Create /etc/apache2/conf.d/opsview.conf:
    <VirtualHost *>
        Include /usr/local/opsview-web/etc/apache_proxy.conf
  3. If you use a centralised user management system, you may need to check that the wwwrun user is a member of the nagcmd group. To see if this is so, run id wwwrun and look for the nagcmd group.
  4. Restart Apache:
    service apache2 restart

You can now access Opsview using Apache.

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 'admin' → 'access profile', top right of the page.

See the quick start guide for an introduction to Opsview

Known issues

  • The Netaudit module does not install on SLES11 SP3. This is because Subversion is missing. We suggest installing Subversion before attempting to install Netaudit.
  • VMware's vSphere SDK does not install. This is because it does not support SLES11.
  • NMIS does not generate graphs.


Authentication to repository does not work

If you keep being requested to enter a password to our repository, it maybe that you have invalid characters in your password. This appears to be a limitation of zypper. Please change your opsview.com password and try again.