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

From Pandora FMS Wiki
Jump to: navigation, search
(Console and Server Requirements)
(Installation via Cloud provider)
 
(317 intermediate revisions by 18 users not shown)
Line 1: Line 1:
 
[[Pandora:Documentation_en|Go back to Pandora FMS documentation index]]
 
[[Pandora:Documentation_en|Go back to Pandora FMS documentation index]]
  
= Pandora FMS Installation =
 
  
== Minimum Hardware Requirements ==
 
  
=== Console and Server Requirements ===
+
= Console and Pandora FMS Server Installation =
  
* '''Up to 500 agents or 5.000 modules''': 3GB of RAM, a 2.5GHz single-core CPU and a fast hard drive, 7200 RPM or equivalent, assuming 80% of modules with history and an average interval of 5 min.
+
==Minimum hardware requirements==
  
* '''Up to 2.000 agents or 10.000 modules''': 6GB of RAM, a dual core 2.5GHz CPU and a very fast hard drive (10000 RPM or more), assuming 80% of modules with history and an average interval of 5 min. You're also required to tune up your MySQL very well.
+
The requirements set out in this table are the minimum recommendations for different installations. These recommendations are calculated assuming that 80% of the modules have historical data and the average sampling time is 5 minutes. These recommendations are specified for an environment where they are installed in the same database server, server and console.
  
* '''For more than 4.000 agents''': 12GB of RAM, a 3GHz quad-core CPU and the fastest hard drives available on the market (15,000 RPM or more), assuming 80% of modules with history and an average interval of 5 min. It's recommended to have MySQL installed on another server. You're required to fine tune your MySQL or to have 'Percona XtraDB' installed.
+
<table cellpadding=6 cellspacing=0 border=1 style='text-align:center;  background-color: #ECECEC;'>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:center; background-color: #7CA12A; color:#FFFFFF'> Hardware </th>
 +
<th style='border-color: #000000; background-color: #7CA12A; color:#FFFFFF'> SMALL: up to 500 agents or 5000 modules </th>
 +
<th style=' border-color: #000000; background-color: #7CA12A; color:#FFFFFF'> MEDIUM: up to 2000 agents or 10000 modules </th>
 +
<th style=' border-color: #000000; background-color: #7CA12A; color:#FFFFFF'> BIG: For more than 4000 agents*</th>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; background-color: #7CA12A; color:#FFFFFF'> CPU </th>
 +
<td>1 core at 2 GHz </td>
 +
<td>2 cores at 2,5 GHz</td>
 +
<td>4 cores at 3 GHz </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; background-color: #7CA12A; color:#FFFFFF'> RAM </th>
 +
<td>4 GB </td>
 +
<td>8 GB </td>
 +
<td>16 GB </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; background-color: #7CA12A; color:#FFFFFF'> Hard drive </th>
 +
<td>7200 rpm </td>
 +
<td>15K rpm or SSD </td>
 +
<td> SSD </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; background-color: #7CA12A; color:#FFFFFF'> Disk Space </th>
 +
<td>20GB minimum <br> 40GB recommended </td>
 +
<td>60GB minimum <br> 120GB recommended </td>
 +
<td> 120GB minimum <br>250GB recommended </td>
 +
</tr>
 +
</table>
  
{{Warning|In case you install Pandora FMS in a virtual environment, make sure to assign an independent disk with reserved space and a high access ratio. It's also better to assign independent RAM and CPU instead of using a part of its host's resources.}}
+
(*) In addition to the these recommendations, we recommend installing MySQL on a standalone server and installing '''Percona XTraDB''' instead of standard MySQL.
  
