Home
Remote configuration of PFMS Servers and EndPoints
Introduction
In the Pandora FMS architecture, running on a Linux® server, the vital component with almost all the information is the MySQL database. The Pandora FMS Servers, with the data generated by themselves, or by the Agents, enter that information into said database.
The Web console is the part in charge of displaying the data and interacting with the end user. The EndPoints are applications that run on the monitored systems and collect information, which is then sent to the PFMS Servers.
The configuration file /etc/pandora/pandora_server.conf stores all the tokens of the PFMS Servers, including other features of functionalities and complementary components. In this topic, and given its importance, the management of said file is briefly described.
Remote management of PFMS Servers
Menu Management → 
Servers → Manage servers.
Since the creation of Pandora FMS, the file
/etc/pandora/pandora_server.conf
has always housed the general system configuration through value pairs (token name and its value), one for each line, and accompanied by useful comments.
As of version 752, the Advanced editor was established in the Web console, which completely shows (and allows editing) the configuration file, and the Standard editor with a user-friendly visual interface. Both options are accessed, respectively, through their respective icons:
Only for new Pandora FMS installations with version 771 and later, the remote_config token comes active by default, which means that the management of all parameters is fully delegated to the Web console (any changes through the command terminal will be discarded).
The configuration changes made and saved will be applied in moments and the PFMS Server will automatically restart, a manual restart being unnecessary.
If you have an installation prior to version 771, you can activate remote configuration without any problem and also enjoy this management facility.
Remote management of PFMS EndPoints
Menu Management → 
Resources → Manage agents.
In monitoring with EndPoints, their remote configuration comes active by default starting with version 778.
Once an EndPoint's remote configuration is activated, any changes made locally in its configuration file will be overwritten by the configuration stored in the Web console.
In this way, the remote_config token is set to 1 in the following configuration files (default locations on remote devices):
- On MS Windows®:
%ProgramFiles%\pandora_agent\pandora_agent.conf
- On Linux® systems:
/etc/pandora/pandora_agent.conf
To learn how and where the PFMS Server saves the Agent configuration corresponding to an EndPoint, see the topic “Monitoring with EndPoints”, in the respective section.
To return to local EndPoint management (and vice-versa), first you must stop its service, reset remote_config to the desired value, and start that service again.
By accessing an EndPoint's remote configuration, you will be able to edit the values of each of the tokens that dictate its operation, as well as other advanced functions.
After clicking the Update button, the changes will be sent via the Tentacle protocol and in each check execution interval, those orders will always be read (it is unnecessary to restart the EndPoint service).
