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

From Pandora FMS Wiki
Jump to: navigation, search
(Unattended Windows Agent Installation)
(Minimum software requirements: Translation from Spanish to English.)
 
(170 intermediate revisions by 13 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]]
 +
 +
  
 
= Console and Pandora FMS Server Installation =
 
= Console and Pandora FMS Server Installation =
Line 40: Line 42:
 
</table>
 
</table>
  
(*) In addition to the above recommendations, we recommend installing MySQL on a standalone server and installing Percona XTraDB instead of standard MySQL.
+
(*) In addition to the these recommendations, we recommend installing MySQL on a standalone server and installing '''Percona XTraDB''' instead of standard MySQL.
  
  
 
<br>
 
<br>
{{Warning|In case you install Pandora FMS in a virtual environment, be sure to assign an independent disk with reserved space and a high access speed. }}
+
{{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.}}
 
 
{{Tip|We strongly recommend the use of ''SSD'' disks, due to the high impact they have on performance improvement.}}
 
  
{{Tip|A 25GB disk is recommended, with a minimum of 15GB. If you are going to use functionalities such as log storage or want to save information more than one month old, you should use the ''history database''.}}
+
{{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>
  
 
== Minimum software requirements ==
 
== Minimum software requirements ==
Line 60: Line 60:
 
<th rowspan =2 style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Operating System</th>
 
<th rowspan =2 style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Operating System</th>
 
<td colspan=3 style=' text-align: center;'>
 
<td colspan=3 style=' text-align: center;'>
 +
* RedHat Enterprise (RHEL) 7.X (Enterprise only)
 +
* RedHat Enterprise (RHEL) 8.X (Enterprise only)
 +
* CentOS 7.X ('''recommended''')
 +
* CentOS 8.X
 +
</td>
 +
</tr>
 +
<tr>
 +
<td colspan=2 style=' text-align: center;'>
 
* Windows Server (2003 or higher)
 
* Windows Server (2003 or higher)
* RedHat Enterprise (RHEL) 7.X
 
* CentOS 7.X (recommended)
 
 
* SLES 11 SP1 or higher
 
* SLES 11 SP1 or higher
 
* OpenSUSE 11.X or higher
 
* OpenSUSE 11.X or higher
 
* Debian 5, 6, 7 or higher
 
* Debian 5, 6, 7 or higher
* Ubuntu 11 or higher</td>
+
* Ubuntu 11 or higher
</tr>
 
<tr>
 
<td colspan=2 style=' text-align: center;'>
 
 
* FreeBSD 9.X and 10.X
 
* FreeBSD 9.X and 10.X
 
* Solaris 10/OpenSolaris
 
* Solaris 10/OpenSolaris
 
</td>
 
</td>
<td style='text-align: center; background-color: #FCFFD2'> Pandora FMS does not give official support in these platforms </td>
+
<td style='text-align: center; background-color: #FCFFD2'> '''Pandora FMS does not give official support in these platforms''' </td>
 
<tr>
 
<tr>
 
<th style=' border-color: #000000; background-color: #7CA12A; color:#FFFFFF'>Permissions</th>
 
<th style=' border-color: #000000; background-color: #7CA12A; color:#FFFFFF'>Permissions</th>
Line 79: Line 82:
 
* '''Server'''
 
* '''Server'''
  
- Linux: Pandora FMS Server service must be executed as root permissions. It is possible the execution as non-root user, being a special and different procedure, more information in this link.
+
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]].
 
 
-Windows: Pandora FMS Server service must be executed as administrator permissions.
 
  
 
* '''Console'''
 
* '''Console'''
Line 87: Line 88:
 
To be able to use the console from any web browser, Apache must have read and execute permissions on the console files.
 
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).
+
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: /var/spool/pandora/.
+
It is necessary to have writing permissions in the server directory: <code>/var/spool/pandora/</code>.
  
 
* '''Agent'''
 
* '''Agent'''
  
-Linux: The Pandora FMS Server Software Agent must be executed as root permissions in order to have all the agent functionalities, although it is also possible to execute it with other permissions..
+
-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 permissions.
+
-Windows®: Pandora FMS Server Software Agent must be executed as administrator permission.
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 108: Line 109:
 
<th rowspan =2 style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Browsers    </th>
 
<th rowspan =2 style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Browsers    </th>
 
<td colspan=3 style='text-align: center'>
 
<td colspan=3 style='text-align: center'>
* Microsoft Edge
+
* Microsoft Edge®
* Opera
+
* Opera web browser®
* Chrome
+
* Google Chrome®
* Firefox
+
* Mozilla Firefox®
 
</td>
 
</td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<td colspan= 3 style='text-align:center; background-color: #FCFFD2'>
 
<td colspan= 3 style='text-align:center; background-color: #FCFFD2'>
Firefox and Chrome are recommended to make use of interactive graphs and network maps.
+
Mozilla Firefox® and Google Chrome® are recommended to make use of interactive graphs and network maps.
 
