Operating Dossier:Doc-centreon1 4

From Wiki Centreon

Included below is a copy of Daniel Sloan's guide originally at: http://danielsloan.org/OreonGettingStarted.

As his site appears to be down and there's precious little English documentation for Centreon/Oreon I've managed to retrieve copies of the pages from the search engine caches and have reformatted them for the wiki.

Pages 1,2,3,4 + 6 are from google cache.

Page 5 is from live.com as strangely neither google or yahoo had caches - seems that site is actually useful for something after all :)

As this was originally published to a wiki I imagine Daniel would have little objection to anyone adding comments, clarifying, or otherwise improving upon the guide.

Daniels original forum post announcing the guide can be found here: http://forum.oreon-project.org/showthread.php?t=2479

Contents 1 Initial Server Build 1.1 Introduction 1.2 Prerequisite Packages 2 Nagios 2.5 2.1 Compiling and Installing Nagios Base Application 2.2 Compiling and Installing Nagios Official Plugins 2.3 Configuring and Testing Nagios 2.5 2.4 Troubleshooting for Nagios 3 Perfparse 3.1 MySQL Security 3.2 Compiling and Installing Perfparse 3.3 Installing Perfparse Database Schema 3.4 Configure integration with Nagios 3.5 Testing Perfparse 3.6 Troubleshooting Perfparse 4 Oreon 4.1 Prerequisites - PEAR Libraries 4.2 Installing Oreon, Part 1 4.3 Installing Oreon, Part 2 4.4 Configuring Oreon 4.5 Testing Oreon 4.6 Troubleshooting Oreon

Initial Server Build

Introduction

First things first - if you don't already have a server set up, you will need to choose what distribution you want to run. There are a lot of people (including myself) using Ubuntu or Debian for Oreon servers, and these distributions both work very well. In fact this Guide was written based on Ubuntu 6.10, so you can expect things to run very smoothly if you are following the instructions to the letter (at least, I hope so!).

The other most popular distribution choice for Oreon seems to be Fedora Core. In reality, any distribution should work, and most of them will (almost) work with this documentation - the one major problem will be differing package names. If you find differences on your distribution, let me know and I'll update the document.

Whatever distribution you use, make sure it’s the most recent release of that distribution, as some of the prerequisites for Oreon require very recent versions of software (eg the PHP PEAR libraries). For this reason installing on a "Long Term Support" style release such as Red Hat Enterprise Linux *might* prove more difficult (I’ll update this if I find out for sure one way or the other).

So, let's get started - I'm not going to lead you through the steps to set up a secure linux server at all, there are plenty of distributions about this. We'll start with the packages that you will need to compile and install Oreon and its companion products Nagios and Perfparse.

Prerequisite Packages

I advise NOT to use pre-built packaged versions of Nagios, PerfParse?, or Oreon (if they exist in your distribution). Generally each package will have been built to run independently, and you may find you have more work to get all three products working together than compiling the software yourself. In addition, every time a package upgrade is released, you run the risk of losing the integration and having to do it all again.

I suggest that at least for your first time with Oreon, follow the process in this Guide rather than using pre-built packages.

So, assuming you are joining me on this journey to compile and install the software, you will need to install the following list of packages. Note I have indicated with a ‘*’ and in red where packages only need to be installed during the course of the compile. Some of these packages are not essential to get a bare-bones Oreon system running, and some of them you may never use (eg LDAP). However once again, I recommend that for your first install to just get everything running.

• snmp
• snmpd
• ldap-utils
• nmap
• fping
• dig
• traceroute
• mailx
• ntpdate
• ntp
• gcc*
• g++*
• binutils*
• make*
• cpp*
• patch*
• libtool*
• libpng
• libpng-dev*
• libc6
• libc6-dev*
• libjpeg
• libjpeg-dev*
• libgd2-xpm
• libgd2-xpm-dev*
• libglib2.0
• libglib2.0-dev*
• libmysqlclient
• libmysqlclient-dev*
• libstdc++6
• libstdc++6-4.1-dev*
• apache2
• libapache2-mod-php5
• php5
• php5-mysql
• php5-ldap
• php5-snmp
• php5-gd
• php-pear
• perl (version >= 5.8)
• libgd-gd2-perl
• librrds-perl
• rrdtool
• libnet-snmp-perl
• gnuplot
• mysql-client
• mysql-server
• libgnutls
• libgnutls-dev
• libpq4
• libpq-dev
• libssl0.9.8
• libssl-dev
• libradius1
• libradius1-dev*
• libbind9-0
• libbind-dev*
• libldap2
• libldap-dev*
• smbclient
• dnsutils
• mail-transport-agent (sendmail, postfix, exim4, etc)

