Difference between revisions of "Pandora: Documentation en: Installing"

From Pandora FMS Wiki
Jump to: navigation, search
(Software Requirements)
(Software Requirements)
Line 34: Line 34:
 
* FreeBSD 9.1
 
* FreeBSD 9.1
 
* Solaris 10 / OpenSolaris
 
* Solaris 10 / OpenSolaris
 +
 +
=== Database Requirement ===
 +
 +
Prior to install Pandora FMS you need a MySQL Database running (Oracle and PostgreSQL support is still experimental). That means, before installing Pandora FMS you will need to have a MySQL Server running in a server, could be the same server you will install Pandora FMS into or a separate server, accesible from your Pandora FMS server/console using TCP/IP network. So you need:
 +
 +
* '''IP Address of your MySQL Server''' (localhost if is installed in the same Pandora FMS server host).
 +
* '''User with privileges''' to create databases and users (usually root). This user must be allowed to connect from the IP address of your Pandora FMS server host.
 +
* '''Password''' for privileged user.
 +
 +
 +
{{Warning|You need this to be up and running BEFORE installing Pandora FMS. If you don't know how to install a MySQL server, please check online documentation about the full process on how to do that, because it changes in different operating systems and Linux distros.}}
 +
 +
=== Agent Requirement ===
 +
 +
The remote agent is able to run on any hardware that can run the minimum required operating system:
  
 
Besides Linux, Pandora FMS agents works on following systems:
 
Besides Linux, Pandora FMS agents works on following systems:
Line 51: Line 66:
 
* Windows 2012
 
* Windows 2012
  
=== Database Requirement ===
 
 
Prior to install Pandora FMS you need a MySQL Database running (Oracle and PostgreSQL support is still experimental). That means, before installing Pandora FMS you will need to have a MySQL Server running in a server, could be the same server you will install Pandora FMS into or a separate server, accesible from your Pandora FMS server/console using TCP/IP network. So you need:
 
 
* '''IP Address of your MySQL Server''' (localhost if is installed in the same Pandora FMS server host).
 
* '''User with privileges''' to create databases and users (usually root). This user must be allowed to connect from the IP address of your Pandora FMS server host.
 
* '''Password''' for privileged user.
 
 
 
{{Warning|You need this to be up and running BEFORE installing Pandora FMS. If you don't know how to install a MySQL server, please check online documentation about the full process on how to do that, because it changes in different operating systems and Linux distros.}}
 
 
=== Agent Requirement ===
 
 
The remote agent is able to run on any hardware that can run the minimum required operating system:
 
 
*Windows 2000 SP3
 
*Windows 2003
 
*Windows XP
 
*Windows Vista
 
*Windows 2008
 
*Windows 7
 
*Windows 8
 
*Linux and Unix (see supported versions/distros and version at the begin of this chapter)
 
 
<br>
 
<br>
 
{{Tip|It is known that the agent has been implemented successfully in other operating systems, but there is no official support. The agent does not work in Windows NT4. To monitor previous Windows systems, you can install Cygwin environment and install the agent for Linux, although the performance is much lower than native Windows agent.}}
 
{{Tip|It is known that the agent has been implemented successfully in other operating systems, but there is no official support. The agent does not work in Windows NT4. To monitor previous Windows systems, you can install Cygwin environment and install the agent for Linux, although the performance is much lower than native Windows agent.}}

Revision as of 08:36, 19 June 2013

Go back to Pandora FMS documentation index

Contents

1 Pandora FMS Installation

1.1 Minimum Hardware Requirements

1.1.1 Console and Server Requirements

  • Up to 500 agents or 5.000 modules: 3GB of RAM, a single-core CPU at 2.5GHz clock, and a fast hard disk, 7200rpm or equivalent. Assuming a 80% of modules with history and an average interval of 5 min.
  • Up to 2.000 agents or 10.000 modules: 6GB of RAM, a dual core CPU clock to 2.5GHz, and faster hard drive (10000 rpm or more). Assuming a 80% of modules with history and an average interval of 5 min. You need to tune up your MySQL very well.
  • For more than 4.000 agents: 12GB of RAM, a quad-core CPU to 3GHZ and very fast hard drive (15,000 rpm or more). Assuming a 80% of modules with history and an average interval of 5 min. It's recommended to have MySQL in another server. You need to tune up your MySQL very well, and/or install Percona XtraDB.

Template warning.png

It is *not* advisable to use Pandora FMS in virtualized environmennts, since the disk access requirements are very strict. In case you are willing to do so, it is a must to assign independent RAM, CPU and disks, instead of using part of the host resources. It is more than advisable to use SAN disks in this kind of environments.

 


Info.png

Is's only possible to use Pandora FMS in virtual enviroments for testing, certification or development enviroments, but never in production systems

 


Disk size: A minimum of 15GB free space, it's recommended to have 25GB.

1.2 Software Requirements

Official supported plattform for Pandora FMS is Linux, and we support, for the server and agent, the following Linux distros and versions:

  • RedHat Enterprise (RHEL) 6.x
  • CentOS 6.x
  • SLES 11 SP1 or higher.
  • OpenSUSE 11.x or higher.
  • Debian 5.x or higher.
  • Ubuntu 11 or higher.

Other plattforms where Pandora FMS works, but we don't offer official support are:

  • FreeBSD 9.1
  • Solaris 10 / OpenSolaris

1.2.1 Database Requirement

Prior to install Pandora FMS you need a MySQL Database running (Oracle and PostgreSQL support is still experimental). That means, before installing Pandora FMS you will need to have a MySQL Server running in a server, could be the same server you will install Pandora FMS into or a separate server, accesible from your Pandora FMS server/console using TCP/IP network. So you need:

  • IP Address of your MySQL Server (localhost if is installed in the same Pandora FMS server host).
  • User with privileges to create databases and users (usually root). This user must be allowed to connect from the IP address of your Pandora FMS server host.
  • Password for privileged user.


Template warning.png

You need this to be up and running BEFORE installing Pandora FMS. If you don't know how to install a MySQL server, please check online documentation about the full process on how to do that, because it changes in different operating systems and Linux distros.

 


1.2.2 Agent Requirement

The remote agent is able to run on any hardware that can run the minimum required operating system:

Besides Linux, Pandora FMS agents works on following systems:

  • HPUX 11.x or higher, with Perl 5.8.
  • AIX 4.3.3 or higher, with Perl 5.8.
  • BSD (NetBSD, OpenBSD, FreeBSD), with Perl 5.8.
  • MacOSX.
  • Solaris 8 or higher, with Perl 5.8.
  • Windows NT4 (see special version notes).
  • Windows XP
  • Windows 2000
  • Windows 2003
  • Windows 2008
  • Windows 7
  • Windows 8
  • Windows 2012


Info.png

It is known that the agent has been implemented successfully in other operating systems, but there is no official support. The agent does not work in Windows NT4. To monitor previous Windows systems, you can install Cygwin environment and install the agent for Linux, although the performance is much lower than native Windows agent.

 


Furthermore on UNIX platforms, you must have installed:

  • Perl 5.8 or greater.
  • Optionally unzip package and executable via path by the user of Pandora FMS Agent. (This package is required only if you will use file collection).
  • Optionally, if you want to use the local inventory plugin and get information from hardware, you must install the tool lshw and let it accesible/executable from system path.

1.2.3 Server Requirements

Although you can work on any operating system with Perl 5.8 installed with iThreads enabled.

Should be noted that Pandora FMS requires a MySQL server to store all information. This server can be installed on any platform supported by MySQL. This could be Windows, Linux, Solaris, etc.

It must have Perl 5.8 installed, at least for the server to work well. In addition to the operating system SNMP packets (net-snmp) to use the Pandora FMS SNMP service, it also requires a database (MySQL). Also required nmap packages and optionally xprobe2 to use the advanced features of reconserver and traceroute Perl libraries to be able to self-discovery network. It is also necessary, the WMI client binary for WMI queries against Windows systems. The client binary is part of the SAMBA project (v4) and can be compiled, not without some difficulty in any Unix environment.

1.2.4 Console Requirements

Same as the server, we recommend its operation being on Linux systems, but like the web interface it's a pure AMP application (Apache, MySQL and PHP), theoretically it could work on any system that supports Windows, Unix, etc..

1.2.5 Requirements to Administer the Tool via WEB

It must have a web browser to install and verify operations of the console. To start it is not required flash plugin installed in your browser, although it is recommended to make use of interactive graphics in Flash.

1.2.6 Package Dependencies

Pandora FMS has a big dependency of the Linux operating system, but it also needs additional packages that often are not installed by default. In the installation process there are a detailed list of package dependencies for Debian / Ubuntu and OpenSUSE.

1.3 Issues before installation

1.3.1 MySQL

You will need a MySQL Server BEFORE configuring Pandora FMS, because in one of the steps you need to access a running MySQL server instance. For doing that, you need to have it operative. If you are installing the MySQL Server at the same time as Pandora FMS, remember that prior to configure Pandora, you need to setup MySQL server properly. This is easily done in two steps:

1. Start MySQL Server daemon:

/etc/init.d/mysql start

2. Configure root password for MySQL root user:

mysqladmin password <password>

Where '<password>' is the password you setup for mysql root user (different from "root" user in the system). This password will be ask in the Pandora FMS installation process.

1.3.2 Pandora FMS installation order

You should follow this order to install properly Pandora FMS:

  1. Install console
  2. Install server

The reason is because the MySQL database configuration is made during the Initial Configuration fase of the console installation and for be sure the properly work of the server is recommended do first the whole installation process of the console.

Also, Pandora FMS server and Pandora FMS console could be hosted in different machines, because you can configure the server to use a remote MySQL database through the server configuration file.

About the agent, you can install it before or after install the server and the console, because the agent works independently and it can be installed in any machine.

1.3.3 Installing the Enterprise version

From version 4.0.2 the license number of Pandora FMS enables the use of the Enterprise features. This means that if you have installed version 4.0.2 enterprise without a valid license number will not work. You must first install the OpenSource version, get the license number and then install the enterprise version 'in that order.' In summary:

  • Install the console OpenSource.
  • Access the console, go to the setup section and enter your license there (see the image below).
  • Install the Enterprise Console.

However, if you do it in another order, the screen wich reports you the error, could be used to enter the licence. Remember that the license validation is performed only on the console. Not on the server.

Enter the license here, in the main option configuration (setup):



Licence setup.png

1.4 Installing on SUSE (OpenSUSE or SLES)

1.4.1 Automated installation using the Official Repo

You will need access to Internet to perform this kind of installation. This method is easy and fast. All steps must be done as root user or using sudo before each command:

Step 1. Create repo

zypper ar -G http://artica.es/suse PandoraFMS_Official_Repo

Step 2. Update repo information

zypper refresh

Step 3. Install Pandora FMS:

zypper install pandorafms_agent_unix pandorafms_console pandorafms_server mysql-community-server apache2-mod_php5 

This will install Pandora FMS and all of it's dependencies in a single command.

1.4.2 Manual RPM installation

1.4.2.1 Configuring Software repositories

The installation of software on SLES is done via .RPM packets. These RPM packets can contain official software, provided by the manufacturer - Novell -, through the installation DVD/CD, HTTP / FTP repositories or other non-official repositories, maintained by the community of developers and users of SUSE (OpenSUSE). These repositories can only be accessed through the internet, but the individual RPM packages can be downloaded, copied to servers and installed manually by command line.

SLES uses a general management interface - YAST - for package management and software repositories. This interface is used to manage the entire system SLES: disk partition, install software, configure the network cards, etc... It can be used with graphical interface (X) or any console or remote session via SSH.

For this documentation we use the Zypper Suse tool, able to solve dependencies and download the packages directly from the repositories on the Internet. If you don't have Zypper installed, you should install it, is much more convenient and faster. If not, you will have to do all the manual installation of packages using YaST and SUSE installation CD.

1.4.2.2 Previous Dependencies Installation

You have to install the following package dependencies, included in SUSE:

apache2 apache2-mod_php5 php5 php5-gd php5-gettext php5-json php5-mbstring php5-ldap php5-mysql \
php5-pear php5-snmp php5-zip nmap perl-DBD-mysql perl-DBI perl-Date-Calc perl-HTML-Parser \
perl-HTML-Encoding perl-HTML-Tree perl-IO-Socket-inet6 perl-Socket6 perl-Mail-Sendmail perl-NetAddr-IP \ 
perl-TimeDate perl-XML-Simple perl-XML-Twig perl-libwww-perl mysql-client mysql-max mysql  \
net-snmp xorg-x11-fonts-core php5-pear-db php5-curl php5-xmlrpc perl-SNMP graphviz graphviz-gd

Info.png

OpenSUSE unlike SLES doesn't have mysql-max package, you can install Mysql standard package without any problem.

 


To install all dependencies, run:

zypper install ..

Followed by the whole package list specified in the paragraph above. This will give you a screen like this:

Getting repositories data...
Reading packets installed...
perl-DBI already installed.
perl-HTML-Parser already installed.
perl-TimeDate already installed.
perl-XML-Simple already installed.
perl-libwww-perl already installed.
xorg-x11-fonts-core already installed.
Resolving dependencies...

Following NEW packages will be installed:
  apache2 apache2-mod_php5 apache2-prefork apache2-utils libapr1 libapr-util1 libdnet1 
liblua5_1 libmm14 libmysqlclient15 mysql mysql-client mysql-Max net-snmp nmap 
perl-Bit-Vector perl-Carp-Clan perl-Data-ShowTable perl-Date-Calc perl-Date-Manip 
perl-DBD-mysql perl-HTML-Encoding perl-HTML-Tree perl-IO-Socket-inet6 
perl-Mail-Sendmail perl-NetAddr-IP perl-SNMP php5 php5-ctype php5-dom php5-gd 
php5-gettext php5-hash php5-iconv php5-json php5-ldap php5-mbstring php5-mysql 
php5-openssl php5-pdo php5-pear php5-snmp php5-sqlite php5-tokenizer php5-xmlreader 
php5-xmlwriter php5-zip php5-zlib t1lib 

Total Size: 19.1 M. After the operation, additional 55.9 M will be used.
 Continue? [Yes / no]:

By clicking YES, Zypper start downloading and installing packages.

When finished, you need to install some extra packages. In OpenSuse not all packages you need for Pandora FMS exist, so they are provided some additional RPM to satisfy these dependencies from the Pandora FMS Sourceforge website, these files. Additional rpm are:

perl-time-format php-pear-xml_rpc wmic smstools perl-HTML-Tree perl-XML-Twig

Info.png

Extra packages perl-HTML-Tree y perl-XML-Twig must be installed manually.

 


Optionaly and only if you will use Recon Server you should install these packages:

perl-net-traceroute perl-net-traceroute-pureperl xprobe2

These RPM files can be found on the official site of distribution of Pandora FMS software in a specific dependencies directory for OpenSuse.

NOTE: Be sure you download the correct packages for OpenSuse.

Place them in a directory, for example /tmp/extra. In that directory run the command:

rpm -i *.rpm

1.4.2.3 Agent Installation

You should have download from our web site a RPM package similar to this one ( some version number or another details could be slightly different):

pandorafms_agent-3.0.0-1.noarch.rpm

In order to install it, simply execute this command:

rpm -i pandorafms_agent-3.0.0-1.noarch.rpm

If these phrases are shown:

Insserv:warning:script 'smsd' missing LSB tags and overrides Insserv:default-start undefined, assuming default start runlevel (s) for script 'smsd'.

Do not worry. It is only a warning message. It is not an error.

1.4.2.4 Server installation

Same as with the agent.Execute:

rpm -i pandorafms_server-3.0.0-1.noarch.rpm

If you have previously installed the agent, then you will obtain the following not important warning:

useradd: Account `pandora' already exists.

1.4.2.5 Console installation

Same as before, execute the rpm installation tool for packages in order to install the package that contains the Pandora FMS console:

rpm -i pandorafms_console-3.0.0-1.noarch.rpm

If you have any trouble installing Pandora FMS console caused by a wrong package name, something like this:

error: Failed dependencies:
php5-pear-db is needed by pandorafms_console-3.1-1.noarch

You can force the installation using the flag --nodeps.

1.4.2.6 Installing the Enterprise version

Same way, execute the rpm package installing tool to install the package that contains the Enterprise version and the Pandora FMS Enterprise server:

rpm -i pandorafms_console_enterprise-3.0.0-1.noarch.rpm
rpm -i pandorafms_server_enterprise-3.0.0-1.noarch.rpm

You should restart the Pandora FMS server in order to detect the Enterprise version new functionalities:

/etc/init.d/pandora_server restart

1.4.3 Uninstalling Pandora FMS

You could uninstall any of Pandora FMS components with the following commands:

rpm -e pandorafms_agent
rpm -e pandorafms_console
rpm -e pandorafms_server

Pandora FMS database will be not uninstalled if any of the Pandora FMS packages are unistalled. All files ( also the configuration ones) from any package will be eliminated.

1.5 Installation in Red Hat Enterprise Linux / Fedora / CentOS

The installation process is nearly the same than the SUSE one. However, notice that RHEL/CentOS/Fedora RPM packages are not the same than in SUSE and are incompatibles.

1.5.1 Automated install by using Pandora FMS repository

You will need YUM and access to internet. First, you need to create the reference to Pandora FMS official repo for Centos6. This is also valid to be used in RHEL6.

vi /etc/yum.repos.d/pandorafms

Add this contents:

[artica_pandorafms]
name=CentOS6 - PandoraFMS official repo
baseurl=http://artica.es/centos6
gpgcheck=0
enabled=1

Refresh your repo information:

yum makecache

You now can install Pandora FMS, together with mysql server (this is an "optional" dependency, but you will need a MySQL server if you don't have one already).

yum install pandorafms_console pandorafms_server mysql-server

This will download all rpms and dependencies and will install for you, and will left the system ready for setup.

1.5.2 Manual installation from RPM files

Most of dependencies should be resolved using YUM or other automatic package. All dependencies are marked as needed package in the RPM definition:

yum install php php-gd graphviz php-mysql php-pear-DB  php-mbstring php-ldap php-snmp \
php-ldap php-common php-zip 

yum install perl-HTML-Tree perl-DBI perl-DBD-mysql perl-libwww-perl perl-XML-Simple \
perl-XML-SAX perl-NetAddr-IP net-snmp net-tools perl-IO-Socket-INET6 perl-Socket6 \ 
nmap wmic sudo xprobe2 make perl-CPAN perl-JSON net-snmp-perl perl-Time-HiRes perl-XML-Twig

Some dependencies (like wmic or xprobe2) are not in the official RHEL repositories, we provide in our Sourceforge download page as Tools and dependencies.

Some other dependencies like graphviz, perl-XML-Simple or perl-HTML-Tree are not in the official RHEL repositories either, however they can be found in the CentOS base repository, so we would only have to add this one to our repository list.

[centos_base]
gpgcheck = False
enabled = 1
name = CentOS Base
baseurl = http://mirror.centos.org/centos/6/os/i386/
http://public.planetmirror.com/pub/caosity/centos/6/os/i386/

Be sure you download the correct packages for Red Hat Enterprise Linux.

However, for Red Hat Enterprise Linux 6 we would only have to install these dependencies, since most of the necessary packages for the console and the server are already included in the php and perl dependencies by default:

yum install php php-common graphviz

yum install perl-HTML-Tree perl-DBD-mysql perl-XML-Simple perl-XML-SAX perl-NetAddr-IP \ 
net-snmp perl-SNMP net-tools perl-IO-Socket-INET6 perl-Socket6 nmap wmic xprobe2

Template warning.png

If you are using a version prior to RHEL6, some dependencies could have another name. For instance, perl-SNMP, in CentOS5, RHEL5, etc, would be called net-snmp-perl.

 


To install the RPM just use the rpm -i commando or directly yum command, for example:

rpm -i pandorafms_server-3.2-2.noarch.rpm

or

yum install pandorafms_server-3.2-2.noarch.rpm

If you encounter any problem by the time you try to access the Pandora FMS Console installation web page, please check if SELinux is active: in that case it is needed to deactivate it following the FAQ procedures.


Template warning.png

RHEL/CentOS 5.x by default uses PHP 5.1 and this is not compatible with Pandora FMS, you need to use PHP 5.2 or higher.

 


To do that, we recommend to use the following repository for CentOS5/RHEL5, which contains PHP 5.2:

[c5-testing]
name=CentOS-5 Testing 
baseurl=http://dev.centos.org/centos/5/testing/$basearch/
enabled=1
gpgcheck=1
gpgkey=http://dev.centos.org/centos/RPM-GPG-KEY-CentOS-testing

1.6 Instalation in Debian/Ubuntu

It is recommended to install Pandora FMS over a 10.04 version or superior. On Debian Stable (Squeeze) versions you can find problems due old versions of some optional software needed, as The LWP library Debian does not implement some methods for SSL, and this is necessary for monitoring Enteprise WEB modules can fix by installing a newer version of LWP by CPAN (manual method). Similarly, to use the ICMP Server Enterprise, you need a version 5.2 or higher NMAP, Squeeze comes with version 5.0. You can install a newer version, using packages. DEB unofficial or compile a version for yourself.

Info.png

If you install in Debian Squeeze, you must add the "Non-Free" repository for the package snmp-mibs-downloader.

 


Info.png

Due nature of debian packaging, if you choose Debian/Ubuntu, you should have access to internet or a local package repository to do the installation. A single depedency in Debian, could have sub-dependencies, so install without access to a online repository could be very complex.

 


1.6.1 Install by using the Artica private repository

There is a method faster and easy, by adding Artica private repository, which contains all needed Ubuntu/Debian packages.

Edit file /etc/apt/sources.list and add the following line:

deb http://www.artica.es/debian/squeeze /

Execute apt-get update as root (or sudo)

apt-get update

Install Pandora FMS with apt-get :

[email protected]:~# apt-get install pandorafms-console pandorafms-server pandorafms-agent-unix
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  apache2-mpm-prefork apache2-utils apache2.2-common dbconfig-common graphviz libapache2-mod-php5 libcgraph5 libcurl3 libgd2-xpm libgvpr1
  libio-socket-inet6-perl libnetaddr-ip-perl libonig2 libqdbm14 libsnmp-perl libsocket6-perl libssh2-1 libtime-format-perl
  libxml-namespacesupport-perl libxml-sax-expat-perl libxml-sax-perl libxml-simple-perl nmap php-db php-gettext php-pear php5 php5-cli php5-common
  php5-curl php5-gd php5-ldap php5-mysql php5-snmp php5-suhosin php5-xmlrpc smistrip snmp snmp-mibs-downloader snmpd xprobe
Suggested packages:
  apache2-doc apache2-suexec apache2-suexec-custom graphviz-doc libgd-tools php5-dev
The following packages will be REMOVED:
  libgd2-noxpm
The following NEW packages will be installed:
  apache2-mpm-prefork apache2-utils apache2.2-common dbconfig-common graphviz libapache2-mod-php5 libcgraph5 libcurl3 libgd2-xpm libgvpr1
  libio-socket-inet6-perl libnetaddr-ip-perl libonig2 libqdbm14 libsnmp-perl libsocket6-perl libssh2-1 libtime-format-perl
  libxml-namespacesupport-perl libxml-sax-expat-perl libxml-sax-perl libxml-simple-perl nmap pandorafms-agent-unix pandorafms-console
  pandorafms-server php-db php-gettext php-pear php5 php5-cli php5-common php5-curl php5-gd php5-ldap php5-mysql php5-snmp php5-suhosin php5-xmlrpc
  smistrip snmp snmp-mibs-downloader snmpd xprobe
0 upgraded, 44 newly installed, 1 to remove and 0 not upgraded.
Need to get 40.9 MB of archives.
After this operation, 90.8 MB of additional disk space will be used.
Do you want to continue [Y/n]? y
WARNING: The following packages cannot be authenticated!
  pandorafms-agent-unix pandorafms-console pandorafms-server
Install these packages without verification [y/N]? y

1.6.2 Manual install

1.6.2.1 Previous installation of dependencies

In Debian/Ubuntu the dependencies are the following ones:

Server:

snmp snmpd libtime-format-perl libxml-simple-perl libdbi-perl libnetaddr-ip-perl
libhtml-parser-perl wmi-client xprobe2 nmap traceroute 
libio-socket-inet6-perl libhtml-tree-perl libsnmp-perl snmp-mibs-downloader
libio-socket-multicast-perl libsnmp-perl libjson-perl

Info.png

If the wmi-client package is not in the repositories, you should download it from Pandora FMS sourceforge website

 


Console

php5 libapache2-mod-php5 apache2 mysql-server php5-gd php5-mysql php-pear php5-snmp php-db php-gettext 
graphviz mysql-client php5-curl php5-xmlrpc php5-ldap

In order to install the Server package or the console one, you will have to fulfill the dependencies before. This should be done installing all the packages before mentioned with the commandapt-get, having root priviledges, like this:

apt-get install snmp snmpd libtime-format-perl libxml-simple-perl libdbi-perl libnetaddr-ip-perl \
libhtml-parser-perl wmi-client xprobe2 nmap libmail-sendmail-perl traceroute libio-socket-inet6-perl \
libhtml-tree-perl php5 libapache2-mod-php5 apache2 mysql-server php5-gd php5-mysql php-pear php5-snmp \
php-db php-gettext graphviz mysql-client php5-curl php5-xmlrpc php5-ldap libsnmp-perl snmp-mibs-downloader \
libio-socket-multicast-perl libsnmp-perl libjson-perl


Info.png

The character \ is used as a line divider. You can do copy/paste of this documentation directly on the console and the line breaks will be considered as such ones thanks to the character \

 


This command would install all the dependencies needed to install the Pandora's FMS server and console into a Debian/Ubuntu system.

1.6.2.2 Pandora FMS installation with .DEB packages

The installation with the deb packages is very easy. First you should download all the necessary packages and after, simply you should execute the following commands in the same directory where you have put them.

In this example they are installed all together, but could be only one of them.

dpkg -i pandorafms-console_xxx.deb pandorafms-server_xxxx.deb

If once that the command has been executed you see that some dependencies are missing, then you can try to solve them in an automatic way with the command:

apt-get -f install

This will try to download all the necessary packages that are missing for the automatic installation of Pandora FMS into the system. Once the necessary packages have been installed, then we should continue with the installation of all Pandora FMS components.

1.6.2.2.1 Console installation

In order to complete the installation of the Pandora FMS Console, you must access the console URL and follow the installation wizard steps. If the console is installed in a server with IP 10.20.34.54 you will have to enter the following URL:

http://10.20.34.54/pandora_console

1.6.3 Upgrading Pandora FMS

Use dpkg -i to install a newer version or apt-get update & apt-get upgrade if using Artica's repo.

1.6.4 Uninstalling Pandora FMS

dpkg -r pandorafms-console-enterprise
dpkg -r pandorafms-console

1.7 Installation in FreeBSD

From version 3.2 of Pandora FMS supports FreeBSD.

1.7.1 Perl with ithread Installation

To execute the pandora server daemon, perl should be compiled with thread enabled. But, the FreeBSD perl 5.x (5.8 or later) package, perl-5.x.x.pkg, is without thread. So, it cannot be used.

You should compile and install perl 5.x executable by using FreeBSD ports collection like this:

cd /usr/ports/lang/perl5.x
make config
  -> Enable THREADS.
make
make install

1.7.2 Previous Dependencies Installation

In FreeBSD the dependencies are the following ones:

server:

databases/p5-DBI mail/p5-Mail-Sendmail net-mgmt/p5-NetAddr-IP textproc/p5-XML-Simple
devel/p5-Time-Format www/p5-HTML-Parser net/p5-Net-Traceroute-PurePerl
net/p5-IO-Socket-INET6 database/p5-DBD-mysql textproc/p5-XML-Twig converters/p5-JSON
net-mgmt/net-snmp security/nmap net/xprobe sysutils/coreutils

In order to install the pandora server, you will have to fulfill the dependencies before. This should be done by using ports collection. Don't use packages.

You can install all dependencies like this:

e.g.) p5-DBI installation.

cd /usr/ports/databases/p5-DBI
make
make install

console:

www/apache22, lang/php5, net-mgmt/php5-snmp, www/php5-session, devel/php5-gettext,
converters/php5-mbstring, net/php5-ldap, databases/php5-mysql, graphics/php5-gd, archivers/php5-zip, 
archivers/php5-zlib, devel/php5-json, ftp/php5-curl, devel/pear, databases/pear-DB, net/pear-XML_RPC, 
graphics/graphviz (GTK, GDK_PIXBUF, PERL, PHP should be enabled.)

In order to install the pandora console, you will have to fulfill the dependencies before. You can use ports collection or packages.

1.7.3 Console installation

There are no pandora console package file for FreeBSD. You should install the pandora console by using installer.

How to install using installer is described in following section, "Manual Installation from Sources in Linux/Unix".

On FreeBSD with apache22, pandora_console directory is:

/usr/local/www/apache22/data/pandora_console

1.7.4 Server installation

There are no pandora server package file for FreeBSD. You should install the pandora server by using installer.

How to install using installer is described in following section, "Manual Installation from Sources in Linux/Unix".

The file locations and startup script structure are different from Linux. We show FreeBSD specific things below.

After installation, you should add following lines to /etc/rc.conf.

pandora_server_enable="YES"
tentacle_server_enable="YES"

To enable pandora servers, pandora and tentacle, these settings are needed. Otherwise, they are not launched.

On FreeBSD, most files of pandora server are installed in /usr/local.

pandora_server, tentacle_server:

/usr/local/bin/pandora_server
/usr/local/bin/tentacle_server

Startup script:

/usr/local/etc/rc.d/pandora_server
/usr/local/etc/rc.d/tentacle_server

Configuration file:

/usr/local/etc/pandora/pandora_server.conf

util:

/usr/local/share/pandora_server/util/*

Man pages:

/usr/local/man/man1/*

Other:

The data_in and log directories are the same as Linux.

1.7.5 Agent installation

There are no pandora agent package file for FreeBSD. You should install the pandora agent by using installer.

How to install using installer is described in following section, "Manual Installation from Sources in Linux/Unix".

The file locations and startup script structure are different from Linux. We show FreeBSD specific things below.

After installation, you should add a following line to /etc/rc.conf.

pandora_agent_enable="YES"

To enable pandora agent, this settings are needed. Otherwise, it is not launched.

On FreeBSD, most files of pandora agent are installed in /usr/local.

Agent:

/usr/local/bin/pandora_agent

Startup script:

/usr/local/etc/rc.d/pandora_agent

Configuration file:

/usr/local/etc/pandora/pandora_agent.conf

Plugins:

/usr/local/share/pandora_agent/plugins/*

Man pages:

/usr/local/man/man1/*

Other:

The data_out and log directories are the same as Linux.

1.8 Installation in NetBSD

From version 5.0 of Pandora FMS supports NetBSD.

1.8.1 Previous Dependencies Installation

In NetBSD the dependencies are the following ones:

server:

mysql55-server databases/p5-DBI mail/p5-Mail-Sendmail net/p5-NetAddr-IP textproc/p5-XML-Simple 
time/p5-Time-Format www/p5-HTML-Parser net/nmap net/p5-IO-Socket-INET6
database/p5-DBD-mysql textproc/p5-XML-Twig  sysutils/coreutils converters/p5-JSON net/net-snmp

In order to install the pandora server, you will have to fulfill the dependencies before. This should be done by using 'pkgsrc'.

You can install all dependencies like this:

e.g.) p5-DBI installation.

cd /usr/pkgsrc/databases/p5-DBI
make
make install

In addition, you should install 'Net::Traceroute::PurePerl' and 'LWP::Simple' using CPAN.

perl -MCPAN -e 'install Net::Traceroute::PurePerl'
perl -MCPAN -e 'install LWP::Simple'

'xprobe' should also be installed by compiling source package.

You can download it from: http://sourceforge.net/projects/xprobe/files/latest/download

If you cannot compile with some error, modify following files and try again.

  • Add ' include <cstdlib> ' to 'libs-external/USI++/src/ip.cc'.
  • Add ' include <cstdlib> ' to 'libs-external/USI++/src/misc.cc'.
  • Add ' include <cstring> ' to 'libs-external/USI++/usi++/tcp.h'.

console:

www/apache22, lang/php54, net/php-snmp, www/ap-php, devel/php-gettext,
converters/php-mbstring, databases/php-ldap, databases/php-mysql, raphics/php-gd,
archivers/php-zip, archivers/php-zlib, textproc/php-json, www/php-curl, lang/pear, 
databases/pear-DB, graphics/graphviz, 

In order to install the pandora console, you will have to fulfill the dependencies before. You can use 'pkgsrc'.

In addition, you should install the 'XML_RPC' using pear.

pear install XML_RPC

1.8.2 Console installation

There are no pandora console package file for NetBSD. You should install the pandora console by using installer.

How to install using installer is described in following section, "Manual Installation from Sources in Linux/Unix".

On NetBSD with apache22, pandora_console directory is:

/usr/pkg/share/httpd/htdocs/pandora_console

1.8.3 Server installation

There are no pandora server package file for NetBSD. You should install the pandora server by using installer.

How to install using installer is described in following section, "Manual Installation from Sources in Linux/Unix".

The file locations and startup script structure are different from Linux. We show NetBSD specific things below.

After installation, you should add following lines to /etc/rc.conf.

pandora_server="YES"
tentacle_server="YES"

To enable pandora servers, pandora and tentacle, these settings are needed. Otherwise, they are not launched.

On NetBSD, most files of pandora server are installed in /usr/local.

pandora_server, tentacle_server:

/usr/local/bin/pandora_server
/usr/local/bin/tentacle_server

Startup script:

/etc/rc.d/pandora_server
/etc/rc.d/tentacle_server

Configuration file:

/usr/local/etc/pandora/pandora_server.conf

util:

/usr/local/share/pandora_server/util/*

Man pages:

/usr/share/man/man1/*

Other:

The data_in and log directories are the same as Linux.

1.8.4 Agent installation

There are no pandora agent package file for NetBSD. You should install the pandora agent by using installer.

How to install using installer is described in following section, "Manual Installation from Sources in Linux/Unix".

The file locations and startup script structure are different from Linux. We show NetBSD specific things below.

After installation, you should add a following line to /etc/rc.conf.

pandora_agent="YES"

To enable pandora agent, this settings are needed. Otherwise, it is not launched.

On NetBSD, most files of pandora agent are installed in /usr/local.

Agent:

/usr/local/bin/pandora_agent

Startup script:

/etc/rc.d/pandora_agent

Configuration file:

/usr/local/etc/pandora/pandora_agent.conf

Plugins:

/usr/local/share/pandora_agent/plugins/*

Man pages:

/usr/share/man/man1/*

Other:

The data_out and log directories are the same as Linux.

1.9 Manual Installation from Sources in Linux/Unix

This option is specially important if you want to use the development version code or directly from the code repositories.

1.9.1 Previous Installation of Necessary Software

So as you are going to build Pandora FMS from the sources, you will need the basic software in order to compile and installe software from the code. Depending on the use of one distro or another one, you will have to install packages such as make,gcc and others. Furthermore, it is recommended to review the dependencies section corresponding to your distribution.

In debian/ubuntu there is a metapackage that contains all of them:

apt-get install build-essential subversion

In SUSE/Redhat/Fedora you should install several packages:

zypper install make automake subversion

1.9.2 Download from Sources

The easiest way is to download the sources in "tarball" format (.tar.gz, .tgz o .tar.bz2) and decompress them. For it, you should go to Pandora official web site, download section at http://pandorafms.org.

Other interesting option if you want to keep well informed and use the latest code, stable or at development, is using the client from Subversion (svn)code version system.For it you could visit the development version at Pandora FMS official web site project FMS http://pandorafms.org/index.php?sec=community&sec2=development&lang=es.

To download the development version code using the commands line from the SVN client:

svn co https://svn.code.sf.net/p/pandora/code/

1.9.3 Agent Installation

The agent does not requires neither compilation nor preparation. Once we have the agent pandorafms_3.0_unix.tar.gz

1. Do root

su -

2. Copy to /tmp and at /tmp we should execute:

tar xvzf pandorafms_3.0_unix.tar.gz 
./pandora_agent_installer --install

3. We start the agent manually

/etc/init.d/pandora_agent_daemon start

1.9.3.1 Custom agent installation

Starting with 3.1 version, the agent could be installed completely is a custom defined directory, like for example /opt/pandora. This custom defined directory will contain everything agent has: configuration files, logfiles, plugins, and even the man pages.

To use this method:

./pandora_agent_install --install /opt/pandora

The only file pandora will create outside it's defined directory is the main agent service launcher at /etc/init.d/pandora_agent_daemon (or equivalente in other unix kinds), and the startup level link, for example /etc/rc.d/rc2.d/S90pandora_agent_daemon.

Also it is possible to perform installation to execute agent with other user than root. For example to execute with user Pandora, you have to install with the following command:

./pandora_agent_install --install "" pandora

1.9.4 Console Installation

Once we have the compressed file with the console that should be named pandorafms_console-3.0.0.tar.gz o similar:

1. We do root

su -

2. We copy it to /tmp and at/tmp we execute:

tar xvzf pandorafms_console-3.0.0.tar.gz 
cd pandora_console
./pandora_console_install --install

1.9.4.1 Enterprise Versión

Once we have the file compressed with the console, that will be called pandorafms_console_enterprise-3.0.0.tar.gz or similar:

1. We do root

su -

2. We copy it to /tmp and in /tmp we execute:

tar xvzf pandorafms_console-3.0.0.tar.gz 

And we copy it to the directory where is installed our Pandora FMS Opensource console, either /var/www/pandora_console for Debian or Ubuntu, or /srv/www/htdocs/pandora_console/ for SUSE, RH, Fedora, etc (or in another directory depending on your distribution).

Debian:

cp -R enterprise /var/www/pandora_console

SUSE:

cp -R enterprise /srv/www/htdocs/pandora_console


3. Change the permissions in order that files would be for the web server user, for example:

Debian:

chown -R www-data /var/www/pandora_console/enterprise

SUSE:

chown -R wwwrun /srv/www/htdocs/pandora_console/enterprise

After that, we should proceed with Console Initial Configuration

1.9.5 Server Installation

Once we have the compressed file with the server that will be called pandorafms_server-3.0.0.tar.gzor similar:

1. We do root

su - 

2. We copy it to /tmp and at y /tmp we execute:

tar xvzf pandorafms_server-3.0.0.tar.gz 
cd pandora_server
./pandora_server_installer --install

If there are problems with dependencies, then we should have to solve them before trying the installation. We could force the installation ignoring the problem with dependencies, but Pandora FMS will not work right.

1.9.5.1 Enterprise Version

Once we have the file compressed with the server,that will be named pandorafms_server_enterprise-3.0.0.tar.gz or similar:

1. We do root

su - 

2. We copy it to /tmp and in /tmp we execute:

tar xvzf pandorafms_server_enterprise-3.0.0.tar.gz 
cd PandoraFMS-Enterprise/
perl Makefile.PL
make
make install

If the installation has been done with a system with a Pandora FMS OpenSource that is already functioning and we want that it consider the new features or the Enterprise version, we only have to restart the Pandora FMS server:

/etc/init.d/pandora_server restart

If there are problems with dependencies, then we have to resolve them before trying the installation. We could force the installation ignoring the problem with the dependencies, but Pandora FMS will not work or will not work correctly.

1.9.5.2 Uninstallation / Manual wipe from server

If we have installed / updated several different versions, using different installation methods (RPM, Tarball), it could come to a point in which we have various versions mixed up that could be using wrong versions of libraries or of the server itself. The following procedure is aimed at detecting which versions are there and manually erase them:

Binaries should always be in /usr/local/bin, with a link to /usr/bin. To test this simply:

ls -la /usr/local/bin/pandora_server
ls -la /usr/local/bin/tentacle_server
ls -la /usr/bin/tentacle_server
ls -la /usr/bin/tentacle_server

Pandora's libraries depend on their distribution's version. The following command should allow to know where they are and whether there are various ones:

find / -name "WMIServer.pm"

This will display a complete path where Pandora's library is installed, for example:

/usr/local/share/perl/5.10.0/PandoraFMS/WMIServer.pm

It could happen that various paths are displayed:

/usr/local/share/perl/5.10.0/PandoraFMS/WMIServer.pm
/usr/local/share/perl/PandoraFMS/WMIServer.pm

En such case we won't know which one is in use, so our best option is to remove the entire directories and reinstall Pandora FMS:

 rm -Rf /usr/local/share/perl/5.10.0/PandoraFMS
 rm -Rf /usr/local/share/perl/PandoraFMS/

It is always a good idea to backup /etc/pandora/pandora_server.conf, just in case.

1.9.6 Server Code Update:Compilation and Manual Installation of the Server

There is another way besides the generic installation script. You could "compile" the Pandora FMS code through the Perl interpreter of its system. This process simply install the libraries and the minimum executables, but does not touch the starting script system , maintenance scripts, configuration or any other thing besides the application and its libraries. This process is the indicated one when has to update the server code but without overwrite its configuration.

For it, decompress your server code in /tmp, such as it has been said in the previous step.

1. We do root

2. We copy to /tmp and in /tmp we execute:

tar xvzf pandorafms_server-3.0.0.tar.gz 
cd pandora_server
perl Makefile.PL
make
make install

Observe the error exit from the screen. If any dependency is missing or there is any other problem, then the system will notify to you. If you observe a message like this:

Warning: prerequisiete Mail::Sendmail 0 not found
Warning: prerequisiete Net::Traceroute::PurePerl 0 not found

Then it means that there are some Perl packages that Pandora FMS needs and that the system does not have installed. Check the previous paragraphs in order to know how to install the previous required dependencies to install Pandora FMS. Nevertheless you can "ignore" these errors (they are warnings no errors) and force the installation. For sure you will have problems in one moment or another because there is one component missing to work. But if you know the component that is not installed and is not going to be used (f.e: traceroute is used only for the Pandora FMS Recon Server) then you can go on.

After all this process, the files are automatically copied

/usr/local/bin/pandora_server
/usr/local/bin/pandora_exec

And several .pm files (Perl libraries) that Pandora FMS needs. These libraries .pm are copied into several files, depending on its distribution version and on its distribution.For example in Ubuntu 9.04 they are copied to:

/usr/local/share/perl/5.10.0/PandoraFMS/

In SUSE/SLES 11 they are copied to:

/usr/lib/perl5/site_perl/5.10.0/PandoraFMS/

1.10 Windows Agent Installation

The agent is given as an self-installer in executable format (.exe). The basic installation does all the required steps and it will be necessary only to accept all the options. To install the Pandora FMS agent in Windows you only need to download and to execute it. The installer will guide you with all the steps in the language that you choose. In the following example it is shown the installation for Windows Vista. Remember that Pandora FMS works with any current Microsoft (2000 or upper) platform.

Select the language:



Pandora agent 3.0 RC3 install windows 01.png



Follow the installer steps.



Pandora agent 3.0 RC3 install windows 02.png



Accept the license terms and press Next:



Pandora agent 3.0 RC3 install windows 03.png



Select the path where the Pandora FMS agent will be installed. You can change it pressing Browse...,after press Next:



Pandora agent 3.0 RC3 install windows 04.png



Check the installation data and press Next:



File:Pandora agent 3.0 RC3 install windows 05.png



Wait mean while the files are being copied.



Pandora agent 3.0 RC3 install windows 06.png



Configure the data for the agent as the IP (or name) of the Pandora FMS server that will receive the agent data and the data entry path (if you are not sure of this value, then leave the default value).



Pandora agent 3.0 RC3 install windows 07.png



Choose if you want to start at the moment the Pandora FMS agent service. On the contrary, you will have to do it in a manual way or else it will start when Windows reboots again.



Pandora agent 3.0 RC3 install windows 08.png



When the installation has finished you can change the agent's parameters at file pandora_agent.conf or trough the direct link at Pandora FMS menu:



File:Pandora agent 3.0 RC3 install windows 09.png



1.10.1 Windows Agent Unattended Installation

From versión 3 RC3, Pandora FMS includes the option of installing the Windows agent in an unattended way . For it, you should execute the agent installator giving it the /mode Silent parameter that shows that the installation should be done in an unattended way. Besides, you can pass it the /prefix <Ruta> parameter to show it the installation complete path.

Execute the following command (where XXXXX) could change depending on the installator version, and <Ruta> is the complete path where we want to install it (in inverted commas if it has spaces).

PandoraFMS_windows_agent_v3.0.XXXXX.setup.exe /mode Silent /prefix <Ruta>

For example, to install the current version, to install in c:\agente_pandora\, you should execute:

PandoraFMS_windows_agent_v3.0.RC3.setup.exe /mode Silent /prefix c:\agente_pandora

This will install Pandora FMS with the default values in the showed path, and it start the Pandora FMS service in the machine. It is necessary to execute this installing process with priviledges to could install software/ services in the machine.

1.10.2 Unattended Uninstallation

The uninstaller that is an executable called uninstall.exe that remains in Pandora FMS installation directory, also allows the unattended unistallation, for it, you have to execute the unistaller with the /mode Silent option

For example, assuming that Pandora FMS is installed in the default path:

c:\archivos de programa\pandora_agent

You should execute:

“c:\archivos de programa\pandora_agent\uninstall.exe” /mode silent

1.10.3 Windows Agent Manual Installation

The Window's agent could be installed in a manual way. To learn how the manual installation works serves also to understand how the Agent works at inside and to could reset later the installation of some parameters.

Assuming that all the agent's necessary files are obtained and also their directory structure, that summarizing is this one:

  • PandoraAgent.exe: Pandora FMS service executable. We will see later that it accepts any parameters that could be very useful for us.
  • pandora_agent.conf: the configuration main file
  • libcurl.dll: library used by Pandora FMS to upload the files through FTP.
  • libeay32.dll: library used by Pandora FMS to cypher connections (SSH y Tentacle).
  • zlub1.dll: Library used by Pandora FMS to compress data.
  • libodbc++.dll: library used by Pandora FMS for para ODBC checking
  • pandora_agent.log: agent's main log
  • pandora_debug.log: agent's main log (as debug )
  • /util:In util directory there are several unix "typical" tools given to Win32, such as grep,gawk, wc, head,tail, etc.

There is also placed the tentacle client, "tentacle_client.exe" that is the one used to send the packages to the Pandora FMS server.

These files could be obtained from our code repository (subversion) at sourceforge, just as it's described in our website.

Another easier solution is to make a zip with the contents of a currently installed agent. Just zip contents of the directory c:\program files\pandora_agent and decompress into the destination system.

1.10.3.1 Using PandoraAgent.exe from the Commands Line

If we execute pandoraagent.exe --help, it will show something like this:

Pandora agent for Windows. Version 3.0(Build 090924)
Usage: pandoraagent.exe [OPTION]

Available options are:
        --install:  Install the Pandora Agent service.
        --uninstall: Uninstall the Pandora Agent service.
        --test-ssh: Test the SSH Pandora Agent configuration.
        --test-ftp: Test the FTP Pandora Agent configuration.
        --process: Run the Pandora Agent as a user process instead of a service.

To install the service (if it is not installed), execute following command from the directory where is placed the .exe, like c:\program files\pandora_agent:

pandoraagent.exe --install

This will install the service in the machine building on the path where the .exe is located. If we want to remove it, it is the same process, but:

pandoraagent.exe --uninstall

Depending on the kind of Windows system that it would be it is possible that you should have to reboot the system after removing the service. In other systems the change is taken without having to reboot.

If you want to try a ftp or ssh connection from the command line, then you can use the options above mentioned.

1.10.3.2 Pandora FMS Window's Agent as Process

Is possible, for debugging reasons,tests and other unusual circunstances, to execute the agent in "Process" way. This is done executing it from the command line:

pandoraagent.exe --process

There are some restrictions in the execution to the process mode, so Pandora FMS is thought to execute as service and as a user SYSTEM. If you execute it with other user without privileges, then it will be functions that will not work properly.

1.10.4 Pandora FMS for windows NT4

This agent is a port of the Unix agent (in perl) compiled with ActiveState DevKit Perl compiler. This is a stand-alone EXE with all the tools it will need to run. It has the same features than the Unix agent, but running on a NT4 box. This means can execute commands and get the output to produce data for Pandora FMS.

Could be used on any Windows machine (NT4, Win95, Windows 2000-2008, and of course Windows 7), could be useful on windows embedded systems without WMI core, which makes standard Pandora FMS windows agent to do not run properly.

1.10.4.1 Installing the agent

Copy all contents on a directory of your choice, for example c:\pandora.

Edit pandora_agent.conf and set your parameters, including the log file and the temporal directory, should be something like c:\pandora\temp and c:\pandora\log. MAKE SURE that directories exists before trying to start Pandora agent.

1.10.4.2 Running the agent

This agent does not run as a service, so you need to install in the startup menu or start by hand. The shortlink you create must have a parameter, which is where is the main Pandora FMS agent directory, in this scenario is c:\pandora, so the command to start will be :

c:\pandora\pandora_agent.exe c:\pandora

1.10.4.3 Install as a service

srvany.exe tool is provided to do this. Is a microsoft resource kit tool to be able to use any .exe as a service. Just read the documentation about how to use srvany (provided in this package).


1.11 Embedded Agent

Pandora FMS has a very special agent called "embedded" agent. It's a pure-C development designed to be full cross-plattform compatible, you only need the GNU C compiler to compile, link and use it in any system available, we have tested in a few ARM enviroments. It doesn't require anything special, and should be run on any system with GNU C compiler.

In order to use it, you will need also to compile and link the tentacle client protocolo, to send information to Pandora FMS server.

To compile both you will need GNU C extensions and autotools (autoconf, automake, pkg-config, etc).

You will need sources for embedded agent, from our SVN or file release section on Sourceforge AND the code for tentacle client, also from our SVN or the download section, as a separate file.

1.11.1 Basic installation

The simplest way to compile this package is:

1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're using `csh' on an old version of System V, you might need to type `sh ./configure' instead to prevent `csh' from trying to execute `configure' itself.

Running `configure' takes awhile. While running, it prints some messages telling which features it is checking for.

2. Type `make' to compile the package.

3. Optionally, type `make check' to run any self-tests that come with the package.

4. Type `make install' to install the programs and any data files and documentation.

5. You can remove the program binaries and object files from the source code directory by typing `make clean'. To also remove the files that `configure' created (so you can compile the package for a different kind of computer), type `make distclean'. There is also a `make maintainer-clean' target, but that is intended mainly for the package's developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.

1.11.2 Installation Names

By default, `make install' will install the package's files in `/usr/local/bin', `/usr/local/etc', etc. You can specify an installation prefix other than `/usr/local' by giving `configure' the option `--prefix=PATH'. Make install will install these files by default:

 /usr/local/etc/pandora/pandora_agent.conf
 /usr/local/bin/pandora/pandora_agent

You can specify separate installation prefixes for architecture-specific files and architecture-independent files. If you give `configure' the option `--exec-prefix=PATH', the package will use PATH as the prefix for installing programs and libraries. Documentation and other data files will still use the regular prefix.

In addition, if you use an unusual directory layout you can give options like `--bindir=PATH' to specify different values for particular kinds of files. Run `configure --help' for a list of the directories you can set and what kinds of files go in them.

If the package supports it, you can cause programs to be installed with an extra prefix or suffix on their names by giving `configure' the option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.

1.11.3 Features of the embedded agent

At this moment agent support only the basic features, that means, module_exec method to get information and also module_plugin, all information you gather from the system must be done by using external command execution.

2 Initial Configuration after Installing

The order you should follow after installing is:

  1. Create the database through the Pandora FMS web console installation wizard.
  2. Modify the server configuration including the access credentials to the BBDD that have been generated by the previous step.
  3. Start server Arrancar servidor.
  4. Start local agent (if it is required).
  5. Go to the Pandora FMS for first time to start using Pandora FMS.

2.1 Console Initial Configuration

Assuming we are going to execute all components (Database, Console, Server and Agent) on the same machine. If you have not done it already, then start the Mysql server and create an admin password (root).

/etc/init.d/mysql start

Now create the password, for example "pandora123" for your MYSQL root user:

mysqladmin password pandora123

Then start the Apache server in your server:

/etc/init.d/apache2 start

Now you can get to your server IP address trough web to do the Pandora FMS post-installation trough web. This post-installation serves to create the Pandora FMS database and to configure the access credentials (user password, BD name) in the Pandora server to the DDBB established by the user.


If your server IP is, for example,"192.168.5.54" put in your browser:

http://192.168.5.54/pandora_console/install.php

From now you only have to follow the following steps in order to create the Pandora FMS DDBB.



Pandora install 1.png



Press next.



Pandora install 2.png



This screen is used to verify that it has all software dependencies well installed.

Note: if you need to install some dependencies, it will be necessary to restart the web server in order to recognise them.



Pandora install 3.png



Here it configures the access data to your MySQL server. You should entry the root password that you created in the previous step. (pandora 1234 in the example).



Pandora install 4.png



You need to enter here the password for the dabatabase access.



File:Paso5.png



Ending of the installation.



Paso6.png



In this point, you will need to delete "install.php" manually, go to pandora fms console install directory and delete install.php:

  • (DEBIAN/UBUNTU) /var/www/pandora_console
  • (FEDORA/CENTOS/REDHAT) /var/www/htdocs/pandora_console
  • (SUSE) /srv/www/htdocs/pandora_console

To delete a file in linux, use rm command:

rm install.php

2.1.1 License Application

Pandora FMS Entperise version has a different license key associated to each instalation. To use Enterprise features and remote updates of console is needed to introduce the license code in console configuration section.

2.1.1.1 License on versions older than 4.0.2

For versions previous to 4.0.2 the license is use on remote updates of console. To introduce the license in a installation of Pandora FMS with a version older than 4.0.2 you must follow these steps:


1. Go to Administration menu and inside Setup submenu, select Update Manager Settings.



File:Setup menu license.png



2. In the screen will appear a form with all data required to connect to update server. You must introduce the license code in the field Customer Key and click on button Update.



700px



3. To ensure the license code was added sucessfully go to Operation menu and in Extesions submenu, select Update Manager, a screen like the following will appear:



700px



If you get a screen like below showing and error related to keygen, you must install it following the section Installing the Keygen.



700px



2.1.1.2 Licencia on versions 4.0.2 and higher

For versions 4.0.2 or higher Pandora FMS license are used to updates and also to ensure the user is using Enterprise code properly. Because of that is important to have a valid license. To introduce your license key in Pandora FMS 4.0.3 or higher follow these steps.

1. Go to Setup menu inside Administration section.



File:Setup license 402.png




2. In the screen will appear a form with all data required to connect to update server. Search License information parameter and enter your license code.



700px




3. To ensure the license code was added sucessfully go to Operation menu and in Extesions submenu, select Update Manager, a screen like the following will appear:



700px



If you get a screen like below showing and error related to keygen, you must install it following the section Installing the Keygen.

2.2 Server Initial and Basic Configuration

Pandora FMS has configured your Database and created a MySql user to have access to it. It has created a random password for "pandora" user that should be the one used to modify the password that is defined in th Pandora FMS server.

For this last step, you have to edit the file /etc/pandora/pandora_server.conf from your Pandora installation and look for the line:

dbpass pandora

And replace "pandora" for the password that has been created by the wizard.?Once that it has done it and it has also recorded the file it can start the Pandora FMS server in this way:

/etc/init.d/pandora_server start

It should give an start like this:

Pandora FMS Server 3.0-dev Build PS090915 Copyright (c) 2004-2009 ArticaST
This program is OpenSource, licensed under the terms of GPL License version 2.
You can download latest versions and documentation at http://www.pandorafms.org 

 [*] Backgrounding Pandora FMS Server process.
 
Pandora Server is now running with PID 2085

2.3 Initial and Basic Configuration of the Agent

You could start your machine local agent(it comes preconfigured to send data to the same machine where it is run, through tentacle), to start to collect data automatically:

/etc/init.d/pandora_agent_daemon start

Now you can have access to your Pandora FMS WEB console through the URL:

http://x.x.x.x/pandora_console

Where x.x.x.x is the IP of the machine where you have installed the Pandora FMS console.

Go back to Pandora FMS documentation index