</td>
 
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
There are Pandora FMS server functionalities that are not supported for Windows. To learn more about these functionalities visit the following [[Pandora:Documentation_en:Installing#Server_and_Console_Installation_in_Windows| link.]]
 
  
 
== Database requisites ==
 
== Database requisites ==
Line 127: Line 127:
 
<tr>
 
<tr>
 
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>BBDD</th>
 
<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'>Detalles</th>
+
<th style=' border-color: #000000; text-align:center; background-color: #7CA12A; color:#FFFFFF'>Details</th>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>MySQL Standard</th>
 
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>MySQL Standard</th>
 
<td>
 
<td>
* Version 5.5
+
* '''Version 5.7'''
* For the standard installation, a user with creation privileges in the pandora DB is required. In case of not having this user, a manual installation can be done.
+
* 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>
 
</td>
 
</tr>
 
</tr>
Line 139: Line 139:
 
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Percona XTraDB</th>
 
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Percona XTraDB</th>
 
<td>
 
<td>
Percona XTraDB installation is recommended for large Pandora FMS environments where more than 4000 agents will be created.
+
Percona XTraDB installation is recommended for large Pandora FMS environments where more than 4000 agents must be created.
  
* Version 5.5
+
* '''Version 5.7'''
* For the standard installation, a user with creation privileges in the pandora DB is required. In case of not having this user it will be possible to make a manual installation.
+
* 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.
 
</td>
 
</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
 
 
{{Warning|You will need to have all this BEFORE you start installing Pandora FMS. If you don't know how to install a MySQL server, look for documentation about the whole process. We can't provide all that documentation since it varies in each system, distribution and/or version.}}
 
  
 
== Satellite Server Requirements==
 
== Satellite Server Requirements==
Line 159: Line 156:
 
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Hardware</th>
 
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>Hardware</th>
 
<td>
 
<td>
As it happens with Pandora FMS installation, the hardware requirements of the system that will host the satellite server will depend on the monitoring volume that it will have to do.
+
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, we recommend a minimum of 1 core at 2GHz and 1 GB of RAM.
+
For environments with less than 1000 agents, a minimum of 1 core at 2GHz and 1 GB of RAM is recommended.
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 167: Line 164:
 
<td>
 
<td>
 
The main dependencies are:
 
The main dependencies are:
* Fping
+
* <code>fping</code>
* Nmap
+
* <code>nmap</code>
* Perl
+
* <code>perl</code>
 +
* <code>wmic</code>
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 176: Line 174:
 
<td>
 
<td>
 
The main dependencies are:
 
The main dependencies are:
* Linux 32 Bits
+
* Linux® 32 Bits
* Linux 64 Bits
+
* Linux® 64 Bits
* Windows 32 Bits
+
* Windows® 32 Bits
* Windows 64 Bits
+
* Windows® 64 Bits
* Raspberry</td>
+
* Raspberry Pi OS</td>
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 199: Line 197:
 
<td> Pandora FMS Console </td>
 
<td> Pandora FMS Console </td>
 
<td> IP management  </td>
 
<td> IP management  </td>
<td> Browser -> Pandora FMS Console Server </td>
+
<td> Browser '''->''' Pandora FMS Console Server </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 205: Line 203:
 
<td> TCP </td>
 
<td> TCP </td>
 
<td> Pandora FMS Console (API Communication) </td>
 
<td> Pandora FMS Console (API Communication) </td>
<td> Use of API/CLI functionality </td>
+
<td> Use of API/CLI feature </td>
<td> Browser/Server that starts the query -> Pandora FMS Console Server</td>
+
<td> Browser/Server that starts the query '''->''' Pandora FMS Console Server</td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 213: Line 211:
 
<td> Metaconsole </td>
 
<td> Metaconsole </td>
 
<td> Communication between Metaconsole and Nodes </td>
 
<td> Communication between Metaconsole and Nodes </td>
<td> Metaconsole server -> Node Server
+
<td> Metaconsole server '''->''' Node Server
  
Node Server -> Metaconsole server </td>
+
Node Server '''->''' Metaconsole server </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 221: Line 219:
 
<td> UDP </td>
 
<td> UDP </td>
 
<td> Pandora FMS Server </td>
 
<td> Pandora FMS Server </td>
<td> Traps reception </td>
+
<td> Trap reception </td>
<td> Trap generator device -> Pandora FMS Server </td>
+
<td> Trap generator device '''->''' Pandora FMS Server </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 228: Line 226:
 
<td> TCP </td>
 
<td> TCP </td>
 
<td> Pandora FMS Console (API Communication)</td>
 
<td> Pandora FMS Console (API Communication)</td>
<td> Use of API/CLI functionality </td>
+
<td> Use of API/CLI feature </td>
<td> Browser/Server that starts the query -> Pandora FMS Console Server </td>
+
<td> Browser/Server that starts the query '''->''' Pandora FMS Console Server </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 236: Line 234:
 
<td> Metaconsole </td>
 
<td> Metaconsole </td>
 
<td> Communication between Metaconsole and Nodes </td>
 
<td> Communication between Metaconsole and Nodes </td>
<td> Metaconsole server -> Node server
+
<td> Metaconsole server '''->''' Node server
  
Node server -> Metaconsole server </td>
+
Node server '''->''' Metaconsole server </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 245: Line 243:
 
<td> Pandora FMS Console and Server </td>
 
<td> Pandora FMS Console and Server </td>
 
<td> DB connection</td>
 
<td> DB connection</td>
<td> Pandora FMS Console Server -> Pandora FMS Database Server
+
<td> Pandora FMS Console Server '''->''' Pandora FMS Database Server
  
Pandora FMS Server -> Pandora FMS Database Server </td>
+
Pandora FMS Server '''->''' Pandora FMS Database Server </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 254: Line 252:
 
<td> Metaconsole </td>
 
<td> Metaconsole </td>
 
<td> Communication between Metaconsole and DB Nodes </td>
 
<td> Communication between Metaconsole and DB Nodes </td>
<td> Metaconsole server -> DB Nodes Server
+
<td> Metaconsole server '''->''' DB Nodes Server
  
Node Server -> Metaconsole BBDD Server </td>
+
Node Server '''->''' Metaconsole BBDD Server </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 262: Line 260:
 
<td> TCP </td>
 
<td> TCP </td>
 
<td> Pandora FMS Server </td>
 
<td> Pandora FMS Server </td>
<td> Conection with Selenium GRID </td>
+
<td> Connection with Selenium GRID </td>
<td> Pandora FMS Server -> Selenium Server </td>
+
<td> Pandora FMS Server '''->''' Selenium Server </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 270: Line 268:
 
<td> Pandora FMS Server </td>
 
<td> Pandora FMS Server </td>
 
<td> Receiving Netflow probes </td>
 
<td> Receiving Netflow probes </td>
<td> nfcapd Server -> Pandora FMS Server </td>
+
<td> nfcapd Server '''->''' Pandora FMS Server </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>10514 </th>
+
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>9200 </th>
 
<td> TCP </td>
 
<td> TCP </td>
 
<td> Pandora FMS Console and Server </td>
 
<td> Pandora FMS Console and Server </td>
<td> Log storage management with Logstash </td>
+
<td> Log storage management with Elasticsearch </td>
<td> Logstash Server -> Pandora FMS Server </td>
+
<td> Elasticsearch Server '''->''' Pandora FMS Server </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 284: Line 282:
 
<td> Pandora FMS Agents </td>
 
<td> Pandora FMS Agents </td>
 
<td> Tentacle Communication </td>
 
<td> Tentacle Communication </td>
<td> Agente Software Agent Server -> Pandora FMS Server </td>
+
<td> Software Agent Server Agent '''->''' Pandora FMS Server </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
<th colspan= 5 style=' border-color: #000000; text-align:center; background-color: #7CA12A; color:#FFFFFF'> It is recommended to facilitate the communication from the Pandora FMS server and console to the whole network. For standard monitoring you would need as minimum:</th>
+
<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>
 
<tr>
 
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>80 </th>
 
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>80 </th>
Line 293: Line 291:
 
<td> Pandora FMS Server </td>
 
<td> Pandora FMS Server </td>
 
<td> Web monitoring for WUX server </td>
 
<td> Web monitoring for WUX server </td>
<td> Pandora FMS Server -> Server to monitor </td>
+
<td> Pandora FMS Server '''->''' Server to monitor </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 300: Line 298:
 
<td> Pandora FMS Console and Server </td>
 
<td> Pandora FMS Console and Server </td>
 
<td> Monitoring via SNMP Polling </td>
 
<td> Monitoring via SNMP Polling </td>
<td> Pandora FMS Server -> Server to monitor </td>
+
<td> Pandora FMS Server '''->''' Server to monitor </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
Line 306: Line 304:
 
<td> TCP </td>
 
<td> TCP </td>
 
<td> Pandora FMS Server </td>
 
<td> Pandora FMS Server </td>
<td> Monitorización web para servidor WUX </td>
+
<td> Web monitoring for WUX server </td>
<td> Pandora FMS Server -> Server to monitor </td>
+
<td> Pandora FMS Server '''->''' Server to monitor </td>
 
</tr>
 
</tr>
 
<tr>
 
<tr>
 
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>ICMP </th>
 
<th style=' border-color: #000000; text-align:middle; background-color: #7CA12A; color:#FFFFFF'>ICMP </th>
 
<td> ICMP </td>
 
<td> ICMP </td>
<td> Consola y Pandora FMS Server </td>
+
<td> Console and Pandora FMS Server </td>
 
<td> Web monitoring for WUX server </td>
 
<td> Web monitoring for WUX server </td>
<td> Pandora FMS Server -> Server to monitor </td>
+
<td> Pandora FMS Server '''->''' Server to monitor </td>
 
</tr>
 
</tr>
 
</table>
 
</table>
Line 320: Line 318:
 
== Package Dependencies ==
 
== Package Dependencies ==
  
Pandora FMS has a strong dependency on the GNU/Linux Operating System, but it also needs additional packages which,  in many cases, aren't installed by default. During the installation process, there is a detailed list of package dependencies for Debian, Ubuntu and OpenSUSE.
+
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.
  
 
== 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, since the next step after installing the Pandora 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 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>
  
In ''<password>'', you have to type the password 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 is configured 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 is capable of being 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 ===  
The proper order for an Enterprise installation is as follows:
+
 
 +
The correct order for an Enterprise installation is as follows:
  
 
* Install the open-source console.
 
* Install the open-source console.
 
* 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.
 
* 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 on the server.
+
Validation of the license is only done in the console. '''Not''' in the server.
  
We can find details on how to correctly enter the license in the following section: [[Pandora:Documentation en:Installing#License_Application | '''License Application v5.X''']] window opens.
+
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>
  
==== Special Requirements for the Enterprise Version ====
+
== Installation via Cloud provider ==
  
The Enterprise installation of the web console has no additional dependencies. The installation of the Enterprise server is done by means of an installer in binary format that contains all the necessary dependencies.
+
The term "Cloud provider" (or simply "Cloud") is used to describe the hosting of virtual machines, either exclusively or shared, in specialised providers with hardware, hypervisors and customer support web systems for configuration and administration.
  
== Installation using ISO or "Software appliance"  ==
+
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).
  
This DVD ISO contains a modified CentOS7 system, with Pandora FMS software, all its dependencies, pre-configured and ready to install along with the operating system in a machine (virtual or real). Due to the length of this section, we have established a special screen shot-equipped section. It's called [[Pandora:QuickGuides_EN:General_Quick_Guide#Installing_the_Appliance_CD|'''Appliance CD Installation.''']]
+
Access the command line as provided by your Cloud provider and execute:
  
== Installation under Docker ==
+
<nowiki>curl -Ls https://pfms.me/deploy-pandora | sh</nowiki>
  
=== Get the latest stable version ===
+
== Installation using ISO or "Software appliance"  ==
To get the latest stable version:
 
  
    curl -sSL http://pandorafms.org/getpandora  | sh
 
  
 +
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.
  
{{Warning|This command requires Docker Engine installed and running.}}
+
<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.  
  
=== Advanced installation ===
+
[[Image:Install_1.png|center|520px]]
  
Pandora FMS runs as a container under Docker environments. It can be launched as follows:
+
<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.
    docker run -d --name pandorafms pandorafms/pandorafms:7
 
  
{{Tip|Docker images are updated on a daily basis}}
+
[[image:Install_2.png|center|520px]]
  
{{Tip|The latest stable version is 7.}}
+
<br><hr>It is a very easy process but special attention must be paid when:
  
== Installing the VMWare Virtual Machine ==
+
* Entering the superuser password (root).
 +
* When asked about the hard drive partitioning:
  
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.
+
[[Image:Install_3.png|center|520px]]
  
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.
+
Select and configure all the necessary options to install, '''Date & Time''', '''Keyboard''' and '''Installation Destination'''.
  
The credentials for this machine are the following:
+
<br><hr>Remember to activate the network interface, or else it will need to activated manually after installation.
  
''User:'' ''' root'''
+
[[Image:Install_4.png|center|520px]]
  
''Password:'' ''' pandora'''
+
Activate the network interface and optionally change the hostname
  
''Console User:'' ''' admin'''
+
[[Image:Install_5.png|center|520px]]
  
''Password:'' ''' pandora'''
+
<br><hr>When clicking the installation destination button, the partition process will start.
  
''MySQL user:''''' root'''
+
[[Image:Install_6.png|center|520px]]
  
''Password:'' ''' pandora'''
+
<br><hr>Select the disk where the installation will be performed and click on '''Done'''.
  
{{Warning|For security reasons, please change the passwords used during the installation as soon as possible.}}
+
[[image:install_7.png|500px]]
  
== Installation under SUSE (OpenSUSE or SLES) ==
+
<br><hr>Select the partitioning, unless you have advanced knowledge use the option ''''Click here to create them automatically''''. Click '''Done'''.
  
=== Automatized Installation by the Official Repository ===
+
[[Image:Install_8.png|center|520px]]
  
To be able to choose this method -the fastest and most convenient-, you have to have access to internet from the server where you are going to install Pandora FMS. All steps must be executed as root (or under sudo).
+
<br><hr>Verify the created partitions and click on '''Done'''.
  
'''Step 1:''' Create a repository :
+
[[image:install_9.png|500px]]
  
#'''SLES 12 SP3'''
+
Accept Changes.
zypper ar -f http://firefly.artica.es/suse PandoraFMS_Official_Repo
+
<br><hr>Click on '''Begin installation'''.
zypper ar -f http://download.opensuse.org/repositories/server:/php:/applications/SLE_12_SP3/
 
zypper ar -f http://download.opensuse.org/repositories/devel:/languages:/perl/SLE_12_SP3/ Perl
 
  
wget --no-check-certificate https://dev.mysql.com/get/mysql80-community-release-sles12-1.noarch.rpm
+
[[Image:Install_10.png|center|520px]]
rpm -i mysql80-community-release-sles12-1.noarch.rpm
 
  
#'''openSUSE (15.0)'''
+
<br><hr>Here you can assign the root password and optionally create a user.
zypper ar -f http://firefly.artica.es/suse PandoraFMS_Official_Repo
 
zypper ar -f http://download.opensuse.org/repositories/server:/php:/applications/openSUSE_Leap_15.0/ Php5
 
zypper ar -f http://download.opensuse.org/repositories/devel:/languages:/perl/openSUSE_Leap_15.0/Perl
 
 
wget --no-check-certificate https://dev.mysql.com/get/mysql80-community-release-sl15-1.noarch.rpm
 
rpm -ivh mysql80-community-release-sl15-1.noarch.rpm
 
  
 +
[[Image:Install_11.png|center|520px]]
  
'''Step 2:''' Update the repository's information:
+
Now just wait until the process is finished and the system restarts automatically.
  
zypper refresh
+
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.
  
'''Step 3:''' Install Pandora FMS and some of its dependencies :
+
== Installing the ISO image using a USB Stick ==
  
zypper install pandorafms_console pandorafms_server apache2-mod_php5
 
  
{{Warning|For versions of Pandora FMS 729 or higher, it will be necessary to update to PHP7 so the console works}}
+
To install the Pandora FMS appliance from a USB flash drive, follow these steps:
  
=== Manual RPM Installation ===
+
* 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'''.
  
==== Previous Dependencies Installation ====
+
<center>
 +
[[image:Usb_installation_1.PNG]]
 +
</center>
  
For this documentation we will make use of the Suse '''Zypper''' system that allows you to resolve dependencies and download packages directly from the repositories on the internet. If you don't have Zypper, install it, it's much more comfortable and fast. If this is not possible, dependencies can be downloaded in. rpm format from the internet, but the process is considerably longer and more laborious.
+
* Select the Pandora FMS ISO image.
  
The following package dependencies, included in the SUSE system, must be installed:
+
<center>
 +
[[image:Usb_installation_2.PNG]]
 +
</center>
  
apache2 apache2-mod_php5 php5 php5-gd php5-gettext php5-json php5-mbstring php5-ldap php5-mysql \
+
* Press '''START''' to start the creation of the Pandora FMS installation USB.
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
 
  
 +
<center>
 +
[[image:Usb_installation_3.PNG]]
 +
</center>
  
{{Tip|Unlike SLES, OpenSUSE doesn't have a 'mysql-max' package. You may install the MySQL standard package instead without experiencing any problems.}}
+
<center>
{{Warning|For versions of Pandora FMS 729 or higher, it is necessary to install the dependencies of PHP7 for a correct use of the console}}
+
[[image:Usb_installation_4.PNG]]
 +
</center>
  
In order to install all dependencies execute:
+
* Your Pandora FMS installation USB device is ready
  
zypper install ..
+
<center>
 +
[[image:Usb_installation_5.PNG]]
 +
</center>
  
Followed by the whole package list, specified in the paragraph above, this is going to display a screen like the one below:
 
  
Getting repositories data...
+
* Connect the USB to the machine where you want to install Pandora FMS.
Reading packets installed...
+
* When starting the system, configure the BIOS to start first from USB.
perl-DBI already installed.
 
perl-HTML-Parser already installed.
 
perl-TimeDate already installed.
 
perl-XML-Simple already installed.
 
perl-libwww-perl already installed.
 
xorg-x11-fonts-core already installed.
 
Resolving dependencies...
 
 
Following NEW packages will be installed:
 
  apache2 apache2-mod_php5 apache2-prefork apache2-utils libapr1 libapr-util1 libdnet1
 
liblua5_1 libmm14 libmysqlclient15 mysql mysql-client mysql-Max net-snmp nmap
 
perl-Bit-Vector perl-Carp-Clan perl-Data-ShowTable perl-Date-Calc perl-Date-Manip
 
perl-DBD-mysql perl-HTML-Encoding perl-HTML-Tree perl-IO-Socket-inet6
 
perl-Mail-Sendmail perl-NetAddr-IP perl-SNMP php5 php5-ctype php5-dom php5-gd
 
php5-gettext php5-hash php5-iconv php5-json php5-ldap php5-mbstring php5-mysql
 
php5-openssl php5-pdo php5-pear php5-snmp php5-sqlite php5-tokenizer php5-xmlreader
 
php5-xmlwriter php5-zip php5-zlib t1lib perl-JSON
 
 
Total Size: 19.1 M. After the operation, additional 55.9 M will be used.
 
  Continue? [Yes / no]:
 
  
Click 'yes' to download Zypper and install the packages.
+
The following screen should be displayed:
  
When finished, you're required to install some extra packages. Under OpenSuse, the required packages for Pandora FMS are at https://sourceforge.net/projects/pandora/files/Pandora%20FMS%207.0NG/Final/. Additional RPMs 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_6.PNG]]
 +
</center>
  
perl-time-format php-pear-xml_rpc wmic smstools perl-HTML-Tree perl-XML-Twig
+
Select '''Installing from USB stick''' and continue the installation as described in the previous chapter.
  
 +
== Package installation for CentOS 7/8 ==
  
{{Tip|Extra packages like 'Perl-HTML-Tree' and 'Perl-XML-Twig' require manual installation.}}
+
=== Repository configuration ===
  
{{Tip|In Centos7 wmic is not an explicit requirement 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 site].}}
+
==== Repository configuration on CentOS 8 ====
  
 +
To configure it it will be necessary to execute the following commands:
  
If you intend to use the Recon Server, install these additional packages:
+
dnf install -y \
 +
    epel-release \
 +
    tar \
 +
    dnf-utils \
 +
    http://rpms.remirepo.net/enterprise/remi-release-8.rpm
  
  perl-net-traceroute perl-net-traceroute-pureperl xprobe2
+
  dnf module reset php
 +
dnf module install -y php:remi-7.3
 +
yum config-manager --set-enabled PowerTools
  
These RPM files can be found on the official distribution site of Pandora FMS Software in a specific dependencies directory for OpenSUSE.
+
(''Note'': In CentOS 8.3 it changes from PowerTools to powertools.)
  
{{Tip|Please make sure to download the appropriate packages for OpenSUSE.}}
+
==== Repository configuration in CentOS 7 ====
  
Please put them in a directory to install them, e.g.: '/tmp/extra' and execute the following command:
+
Configure <b>yum</b> and the necessary repositories. Execute the following commands:
  
  rpm -i *.rpm
+
  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
  
==== Server Installation ====
+
yum-config-manager --enable remi-php73
  
Just execute:
 
  
rpm -i pandorafms_server-5.1SP2-1.noarch.rpm
+
=== Database installation ===
  
==== Console Installation ====
+
==== Database installation on CentOS 8 ====
  
Please execute the RPM installation tool for packages in order to install the package which contains the Pandora FMS Console:
 
  
  rpm -i pandorafms_console-5.1SP2-1.noarch.rpm
+
It will also be necessary to install a database <b>percona</b> using the following commands:  
  
=== Uninstalling Pandora FMS ===
 
  
You're able to uninstall any of Pandora FMS components by 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
  
rpm -e pandorafms_agent
+
==== Database installation on CentOS 7 ====
rpm -e pandorafms_console
 
rpm -e pandorafms_server
 
  
The Pandora FMS database won't get uninstalled if any of the Pandora FMS packages are - but all files from any other package (including the configuration files) will be deleted, but the database  will have to be deleted manually.
 
  
== Installation in Red Hat Enterprise Linux / Fedora / CentOS ==
+
It will also be necessary to install a database <b>percona</b> using the following commands: 
  
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.
+
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
  
First of all, you will need to activate certain official Redhat/Centos/Fedora repositories to perform dependency installation. The repositories to be activated are EXTRAS, UPDATES and the additional installation of the EPEL repository.
 
  
Edit /etc/yum.repos.d/CentOS-Base.repo and enable EXTRAS, and UPDATES repos. Usually should be something like this:
+
=== Dependency installation ===
  
 +
==== Dependency installation on CentOS 8 ====
  
[updates]
+
'''Console dependencies'''
name=CentOS-$releasever - Updates
 
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=updates
 
gpgcheck=0
 
 
[extras]
 
name=CentOS-$releasever - Extras
 
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras
 
gpgcheck=0
 
  
Add the EPEL repository:
+
Once with <b>dnf</b> and <b>percona</b> installed we can start to install all the necessary dependencies for the <b>console</b>:  
  
[EPEL]
 
Name = EPEL
 
baseurl = http://dl.fedoraproject.org/pub/epel/$releasever/$basearch/
 
enabled = 1
 
gpgcheck = 0
 
  
Please refresh your repository information with this command:
+
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
  
yum makecache
 
  
=== Installation using the Pandora FMS Repository ===
+
'''Phantomjs''' is a special component used to generate PDF graphs dynamically. Install it through the command:
  
You're going to need YUM and access to the Internet. First, you're required to create a reference to the Pandora FMS official repository for CentOS 7. This also applies for the usage under RHEL7.
 
  
  vi /etc/yum.repos.d/pandorafms.repo
+
  dnf install -y http://firefly.artica.es/centos8/wmi-1.3.14-4.el7.art.x86_64.rpm
 
Add these contents:
 
  
[artica_pandorafms]
+
'''Server dependencies'''
name=CentOS7 - PandoraFMS official repo
 
baseurl=http://firefly.artica.es/centos7
 
gpgcheck=0
 
enabled=1
 
  
 +
Once console dependencies are installed, install those of the '''server''':
  
Refresh your repository information:
+
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
  
yum makecache
+
After this, the following additional dependencies from different components must be installed from Pandora FMS public repository:
  
And install Pandora FMS, along with the mysql server (it is an optional dependency, but you will need a MySQL server if you don't have one already installed or accessible in another server).
+
dnf install -y <nowiki>http://firefly.artica.es/centos8/wmi-1.3.14-4.el7.art.x86_64.rpm</nowiki>
 +
dnf install -y <nowiki>http://firefly.artica.es/centos8/perl-Net-Telnet-3.04-1.el8.noarch.rpm</nowiki>
 +
dnf install -y <nowiki>http://firefly.artica.es/centos7/xprobe2-0.3-12.2.x86_64.rpm</nowiki>
  
yum install pandorafms_console pandorafms_server mariadb-server
+
{{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.}}
  
Download all the necessary packages and leave the system ready for configuration and use.
+
if necessary, add all [[Pandora:Documentation_en:Discovery |Discovery]] dependencies for each section.
  
{{Tip|Mariadb-server replaces the mysql-server package, but it depends on the distro you're using (it is not the same CentOS as RHEL, you will have to use one or the other, being the differences of use minimum when using Pandora).}}
+
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>
  
=== Manual Installation by RPM Files ===
+
==== Dependency installation on CentOS 7 ====
  
Most dependencies should be resolved using YUM or another automatic tool. All dependencies are marked as required packages in the RPM definition. If you have already configured the required repositories in the previous step, this operation will be almost automatic.
+
'''Console dependencies'''
  
In the case of CentOS it will be necessary to install the following dependencies:
+
Once with repositories and <b>percona</b> installed we can start to install all the necessary dependencies for the <b>console</b>:  
  
yum install php php-gd graphviz php-mysql php-pear-DB php-zip php-mbstring php-ldap \
 
php-snmp php-ldap php-common make perl-CPAN perl-HTML-Tree perl-DBI perl-DBD-mysql \
 
perl-libwww-perl perl-XML-Simple perl-XML-Twig perl-XML-SAX perl-NetAddr-IP \
 
net-snmp perl-SNMP net-tools perl-IO-Socket-INET6 perl-Socket6 nmap sudo xprobe2 \
 
perl-Encode-Locale
 
  
It is possible that if you use Fedora or Redhat the names of some packages are slightly different, so we will use these added to the previous ones:
+
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
  
yum install net-snmp-perl perl-JSON perl-NetAddr-IP perl-Socket6 \
+
<b>Phantomjs</b> is a special component used to generate PDF graphs dynamically. Install if from Pandora FMS servers through the command:
perl-Time-HiRes perl-XML-Twig perl-IO-Socket-INET6
 
  
Some dependencies (like 'wmic' or 'xprobe2') aren't contained in the official RHEL repositories. We're providing them on our Sourceforge download page in the "Tools and Dependecies" section [https://sourceforge.net/projects/pandora/files/Tools%20and%20dependencies%20%28All%20versions%29].
+
yum install -y <nowiki>https://firefly.pandorafms.com/centos8/phantomjs-2.1.1-1.el7.x86_64.rpm</nowiki>
  
In the meantime, for Red Hat Enterprise Linux 6 it will be sufficient to install these others, as several of the packages required for the console and server are included in the php and perl and serial dependencies:
+
'''Server dependencies'''
  
yum install php php-common graphviz
+
To install all dependencies necessary for the <b>server</b> execute the following commands:
 
yum install perl-HTML-Tree perl-DBD-mysql perl-XML-Simple perl-XML-SAX \
 
perl-NetAddr-IP net-snmp perl-SNMP net-tools perl-IO-Socket-INET6 perl-Socket6 nmap wmic xprobe2
 
  
{{Warning|If you're using a version prior to RHEL6, some dependencies could have another name,In the case of perl-SNMP, in CentOS5, RHEL5, etc, the dependency to obtain would be net-snmp-perl.}}
+
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|For versions of Pandora FMS 729 or higher, it is necessary to install the dependencies of PHP7 for a correct use of the console}}
+
And finally install the following additional dependencies too from our public repository:
  
In order to install the RPM, just 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. For versions of Pandora FMS 729 or higher, its required to use PHP version 7.2}}
+
After previous steps, disable <b>SELINUX</b> and the firewall.  
  
To do so, we recommend using 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 can be 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
  
===  Uninstalling Pandora in CentOS/RHEL ===
+
Also generate the file <b>my.cnf</b>.
  
Just execute the order
+
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
  
yum remove pandorafms_console pandorafms_server
 
  
If you have installed MySQL and no longer need it, you can also delete it with the same command:
+
Once the changes have been saved, it will be necessary to restart the <code>mysqld</code> service. 
  
  yum remove mysql-server
+
  systemctl restart mysqld
  
== Installation under Debian and Ubuntu ==
+
Enable the services <code>mysql</code>, <code>apache</code> and <code>php</code>. 
  
Installing Pandora FMS '''version 10.04 or above''' is recommended. In the Debian Stable version (Squeeze) there are problems with some libraries and applications that Pandora FMS needs for some components. The Debian LWP library does not implement certain methods for SSL, and this is necessary for the Enteprise modules of WEB monitoring. You can fix this by installing a newer version of LWP using CPAN (manual method).
+
systemctl enable mysqld --now
 +
systemctl enable httpd --now
  
When installing you need to add the official repositories of each version. For example, to install the libencode-locale-perl and snmp-mibs-downloader packages in a Debian Squeeze, you will need to add the following repositories to the file named /etc/apt/sources.list
+
If you use CentOS 8, execute:
 +
systemctl enable php-fpm --now
  
 +
=== Pandora FMS console and server installation ===
  
deb http://ftp.us.debian.org/debian/ squeeze main non-free
+
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.   
  deb http://ftp.at.debian.org/debian-cd/ squeeze-backports main
 
  
Alternatively, for Debian Wheezy:
+
mkdir $HOME/pandora && cd $HOME/pandora
  
deb http://ftp.debian.org/debian/dists/Debian9.6/ wheezy-backports main
+
{{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.}}
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.
+
In the OpenSource version:
  
Due to the way in which Debian/Ubuntu manages the packages, it is more than recommended to install Pandora FMS in a system that has access to the online package repositories (or a replica in the local network). A dependency on Debian can involve dozens of sub-dependencies, so preparing an accurate list of packages needed for offline installation can be a very complex task.
+
wget <nowiki>https://firefly.pandorafms.com/pandorafms/latest/RHEL_CentOS/pandorafms_agent_unix-7.0NG.noarch.rpm</nowiki>
 +
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>
  
=== Installation with Artica Private Repository ===
+
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).
  
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.
+
Package installation (after download):
  
In order to do so, please edit the file '/etc/apt/sources.list' and add the following line:
+
yum install -y $HOME/pandora/pandorafms*.rpm
  
For Debian Squeeze:
+
For '''Enterprise''' tarball, execute:
  
  deb http://firefly.artica.es/debian/squeeze /
+
  tar xvfz $HOME/pandora/pandorafms_server* && cd pandora_server && ./pandora_server_installer --install --ha; cd -
  
For Debian Wheezy:
+
Once the process is finished, populate the database:  
  
  deb http://firefly.artica.es/debian/wheezy /
+
  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
  
Execute as root (sudo)
+
Then configure the console.
  
  apt-get update
+
  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
  
Installation of Pandora FMS by apt-get:
+
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
  
<pre>
+
sed -i -e "s/php_flag engine off//g" $PANDORA_CONSOLE/images/.htaccess
[email protected]:~# apt-get install pandorafms-console pandorafms-server pandorafms-agent-unix
+
sed -i -e "s/php_flag engine off//g" $PANDORA_CONSOLE/attachment/.htaccess
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>
 
  
{{Warning|For versions of Pandora FMS 729 or higher, it is necessary to install the dependencies of PHP7 for a correct use of the console}}
+
chmod 600 $CONSOLE_PATH/include/config.php
 +
chown apache. $CONSOLE_PATH/include/config.php
 +
mv $CONSOLE_PATH/install.php $CONSOLE_PATH/install.done
  
=== Manual Installation by DEB Packages ===
 
  
Under Debian or Ubuntu, the dependencies are the following:
+
Then prepare the file <b>php.ini</b>. 
  
Server:
+
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
  
  snmp snmpd libtime-format-perl libxml-simple-perl libdbi-perl libnetaddr-ip-perl
+
  cat > /var/www/html/index.html << EOF_INDEX
  libhtml-parser-perl wmi-client xprobe2 nmap traceroute
+
  <meta HTTP-EQUIV="REFRESH" content="0; url=/pandora_console/">
libio-socket-inet6-perl libhtml-tree-perl libsnmp-perl snmp-mibs-downloader
+
  EOF_INDEX
  libio-socket-multicast-perl libsnmp-perl libjson-perl libencode-locale-perl
 
  
 +
If you use CentOS 8, execute in addition:
  
{{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.]}}
+
systemctl restart php-fpm
 +
systemctl restart httpd
  
{{Tip|If you are installing Pandora FMS in a Debian Squeeze, you will need to add the "Non-Free" repository to access the snmp-mibs-downloader package.}}
+
The server configuration file will be prepared: 
  
Console:
+
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
  
php5 libapache2-mod-php5 apache2 mysql-server php5-gd php5-mysql php-pear php5-snmp php-db php-gettext
+
In the <b>Enterprise</b> version, enable the ([[Pandora:Documentation_en:HA|HA]]) service.
graphviz mysql-client php5-curl php5-xmlrpc php5-ldap
 
  
{{Warning|For versions of Pandora FMS 729 or higher, it is necessary to install the dependencies of PHP7 for a correct use of the console}}
+
systemctl enable pandora_ha --now
 +
service tentacle_serverd start
  
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 previously mentioned packages by using the command ''apt-get'' along with root privileges:
 
  
apt-get install  snmp snmpd libtime-format-perl libxml-simple-perl libxml-twig-perl libdbi-perl
+
In the <b>Community</b> version, pandora_ha service does not exist, so execute the following commands to enable the server:
libnetaddr-ip-perl libhtml-parser-perl wmi-client xprobe2 nmap libmail-sendmail-perl traceroute
 
libio-socket-inet6-perl libhtml-tree-perl libsnmp-perl snmp-mibs-downloader libio-socket-multicast-perl
 
libsnmp-perl libjson-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 dbconfig-common
 
  
 +
systemctl enable pandora_server --now
 +
systemctl start pandora_server
 +
service tentacle_serverd start
  
This command will install all the dependencies required to install the Pandora FMS Server and its console into a Debian or Ubuntu system.
 
  
{{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.}}
+
Enable the <code>cron</code> 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:
  
                   
+
[[Image:Pandora_login.png|center|800px]]
The installation with the DEB packages is very easy.  
 
  
FIf we do not have internet connection, we install the dependencies. Then we install the Pandora FMS packages, in this example all Pandora FMS components are installed together.
+
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.  
  
dpkg -i pandorafms-console_xxx.deb pandorafms-server_xxxx.deb
+
It is recommended to [[Pandora:Documentation_en:Installing#Pandora_FMS_Agent_Installation |install the agent]] to automonitor the server.
  
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:
+
<br><br><br>
  
apt-get -f install
+
=== 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.
  
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.
+
If you want to expand this license, please contact your trusted commercial or fill in the following [https://pandorafms.com/contact/ contact form]
  
{{Warning|In some Ubuntu versions you will have to move the directory /var/www/pandora_console/ to the public directory of the web server by default /var/www/html/pandora_console }}
+
The <b>Community</b> version does not require any license for its use.
  
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 '10.20.34.54', you're required to enter the following URL:
+
== Installation by packages on RHEL 7/8 ==
  
http://10.20.34.54/pandora_console
+
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]
  
=== Uninstalling Pandora FMS ===
+
== Installation under Docker ==
  
dpkg -r pandorafms-console-enterprise
+
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:
dpkg -r pandorafms-console
+
https://hub.docker.com/r/pandorafms/pandorafms-open-stack-el8
  
== Installation in FreeBSD ==
+
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>.
  
To install Pandora FMS server, FreeBSD 10.x or later is recommended.
+
First, you need to have installed in the system docker and docker compose, installation documentation: https://docs.docker.com/get-docker/
If you want to install it to FreeBSD 9.x or earlier with the following instructions, the package management system of FreeBSD should be updated to pkgng.
 
  
=== Previous Dependencies Installation ===
+
Once installed, we will use the <code>yaml</code> file from the official PandoraFMS repository:
  
In FreeBSD, the dependencies are the following:
+
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
  
Server:
+
We wait a few seconds for the download and configuration of the environment. You can access to the PFMS console from the URL:
  
  p5-DBI p5-Mail-Sendmail p5-NetAddr-IP p5-XML-Simple p5-Time-Format p5-HTML-Parser
+
  http://127.0.0.1:8080/pandora_console
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.
+
Use “admin” as user  and “pandora” as password.
  
You may install all the necessary dependencies in the following way:
+
==  Uninstalling Pandora FMS  ==
  
e.g.) p5-DBI installation.
+
Just execute the command
pkg install p5-DBI
 
  
Console:
+
yum remove pandorafms_console pandorafms_server
  
apache24, php5, php5-snmp, php5-session, php5-gettext, php5-mbstring, php5-ldap,
+
If MySQL is installed but it is no longer needed, it can also be deleted with the same command:
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 previously mentioned dependencies. You may use the packages to do so.
+
yum remove Percona-Server*
  
{{Warning |From version 729 of Pandora FMS it is necessary to update to PHP7 for the proper functioning of the tool}}
+
== Custom Installation ==
 +
=== Manual Installation from Sources under Linux / UNIX / MAC OS ===
  
=== Console Installation ===
+
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/.
  
There are no Pandora FMS Console package files for FreeBSD. The Pandora console must be installed by using the installer.
 
  
Installation via the installer is described in the section named 'Manual Installation from Sources in Linux/Unix' below.
+
==== Console Installation ====
  
Under FreeBSD with apache 2.4, the Pandora FMS console directory is:
+
Once you have opened the console zip file, follow these steps:
 
 
/usr/local/www/apache24/data/pandora_console
 
 
 
=== Server Installation ===
 
 
 
There are no Pandora FMS Server package files for FreeBSD. You're required to install the Pandora Server by using the installer.
 
 
 
Installation via 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 Linux. We're going to show the FreeBSD-specific procedures below.
 
 
 
After installation add the following lines to the '/etc/rc.conf' file:
 
 
 
pandora_server_enable="YES"
 
tentacle_server_enable="YES"
 
 
 
These settings are required to enable Pandora, the Pandora Servers and Tentacle. Otherwise, they are '''not''' going to be launched.
 
 
 
On FreeBSD, most of the Pandora server's files are gong to be installed in the directory named '/usr/local'.
 
 
 
pandora_server, tentacle_server:
 
/usr/local/bin/pandora_server
 
/usr/local/bin/tentacle_server
 
Startup script:
 
/usr/local/etc/rc.d/pandora_server
 
/usr/local/etc/rc.d/tentacle_server
 
Configuration file:
 
/usr/local/etc/pandora/pandora_server.conf
 
util:
 
/usr/local/share/pandora_server/util/*
 
Man pages:
 
/usr/local/man/man1/*
 
Other:
 
The 'data_in' and log directories are the same as 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 (using 'pkgsrc', recommended) before doing so.
 
 
 
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/download
 
 
 
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.
 
 
 
{{Warning |From version 729 of Pandora FMS it is necessary to update to PHP7 for the proper functioning of the tool}}
 
 
 
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. Install the Pandora server by using the installer.
 
 
 
Installation via 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.
 
 
 
== Manual Installation from Sources under Linux / UNIX / MAC OS ==
 
 
 
It will be necessary to download the files in "tarball" format (. tar. gz,. tgz or. tar. bz2) and unzip it. To do this, locate the latest version of Pandora FMS and download the files from here: https://sourceforge.net/projects/pandora/files/.
 
 
 
 
 
=== Console Installation ===
 
 
 
Once you've opened the console zip file, please follow these steps:
 
  
 
1. Acquire root privileges by entering:
 
1. Acquire root privileges by entering:
Line 1,000: Line 1,270:
 
  ./pandora_console_install --install
 
  ./pandora_console_install --install
  
=== Server Installation ===
+
==== Server Installation ====
  
Once you've opened the server zip 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 copy 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-X.Y.tar.gz  
 
  tar xvzf pandorafms_server-X.Y.tar.gz  
Line 1,014: Line 1,284:
 
  ./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.
  
=== Server Manual Installation (from source code) ===
+
==== Server Manual Installation (from source code) ====
  
Alternatively to the generic 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 scripts system, maintenance scripts, configuration or anything else that strictly concerns the application and its libraries. This process is indicated when you have to update the server code, but without overwriting its configuration.
+
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 this, unzip your server code to /tmp, as described in the previous step.
+
To do it properly, unzip your server code to <code>/tmp</code>, as described in the previous step.
  
1. We acquire root privileges:
+
1. Acquire root privileges. You are the only one responsible for that key:
  
 
  su -  
 
  su -  
  
2. We copy it to '/tmp' and in there, we execute:
+
2. Copy it to the directory where you are unzipping files (<code>/tmp</code> in this example) and once there, execute:
  
 
  tar xvzf pandorafms_server-X.Y.tar.gz  
 
  tar xvzf pandorafms_server-X.Y.tar.gz  
Line 1,039: Line 1,309:
 
  Warning: prerequisiete Net::Traceroute::PurePerl 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 doesn't have 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's why they are warnings and not errors) and force the installation. You are sure to have problems at one time or another as 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 with no poblems.
+
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, these files are automatically copied:
 
After this process, these files are automatically copied:
Line 1,046: Line 1,316:
 
  /usr/local/bin/pandora_exec
 
  /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:
+
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/
  
In SUSE/SLES 11 they're copied to:
+
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 ===
 
 
To install the Enterprise version of Pandora FMS, we have to install the packages "Open" of the Console and Server, and then add the packages "Enterprise" of each one. In the case of the '''Console''' we will use one package or another, depending on the distribution we have installed.
 
 
 
=== Enterprise Console Installation ===
 
 
 
For Red Hat Enterprise Linux / CentOS / Fedora:
 
 
 
rpm -i pandorafms_console_enterprise-X.X.noarch.rpm
 
 
 
For SUSE:
 
 
 
rpm -i pandorafms_console_enterprise-X.X.noarch.rpm
 
  
For Debian / Ubuntu:
+
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.
  
dpkg -i pandorafms_console_enterprise_xxx.deb
+
==== Enterprise Console Installation ====
  
 
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. We acquire root privileges by entering:
+
1. Acquire root privileges by entering:
  
 
  su -
 
  su -
  
2. Copy it to '/tmp' and in there 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.:
  
SUSE:
 
  
  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 ====
  
SUSE:
+
{{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:  
  
=== Enterprise Server Installation ===
+
1. Acquire root privileges. You are the only one responsible for that key:
 
 
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, please follow the below mentioned steps:
 
 
 
1. Acquire root privileges:
 
  
 
  su -  
 
  su -  
  
2. Copy 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,122: Line 1,372:
 
  # ./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  
  
{{Warning|Do not restart the server until the Pandora FMS Enteprise license key installation is complete, otherwise the server will not start and your monitoring service will be interrupted.}}
+
/etc/init.d/pandora_server restart
  
<center>
+
Then, the Enterprise Servers will be shown as enabled.
[[image:Pandora_server_view.png | 800px]]
+
 
</center>
+
{{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.}}
 +
 
 +
[[Image:Servidores Enterprise.png|center|800px]]
  
==== Installing to a different path ====
+
=== Installing on a different path ===
  
To install the Pandora FMS Server to a different path, specify it with the ''--destdir'' option:
+
To install the Pandora FMS Server on a different path, specify it with the <code>--destdir</code> option:
  
 
  ./pandora_server_installer --install --destdir <path>
 
  ./pandora_server_installer --install --destdir <path>
  
After the installation, you should manually configure your Pandora FMS 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''):
+
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>):
  
 
  ln -s <destdir>/etc/init.d/pandora_server /etc/init.d/
 
  ln -s <destdir>/etc/init.d/pandora_server /etc/init.d/
Line 1,146: Line 1,398:
 
  \"<destdir>/etc/pandora/pandora_server.conf\" >/dev/null 2>&1" > /etc/cron.hourly/pandora_db
 
  \"<destdir>/etc/pandora/pandora_server.conf\" >/dev/null 2>&1" > /etc/cron.hourly/pandora_db
  
==== Running as a non-privileged user ====
+
=== Installing with a non-privileged user ===
 
 
To make the Pandora FMS server run as a non-privileged user, install it as the user you want it to run as with the ''--no-root'' option:
 
 
 
./pandora_server_installer --install --no-root
 
 
 
==== Installing with a non-privileged user ====
 
  
''--no-root'' can be combined with ''--destdir'' to install the Pandora FMS server with an unprivileged user, as long as this user has write permissions on the path passed to ''--destdir''. For example:
+
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
 
  ./pandora_server_installer --install --no-root --destdir /opt/pandora
  
== Server and Console Installation in Windows ==
+
This user must have writing permissions on the path that is passed to <code>--destdir</code>.
 
 
From Pandora FMS versions 5.1 and above, there is a Windows installer which allows us to install: '''Nginx''', '''PHP''', '''MySQL''', '''Pandora FMS''' and some dependencies necessary for the server and console operation under Windows.
 
 
 
<br><br>
 
{{Warning|Pandora FMS Console & server setup in '''Windows''' is not recommended for production systems, due to inferior performance compared to Linux. We are working to make it more stable and faster in future versions .}}
 
<br><br>
 
{{Warning |From version 729 of Pandora FMS it is necessary to update to PHP7 for the proper functioning of the tool}}
 
 
 
Some features of the Pandora FMS server rely on a Linux-based operating system and do not work on Windows:
 
 
 
* [[Pandora:Documentation_en:Recon_Server#Recon_Scripts|Recon scripts]]
 
* [[Pandora:Documentation_en:IPAM|IPAM]]
 
* [[Pandora:Documentation_en:UX_Monitoring|UX monitoring]]
 
* [[Pandora:Documentation_en:Transactional_Monitoring|Transactional monitoring]]
 
* [[Pandora:Documentation_en:Netflow|Netflow]]
 
* [[Pandora:Documentation_en:Remote_Monitoring#Monitoring_with_Plug_Ins_.28Server_Plugin.29|Server plug-ins]]. The default plug-ins are Linux scripts. You could, however, write your own scripts for Windows.
 
* [[Pandora:Documentation_en:Virtual_environment_monitoring#VMware|VMware plug-in]]
 
* [[Pandora:Documentation_en:Inventory|Remote inventory]]
 
* [[Pandora:Documentation_en:Log_Monitoring|Log monitoring]]
 
 
 
It is delivered as an installer in executable format (. exe) and for its basic installation you
 
only have to accept all the options listed below.
 
 
 
Please select the language:
 
 
 
<center>
 
[[image:Pandora_agent_3.0_RC3_install_windows_01_eng.png]]
 
</center>
 
 
 
Please follow the installer steps:
 
 
 
<center>
 
[[image:Pandora_server_install_windows_011.png]]
 
</center>
 
 
 
Please accept the license terms:
 
 
 
<center>
 
[[image:Pandora_server_install_windows_021.png]]
 
</center>
 
 
 
Please select the components to install:
 
 
 
<center>
 
[[image:Pandora_server_install_windows_031.png]]
 
</center>
 
 
 
{{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.}}
 
 
 
{{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, although you're required to disable it in order to work through Nginx.
 
 
 
If you have a MySQL Server installed and running on the computer before installing the remaining components of Pandora FMS, you will have to modify the MySQL root password, for "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.
 
 
 
After selecting the components to install, you're required to specify the installation path:
 
 
 
 
 
<center>
 
[[image:Pandora_server_install_windows_041.png]]
 
</center>
 
 
 
The components are going to be installed. The only component which requires a user validation is Nginx. It will ask for the Pandora FMS server's name or IP address:
 
 
 
<center>
 
[[image:Pandora_server_install_windows_051.png]]
 
</center>
 
 
 
 
 
As denoted above, other components are installed besides MySQL and Nginx. In case they are already installed, you may see a message like this:
 
 
 
<center>
 
[[image:Pandora_server_install_windows_06.png]]
 
</center>
 
 
 
Please remember that Microsoft Visual C++ is required for the modules to work properly.
 
 
 
<center>
 
[[image:Pandora_server_install_windows_06_21.png]]
 
</center>
 
 
 
Nginx requires '''Microsoft Visual C++ 2012''', while if you are running a '''Windows 2008 Professional R2''' system, 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.
 
 
 
 
 
'''Microsoft Visual C++ 2008'''
 
 
 
https://www.microsoft.com/en-us/download/details.aspx?id=29
 
 
 
 
 
'''Microsoft Visual C++ 2010 SP1 Redistributable Package'''
 
 
 
https://www.microsoft.com/en-us/download/details.aspx?id=8328
 
 
 
 
 
'''Visual C++ 2012 (Update 4)'''
 
 
 
https://www.microsoft.com/en-US/download/details.aspx?id=30679
 
 
 
'''Visual C++ 2015 '''
 
 
 
https://www.microsoft.com/es-es/download/details.aspx?id=48145
 
 
 
Please wait until the files are copied and all the setup-related settings are carried out.
 
 
 
<center>
 
[[image:Pandora_server_install_windows_071.png]]
 
</center>
 
 
 
Until the installation is complete as shown below.
 
 
 
<center>
 
[[image:Pandora_server_install_windows_081.png]]
 
</center>
 
 
 
Once completed the browser on the login screen will open automatically. In case Enterprise Version is installed, 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.
 
 
 
In order to quickly start the process, please click on 'Start' and 'Programs'.
 
 
 
<center>
 
[[image:Pandora_server_install_windows_091.png]]
 
</center>
 
 
 
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.
 
 
 
 
 
<center>
 
[[image:Pandora_server_install_windows_101.png|800px]]
 
</center>
 
 
 
 
 
=== Operation WMI modules in some Windows versions ===
 
 
 
For security reasons, some Windows versions have limited users who can remotely query WMI. If these modules are not carried out, the solution is to run the service Satellite Server as an Administrator user.
 
 
 
The process to follow is:
 
 
 
Open the services:
 
 
 
<center>
 
[[File:Instalacion windows7e.png|400px]]
 
</center>
 
 
 
Right click on the service and enter in Properties
 
 
 
<center>
 
[[File:Instalacion windows8e.png|700px]]
 
</center>
 
 
 
On the Log On window, select an account with Administrator permissions and apply changes:
 
 
 
<center>
 
[[File:Instalacion windows9e.png|500px]]
 
</center>
 
 
 
And after these changes, restart the service.
 
 
 
=== Folders to consider in Windows ===
 
 
 
There are a set of directories you need to set correctly in Pandora FMS Setup, which are:
 
 
 
- Remote Config directory
 
 
 
- Attachment store
 
 
 
<center>
 
[[image:Path_windows.png|800px]]
 
</center>
 
 
 
- Server logs directory
 
 
 
<center>
 
[[image:Path_windows2.png|800px]]
 
</center>
 
 
 
- Graphviz binary directory
 
 
 
<center>
 
[[image:Path_windows3.png|800px]]
 
</center>
 
 
 
 
 
{{Warning|It has been observed that it  is necessary to install '''Microsoft Visual C++ 2008'''  in '''Windows 2008 Professional R2''' for the proper operation of Apache.}}
 
 
 
'''Microsoft Visual C++ 2008'''<br>
 
http://www.microsoft.com/es-es/download/details.aspx?id=29<br><br>
 
 
 
= Initial Configuration after Installation =
 
 
 
Post-installation order is:
 
 
 
# Create the database through the Pandora FMS web console installation wizard.
 
# Modify the server configuration including access credentials to the databases generated by the previous step.
 
#Boot the server.
 
#Start local agent (if needed).
 
#Access Pandora FMS console for the first time to start using Pandora FMS.
 
 
 
==Tuning the settings in CentOS7==
 
 
 
CentOS 7 is a good Linux distribution but it has its small details that we will try here briefly, which will make it easier to install Pandora FMS:
 
 
 
CentOS 7 doesn't install ifconfig, to install it :
 
 
 
  yum install net-tools
 
 
 
CentOS has a very aggressive firewall, and we need to disable it (later you can secure the server if needed):
 
 
 
  systemctl disable firewalld
 
  systemctl stop firewalld
 
 
 
CentOS 7 also has SELinux enabled by default, to disable it:
 
 
 
  setenforce 0
 
  sed -i 's/enforcing/disabled/g' /etc/selinux/config /etc/selinux/config
 
 
 
We program both the WEB server and the database server for booting:
 
 
 
  systemctl start httpd.service
 
  systemctl enable httpd.service
 
  systemctl enable mariadb.service
 
 
 
We remove the private tmp fromt the systemd  in Apache:
 
 
 
sed -i 's/PrivateTmp=true/PrivateTmp=false/g' /etc/systemd/system/multi-user.target.wants/httpd.service
 
 
 
== Initial Console Configuration ==
 
 
 
We're assuming all components  (Database, Console, Server and Agent) will be executed on the same machine. If you haven't done it already, start the MySQL server and create an Admin password (root).
 
 
 
/etc/init.d/mysql start
 
 
 
Or, depending on the Linux version:
 
 
 
service mariadb 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
 
 
 
Or:
 
 
 
service httpd start
 
 
 
Now it should be possible to access through the browser to the IP address of our Pandora FMS server and complete the database creation process.
 
 
 
If your server's IP is, for exmaple,  '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 following steps in order to create the Pandora FMS DB.
 
 
 
<center>
 
[[Image:Pandora_install_1.png]]
 
</center>
 
 
 
Please click on 'Next'.
 
 
 
<center>
 
[[Image:Pandora_install_2.png]]
 
</center>
 
 
 
This screen is intended to verify that all software dependencies have been properly installed.
 
 
 
Note: If you're required to install some dependencies, restart the web server in order for it to recognize them.
 
 
 
<center>
 
[[Image:Pandora_install_3.png]]
 
</center>
 
 
 
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 blank spaces in the database name.
 
 
 
<center>
 
[[Image:Pandora_install_4.png]]
 
</center>
 
 
 
Enter the password for database access here:
 
 
 
<center>
 
[[Image:Paso5.png]]
 
</center>
 
 
 
Installation complete:
 
 
 
<center>
 
[[Image:Paso6.png]]
 
</center>
 
 
 
 
 
=== 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, 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 appears:
 
 
 
<center>
 
[[Image:license_accept.png]]
 
</center>
 
 
 
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, will appear:
 
 
 
<center>
 
[[Image:license_setup.png]]
 
</center>
 
 
 
{{tip|It is very important that the pandora_server daemon is not started with the Enterprise version of the same one installed, without having enabled the Enterprise version of the console first, as errors will occur.}}
 
 
 
== 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 X.Y Build XXXX 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.
 
 
 
The Pandora Server is now running with PID 2085.
 
 
 
{{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 manually restart this service.}}
 
 
 
To boot the tentacle_server manually, you will need to type the command:
 
 
 
/etc/init.d/tentacle_serverd start
 
  
 
= Pandora FMS Agent Installation =
 
= Pandora FMS Agent Installation =
Line 1,535: Line 1,444:
 
<td>Pandora Android Agent 2.0 or above</td>
 
<td>Pandora Android Agent 2.0 or above</td>
 
<td>
 
<td>
* Android 2.2 or above
+
* Android 6 or above
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 1,553: Line 1,462:
  
 
* '''Perl 5.8''' or above
 
* '''Perl 5.8''' or above
* Optionally the package '''unzip''' installed correctly and '''accessible in the path of the user''' that will run the agent (only if you want to use the file collections).
+
* It will be necessary to install the following dependencies:
 +
perl-YAML-Tiny-1.73-2
 +
perl-Sys-Syslog
 +
unzip
 +
 
 +
== 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
 +
 
 +
== 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
  
 
== Installing the agent from tarball ==
 
== Installing the agent from tarball ==
Line 1,559: Line 1,494:
 
This agent version is ready for installation on any Unix/Linux/MAC OS system.
 
This agent version is ready for installation on any Unix/Linux/MAC OS system.
  
The agent does not require compilation or preparation, once we have the agent downloaded in. tar. gz format.
+
The agent does not require compilation nor preparation, once the agent is downloaded in. tar. gz format.
  
 
1. Acquire root privilges
 
1. Acquire root privilges
Line 1,565: Line 1,500:
 
  su -
 
  su -
  
2. Copy it to /tmp and insidee /tmp execute:
+
2. Copy it to <code>/tmp</code> and execute:
  
 
  tar xvzf pandorafms_X.Y_unix.tar.gz  
 
  tar xvzf pandorafms_X.Y_unix.tar.gz  
Line 1,571: Line 1,506:
 
  ./pandora_agent_installer --install
 
  ./pandora_agent_installer --install
  
3. Start the aagent manually:
+
3. Start the agent manually:
  
 
  /etc/init.d/pandora_agent_daemon start
 
  /etc/init.d/pandora_agent_daemon start
  
=== Custom installation ===  
+
== 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.
+
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:
 
To use that method, simply run it as the following example:
Line 1,583: Line 1,518:
 
  ./pandora_agent_installer --install /opt/pandora
 
  ./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''.
+
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 user, it would be:
+
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
 
  ./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).
+
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).
  
  
 
<br>
 
<br>
{{Warning|The user '''pandora''' is deactivated by default, you must enable it by putting a valid shell in ''/etc/passwd'' if you want to use it to run the agent with that user.}}
+
{{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.}}
 
 
{{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: csrutil disable.}}
 
 
 
===Agent installation in CentOS/RedHat ===
 
 
 
To install the software agent in CentOS/RedHat you should have downloaded the CentOS/Rehdat RPM package from our website.
 
 
 
To install it, simply run this command:
 
 
 
rpm -i pandorafms_agent-7.0NG-1.noarch.rpm
 
 
 
In case you have activated the CentOS repository, you can install the agent like this:
 
 
 
yum install pandorafms_agent
 
 
 
===Agent installation in Ubuntu/Debian ===
 
 
 
To install the software agent in Debian you should have downloaded from our website a deb package with this or similar name.
 
 
 
pandorafms_agent_unix-7.0NG-1.noarch.deb
 
 
 
To install it, simply run this command:
 
 
 
dpkg -i pandorafms_agent_unix-7.0NG-1.noarch.deb
 
 
 
If you have the Debian repository turned on, you can install the agent like this:
 
 
 
apt-get install pandorafms_agent_unix
 
 
 
===Agent installation in SUSE===
 
 
 
To install the software agent on SUSE you should have downloaded a similar RPM package from our website (maybe some version number or other details may change), but it should look like this one:
 
 
 
pandorafms_agent_unix-7.0NG-1.noarch.rpm
 
 
 
To install it, simply run this command:
 
 
 
rpm -i pandorafms_agent_unix-7.0NG-1.noarch.rpm
 
 
 
If you have the SUSE repository enabled, you can install the agent like this:
 
 
 
zypper install pandorafms_agent_unix
 
 
 
===Agent installation in NetBSD and FreeBSD ===
 
  
Pandora FMS agents file does not exist for FreeBSD and NetBSD.
+
{{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>.}}
You must install the Pandora FMS agent using the installer.
 
  
To install using the installer, read the following section carefully: "Manual installation from sources on Linux/Unix".
+
==Agent installation in NetBSD and FreeBSD ==
  
 
The file location and startup script structure are different from Linux.
 
The file location and startup script structure are different from Linux.
  
We will study the peculiarities of FreeBSD later on.
+
The particulars of FreeBSD will be discussed later on.
  
After installation, you should add the following line to /etc/rc. conf.
+
After installation, add the following line to <code>/etc/rc.conf.</code>
  
 
  pandora_agent_enable="YES"
 
  pandora_agent_enable="YES"
  
To enable the pandora agent, these settings are needed, otherwise the process cannot be started.
+
To enable the Pandora FMS agent, these settings are needed, otherwise the process cannot be started.
  
In FreeBSD, most pandora agent files are installed in /usr/local.
+
In FreeBSD, most Pandora FMS agent files are installed in <code>/usr/local</code>.
  
 
Agent:
 
Agent:
Line 1,664: Line 1,554:
 
Plugins:
 
Plugins:
 
  /usr/local/share/pandora_agent/plugins/*
 
  /usr/local/share/pandora_agent/plugins/*
Man pages:
+
'''Man''' pages:
 
  /usr/local/man/man1/*
 
  /usr/local/man/man1/*
 
Other:
 
Other:
  The data_in and log directories are the same as in Linux.
+
  The data_in and log directories are the same as those of Linux.
  
===Agent installation in Windows===
+
==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.
+
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.
  
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. In the following example shows the installation for Windows XP, remember that Pandora FMS works on any modern Microsoft platform (2000 or higher). It also has 32 and 64 bit versions.
+
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.
  
  
Line 1,683: Line 1,573:
 
</center>
 
</center>
  
Follow the steps:
+
Follow the steps of the installer:
 
<center>
 
<center>
 
[[image:Pandora_agent_3.0_RC3_install_windows_021.png]]
 
[[image:Pandora_agent_3.0_RC3_install_windows_021.png]]
 
</center>
 
</center>
Acept Terms and Conditions and click on Next:
+
Acept Terms and Conditions and click '''Next''':
  
 
<center>
 
<center>
Line 1,693: Line 1,583:
 
</center>
 
</center>
  
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..., then 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''':
  
 
<center>
 
<center>
Line 1,715: Line 1,605:
 
</center>
 
</center>
  
Decide if you want to start Pandora FMS agent service at the moment, otherwise you will have to do it manually, or it will start when Windows restarts again.
+
Start Pandora FMS agent service, otherwise you will have to do it manually, or it will start when Windows restarts again.
  
 
<center>
 
<center>
 
[[image:Pandora_agent_3.0_RC3_install_windows_081.png]]
 
[[image:Pandora_agent_3.0_RC3_install_windows_081.png]]
 
</center>
 
</center>
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.
+
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.
  
====Unattended Windows Agent Installation ====
+
===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:
 
Starting with the agent's '''VERSION 5.1''', the installer supports unattended mode. To perform the installation, simply run the following:
Line 1,728: Line 1,618:
 
  "Pandora FMS Windows Agent v7.0NG.VERSION-BUILD_ARCH.exe" /S
 
  "Pandora FMS Windows Agent v7.0NG.VERSION-BUILD_ARCH.exe" /S
  
In case we want to install the agent in a different path than the default one:  
+
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
 
  "Pandora FMS Windows Agent v7.0NG.VERSION-BUILD_ARCH.exe" /S /D=C:\Agent_Pandora
  
{{WIP}}
+
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:
  
También se pueden pasar ciertos parámetros para que se escriban en el fichero de configuración del agente. Gracias a estas opciones el despliegue de los agentes de Pandora puede ser mucho más personalizable. Las opciones por línea de comandos que se soportan son las siguientes:
+
* <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''.
  
* '''--ip''': Se corresponde con ''server_ip''.
+
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:
* '''--group''': Se corresponde con ''group''.
 
* '''--alias''': Se corresponde con ''agent_alias''.
 
 
 
Por ejemplo, si se quiere un agente que pertenezca al grupo ''Applications'', con nombre ''Mifunne'' y que apunte al servidor con la IP ''192.168.0.59'' el comando sería:
 
  
 
  "Pandora FMS Windows Agent v7.0NG.VERSION-BUILD_ARCH.exe" /S  --ip 192.168.0.59 --group Applications --alias Mifunne
 
  "Pandora FMS Windows Agent v7.0NG.VERSION-BUILD_ARCH.exe" /S  --ip 192.168.0.59 --group Applications --alias Mifunne
  
====Unattended Uninstallation====
+
===Unattended Uninstallation===
  
The uninstaller that is an executable named <code>uninstall. exe</code> that is in the Pandora FMS installation directory also allows the unattended uninstaller, to do this you must run the uninstaller with the option <code>''' /S''' </code>.
+
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>.
  
 
For example, assuming that Pandora FMS is installed in the default path:
 
For example, assuming that Pandora FMS is installed in the default path:
Line 1,752: Line 1,640:
 
  c:\program files\pandora_agent
 
  c:\program files\pandora_agent
  
We should execute:
+
You should execute:
  
 
  “c:\program files\pandora_agent\uninst.exe” /S
 
  “c:\program files\pandora_agent\uninst.exe” /S
  
==== Using PandoraAgent.exe from the command line ====
+
=== Using PandoraAgent.exe from the command line ===
  
If we run pandoraagent.exe --help, it will show us something similar to this:
+
If you run <code>pandoraagent.exe --help</code>, it will show you something similar to this:
  
  Pandora agent for Windows. Version 3.0(Build 091125)
+
C:\Program Files\pandora_agent>pandoraagent.exe --help
  Usage: PandoraAgent.exe [OPTION]
+
  Pandora agent for Windows. Version 7.0NG.752(Build 210223)
 +
  Usage: pandoraagent.exe [OPTION]
 
   
 
   
 
  Available options are:
 
  Available options are:
Line 1,770: Line 1,659:
 
         --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.
  
 +
C:\Program Files\pandora_agent>
  
To install the service (if it is not installed), simply run the following '' inside'' the directory where the executable is located (usually c:/program files or equivalent).
+
 
 +
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).
  
 
  pandoraagent.exe --install
 
  pandoraagent.exe --install
  
This will prompt the service on the machine, based on the path where the. exe is located.
+
This will prompt the service on the machine, based on the path where the <code>.exe</code> is located.
  
If we want to uninstall it, it's the same process but using:
+
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
 
  pandoraagent.exe --uninstall
  
If you want to test an ftp or ssh connection from the command line you can use the options above.
+
=== Pandora FMS Windows Agent as a process ===
 
 
==== Pandora FMS Windows Agent as a process ====
 
  
It is possible, for debugging, testing and other unusual circumstances, to execute the agent in "Process"mode. This is done by running it from the command line:
+
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
 
  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 functionalities that won't work properly.
+
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 11:22, 1 March 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

The term "Cloud provider" (or simply "Cloud") is used to describe the hosting of virtual machines, either exclusively or shared, in specialised 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.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.

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

pandora_agent_enable="YES"

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

In FreeBSD, most Pandora FMS agent files are installed in /usr/local.

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