Distribution-specific notes:

   * On Ubuntu, you will likely need to enable the "Universe" repository to access all of these packages.
   * On non-Debian based distributions, the package names may vary somewhat.

If you are security conscious and working with a mission-critical environment, you may want to clone your server into a VMware virtual machine, and do the compiling etc there. This avoids installing any developer tools on your production server (which is generally a Bad Idea, only makes life easier for hackers). Then once the application is working, you can copy it to your production environment (tar up and copy across /usr/local/nagios and /usr/local/oreon, install any packages you installed in the virtual machine, and you’re done). If you do this you’re well on the way to adopting best practice for change/release management as well, by deploying to a test environment before production. However, don't worry I won't come hunting for you just because you don't do it - there is substantially more work involved in doing it that way.

Last but certainly not least, you will need the source packages of the software we will be installing – Nagios, Perfparse, and Oreon. You can find them at these locations (no direct links – versions might change):

   * Nagios 2.5
     http://www.nagios.org/download/
   * Nagios Official Plugins
     http://www.nagios.org/download/
   * Perfparse 1.106.1
     http://prdownloads.sourceforge.net/perfparse/
   * Oreon 1.3.1
     http://www.oreon-project.org/ 

I recommend that all operations on the server from here onward be done using a normal user account with no superuser privileges. I will be using 'sudo' and 'sudo -u nagios' to escalate to root access or assume the user 'nagios' when necessary. If you don’t have sudo, you can use 'su' instead, although its more cumbersome and won’t revert back to normal user privileges without an explicit 'exit' command. Whatever you do, try to avoid running 'root' throughout the whole installation process, as you increase the risk of accidents and of leaving security holes behind in the installation.

I also recommend creating a directory in your user account’s home directory called 'src' or something similar. From here on I will refer to this as “the source directory” or '<srcdir>'.

Nagios 2.5

The first step is to get Nagios installed and tested.

Compiling and Installing Nagios Base Application

First, expand the tarball for Nagios (I’m assuming your tarballs are downloaded into your home directory):

~$ cd <srcdir>

~/src$ tar –xzf ../nagios-2.5.tar.gz

~/src$ tar –xzf ../nagios-plugins-1.4.5.tar.gz

~/src$ ls –l

drwxr-xr-x 11 daniel daniel 4096 2006-07-14 07:58 nagios-2.5

drwxr-xr-x 12 daniel daniel 4096 2006-11-02 08:27 nagios-plugins-1.4.5

~/src$

Now let’s compile and install Nagios. But before we do that we need to set up some users and groups.

~/src$ sudo groupadd nagios

~/src$ sudo useradd –g nagios –d /usr/local/nagios –m nagios

~/src$ sudo useradd –g nagios nagcmd

~/src$

The above users are used for running the Nagios and Perfparse applications. Now we can start compiling.

~/src$ cd nagios-2.5

~/src/nagios-2.5$ ./configure –prefix=/usr/local/nagios --with-nagios-user=nagios --with-nagios-group=nagios --with-nagios-command-user=nagcmd

<...much output from configuration tests...>

~/src/nagios-2.5$

The above line configures what additional options you want to install. If you encounter any errors here, it means you are missing some prerequisite packages. If that happens to you, please contact me with the distribution and error messages, so I can update the documentation! Please note: There are additional options for the above line which may interest you. In particular ‘—enable-embedded-perl’ and ‘–with-perlcache’ are worth investigating if you are monitoring a very large number of hosts and your server is running very slow as a result. However, for normal users those options can introduce additional complexity – I wouldn’t advise using them initially.

Now we are ready to build and install the files.

~/src/nagios-2.5$ make all

<...much output from compiler and make...>

~/src/nagios-2.5$ sudo make install

<...much output from compiler and make...>

~/src/nagios-2.5$ sudo make install-init

<...much output from compiler and make...>

~/src/nagios-2.5$ sudo make install-commandmode

<...much output from compiler and make...>

~/src/nagios-2.5$ sudo make install-config

<...much output from compiler and make...>

~/src/nagios-2.5$

One last item which doesn’t auto-copy…