{{Tip|We strongly recommended using '''SSD''' type disks, for performance improvement.}}
 
  
Disk size: A minimum of 15GB free space. 25GB is recommended to have 25GB.
+
<br>
 +
{{Warning|In case you install Pandora FMS in a virtual environment, make sure to assign an independent disk with reserved space and high access speed. It is recommended to use [https://pandorafms.com/blog/hard-disk-types/ '''SSD''' hard drives], due to their high impact on performance improvement.}}
  
== Software Requirements ==
+
{{Tip|A 25GB disk is recommended for a single-node database, server and console installation. If you are going to use functionalities such as log storage or want to save information that is more than one month old, you should create a [[Pandora:Documentation_en:Server_Management#History_database | history database]]}}<br><br><br>
  
The officially supported OS platform for Pandora FMS is Linux. From Pandora FMS versions 5.1 and above, Windows Server is also supported. The supported Linux distributions and versions for the server and console are as follows:
+
== Minimum software requirements ==
  
 
+
<table cellpadding=6 cellspacing=0 border=1 style='background-color: #ECECEC'>
<table cellpadding=6 cellspacing=0 style='background-color: #ECECEC;'>
 
 
<tr>
 
<tr>
<th style='text-align:center; background-color: #6fb034; color:#FFFFFF'>Component</th>
+
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Software</th>
<th style='text-align:center; background-color: #6fb034; color:#FFFFFF'>Operating System</th>
+
<th colspan=3 style=' border-color: #000000; text-align:center; background-color: #7CA12A; color:#FFFFFF'>Requirements</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<td>Pandora FMS 5.1 or higher</td>
+
<th rowspan =2 style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Operating System</th>
<td>
+
<td colspan=3 style=' text-align: center;'>
* RedHat Enterprise (RHEL) 6.x
+
* RedHat Enterprise (RHEL) 7.X (Enterprise only)
* CentOS 6.x
+
* RedHat Enterprise (RHEL) 8.X (Enterprise only)
* SLES 11 SP1 or higher.
+
* CentOS 7.X ('''recommended''')
* OpenSUSE 11.x or higher.
+
* CentOS 8.X
* Debian 5.x or higher.
 
* Ubuntu 11 or higher.
 
* Microsoft Windows Server (2003 or higher)
 
 
</td>
 
</td>
 
</tr>
 
</tr>
</table>
+
<tr>
 +
<td colspan=2 style=' text-align: center;'>
 +
* Windows Server (2003 or higher)
 +
* SLES 11 SP1 or higher
 +
* OpenSUSE 11.X or higher
 +
* Debian 5, 6, 7 or higher
 +
* Ubuntu 11 or higher
 +
* FreeBSD 9.X and 10.X
 +
* Solaris 10/OpenSolaris
 +
</td>
 +
<td style='text-align: center; background-color: #FCFFD2'> '''Pandora FMS does not give official support in these platforms''' </td>
 +
<tr>
 +
<th style=' border-color: #000000; background-color: #7CA12A; color:#FFFFFF'>Permissions</th>
 +
<td colspan=3 style='text-align: center;'>
 +
* '''Server'''
 +
 
 +
Pandora FMS Server service must be executed as root permission. Execution as non-root user is possible, being a special and different procedure. Find out more information in this [[Pandora:Documentation_en:Installing#Custom_Installation |link]].
 +
 
 +
* '''Console'''
 +
 
 +
To be able to use the console from any web browser, Apache must have read and execute permissions on the console files.
 +
 
 +
Additionally, the <code>config.php</code> file must have the 600 permissions (read and write for <code>administrator/root</code>).
  
 +
It is necessary to have writing permissions in the server directory: <code>/var/spool/pandora/</code>.
  
We don't offer official support for them, but other platforms where Pandora FMS works are as follows:
+
* '''Agent'''
  
 +
-Linux®: The Pandora FMS Server Software Agent must be executed as root permission in order to have all the agent features available, although it is also possible to execute it with other permissions..
  
<table cellpadding=6 cellspacing=0 style='background-color: #ECECEC;'>
+
-Windows®: Pandora FMS Server Software Agent must be executed as administrator permission.
 +
</td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; background-color: #7CA12A; color:#FFFFFF'>Console</th>
 +
<td colspan=3 style='text-align: middle'>
 +
* PHP 7.2 -> For Pandora FMS version 729 or higher.
 +
* PHP 5 -> For Pandora FMS version 728 or older.
 +
</td>
 +
</tr>
 
<tr>
 
<tr>
<th style='text-align:center; background-color: #6fb034; color:#FFFFFF'>Component</th>
+
<th rowspan =2 style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Browsers    </th>
<th style='text-align:center; background-color: #6fb034; color:#FFFFFF'>Operating System</th>
+
<td colspan=3 style='text-align: center'>
 +
* Microsoft Edge®
 +
* Opera web browser®
 +
* Google Chrome®
 +
* Mozilla Firefox®
 +
</td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<td>Pandora FMS 4.0 or higher</td>
+
<td colspan= 3 style='text-align:center; background-color: #FCFFD2'>
<td>
+
Mozilla Firefox® and Google Chrome® are recommended to make use of interactive graphs and network maps.
* FreeBSD 9.x, 10.x
 
* Solaris 10 / OpenSolaris
 
 
</td>
 
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
  
The Pandora FMS Agents run on almost any modern operating system. Please take a look at the Agent Requirements section for more details.
+
== Database requisites ==
  
=== Database Requirements ===
+
<table cellpadding=6 cellspacing=0 border=1 style='background-color: #ECECEC'>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>BBDD</th>
 +
<th style=' border-color: #000000; text-align:center; background-color: #7CA12A; color:#FFFFFF'>Details</th>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>MySQL Standard</th>
 +
<td>
 +
* '''Version 5.7'''
 +
* For standard installation, a user with creating privileges in the pandora DB is required. In case of not having this user, a manual installation can be performed.
 +
</td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Percona XTraDB</th>
 +
<td>
 +
Percona XTraDB installation is recommended for large Pandora FMS environments where more than 4000 agents must be created.
  
Prior to installing Pandora FMS, you're required to have a MySQL Database up and running. You're also required to have a MySQL Server running on a server. It may be the same server you're going to install Pandora FMS on. You may also utilize a separate server which is accessible from your Pandora FMS Server / Console using a TCP/IP network. To do so, you're required to have:
+
* '''Version 5.7'''
 
+
* For standard installation, a user with creating privileges in the pandora DB is required. In case of not having this user, it will be possible to carry out manual installation.
* '''The IP Address of your MySQL Server:''' ('localhost' if it's installed on the same Pandora FMS Server Host).
+
</td>
* '''A privileged User:'''A user who has the rights to create databases and users (usually the user named 'root'). This user must be allowed to connect from the IP address of your Pandora FMS Server host.
+
</tr>
* '''A Password:''' A password for privileged users.
+
</table>
 
 
 
 
{{Warning|You're required to get this up and running '''before''' installing Pandora FMS. If you don't know how to install a MySQL Server, please check the [http://www.mysql.com/ '''On-Line Documentation'''] for the entire process on how to do that, because this procedure changes considerably on different operating systems and Linux distributions.}}
 
 
 
=== Agent Requirements ===
 
 
 
The remote agent is able to run on any hardware which is able to run the minimum required operating systems.
 
 
 
Alongside Linux, Pandora FMS Agents work on the following systems:
 
  
 
+
== Satellite Server Requirements==
<table cellpadding=6 cellspacing=0 style='background-color: #ECECEC;'>
+
<table cellpadding=6 cellspacing=0 border=1 style='background-color: #ECECEC'>
 
<tr>
 
<tr>
<th style='text-align:center; background-color: #6fb034; color:#FFFFFF'>Component</th>
+
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Satellite</th>
<th style='text-align:center; background-color: #6fb034; color:#FFFFFF'>Operating System</th>
+
<th style=' border-color: #000000; text-align:center; background-color: #7CA12A; color:#FFFFFF'>Details</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<td>Pandora Agent (versions 4.0 or above)</td>
+
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Hardware</th>
 
<td>
 
<td>
* Linux (all distributions)
+
Similarly to Pandora FMS installation, the hardware requirements of the system that will host the satellite server will depend on the monitoring volume to be managed.
* HPUX B.11.11 or higher, with Perl 5.8.
+
For environments with less than 1000 agents, a minimum of 1 core at 2GHz and 1 GB of RAM is recommended.
* AIX 4.3.3 or higher, with Perl 5.8.
 
* BSD (NetBSD, OpenBSD, FreeBSD), with Perl 5.8.
 
* MacOSX 10.6 or higher, with Perl 5.8
 
* Solaris 8 or higher, with Perl 5.8.
 
* Windows NT4 (see special version notes here).
 
* Windows XP
 
* Windows 2000
 
* Windows 2003
 
* Windows 2008
 
* Windows 7
 
* Windows 8
 
* Windows 2012
 
 
</td>
 
</td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<td>Pandora Android Agent (versions 2.0 or above)</td>
+
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Dependencies</th>
 
<td>
 
<td>
* Android 2.2 or above
+
The main dependencies are:
 +
* <code>fping</code>
 +
* <code>nmap</code>
 +
* <code>perl</code>
 +
* <code>wmic</code>
 
</td>
 
</td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<td>Pandora Embedded Agent (versions 4.0 or above)</td>
+
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Binaries</th>
 
<td>
 
<td>
* Embedded devices require compilation.
+
The main dependencies are:
</td>
+
* Linux® 32 Bits
 +
* Linux® 64 Bits
 +
* Windows® 32 Bits
 +
* Windows® 64 Bits
 +
* Raspberry Pi OS</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
  
<br>
+
==Port requirements==
{{Tip|It's well known that the agent has been implemented successfully into other operating systems, but there is '''no official support''' for them. The agent '''does not''' work under Windows NT4. To be able to monitor outdated Windows systems, you may install the 'Cygwin' environment and the Agent for Linux. If you intend to do so, please expect the performance to be much lower than it would be under current Windows versions.}}
 
  
Under UNIX platforms, you're additionally required to have installed:
+
<table cellpadding=6 cellspacing=0 border=1 style='background-color: #ECECEC'>
 +
<tr>
 +
<th style=' border-color: #000000; align:middle; background-color: #7CA12A; color:#FFFFFF'>Port</th>
 +
<th style=' border-color: #000000; align:middle; background-color: #7CA12A; color:#FFFFFF'>Protocol</th>
 +
<th style=' border-color: #000000; align:middle; background-color: #7CA12A; color:#FFFFFF'>Service/Process</th>
 +
<th style=' border-color: #000000; align:middle; background-color: #7CA12A; color:#FFFFFF'>Descripction</th>
 +
<th style=' border-color: #000000; align:middle; background-color: #7CA12A; color:#FFFFFF'>Address</th>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>80 </th>
 +
<td> TCP </td>
 +
<td> Pandora FMS Console </td>
 +
<td> IP management  </td>
 +
<td> Browser '''->''' Pandora FMS Console Server </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>80 </th>
 +
<td> TCP </td>
 +
<td> Pandora FMS Console (API Communication) </td>
 +
<td> Use of API/CLI feature </td>
 +
<td> Browser/Server that starts the query '''->''' Pandora FMS Console Server</td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>80 </th>
 +
<td> TCP </td>
 +
<td> Metaconsole </td>
 +
<td> Communication between Metaconsole and Nodes </td>
 +
<td> Metaconsole server '''->''' Node Server
  
* 'Perl 5.8' or higher.
+
Node Server '''->''' Metaconsole server </td>
* You may optionally unzip the package and execute it via path by the user on which the Pandora FMS Agent gets hosted on. This package is only required if you intend to use the file collection.
+
</tr>
* If you intend to use the local inventory plug in to obtain information from the hardware, you're required to install the tool named 'lshw' which requires to have full access and the right to execute itself from the system path.
+
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>162 </th>
 +
<td> UDP </td>
 +
<td> Pandora FMS Server </td>
 +
<td> Trap reception </td>
 +
<td> Trap generator device '''->''' Pandora FMS Server </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>443 </th>
 +
<td> TCP </td>
 +
<td> Pandora FMS Console (API Communication)</td>
 +
<td> Use of API/CLI feature </td>
 +
<td> Browser/Server that starts the query '''->''' Pandora FMS Console Server </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>443 </th>
 +
<td> TCP </td>
 +
<td> Metaconsole </td>
 +
<td> Communication between Metaconsole and Nodes </td>
 +
<td> Metaconsole server '''->''' Node server
  
=== Server Requirements ===
+
Node server '''->''' Metaconsole server </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>3306 </th>
 +
<td> TCP </td>
 +
<td> Pandora FMS Console and Server </td>
 +
<td> DB connection</td>
 +
<td> Pandora FMS Console Server '''->''' Pandora FMS Database Server
  
You can also work on any operating system with Perl 5.8 installed and iThreads enabled.
+
Pandora FMS Server '''->''' Pandora FMS Database Server </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>3306 </th>
 +
<td> TCP </td>
 +
<td> Metaconsole </td>
 +
<td> Communication between Metaconsole and DB Nodes </td>
 +
<td> Metaconsole server '''->''' DB Nodes Server
  
It should be noted that Pandora FMS requires a MySQL server to store all information. This server may be installed on any MySQL-supported platform. This could be Windows, Linux, Solaris, etc.
+
Node Server '''->''' Metaconsole BBDD Server </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>4444 </th>
 +
<td> TCP </td>
 +
<td> Pandora FMS Server </td>
 +
<td> Connection with Selenium GRID </td>
 +
<td> Pandora FMS Server '''->''' Selenium Server </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>9995 </th>
 +
<td> UDP </td>
 +
<td> Pandora FMS Server </td>
 +
<td> Receiving Netflow probes </td>
 +
<td> nfcapd Server '''->''' Pandora FMS Server </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>9200 </th>
 +
<td> TCP </td>
 +
<td> Pandora FMS Console and Server </td>
 +
<td> Log storage management with Elasticsearch </td>
 +
<td> Elasticsearch Server '''->''' Pandora FMS Server </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>41121 </th>
 +
<td> TCP </td>
 +
<td> Pandora FMS Agents </td>
 +
<td> Tentacle Communication </td>
 +
<td> Software Agent Server Agent '''->''' Pandora FMS Server </td>
 +
</tr>
 +
<tr>
 +
<th colspan= 5 style=' border-color: #000000; text-align:center; background-color: #7CA12A; color:#FFFFFF'> It is recommended to facilitate communication from Pandora FMS server and console to the whole network. For standard monitoring you should need minimum:</th>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>80 </th>
 +
<td> TCP </td>
 +
<td> Pandora FMS Server </td>
 +
<td> Web monitoring for WUX server </td>
 +
<td> Pandora FMS Server '''->''' Server to monitor </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>161 </th>
 +
<td> UDP </td>
 +
<td> Pandora FMS Console and Server </td>
 +
<td> Monitoring via SNMP Polling </td>
 +
<td> Pandora FMS Server '''->''' Server to monitor </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>443 </th>
 +
<td> TCP </td>
 +
<td> Pandora FMS Server </td>
 +
<td> Web monitoring for WUX server </td>
 +
<td> Pandora FMS Server '''->''' Server to monitor </td>
 +
</tr>
 +
<tr>
 +
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>ICMP </th>
 +
<td> ICMP </td>
 +
<td> Console and Pandora FMS Server </td>
 +
<td> Web monitoring for WUX server </td>
 +
<td> Pandora FMS Server '''->''' Server to monitor </td>
 +
</tr>
 +
</table>
  
It's required to have Perl 5.8 installed, at least for the server to work appropriately. In addition to the operating system's SNMP packets ('net-snmp') to utilize the Pandora FMS SNMP service, it also requires a MySQL-Database, NMAP packages and the optional xprobe2 to be able to use the advanced features of the Recon Server and traceroute's Perl libraries to be able to setup a self-discovering network. It's also necessary to install the WMI client's binary for WMI queries against Windows systems. The client binary is a part of the SAMBA project (v4) and can be compiled, but not without some difficulty under any UNIX environments.
+
== Package Dependencies ==
  
=== Console Requirements ===
+
Pandora FMS has a strong dependency on the Linux® Operating System, but it also needs additional packages which,  in many cases, are not installed by default. During the installation process, there is a detailed list of package dependencies for CentOS.
 
 
The console requirements are the same as for the server. We recommend its operation being resident 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 which is able to run Windows, Unix, etc.
 
 
 
=== Web-Administration Requirements for the Tool ===
 
 
 
You're required to have a web browser installed to verify the operations of the console. It's not required to have the Flash plug in installed in your browser to start, but it's recommended to utilize some of the interactive Flash graphics.
 
 
 
=== Package Dependencies ===
 
 
 
Pandora FMS has a heavy dependency on the GNU/Linux Operating System, but it also needs additional packages which aren't installed by default in many cases. During the installation process, there is a detailed list of package dependencies for Debian, Ubuntu and OpenSUSE.
 
  
 
== Issues prior to Installation ==
 
== Issues prior to Installation ==
  
 
=== MySQL ===
 
=== MySQL ===
 +
{{Warning|During the installation process of Pandora FMS in [[Pandora:Documentation_en:Installing#Package_installation_for_CentOS_7.2F8|Centos 7 and 8 systems by packages]] it is already explained how to install and configure the database compatible with the server, so it is not necessary any previous installation before following the guide and you can skip this point}}
  
You will need to have a MySQL Server installed BEFORE configuring Pandora FMS, because in one of the steps, you're required to access a running MySQL server instance. For doing that, you need to have it operational. If you are installing the MySQL Server at the same time as Pandora FMS, remember that you need to set up the MySQL server properly prior to configuring Pandora FMS. This is easily done in two steps:
+
You will need to have MySQL Server installed '''before''' configuring Pandora FMS, since the next step after installing Pandora FMS packages, is to configure access to the databases. To do that, it must be operational. If you are installing the MySQL Server at the same time as Pandora FMS, remember that you need to set up the root user for MySQL. This can be easily done in two steps:
  
1. Please start the MySQL Server daemon:
+
1. Start MySQL Server daemon:
  
 
  /etc/init.d/mysql start
 
  /etc/init.d/mysql start
  
2. Configure the root password for the MySQL root user:
+
2. Configure the root password for MySQL root user:
  
 
  mysqladmin password <password>
 
  mysqladmin password <password>
  
Where '<password>' is the password you have to setup for the MySQL root user (which is different from the systems 'root' user). The system is going to ask for this password throughout the entire Pandora FMS installation process.
+
In <code><password></code>, type in the password for MySQL root user (which is different from the system's root user). The system will ask for this password throughout the entire Pandora FMS installation process.
  
 
=== Pandora FMS Installation Order ===
 
=== Pandora FMS Installation Order ===
  
You're required to follow this sequence in order to install Pandora FMS properly:
+
You are required to follow this sequence in order to install Pandora FMS properly:
  
 
# Install console
 
# Install console
 
# Install server
 
# Install server
  
The reason for this is the MySQL database configuration is made during the initial configuration phase of the console installation. To ensure the correct working of the server, it's recommended to conduct the whole console's installation process first.
+
The reason for this is that MySQL database is configured during the initial configuration phase of the console installation. To ensure the correct working of the server, it is recommended to conduct the whole console installation process first.
  
The Pandora FMS Server and console are also possible to be hosted on different machines, because you can configure the server to utilize a remote MySQL database by means of the server's configuration file.
+
It is also possible to host Pandora FMS Server and console in different machines. It is possible to indicate both where MySQL database is through the corresponding configuration file, although in '''Enterprise''' environments when carrying out a distributed installation you should take into account more factors for installation.
  
Regarding the agent: You may install it before or after installing the server and console, because the agent works independently and it's capable of getting installed on any machine.
+
Regarding the agent: You may install it before or after installing the server and console, because the agent works independently and it may be installed on any machine.
  
 
=== Installing the Enterprise Version ===  
 
=== Installing the Enterprise Version ===  
  
From versions 4.0.2 and above, the license number of Pandora FMS activates all features of the Enterprise Version. If you're installing the Pandora FMS 4.0.2 Enterprise without a valid license number, it's not going to work. You first have to install the open-source version, get the license number and install the Enterprise Version.
+
The correct order for an Enterprise installation is as follows:
 
 
In summary:
 
  
* Please install the open-source console.
+
* Install the open-source console.
* Please access the console, go to the setup section and insert your license code as shown on the picture below.
 
 
* Install the Enterprise Console.
 
* Install the Enterprise Console.
 +
* Install the Enterprise Server.
 +
* When accessing the console, a box will appear requiring you to enter your Enterprise license code.
  
However, if you do it in any other order, the screen which reports the error to you could be used for inserting the license number.
+
Validation of the license is only done in the console. '''Not''' in the server.
  
<b>Please enter the license number in the main configuration option (setup): </b>
+
Details on how to correctly enter the license can be found in the following section: [[Pandora:Documentation en:Installing#License_Application | '''License Application v5.X''']] window opens.<br><br><br>
  
<center>
+
== Installation via Cloud provider ==
<br>
 
<br>
 
[[image:Licence_setup.png|600px]]
 
<br>
 
<br>
 
</center>
 
  
From Pandora FMS versions 5 and above, the security for license verification was improved and requires a different method of license installation. In order to install the license for versions 5 and above, you're required to install the enterprise console and access the login screen first. Once you've agreed, a window called  [[Pandora:Documentation en:Installing#License_Application | '''License Application v5.X''']] is going to open.
+
=== Pandora Server environment ===
 +
The term "Cloud provider" (or simply "Cloud") is used to describe the hosting of virtual machines, either exclusively or shared, in specialized providers with hardware, hypervisors and customer support web systems for configuration and administration.
  
==== Special Requirements for the Enterprise Version ====
+
For any of them you can install Pandora FMS Community edition. CentOS 7.x is recommended as operating system, 4 gigabytes in RAM memory and 20 gigabytes in free disk space, preferably Solid State Drive (SSD).
  
In order to use the ICMP Enterprise Server, you're required to have fping installed.
+
Access the command line as provided by your Cloud provider and execute:
  
== Installing the Appliance CD ==
+
<nowiki>curl -Ls https://pfms.me/deploy-pandora | sh</nowiki>
  
Due to the length of this section, we have established a special screen shot-equipped section. It's called [[Pandora:Documentation_en:Appliance_Install|'''Appliance CD Installation.''']]
+
=== Pandora Agent ===
 +
To install only the agent there is also a one line installation tool, it is compatible wiht Red Hat base OS (Fedora, Centos, etc) and Debian base OS (debian, ubuntu, etc):
  
== Installation under Docker ==
+
The script support a series of environments variables to customize the installation, and just one of it is mandatory '''$PANDORA_SERVER_IP''' so to perform a standard installation in one line just execute:
  
=== Get the last stable version ===
+
<nowiki>export PANDORA_SERVER_IP=<PandoraServer IP or FQDN> && curl -Ls https://pfms.me/agent-deploy | bash </nowiki>
To get the last stable version:
 
  
    curl -sSL http://pandorafms.org/getpandora  | sh
+
Optionally is possible to use another env variables to customize installation:
  
 +
'''$PANDORA_REMOTE_CONFIG''': Configure the remote config setting - '0' by default (disabled)
  
{{Warning|This command requires Docker Engine installed and running.}}
+
'''$PANDORA_AGENT_NAME''': Configure the agent name setting - autogenerated by default
  
=== Advanced installation ===
+
'''$PANDORA_AGENT_ALIAS''': Configure the agent alias setting - hostname by default
  
Pandora FMS runs as a container under Docker environments using three components from the [https://hub.docker.com/r/pandorafms/ Docker Hub]:
+
'''$PANDORA_GROUP''': Configure the agent group setting - 'Servers' by default
*[https://hub.docker.com/r/pandorafms/pandorafms-mysql/ MySQL container]: Container to store the data. It can be launched as follows:
 
    docker run --name pandora-mysql -e MYSQL_ROOT_PASSWORD=AVeryStrongRootPassword -e MYSQL_DATABASE=pandora -e MYSQL_USER=pandora -e MYSQL_PASSWORD=pandora -d pandorafms/pandorafms-mysql:6
 
  
{{Warning|Be aware to change your database credentials before launching this container.}}
+
'''$PANDORA_SECONDARY_GROUPS''': Configure the agent secondary groups setting - Empty by default
  
* [https://hub.docker.com/r/pandorafms/pandorafms-console/ Console container]: Pandora FMS web interface. It can be launched as follows:
+
'''$PANDORA_DEBUG''': Configure the debug setting - '0' by default (disabled)
    docker run -p 80:80 -p 8022:8022 -p 8023:8023 --link pandora-mysql:mysql -d pandorafms/pandorafms-console:6
 
  
* [https://hub.docker.com/r/pandorafms/pandorafms-server/ Server container]: Pandora FMS Server. It can be launched as follows:
+
'''$TIMEZONE''' : Configure the system timezone
    docker run -p 41121:41121 --link pandora-mysql:mysql -d pandorafms/pandorafms-server:6
 
  
 +
Example:
  
{{Tip|Docker images are updated on a daily basis}}
+
  <nowiki> export PANDORA_SERVER_IP='env.pfms.com' && \
 +
  export PANDORA_REMOTE_CONFIG=1 && \
 +
  export PANDORA_AGENT_NAME='Agent_name' && \
 +
  export PANDORA_AGENT_ALIAS='Agent alias' && \
 +
  export PANDORA_GROUP='Servers' && \
 +
  export PANDORA_SECONDARY_GROUPS='VMware,Web' && \
 +
  curl -Ls https://pfms.me/agent-deploy | bash </nowiki>
  
{{Tip|There are three tags: 5.1, 6 and latest. '''The last stable version is 6'''.}}
+
'''Note''': this environment variables are used just in installation process, could be destroyed or change after installation without alter Pandora FMS agent behave
  
== Installing the VMWare Virtual Machine ==
+
== Installation using ISO or "Software appliance"  ==
  
Alongside the Centos ISO, you can find a virtual machine which contains an already installed Pandora FMS under 'sourceforge.net'. This image is tested with VMWare ESX, VMWare Workstation, VirtualBox and Hyper-V. To run it under Hyper-V, you're required to export the VMDX and VDH files from the 'MVDC.exe' executable. They are available after you've installed the Microsoft Virtual Machine Converter.
 
  
To install it, you have to execute the '.ovf' file under 'Virtualbox' and 'VMWare Workstation'. Under ESX and Hyper-V, you're required to import the image under 'Import VM' and select the virtual image there.
+
Download the CD image from the [https://pandorafms.com/community/get-started/ download section] of our website and burn the ISO image onto a DVD, or run the system from that file if you are using a virtualized system (XenServer, VMware®, VirtualBox®, etc). There are CD images for both 32- and 64-bit installations.
  
The credentials for this machine are the following:
+
<br><hr>The following screen will be displayed at the beginning of the boot process. If you do not press any key, the process will automatically load the Live CD, or you can press any key, select the '''Install Pandora FMS'''' option and press "enter" to start the installation.
  
'''User:''' root
+
[[Image:Install_1.png|center|520px]]
  
'''Password:''' pandora
+
<br><hr>The graphic installer will lead you step by step throughout the whole installation process. This installer is a standard installation process used by CentOS, and it is available in different languages.
  
'''Console User:''' admin
+
[[image:Install_2.png|center|520px]]
  
'''Password:''' pandora
+
<br><hr>It is a very easy process but special attention must be paid when:
  
'''MySQL user:''' root
+
* Entering the superuser password (root).
 +
* When asked about the hard drive partitioning:
  
'''Password:''' pandora
+
[[Image:Install_3.png|center|520px]]
  
== Installation under SUSE (OpenSUSE or SLES) ==
+
Select and configure all the necessary options to install, '''Date & Time''', '''Keyboard''' and '''Installation Destination'''.
  
=== Automatized Installation by the Official Repository ===
+
<br><hr>Remember to activate the network interface, or else it will need to activated manually after installation.
  
You're required to have access to the internet to perform this kind of installation. This method is easy and fast. All steps are required to be conducted as a 'root' user or by the use of 'sudo' before entering any command:
+
[[Image:Install_4.png|center|520px]]
  
'''Step 1:''' Please create a repository by entering the following command:
+
Activate the network interface and optionally change the hostname
  
zypper ar -f http://firefly.artica.es/suse PandoraFMS_Official_Repo
+
[[Image:Install_5.png|center|520px]]
zypper ar -f http://download.opensuse.org/repositories/server:/php:/applications/SLE_11_SP3/ Php5
 
zypper ar -f http://download.opensuse.org/repositories/devel:/languages:/perl/SLE_11_SP3 Perl
 
  
wget --no-check-certificate https://dev.mysql.com/get/mysql-community-release-sles11-6.noarch.rpm
+
<br><hr>When clicking the installation destination button, the partition process will start.
  
'''Step 2:''' Update the repository's information:
+
[[Image:Install_6.png|center|520px]]
  
zypper refresh
+
<br><hr>Select the disk where the installation will be performed and click on '''Done'''.
  
'''Step 3:''' Install Pandora FMS and some dependencies :
+
[[image:install_7.png|500px]]
  
rpm -i mysql-community-release-sles11-6.noarch.rpm
+
<br><hr>Select the partitioning, unless you have advanced knowledge use the option ''''Click here to create them automatically''''. Click '''Done'''.
zypper install pandorafms_agent_unix pandorafms_console pandorafms_server apache2-mod_php5
 
  
=== Manual RPM Installation ===
+
[[Image:Install_8.png|center|520px]]
  
==== Configuring Software Repositories ====
+
<br><hr>Verify the created partitions and click on '''Done'''.
  
The installation of software on SLES [http://en.wikipedia.org/wiki/SUSE_Linux_Enterprise_Server ('''S'''USE '''L'''inux '''E'''nterprise '''S'''erver)] is conducted via RPM packets. These RPM packets can contain official software provided by the manufacturer Novell. The installation DVD / CD or HTTP / FTP repositories or other non-official repositories are maintained by the community of developers and users of SUSE (OpenSUSE). These repositories can only be accessed by the internet, but the individual RPM packages may be downloaded, copied to servers and manually installed by the command line.
+
[[image:install_9.png|500px]]
  
SLES utilizes a general management interface (YAST) for package management and software repositories. This interface is used to manage the entire SLES system: Disk partitioning, installing software, configuring the NICs, etc. It can be used with graphical interface (X), any console or remote session via SSH.
+
Accept Changes.
 +
<br><hr>Click on '''Begin installation'''.
  
For this documentation, we've used the 'Zypper' tool from SUSE, which is capable of solving dependencies and downloading packages directly from the repositories on the internet. If you don't have Zypper installed, you should install it, because it's faster and much more convenient. If you don't, you're required to have to conduct all the entire installation of packages using YaST and the SUSE Installation CD manually.
+
[[Image:Install_10.png|center|520px]]
  
==== Previous Dependencies Installation ====
+
<br><hr>Here you can assign the root password and optionally create a user.
  
You're required to install the following package dependencies (which are included under SUSE):
+
[[Image:Install_11.png|center|520px]]
  
apache2 apache2-mod_php5 php5 php5-gd php5-gettext php5-json php5-mbstring php5-ldap php5-mysql \
+
Now just wait until the process is finished and the system restarts automatically.
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 \
 
perl-Encode-Locale perl-JSON
 
  
 +
After removing the ISO image of the machine's startup so that the installer does not appear again, the recently installed CentOS system will be started and you will be able to use Pandora FMS with all the necessary dependencies for its correct operation.
  
{{Tip|Unlike SLES, OpenSUSE doesn't have a 'mysql-max' package. You may install the MySQL standard package without experiencing any problems.}}
+
== Installing the ISO image using a USB Stick ==
  
In order to install all dependencies, please just execute:
 
  
zypper install ..
+
To install the Pandora FMS appliance from a USB flash drive, follow these steps:
  
Followed by the whole package list, specified in the paragraph above, this is going to display a screen like the one on the picture below:
+
* Download the Pandora FMS ISO image from the download section.
 +
* Download the program '''rufus''' to prepare your USB for the installation (https://rufus.akeo.ie/)
 +
* Insert the flash drive.
 +
* Start the program '''rufus'''.
  
Getting repositories data...
+
<center>
Reading packets installed...
+
[[image:Usb_installation_1.PNG]]
perl-DBI already installed.
+
</center>
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 perl-JSON
 
 
Total Size: 19.1 M. After the operation, additional 55.9 M will be used.
 
  Continue? [Yes / no]:
 
  
By clicking 'yes', Zypper starts downloading and installing the packages.
+
* Select the Pandora FMS ISO image.
  
When finished, you're required to install some extra packages. Under OpenSuse, not all the required packages for Pandora FMS exist yet. They are going to be provided by an additional RPM to satisfy the dependencies [http://sourceforge.net/projects/pandora/files/Tools%20and%20dependencies%20%28All%20versions%29/RPM%20SUSE/ from the Pandora FMS Sourceforge website.] The additional RPMs are the following:
+
<center>
 +
[[image:Usb_installation_2.PNG]]
 +
</center>
  
perl-time-format php-pear-xml_rpc wmic smstools perl-HTML-Tree perl-XML-Twig
+
* Press '''START''' to start the creation of the Pandora FMS installation USB.
  
 +
<center>
 +
[[image:Usb_installation_3.PNG]]
 +
</center>
  
{{Tip|Extra packages like 'Perl-HTML-Tree' and 'Perl-XML-Twig' are required to be installed manually.}}
+
<center>
 +
[[image:Usb_installation_4.PNG]]
 +
</center>
  
{{Tip|In Centos7 wmic is not an explicit requeriment for pandorafms_server but is still needed by the WMIServer. You can find the binary file at [https://sourceforge.net/projects/pandora/files/Tools%20and%20dependencies%20%28All%20versions%29/wmic_centOS7_x64.zip/download the SourceForge web place]. The correct path for its deployment is /usr/bin/wmic}}
+
* Your Pandora FMS installation USB device is ready
  
 +
<center>
 +
[[image:Usb_installation_5.PNG]]
 +
</center>
  
If you intend to use the Recon Server, you're required to install these additional packages:
 
  
perl-net-traceroute perl-net-traceroute-pureperl xprobe2
+
* Connect the USB to the machine where you want to install Pandora FMS.
 +
* When starting the system, configure the BIOS to start first from USB.
  
These RPM files can be found on the official distribution site of Pandora FMS Software in a specific dependencies directory for OpenSUSE.
+
The following screen should be displayed:
  
{{Tip|Please make sure to download the appropriate packages for OpenSUSE.
+
<center>
 +
[[image:Usb_installation_6.PNG]]
 +
</center>
  
Please put them in a directory, e.g.: '/tmp/extra' and execute the following command:
+
Select '''Installing from USB stick''' and continue the installation as described in the previous chapter.
  
rpm -i *.rpm
+
== Package installation for CentOS 7/8 ==
  
==== Agent Installation ====
+
=== Repository configuration ===
  
You're required to download an RPM package similar to this one from our web site (the version or some other details could be slightly different):
+
==== Repository configuration on CentOS 8 ====
  
pandorafms_agent-5.1SP2-1.noarch.rpm
+
To configure it it will be necessary to execute the following commands:
  
In order to install it, just execute this command:
+
dnf install -y \
 +
    epel-release \
 +
    tar \
 +
    dnf-utils \
 +
    http://rpms.remirepo.net/enterprise/remi-release-8.rpm
  
  rpm -i pandorafms_agent-5.1SP2-1.noarch.rpm
+
  dnf module reset php
 +
dnf module install -y php:remi-7.3
 +
yum config-manager --set-enabled PowerTools
  
If these phrases are shown:
+
(''Note'': In CentOS 8.3 it changes from PowerTools to powertools.)
  
Insserv:warning:script 'smsd' missing LSB tags and overrides
+
==== Repository configuration in CentOS 7 ====
Insserv:default-start undefined, assuming default start runlevel (s) for script 'smsd'.
 
  
Don't worry. It's just a warning message, not an error.
+
Configure <b>yum</b> and the necessary repositories. Execute the following commands:
  
==== Server Installation ====
+
yum install -y \
 +
    tar \
 +
    yum-utils \
 +
    https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm \
 +
    http://rpms.remirepo.net/enterprise/remi-release-7.rpm
  
Same as on the agent. Just execute:
+
yum-config-manager --enable remi-php73
  
rpm -i pandorafms_server-5.1SP2-1.noarch.rpm
 
  
If you have installed the agent before that, you'll get the following (quite unimportant) warning:
+
=== Database installation ===
  
useradd: Account "pandora" already exists.
+
==== Database installation on CentOS 8 ====
  
==== Console Installation ====
 
  
Please execute the RPM installation tool for packages in order to install the package which contains the Pandora FMS Console:
+
It will also be necessary to install a database <b>percona</b> using the following commands:
  
rpm -i pandorafms_console-5.1SP2-1.noarch.rpm
 
  
If you have any trouble installing the Pandora FMS console caused by a wrong package name, you'll probably get an error message such as this:
+
dnf install -y https://repo.percona.com/yum/percona-release-latest.noarch.rpm
 +
dnf module disable -y mysql
 +
rm -rf /etc/my.cnf
 +
dnf install -y Percona-Server-server-57
  
error: Failed dependencies:
+
==== Database installation on CentOS 7 ====
php5-pear-db is needed by pandorafms_console-5.1SP2-1.noarch
 
  
You can force the installation by using the '--nodeps' flag.
 
  
=== Uninstalling Pandora FMS ===
+
It will also be necessary to install a database <b>percona</b> using the following commands: 
  
You're able to uninstall any of Pandora FMS components by using the following commands:
+
yum install -y https://repo.percona.com/yum/percona-release-latest.noarch.rpm
 +
rm -rf /etc/my.cnf
 +
yum install -y Percona-Server-server-57
  
rpm -e pandorafms_agent
 
rpm -e pandorafms_console
 
rpm -e pandorafms_server
 
  
The Pandora FMS database won't get uninstalled if any of the Pandora FMS packages are - just all files from any other package (including the configuration files) are going to be deleted.
+
=== Dependency installation ===
  
== Installation in Red Hat Enterprise Linux / Fedora / CentOS ==
+
==== Dependency installation on CentOS 8 ====
  
The installation process is nearly the same as the one from SUSE. Please keep in mind that RHEL, CentOS or Fedora RPM packages aren't the same as the ones in SUSE - there are also some incompatibilities.
+
'''Console dependencies'''
  
First of all, you're required to add some official repositories to your system. Subsequently, you may choose to add the Pandora FMS official repository to conduct an installation from the online repositories. Adding this additional repositories is going to help you to install all required dependencies for Pandora FMS.
+
Once with <b>dnf</b> and <b>percona</b> installed we can start to install all the necessary dependencies for the <b>console</b>:
  
Edit /etc/yum.repos.d/CentOS-Base.repo and enable EXTRAS, and UPDATES repos. Usually should be something like this:
 
  
  [updates]
+
  dnf install -y \
name=CentOS-$releasever - Updates
+
    php \
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates
+
    postfix \
gpgcheck=1
+
    php-mcrypt \php-cli \
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
+
    php-gd \
+
    php-curl \
[extras]
+
    php-session \
name=CentOS-$releasever - Extras
+
    php-mysqlnd \
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras
+
    php-ldap \
gpgcheck=1
+
    php-zip \
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-6
+
    php-zlib \
 +
    php-fileinfo \
 +
    php-gettext \
 +
    php-snmp \
 +
    php-mbstring \
 +
    php-pecl-zip \
 +
    php-xmlrpc \
 +
    libxslt \
 +
    wget \
 +
    php-xml \
 +
    httpd \
 +
    mod_php \
 +
    atk \
 +
    avahi-libs \
 +
    cairo \
 +
    cups-libs \
 +
    fribidi \
 +
    gd \
 +
    gdk-pixbuf2 \
 +
    ghostscript \
 +
    graphite2 \
 +
    graphviz \
 +
    gtk2 \
 +
    harfbuzz \
 +
    hicolor-icon-theme \
 +
    hwdata \
 +
    jasper-libs \
 +
    lcms2 \
 +
    libICE \
 +
    libSM \
 +
    libXaw \
 +
    libXcomposite \
 +
    libXcursor \
 +
    libXdamage \
 +
    libXext \
 +
    libXfixes \
 +
    libXft \
 +
    libXi \
 +
    libXinerama \
 +
    libXmu \
 +
    libXrandr \
 +
    libXrender \
 +
    libXt \
 +
    libXxf86vm \
 +
    libcroco \
 +
    libdrm \
 +
    libfontenc \
 +
    libglvnd \
 +
    libglvnd-egl \
 +
    libglvnd-glx \
 +
    libpciaccess \
 +
    librsvg2 \
 +
    libthai \
 +
    libtool-ltdl \
 +
    libwayland-client \
 +
    libwayland-server \
 +
    libxshmfence \
 +
    mesa-libEGL \
 +
    mesa-libGL \
 +
    mesa-libgbm \
 +
    mesa-libglapi \
 +
    pango \
 +
    pixman \
 +
    xorg-x11-fonts-75dpi \
 +
    xorg-x11-fonts-misc \
 +
    poppler-data \
 +
    php-yaml
  
We're also going to add the EPEL repository:
 
  
[EPEL]
+
'''Phantomjs''' is a special component used to generate PDF graphs dynamically. Install it through the command:
Name = EPEL
 
baseurl = http://dl.fedoraproject.org/pub/epel/6/$basearch/
 
enabled = 1
 
gpgcheck = 0
 
  
Please refresh your repository information by this command:
 
  
  yum makecache
+
  dnf install -y http://firefly.artica.es/centos8/wmi-1.3.14-4.el7.art.x86_64.rpm
  
=== Automated Install by using the Pandora FMS Repository ===
+
'''Server dependencies'''
  
You're going to need YUM and access to internet. First, you're required to create a reference to the Pandora FMS official repository for CentOS 6. This also applies for the usage under RHEL6.
+
Once console dependencies are installed, install those of the '''server''':
  
  vi /etc/yum.repos.d/pandorafms.repo
+
  dnf install -y  GeoIP \
   
+
GeoIP-GeoLite-data \
Add this contents:
+
dwz \
 +
efi-srpm-macros \
 +
ghc-srpm-macros \
 +
go-srpm-macros \
 +
ocaml-srpm-macros \
 +
openblas-srpm-macros \
 +
perl \
 +
perl-Algorithm-Diff \
 +
perl-Archive-Tar \
 +
perl-Archive-Zip \
 +
perl-Attribute-Handlers \
 +
perl-B-Debug \
 +
perl-CPAN \
 +
perl-CPAN-Meta \
 +
perl-CPAN-Meta-Requirements \
 +
perl-CPAN-Meta-YAML \
 +
perl-Compress-Bzip2 \
 +
perl-Config-Perl-V \
 +
perl-DBD-MySQL \
 +
perl-DBI \
 +
perl-DB_File \
 +
perl-Data-Dump \
 +
perl-Data-OptList \
 +
perl-Data-Section \
 +
perl-Devel-PPPort \
 +
perl-Devel-Peek \
 +
perl-Devel-SelfStubber \
 +
perl-Devel-Size \
 +
perl-Digest-HMAC \
 +
perl-Digest-SHA \
 +
perl-Encode-Locale \
 +
perl-Encode-devel \
 +
perl-Env \
 +
perl-ExtUtils-CBuilder \
 +
perl-ExtUtils-Command \
 +
perl-ExtUtils-Embed \
 +
perl-ExtUtils-Install \
 +
perl-ExtUtils-MM-Utils \
 +
perl-ExtUtils-MakeMaker \
 +
perl-ExtUtils-Manifest \
 +
perl-ExtUtils-Miniperl \
 +
perl-ExtUtils-ParseXS \
 +
perl-File-Fetch \
 +
perl-File-HomeDir \
 +
perl-File-Listing \
 +
perl-File-Which \
 +
perl-Filter \
 +
perl-Filter-Simple \
 +
perl-Geo-IP \
 +
perl-HTML-Parser \
 +
perl-HTML-Tagset \
 +
perl-HTML-Tree \
 +
perl-HTTP-Cookies \
 +
perl-HTTP-Date \
 +
perl-HTTP-Message \
 +
perl-HTTP-Negotiate \
 +
perl-IO-HTML \
 +
perl-IO-Socket-INET6 \
 +
perl-IO-Zlib \
 +
perl-IO-stringy \
 +
perl-IPC-Cmd \
 +
perl-IPC-SysV \
 +
perl-IPC-System-Simple \
 +
perl-JSON \
 +
perl-JSON-PP \
 +
perl-LWP-MediaTypes \
 +
perl-Locale-Codes \
 +
perl-Locale-Maketext \
 +
perl-Locale-Maketext-Simple \
 +
perl-MRO-Compat \
 +
perl-Math-BigInt \
 +
perl-Math-BigInt-FastCalc \
 +
perl-Math-BigRat \
 +
perl-Memoize \
 +
perl-Module-Build \
 +
perl-Module-CoreList \
 +
perl-Module-CoreList-tools \
 +
perl-Module-Load \
 +
perl-Module-Load-Conditional \
 +
perl-Module-Loaded \
 +
perl-Module-Metadata \
 +
perl-NTLM \
 +
perl-Net-HTTP \
 +
perl-Net-Ping \
 +
perl-NetAddr-IP \
 +
perl-Package-Generator \
 +
perl-Params-Check \
 +
perl-Params-Util \
 +
perl-Perl-OSType \
 +
perl-PerlIO-via-QuotedPrint \
 +
perl-Pod-Checker \
 +
perl-Pod-Html \
 +
perl-Pod-Parser \
 +
perl-SelfLoader \
 +
perl-Socket6 \
 +
perl-Software-License \
 +
perl-Sub-Exporter \
 +
perl-Sub-Install \
 +
perl-Sys-Syslog \
 +
perl-Test \
 +
perl-Test-Harness \
 +
perl-Test-Simple \
 +
  perl-Text-Balanced \
 +
perl-Text-Diff \
 +
perl-Text-Glob \
 +
perl-Text-Template \
 +
perl-Thread-Queue \
 +
perl-Time-Piece \
 +
perl-TimeDate \
 +
perl-Try-Tiny \
 +
perl-Unicode-Collate \
 +
perl-WWW-RobotRules \
 +
perl-XML-NamespaceSupport \
 +
perl-XML-Parser \
 +
perl-XML-SAX \
 +
perl-XML-SAX-Base \
 +
perl-XML-Simple \
 +
perl-XML-Twig \
 +
perl-autodie \
 +
perl-bignum \
 +
perl-devel \
 +
perl-encoding \
 +
perl-experimental \
 +
perl-inc-latest \
 +
perl-libnetcfg \
 +
perl-libwww-perl \
 +
perl-local-lib \
 +
perl-open \
 +
perl-perlfaq \
 +
perl-srpm-macros \
 +
perl-utils \
 +
perl-version \
 +
python-srpm-macros \
 +
python3-pyparsing \
 +
python3-rpm-macros \
 +
qt5-srpm-macros \
 +
redhat-rpm-config \
 +
rust-srpm-macros \
 +
systemtap-sdt-devel \
 +
perl-TermReadKey \
 +
perl \
 +
perl-DBD-MySQL \
 +
perl-DBI
  
Centos6
+
After this, the following additional dependencies from different components must be installed from Pandora FMS public repository:
  
  [artica_pandorafms]
+
  dnf install -y <nowiki>http://firefly.artica.es/centos8/wmi-1.3.14-4.el7.art.x86_64.rpm</nowiki>
  name=CentOS6 - PandoraFMS official repo
+
  dnf install -y <nowiki>http://firefly.artica.es/centos8/perl-Net-Telnet-3.04-1.el8.noarch.rpm</nowiki>
  baseurl=http://firefly.artica.es/centos6
+
  dnf install -y <nowiki>http://firefly.artica.es/centos7/xprobe2-0.3-12.2.x86_64.rpm</nowiki>
gpgcheck=0
 
enabled=1
 
  
Centos 7
+
{{Tip|Although you see in the <code>xprobe</code> installation link that the package is within CentOS 7 repository, it works properly in both versions.}}
  
[artica_pandorafms]
+
if necessary, add all [[Pandora:Documentation_en:Discovery |Discovery]] dependencies for each section.
name=CentOS6 - PandoraFMS official repo
 
baseurl=http://firefly.artica.es/centos7
 
gpgcheck=0
 
enabled=1
 
  
 +
At this point you can continue with the configuration of the operating system and database by following [[Pandora:Documentation_en:Installing#OS_settings_and_database_creation |this link]]<br><br><br>
  
Please refresh your repository information:
+
==== Dependency installation on CentOS 7 ====
  
yum makecache
+
'''Console dependencies'''
  
You can now install Pandora FMS along with the MySQL-Server. This is an 'optional' dependency. You're required to have a MySQL server if you don't already have one.
+
Once with repositories and <b>percona</b> installed we can start to install all the necessary dependencies for the <b>console</b>:
  
yum install pandorafms_console pandorafms_server mysql-server
 
  
This is going to download all RPMs and dependencies, install them for you and leave the system ready for setup.
+
yum install -y \
 +
    php \
 +
    postfix \
 +
    php-mcrypt \
 +
    php-cli \
 +
    php-gd \
 +
    php-curl \
 +
    php-session \
 +
    php-mysqlnd \
 +
    php-ldap \
 +
    php-zip \
 +
    php-zlib \
 +
    php-fileinfo \
 +
    php-gettext \
 +
    php-snmp \
 +
    php-mbstring \
 +
    php-pecl-zip \
 +
    php-xmlrpc \
 +
    libxslt \
 +
    wget \
 +
    php-xml \
 +
    httpd \
 +
    mod_php \
 +
    atk \
 +
    avahi-libs \
 +
    cairo \
 +
    cups-libs \
 +
    fribidi \
 +
    gd \
 +
    gdk-pixbuf2 \
 +
    ghostscript \
 +
    graphite2 \
 +
    graphviz \
 +
    gtk2 \
 +
    harfbuzz \
 +
    hicolor-icon-theme \
 +
    hwdata \
 +
    jasper-libs \
 +
    lcms2 \
 +
    libICE \
 +
    libSM \
 +
    libXaw \
 +
    libXcomposite \
 +
    libXcursor \
 +
    libXdamage \
 +
    libXext \
 +
    libXfixes \
 +
    libXft \
 +
    libXi \
 +
    libXinerama \
 +
    libXmu \
 +
    libXrandr \
 +
    libXrender \
 +
    libXt \
 +
    libXxf86vm \
 +
    libcroco \
 +
    libdrm \
 +
    libfontenc \
 +
    libglvnd \
 +
    libglvnd-egl \
 +
    libglvnd-glx \
 +
    libpciaccess \
 +
    librsvg2 \
 +
    libthai \
 +
    libtool-ltdl \
 +
    libwayland-client \
 +
    libwayland-server \
 +
    libxshmfence \
 +
    mesa-libEGL \
 +
    mesa-libGL \
 +
    mesa-libgbm \
 +
    mesa-libglapi \
 +
    pango \
 +
    pixman \
 +
    xorg-x11-fonts-75dpi \
 +
    xorg-x11-fonts-misc \
 +
    poppler-data \
 +
    php-yaml
  
=== Manual Installation by RPM Files ===
+
<b>Phantomjs</b> is a special component used to generate PDF graphs dynamically. Install if from Pandora FMS servers through the command:
  
Most of the dependencies should be resolved using YUM or any other automatic package. All dependencies are marked as needed packages in the RPM definition:
+
yum install -y <nowiki>https://firefly.pandorafms.com/centos8/phantomjs-2.1.1-1.el7.x86_64.rpm</nowiki>
  
yum install php php-gd graphviz php-mysql php-pear-DB  php-mbstring php-ldap php-snmp \
+
'''Server dependencies'''
php-ldap php-common php-zip nmap
 
 
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 sudo xprobe2 make perl-CPAN perl-JSON net-snmp-perl perl-Time-HiRes perl-XML-Twig \
 
perl-Encode-Locale
 
  
Some dependencies (like 'wmic' or 'xprobe2') aren't contained in the official RHEL repositories. We're providing them on our Sourceforge download page as [https://sourceforge.net/projects/pandora/files/Tools%20and%20dependencies%20%28All%20versions%29/ Tools and Dependencies].
+
To install all dependencies necessary for the <b>server</b> execute the following commands:
  
Some other dependencies like 'graphviz', 'perl-XML-Simple' or 'perl-HTML-Tree' are in the additional repositories we've installed before. It's important that you activate/install it '''prior''' to executing yum.
+
yum install -y \
 +
    vim \
 +
    fping \
 +
    perl-IO-Compress \
 +
    nmap \
 +
    sudo \
 +
    perl-Time-HiRes \
 +
    nfdump \
 +
    net-snmp-utils \
 +
    epel-release \
 +
    GeoIP \
 +
    groff-base \
 +
    initscripts \
 +
    iproute \
 +
    iptables \
 +
    libmnl \
 +
    libnetfilter_conntrack \
 +
    libnfnetlink \
 +
    libpcap \
 +
    lm_sensors-libs \
 +
    mailcap \
 +
    make \
 +
    mariadb-libs \
 +
    net-snmp \
 +
    net-snmp-agent-libs \
 +
    net-snmp-libs \
 +
    net-tools \
 +
    nmap \
 +
    nmap-ncat \
 +
    openssl \
 +
    perl \
 +
    perl-Business-ISBN \
 +
    perl-Business-ISBN-Data \
 +
    perl-Carp \
 +
    perl-Compress-Raw-Bzip2 \
 +
    perl-Compress-Raw-Zlib \
 +
    perl-DBD-MySQL \
 +
    perl-DBI \
 +
    perl-Data-Dumper \
 +
    perl-Digest \
 +
    perl-Digest-MD5 \
 +
    perl-Encode \
 +
    perl-Encode-Locale \
 +
    perl-Exporter \
 +
    perl-File-Listing \
 +
    perl-File-Path \
 +
    perl-File-Temp \
 +
    perl-Filter \
 +
    perl-Font-AFM \
 +
    perl-Geo-IP \
 +
    perl-Getopt-Long \
 +
    perl-HTML-Format \
 +
    perl-HTML-Parser \
 +
    perl-HTML-Tagset \
 +
    perl-HTML-Tree \
 +
    perl-HTTP-Cookies \
 +
    perl-HTTP-Daemon \
 +
    perl-HTTP-Date \
 +
    perl-HTTP-Message \
 +
    perl-HTTP-Negotiate \
 +
    perl-HTTP-Tiny \
 +
    perl-IO-Compress \
 +
    perl-IO-HTML \
 +
    perl-IO-Socket-INET6 \
 +
    perl-IO-Socket-IP \
 +
    perl-IO-Socket-SSL \
 +
    perl-IO-stringy \
 +
    perl-JSON \
 +
    perl-LWP-MediaTypes \
 +
    perl-Mozilla-CA \
 +
    perl-Net-Daemon \
 +
    perl-Net-HTTP \
 +
    perl-Net-LibIDN \
 +
    perl-Net-SSLeay \
 +
    perl-Net-Telnet \
 +
    perl-NetAddr-IP \
 +
    perl-PathTools \
 +
    perl-PlRPC \
 +
    perl-Pod-Escapes \
 +
    perl-Pod-Perldoc \
 +
    perl-Pod-Simple \
 +
    perl-Pod-Usage \
 +
    perl-Scalar-List-Utils \
 +
    perl-Socket \
 +
    perl-Socket6 \
 +
    perl-Storable \
 +
    perl-Sys-Syslog \
 +
    perl-Text-ParseWords \
 +
    perl-Time-HiRes \
 +
    perl-Time-Local \
 +
    perl-TimeDate \
 +
    perl-URI \
 +
    perl-WWW-RobotRules \
 +
    perl-XML-NamespaceSupport \
 +
    perl-XML-Parser \
 +
    perl-XML-SAX \
 +
    perl-XML-SAX-Base \
 +
    perl-XML-Simple \
 +
    perl-XML-Twig \
 +
    perl-constant \
 +
    perl-libs \
 +
    perl-libwww-perl \
 +
    perl-macros \
 +
    perl-parent \
 +
    perl-podlators \
 +
    perl-threads \
 +
    perl-threads-shared \
 +
    sudo \
 +
    systemd-sysv \
 +
    sysvinit-tools \
 +
    tcp_wrappers-libs
  
{{Warning|If you're using a version prior to RHEL6, some dependencies could have another name, e.g. 'perl-SNMP'. Under CentOS5, RHEL5, etc. it would be called 'net-snmp-perl'.}}
+
And finally install the following additional dependencies too from our public repository:
  
In order to install the RPM, just e.g. use the 'rpm -i' or the yum command directly:
+
yum install -y <nowiki>https://firefly.pandorafms.com/centos7/wmi-1.3.14-4.el7.art.x86_64.rpm</nowiki>
 +
yum install -y <nowiki>https://firefly.pandorafms.com/centos7/xprobe2-0.3-12.2.x86_64.rpm</nowiki>
  
rpm -i pandorafms_server-x.x-x.noarch.rpm
+
=== OS settings and database creation ===
  
or
+
To configure Pandora FMS by packages in CentOS, it will be necessary to define first the following variables for any of the two systems and that we will use in the following steps:
  
  yum install pandorafms_server-x.x-x.noarch.rpm
+
  PANDORA_CONSOLE=/var/www/html/pandora_console
 +
CONSOLE_PATH=/var/www/html/pandora_console
 +
PANDORA_SERVER_CONF=/etc/pandora/pandora_server.conf
 +
PANDORA_SERVER_BIN=/usr/bin/pandora_server
 +
PANDORA_HA_BIN=/usr/bin/pandora_ha
 +
PANDORA_TABLES_MIN=160
 +
DBHOST=127.0.0.1
 +
DBNAME=pandora
 +
DBUSER=pandora
 +
DBPASS=pandora
 +
DBPORT=3306
  
If you encounter any problems at the time you're trying to access the Pandora FMS Console installation web page, please check if SELinux is active: In this case, it's mandatory to deactivate it. Please follow the [[Pandora:FAQ#I_cannot_access_the_Pandora_Console_installation_web_page_in_CentOS.|FAQ]] procedures in such a case.
+
{{Warning|After this point the installation for CentOS 7 and CentOS 8 is common for both systems, if there is any step that is not common the operating system for which it is valid will be indicated in bold}}
  
  
{{Warning|RHEL and CentOS 5.x use PHP 5.1 by default. This version is '''not''' compatible with Pandora FMS. You're required to use PHP version 5.2 or above. Tested in php55w }}
+
After previous steps, disable <b>SELINUX</b> and the firewall.  
  
To do so, we recommend to use the following repository for CentOS6/RHEL6, which contains PHP 5.6:
+
setenforce 0
 +
sed -i -e "s/^SELINUX=.*/SELINUX=disabled/g" /etc/selinux/config
 +
systemctl disable firewalld --now
  
[remi]
+
{{Tip|If you decide to use '''Security-Enhanced Linux''' (SELinux) with Pandora FMS, follow [[Pandora:Documentation_en:Selinux|these instructions]].}}
name=Les RPM de remi pour Enterprise Linux 6 - $basearch
 
#baseurl=http://rpms.famillecollet.com/enterprise/6/remi/$basearch/
 
mirrorlist=http://rpms.famillecollet.com/enterprise/6/remi/mirror
 
enabled=1
 
gpgcheck=1
 
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-remi
 
  
 +
Then you may start configuring the database:
  
  [remi-php56]
+
  systemctl start mysqld
  name=Les RPM de remi de PHP 5.6 pour Enterprise Linux 6 - $basearch
+
  mysql -uroot -p$(grep "temporary password" /var/log/mysqld.log | rev | cut -d' ' -f1 | rev)
#baseurl=http://rpms.famillecollet.com/enterprise/6/php56/$basearch/
 
mirrorlist=http://rpms.famillecollet.com/enterprise/6/php56/mirror
 
# WARNING: If you enable this repository, you must also enable "remi"
 
enabled=1
 
gpgcheck=1
 
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-remi
 
  
 +
SET PASSWORD FOR 'root'@'localhost' = PASSWORD('Pandor4!');
 +
UNINSTALL PLUGIN validate_password;
 +
SET PASSWORD FOR 'root'@'localhost' = PASSWORD('pandora');
 +
quit
  
gpg key for remi repository could been found here: http://rpms.remirepo.net/RPM-GPG-KEY-remi
+
echo "create database $DBNAME" | mysql -uroot -ppandora -P$DBPORT -h$DBHOST
 +
echo "GRANT ALL PRIVILEGES ON $DBNAME.* TO \"$DBUSER\"@'%' identified by \"$DBPASS\"" | mysql -uroot -ppandora -P$DBPORT -h$DBHOST
  
== Installation under Debian and Ubuntu ==
+
Also generate the file <b>my.cnf</b>.
  
It's recommended to install Pandora FMS on a '''10.04''' version or above. On Debian Stable ('Squeeze') versions, it's possible to experience problems due to old versions of some required optional software, such as:
+
POOL_SIZE=$(grep -i total /proc/meminfo | head -1 | awk '{print $(NF-1)*0.4/1024}' | sed s/\\..*$/M/g)
The Debian LWP library does not implement some methods for SSL. This is necessary for the monitoring of Enterprise WEB modules to get fixed by installing a newer version of LWP by CPAN (manual method). You also require an fping to use the Enterprise ICMP Server. 'Squeeze' comes with version 5.0. You may install a newer version, using those packages. We're recommending to use the unofficial DEB or to compile a version for yourselves.
+
cat > /etc/my.cnf << EO_CONFIG_F
 +
[mysqld]
 +
datadir=/var/lib/mysql
 +
socket=/var/lib/mysql/mysql.sock
 +
user=mysql
 +
character-set-server=utf8
 +
skip-character-set-client-handshake
 +
# Disabling symbolic-links is recommended to prevent assorted security risks
 +
symbolic-links=0
 +
# Mysql optimizations for Pandora FMS
 +
# Please check the documentation in http://pandorafms.com for better results
 +
max_allowed_packet = 64M
 +
innodb_buffer_pool_size = $POOL_SIZE
 +
innodb_lock_wait_timeout = 90
 +
innodb_file_per_table
 +
innodb_flush_log_at_trx_commit = 0
 +
innodb_flush_method = O_DIRECT
 +
innodb_log_file_size = 64M
 +
innodb_log_buffer_size = 16M
 +
innodb_io_capacity = 100
 +
thread_cache_size = 8
 +
thread_stack    = 256K
 +
max_connections = 100
 +
key_buffer_size=4M
 +
read_buffer_size=128K
 +
read_rnd_buffer_size=128K
 +
sort_buffer_size=128K
 +
join_buffer_size=4M
 +
query_cache_type = 1
 +
query_cache_size = 64M
 +
query_cache_min_res_unit = 2k
 +
query_cache_limit = 256K
 +
sql_mode=""
 +
[mysqld_safe]
 +
log-error=/var/log/mysqld.log
 +
pid-file=/var/run/mysqld/mysqld.pid
 +
EO_CONFIG_F
  
  
{{Tip|Before installing any packages you need to add the official repositories for your version. For example: To install the packages snmp-mibs-downloader and libencode-locale-perl under Debian Squeeze, you're required to add the following repositories at the file /etc/apt/sources.list
+
Once the changes have been saved, it will be necessary to restart the <code>mysqld</code> service.
  
"deb http://ftp.us.debian.org/debian/ squeeze main non-free"
+
systemctl restart mysqld
<br>
 
"deb http://ftp.at.debian.org/debian-backports/ squeeze-backports main"
 
  
Alternatively, for Debian Wheezy:
+
Enable the services <code>mysql</code>, <code>apache</code> and <code>php</code>. 
  
"deb http://ftp.debian.org/debian wheezy-backports main"
+
systemctl enable mysqld --now
<br>
+
systemctl enable httpd --now
"deb http://ftp.us.debian.org/debian/ wheezy main non-free"
 
  
Once they have been added you need to execute 'apt-get update' to apply the changes.}}
+
If you use CentOS 8, execute:
 +
systemctl enable php-fpm --now
  
{{Tip|Due to the nature of Debian packaging (if you choose Debian or Ubuntu), you're required to have access to the internet or a local package repository to conduct the installation. A single dependency under Debian could have sub-dependencies. The installation without access an on-line repository could turn out to be very complex.}}
+
=== Pandora FMS console and server installation ===
  
=== Installation by using the Artica Private Repository ===
+
With all the environment ready, it's time to install <b>Pandora FMS</b>. The first thing will be to create a directory to store all the data. 
  
There's also a much faster and easier method: Just add the Artica Private Repository. It contains any and all the Ubuntu and Debian packages you might require.
+
mkdir $HOME/pandora && cd $HOME/pandora
  
In order to do so, please edit the file '/etc/apt/sources.list' and add the following line:
+
{{Warning|It will be necessary to download the packages of the <b>console</b>, <b>enterprise console</b> and <b>enterprise server</b> from Sourceforge or the links provided by the support team.}}
  
For Debian Squeeze:
+
In the OpenSource version:
deb http://firefly.artica.es/debian/squeeze /
 
  
For Debian Wheezy:
+
wget <nowiki>https://firefly.pandorafms.com/pandorafms/latest/RHEL_CentOS/pandorafms_agent_unix-7.0NG.noarch.rpm</nowiki>
  deb http://firefly.artica.es/debian/wheezy /
+
  wget <nowiki>https://firefly.pandorafms.com/pandorafms/latest/RHEL_CentOS/pandorafms_console-7.0NG.noarch.rpm</nowiki>
 +
wget <nowiki>https://firefly.pandorafms.com/pandorafms/latest/RHEL_CentOS/pandorafms_server-7.0NG.noarch.rpm</nowiki>
  
Execute as root (sudo)
+
With the packages already prepared, start the installation. In the case of the Enterprise console, you must have two more, the Enterprise console package and the Enterprise server package (which is a tarball file installed separate from RPM packages).
  
apt-get update
+
Package installation (after download):
  
Installation of Pandora FMS by apt-get:
+
yum install -y $HOME/pandora/pandorafms*.rpm
  
<pre>
+
For '''Enterprise''' tarball, execute:
[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
 
</pre>
 
  
=== Manual Installation by DEB Packages ===
+
tar xvfz $HOME/pandora/pandorafms_server* && cd pandora_server && ./pandora_server_installer --install --ha; cd -
  
Under Debian or Ubuntu, the dependencies are the following:
+
Once the process is finished, populate the database:  
  
Server:
+
mysql -u$DBUSER -p$DBPASS -P$DBPORT -h$DBHOST $DBNAME < $PANDORA_CONSOLE/pandoradb.sql
 +
mysql -u$DBUSER -p$DBPASS -P$DBPORT -h$DBHOST $DBNAME < $PANDORA_CONSOLE/pandoradb_data.sql
  
snmp snmpd libtime-format-perl libxml-simple-perl libdbi-perl libnetaddr-ip-perl
+
Then configure the console.
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 libencode-locale-perl
 
  
 +
cat > $CONSOLE_PATH/include/config.php << EO_CONFIG_F
 +
<?php
 +
\$config["dbtype"] = "mysql";
 +
\$config["dbname"]="$DBNAME";
 +
\$config["dbuser"]="$DBUSER";
 +
\$config["dbpass"]="$DBPASS";
 +
\$config["dbhost"]="$DBHOST";
 +
\$config["homedir"]="/var/www/html/pandora_console";
 +
\$config["homeurl"]="/pandora_console";
 +
error_reporting(0);
 +
\$ownDir = dirname(__FILE__) . '/';
 +
include (\$ownDir . "config_process.php");
 +
EO_CONFIG_F
  
{{Tip|If the 'wmi-client' package is not available in the repositories, you're required to download it from the [http://sourceforge.net/projects/pandora/files/Tools%20and%20dependencies%20(All%20versions)/DEB%20Debian,%20Ubuntu/ Pandora FMS Sourceforge website.]}}
+
cat > /etc/httpd/conf.d/pandora.conf << EO_CONFIG_F
 +
<Directory "/var/www/html">
 +
    Options Indexes FollowSymLinks
 +
    AllowOverride All
 +
    Require all granted
 +
</Directory>
 +
EO_CONFIG_F
  
Console:
+
sed -i -e "s/php_flag engine off//g" $PANDORA_CONSOLE/images/.htaccess
 +
sed -i -e "s/php_flag engine off//g" $PANDORA_CONSOLE/attachment/.htaccess
  
  php5 libapache2-mod-php5 apache2 mysql-server php5-gd php5-mysql php-pear php5-snmp php-db php-gettext
+
  chmod 600 $CONSOLE_PATH/include/config.php
  graphviz mysql-client php5-curl php5-xmlrpc php5-ldap
+
chown apache. $CONSOLE_PATH/include/config.php
 +
  mv $CONSOLE_PATH/install.php $CONSOLE_PATH/install.done
  
In order to install the Server package or the console, you first have to implement all of the required dependencies. This is done by installing all the before mentioned packages by using the command ''apt-get'' along with root privileges:
 
  
apt-get install snmp snmpd libtime-format-perl libxml-simple-perl libdbi-perl libnetaddr-ip-perl \
+
Then prepare the file <b>php.ini</b>.  
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
 
  
 +
sed -i -e "s/^max_input_time.*/max_input_time = -1/g" /etc/php.ini
 +
sed -i -e "s/^max_execution_time.*/max_execution_time = 0/g" /etc/php.ini
 +
sed -i -e "s/^upload_max_filesize.*/upload_max_filesize = 800M/g" /etc/php.ini
 +
sed -i -e "s/^memory_limit.*/memory_limit = 500M/g" /etc/php.ini
  
{{Tip|The character '\' is used as a line divider. You may copy and paste it directly out of this documentation into the console and the line breaks will be considered as such.}}
+
cat > /var/www/html/index.html << EOF_INDEX
 +
<meta HTTP-EQUIV="REFRESH" content="0; url=/pandora_console/">
 +
EOF_INDEX
  
 +
If you use CentOS 8, execute in addition:
  
This command would install all the dependencies required to install the Pandora FMS Server and its console into a Debian or Ubuntu system.
+
systemctl restart php-fpm
                   
+
systemctl restart httpd
The installation with the DEB packages is very easy. First, you're required to download all the necessary packages. Subsequently, you're required to execute the following commands in the same directory in which you've put the packages.
 
  
In this example they are installed all together, but it could also be just one of them.
+
The server configuration file will be prepared: 
  
  dpkg -i pandorafms-console_xxx.deb pandorafms-server_xxxx.deb
+
  sed -i -e "s/^dbhost.*/dbhost $DBHOST/g" $PANDORA_SERVER_CONF
 +
sed -i -e "s/^dbname.*/dbname $DBNAME/g" $PANDORA_SERVER_CONF
 +
sed -i -e "s/^dbuser.*/dbuser $DBUSER/g" $PANDORA_SERVER_CONF
 +
sed -i -e "s|^dbpass.*|dbpass $DBPASS|g" $PANDORA_SERVER_CONF
 +
sed -i -e "s/^dbport.*/dbport $DBPORT/g" $PANDORA_SERVER_CONF
  
Once the command has been executed, you might see that some dependencies are missing. If so, you can try to solve it automatically by using the following command:
+
In the <b>Enterprise</b> version, enable the ([[Pandora:Documentation_en:HA|HA]]) service.
  
  apt-get -f install
+
  systemctl enable pandora_ha --now
 +
service tentacle_serverd start
  
This will attempt to download all the necessary missing packages from the automated installation of Pandora FMS on the system. Once the necessary packages have been installed, you're required to continue with the installation of all Pandora FMS components.
 
  
In order to complete the installation of the Pandora FMS Console, you have to access the console URL and follow the steps suggested by the installation wizard. If the console is installed on a server with the IP of e.g. '10.20.34.54', you're required to enter the following URL:
+
In the <b>Community</b> version, pandora_ha service does not exist, so execute the following commands to enable the server:  
  
  http://10.20.34.54/pandora_console
+
  systemctl enable pandora_server --now
 +
systemctl start pandora_server
 +
service tentacle_serverd start
  
=== Uninstalling Pandora FMS ===
 
  
dpkg -r pandorafms-console-enterprise
+
Enable the <code>cron</code> of the console:
dpkg -r pandorafms-console
 
  
== Installation in FreeBSD ==
+
echo "* * * * * root wget -q -O - --no-check-certificate http://127.0.0.1/pandora_console/enterprise/cron.php >> /var/www/html/pandora_console/log/cron.log" >> /etc/crontab
  
To install Pandora FMS server, it is recommended FreeBSD 10.x or later.
+
Then you may go to the CentOS server IP and enter Pandora FMS console and check the service is running properly:
If you want to install it to FreeBSD 9.x or earlier with following instructions, package management system of FreeBSD should be updated to pkgng.
 
  
=== Previous Dependencies Installation ===
+
[[Image:Pandora_login.png|center|800px]]
  
In FreeBSD, the dependencies are the following:
+
With these steps we will have a basic installation of Pandora FMS. If necessary, all [[Pandora:Documentation_en:Discovery |Discovery]] dependencies should be added for each section.
  
Server:
+
It is recommended to [[Pandora:Documentation_en:Installing#Pandora_FMS_Agent_Installation |install the agent]] to automonitor the server.
  
p5-DBI p5-Mail-Sendmail p5-NetAddr-IP p5-XML-Simple p5-Time-Format p5-HTML-Parser
+
<br><br><br>
p5-Net-Traceroute-PurePerl p5-IO-Socket-INET6 p5-DBD-mysql p5-XML-Twig p5-JSON
 
net-snmp nmap xprobe coreutils net-snmp wmi-client
 
  
In order to install the Pandora FMS Server, you're required to implement all the dependencies before doing so. It's recommended to do so by using pkg command.
+
=== License application ===
 +
Pandora FMS <b>Enterprise</b> version is associated with an individual key for each installation. In order to use the Enterprise features and perform automatic updates of the console, it is necessary to enter the license number provided by Artica. From Pandora FMS version 748 on, the server is installed with a trial license valid for a maximum of 100 agents and one month of use.  
  
You may install all the necessary dependencies in the following way:
+
If you want to expand this license, please contact your trusted commercial or fill in the following [https://pandorafms.com/contact/ contact form]
  
e.g.) p5-DBI installation.
+
The <b>Community</b> version does not require any license for its use.
pkg install p5-DBI
 
  
Console:
+
== Installation by packages on RHEL 7/8 ==
  
apache24, php5, php5-snmp, php5-session, php5-gettext, php5-mbstring, php5-ldap,
+
The installation of Pandora FMS on RHEL 7 and RHEL 8 systems is an Enterprise service. You can consult how to install on these systems by contacting your trusted commercial or by filling out the following [https://pandorafms.com/contact/ contact form]
php5-mysql, php5-gd, php5-zip, php5-zlib, php5-json, php5-curl, php5-filter, pear,
 
pear-DB, pear-XML_RPC, graphviz
 
  
In order to install the Pandora FMS Console, you will have to implement all of the before mentioned dependencies. You may use the packages to do so.
+
== Installation under Docker ==
 
 
=== Console Installation ===
 
 
 
There are no Pandora FMS Console package files for FreeBSD. It's recommended to install the pandora console by using the installer.
 
 
 
How to install it by the installer is described in the section named 'Manual Installation from Sources in Linux/Unix' below.
 
 
 
Under FreeBSD with apache 2.2, the Pandora FMS console directory is:
 
  
/usr/local/www/apache22/data/pandora_console
+
We have an entry in the docker hub website explaining how to mount a Pandora FMS stack based on CentOS 8 step by step in the link:
 +
https://hub.docker.com/r/pandorafms/pandorafms-open-stack-el8
  
=== Server Installation ===
+
It is also possible to install through a <code>yaml</code> file, as a quick installation method. The following explains how to perform this deployment via <code>docker-compose</code>.
  
There are no Pandora FMS Server package files for FreeBSD. You're required to install the Pandora Server by using the installer.
+
First, you need to have installed in the system docker and docker compose, installation documentation: https://docs.docker.com/get-docker/
  
How to install it by the installer is described in the section named 'Manual Installation from Sources in Linux / UNIX' below.
+
Once installed, we will use the <code>yaml</code> file from the official PandoraFMS repository:
  
The file locations and startup script structures are different from Linux. We're going to show the FreeBSD-specific procedures below.
+
mkdir $HOME/pandorafms; cd $HOME/pandorafms
 +
wget https://raw.githubusercontent.com/pandorafms/pandorafms/develop/extras/docker/centos8/docker-compose.yml
 +
docker-compose -f $HOME/pandorafms/docker-compose.yml up
  
After the installation, you're required to add the following lines to the '/etc/rc.conf' file:
+
We wait a few seconds for the download and configuration of the environment. You can access to the PFMS console from the URL:
  
  pandora_server_enable="YES"
+
  http://127.0.0.1:8080/pandora_console
tentacle_server_enable="YES"
 
  
These settings are required to enable Pandora, the Pandora Servers and Tentacle. Otherwise, they are '''not''' going to be launched.
+
Use “admin” as user  and “pandora” as password.
  
On FreeBSD, most of the Pandora server's files are gong to be installed in the directory named '/usr/local'.
+
==  Uninstalling Pandora FMS  ==
  
pandora_server, tentacle_server:
+
Just execute the command
/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 the ones under Linux.
 
  
=== Agent Installation ===
+
yum remove pandorafms_console pandorafms_server
  
There are no Pandora FMS Agent package files for FreeBSD. It's recommended to install the Pandora Agent by using the installer.
+
If MySQL is installed but it is no longer needed, it can also be deleted with the same command:
  
How to install the agent by the installer is described in the section named 'Manual Installation from Sources under Linux / UNIX' below.
+
yum remove Percona-Server*
  
The file locations and startup script structures are different from the ones under Linux. We're going to show the FreeBSD specific procedures below.
+
== Custom Installation ==
 +
=== Manual Installation from Sources under Linux / UNIX / MAC OS ===
  
After the installation, you're required to add the following line to the file '/etc/rc.conf':
+
It will be necessary to install all dependencies installed depending of the OS, and then download the files in '''tarball''' format (<code>.tar. gz</code>,<code>.tgz</code> or <code>.tar. bz2</code>) and unzip them. To do it, locate the latest version of Pandora FMS and download the files from here: https://sourceforge.net/projects/pandora/files/.
  
pandora_agent_enable="YES"
 
  
To enable the Pandora FMS Agent, these settings are required. Otherwise, it's '''not''' going to be launched.
+
==== Console Installation ====
  
On FreeBSD, the majority of the files of the Pandora FMS Agent are installed in the directory '/usr/local'.
+
Once you have opened the console zip file, follow these steps:
  
Agent:
+
1. Acquire root privileges by entering:
/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 the ones under Linux.
 
 
 
== Installation in NetBSD ==
 
 
 
From versions 5.0 and above, Pandora FMS supports the use of NetBSD.
 
 
 
=== Previous Dependencies Installation ===
 
 
 
In NetBSD the dependencies are as follows:
 
 
 
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 FMS Server, you are required to implement all of the dependencies before doing so. It's recommended to be done by using 'pkgsrc'.
 
 
 
You may install all dependencies like this:
 
 
 
e.g.) p5-DBI installation.
 
cd /usr/pkgsrc/databases/p5-DBI
 
make
 
make install
 
 
 
Subsequently, you're required to install 'Net::Traceroute::PurePerl' and 'LWP::Simple' using CPAN.
 
 
 
perl -MCPAN -e 'install Net::Traceroute::PurePerl'
 
perl -MCPAN -e 'install LWP::Simple'
 
 
 
'xprobe' is also required to be installed by compiling the source package.
 
 
 
You may download it from [http://sourceforge.net/projects/xprobe/files/latest/here.]
 
 
 
If you're unable to compile it without some errors showing up, please modify the 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 FMS Console, you're required to implement all of the dependencies before doing so. You may use 'pkgsrc' for that.
 
 
 
In addition, you're required to install the 'XML_RPC' using the 'pear' command as shown below.
 
 
 
pear install XML_RPC
 
 
 
=== Console Installation ===
 
 
 
There are no Pandora FMS Console package files for NetBSD. You're required to install the pandora console by using the installer.
 
 
 
How to install it by the installer is described in the section named 'Manual Installation from Sources in Linux/Unix' below.
 
 
 
On NetBSD with apache 2.2, the Pandora FMS Console directory is the one mentioned below.
 
 
 
/usr/pkg/share/httpd/htdocs/pandora_console
 
 
 
=== Server Installation ===
 
 
 
There are no Pandora FMS Server package files for NetBSD. You're required install the pandora server by using the installer.
 
 
 
How to install it by the installer is described in the section named 'Manual Installation from Sources in Linux/Unix' below.
 
 
 
The file locations and startup script structures are different from the one under Linux. We're going to show the NetBSD specific procedures below.
 
 
 
After the installation, you're required to add the following lines to the '/etc/rc.conf':
 
 
 
pandora_server="YES"
 
tentacle_server="YES"
 
 
 
To enable the Pandora Servers, Pandora and Tentacle, these settings are required. Otherwise, they are '''not''' going to be launched.
 
 
 
On NetBSD, most of the Pandora FMS Server files are installed under '/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 the ones under Linux.
 
 
 
=== Agent Installation ===
 
 
 
There are no Pandora FMS Agent package files for NetBSD. You're required to install the Pandora FMS Agent by using the installer.
 
 
 
How to install an agent by the installer is described in the section named 'Manual Installation from Sources in Linux/Unix' below. The file locations and startup script structures are different from the ones under Linux. We're going to show the NetBSD specific procedures below.
 
 
 
After the installation, you're required to add the following line to the '/etc/rc.conf':
 
 
 
pandora_agent="YES"
 
 
 
To enable the Pandora FMS Agent, these settings are required. Otherwise they are '''not''' going to be launched.
 
 
 
On NetBSD, most files of the Pandora FMS Agent are installed in the directory named '/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 the ones under Linux.
 
 
 
== Manual Installation from Sources under Linux / UNIX / MAC OS ==
 
 
 
This option is especially important in cases where you intend to utilize the development version's code or directly from the code repositories.
 
 
 
=== Previous Installation of Necessary Software ===
 
 
 
As you're going to build Pandora FMS from the sources, you'll require the basic software in order to compile and install software from the code. Depending on the use of one distribution or another, you're required to install packages such as 'make', 'gcc' and others. Furthermore, it's recommended to review the corresponding dependencies section to your distribution.
 
 
 
Under Debian and Ubuntu there is a metapackage which contains all of them:
 
 
 
apt-get install build-essential subversion
 
 
 
Under SUSE, Redhat or Fedora, you're required to install several packages:
 
 
 
zypper install make automake subversion
 
 
 
=== Download from Sources ===
 
 
 
The easiest way is to download the sources in the 'tarball' format (.tar.gz, .tgz or .tar.bz2) and decompress them.
 
For it, you have to go to the Pandora official web site and into the download section at http://pandorafms.com.
 
 
 
Other interesting option if you want to keep well informed and to use the latest code, stable or in development, is using the client from Subversion (svn) code version system.  You may visit the development version at Pandora FMS official web site project http://pandorafms.org/index.php?sec=community&sec2=development&lang=es for it.
 
 
 
To download the development version code using the command line from the SVN client:
 
 
 
svn co https://svn.code.sf.net/p/pandora/code/
 
 
 
=== Agent Installation ===
 
 
 
The agents don't require compilation or preparation. Once you're acquired the agent package named 'pandorafms_3.0_unix.tar.gz', please perform the following:
 
 
 
1. Open a shell and acquire root privileges by entering:
 
 
 
su -
 
 
 
2. Copy the package to '/tmp' and execute:
 
 
 
tar xvzf pandorafms_3.0_unix.tar.gz
 
./pandora_agent_installer --install
 
 
 
3. Start the agent manually by executing:
 
 
 
/etc/init.d/pandora_agent_daemon start
 
 
 
==== Custom Agent Installation ====
 
 
 
From Pandora FMS versions 3.1 and above, the agent is able to be completely installed in a custom defined directory, like e.g. '/opt/pandora'. This custom-defined directory is going to contain everything the agent has, e.g. configuration files, log files, plug ins and even man pages.
 
 
 
To use this method, just enter:
 
 
 
./pandora_agent_install --install /opt/pandora
 
 
 
The only file that Pandora FMS is going to create outside it's defined directory is the main agent's service launcher in '/etc/init.d/pandora_agent_daemon' (or equivalent under other UNIX branches) and the startup level link e.g. '/etc/rc.d/rc2.d/S90pandora_agent_daemon'.
 
 
 
It's also possible to perform an installation to execute the agent by other means than root. To execute it by the user 'Pandora', you have to e.g. install it by using the following command:
 
 
 
./pandora_agent_install --install /home/pandora pandora
 
 
 
When specifying a custom user, the agent has to be installed to a custom location where that user has to have write permissions ('/home/pandora' in the previous example).
 
 
 
<br>
 
{{Warning|User '''pandora''' is disabled by default on most installs -by security-, you if you want to use pandora user for agent execution you first need to activate by setting a valid shell in ''/etc/passwd'' file }}
 
 
 
{{Warning|For people stumbling upon this in an '''OS X 10.11+''' era (El Capitan or newer): Apple has added a whole new layer of security in OS X. They have taken away some privileges from root. When installing the Agent Pandora will appear as a restricted process. Only restricted processes which are signed by Apple will be able to modify these files. However, you can disable this security system by booting in recovery mode and disabling it in a Terminal by doing: csrutil disable.}}
 
 
 
==== Agent in Proxy Mode ====
 
 
 
In order to use proxy mode in the UNIX agent, you need to copy the tentacle_server on /usr/bin. Tentacle server is not installed with the agent by default. This is an exception on Windows plattform, where the tentacle_server comes with the agent package by default.
 
 
 
You will find the tentacle_server in your Linux server setup, copy the /usr/bin/tentacle_server file to your agent host and be sure it has execution permissions:
 
 
 
chmod 755 /usr/bin/tentacle_server
 
 
 
=== Console Installation ===
 
 
 
Once you've opened the console and arrived at the location of the compressed file named 'pandorafms_console-3.0.0.tar.gz' or similar, please follow the below mentioned steps:
 
 
 
1. We acquire root privileges by entering:
 
  
 
  su -
 
  su -
  
2. We're copying it to '/tmp' and execute:
+
2. Copy to '/tmp' and execute:
  
  tar xvzf pandorafms_console-3.0.0.tar.gz  
+
  tar xvzf pandorafms_console-X.Y.tar.gz  
 
  cd pandora_console
 
  cd pandora_console
 
  ./pandora_console_install --install
 
  ./pandora_console_install --install
  
=== Server Installation ===
+
==== Server Installation ====
  
Once you've opened the console and arrived at the location of the compressed file named 'pandorafms_server-3.0.0.tar.gz' or similar, please follow the below mentioned steps:
+
Once you have opened the server zip file named <code>pandorafms_server-3.0.0.tar.gz</code> or similar, follow the steps described below:
  
1. We acquire root privileges:
+
1. Acquire root privileges. You are the only one responsible for said key:
  
 
  su -  
 
  su -  
  
2. We're copying it to '/tmp' and execute:
+
2. Copy it to a directory where you can unzip the file (in this example <code>/tmp</code> y used again) and execute:
  
  tar xvzf pandorafms_server-3.0.0.tar.gz  
+
  tar xvzf pandorafms_server-X.Y.tar.gz  
 
  cd pandora_server
 
  cd pandora_server
 
  ./pandora_server_installer --install
 
  ./pandora_server_installer --install
  
If you're experiencing any dependency-related problems, you're required to rectify them before attempting any installation. We might be able to force the installation and ignore the problems with the dependencies, but Pandora FMS wouldn't work properly in this case.
+
If you experience any dependency-related problems, fix them before attempting any installation. It might be possible to force the installation and ignore the problems with the dependencies, but Pandora FMS will not work properly in that case.
  
==== Uninstallation / Manual Wipe from Server ====
+
==== Server Manual Installation (from source code) ====
  
If we have installed / updated several different versions, using different installation methods (RPM or tarball), we might reach a point in which we have various versions mixed up that could be using wrong versions of libraries or the server itself. The following procedure is aimed at detecting which versions are there and manually erase them:
+
Alternatively to the general installation script, you can "compile" the Pandora FMS code through the Perl interpreter of your system. This process simply installs the minimum libraries and executables, but does not alter the boot script system, maintenance scripts, configuration or anything else that strictly concerns the application and its libraries. This process is recommended when the server code must be updated, but without overwriting its configuration.
  
Binaries should always be located under '/usr/local/bin', containing a link to '/usr/bin'. To test this, please enter the following commands:
+
To do it properly, unzip your server code to <code>/tmp</code>, as described in the previous step.
  
ls -la /usr/local/bin/pandora_server
+
1. Acquire root privileges. You are the only one responsible for that key:
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 you to learn where they are and whether there are various ones or not:
+
  su -  
 
 
  find / -name "WMIServer.pm"
 
 
 
This is going to display a complete path where Pandora's library is installed, e.g.:
 
 
 
/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
+
2. Copy it to the directory where you are unzipping files (<code>/tmp</code> in this example) and once there, execute:
/usr/local/share/perl/PandoraFMS/WMIServer.pm
 
  
In such a case, we wouldn't know which one is in use, so our best option is to remove the entire directories and reinstall Pandora FMS:
+
  tar xvzf pandorafms_server-X.Y.tar.gz  
 
 
  rm -Rf /usr/local/share/perl/5.10.0/PandoraFMS
 
  rm -Rf /usr/local/share/perl/PandoraFMS/
 
 
 
It's always a good idea to backup the '/etc/pandora/pandora_server.conf' ... just in case.
 
 
 
=== Server Code Update: Compilation and Manual Installation of the Server ===
 
 
 
There is another way other than via the generic installation script. You could 'compile' the Pandora FMS code by the Perl interpreter of its system. This process simply installs the libraries and the minimum required executables, but it doesn't touch the starting script system, the maintenance scripts, the configuration or any other thing other than the application and its libraries. This process is recommended if someone is forced to update the server code without overwriting its configuration.
 
 
 
Please decompress your server code under '/tmp' and follow the below mentioned steps:
 
 
 
1.We acquire root privileges:
 
 
 
2. We're copying it to '/tmp' and execute:
 
 
 
  tar xvzf pandorafms_server-3.0.0.tar.gz  
 
 
  cd pandora_server
 
  cd pandora_server
 
  perl Makefile.PL
 
  perl Makefile.PL
Line 1,028: Line 1,340:
 
  make install
 
  make install
  
Please observe all errors which get returned by the console. If any dependency is missing or if there is any other problem, the system is going to notify you. If you observe a message like this:
+
If any dependency is missing or there is another problem, the system will warn you. If you see a message similar to:
  
 
  Warning: prerequisiete Mail::Sendmail 0 not found
 
  Warning: prerequisiete Mail::Sendmail 0 not found
 
  Warning: prerequisiete Net::Traceroute::PurePerl 0 not found
 
  Warning: prerequisiete Net::Traceroute::PurePerl 0 not found
  
If displayed, it means there are some Perl packages that Pandora FMS requires and the system doesn't have them installed yet. Please check the previous paragraphs on how to install the previous required dependencies in Pandora FMS. You can however 'ignore' these errors (because they are warnings, not errors) and force the installation. Of course you'll experience problems in one moment or another, because there is a missing but required component. If you know the non-installed component and it's not going to be used (e.g. 'traceroute' is only used for the Pandora FMS Recon Server) you may go on.
+
It means that there are some Perl packages that Pandora FMS needs and that the system does not have them installed. Check the previous paragraphs to know how to install the necessary dependencies to be able to install Pandora FMS. However, you can temporarily ignore these warnings (that is why they are warnings and not errors) and force the installation. But you will surely have problems at one time or another since you are missing a component needed to function. However, if you know that the component that is not installed will not be used (e. g. <code>traceroute</code> is used exclusively for Pandora FMS Recon Server), you can continue without any problem.
  
After this process is completed, the files are automatically copied into the following directories:
+
After this process, these files are automatically copied:
  
 
  /usr/local/bin/pandora_server
 
  /usr/local/bin/pandora_server
 
  /usr/local/bin/pandora_exec
 
  /usr/local/bin/pandora_exec
  
There are several '.pm' files (Perl libraries) that Pandora FMS requires. These '.pm' libraries are copied into several files, depending on its distribution and its version, e.g. under Ubuntu 9.04, they're copied into the following directories:
+
And several <code>.pm</code> files (Perl libraries) that Pandora FMS needs. Those <code>.pm</code> libraries are copied to different directories, depending on the version of your distribution and distribution. For example in Ubuntu 9.04 they are copied to:
  
 
  /usr/local/share/perl/5.10.0/PandoraFMS/
 
  /usr/local/share/perl/5.10.0/PandoraFMS/
  
Under SUSE and SLES 11, they are copied into:
+
In SUSE/SLES 11 they are copied to:
  
 
  /usr/lib/perl5/site_perl/5.10.0/PandoraFMS/
 
  /usr/lib/perl5/site_perl/5.10.0/PandoraFMS/
  
== Installing the Enterprise Version ==
+
=== Installing the Enterprise Version ===
  
In order to install the Enterprise version of Pandora FMS (besides installing the 'Open' packages of the console and server) we're required to install two additional packages to the console and server. The package called 'console' is going to depend on the distribution you have installed. We're going to use different packages for each distribution:
+
To install the Enterprise version of Pandora FMS, install the packages "Open" of the Console and Server, and then add the packages "Enterprise" of each one. In the case of the '''Console''' use one package or another, depending on the installed distribution.
  
For Red Hat Enterprise Linux / CentOS / Fedora:
+
==== Enterprise Console Installation ====
 
 
rpm -i pandorafms_console_enterprise-X.X.noarch.rpm
 
 
 
For OpenSUSE:
 
 
 
rpm -i pandorafms_console_enterprise-X.X.noarch.rpm
 
 
 
For Debian / Ubuntu:
 
 
 
dpkg -i pandorafms_console_enterprise_xxx.deb
 
  
 
To install the Enterprise Console by using the source code:
 
To install the Enterprise Console by using the source code:
  
Once you've opened the console and arrived at the location of the compressed file named 'pandorafms_console-X.X.tar.gz' or similar, please follow the below mentioned steps:
+
Once you have opened the console and arrived at the location of the compressed file named <code>pandorafms_console_enterprise-X.X.tar.gz</code> or similar, follow the steps mentioned bellow:
  
1. You're acquiring root privileges by entering:
+
1. Acquire root privileges by entering:
  
 
  su -
 
  su -
  
2. Please copy it to '/tmp' and execute:
+
2. Copy it to a directory where you can unzip de file <code>/tmp</code> and then execute:
  
 
  tar xvzf pandorafms_console-X.Xtar.gz  
 
  tar xvzf pandorafms_console-X.Xtar.gz  
  
Then please copy it to the directory in which your Pandora FMS open-source console is installed. It's either '/var/www/pandora_console' for Debian or Ubuntu, or '/srv/www/htdocs/pandora_console/' for SUSE, RH, Fedora, etc. (or any other directory, depending on your distribution).  
+
3. Later, copy it to the directory in which your Pandora FMS open-source console is installed.  
  
Debian:
+
cp -R enterprise /var/www/html/pandora_console
  
cp -R enterprise /var/www/pandora_console
+
4. Just change the permissions in case the files are intended to get used by the web server user, e.g.:
  
OpenSUSE:
 
  
  cp -R enterprise /srv/www/htdocs/pandora_console
+
  chown -R apache /var/www/html/pandora_console/enterprise
  
3. Just change the permissions in case the files are intended to get used by the web server's user, e.g.:
 
  
Debian:
+
<br>
  
chown -R www-data /var/www/pandora_console/enterprise
+
==== Enterprise Server Installation ====
  
OpenSUSE:
+
{{Warning|We are working on a pilot version that will include upgrades in the Enterprise server. From 738 update on, it is advised to use Pandora FMS Enterprise server version E7. Version E6 should only be used in case of compatibility issues.}}
  
chown -R wwwrun /srv/www/htdocs/pandora_console/enterprise
+
First, make sure the Open version of the server is installed. Then proceed to install the enterprise version in order to install the Enterprise '''Server.'''
  
It's recommended to conduct the [[Pandora:Documentation en:Installing#License_Application | License Activation]] at this point.
+
Once you have the zip file with the server, named <code>pandorafms_server_enterprise-X.X.tar.gz</code> or similar, follow the steps mentioned below:  
  
 
+
1. Acquire root privileges. You are the only one responsible for that key:
First make sure the open-source server version is installed. Then proceed to install the enterprise version in order to install the Enterprise '''Server.'''
 
 
 
Once you've opened the console and arrived at the location of the compressed file named 'pandorafms_server-X.X.tar.gz' or similar, please follow the below mentioned steps:
 
 
 
1. You're acquiring root privileges:
 
  
 
  su -  
 
  su -  
  
2. You're copying it to '/tmp' and execute:
+
2. Copy it to the directory where to unzip the files (<code>/tmp</code> in this example) and execute:
  
 
  tar xvzf pandorafms_server_enterprise-X.X.tar.gz  
 
  tar xvzf pandorafms_server_enterprise-X.X.tar.gz  
Line 1,113: Line 1,408:
 
  # ./pandora_server_installer --install
 
  # ./pandora_server_installer --install
  
If the Pandora FMS Server Binary isn't contained in the default directory '/usr/bin', you'll have to indicate the directory as follows:
+
If the Pandora FMS Server Binary is not contained in the default directory <code>/usr/bin</code>, indicate the directory as follows:
  
 
  # PREFIX=/usr/local ./pandora_server_installer --install
 
  # PREFIX=/usr/local ./pandora_server_installer --install
  
After installing, the server is going to restart (/etc/init.d/pandora_server restart). Subsequently, the Enterprise Servers are going to be shown as enabled.
+
After installing, restart the server  
  
<br>
+
/etc/init.d/pandora_server restart
<br>
 
<center>
 
[[image:Pandora_server_view.png | 800px]]
 
</center>
 
<br>
 
<br>
 
  
== Installation of the Pandora FMS Server and Console under Windows ==
+
Then, the Enterprise Servers will be shown as enabled.
  
From Pandora FMS versions 5.1 and above, there is a windows installer which allows us to install all together: '''Nginx''', '''PHP''', '''MySQL''', '''Pandora FMS''' and some dependencies necessary for the server and console operation under Windows.
+
{{Warning|Do not restart the server until the Pandora FMS Enterprise license key installation is completed, otherwise the server will not start and your monitoring service will be interrupted.}}
  
<br><br>
+
[[Image:Servidores Enterprise.png|center|800px]]
{{Warning|Pandora FMS Console & server setup in '''Windows''' is not recommended for production systems, due inferior performance compared with Linux. Windows setup is only intended for small enviroments, secondary servers, testing labs, evaluation purposes or/and hacking in general. We are working for next versions be more realiable, fast and complete. Remember this is our first version with support for Windows server/console setups.}}
 
<br><br>
 
  
It comes as a self-installer into executable format (.exe). For a basic installation, you're just required to accept all the options listed below. Please select the language:
+
=== Installing on a different path ===
  
<br>
+
To install the Pandora FMS Server on a different path, specify it with the <code>--destdir</code> option:
<br>
 
<center>
 
[[image:Pandora_agent_3.0_RC3_install_windows_01_eng.png]]
 
</center>
 
<br>
 
<br>
 
  
Please follow the installer steps:
+
./pandora_server_installer --install --destdir <path>
  
<br>
+
After the installation, configure the Pandora FMS server manually to run at startup and configure the database maintenance script, <code>pandora_db</code>, to run periodically. For example, on Linux (replace <code><destdir></code> with the actual path passed to <code>--destdir</code>):
<br>
 
<center>
 
[[image:Pandora_server_install_windows_01.png]]
 
</center>
 
<br>
 
<br>
 
  
Please accept the license terms:
+
ln -s <destdir>/etc/init.d/pandora_server /etc/init.d/
 +
echo "\"<destdir>/usr/share/pandora_server/util/pandora_db\" \
 +
\"<destdir>/etc/pandora/pandora_server.conf\" >/dev/null 2>&1" > /etc/cron.hourly/pandora_db
  
<br>
+
=== Installing with a non-privileged user ===
<br>
 
<center>
 
[[image:Pandora_server_install_windows_02.png]]
 
</center>
 
<br>
 
<br>
 
  
Please select the components to install:
+
To install Pandora FMS server with a non-privileged user, launch the following command with the user you want to install.
  
<br>
+
./pandora_server_installer --install --no-root --destdir /opt/pandora
<br>
 
<center>
 
[[image:Pandora_server_install_windows_03_eng.png]]
 
</center>
 
<br>
 
<br>
 
  
{{Warning|If you have a previous version of the Console and the Server already installed and you want an update, check '''only''' the 'Update installed version' option.}}
+
This user must have writing permissions on the path that is passed to <code>--destdir</code>.
{{Tip|Nginx is a web server that replaces Apache, which was used in previous versions. This new server uses PHP with FastCGI, improving the Console performance.}}
 
  
This installer is mainly prepared for an installation on a computer which doesn't have an already installed Nginx or MySQL. In case you have any other web server, such as IIS: It can be enabled, you're however required to disable it in order to work through Nginx.
+
= Pandora FMS Agent Installation =
  
If you have a MySQL Server installed and running on the computer before installing the remaining components of Pandora FMS, you're required to change the MySQL root password for the user called 'pandora'. This change is necessary in order for the database to be created which has to be able to assign permissions to the Pandora FMS Database correctly. Once you've installed Pandora FMS on your computer, please feel free to replace the password.
+
== Agent Requirements ==
  
After selecting the components to install, you're required to specify the installation path:
+
The agent can run on any computer with the minimum required operating system, either of the following:
  
<br>
+
<table cellpadding=6 cellspacing=0 style='background-color: #ECECEC;'>
<br>
+
<tr>
<center>
+
<th style='text-align:center; background-color: #7CA12A; color:#FFFFFF'>Component</th>
[[image:Pandora_server_install_windows_04.png]]
+
<th style='text-align:center; background-color: #7CA12A; color:#FFFFFF'>Operating  System</th>
</center>
+
</tr>
<br>
+
<tr>
<br>
+
<td>Pandora Agent 4.0 or above</td>
 +
<td>
 +
* RedHat Enterprise (RHEL) 6.x
 +
* CentOS 6.x
 +
* SLES 11 SP1 or above
 +
* OpenSUSE 11.x or above
 +
* Debian 5.x or above.
 +
* Ubuntu 11 or above.
 +
* HPUX B.11.11 or above, with Perl 5.8.
 +
* AIX 4.3.3 or above, with Perl 5.8.
 +
* BSD Systems (NetBSD, OpenBSD, FreeBSD), with Perl 5.8.
 +
* MacOSX 10.6 or higher.
 +
* Solaris 8 or above, with Perl 5.8.
 +
* Windows NT4 (see special notes for this section).
 +
* Windows XP
 +
* Windows 2000
 +
* Windows 2003
 +
* Windows 2008
 +
* Windows 7
 +
* Windows 8
 +
* Windows 2012
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>Pandora Android Agent 2.0 or above</td>
 +
<td>
 +
* Android 6 or above
 +
</td>
 +
</tr>
 +
<tr>
 +
<td>Pandora Embedded Agent 4.0 or above</td>
 +
<td>
 +
* Embedded devices, requires compiling
 +
</td>
 +
</tr>
 +
</table>
  
The components are going to be installed by following this setup window. The only component which requires a user validation is Nginx. It will ask for the server's name or IP address:
 
  
 
<br>
 
<br>
<br>
+
{{Tip|There is a special agent for Windows NT, which is basically the Unix agent compiled for Windows, although performance is much lower than that of a native Windows agent and native API access features are not present.}}
<center>
 
[[image:Pandora_server_install_windows_05_eng.png]]
 
</center>
 
<br>
 
<br>
 
  
As denoted above, other components are installed besides MySQL and Nginx. In case they have been already installed, you may see a message like this:
+
In UNIX environments, the following must also be installed:
  
<br>
+
* '''Perl 5.8''' or above
<br>
+
* It will be necessary to install the following dependencies:
<center>
+
perl-YAML-Tiny-1.73-2
[[image:Pandora_server_install_windows_06.png]]
+
perl-Sys-Syslog
</center>
+
unzip
<br>
 
<br>
 
  
Please remember that Microsoft Visual C++ is required for the modules to work properly.
+
== Installing the agent in Centos8 ==
  
<br>
+
Dependency installation:
<br>
 
<center>
 
[[image:Pandora_server_install_windows_06_2_eng.png]]
 
</center>
 
<br>
 
<br>
 
  
Nginx requires '''Microsoft Visual C++ 2012''', while if you are running a '''Windows 2008 Professional R2''' server, you will need to install '''Microsot Visual C++ 2008'''. Installing '''Microsoft Visual C++ 2010 SP1 Redistributable Package''' might be required as well for Nmap and the ICMP Enterprise Server to work properly.
+
yum install dnf-plugins-core -y
 +
yum config-manager --set-enabled powertools -y
 +
yum install -y perl-YAML-Tiny perl-Sys-Syslog unzip
  
 +
Agent installation:
  
'''Microsoft Visual C++ 2008'''
+
yum install -y http://firefly.artica.es/pandorafms/latest/RHEL_CentOS/pandorafms_agent_unix-7.0NG.noarch.rpm
  
https://www.microsoft.com/en-us/download/details.aspx?id=29
+
== Installing the agent in Centos7 ==
  
 +
Dependency installation:
  
'''Microsoft Visual C++ 2010 SP1 Redistributable Package'''
+
yum install dnf-plugins-core -y
 +
yum install -y perl-YAML-Tiny perl-Sys-Syslog unzip
  
https://www.microsoft.com/en-us/download/details.aspx?id=8328
+
Agent installation:
  
 +
yum install -y http://firefly.artica.es/pandorafms/latest/RHEL_CentOS/pandorafms_agent_unix-7.0NG.noarch.rpm
  
'''Visual C++ 2012 (Update 4)'''
+
== Installing the agent from tarball ==
  
https://www.microsoft.com/en-US/download/details.aspx?id=30679
+
This agent version is ready for installation on any Unix/Linux/MAC OS system.
  
 +
The agent does not require compilation nor preparation, once the agent is downloaded in. tar. gz format.
  
 +
1. Acquire root privilges
  
Please wait until the files are copied and all the setup-related settings are carried out.
+
su -
  
<br>
+
2. Copy it to <code>/tmp</code> and execute:
<br>
 
<center>
 
[[image:Pandora_server_install_windows_07.png]]
 
</center>
 
<br>
 
<br>
 
  
Until the installation is complete as shown below.
+
tar xvzf pandorafms_X.Y_unix.tar.gz
 +
cd unix
 +
./pandora_agent_installer --install
  
 +
3. Start the agent manually:
  
<br>
+
/etc/init.d/pandora_agent_daemon start
<br>
 
<center>
 
[[image:Pandora_server_install_windows_08_eng.png]]
 
</center>
 
<br>
 
<br>
 
  
Once completed, it's going to open the browser on the login screen automatically. In cases you've installed the Enterprise Version, you're going to be asked for the license code which will be provided from Artica for implementation. Except for the Enterprise Version, the server is installed as a service and starts automatically during the installation process. If the installation of the Enterprise Version has been completed with no valid license code, the server is not going to boot.
+
== Custom installation ==
  
In order to quickly start the process, please click on 'Start' and 'Programs'.
+
The agent can be installed in a directory defined by the user in an "integral" way, this means that all the files of the agent will be put in that directory: logs, configuration files, binaries, '''man''' pages, etc.
  
 +
To use that method, simply run it as the following example:
  
<br>
+
./pandora_agent_installer --install /opt/pandora
<br>
 
<center>
 
[[image:Pandora_server_install_windows_09.png]]
 
</center>
 
<br>
 
<br>
 
  
Once the service is running properly, a ready-to-use console with all the servers is going to appear as shown on the picture below.
+
The only file that Pandora FMS will create outside this user-defined directory is the agent launcher in <code>/etc/init. d/pandora_agent_daemon</code> (or equivalent in other Unix systems), and the link in the directory of the system's boot level, for example <code>/etc/rc. d/rc2. d/S90pandora_agent_daemon</code>.
  
 +
Moreover, the installation can be configured so that instead of running the agent with root user, it can run with another user. For example, for the agent to run with the Pandora FMS user, it would be:
  
<br>
+
./pandora_agent_installer --install /home/pandora pandora
<br>
 
<center>
 
[[image:Pandora_server_install_windows_10.png|800px]]
 
</center>
 
<br>
 
<br>
 
  
 +
When a custom user is specified, the agent must be installed in a custom location where the user has writing permissions (<code>/home/pandora</code> in the previous example).
  
=== Operation WMI modules in some Windows versions ===
 
  
For security reasons in Windows, some versions have limited users who can remotely query WMI. If these modules were not carried out, the solution is to run the service Satellite Server as an Administrator user.
 
 
The process to follow is:
 
 
Open services:
 
 
<center>
 
<br>
 
[[File:Instalacion windows7e.png|400px]]
 
</center>
 
 
<br>
 
<br>
 +
{{Warning|The user '''pandora''' is deactivated by default, you must enable it by entering a valid shell in <code>/etc/passwd</code> if you want to use it to run the agent with that user.}}
  
We click right click on the service and enter in Properties
+
{{Warning|For users with '''MAC OS X 10.11''' or higher (The Captain or newer): Apple has added a new security layer on OS X. Some root privileges have disappeared. When installing the Pandora FMS Agent, it will appear as a restricted process. Only restricted processes that are signed by Apple can modify these files. However, you can disable this security system by booting into recovery mode and deactivating it on a terminal by doing: <code>csrutil disable</code>.}}
  
 +
==Agent installation in NetBSD and FreeBSD ==
  
<center>
+
The file location and startup script structure are different from Linux.
<br>
 
[[File:Instalacion windows8e.png|700px]]
 
</center>
 
<br>
 
  
On the Log On window, select an account with Administrator permissions and apply changes:
+
The particulars of FreeBSD will be discussed later on.
  
<center>
+
To install the agent, download the agent tarball file and follow the instructions below:
<br>
 
[[File:Instalacion windows9e.png|500px]]
 
</center>
 
<br>
 
  
And following these changes, restart the service.
+
1. Acquire root priviledges
  
 +
su -
  
=== Folders to consider in Windows ===
+
2. Copy it to /tmp and inside /tmp execute:
  
There are a set of directories you need to set correctly in Pandora FMS Setup. They are:
+
tar xvzf pandorafms_X.Y_unix.tar.gz
 +
cd unix
 +
./pandora_agent_installer --install
  
- Remote Config directory
+
After installation, add the following line to <code>/etc/rc.conf.</code>
  
- Attachment store
+
pandora_agent_enable="YES"
  
<br>
+
To enable Pandora FMS agent, these settings are needed, otherwise the process cannot be started.
<br>
 
<center>
 
[[image:Path_windows.png|800px]]
 
</center>
 
<br>
 
<br>
 
  
- Server logs directory
+
If you want to start the agent manually, execute this:
  
<br>
+
/usr/local/etc/rc.d/pandora_agent start
<br>
 
<center>
 
[[image:Path_windows2.png|800px]]
 
</center>
 
<br>
 
<br>
 
  
- Custom graphviz directory
+
Agent:
 +
/usr/local/bin/pandora_agent
 +
Boot 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 <code>data_in</code> and <code>log</code> directories are the same as those of Linux.
  
<br>
+
==Agent installation in Windows==
<br>
 
<center>
 
[[image:Path_windows3.png|800px]]
 
</center>
 
<br>
 
<br>
 
  
{{Warning|It has been observed that in '''Windows 2008 Professional R2''', is needed the installation of '''Microsoft Visual C++ 2008''' for the proper operation of Apache.}}
+
The agent is delivered as an installer in executable format (<code>.exe</code>). The basic installation performs all the necessary steps and it is only necessary to accept all the options.
  
'''Microsoft Visual C++ 2008'''<br>
+
To install the Pandora FMS agent in Windows®, you only need to [https://pandorafms.com/community/get-started/ download] and run it. The installer will guide you through the necessary steps in the language you select. The following example shows the installation for Windows 10®, remember that Pandora FMS works on any modern Microsoft® platform (2000 or higher). It also has 32 and 64 bit versions. If you execute Windows as standard user, you will need administrator permissions; enter them when executing the installer.
http://www.microsoft.com/es-es/download/details.aspx?id=29<br><br>
 
  
== Windows Agent Installation ==
 
  
The agent comes as a self-installer in executable format (.exe). The basic installation conducts all the required steps. It's only going to be necessary to accept all of the options. To install the Pandora FMS Agent under Windows, you're just required to download and to execute it. The installer is going to guide you though all the steps in your chosen language. The following example shows the installation for Windows Vista. Pandora FMS has been tested on all Microsoft Windows versions, from Windows 2000 to Windows 8, you have 32 and 64 bit versions of the agent.
+
<br><br>
 +
Select language:
  
Please select the language:
 
 
<br>
 
<br>
 
 
<center>
 
<center>
 
[[image:Pandora_agent_3.0_RC3_install_windows_01.png]]
 
[[image:Pandora_agent_3.0_RC3_install_windows_01.png]]
 
</center>
 
</center>
<br>
 
<br>
 
  
Please follow the installer steps.
+
Follow the steps of the installer:
 +
<center>
 +
[[image:Pandora_agent_3.0_RC3_install_windows_021.png]]
 +
</center>
 +
Acept Terms and Conditions and click '''Next''':
  
<br>
 
<br>
 
 
<center>
 
<center>
[[image:Pandora_agent_3.0_RC3_install_windows_02.png]]
+
[[image:Pandora_agent_3.0_RC3_install_windows_031.png]]
 
</center>
 
</center>
<br>
 
<br>
 
  
Please accept the license terms here and click on 'next':
+
Select the path where the Pandora FMS agent will be installed (by default it is installed in <code>c:/program files/pandora_agent</code>), but you can change it by clicking on '''Browse'''..., and then '''Next''':
  
<br>
 
<br>
 
 
<center>
 
<center>
[[image:Pandora_agent_3.0_RC3_install_windows_03.png]]
+
[[image:Pandora_agent_3.0_RC3_install_windows_041.png]]
 
</center>
 
</center>
<br>
 
<br>
 
 
Please select the path where you want the Pandora FMS Agent to be installed. You can change it by clicking on 'Browse'. After that, just klick on 'Next'.
 
  
<br>
+
Wait for the files to be copied.
<br>
 
 
<center>
 
<center>
[[image:Pandora_agent_3.0_RC3_install_windows_04.png]]
+
[[image:Pandora_agent_3.0_RC3_install_windows_061.png]]
 
</center>
 
</center>
<br>
 
<br>
 
  
Please wait while the files are being copied.
+
Configure the data for the agent as the IP address (or name) of the Pandora FMS server that will receive the agent data.
 +
In order to be able to change other parameters, such as the agent name (by default it takes the hostname value of the machine) or the path of the temporary files, you will have to manually edit the agent configuration.
 +
 
  
<br>
 
<br>
 
 
<center>
 
<center>
[[image:Pandora_agent_3.0_RC3_install_windows_06.png]]
+
[[image:Pandora_agent_3.0_RC3_install_windows_071.png]]
 
</center>
 
</center>
<br>
 
<br>
 
 
Please configure the agent's data such as IP (or name) of the Pandora FMS Server which is going to receive the agent's data and the data entry path (if you aren't sure whether you know the correct value or not, just leave it at the default value that's already in here).
 
 
<br>
 
<br>
 
 
<center>
 
<center>
[[image:Pandora_agent_3.0_RC3_install_windows_07.png]]
+
[[image:Pandora_agent_3.0_RC3_install_windows_072.png]]
 
</center>
 
</center>
<br>
 
<br>
 
  
Please decide whether you want to start the Pandora FMS Agent's service in this moment. Contrary to common belief you're going to have to do this manually, otherwise Pandora FMS won't start automatically if Windows reboots.
+
Start Pandora FMS agent service, otherwise you will have to do it manually, or it will start when Windows restarts again.
  
<br>
 
<br>
 
 
<center>
 
<center>
[[image:Pandora_agent_3.0_RC3_install_windows_08.png]]
+
[[image:Pandora_agent_3.0_RC3_install_windows_081.png]]
 
</center>
 
</center>
<br>
+
The installation is finished. You can change the agent parameters in the file <code>pandora_agent.conf</code> or through the direct link in the PandoraFMS menu.
<br>
 
 
 
When the installation is finished, you may change the agent's parameters in the file named 'pandora_agent.conf' or by the direct link in the Pandora FMS Menu
 
 
 
 
 
=== Windows Agent - Unattended Installation ===
 
 
 
From versions 3 RC3 and above, Pandora FMS includes the option of installing the Windows Agent unattended. You're required to execute the agent installer, handing over the <code>'''/mode Silent'''</code> parameter, indicating the installation to be conducted unattendedly. Besides, you can hand over the <code>'''/prefix <nowiki><Ruta></nowiki>'''</code> parameter to indicate the complete installation path to the installer.
 
 
 
Please execute the following command where '<code>XXXXX</code>' could change depending on the installers version, and <code><nowiki><Ruta></nowiki></code> is the complete path where we want to install it (in inverted commas if it has any spaces).
 
 
 
PandoraFMS_windows_agent_v3.0.XXXXX.setup.exe /mode Silent /prefix <Ruta>
 
 
 
In order to install the current version and to install e.g. in <code>c:\agente_pandora\</code>, you're required to execute the following:
 
 
 
PandoraFMS_windows_agent_v3.0.RC3.setup.exe /mode Silent /prefix c:\agente_pandora
 
 
 
This is going to install Pandora FMS along with the default values in the indicated path and starts the Pandora FMS service on the machine. It's necessary to execute this installing process by a user which bears the privileges to install software or services on the machine.
 
 
 
From the agent's versions '''5.1''' and above, the installer has changed. In order to install the agent in an unattended way, you're required to execute it in the following way:
 
 
 
PandoraFMS_agent_v5.1.exe /S
 
 
 
In case you intend to install the agent in a different path:
 
 
 
PandoraFMS_agent_v5.1.exe /S /D=C:\Agente_Pandora
 
 
 
=== Unattended Deinstallation ===
 
 
 
The uninstaller is an executable called '<code> uninstall.exe</code>' which remains in the Pandora FMS installation directory. It also allows the unattended deinstallation for it. You're required to execute the unistaller by the <code>'''/mode Silent'''</code> option to use it.
 
 
 
Let's assume that Pandora FMS is installed in the default path:
 
 
 
c:\archivos de programa\pandora_agent
 
  
You're required to execute it in the following way:
+
===Unattended Windows Agent Installation ===
  
“c:\archivos de programa\pandora_agent\uninstall.exe” /mode silent
+
Starting with the agent's '''VERSION 5.1''', the installer supports unattended mode. To perform the installation, simply run the following:
  
=== Manual Installation of Windows Agent ===
+
"Pandora FMS Windows Agent v7.0NG.VERSION-BUILD_ARCH.exe" /S
  
The Windows Agent can be installed manually. To learn in which way the manual installation works also serves to understand how the Agent works internally and to be able to reset some parameters of the installation later.
+
In case you want to install the agent in a different path than the default one:
  
Assuming that all the agents necessary files are obtained including their directory structure, they are summarized below.
+
"Pandora FMS Windows Agent v7.0NG.VERSION-BUILD_ARCH.exe" /S /D=C:\Agent_Pandora
  
* '''PandoraAgent.exe:''' The Pandora FMS service executable. We'll later see that it accepts any parameters useful for us.
+
You can also pass certain parameters so that they are written in the configuration file of the agent to be created. Thanks to these options, the deployment of Pandora FMS agents is much more customizable. The options per command line that are supported are the following:
  
* '''pandora_agent.conf:''' The main configuration file.
+
* <code>--ip</code>: It corresponds to the token ''server_ip''.
 +
* <code>--group</code>: It corresponds to the token''group''.
 +
* <code>--alias</code>: It corresponds to the token''agent_alias''.
  
* '''libcurl.dll:''' The library used by Pandora FMS to upload the files by FTP.
+
For example, if you want to create an agent that belongs to the group''Applications'', with the name ''Mifunne'' and that points to the server with the IP ''192.168.0.59'', the command would be:
  
* '''libeay32.dll:''' The library used to encrypt connections (SSH and Tentacle) by Pandora FMS.
+
"Pandora FMS Windows Agent v7.0NG.VERSION-BUILD_ARCH.exe" /S  --ip 192.168.0.59 --group Applications --alias Mifunne
  
* '''zlub1.dll:''' The Library used to compress data by Pandora FMS.
+
===Unattended Uninstallation===
  
* '''libodbc++.dll:''' The library used for ODBC checking by Pandora FMS.
+
The uninstaller that is an executable named <code>uninstall. exe</code> in the Pandora FMS installation directory also enables the unattended uninstaller, to do it, run the uninstaller with the option <code>''' /S''' </code>.
  
* '''pandora_agent.log:''' The agents main log.
+
For example, assuming that Pandora FMS is installed in the default path:
  
* '''pandora_debug.log:''' The agents main log (as debug).
+
c:\program files\pandora_agent
  
* '''/util:''' In the 'util' directory, there are several 'typical' given UNIX tools to Win32 such as 'grep', 'gawk', 'wc', 'head', 'tail', etc.
+
You should execute:
  
There is also the Tentacle client named 'tentacle_client.exe. It's the one used to send the packages to the Pandora FMS Server.
+
“c:\program files\pandora_agent\uninst.exe” /S
  
All these files can be obtained from our code repository (subversion) under 'sourceforge.net'.
+
=== Using PandoraAgent.exe from the command line ===
  
Another easier solution is to compress a ZIP file from the contents of a currently installed agent. Just zip the contents of the directory named 'c:\program files\pandora_agent' and decompress it within the appropriate sub folder on the desired system.
+
If you run <code>pandoraagent.exe --help</code>, it will show you something similar to this:
  
==== Using 'PandoraAgent.exe' from the Command Line ====
+
C:\Program Files\pandora_agent>pandoraagent.exe --help
 
+
  Pandora agent for Windows. Version 7.0NG.752(Build 210223)
If we're executing 'pandoraagent.exe' including the '--help' parameter, it's going to show something like this:
 
 
 
  Pandora agent for Windows. Version 3.0 (Build 090924)
 
 
  Usage: pandoraagent.exe [OPTION]
 
  Usage: pandoraagent.exe [OPTION]
 
   
 
   
Line 1,517: Line 1,709:
 
         --process: Run the Pandora Agent as a user process instead of a service.
 
         --process: Run the Pandora Agent as a user process instead of a service.
  
To install the service (if not already installed), please execute the following command from the directory where the '.exe' is residing, e.g. 'c:\program files\pandora_agent':
+
C:\Program Files\pandora_agent>
  
pandoraagent.exe --install
 
  
This command is going to install the service on the machine, building on the path where the '.exe' is located.
+
To install the service (if it is not installed), just run the following '' inside'' the directory where the executable is located (usually <code>C:\Program&nbsp;Files</code> or equivalent).
If we want to remove it, it's the same process, but with a differt option:
 
  
  pandoraagent.exe --uninstall
+
  pandoraagent.exe --install
  
Depending on the kind of the selected Windows system, it's possible that you may have to reboot the system after removing the service. On other systems, the change is inherited without the need for a reboot.
+
This will prompt the service on the machine, based on the path where the <code>.exe</code> is located.
  
If you want to try a FTP or SSH connection from the command line, you may use the above mentioned options.
+
To check whether it connects through SSH with Pandora FMS server:
  
==== Pandora FMS Windows Agent as a Process ====
+
  C:\Windows\system32>cd %PROGRAMFILES%
 
+
   
For debugging reasons, tests and other unusual circumstances, it's possible to execute the agent the way processes usually do. To get this done, please execute the following command:
+
  C:\Program Files>cd pandora_agent
 
 
  pandoraagent.exe --process
 
 
 
There are some restrictions to the execution in process mode. Pandora FMS is meant to be executed as service and a user '''system'''. If you execute it by means of other users without privileges, there are going to be some functions which aren't going to work properly.
 
 
 
=== Pandora FMS for Windows NT4 ===
 
 
 
This agent is a porting of the UNIX agent, compiled in Perl by the 'ActiveState DevKit' Perl compiler. It's a stand-alone EXE file, equipped with all the tools required to run. It comes with the same features as the UNIX agent, but it runs on an NT4 box. This means it can execute commands and change the output in a way to produce usable data for Pandora FMS.
 
 
 
It was created to be used on any Windows machine (NT4, Win95, Windows 2000-2008 and Windows 7) and could be useful on Windows embedded systems without WMI core (which renders the standard Pandora FMS Windows Agent not to run properly).
 
 
 
==== Installing the Agent ====
 
 
 
Please copy all contents on a directory of your choice, e.g. 'c:\pandora'.
 
 
 
Edit the 'pandora_agent.conf' and set your parameters, including the log file and the temporary directory. It should be something like 'c:\pandora\temp' and 'c:\pandora\log'. Please '''make sure''' the appropriate directories exist before trying to start the Pandora FMS Agent.
 
 
 
==== Running the Agent ====
 
 
 
This agent doesn't run as a service. You're required to install by the startup menu or by hand. The shortlink you're creating has to have a parameter, which is where the main Pandora FMS agent directory is located. In this scenario, it's 'c:\pandora'. The start-up command has to be the following:
 
 
 
c:\pandora\pandora_agent.exe c:\pandora
 
 
 
==== Installation as a Service ====
 
 
 
The 'srvany.exe' tool is intended to perform this task. It's a Microsoft resource kit tool and capable to use any '.exe' file as a service. Please read the documentation on how to use 'srvany' tool. It's contained in this package.
 
 
 
== Embedded Agent ==
 
 
 
Pandora FMS has a very special agent, called the "embedded" agent. It's a pure C development, designed to be entirely cross-plattform compatible. You're only required to have the GNU C compiler to compile. You may link and use it in any available system. We have tested it in a few ARM enviroments. It doesn't require anything special and should be able to run on any system equipped with a GNU C compiler.
 
 
 
In order to use it, you'll also require to compile and link the Tentacle client protocol to send information to the Pandora FMS Server.
 
 
 
To compile both, you're going to require the GNU C extensions and autotools (e.g. 'autoconf', 'automake', 'pkg-config', etc).
 
 
 
You'll require sources for the embedded agent from our SVN or [https://sourceforge.net/projects/pandora/upload/Tools%20and%20dependencies%20%28All%20versions%29/Embedded%20Agent/ file release section on Sourceforge] AND the code for Tentacle Client from our SVN or the download section as a separate file.
 
 
 
=== Basic Installation ===
 
 
 
The simplest way to compile this package is the following:
 
 
 
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 a while. While running, it gives back some messages, telling for which features it's checking for.
 
 
 
2. Type 'make' to compile the package.
 
 
 
3. Optionally, type 'make check' to run any self-tests that comes along with the package.
 
 
 
4. Type 'make install' to install the programs, all data files and the documentation.
 
 
 
5. You may remove the program binaries and the object files from the source code directory by executing 'make clean'. To also remove the files created by the 'configure' command (to compile the package for a different kind of computer), please execute 'make distclean'. There is also a 'make maintainer-clean' target, but it's mainly intended for the package developers. If you use it, you may have to get all sorts of other programs in order to regenerate files which came along with the distribution.
 
 
 
=== Installation Names ===
 
 
 
By default, 'make install' is going to install the package's files in '/usr/local/bin', '/usr/local/etc', etc. You may specify an installation prefix other than '/usr/local' by giving 'configure' the option of '--prefix=PATH'. The command 'make install' is going to install the following 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 is going to use 'PATH' as the prefix for installing programs and libraries. The documentation and other data files are still going to use the regular prefixes.
 
 
 
In addition, if you use an unusual directory layout, you may execute options like '--bindir=PATH' to specify different values for particular kinds of files. Please execute 'configure --help' for a list of the directories you can set up and which types of files go into them.
 
 
 
If the package supports it, you can cause programs to be installed by an extra prefix or suffix on their names by giving 'configure' the option of '--program-prefix=PREFIX' or '--program-suffix=SUFFIX'.
 
 
 
=== Features of the Embedded Agent ===
 
 
 
In this moment, the agents supports the basic features only, which means there are only the 'module_exec' and the 'module_plugin' method to obtain information. All information you're gathering from the system must be done by using an external command execution.
 
 
 
= Initial Configuration after Installation =
 
 
 
The order you should follow after Installation is:
 
 
 
# Create the database through the Pandora FMS web console installation wizard.
 
# Modify the server configuration including the access credentials to the BBDD that have been generated by the previous step.
 
# Start server Arrancar servidor.
 
# Start the local agent (if required).
 
# Go to Pandora FMS for the first time to start using it.
 
 
 
== Console Initial Configuration ==
 
 
 
Assuming we are going to execute all components (Database, Console, Server and Agent) on the same machine:
 
If you haven't done it already, please 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 on your server:
 
 
 
/etc/init.d/apache2 start
 
 
 
You may get to your server IP address through the web to conduct the Pandora FMS post-installation now. This post-installation serves to create the Pandora FMS database and to configure the access credentials (user, password, name of database) in the Pandora Server to the established user DB.
 
 
 
 
 
If your server's IP is e.g. '192.168.5.54', please put the following line into the address bar of your browser:
 
 
 
http://192.168.5.54/pandora_console/install.php
 
 
 
From now on, you're just required to follow the below mentioned steps in order to create the Pandora FMS DB.
 
 
 
<center><br><br>
 
[[Image:Pandora_install_1.png]]
 
</center>
 
<br>
 
<br>
 
 
 
Please klick on 'Next'.
 
 
 
<br>
 
<br>
 
<center>
 
[[Image:Pandora_install_2.png]]
 
</center>
 
<br>
 
<br>
 
 
 
This screen is intended to verify that all software dependencies have been properly installed.
 
 
 
Note: If you're required to install some dependencies, it's going to be necessary to restart the web server in order to use it.
 
 
 
<br>
 
<br>
 
<center>
 
[[Image:Pandora_install_3.png]]
 
</center>
 
<br>
 
<br>
 
 
 
At this point, it configures the access data to your MySQL server. You're required to enter the root password which you've created in the previous step (which was 'pandora 1234' in the example).
 
 
 
<b>Note:</b> Please avoid to use blank spaces in the database name.
 
 
 
<br>
 
<br>
 
<center>
 
[[Image:Pandora_install_4.png]]
 
</center>
 
<br>
 
<br>
 
 
 
You're required to enter the password for database access here.
 
 
 
<br>
 
<br>
 
<center>
 
[[Image:Paso5.png]]
 
</center>
 
<br>
 
<br>
 
 
 
Installation complete.
 
 
 
<br>
 
<br>
 
<center>
 
[[Image:Paso6.png]]
 
</center>
 
<br>
 
<br>
 
 
 
In this point, you're required to delete "install.php" manually. Please go to the Pandora FMS Console install directory and delete the '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 under Linux, please use the 'rm' command in the following way:
 
 
 
rm install.php
 
 
 
=== License Application ===
 
 
 
The Pandora FMS Enterprise version bears a different license key associated to each installation. To use the Enterprise Features and the console's remote updates, you're required to enter the license code in the console configuration section.
 
 
 
After installing the Enterprise version's Pandora FMS Console by any installation method, you're required to access the Pandora Console (http://IP/pandora_console/). Subsequently, the following welcome screen to accept the license is going to appear:
 
 
 
<br>
 
<center>
 
[[Image:license_accept.png]]
 
</center>
 
<br>
 
 
 
After accepting the license, the Pandora FMS Database schema is going to change, adding required new tables for the use of the Enterprise Version. In this moment, a new screen to register the license key, which Artica has sent to you, is going to appear:
 
 
 
<br>
 
<center>
 
[[Image:license_setup.png]]
 
</center>
 
<br>
 
 
 
For versions prior to Pandora FMS 5, you're required to enter the license key directly. For Pandora FMS Versions 5 and above, you're required to perform a specific procedure, which is thoroughly explained in a welcome document which is going to be shipped along with the License to you.
 
 
 
 
 
{{warning|It's very important '''-not-''' to start the 'pandora_server' daemon until the Enterprise Version's Pandora FMS Console has been properly installed, because numerous different errors might occur if you do so before completing the process.}}
 
 
 
== Server Initialization and Basic Configuration ==
 
 
 
Pandora FMS has configured your database and created a MySQL user for gaining access to it. It has created a random password for the 'pandora' user that should be the one which was used to modify the defined password in the Pandora FMS Server.
 
 
 
For this last step, you're required to edit the file named '/etc/pandora/pandora_server.conf' from your Pandora installation and look for the following line:
 
 
 
dbpass pandora
 
 
 
Then replace 'pandora' for the password which was created by the wizard. Once this is done and the file is saved, you're able to start the Pandora FMS server by entering the following command:
 
 
 
/etc/init.d/pandora_server start
 
 
 
The server should return start values like the ones below.
 
 
 
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.
+
C:\Program Files\pandora_agent>PandoraAgent.exe --test-ssh
 
+
Public key file C:\Program Files\pandora_agent\key\id_dsa.pub exists.
The Pandora Server is now running with PID 2085.
+
Private key file: C:\Program Files\pandora_agent\key\id_dsa exists.
 +
Connecting with pfms.example.com.
 +
Authentication successful.
 +
Host fingerprint:
 +
Created a blank XML file in C:\Program
 +
Files\pandora_agent\temp\ssh.test
 +
Remote copying C:\Program Files\pandora_agent\temp\ssh.test on server pfms.example.com at /var/spool/pandora/data_in/ssh.test
 +
Successfuly file copied to remote host
 +
Successfuly disconnected from remote host
 +
The SSH test was successful!
  
 +
If you want to uninstall it, the process is the same but using:
  
{{tip|The Tentacle Server is configured to start along with the system boot. If you intend to work with the Pandora FMS Server without rebooting the machine, it's recommended to restart this service by hand.}}
+
pandoraagent.exe --uninstall
  
== Initial and Basic Configuration of the Agent ==
+
=== Pandora FMS Windows Agent as a process ===
  
You can start your machines local agent (it comes preconfigured to send data to the same machine where it's running, using tentacle), to start collecting data automatically:
+
It possible, for debugging, testing and other unusual circumstances, execute the agent in "Process" mode. This is done by running it from the command line:
  
  /etc/init.d/pandora_agent_daemon start
+
  pandoraagent.exe --process
 
 
You're now able to gain access to your Pandora FMS WEB console by the following URL:
 
 
 
http://x.x.x.x/pandora_console
 
  
x.x.x.x is the IP of the machine on which you've installed the Pandora FMS Console.
+
There are some limitations in the execution of the process mode, since Pandora FMS is meant to run as a service and under the user <code>SYSTEM</code>. If you run it with another user without privileges, there will be features that will not work properly.
  
 
[[Pandora:Documentation en|Go back to Pandora FMS documentation index]]
 
[[Pandora:Documentation en|Go back to Pandora FMS documentation index]]

Latest revision as of 14:33, 19 April 2021

Go back to Pandora FMS documentation index


Contents

1 Console and Pandora FMS Server Installation

1.1 Minimum hardware requirements

The requirements set out in this table are the minimum recommendations for different installations. These recommendations are calculated assuming that 80% of the modules have historical data and the average sampling time is 5 minutes. These recommendations are specified for an environment where they are installed in the same database server, server and console.

Hardware SMALL: up to 500 agents or 5000 modules MEDIUM: up to 2000 agents or 10000 modules BIG: For more than 4000 agents*
CPU 1 core at 2 GHz 2 cores at 2,5 GHz 4 cores at 3 GHz
RAM 4 GB 8 GB 16 GB
Hard drive 7200 rpm 15K rpm or SSD SSD
Disk Space 20GB minimum
40GB recommended
60GB minimum
120GB recommended
120GB minimum
250GB recommended

(*) In addition to the these recommendations, we recommend installing MySQL on a standalone server and installing Percona XTraDB instead of standard MySQL.



Template warning.png

In case you install Pandora FMS in a virtual environment, make sure to assign an independent disk with reserved space and high access speed. It is recommended to use SSD hard drives, due to their high impact on performance improvement.

 


Info.png

A 25GB disk is recommended for a single-node database, server and console installation. If you are going to use functionalities such as log storage or want to save information that is more than one month old, you should create a history database

 




1.2 Minimum software requirements

Software Requirements
Operating System
  • RedHat Enterprise (RHEL) 7.X (Enterprise only)
  • RedHat Enterprise (RHEL) 8.X (Enterprise only)
  • CentOS 7.X (recommended)
  • CentOS 8.X
  • Windows Server (2003 or higher)
  • SLES 11 SP1 or higher
  • OpenSUSE 11.X or higher
  • Debian 5, 6, 7 or higher
  • Ubuntu 11 or higher
  • FreeBSD 9.X and 10.X
  • Solaris 10/OpenSolaris
Pandora FMS does not give official support in these platforms
Permissions
  • Server

Pandora FMS Server service must be executed as root permission. Execution as non-root user is possible, being a special and different procedure. Find out more information in this link.

  • Console

To be able to use the console from any web browser, Apache must have read and execute permissions on the console files.

Additionally, the config.php file must have the 600 permissions (read and write for administrator/root).

It is necessary to have writing permissions in the server directory: /var/spool/pandora/.

  • Agent

-Linux®: The Pandora FMS Server Software Agent must be executed as root permission in order to have all the agent features available, although it is also possible to execute it with other permissions..

-Windows®: Pandora FMS Server Software Agent must be executed as administrator permission.

Console
  • PHP 7.2 -> For Pandora FMS version 729 or higher.
  • PHP 5 -> For Pandora FMS version 728 or older.
Browsers
  • Microsoft Edge®
  • Opera web browser®
  • Google Chrome®
  • Mozilla Firefox®

Mozilla Firefox® and Google Chrome® are recommended to make use of interactive graphs and network maps.

1.3 Database requisites

BBDD Details
MySQL Standard
  • Version 5.7
  • For standard installation, a user with creating privileges in the pandora DB is required. In case of not having this user, a manual installation can be performed.
Percona XTraDB

Percona XTraDB installation is recommended for large Pandora FMS environments where more than 4000 agents must be created.

  • Version 5.7
  • For standard installation, a user with creating privileges in the pandora DB is required. In case of not having this user, it will be possible to carry out manual installation.

1.4 Satellite Server Requirements

Satellite Details
Hardware

Similarly to Pandora FMS installation, the hardware requirements of the system that will host the satellite server will depend on the monitoring volume to be managed. For environments with less than 1000 agents, a minimum of 1 core at 2GHz and 1 GB of RAM is recommended.

Dependencies

The main dependencies are:

  • fping
  • nmap
  • perl
  • wmic
Binaries

The main dependencies are:

  • Linux® 32 Bits
  • Linux® 64 Bits
  • Windows® 32 Bits
  • Windows® 64 Bits
  • Raspberry Pi OS

1.5 Port requirements

Port Protocol Service/Process Descripction Address
80 TCP Pandora FMS Console IP management Browser -> Pandora FMS Console Server
80 TCP Pandora FMS Console (API Communication) Use of API/CLI feature Browser/Server that starts the query -> Pandora FMS Console Server
80 TCP Metaconsole Communication between Metaconsole and Nodes Metaconsole server -> Node Server Node Server -> Metaconsole server
162 UDP Pandora FMS Server Trap reception Trap generator device -> Pandora FMS Server
443 TCP Pandora FMS Console (API Communication) Use of API/CLI feature Browser/Server that starts the query -> Pandora FMS Console Server
443 TCP Metaconsole Communication between Metaconsole and Nodes Metaconsole server -> Node server Node server -> Metaconsole server
3306 TCP Pandora FMS Console and Server DB connection Pandora FMS Console Server -> Pandora FMS Database Server Pandora FMS Server -> Pandora FMS Database Server
3306 TCP Metaconsole Communication between Metaconsole and DB Nodes Metaconsole server -> DB Nodes Server Node Server -> Metaconsole BBDD Server
4444 TCP Pandora FMS Server Connection with Selenium GRID Pandora FMS Server -> Selenium Server
9995 UDP Pandora FMS Server Receiving Netflow probes nfcapd Server -> Pandora FMS Server
9200 TCP Pandora FMS Console and Server Log storage management with Elasticsearch Elasticsearch Server -> Pandora FMS Server
41121 TCP Pandora FMS Agents Tentacle Communication Software Agent Server Agent -> Pandora FMS Server
It is recommended to facilitate communication from Pandora FMS server and console to the whole network. For standard monitoring you should need minimum:
80 TCP Pandora FMS Server Web monitoring for WUX server Pandora FMS Server -> Server to monitor
161 UDP Pandora FMS Console and Server Monitoring via SNMP Polling Pandora FMS Server -> Server to monitor
443 TCP Pandora FMS Server Web monitoring for WUX server Pandora FMS Server -> Server to monitor
ICMP ICMP Console and Pandora FMS Server Web monitoring for WUX server Pandora FMS Server -> Server to monitor

1.6 Package Dependencies

Pandora FMS has a strong dependency on the Linux® Operating System, but it also needs additional packages which, in many cases, are not installed by default. During the installation process, there is a detailed list of package dependencies for CentOS.

1.7 Issues prior to Installation

1.7.1 MySQL

Template warning.png

During the installation process of Pandora FMS in Centos 7 and 8 systems by packages it is already explained how to install and configure the database compatible with the server, so it is not necessary any previous installation before following the guide and you can skip this point

 


You will need to have MySQL Server installed before configuring Pandora FMS, since the next step after installing Pandora FMS packages, is to configure access to the databases. To do that, it must be operational. If you are installing the MySQL Server at the same time as Pandora FMS, remember that you need to set up the root user for MySQL. This can be easily done in two steps:

1. Start MySQL Server daemon:

/etc/init.d/mysql start

2. Configure the root password for MySQL root user:

mysqladmin password <password>

In <password>, type in the password for MySQL root user (which is different from the system's root user). The system will ask for this password throughout the entire Pandora FMS installation process.

1.7.2 Pandora FMS Installation Order

You are required to follow this sequence in order to install Pandora FMS properly:

  1. Install console
  2. Install server

The reason for this is that MySQL database is configured during the initial configuration phase of the console installation. To ensure the correct working of the server, it is recommended to conduct the whole console installation process first.

It is also possible to host Pandora FMS Server and console in different machines. It is possible to indicate both where MySQL database is through the corresponding configuration file, although in Enterprise environments when carrying out a distributed installation you should take into account more factors for installation.

Regarding the agent: You may install it before or after installing the server and console, because the agent works independently and it may be installed on any machine.

1.7.3 Installing the Enterprise Version

The correct order for an Enterprise installation is as follows:

  • Install the open-source console.
  • Install the Enterprise Console.
  • Install the Enterprise Server.
  • When accessing the console, a box will appear requiring you to enter your Enterprise license code.

Validation of the license is only done in the console. Not in the server.

Details on how to correctly enter the license can be found in the following section: License Application v5.X window opens.


1.8 Installation via Cloud provider

1.8.1 Pandora Server environment

The term "Cloud provider" (or simply "Cloud") is used to describe the hosting of virtual machines, either exclusively or shared, in specialized providers with hardware, hypervisors and customer support web systems for configuration and administration.

For any of them you can install Pandora FMS Community edition. CentOS 7.x is recommended as operating system, 4 gigabytes in RAM memory and 20 gigabytes in free disk space, preferably Solid State Drive (SSD).

Access the command line as provided by your Cloud provider and execute:

curl -Ls https://pfms.me/deploy-pandora | sh

1.8.2 Pandora Agent

To install only the agent there is also a one line installation tool, it is compatible wiht Red Hat base OS (Fedora, Centos, etc) and Debian base OS (debian, ubuntu, etc):

The script support a series of environments variables to customize the installation, and just one of it is mandatory $PANDORA_SERVER_IP so to perform a standard installation in one line just execute:

export PANDORA_SERVER_IP=<PandoraServer IP or FQDN> && curl -Ls https://pfms.me/agent-deploy | bash 

Optionally is possible to use another env variables to customize installation:

$PANDORA_REMOTE_CONFIG: Configure the remote config setting - '0' by default (disabled)

$PANDORA_AGENT_NAME: Configure the agent name setting - autogenerated by default

$PANDORA_AGENT_ALIAS: Configure the agent alias setting - hostname by default

$PANDORA_GROUP: Configure the agent group setting - 'Servers' by default

$PANDORA_SECONDARY_GROUPS: Configure the agent secondary groups setting - Empty by default

$PANDORA_DEBUG: Configure the debug setting - '0' by default (disabled)

$TIMEZONE : Configure the system timezone

Example:

  export PANDORA_SERVER_IP='env.pfms.com' && \
  export PANDORA_REMOTE_CONFIG=1 && \
  export PANDORA_AGENT_NAME='Agent_name' && \
  export PANDORA_AGENT_ALIAS='Agent alias' && \
  export PANDORA_GROUP='Servers' && \
  export PANDORA_SECONDARY_GROUPS='VMware,Web' && \
  curl -Ls https://pfms.me/agent-deploy | bash 

Note: this environment variables are used just in installation process, could be destroyed or change after installation without alter Pandora FMS agent behave

1.9 Installation using ISO or "Software appliance"

Download the CD image from the download section of our website and burn the ISO image onto a DVD, or run the system from that file if you are using a virtualized system (XenServer, VMware®, VirtualBox®, etc). There are CD images for both 32- and 64-bit installations.



The following screen will be displayed at the beginning of the boot process. If you do not press any key, the process will automatically load the Live CD, or you can press any key, select the Install Pandora FMS' option and press "enter" to start the installation.
Install 1.png


The graphic installer will lead you step by step throughout the whole installation process. This installer is a standard installation process used by CentOS, and it is available in different languages.
Install 2.png


It is a very easy process but special attention must be paid when:
  • Entering the superuser password (root).
  • When asked about the hard drive partitioning:
Install 3.png

Select and configure all the necessary options to install, Date & Time, Keyboard and Installation Destination.



Remember to activate the network interface, or else it will need to activated manually after installation.
Install 4.png

Activate the network interface and optionally change the hostname

Install 5.png


When clicking the installation destination button, the partition process will start.
Install 6.png


Select the disk where the installation will be performed and click on Done.

Install 7.png



Select the partitioning, unless you have advanced knowledge use the option 'Click here to create them automatically'. Click Done.
Install 8.png


Verify the created partitions and click on Done.

Install 9.png

Accept Changes.



Click on Begin installation.
Install 10.png


Here you can assign the root password and optionally create a user.
Install 11.png

Now just wait until the process is finished and the system restarts automatically.

After removing the ISO image of the machine's startup so that the installer does not appear again, the recently installed CentOS system will be started and you will be able to use Pandora FMS with all the necessary dependencies for its correct operation.

1.10 Installing the ISO image using a USB Stick

To install the Pandora FMS appliance from a USB flash drive, follow these steps:

  • Download the Pandora FMS ISO image from the download section.
  • Download the program rufus to prepare your USB for the installation (https://rufus.akeo.ie/)
  • Insert the flash drive.
  • Start the program rufus.

Usb installation 1.PNG

  • Select the Pandora FMS ISO image.

Usb installation 2.PNG

  • Press START to start the creation of the Pandora FMS installation USB.

Usb installation 3.PNG

Usb installation 4.PNG

  • Your Pandora FMS installation USB device is ready

Usb installation 5.PNG


  • Connect the USB to the machine where you want to install Pandora FMS.
  • When starting the system, configure the BIOS to start first from USB.

The following screen should be displayed:

Usb installation 6.PNG

Select Installing from USB stick and continue the installation as described in the previous chapter.

1.11 Package installation for CentOS 7/8

1.11.1 Repository configuration

1.11.1.1 Repository configuration on CentOS 8

To configure it it will be necessary to execute the following commands:

dnf install -y \
   epel-release \
   tar \
   dnf-utils \
   http://rpms.remirepo.net/enterprise/remi-release-8.rpm
dnf module reset php
dnf module install -y php:remi-7.3
yum config-manager --set-enabled PowerTools

(Note: In CentOS 8.3 it changes from PowerTools to powertools.)

1.11.1.2 Repository configuration in CentOS 7

Configure yum and the necessary repositories. Execute the following commands:

yum install -y \
   tar \
   yum-utils \
   https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm \
   http://rpms.remirepo.net/enterprise/remi-release-7.rpm
yum-config-manager --enable remi-php73


1.11.2 Database installation

1.11.2.1 Database installation on CentOS 8

It will also be necessary to install a database percona using the following commands:


dnf install -y https://repo.percona.com/yum/percona-release-latest.noarch.rpm
dnf module disable -y mysql
rm -rf /etc/my.cnf
dnf install -y Percona-Server-server-57

1.11.2.2 Database installation on CentOS 7

It will also be necessary to install a database percona using the following commands:

yum install -y https://repo.percona.com/yum/percona-release-latest.noarch.rpm
rm -rf /etc/my.cnf
yum install -y Percona-Server-server-57


1.11.3 Dependency installation

1.11.3.1 Dependency installation on CentOS 8

Console dependencies

Once with dnf and percona installed we can start to install all the necessary dependencies for the console:


dnf install -y \
   php \
   postfix \
   php-mcrypt \php-cli \
   php-gd \
   php-curl \
   php-session \
   php-mysqlnd \
   php-ldap \
   php-zip \
   php-zlib \
   php-fileinfo \
   php-gettext \
   php-snmp \
   php-mbstring \
   php-pecl-zip \
   php-xmlrpc \
   libxslt \
   wget \
   php-xml \
   httpd \
   mod_php \
   atk \
   avahi-libs \
   cairo \
   cups-libs \
   fribidi \
   gd \
   gdk-pixbuf2 \
   ghostscript \
   graphite2 \
   graphviz \
   gtk2 \
   harfbuzz \
   hicolor-icon-theme \
   hwdata \
   jasper-libs \
   lcms2 \
   libICE \
   libSM \
   libXaw \
   libXcomposite \
   libXcursor \
   libXdamage \
   libXext \
   libXfixes \
   libXft \
   libXi \
   libXinerama \
   libXmu \
   libXrandr \
   libXrender \
   libXt \
   libXxf86vm \
   libcroco \
   libdrm \
   libfontenc \
   libglvnd \
   libglvnd-egl \
   libglvnd-glx \
   libpciaccess \
   librsvg2 \
   libthai \
   libtool-ltdl \
   libwayland-client \
   libwayland-server \
   libxshmfence \
   mesa-libEGL \
   mesa-libGL \
   mesa-libgbm \
   mesa-libglapi \
   pango \
   pixman \
   xorg-x11-fonts-75dpi \
   xorg-x11-fonts-misc \
   poppler-data \
   php-yaml


Phantomjs is a special component used to generate PDF graphs dynamically. Install it through the command:


dnf install -y http://firefly.artica.es/centos8/wmi-1.3.14-4.el7.art.x86_64.rpm

Server dependencies

Once console dependencies are installed, install those of the server:

dnf install -y  GeoIP \
GeoIP-GeoLite-data \
dwz \
efi-srpm-macros \
ghc-srpm-macros \
go-srpm-macros \
ocaml-srpm-macros \
openblas-srpm-macros \
perl \
perl-Algorithm-Diff \
perl-Archive-Tar \
perl-Archive-Zip \
perl-Attribute-Handlers \
perl-B-Debug \
perl-CPAN \
perl-CPAN-Meta \
perl-CPAN-Meta-Requirements \
perl-CPAN-Meta-YAML \
perl-Compress-Bzip2 \
perl-Config-Perl-V \
perl-DBD-MySQL \
perl-DBI \
perl-DB_File \
perl-Data-Dump \
perl-Data-OptList \
perl-Data-Section \
perl-Devel-PPPort \
perl-Devel-Peek \
perl-Devel-SelfStubber \
perl-Devel-Size \
perl-Digest-HMAC \
perl-Digest-SHA \
perl-Encode-Locale \
perl-Encode-devel \
perl-Env \
perl-ExtUtils-CBuilder \
perl-ExtUtils-Command \
perl-ExtUtils-Embed \
perl-ExtUtils-Install \
perl-ExtUtils-MM-Utils \
perl-ExtUtils-MakeMaker \
perl-ExtUtils-Manifest \
perl-ExtUtils-Miniperl \
perl-ExtUtils-ParseXS \
perl-File-Fetch \
perl-File-HomeDir \
perl-File-Listing \
perl-File-Which \
perl-Filter \
perl-Filter-Simple \
perl-Geo-IP \
perl-HTML-Parser \
perl-HTML-Tagset \
perl-HTML-Tree \
perl-HTTP-Cookies \
perl-HTTP-Date \
perl-HTTP-Message \
perl-HTTP-Negotiate \
perl-IO-HTML \
perl-IO-Socket-INET6 \
perl-IO-Zlib \
perl-IO-stringy \
perl-IPC-Cmd \
perl-IPC-SysV \
perl-IPC-System-Simple \
perl-JSON \
perl-JSON-PP \
perl-LWP-MediaTypes \
perl-Locale-Codes \
perl-Locale-Maketext \
perl-Locale-Maketext-Simple \
perl-MRO-Compat \
perl-Math-BigInt \
perl-Math-BigInt-FastCalc \
perl-Math-BigRat \
perl-Memoize \
perl-Module-Build \
perl-Module-CoreList \
perl-Module-CoreList-tools \
perl-Module-Load \
perl-Module-Load-Conditional \
perl-Module-Loaded \
perl-Module-Metadata \
perl-NTLM \
perl-Net-HTTP \
perl-Net-Ping \
perl-NetAddr-IP \
perl-Package-Generator \
perl-Params-Check \
perl-Params-Util \
perl-Perl-OSType \
perl-PerlIO-via-QuotedPrint \
perl-Pod-Checker \
perl-Pod-Html \
perl-Pod-Parser \
perl-SelfLoader \
perl-Socket6 \
perl-Software-License \
perl-Sub-Exporter \
perl-Sub-Install \
perl-Sys-Syslog \
perl-Test \
perl-Test-Harness \
perl-Test-Simple \
perl-Text-Balanced \
perl-Text-Diff \
perl-Text-Glob \
perl-Text-Template \
perl-Thread-Queue \
perl-Time-Piece \
perl-TimeDate \
perl-Try-Tiny \
perl-Unicode-Collate \
perl-WWW-RobotRules \
perl-XML-NamespaceSupport \
perl-XML-Parser \
perl-XML-SAX \
perl-XML-SAX-Base \
perl-XML-Simple \
perl-XML-Twig \
perl-autodie \
perl-bignum \
perl-devel \
perl-encoding \
perl-experimental \
perl-inc-latest \
perl-libnetcfg \
perl-libwww-perl \
perl-local-lib \
perl-open \
perl-perlfaq \
perl-srpm-macros \
perl-utils \
perl-version \
python-srpm-macros \
python3-pyparsing \
python3-rpm-macros \
qt5-srpm-macros \
redhat-rpm-config \
rust-srpm-macros \
systemtap-sdt-devel \
perl-TermReadKey \
perl \
perl-DBD-MySQL \
perl-DBI

After this, the following additional dependencies from different components must be installed from Pandora FMS public repository:

dnf install -y http://firefly.artica.es/centos8/wmi-1.3.14-4.el7.art.x86_64.rpm
dnf install -y http://firefly.artica.es/centos8/perl-Net-Telnet-3.04-1.el8.noarch.rpm
dnf install -y http://firefly.artica.es/centos7/xprobe2-0.3-12.2.x86_64.rpm

Info.png

Although you see in the xprobe installation link that the package is within CentOS 7 repository, it works properly in both versions.

 


if necessary, add all Discovery dependencies for each section.

At this point you can continue with the configuration of the operating system and database by following this link


1.11.3.2 Dependency installation on CentOS 7

Console dependencies

Once with repositories and percona installed we can start to install all the necessary dependencies for the console:


yum install -y \
   php \
   postfix \
   php-mcrypt \
   php-cli \
   php-gd \
   php-curl \
   php-session \
   php-mysqlnd \
   php-ldap \
   php-zip \
   php-zlib \
   php-fileinfo \
   php-gettext \
   php-snmp \
   php-mbstring \
   php-pecl-zip \
   php-xmlrpc \
   libxslt \
   wget \
   php-xml \
   httpd \
   mod_php \
   atk \
   avahi-libs \
   cairo \
   cups-libs \
   fribidi \
   gd \
   gdk-pixbuf2 \
   ghostscript \
   graphite2 \
   graphviz \
   gtk2 \
   harfbuzz \
   hicolor-icon-theme \
   hwdata \
   jasper-libs \
   lcms2 \
   libICE \
   libSM \
   libXaw \
   libXcomposite \
   libXcursor \
   libXdamage \
   libXext \
   libXfixes \
   libXft \
   libXi \
   libXinerama \
   libXmu \
   libXrandr \
   libXrender \
   libXt \
   libXxf86vm \
   libcroco \
   libdrm \
   libfontenc \
   libglvnd \
   libglvnd-egl \
   libglvnd-glx \
   libpciaccess \
   librsvg2 \
   libthai \
   libtool-ltdl \
   libwayland-client \
   libwayland-server \
   libxshmfence \
   mesa-libEGL \
   mesa-libGL \
   mesa-libgbm \
   mesa-libglapi \
   pango \
   pixman \
   xorg-x11-fonts-75dpi \
   xorg-x11-fonts-misc \
   poppler-data \
   php-yaml

Phantomjs is a special component used to generate PDF graphs dynamically. Install if from Pandora FMS servers through the command:

yum install -y https://firefly.pandorafms.com/centos8/phantomjs-2.1.1-1.el7.x86_64.rpm

Server dependencies

To install all dependencies necessary for the server execute the following commands:

yum install -y \
   vim \
   fping \
   perl-IO-Compress \
   nmap \
   sudo \
   perl-Time-HiRes \
   nfdump \
   net-snmp-utils \
   epel-release \
   GeoIP \
   groff-base \
   initscripts \
   iproute \
   iptables \
   libmnl \
   libnetfilter_conntrack \
   libnfnetlink \
   libpcap \
   lm_sensors-libs \
   mailcap \
   make \
   mariadb-libs \
   net-snmp \
   net-snmp-agent-libs \
   net-snmp-libs \
   net-tools \
   nmap \
   nmap-ncat \
   openssl \
   perl \
   perl-Business-ISBN \
   perl-Business-ISBN-Data \
   perl-Carp \
   perl-Compress-Raw-Bzip2 \
   perl-Compress-Raw-Zlib \
   perl-DBD-MySQL \
   perl-DBI \
   perl-Data-Dumper \
   perl-Digest \
   perl-Digest-MD5 \
   perl-Encode \
   perl-Encode-Locale \
   perl-Exporter \
   perl-File-Listing \
   perl-File-Path \
   perl-File-Temp \
   perl-Filter \
   perl-Font-AFM \
   perl-Geo-IP \
   perl-Getopt-Long \
   perl-HTML-Format \
   perl-HTML-Parser \
   perl-HTML-Tagset \
   perl-HTML-Tree \
   perl-HTTP-Cookies \
   perl-HTTP-Daemon \
   perl-HTTP-Date \
   perl-HTTP-Message \
   perl-HTTP-Negotiate \
   perl-HTTP-Tiny \
   perl-IO-Compress \
   perl-IO-HTML \
   perl-IO-Socket-INET6 \
   perl-IO-Socket-IP \
   perl-IO-Socket-SSL \
   perl-IO-stringy \
   perl-JSON \
   perl-LWP-MediaTypes \
   perl-Mozilla-CA \
   perl-Net-Daemon \
   perl-Net-HTTP \
   perl-Net-LibIDN \
   perl-Net-SSLeay \
   perl-Net-Telnet \
   perl-NetAddr-IP \
   perl-PathTools \
   perl-PlRPC \
   perl-Pod-Escapes \
   perl-Pod-Perldoc \
   perl-Pod-Simple \
   perl-Pod-Usage \
   perl-Scalar-List-Utils \
   perl-Socket \
   perl-Socket6 \
   perl-Storable \
   perl-Sys-Syslog \
   perl-Text-ParseWords \
   perl-Time-HiRes \
   perl-Time-Local \
   perl-TimeDate \
   perl-URI \
   perl-WWW-RobotRules \
   perl-XML-NamespaceSupport \
   perl-XML-Parser \
   perl-XML-SAX \
   perl-XML-SAX-Base \
   perl-XML-Simple \
   perl-XML-Twig \
   perl-constant \
   perl-libs \
   perl-libwww-perl \
   perl-macros \
   perl-parent \
   perl-podlators \
   perl-threads \
   perl-threads-shared \
   sudo \
   systemd-sysv \
   sysvinit-tools \
   tcp_wrappers-libs

And finally install the following additional dependencies too from our public repository:

yum install -y https://firefly.pandorafms.com/centos7/wmi-1.3.14-4.el7.art.x86_64.rpm
yum install -y https://firefly.pandorafms.com/centos7/xprobe2-0.3-12.2.x86_64.rpm

1.11.4 OS settings and database creation

To configure Pandora FMS by packages in CentOS, it will be necessary to define first the following variables for any of the two systems and that we will use in the following steps:

PANDORA_CONSOLE=/var/www/html/pandora_console
CONSOLE_PATH=/var/www/html/pandora_console
PANDORA_SERVER_CONF=/etc/pandora/pandora_server.conf
PANDORA_SERVER_BIN=/usr/bin/pandora_server
PANDORA_HA_BIN=/usr/bin/pandora_ha
PANDORA_TABLES_MIN=160
DBHOST=127.0.0.1
DBNAME=pandora
DBUSER=pandora
DBPASS=pandora
DBPORT=3306

Template warning.png

After this point the installation for CentOS 7 and CentOS 8 is common for both systems, if there is any step that is not common the operating system for which it is valid will be indicated in bold

 



After previous steps, disable SELINUX and the firewall.

setenforce 0
sed -i -e "s/^SELINUX=.*/SELINUX=disabled/g" /etc/selinux/config
systemctl disable firewalld --now

Info.png

If you decide to use Security-Enhanced Linux (SELinux) with Pandora FMS, follow these instructions.

 


Then you may start configuring the database:

systemctl start mysqld
mysql -uroot -p$(grep "temporary password" /var/log/mysqld.log | rev | cut -d' ' -f1 | rev)
SET PASSWORD FOR 'root'@'localhost' = PASSWORD('Pandor4!');
UNINSTALL PLUGIN validate_password;
SET PASSWORD FOR 'root'@'localhost' = PASSWORD('pandora');
quit
echo "create database $DBNAME" | mysql -uroot -ppandora -P$DBPORT -h$DBHOST
echo "GRANT ALL PRIVILEGES ON $DBNAME.* TO \"$DBUSER\"@'%' identified by \"$DBPASS\"" | mysql -uroot -ppandora -P$DBPORT -h$DBHOST

Also generate the file my.cnf.

POOL_SIZE=$(grep -i total /proc/meminfo | head -1 | awk '{print $(NF-1)*0.4/1024}' | sed s/\\..*$/M/g)
cat > /etc/my.cnf << EO_CONFIG_F
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
character-set-server=utf8
skip-character-set-client-handshake
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
# Mysql optimizations for Pandora FMS
# Please check the documentation in http://pandorafms.com for better results
max_allowed_packet = 64M
innodb_buffer_pool_size = $POOL_SIZE
innodb_lock_wait_timeout = 90
innodb_file_per_table
innodb_flush_log_at_trx_commit = 0
innodb_flush_method = O_DIRECT
innodb_log_file_size = 64M
innodb_log_buffer_size = 16M
innodb_io_capacity = 100
thread_cache_size = 8
thread_stack    = 256K
max_connections = 100
key_buffer_size=4M
read_buffer_size=128K
read_rnd_buffer_size=128K
sort_buffer_size=128K
join_buffer_size=4M
query_cache_type = 1
query_cache_size = 64M
query_cache_min_res_unit = 2k
query_cache_limit = 256K
sql_mode=""
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
EO_CONFIG_F


Once the changes have been saved, it will be necessary to restart the mysqld service.

systemctl restart mysqld 

Enable the services mysql, apache and php.

systemctl enable mysqld --now
systemctl enable httpd --now

If you use CentOS 8, execute:

systemctl enable php-fpm --now

1.11.5 Pandora FMS console and server installation

With all the environment ready, it's time to install Pandora FMS. The first thing will be to create a directory to store all the data.

mkdir $HOME/pandora && cd $HOME/pandora

Template warning.png

It will be necessary to download the packages of the console, enterprise console and enterprise server from Sourceforge or the links provided by the support team.

 


In the OpenSource version:

wget https://firefly.pandorafms.com/pandorafms/latest/RHEL_CentOS/pandorafms_agent_unix-7.0NG.noarch.rpm 
wget https://firefly.pandorafms.com/pandorafms/latest/RHEL_CentOS/pandorafms_console-7.0NG.noarch.rpm 
wget https://firefly.pandorafms.com/pandorafms/latest/RHEL_CentOS/pandorafms_server-7.0NG.noarch.rpm 

With the packages already prepared, start the installation. In the case of the Enterprise console, you must have two more, the Enterprise console package and the Enterprise server package (which is a tarball file installed separate from RPM packages).

Package installation (after download):

yum install -y $HOME/pandora/pandorafms*.rpm

For Enterprise tarball, execute:

tar xvfz $HOME/pandora/pandorafms_server* && cd pandora_server && ./pandora_server_installer --install --ha; cd -

Once the process is finished, populate the database:

mysql -u$DBUSER -p$DBPASS -P$DBPORT -h$DBHOST $DBNAME < $PANDORA_CONSOLE/pandoradb.sql
mysql -u$DBUSER -p$DBPASS -P$DBPORT -h$DBHOST $DBNAME < $PANDORA_CONSOLE/pandoradb_data.sql

Then configure the console.

cat > $CONSOLE_PATH/include/config.php << EO_CONFIG_F
<?php
\$config["dbtype"] = "mysql";
\$config["dbname"]="$DBNAME";
\$config["dbuser"]="$DBUSER";
\$config["dbpass"]="$DBPASS";
\$config["dbhost"]="$DBHOST";
\$config["homedir"]="/var/www/html/pandora_console";
\$config["homeurl"]="/pandora_console";	
error_reporting(0); 
\$ownDir = dirname(__FILE__) . '/';
include (\$ownDir . "config_process.php");
EO_CONFIG_F
cat > /etc/httpd/conf.d/pandora.conf << EO_CONFIG_F
<Directory "/var/www/html">
   Options Indexes FollowSymLinks
   AllowOverride All
   Require all granted
</Directory>
EO_CONFIG_F
sed -i -e "s/php_flag engine off//g" $PANDORA_CONSOLE/images/.htaccess
sed -i -e "s/php_flag engine off//g" $PANDORA_CONSOLE/attachment/.htaccess 
chmod 600 $CONSOLE_PATH/include/config.php	
chown apache. $CONSOLE_PATH/include/config.php
mv $CONSOLE_PATH/install.php $CONSOLE_PATH/install.done


Then prepare the file php.ini.

sed -i -e "s/^max_input_time.*/max_input_time = -1/g" /etc/php.ini
sed -i -e "s/^max_execution_time.*/max_execution_time = 0/g" /etc/php.ini
sed -i -e "s/^upload_max_filesize.*/upload_max_filesize = 800M/g" /etc/php.ini
sed -i -e "s/^memory_limit.*/memory_limit = 500M/g" /etc/php.ini
cat > /var/www/html/index.html << EOF_INDEX
<meta HTTP-EQUIV="REFRESH" content="0; url=/pandora_console/">
EOF_INDEX

If you use CentOS 8, execute in addition:

systemctl restart php-fpm 
systemctl restart httpd

The server configuration file will be prepared:

sed -i -e "s/^dbhost.*/dbhost $DBHOST/g" $PANDORA_SERVER_CONF
sed -i -e "s/^dbname.*/dbname $DBNAME/g" $PANDORA_SERVER_CONF
sed -i -e "s/^dbuser.*/dbuser $DBUSER/g" $PANDORA_SERVER_CONF
sed -i -e "s|^dbpass.*|dbpass $DBPASS|g" $PANDORA_SERVER_CONF
sed -i -e "s/^dbport.*/dbport $DBPORT/g" $PANDORA_SERVER_CONF

In the Enterprise version, enable the (HA) service.

systemctl enable pandora_ha --now
service tentacle_serverd start


In the Community version, pandora_ha service does not exist, so execute the following commands to enable the server:

systemctl enable pandora_server --now
systemctl start pandora_server
service tentacle_serverd start


Enable the cron of the console:

echo "* * * * * root wget -q -O - --no-check-certificate http://127.0.0.1/pandora_console/enterprise/cron.php >> /var/www/html/pandora_console/log/cron.log" >> /etc/crontab

Then you may go to the CentOS server IP and enter Pandora FMS console and check the service is running properly:

Pandora login.png

With these steps we will have a basic installation of Pandora FMS. If necessary, all Discovery dependencies should be added for each section.

It is recommended to install the agent to automonitor the server.




1.11.6 License application

Pandora FMS Enterprise version is associated with an individual key for each installation. In order to use the Enterprise features and perform automatic updates of the console, it is necessary to enter the license number provided by Artica. From Pandora FMS version 748 on, the server is installed with a trial license valid for a maximum of 100 agents and one month of use.

If you want to expand this license, please contact your trusted commercial or fill in the following contact form

The Community version does not require any license for its use.

1.12 Installation by packages on RHEL 7/8

The installation of Pandora FMS on RHEL 7 and RHEL 8 systems is an Enterprise service. You can consult how to install on these systems by contacting your trusted commercial or by filling out the following contact form

1.13 Installation under Docker

We have an entry in the docker hub website explaining how to mount a Pandora FMS stack based on CentOS 8 step by step in the link: https://hub.docker.com/r/pandorafms/pandorafms-open-stack-el8

It is also possible to install through a yaml file, as a quick installation method. The following explains how to perform this deployment via docker-compose.

First, you need to have installed in the system docker and docker compose, installation documentation: https://docs.docker.com/get-docker/

Once installed, we will use the yaml file from the official PandoraFMS repository:

mkdir $HOME/pandorafms; cd $HOME/pandorafms
wget https://raw.githubusercontent.com/pandorafms/pandorafms/develop/extras/docker/centos8/docker-compose.yml
docker-compose -f $HOME/pandorafms/docker-compose.yml up

We wait a few seconds for the download and configuration of the environment. You can access to the PFMS console from the URL:

http://127.0.0.1:8080/pandora_console 

Use “admin” as user and “pandora” as password.

1.14 Uninstalling Pandora FMS

Just execute the command

yum remove pandorafms_console pandorafms_server

If MySQL is installed but it is no longer needed, it can also be deleted with the same command:

yum remove Percona-Server*

1.15 Custom Installation

1.15.1 Manual Installation from Sources under Linux / UNIX / MAC OS

It will be necessary to install all dependencies installed depending of the OS, and then download the files in tarball format (.tar. gz,.tgz or .tar. bz2) and unzip them. To do it, locate the latest version of Pandora FMS and download the files from here: https://sourceforge.net/projects/pandora/files/.


1.15.1.1 Console Installation

Once you have opened the console zip file, follow these steps:

1. Acquire root privileges by entering:

su -

2. Copy to '/tmp' and execute:

tar xvzf pandorafms_console-X.Y.tar.gz 
cd pandora_console
./pandora_console_install --install

1.15.1.2 Server Installation

Once you have opened the server zip file named pandorafms_server-3.0.0.tar.gz or similar, follow the steps described below:

1. Acquire root privileges. You are the only one responsible for said key:

su - 

2. Copy it to a directory where you can unzip the file (in this example /tmp y used again) and execute:

tar xvzf pandorafms_server-X.Y.tar.gz 
cd pandora_server
./pandora_server_installer --install

If you experience any dependency-related problems, fix them before attempting any installation. It might be possible to force the installation and ignore the problems with the dependencies, but Pandora FMS will not work properly in that case.

1.15.1.3 Server Manual Installation (from source code)

Alternatively to the general installation script, you can "compile" the Pandora FMS code through the Perl interpreter of your system. This process simply installs the minimum libraries and executables, but does not alter the boot script system, maintenance scripts, configuration or anything else that strictly concerns the application and its libraries. This process is recommended when the server code must be updated, but without overwriting its configuration.

To do it properly, unzip your server code to /tmp, as described in the previous step.

1. Acquire root privileges. You are the only one responsible for that key:

su - 

2. Copy it to the directory where you are unzipping files (/tmp in this example) and once there, execute:

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

If any dependency is missing or there is another problem, the system will warn you. If you see a message similar to:

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

It means that there are some Perl packages that Pandora FMS needs and that the system does not have them installed. Check the previous paragraphs to know how to install the necessary dependencies to be able to install Pandora FMS. However, you can temporarily ignore these warnings (that is why they are warnings and not errors) and force the installation. But you will surely have problems at one time or another since you are missing a component needed to function. However, if you know that the component that is not installed will not be used (e. g. traceroute is used exclusively for Pandora FMS Recon Server), you can continue without any problem.

After this process, these files are automatically copied:

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

And several .pm files (Perl libraries) that Pandora FMS needs. Those .pm libraries are copied to different directories, depending on the version of your distribution and 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.15.2 Installing the Enterprise Version

To install the Enterprise version of Pandora FMS, install the packages "Open" of the Console and Server, and then add the packages "Enterprise" of each one. In the case of the Console use one package or another, depending on the installed distribution.

1.15.2.1 Enterprise Console Installation

To install the Enterprise Console by using the source code:

Once you have opened the console and arrived at the location of the compressed file named pandorafms_console_enterprise-X.X.tar.gz or similar, follow the steps mentioned bellow:

1. Acquire root privileges by entering:

su -

2. Copy it to a directory where you can unzip de file /tmp and then execute:

tar xvzf pandorafms_console-X.Xtar.gz 

3. Later, copy it to the directory in which your Pandora FMS open-source console is installed.

cp -R enterprise /var/www/html/pandora_console

4. Just change the permissions in case the files are intended to get used by the web server user, e.g.:


chown -R apache /var/www/html/pandora_console/enterprise



1.15.2.2 Enterprise Server Installation

Template warning.png

We are working on a pilot version that will include upgrades in the Enterprise server. From 738 update on, it is advised to use Pandora FMS Enterprise server version E7. Version E6 should only be used in case of compatibility issues.

 


First, make sure the Open version of the server is installed. Then proceed to install the enterprise version in order to install the Enterprise Server.

Once you have the zip file with the server, named pandorafms_server_enterprise-X.X.tar.gz or similar, follow the steps mentioned below:

1. Acquire root privileges. You are the only one responsible for that key:

su - 

2. Copy it to the directory where to unzip the files (/tmp in this example) and execute:

tar xvzf pandorafms_server_enterprise-X.X.tar.gz 
cd pandora_server/
# ./pandora_server_installer --install

If the Pandora FMS Server Binary is not contained in the default directory /usr/bin, indicate the directory as follows:

# PREFIX=/usr/local ./pandora_server_installer --install

After installing, restart the server

/etc/init.d/pandora_server restart

Then, the Enterprise Servers will be shown as enabled.

Template warning.png

Do not restart the server until the Pandora FMS Enterprise license key installation is completed, otherwise the server will not start and your monitoring service will be interrupted.

 


Servidores Enterprise.png

1.15.3 Installing on a different path

To install the Pandora FMS Server on a different path, specify it with the --destdir option:

./pandora_server_installer --install --destdir <path>

After the installation, configure the Pandora FMS server manually to run at startup and configure the database maintenance script, pandora_db, to run periodically. For example, on Linux (replace <destdir> with the actual path passed to --destdir):

ln -s <destdir>/etc/init.d/pandora_server /etc/init.d/
echo "\"<destdir>/usr/share/pandora_server/util/pandora_db\" \
\"<destdir>/etc/pandora/pandora_server.conf\" >/dev/null 2>&1" > /etc/cron.hourly/pandora_db

1.15.4 Installing with a non-privileged user

To install Pandora FMS server with a non-privileged user, launch the following command with the user you want to install.

./pandora_server_installer --install --no-root --destdir /opt/pandora

This user must have writing permissions on the path that is passed to --destdir.

2 Pandora FMS Agent Installation

2.1 Agent Requirements

The agent can run on any computer with the minimum required operating system, either of the following:

Component Operating System
Pandora Agent 4.0 or above
  • RedHat Enterprise (RHEL) 6.x
  • CentOS 6.x
  • SLES 11 SP1 or above
  • OpenSUSE 11.x or above
  • Debian 5.x or above.
  • Ubuntu 11 or above.
  • HPUX B.11.11 or above, with Perl 5.8.
  • AIX 4.3.3 or above, with Perl 5.8.
  • BSD Systems (NetBSD, OpenBSD, FreeBSD), with Perl 5.8.
  • MacOSX 10.6 or higher.
  • Solaris 8 or above, with Perl 5.8.
  • Windows NT4 (see special notes for this section).
  • Windows XP
  • Windows 2000
  • Windows 2003
  • Windows 2008
  • Windows 7
  • Windows 8
  • Windows 2012
Pandora Android Agent 2.0 or above
  • Android 6 or above
Pandora Embedded Agent 4.0 or above
  • Embedded devices, requires compiling



Info.png

There is a special agent for Windows NT, which is basically the Unix agent compiled for Windows, although performance is much lower than that of a native Windows agent and native API access features are not present.

 


In UNIX environments, the following must also be installed:

  • Perl 5.8 or above
  • It will be necessary to install the following dependencies:
perl-YAML-Tiny-1.73-2 
perl-Sys-Syslog 
unzip

2.2 Installing the agent in Centos8

Dependency installation:

yum install dnf-plugins-core -y
yum config-manager --set-enabled powertools -y
yum install -y perl-YAML-Tiny perl-Sys-Syslog unzip

Agent installation:

yum install -y http://firefly.artica.es/pandorafms/latest/RHEL_CentOS/pandorafms_agent_unix-7.0NG.noarch.rpm

2.3 Installing the agent in Centos7

Dependency installation:

yum install dnf-plugins-core -y
yum install -y perl-YAML-Tiny perl-Sys-Syslog unzip

Agent installation:

yum install -y http://firefly.artica.es/pandorafms/latest/RHEL_CentOS/pandorafms_agent_unix-7.0NG.noarch.rpm

2.4 Installing the agent from tarball

This agent version is ready for installation on any Unix/Linux/MAC OS system.

The agent does not require compilation nor preparation, once the agent is downloaded in. tar. gz format.

1. Acquire root privilges

su -

2. Copy it to /tmp and execute:

tar xvzf pandorafms_X.Y_unix.tar.gz 
cd unix
./pandora_agent_installer --install

3. Start the agent manually:

/etc/init.d/pandora_agent_daemon start

2.5 Custom installation

The agent can be installed in a directory defined by the user in an "integral" way, this means that all the files of the agent will be put in that directory: logs, configuration files, binaries, man pages, etc.

To use that method, simply run it as the following example:

./pandora_agent_installer --install /opt/pandora

The only file that Pandora FMS will create outside this user-defined directory is the agent launcher in /etc/init. d/pandora_agent_daemon (or equivalent in other Unix systems), and the link in the directory of the system's boot level, for example /etc/rc. d/rc2. d/S90pandora_agent_daemon.

Moreover, the installation can be configured so that instead of running the agent with root user, it can run with another user. For example, for the agent to run with the Pandora FMS user, it would be:

./pandora_agent_installer --install /home/pandora pandora

When a custom user is specified, the agent must be installed in a custom location where the user has writing permissions (/home/pandora in the previous example).



Template warning.png

The user pandora is deactivated by default, you must enable it by entering a valid shell in /etc/passwd if you want to use it to run the agent with that user.

 


Template warning.png

For users with MAC OS X 10.11 or higher (The Captain or newer): Apple has added a new security layer on OS X. Some root privileges have disappeared. When installing the Pandora FMS Agent, it will appear as a restricted process. Only restricted processes that are signed by Apple can modify these files. However, you can disable this security system by booting into recovery mode and deactivating it on a terminal by doing: csrutil disable.

 


2.6 Agent installation in NetBSD and FreeBSD

The file location and startup script structure are different from Linux.

The particulars of FreeBSD will be discussed later on.

To install the agent, download the agent tarball file and follow the instructions below:

1. Acquire root priviledges

su -

2. Copy it to /tmp and inside /tmp execute:

tar xvzf pandorafms_X.Y_unix.tar.gz 
cd unix
./pandora_agent_installer --install

After installation, add the following line to /etc/rc.conf.

pandora_agent_enable="YES"

To enable Pandora FMS agent, these settings are needed, otherwise the process cannot be started.

If you want to start the agent manually, execute this:

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

Agent:

/usr/local/bin/pandora_agent

Boot 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_in and log directories are the same as those of Linux.

2.7 Agent installation in Windows

The agent is delivered as an installer in executable format (.exe). The basic installation performs all the necessary steps and it is only necessary to accept all the options.

To install the Pandora FMS agent in Windows®, you only need to download and run it. The installer will guide you through the necessary steps in the language you select. The following example shows the installation for Windows 10®, remember that Pandora FMS works on any modern Microsoft® platform (2000 or higher). It also has 32 and 64 bit versions. If you execute Windows as standard user, you will need administrator permissions; enter them when executing the installer.




Select language:

Pandora agent 3.0 RC3 install windows 01.png

Follow the steps of the installer:

Pandora agent 3.0 RC3 install windows 021.png

Acept Terms and Conditions and click Next:

Pandora agent 3.0 RC3 install windows 031.png

Select the path where the Pandora FMS agent will be installed (by default it is installed in c:/program files/pandora_agent), but you can change it by clicking on Browse..., and then Next:

Pandora agent 3.0 RC3 install windows 041.png

Wait for the files to be copied.

Pandora agent 3.0 RC3 install windows 061.png

Configure the data for the agent as the IP address (or name) of the Pandora FMS server that will receive the agent data. In order to be able to change other parameters, such as the agent name (by default it takes the hostname value of the machine) or the path of the temporary files, you will have to manually edit the agent configuration.


Pandora agent 3.0 RC3 install windows 071.png

Pandora agent 3.0 RC3 install windows 072.png

Start Pandora FMS agent service, otherwise you will have to do it manually, or it will start when Windows restarts again.

Pandora agent 3.0 RC3 install windows 081.png

The installation is finished. You can change the agent parameters in the file pandora_agent.conf or through the direct link in the PandoraFMS menu.

2.7.1 Unattended Windows Agent Installation

Starting with the agent's VERSION 5.1, the installer supports unattended mode. To perform the installation, simply run the following:

"Pandora FMS Windows Agent v7.0NG.VERSION-BUILD_ARCH.exe" /S

In case you want to install the agent in a different path than the default one:

"Pandora FMS Windows Agent v7.0NG.VERSION-BUILD_ARCH.exe" /S /D=C:\Agent_Pandora

You can also pass certain parameters so that they are written in the configuration file of the agent to be created. Thanks to these options, the deployment of Pandora FMS agents is much more customizable. The options per command line that are supported are the following:

  • --ip: It corresponds to the token server_ip.
  • --group: It corresponds to the tokengroup.
  • --alias: It corresponds to the tokenagent_alias.

For example, if you want to create an agent that belongs to the groupApplications, with the name Mifunne and that points to the server with the IP 192.168.0.59, the command would be:

"Pandora FMS Windows Agent v7.0NG.VERSION-BUILD_ARCH.exe" /S  --ip 192.168.0.59 --group Applications --alias Mifunne

2.7.2 Unattended Uninstallation

The uninstaller that is an executable named uninstall. exe in the Pandora FMS installation directory also enables the unattended uninstaller, to do it, run the uninstaller with the option /S .

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

c:\program files\pandora_agent

You should execute:

“c:\program files\pandora_agent\uninst.exe” /S

2.7.3 Using PandoraAgent.exe from the command line

If you run pandoraagent.exe --help, it will show you something similar to this:

C:\Program Files\pandora_agent>pandoraagent.exe --help
Pandora agent for Windows. Version 7.0NG.752(Build 210223)
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.
C:\Program Files\pandora_agent>


To install the service (if it is not installed), just run the following inside the directory where the executable is located (usually C:\Program Files or equivalent).

pandoraagent.exe --install

This will prompt the service on the machine, based on the path where the .exe is located.

To check whether it connects through SSH with Pandora FMS server:

C:\Windows\system32>cd %PROGRAMFILES%

C:\Program Files>cd pandora_agent

C:\Program Files\pandora_agent>PandoraAgent.exe --test-ssh
Public key file C:\Program Files\pandora_agent\key\id_dsa.pub exists.
Private key file: C:\Program Files\pandora_agent\key\id_dsa exists.
Connecting with pfms.example.com.
Authentication successful.
Host fingerprint:
Created a blank XML file in C:\Program 
Files\pandora_agent\temp\ssh.test
Remote copying C:\Program Files\pandora_agent\temp\ssh.test on server pfms.example.com at /var/spool/pandora/data_in/ssh.test
Successfuly file copied to remote host
Successfuly disconnected from remote host
The SSH test was successful!

If you want to uninstall it, the process is the same but using:

pandoraagent.exe --uninstall

2.7.4 Pandora FMS Windows Agent as a process

It possible, for debugging, testing and other unusual circumstances, execute the agent in "Process" mode. This is done by running it from the command line:

pandoraagent.exe --process

There are some limitations in the execution of the process mode, since Pandora FMS is meant to run as a service and under the user SYSTEM. If you run it with another user without privileges, there will be features that will not work properly.

Go back to Pandora FMS documentation index