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.
The following tables are synchronized between the Command Center and nodes within the Merging tool (see also "[[:en:documentation:pandorafms:complex_environments_and_optimization:09_pandorafms_engineering#database_main_tables|Main database tables]]"):
+
The following [[:en:documentation:pandorafms:complex_environments_and_optimization:09_pandorafms_engineering#ks1_2|tables]] are synchronized between the Command Center and nodes within the Merging tool:
* The **Command Center** must be able to **connect** to all **databases** and all node **APIs**. Make sure that the "**Consoles setup**" configuration is correct and that the indicators are green.
* The **Command Center** must be able to **connect** to all **databases** and all node **APIs**. Make sure that the "**Consoles setup**" configuration is correct and that the indicators are green.
+
* **Node consoles** must be able to **connect** to the **Command Center database**. Usually this will not be a problem, unless you have the consoles on computers other than that of Pandora FMS servers.
+
* Make sure that the <wrap :en>**Management → Setup → Enterprise**</wrap> configuration parameters for the Command Center on the nodes is correct.
* **コマンドセンター**は、すべての**データベース**とすべてのノード API に**接続**できる必要があります。"**コンソールのセットアップ**" の設定が正しく、インジケーターが緑色であることを確認してください。
* **コマンドセンター**は、すべての**データベース**とすべてのノード API に**接続**できる必要があります。"**コンソールのセットアップ**" の設定が正しく、インジケーターが緑色であることを確認してください。
* **Node consoles** must be able to **connect** to the **Command Center database**. Usually this will not be a problem, unless you have the consoles on computers other than that of Pandora FMS servers. Make sure that the **Setup** → **Enterprise** configuration parameters for the Command Center on the nodes is correct.
* Node **servers** must have their **API configuration **correct in "**pandora_server.conf**" or their **public ****URL **configuration in the consoles **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.
* 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.
* All **nodes** must have a value for the parameter ''post_max_size'' from ''php.ini'' **higher or equal** to the value configured for the same **Command Center** parameter. This value must be at least as big as the biggest file collection size there is. It should also be taken into account that this parameter must have a value higher than or equal, both in the nodes and in the Command Center, to the value of ''upload_max_filesize''.
* All **nodes** must have a value for the parameter ''post_max_size'' from ''php.ini'' **higher or equal** to the value configured for the same **Command Center** parameter. This value must be at least as big as the biggest file collection size there is. It should also be taken into account that this parameter must have a value higher than or equal, both in the nodes and in the Command Center, to the value of ''upload_max_filesize''.
* All **nodes** must have a value for the ''upload_max_filesize'' parameter from ''php.ini'' **higher or equal** to the value configured for the same **Command Center** parameter. This value must be at least as high as the size of the biggest file collection you have.
* All **nodes** must have a value for the ''upload_max_filesize'' parameter from ''php.ini'' **higher or equal** to the value configured for the same **Command Center** parameter. This value must be at least as high as the size of the biggest file collection you have.
* All **nodes and Command Center** must have **enough space **in the disk that hosts its **directory "attachment" ** to be able to carry out **backups from the database and collections**.
* All **nodes and Command Center** must have **enough space **in the disk that hosts its **directory "attachment" ** to be able to carry out **backups from the database and collections**.
+
* 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).
+
If all those requirements are not met, nodes will not be merged and it will return an error. If you check the result errors, it will return a message with the requirements still pending.
<WRAP center round info 60%> \\ If all those requirements are not met, nodes will not be mixed and it will return an error. If you check the errors of the result, it will return a message with the requirements still pending. \\ </WRAP>
+
<WRAP center round info 90%>
-
<WRAP center round info 60%> \\ これらの要件がすべて満たされていない場合、ノードはマージされず、エラーが返されます。 エラー結果を確認すると、満たされていない条件に関するメッセージを確認できます。 \\ </WRAP>
<WRAP center round important 60%>It is important, once the database unification 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</WRAP>
+
</WRAP>
+
+
<WRAP center round important 90%>
+
+
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%>データベースのマージが完了したら、[[:ja:documentation:07_technical_annexes:14_php_7#centos1|設定ファイル]] ''php.ini'' に対応する ''memory_limit'' の値を再設定することが重要です。 変更を有効にするには、** Apache httpd サービスを再起動する必要があることに注意してください。**</WRAP>
+
<wrap #ks1_3 />
==== マージツールを起動する前の推奨事項 ====
==== マージツールを起動する前の推奨事項 ====
-
Although they are notrequisites for database unification process, it is recommended to carry out the following actions too:
+
Although they are not requisites for database unification process, it is recommended to carry out the following actions too:
データベース統合プロセスの必須条件ではありませんが、次の処理も実行することをお勧めします。
データベース統合プロセスの必須条件ではありませんが、次の処理も実行することをお勧めします。
-
* **Stop the**** pandora_server ****of all nodes and the Command Center for the whole process**. As key elements such as groups are going to be changed, their IDs can be modified, and it is not recommended to have the server process include new references to the environment while it lasts. However, the running server shouldn't be a problem in most cases.
+
* **Stop the servers of all nodes and the Command Center for the duration of the process**. As key elements such as groups are going to be changed, their IDs can be modified, and it is not recommended to have the server process include new references to the environment while it lasts. However, the running server shouldn't be a problem in most cases.
-
* **Stop the**** cron **''pandora_db'' ** p****rocess temporarily for the duration of the process**, for the same reasons as the server.
+
* **Stop the** ''pandora_db'' **process from the cron temporarily for the duration of the process**, for the same reasons as the server.
* 処理全体を通してで、すべてのノードの **pandora_server** とコマンドセンターを停止します。グループなどの重要な要素が変更されるため、それらの ID が変更されることがありあす。また、処理中は、環境にアクセスするような処理を動かすことはお勧めしません。 ただし、ほとんどの場合、実行中のサーバは問題にはなりません。
* 処理全体を通してで、すべてのノードの **pandora_server** とコマンドセンターを停止します。グループなどの重要な要素が変更されるため、それらの ID が変更されることがありあす。また、処理中は、環境にアクセスするような処理を動かすことはお勧めしません。 ただし、ほとんどの場合、実行中のサーバは問題にはなりません。
<WRAP center round important 60%> \\ When the merging process starts, both the nodes and the Command Center go into maintenance mode (not for admins). The purpose of this is the same as the recommendation to stop the servers and ''pandora_db'', to prevent a user from modifying elements during the process and for that to cause errors or inconsistencies. \\ </WRAP>
+
<WRAP center round important 90%>
-
<WRAP center round important 60%> \\ マージ処理が開始されると、ノードとコマンドセンターの両方がメンテナンスモードになります。 これの目的は、サーバーと ** pandora_db** を停止して、ユーザが処理中に要素を変更してエラーや不整合を引き起こすことを防ぐためです。 \\ </WRAP>
+
When the merging process starts, both the nodes and the Command Center go into maintenance mode (not for admins). The purpose of this is the same as the recommendation to stop the servers and ''pandora_db'', to prevent a user from modifying elements during the process and for that to cause errors or inconsistencies.
<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.