Welcome to docs.opsview.com

Installation Guide - SUSE Linux Enterprise Server

Before you start

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

There is a known issue with SLES11 SP2 where a perl module hangs, which affects the installation of Opsview. This is raised at https://rt.cpan.org/Ticket/Display.html?id=81575.

To recreate, install opsview-perl and run:

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

This appears to be a conflict with libopenssl version 0.9.8j-0.44.1 in SLES11 SP2. Please upgrade to version 0.9.8r which is available at http://download.opensuse.org/repositories/security:/fips/.

Thanks to Oliver Gorwits for the report and workaround.

Planning

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

Preparation

Prerequisites

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

Repositories

Enable the Extras repo

# zypper mr -e nu_novell_com:SLES11-Extras

Also install MRTG from an appropriate openSUSE repository. You can find a suitable RPM for SLES11 - choose the appropriate architecture. You may need to install gd using zypper first:

# zypper install gd

Opsview repositories

Use zypper to add in the Opsview repository

# zypper addrepo http://downloads.opsview.com/opsview-core/latest/yum/sles/11/<ARCH> 'Opsview Core'

where ARCH is one of

  • i386
  • x86_64

Installation

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

# zypper refresh
# zypper install opsview

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/mysql start

and ensure it is set to start at boot time with chkconfig -s mysql 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. Edit the opsview configuration file and amend the password as you see fit to secure the system (those passwords that should be changed as they are set to changeme by default). Note that any service checks for MySQL systems will also require the default password of changeme to be amended.

Note: Do not use any funny shell characters in the password, such as $ or !.

vi /usr/local/nagios/etc/opsview.conf   # change passwords in this file

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

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/

To secure your instance of Opsview Web, you should change the authtkt secret to be unique to this instance. In /usr/local/nagios/etc/opsview.conf, add the following and change the secret value to be a unique string:

$authtkt_shared_secret = "shared-secret-please-change";

Restart Opsview Web for this value to take effect: /etc/init.d/opsview-web restart.

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. Using YAST enable the proxy modules in Apache

1. Start yast as root
2. Select ''Network Services => HTTP Server''
3. Select ''Server Modules'' tab and enable ''proxy'', ''proxy_http'' and ''proxy_connect'' (Note: ensure proxy_http is used before proxy_connect in the modules list else Nagvis may not function correctly)

2. For Opsview versions since 20131125, create /etc/apache2/conf.d/opsview:

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

For previous versions, copy in the example Apache configuration file and edit to suite your needs:

cd /etc/apache2/conf.d
cp /usr/local/nagios/installer/apache_proxy.conf opsview.conf
vi opsview.conf

Then, edit the Apache configuration file so that the same shared secret is used:

TKTAuthSecret "shared-secret-please-change"

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

usermod -G nagcmd wwwrun

Check to ensure the wwwrun 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 wwwrun and look for the nagcmd group.

4. Restart Apache

/etc/init.d/apache2 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

Navigation
Print/export
Toolbox