~/src/nagios-2.5$ sudo -u nagios cp sample-config/httpd.conf /usr/local/nagios/etc/

~/src/nagios-2.5$

Compiling and Installing Nagios Official Plugins

Next, we need to compile and install the nagios plugins, which are in a seperate tarball.

~/src/nagios-2.5$ cd ..

~/src$ tar -xzf ../nagios-plugins-1.4.5.tar.gz

~/src$ cd nagios-plugins-1.4.5

~/src/nagios-plugins-1.4.5$ ./configure --prefix=/usr/local/nagios --with-openssl

<...much output from configuration tests...>

~/src/nagios-plugins-1.4.5$ make

<...much output from compiler and make...>

~/src/nagios-plugins-1.4.5$ sudo make install

<...much output from compiler and make...>

~/src/nagios-plugins-1.4.5$

Again, if you encountered any errors in this process, please let me know including the distribution you are using and the errors.

At this point, you should have a complete Nagios installation in /usr/local/nagios/ The next step is to make sure Apache is configured, access Nagios via a webpage, and test that it is able to monitor correctly.

Configuring and Testing Nagios 2.5

To test Nagios, we will get the Apache configuration working and set up the Nagios web interface. Ultimately you will probably want to disable this interface, or at least make it hard to get to, since Oreon will replace the Nagios web functionality once we install it.

First, lets set up the Nagios configuration files. In the directory /usr/local/nagios/etc, you should find some sample configuration files which have been prepared for you. Perform the following commands to activate those configuration files:

~/src/nagios-plugins-1.4.5$ cd /usr/local/nagios/etc

/usr/local/nagios/etc$ sudo –u nagios mv nagios.cfg-sample nagios.cfg

/usr/local/nagios/etc$ sudo –u nagios mv resource.cfg-sample resource.cfg

/usr/local/nagios/etc$ sudo –u nagios mv minimal.cfg-sample minimal.cfg

/usr/local/nagios/etc$ sudo –u nagios mv cgi.cfg-sample cgi.cfg

/usr/local/nagios/etc$ sudo –u nagios sh –c "echo '#' > misccomands.cfg"

/usr/local/nagios/etc$ sudo –u nagios sh –c "echo '#' > checkcommands.cfg"

/usr/local/nagios/etc$ sudo /etc/init.d/nagios stop

/usr/local/nagios/etc$ sudo /etc/init.d/nagios start

/usr/local/nagios/etc$

Now, we need to configure Apache. In most cases, the directory we need is /etc/apache2/conf.d/. However, if the directory doesn’t exist, have a look through your distribution’s documentation to find out where it puts this directory.

Once you find it, do the following commands. Substitute /etc/apache2/conf.d/ for the correct path if yours is different, and enter a password of your own choice as well (don’t change the username):

/usr/local/nagios/etc$ cd /etc/apache2/conf.d

/etc/apache2/conf.d$ sudo ln –s /usr/local/nagios/etc/httpd.conf nagios

/etc/apache2/conf.d$ sudo /etc/init.d/apache2 restart

/etc/apache2/conf.d$ sudo -u nagios htpasswd –c –m /usr/local/nagios/etc/htpasswd.users username nagios-admin

Password: <enter password for nagios-admin>

/etc/apache2/conf.d$ sudo chgrp www-data /usr/local/nagios/etc/htpasswd.users

/etc/apache2/conf.d$ sudo -u nagios chmod ug+rw /usr/local/nagios/etc/htpasswd.users

/etc/apache2/conf.d$

Now we can launch a web browser from the server or another machine and test that we can access the server’s Nagios interface. Open a browser and go to the following URL:

http://<servername>/nagios/

If you get a message to enter a username and password, enter the username as ‘nagios-admin’ and password you just configured. Once logged in, click on “Service Detail” on the left hand side. You should be able to see a list of services for ‘localhost’, and they should (probably) be green and indicating “OK”.

Troubleshooting for Nagios

This section still to be completed, partly it will be based on feedback as people make use of this documentation

Perfparse

Now that we have Nagios functioning, it is time to install Perfparse. A prerequisite of Perfparse (and Oreon as it happens) is MySQL, so before we get started let’s set up the MySQL server. You can either install MySQL on the local server (recommended for first-time installations) or you can run it on a second server and access it over the network (make sure it’s a good reasonably fast (100Mbit) network connection though!)

I assume you have installed mysql-server locally (remember I listed it in the prerequisites?). I recommend at least version 4.1, version 5.0 is even better.

