Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:documentation:02_installation:02_anexo_upgrade [2021/06/14 13:04]
jimmy.olano [Migrating to another system] Boleto GitLab # 7664 ticket.
en:documentation:02_installation:02_anexo_upgrade [2021/11/05 12:05] (current)
Line 254: Line 254:
 === Console update process === === Console update process ===
  
-It is fairly simple. Go to **Update manager** -> **Update manager online**. On the main screen you will see if there are any pending or available updates, plus the latest console version.+It is fairly simple. Go to **Update manager** → **Update manager online**. On the main screen you will see if there are any pending or available updates, plus the latest console version.
  
-{{ wiki:Um_online_open_actualizar_es.png?500 }}+{{  :wiki:um_online_open_actualizar_es.png  }}
  
 If there is any update, click **Ok** to install it. After downloading the package, a dialog will appear with the option to accept or reject the update. If there is any update, click **Ok** to install it. After downloading the package, a dialog will appear with the option to accept or reject the update.
  
-{{ wiki:Dialog_um_principal_es.png?500 }}+{{  :wiki:dialog_um_principal_es.png  }}
  
 Click **Ok** to begin the installation process. Click **Ok** to begin the installation process.
Line 266: Line 266:
 Some updates contain database modifications. The update process launches a dialog to inform about these changes, as in the following screenshot: Some updates contain database modifications. The update process launches a dialog to inform about these changes, as in the following screenshot:
  
-{{ wiki:Dialog_hay_mr_es.jpg?500 }}+{{  :wiki:dialog_hay_mr_en.png  }}
  
 At this point there are two possibilities, either applying the changes to the database and updating the console, or rejecting the update, so that nor the database nor the console are updated, since some changes in the console need the according changes in the database. At this point there are two possibilities, either applying the changes to the database and updating the console, or rejecting the update, so that nor the database nor the console are updated, since some changes in the console need the according changes in the database.
  
-<WRAP center round tip 60%> +<WRAP center round tip 60%> To use Update Manager, you need an outgoing Internet connection. It uses WGET by default to download packets, you can use the CURL method (this must be changed in the Pandora FMS configuration) but it is slower. </WRAP>
-To use Update Manager, you need an outgoing Internet connection. It uses WGET by default to download packets, you can use the CURL method (this must be changed in the Pandora FMS configuration) but it is slower. +
-</WRAP>+
  
 After the process, the main update page will appear with the updated console version displayed. Congratulations, you have successfully updated your version! After the process, the main update page will appear with the updated console version displayed. Congratulations, you have successfully updated your version!
  
-{{ wiki:Um_online_open_finalizado.png?300 }}+{{  :wiki:um_online_open_finalizado.png  }} 
  
 ==== Enterprise updates ==== ==== Enterprise updates ====
Line 299: Line 298:
  
 Update Manager is available in the **Update Manager**. If you have the Enterprise version installed, you may use this interface, otherwise the one to appear will be that of the Open version. Update Manager is available in the **Update Manager**. If you have the Enterprise version installed, you may use this interface, otherwise the one to appear will be that of the Open version.
- 
-{{ wiki:Um_online_pag_principal_es.png?750 }} 
  
 From this page, you can see the current version of Pandora FMS, plus any new updates available. From this page, you can see the current version of Pandora FMS, plus any new updates available.
Line 308: Line 305:
 A dialog will appear giving the option to continue or not. A dialog will appear giving the option to continue or not.
  
-{{ wiki:Dialog_um_principal_es.png?500 }}+{{  :wiki:dialog_um_principal_es.png?500  }}
  
 If you click Continue, two things can happen: either the console will be updated and the process will finish; or, the update may include database changes and a dialog will appear asking whether you want to update the database or not. If you click Continue, two things can happen: either the console will be updated and the process will finish; or, the update may include database changes and a dialog will appear asking whether you want to update the database or not.
- 
-{{ wiki:Dialog_hay_mr_es.jpg?500 }} 
  
 If you decide to update it, the process will continue in a normal way, but if you reject it, neither the database nor the console will be updated, since some changes in the database can have critical importance in changes to the console in that same update. If you decide to update it, the process will continue in a normal way, but if you reject it, neither the database nor the console will be updated, since some changes in the database can have critical importance in changes to the console in that same update.
  
 After, the updater will appear with the current version installed on Pandora FMS. After, the updater will appear with the current version installed on Pandora FMS.
 +
  
 === Offline updates === === Offline updates ===
Line 324: Line 320:
 Upload them to the console with the following control: Upload them to the console with the following control:
  
-{{ wiki:Um_offline_pag_principal_es.png?700 }}+{{  :wiki:um_offline_pag_principal_es.png  }}
  
 Once uploaded, the file will appear. We can click on it to start the update. Once uploaded, the file will appear. We can click on it to start the update.
  
-{{ wiki:Um_offline_pag_principal_cargado_es.png?560 }}+{{  :wiki:um_offline_pag_principal_cargado_es.png  }}
  
-The update follows the same operation flow as online downloads, displaying the corresponding console and database update dialogs, if there are any changes to be applied there. +The update follows the same operation flow as online downloads, displaying the corresponding console and database update dialogs, if there are any changes to be applied there.
  
-<WRAP center round tip 60%> +<WRAP center round tip 60%> The Pandora FMS Console can be updated in the same way as with the OUMs, using zip files created by our team. </WRAP>
-The Pandora FMS Console can be updated in the same way as with the OUMs, using zip files created by our team. +
-</WRAP>+
  
