From version 756 of Pandora FMS, the synchronization system for environments with centralized mode has been redesigned from scratch, making it faster and more efficient, <wrap hi>since the changes will be replicated to the nodes automatically without the need for manual synchronization that was done until now</wrap>.
+
From Pandora FMS version 756, the synchronization system for environments with centralized mode was redesigned from scratch, making it faster and more efficient, <wrap hi>since the changes will be replicated to the nodes automatically without the need for manual synchronization that was done until now</wrap>.
This change **replaces the previous system** in disuse, so that in environments where it was active, it will be necessary to go through the automatic merging system to use the new centralization system to guarantee the integrity of the data.
+
This change **replaces the previous system** in disuse, so that, in environments where it was active, it will be necessary to go through the automatic merging system to use the new centralization system to guarantee data integrity.
* 全ノードの**サーバ**は、**コマンドセンター**の API へ**接続**できる必要があります。メタコンソールで公開 URL を設定することをお勧めします。
* 全ノードの**サーバ**は、**コマンドセンター**の API へ**接続**できる必要があります。メタコンソールで公開 URL を設定することをお勧めします。
-
{{ :wiki:10_Command Center_public_url.png }}
+
{{ :wiki:10_metaconsole_public_url.png }}
* Node **servers** must have their **API configuration **correct in ''pandora_server.conf'' or their **public ****URL **configuration in the console **Setup**. If it is not configured, servers must be hosted in the same machines their consoles are in.
* Node **servers** must have their **API configuration **correct in ''pandora_server.conf'' or their **public ****URL **configuration in the console **Setup**. If it is not configured, servers must be hosted in the same machines their consoles are in.
行 292:
行 292:
* All **nodes and the Command Center **must be from the **same version**.
* All **nodes and the Command Center **must be from the **same version**.
* All **nodes and the Command Center **must be in the **same MR**.
* All **nodes and the Command Center **must be in the **same MR**.
* All **nodes and Command Center** must have the **same maximum collection size** configured in the <wrap :en>**Setup** </wrap>.
* All **nodes and Command Center** must have the **same maximum collection size** configured in the <wrap :en>**Setup** </wrap>.
* To avoid errors, the **Command Center and the nodes** must have the ''memory_limit'' parameter from ''php.ini'' to ''-1'', that is, limitless, but only for the database merging process. After finishing it, it is recommended to set it back to the previous value. That is because a lot of memory is used to merge the nodes, and in very large environments (with many different elements) a large amount of memory can be used, that way you make sure that the system can use all the memory available. If the items to be merged exceed the value of the physical memory available on the server, the Merging tool will fail due to an unexpected error, and in the console/apache logs you will see the line indicating the excess memory reached.
* To avoid errors, the **Command Center and the nodes** must have the ''memory_limit'' parameter from ''php.ini'' to ''-1'', that is, limitless, but only for the database merging process. After finishing it, it is recommended to set it back to the previous value. That is because a lot of memory is used to merge the nodes, and in very large environments (with many different elements) a large amount of memory can be used, that way you make sure that the system can use all the memory available. If the items to be merged exceed the value of the physical memory available on the server, the Merging tool will fail due to an unexpected error, and in the console/apache logs you will see the line indicating the excess memory reached.
行 306:
行 299:
* All **nodes and Command Center **must have the computer's **date and time **correctly configured (the use of NTP servers is recommended).
* All **nodes and Command Center **must have the computer's **date and time **correctly configured (the use of NTP servers is recommended).
It is important, once the database merging is done, to set again the corresponding value of ''memory_limit'' in file configuration ''php.ini''. Remember that for the change to take effect, the apache ''httpd'' service must be restarted.
+
Once the database merge is finished, the ''php.ini'' file values must be returned to their normal values, especially ''memory_limit'' to its previous value. **It is important** that whenever the ''php.ini'' file parameters are modified, the Apache ''httpd'' service and the PHP ''php-fpm'' service are **restarted** for the changes to take effect.
<WRAP center round important 60%> \\ If the source of the failure prevents the backups from being recovered, the recovering shall be performed manually. \\ </WRAP>
+
<WRAP center round important 90%>
-
<WRAP center round important 60%> \\ 障害の原因によってバックアップのリカバリが妨げられている場合、リカバリは手動で実行する必要があります。\\ </WRAP>
+
If the source of the failure prevents the backups from being recovered, the recovering shall be performed manually.
<WRAP center round important 60%> \\ Sometimes there might be unexpected failures, for example connection lost for a while between the Command Center and a node's database or the impossibility of creating a backup due to not having aenough disk space, so it is possible the error message shown will be generic. If that's the case and you need it, contact Pandora FMS support team to receive assistance. \\ </WRAP>
+
<WRAP center round important 90%>
+
+
Sometimes there might be unexpected failures, for example connection lost for a while between the Command Center and a node's database or the impossibility of creating a backup due to not having enough disk space, so it is possible the error message shown will be generic. If that's the case and you need it, contact Pandora FMS support team to receive assistance.
<WRAP center round important 60%> \\ コマンドセンターとノードのデータベース間の接続がしばらく失われたり、十分なディスク容量がないためにバックアップを作成できなかったりするなど、予期しない障害が発生する場合があります。そのため、表示されるエラーメッセージは一般的なものになる可能性があります。その場合にサポートが必要であれば、Pandora FMS サポートチームに連絡して支援を受けてください。\\ </WRAP>
* **Main database:** As events are a large volume of information that is also affected, this update process takes place in parallel with the normal operation of the already merged environment. At this point, the server and ''pandora_db'' can be started again normally, and standard users are able to access the console again. Of course, you will see in the event view the update process bar for all the events, so that for that part there might still be inconsistencies (regarding filters for example) only for the events that were there before the merge. //New events would be generated normally//. This stage and process is launched by each of the nodes, through a specific task in the console's **cron**. Due to the volume of information, it can be a heavy and time-consuming task, so as far as possible the less load the environment has at that time the better (try to launch it outside of the busiest hours on Pandora FMS).
+
* **Main database**: As events are a large volume of information that is also affected, this update process takes place in parallel with the normal operation of the already merged environment. At this point, the server and ''pandora_db'' can be started again normally, and standard users are able to access the console again. Of course, you will see in the event view the update process bar for all the events, so that for that part there might still be inconsistencies (regarding filters for example) only for the events that were there before the merge. New events would be generated normally. This stage and process is launched by each of the nodes, through a specific task in the console's **cron**. Due to the volume of information, it can be a heavy and time-consuming task, so as far as possible the less load the environment has at that time the better.
* **History database**: It would be the continuation of the previous point, updating the events in the historical database under the same characteristics already indicated.
* **History database**: It would be the continuation of the previous point, updating the events in the historical database under the same characteristics already indicated.