MySQL Security

Before we do anything else, configure a better password for the administrator. Many systems set a default of nothing, or a standard password.

~$ mysqladmin –u root -p password '<password>'

Password: <enter your current MySQL root password, probably empty so just hit the enter key>

~$

There is a lot that can be done to fine-tune MySQL, but that’s a topic for another time and another article.

Compiling and Installing Perfparse

So, let's move on to compiling and installing the perfparse application.

~$ cd ~/<srcdir>

~/src$ tar –xzf ../perfparse-0.106.1.tar.gz

~/src$ cd perfparse-0.106.1

~/src/perfparse-0.106.1$ ./configure --prefix=/usr/local/nagios

<...much output from configuration tests...>

~/src/perfparse-0.106.1$ make

<...much output from compiler and make...>

~/src/perfparse-0.106.1$ make install

<...much output from compiler and make...>

~/src/perfparse-0.106.1$ sudo chown –Rc nagios.nagios /usr/local/nagios/*

~/src/perfparse-0.106.1$

Now, you need to tell the operating system where to find the perfparse library. Personally the method I prefer is editing 'ld.so.conf', since it almost always works regardless of distribution or other variations. On really new linux distributions, there might be a directory called '/etc/ld.so.conf.d/' – if you have this directory, just do the following:

~/src/perfparse-0.106.1$ sudo sh –c 'echo "/usr/local/nagios/lib" > /etc/ld.so.conf.d/perfparse'

~/src/perfparse-0.106.1$

If the directory '/etc/ld.so.conf.d/' doesn’t exist, use the following command:

~/src/perfparse-0.106.1$ sudo sh –c 'echo "/usr/local/nagios/lib" >> /etc/ld.so.conf.d/perfparse'

~/src/perfparse-0.106.1$

Both commands achieve the same result, but the first one is better as it makes it clear what application owns the library (perfparse). Now update the cache:

~/src/perfparse-0.106.1$ sudo ldconfig

~/src/perfparse-0.106.1$

Installing Perfparse Database Schema

Next, we need to create the MySQL schema for Perfparse. This is pretty easy, but you will need to start up a MySQL shell to do it.

~/src/perfparse-0.106.1$ mysql –u root –p

mysql> CREATE DATABASE perfparse;

mysql> USE perfparse;

mysql> \. scripts/mysql_create.sql

mysql> GRANT ALL ON perfparse.* TO 'perfparse'@'%' IDENTIFIED BY ;

mysql> FLUSH PRIVILEGES;

mysql> \q

~/src/perfparse-0.106.1$

Configure integration with Nagios

Finally we are done, and Perfparse is ready to run. Next, we need to set it up to integrate with Nagios. There is more than one way to do this, and although there is an easier way, the way I am documenting here is the recommended method. We will use a FIFO pipe and the perfparsed daemon application to collect service perfdata from Nagios. There are several benefits to using this method...

   * The data arrives in the Perfparse database almost instantly.
   * Perfparsed is loaded into memory, instead of needing to be executed periodically (the latter incurs a higher CPU overhead).
   * Nagios treats the FIFO as a normal file - as far as it is concerned it is just writing perfdata to a file, which reduces complexity of Nagios configuration. 

The major drawback is that to understand what is happening, you need to know about FIFO pipes. If you want, look up the manpage for 'mkfifo', it may provide some understanding. I'll include some better links later for this topic.

To start with, we need to set up Nagios properly. Edit the file /usr/local/nagios/etc/nagios.cfg, and change the following settings:

process_performance_data=1

service_perfdata_file_template=$TIMET$\t$HOSTNAME$\t$SERVICEDESC$\t$SERVICEOUTPUT$\t$SERVICESTATE$\t$SERVICEPERFDATA$

service_perfdata_file_mode=w

service_perfdata_file=/usr/local/nagios/var/service-perfdata

Now we can restart Nagios with the new settings. But we also need to configure the Perfparse daemon (/usr/local/nagios/bin/perfparsed) and set it up to start right before Nagios does.

Start up your editor for the file /usr/local/nagios/etc/perfparse.cfg (which may not exist yet), and configure the following settings:

Server_Port = ""

Service_Log = "|/usr/local/nagios/var/service-perfdata"

Error_Log = "/usr/local/nagios/var/perfparse.log"

Error_Log_Rotate = "Yes"

Error_Log_Keep_N_Days = "7"

Drop_File = "/tmp/perfparse.drop"

Drop_File_Rotate = "Yes"

Drop_File_Keep_N_Days = "7"

Lock_File = "/usr/local/nagios/var/lock.perfparse"

Show_Status_Bar = "no"

Do_Report = "no"

Default_user_permissions_Policy = "rw"

Default_user_permissions_Host_groups = "rw"

Default_user_permissions_Summary = "rw"

Output_Log_File = "yes"

Output_Log_Filename = "/usr/local/nagios/var/output_perfparse.log"

Output_Log_Rotate = "yes"

Output_Log_Keep_N_Days = "7"

Use_Storage_Socket_Output = "no"

Use_Storage_Mysql = "yes"

No_Raw_Data = "no"

No_Bin_Data = "no"

DB_User = "perfparse"

DB_Name = "perfparse"

DB_Pass = ""

DB_Host = "127.0.0.1"

Dummy_Hostname = "linux"

Storage_Modules_Load = "mysql"

Testing Perfparse

At this point we should try starting Perfparse and restarting Nagios to see if Perfparse is working properly. Stop Nagios, make sure there is no such file as /usr/local/nagios/var/service-perfdata, then start perfparsed and check it is running. Finally, start Nagios again and make sure it is running.

~/src/perfparse-0.106.1$ sudo /etc/init.d/nagios stop

~/src/perfparse-0.106.1$ rm -f /usr/local/nagios/var/service-perfdata

~/src/perfparse-0.106.1$ sudo -u nagios /usr/local/nagios/bin/perfparsed -d

~/src/perfparse-0.106.1$ ps ax | grep perfparse

3909 ? S 0:00 /usr/local/nagios/bin/perfparsed -d

3985 pts/0 S+ 0:00 grep perfparse

~/src/perfparse-0.106.1$ sudo /etc/init.d/nagios start

~/src/perfparse-0.106.1$ ps ax | grep nagios

3939 ? Ssl 0:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg

3964 pts/0 S+ 0:00 grep nagios

~/src/perfparse-0.106.1$

Check to make sure Nagios is monitoring properly (go to a web browser and access the URL 'http://<servername>/nagios/').

To test that data is being collected by Perfparse, wait 10 or 15 minutes, then go to a web browser and access the URL:

http://<servername>/nagios/cgi-bin/perfparse.cgi

Click on ‘View Raw Plugin Data’ - if you can see values in a table on that page, and they are updating every 5 or 10 minutes, perfparse is probably working.

Troubleshooting Perfparse

This section still to be completed, partly it will be based on feedback as people make use of this documentation

Oreon

Now the easy part!! Well…maybe…we will see...

Prerequisites - PEAR Libraries

At this point you should already have PHP 5 and PHP Pear installed, however it is very likely your Pear installation is not up to date enough to run Oreon. Fortunately, even if your distribution is “behind the times”, Pear includes a nice little installer/upgrader that should work anyway. First we will need to upgrade to the latest version of Pear, then we upgrade any other already installed modules. Finally, we install the modules we need for Oreon.

Run the following commands:

~$ sudo pear channel-update pear.php.net

<...much output about downloads and installations...>

~$ sudo pear upgrade PEAR

<...much output about downloads and installations...>

~$ sudo pear upgrade-all

<...much output about downloads and installations...>

~$ sudo pear install –f --alldeps DB DB_DataObject MDB2 Date Numbers_Roman Numbers_Words HTML_Common HTML_QuickForm

<...much output about downloads and installations...>

~$ sudo pear install –f --alldeps HTML_QuickForm_advmultiselect HTML_Table Archive_Tar Auth_SASL Console_Getopt HTTP Image_Canvas Image_Color

Image_Graph Image_GraphViz

<...much output about downloads and installations...>

~$ sudo pear install –f --alldeps Mail Mail_Mime Net_SMTP Net_Socket Net_Traceroute Net_Ping Validate XML_RPC

<...much output about downloads and installations...>

~$ sudo pear install –f --alldeps DB_DataObject_Formbuilder

<...much output about downloads and installations...>

~$

At this point, all PEAR libraries should be up-to-date. If anything is missing, it will be flagged during Oreon's installation process. At that point, you can try re-running the 'pear' application to see if any further upgrades are available.

Installing Oreon, Part 1

Finally we are ready to install the REAL application! Expand the tarball and run the installer as root.

Note: you should run the installer with ‘/bin/bash ./install.sh’ instead of ‘./install.sh’, as some distributions (eg Ubuntu 6.10) use Dash or other shells as their ‘/bin/sh’, and they wont run the installer properly.

Note also the ‘locate’ commands we run, which are to ensure we know the answers to the questions in the installer. Hopefully this is reasonably self-evident. Also note that while you can just press the enter key to accept the default when it is correct, I have explicitly written every answer to the installer so you can see it clearly.

~$ cd <srcdir>

~/src$ tar –xzf ../oreon-1.3.1-1.tar.gz

~/src$ cd oreon-1.3.1-1

~/src/oreon-1.3.1-1$ locate –r RRDs.pm$

/usr/lib/perl5/RRDs.pm

~/src/oreon-1.3.1-1$ locate –r sudoers$

/etc/sudoers

/usr/share/doc/sudo/examples/sudoers

~/src/oreon-1.3.1-1$ locate –r rrdtool$

/usr/bin/rrdtool

/usr/share/doc/rrdtool

~/src/oreon-1.3.1-1$ locate –r mail$

/usr/bin/mail

/usr/bin/rmail

/usr/bin/traptoemail

/usr/lib/python2.4/email

/usr/lib/sendmail

/usr/sbin/rmail

/usr/sbin/sendmail

/var/mail

~/src/oreon-1.3.1-1$ locate –r PEAR.php$

/usr/share/php/PEAR.php

~/src/oreon-1.3.1-1$ sudo /bin/bash ./install.sh

Are you sure to continue ?

[[y/n], default to [n]: y

Where is installed Nagios ?

default to [/usr/local/nagios]: /usr/local/nagios

Where are your nagios etc directory ?

default to [/usr/local/nagios/etc]: /usr/local/nagios/etc

Path /usr/local/nagios/etc/nagios.cfg OK

Where are your nagios plugins / libexec directory ?

default to [/usr/local/nagios/libexec]: /usr/local/nagios/libexec

Where are your nagios bin directory ?

default to [/usr/local/nagios/bin]: /usr/local/nagios/bin

Where do I install Oreon ?

default to [/usr/local/oreon]: /usr/local/oreon

Where is sudo ?

default to [/etc/sudoers]: /etc/sudoers

Where is installed RRD perl modules (RRDs.pm) ?

Just put directory, not full path.

default to [/usr/local/rrdtool/lib/perl]: /usr/lib/perl5

Where is rrdtool binary ?

default to [/usr/bin/rrdtool]: /usr/bin/rrdtool

/usr/bin/rrdtool OK

Where is mail binary ?

default to [/usr/bin/mail]: /usr/bin/mail

/usr/bin/mail OK

Where is PEAR Path ?

default to [/usr/share/pear]: /usr/share/php

<...pages of output about installation parameters, checks, etc...>

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

$$

$$ Go to the URL : http://your-server/oreon/external link to finish the setup

$$

$$ Report bugs at bugs@oreon-project.org

$$

$$ Thanks for using OREON.

$$ -----------------------

$$ Contact : infos@oreon-project.org

$$

$$ http://www.oreon-project.orgexternal link

$$

$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$

Installing Oreon, Part 2

So…do what the last command told you to do lol Open a browser either on the server or from another machine, and open the URL ‘http://<yourservername>/oreon/’. From there a set of instructions will prompt you each step of the way...we will follow those instructions where necessary with a set of screenshots. In most cases, as long as there are no errors on a page in most cases you can just click “Next”, “I Accept”, etc (although I suggest you should read everything too!).

This screen requires you to change Nagios Version to 2.x.

A few screens later (hopefully with no problems) you will get this screen, enter the database name you want to use for Oreon (probably should not be the same one as for Perfparse, although it will work).

Enter an administrator name and password, etc.

Onto the next one...hmm, seems cool, LDAP authentication, right? Well, here’s some advice – leave this OFF for now. Switch it on after you install, its safer. If you are not careful with LDAP authentication, you can lock yourself out of your own Oreon installation!

Ignore this advice, since for one thing the path is wrong, and for another, I’m going to tell you about it anyway. wink

Configuring Oreon

TODO:

- Cron job configuration - Setting up Perfparse, Oreon, and Nagios to run automatically.

Testing Oreon

TODO:

- Basic "Get everything working" in Oreon and test it.

Troubleshooting Oreon

TODO: To be written.