-<WRAP center round important 60%> +<WRAP center round important 60%> In case of updating an installation with High Availability (HA), it will be necessary to take into account what is indicated in [[:en:documentation:05_big_environments:06_ha#update|this section]]. </WRAP>
-In case of updating an installation with High Availability (HA), it will be necessary to take into account what is indicated in [[en:documentation:05_big_environments:06_ha#update|this section]]. +
-</WRAP>+
  
  
 ==== Additional PHP engine configuration for Update Manager ==== ==== Additional PHP engine configuration for Update Manager ====
  
-For Open Update Manager to run correctly, it needs more memory than the default memory it takes. To assign more memory to the PHP run, and make the Open Update Manager work, you must edit the php. ini file and set the memory to at least 256M.+For Open Update Manager to run correctly, it needs more memory than the default memory it takes. To assign more memory to the PHP run, and make the Open Update Manager work, you must edit the php. ini file and set the memory to at least 800M.
  
-The line is: +The line is:
  
-  memory_limit = 256M ; Maximum amount of memory a script may consume (16MB)+<code> 
 +memory_limit = 800M    ; Maximum amount of memory a script may consume 
 + 
 +</code>
  
 To find out the location of the file ''php.ini'' execute: To find out the location of the file ''php.ini'' execute:
 +<code>
 +php -i | grep php.ini
 +
 +</code>
  
-  php -i grep php.ini+Also, depending on Pandora FMS version you have installed, you may get the information to update to version PHP 7 [[:en:documentation:07_technical_annexes:14_php_7|here]].
  
-Also, depending on Pandora FMS version you have installed, you may get the information to update to version PHP 7 [[en:documentation:07_technical_annexes:14_php_7|here]]. 
  
 ===== Migrating to another system ===== ===== Migrating to another system =====
  
-You may want to use a new version of Pandora FMS in another different or newer system or distribution, for example, migrating from a CentOS 6 to 8 or from RHEL to CentOS.+You may want to use a new Pandora FMS version in another different or newer system or distribution, for example, migrating from a CentOS 6 to 8 or from RHEL to CentOS.
  
 1. Back up the previous system's database: 1. Back up the previous system's database:
Line 380: Line 378:
  
 <WRAP center round tip 60%>\\ <WRAP center round tip 60%>\\
-From version NG 754 onwards, [[:en:documentation:05_big_environments:07_server_management#manual_startup:shutdown_for_pandora_fms_servers|additional options are available for manual startup and shutdown]] of High Availability (HA) environments.\\+From version NG 754 onwards, [[:en:documentation:05_big_environments:07_server_management#manual_startupshutdown_for_pandora_fms_servers|additional options are available for manual startup and shutdown]] of High Availability (HA) environments.\\
 </WRAP>\\ </WRAP>\\
-5. Stopping the Apache server will depende on the distribution used:+5. Stopping the Apache server will depend on the distribution used:
 <code> <code>
  
Line 399: Line 397:
 </code> </code>
  
-6. Enter **MySQL** as root user. Access the Pandora FMS database on the new system (¨pandora¨ by default) and import the database.+6. Enter **MySQL** as root user. Access Pandora FMS database on the new system (¨pandora¨ by default) and import the database.
 <code> <code>
  # mysql -u root -p  # mysql -u root -p
Line 410: Line 408:
 This path will vary depending on the directory where the backup is stored. This path will vary depending on the directory where the backup is stored.
  
-7. In case of a migration to a higher version, where the database structure changes, this would be the time to run the migration scripts as indicated in the major version update procedure.+7. In case of migrating to a higher version, where the database structure changes, this would be the time to run the migration scripts as indicated in the major version update procedure.
  
-8. If you have changed the distribution, keep in mind the console ''PATH'' has also changed and some database fields will be different, such as **tconfig** ''attachment_store'' and ''fontpath''. To modify these fields, enter these queries. In the example you can see what a migration to CentOS would look like. For other distributions, change the Apache directory ''path''.+8. If you changed the distribution, keep in mind the console ''PATH'' also changed and some database fields will be different, such as **tconfig** ''attachment_store'' and ''fontpath''. To modify these fields, enter these queries. In the example you can see what a migration to CentOS would look like. For other distributions, change the Apache directory ''path''.
 <code> <code>
  #mysql -u root -p  #mysql -u root -p
Line 424: Line 422:
 Keep these ''PATHS'' in mind in server and console configuration files (''config.php'' and ''pandora_server.conf'') Keep these ''PATHS'' in mind in server and console configuration files (''config.php'' and ''pandora_server.conf'')
  
-9. Once the database is migrated, check that the previous ''…/pandora_console/include/config.php'' and ''/etc/pandora/pandora_server.conf'' files and the new ones contain the same data in the ''dbname'', ''dbuser'' and ''dbpass'' fields. If they are the same ther is no need to do anything. If not, do one of these two things:+9. Once the database is migrated, check that the previous ''…/pandora_console/include/config.php'' and ''/etc/pandora/pandora_server.conf'' files and the new ones contain the same data in the ''dbname'', ''dbuser'' and ''dbpass'' fields. If they are the same there is no need to do anything. If not, do one of these two things:
  
 a. Replace the new files with the old ones or replace the data of the new files for the old ones. a. Replace the new files with the old ones or replace the data of the new files for the old ones.
ºº