1. Home
  2. Knowledge Base
  3. Getting Started & How to (EN)
  4. How do I activate/stop the internal servers of Pandora FMS?

How do I activate/stop the internal servers of Pandora FMS?

To Activate/Deactivate the servers it is necessary to access to the Pandora FMS server configuration file and establish in the corresponding token of each server a 0 or a 1, where zero is deactivated and one is activated.

Here I leave a link to our updated wiki as a reference of the parameters of the configuration file.


After making some changes in the server configuration file, it is necessary to restart the process of Pandora FMS service.

A Pandora FMS server has at the same time 14 internal servers with independent tasks:

  1. Data server. It processes the information sent by the software agents. The software agents collect information locally from the systems where they are installed and build an information package in XML format. These packages in XML format are sent to the server. In the server they are received in a specific directory, the server processes all the files that arrive to this input directory and stores the information in the database.
  2. Network Server. Executes remote monitoring tasks over the network: ICMP checks (ping, latency times), TCP requests and SNMP requests. When you assign an agent to a server you are specifying the network server that will execute the checks for that agent. Therefore, it is very important that the machines running the network servers have “network visibility” to be able to execute the network monitoring tasks assigned to them. That is, if it is going to ping systems on a given network, the network server can reach that network.
  3. SNMP console. This server, called SNMP trap console, uses the standard trap collection system daemon, snmptrapd. This daemon receives SNMP traps and Pandora FMS’ SNMP console processes and stores them in the database. It also launches the alerts associated with SNMP traps that have been defined.
  4. WMI Server. WMI is a Microsoft® standard for obtaining information from the operating system and applications of Microsoft Windows® environments. Pandora FMS has a dedicated server to remotely monitor Windows systems using the WMI protocol.
  5. Recognition server. Now called Discovery server, it is used to regularly scan the network and detect new systems in operation. The discovery server can also apply a monitoring template for those recently detected systems and automatically apply the default modules defined in that template, to immediately start monitoring the new system. Using the system applications nmap, xprobe and traceroute it is also able to detect the Operating Systems and establish the network topology based on the systems it already knows.
  6. Plugins Server. It executes complex checks remotely by means of customized scripts. They can be developed in any language and integrated in Pandora FMS’s interface, being managed in a centralized way. This allows an advanced user to define his own complex tests, developed by himself, and to integrate them in the application so they can be used in a comfortable and centralized way from Pandora FMS.
  7. Prediction Server. It is a small component of Artificial Intelligence that implements a data forecast in a statistical way based on past data with a depth of up to 30 days in four time references, allowing to predict the values of a data with an interval of 10-15 minutes, and to know if a data at the present time is anomalous with respect to its history. Basically we will have to build a dynamic baseline with a weekly profile.
  8. WEB Check Server (Goliath). The WEB check server is used to make load tests. It performs complete web checks, such as the process of identifying a user, passing parameters through forms, checking contents, navigating through menus, etc. It is used for availability checks (it works, it doesn’t work) and to obtain latency times (in seconds) of complete navigation experience, including resources associated to the page (images, complete texts, etc.).
  9. Export server (Enterprise version only). Pandora FMS’s export server allows to export the data of a monitored device from one Pandora FMS’ installation to another one, and thus to have the data replicated. This is especially useful when you have a large deployment, with several Pandora FMS installations, and you want to have some critical information centralized in one.
  10. Inventory server (Enterprise version only). The inventory server obtains and visualizes system inventory information: installed software, model of hardware elements, hard disks, services running in the system, etc. You can obtain this information both remotely and locally, through the Software Agents.
  11. Event correlation server (Enterprise version only). This special server serves to run events and generate alerts, it does not execute monitoring tasks. Like the others, it can be specified in the configuration for startup or not. This server, unlike the others, does not have a thread configuration or high availability.
  12. Enterprise SNMP and ICMP network server (Enterprise version only). They are two additional servers that use advanced strategies to execute ICMP (ping) and SNMP (polling) checks, so that they produce a much higher performance than the Opensource version, and with much more delicate requirements (especially SNMP), since they work with OID’s previously validated by the open server.
  13. Satellite Server (Enterprise version only). This component is installed separately from the main Pandora FMS server. It allows to explore and detect new systems, monitor remotely with ICMP and high speed SNMP, execute remote plugins and allows the forwarding of data files from the software agents to the main server, acting as an agent proxy. It sends the monitoring data as XML through a Tentacle connection, so it does not require connection to the database.
  14. WUX Server. It is a server that, combined with the Selenium Grid, allows complex WEB transactions to be carried out in a distributed manner. It differs from simple WEB checks (Goliath) in that these transactions are executed in a real browser, and their output is captured and processed for step-by-step display, including error captures, as well as detailed statistics of all WEB requests.
Was this article helpful?

Related Articles

Need Support?

Can't find the answer you're looking for?
Contact Support

Recent Discussions