Difference between revisions of "Pandora: Documentation en: Anexo Upgrade"

From Pandora FMS Wiki
Jump to: navigation, search
(Windows client update from installer)
("Offline" updates)
 
(14 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
[[Pandora:Documentation_en|Go back to Pandora FMS documentation index]]
 
[[Pandora:Documentation_en|Go back to Pandora FMS documentation index]]
 +
  
 
= Manual Update =
 
= Manual Update =
  
It is important to understand the basic components in which Pandora FMS is divided. Basically we can distinguish: console, server and database. In Opensource installations we will update these three components quickly, but in Enterprise installations the process will take a few more steps since the components have extended Enterprise functionalities that need to be updated separately.
+
It is important to understand the basic components in which Pandora FMS is divided. There are three main elements: console, server and database. In Opensource installations, these three components are quickly updated, but in Enterprise installations the process will take a few more steps, since the components have extended Enterprise features that need to be updated separately.
  
The breakdown of components is as follows:
+
The component breakdown is as follows:
  
 
Opensource installations:
 
Opensource installations:
Line 17: Line 18:
 
* Open Server.
 
* Open Server.
 
* Enterprise Server (extended server functions).
 
* Enterprise Server (extended server functions).
* Database (additional charts of the Enterprise version ).
+
* Database (additional charts of the Enterprise version).
  
Updates  will '''always''' include console changes, '''occasionally''' server changes, and '''rarely''' database changes. We will organize the updates into two major categories: minor version upgrades, with no database changes, and major version upgrades, with database changes.
+
Updates  will '''always''' include console changes, '''sometimes''' server changes, and '''once in a while''' database changes. Let us organize the updates into two major categories: minor version upgrades, with no database changes, and major version upgrades, with database changes.
  
 
== Update a minor version ==
 
== Update a minor version ==
  
These don't include any changes to the database, only to the console and sometimes to the server. Eg. updates 6.1 SP1 to 6.1 SP2.
+
These do not include any changes in the database, only in the console and sometimes in the server. E.g. updates 6.1 SP1 to 6.1 SP2.
  
Initial precautions/safeguards:  
+
Initial precautions:  
  
 
1. Back up the database. E.g.
 
1. Back up the database. E.g.
Line 42: Line 43:
 
5. Proceed to update.
 
5. Proceed to update.
  
=== From RPM package ===
+
=== From RPM packages ===
  
 
* Open console update:
 
* Open console update:
Line 60: Line 61:
 
  rpm -U pandorafms_server_enterprise_package.rpm
 
  rpm -U pandorafms_server_enterprise_package.rpm
  
You can find out which version you're running at any time, before or after the installation by executing the command:
+
You can find out which version you have installed at any time, before or after the installation by executing the command:
  
 
  rpm -qa | grep -i pandora
 
  rpm -qa | grep -i pandora
Line 122: Line 123:
 
=== Version 7.0NG ( Rolling Release ) ===
 
=== Version 7.0NG ( Rolling Release ) ===
  
If we decide to update manually the Pandora FMS Console in version 7.0NG, (through rpms, tarball or deb) we can find ourselves facing the need to manually apply the migration scripts between the different versions. To avoid this situation in version 7 we always recommend updating the console using Update Manager.
+
If you choose to update manually the Pandora FMS Console in version 7.0NG, (through rpms, tarball or deb) you may have to manually apply the scripts of migration between the different versions. To avoid this situation, in version 7 it is always recommended to update the console using Update Manager.
  
In case of us having an outdated database (a rare error that should not occur under normal conditions), administrator users will see a warning on the notification tab indicating this problem:
+
In case of having an outdated database (a rare error that should not take place under normal circumstances), administrator users will see a warning on the notification tab indicating this problem:
  
 
<center>
 
<center>
Line 130: Line 131:
 
</center>
 
</center>
  
To solve this problem enter the server where the Pandora FMS console is installed and go to the directory named /var/www/html/pandora_console/extras/mr. There should be another directory located labeled as 'updated'. All sqls that are already applied must be stored within the 'updated' directory, and those that are not must be stored outside. So once we apply an sql to the database, we must move them to the 'updated' directory.  
+
To solve this problem, enter the server where the Pandora FMS console is installed and go to the directory named /var/www/html/pandora_console/extras/mr. There should be another directory located within labeled as 'updated'. All sqls that are already applied must be stored within the 'updated' directory, and those that are not must be stored outside. So once an sql is applied to the database, move them to the 'updated' directory.  
Let's give the example of MR1 execution. In this case we don't have any MR applied on the database and the MR0 will appear in the footer of the Pandora FMS console. We have installed version 704 manually and we have to apply the MR1 executing the sql that we will find in /var/www/html/pandora_console/extras/mr/ called 1. sql. We'll have to execute it like this:
+
MR1 execution will serve as example. In this case, there is no MR applied on the database and the MR0 will appear in the footer of the Pandora FMS console. Version 704 has been manually installed and the MR1 must be applied executing the sql found at /var/www/html/pandora_console/extras/mr/ called 1.sql. Execute it like this:
  
 
  [[email protected] mr]# cat 1.sql | mysql -u root -p pandora
 
  [[email protected] mr]# cat 1.sql | mysql -u root -p pandora
Line 137: Line 138:
 
The MySQL user is root and the database is labeled as pandora.
 
The MySQL user is root and the database is labeled as pandora.
  
Once applied, we must update the MR value in the table tconfig of our MySQL. We'll have to execute the following command once entered MySQL:
+
Once applied, update the MR value in the tconfig table of MySQL to cange the footer value to the current one. Execute the following command once entered MySQL:
  
 
  mysql> use pandora;
 
  mysql> use pandora;
 
  mysql> update tconfig set value= XX where token='MR';
 
  mysql> update tconfig set value= XX where token='MR';
  
Once applied, the warning message will disappear from the Console and in the footer the MR1 appears as applied. The next step is to move the sql to the 'updated' file.
+
Once done, the warning message will disappear from the Console and in the footer, the MR1 will appear as applied. The next step is to move the sql to the 'updated' folder. To know which MRs should be applied, please go to the next [[Pandora:Documentation_en:Versions| link.]]
  
 
  [[email protected] mr]# mv 1.sql updated/
 
  [[email protected] mr]# mv 1.sql updated/
Line 148: Line 149:
 
== Major release update ==
 
== Major release update ==
  
Major release updates always include database changes so '''you need to update your database schema''', e. g. updates from version 6.0 to 6.1; or 6.1 to 7.0.
+
Major release updates always include database changes, so '''you need to update your database schema''', e. g. updates from version 6.0 to 6.1; or 6.1 to 7.0.
  
 
=== Database updates ("Major releases")  ===
 
=== Database updates ("Major releases")  ===
  
In order to update the database you first need to update the Open or Enterprise console, depending on your version. These updates allow the necessary sql files to be downloaded.
+
In order to update the database, first update the Open or Enterprise console, depending on your version. These updates allow the necessary sql files to be downloaded.
  
 
Once the console is up to date, the sql scripts of the database update  can be found in /extras or /enterprise (again, depending on your version) on the console. On a standard CentOS installation they can be found at:
 
Once the console is up to date, the sql scripts of the database update  can be found in /extras or /enterprise (again, depending on your version) on the console. On a standard CentOS installation they can be found at:
Line 159: Line 160:
 
  /var/www/html/pandora_console/enterprise/pandoradb_migrate_vX.Y_to_vZ.T.mysql.sql
 
  /var/www/html/pandora_console/enterprise/pandoradb_migrate_vX.Y_to_vZ.T.mysql.sql
  
Before updating it's recommendable to follow the precautions described above: make a backup of the database and the config files, and suspend the Pandora FMS server:
+
Before updating it is recommended to follow the precautions described above: back up the database and the config files, and suspend the Pandora FMS server:
  
 
  service pandora_server stop
 
  service pandora_server stop
Line 171: Line 172:
 
  mysql -u pandora -p -D pandora  
 
  mysql -u pandora -p -D pandora  
  
Execute the following from the MySQL command-line:
+
Execute the following from MySQL command-line:
  
 
  source /yourconsolepath/extras/pandoradb_migrate_X.Y_to_Z.T.mysql.sql;
 
  source /yourconsolepath/extras/pandoradb_migrate_X.Y_to_Z.T.mysql.sql;
  
* Enterprise database update:
+
{{Tip|When executing the Open version migration, the Enterprise version will also be updated.}}
  
mysql -u username -p -D databasename
+
To exit the MySQL client, execute "quit". The database is now updated to the correct version.
  
Eg.
+
In case you need to go back to a previous version, you can restore the backed up database by means of this procedure:
 
 
mysql -u pandora -p -D pandora
 
 
 
Execute the following from the MySQL command line:
 
 
 
source /yourconsolepath/enterprise/pandoradb_migrate_vX.Y_to_vZ.T.mysql.sql;
 
 
 
To exit the MySQL client execute "quit". The database is now updated to the correct version.
 
 
 
In case you need to go back to a previous version, you can restore the backed up database with:
 
  
 
  mysql -u username -p databasename
 
  mysql -u username -p databasename
Line 205: Line 196:
 
  > source backup_pandora_X.Y.sql;
 
  > source backup_pandora_X.Y.sql;
  
= Automatic update withUpdate Manager =
+
= Automatic update with Update Manager =
  
 
== OpenSource updates ==
 
== OpenSource updates ==
  
From version 4.0.2 onward, Pandora FMS (Opensource version) allows semi-automatic weekly updates, based on improvements in the Update Manager system (previously exclusive to Enterprise).  It allows an '''online''' query to be carried out, to find out if there is an update available and, if so, downloading it (with authorization) and automatically update the console.
+
From version 4.0.2 onwards, Pandora FMS (Opensource version) allows semi-automatic weekly updates, based on improvements in the Update Manager system (previously exclusive to Enterprise).  It allows an '''online''' query to be carried out, to find out if there is an update available and, if so, download it and automatically update the console.
  
 
Updates feature the following characteristics:
 
Updates feature the following characteristics:
  
 
* An outgoing Internet connection from the Pandora FMS console is necessary.
 
* An outgoing Internet connection from the Pandora FMS console is necessary.
* Update manager contacts our servers to get the latest available version (in Sourceforge). It sends statistical data on the number of agents used (the data is anonymous).  
+
* Update manager contacts our servers to find the latest version available (in Sourceforge). It sends statistical data on the number of agents used (the data is anonymous).  
* Downloads the update from Sourceforge, from the directory of weekly updates.
+
* It downloads the update from Sourceforge, from the directory of weekly updates.
* Weekly updates are not incremental, but the total content for the console, which means the download can take a while (packet size is approximately 25MB).
+
* Weekly updates are not incremental, but the total content for the console, which means the download process could take a while (packet size is approximately 25MB).
 
* Updates are automatic: they are not checked by the team, and cannot be guaranteed. However, in 99% of cases they present no issues.
 
* Updates are automatic: they are not checked by the team, and cannot be guaranteed. However, in 99% of cases they present no issues.
* Updates are '''only''' for the console, not agents or server.
+
* Updates are '''only''' for the console, not for agents or server.
  
 
=== Console update process ===
 
=== Console update process ===
  
It is fairly simple. Go to extensions -> Update manager. On the main screen you'll see if there are any updates pending or available to install, plus the latest console version. Click to install.
+
It is fairly simple. Go to extensions -> Update manager. On the main screen you will see if there are any pending or available updates, plus the latest console version. Click to install.
  
 
<center>
 
<center>
Line 234: Line 225:
 
</center>
 
</center>
  
Click Confirm to begin the installation process.
+
Click "Ok" to begin the installation process.
  
Some updates contain modifications in the database. The update process launches a dialog to inform about these changes, as in the following screenshot.
+
Some updates contain databas modifications. The update process launches a dialog to inform about these changes, as in the following screenshot.
  
 
<center>
 
<center>
Line 242: Line 233:
 
</center>
 
</center>
  
At this point there are two possibilities, either applying the changes to the database and updating the console, or rejecting the update, and leave the console and database as they are.
+
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.
  
{{tip|For Update Manager to work 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 configuration) but it is slower.}}
+
{{tip|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.}}
  
After the process, the main update page will appear with the updated console version displayed. Congratulations, you've 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!
  
 
<center>
 
<center>
Line 258: Line 249:
 
* 100% tested by our in-house development team, so you can take advantage of the latest updates (even hours after opening an incident, in some cases).
 
* 100% tested by our in-house development team, so you can take advantage of the latest updates (even hours after opening an incident, in some cases).
  
* Specific updates (incrementals) that only update out-of-date elements, without downloading heavy packages.
+
* Specific updates (incremental) that only update out-of-date elements, without downloading heavy packages.
  
* Allows "offline" updates, downloading packages from the support page, for Pandora FMS installations that don't have an Internet connection (for security reasons).
+
* It allows "offline" updates, downloading packages from the support page, for Pandora FMS installations that do not have an Internet connection (for security reasons).
  
 
=== Configuration ===
 
=== Configuration ===
  
In order to be able to use Update Manager in the Enterprise version, first you must have the Updater correctly configured , which has its own section in the menu:
+
To be able to use Update Manager in the Enterprise version, first the updater must be correctly configured, which has its own section in the menu:
  
 
<center>
 
<center>
Line 272: Line 263:
 
=== "Online" updates ===
 
=== "Online" updates ===
  
Access Update Manager from the update section. If you have the Enterprise version installed, you can use its interface (if not, the one of the Open version will appear).
+
Update Manager is available in the update section. If you have the Enterprise version installed, you may use this interface, otherwise the one to appear will be that of the Open version.
  
 
<center>
 
<center>
Line 278: Line 269:
 
</center>
 
</center>
  
From this page you can see the version of Pandora FMS you are currently using, plus any new updates available.
+
From this page, you can see the current version of Pandora FMS, plus any new updates available.
  
To update to the last version click on the link that shows the image in your Pandora FMS console.
+
To update to the last version, click on the link that shows the image in your Pandora FMS console.
  
  A dialog will appear giving with the option to continue or not.
+
  A dialog will appear giving the option to continue or not.
  
 
<center>
 
<center>
Line 288: Line 279:
 
</center>
 
</center>
  
If you click Continue, two things can happen: either the console will be updated and the process will finish; or, the update includes changes to the database and a dialog will appear asking if 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.
  
 
<center>
 
<center>
Line 294: Line 285:
 
</center>
 
</center>
  
If we decide to update it, the process will continue in a normal way, but if we 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.
Line 316: Line 307:
 
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.  
  
{{tip|The Pandora FMS Console can be updated in the same way as with the .OUMs, using zip files created by our team.}}
+
{{tip|The Pandora FMS Console can be updated in the same way as with the OUMs, using zip files created by our team.}}
 +
 
 +
{{Warning|In case of updating an installation with High Availability (HA), it will be necessary to take into account what is indicated in [[http://51.91.156.102/docs/index.php?title=Pandora:Documentation_en:HA#Update this section]].}}
  
 
== Additional PHP engine configuration for Update Manager ==
 
== Additional PHP engine configuration for Update Manager ==
Line 334: Line 327:
 
= Migrating to another system=
 
= Migrating to another system=
  
We can encounter the circumstance that we want to use a new version of Pandora in another different or newer system or distribution , for example, migrating from a SUSE 11 to a SUSE 12 or from an Ubuntu to CentOS.
+
You may want to use a new version of Pandora FMS in another different or newer system or distribution, for example, migrating from a SUSE 11 to a SUSE 12 or from an Ubuntu to CentOS.
  
For this, all we have to do is install Pandora FMS from scratch in the new system , or download the ISO that we provide and install it.
+
To do that, install Pandora FMS from scratch in the new system, or download the ISO that we provide and install it.
  
 
1. When Pandora FMS is running on the new system, back up the previous system's database:
 
1. When Pandora FMS is running on the new system, back up the previous system's database:
Line 344: Line 337:
 
2. Then, send the backup_pandora_X.Y.sql file from the oldd system to the new one.
 
2. Then, send the backup_pandora_X.Y.sql file from the oldd system to the new one.
  
3. Close all running processes except MySQL.
+
3. Close all running processes except for MySQL.
  
 
  /etc/init.d/pandora_server stop  
 
  /etc/init.d/pandora_server stop  
Line 351: Line 344:
 
  /etc/init.d/apache2 stop  o /etc/init.d/httpd stop (for apache servers, this will vary depending on the distribution you're using)
 
  /etc/init.d/apache2 stop  o /etc/init.d/httpd stop (for apache servers, this will vary depending on the distribution you're using)
  
4. Enter MySQL as root user. Access the Pandora FMS database on the new system (¨pandora¨by default) and import the database.
+
4. Enter MySQL as root user. Access the Pandora FMS database on the new system (¨pandora¨ by default) and import the database.
  
 
  #mysql -u root -p
 
  #mysql -u root -p
Line 358: Line 351:
 
  mysql>source /home/artica/backup_pandora_X.Y.sql ( this path will vary depending on the directory where the backup is stored )
 
  mysql>source /home/artica/backup_pandora_X.Y.sql ( this path will vary depending on the directory where the backup is stored )
  
5. In the case of a migration to a higher version in which the database structure changes, this would be the time to run the migration scripts as indicated in the major version update procedure.
+
5. 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.
  
6. If we've changed to a different 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, introduce these queries. In the example you can see how a migration to CentOS would look. For other distributions, just change the Apache directory path.
+
6. 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.
  
  
Line 369: Line 362:
 
  mysql>UPDATE tconfig SET value = '/var/www/html/pandora_console/include/fonts/smallfont.ttf' WHERE token LIKE 'fontpath'
 
  mysql>UPDATE tconfig SET value = '/var/www/html/pandora_console/include/fonts/smallfont.ttf' WHERE token LIKE 'fontpath'
  
Keep these paths in mind in relation to server and console configuration (config.php and pandora_server.conf)
+
Keep these paths in mind in server and console configuration files (config.php and pandora_server.conf)
 
   
 
   
7. 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, dbpass fields. If they are the same you don't need to do anything. If not, we can do one off these two things :
+
7. 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:
  
 
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.
  
b. Give the database permissions with the data from the new installation. E. g. with the following data; dbname=pandora, dbuser=pandora1 and dbpass=pandora2, like this:
+
b. Give the database permissions with the data from the new installation. E. g. with the following data; dbname=pandora, dbuser=pandora1 and dbpass=pandora2, it would be like this:
  
 
  #mysql -u root -p
 
  #mysql -u root -p
Line 381: Line 374:
 
  mysql>flush privileges;
 
  mysql>flush privileges;
  
Restart the daemons and access the Pandora FMS console, including all agents, modules, alerts, etc. already configured and, if you change the IP of the new host for the previous, all the local agents will report to the new system.
+
Restart the daemons and access Pandora FMS console, including all agents, modules, alerts, etc. already configured and, if you replace the IP of the new host by the previous one, all the local agents will report to the new system.
  
Follow the same process for theEnterprise version.
+
If it is the Enterprise version, follow the same procedure.
  
 
= Windows client update from installer =
 
= Windows client update from installer =
In the installation executable of the console and the server there is a new option that allows to update Pandora FMS if a previous version is installed in the computer.
+
In the installation executable of the console and the server, there is a new option that allows to update Pandora FMS if a previous version is installed in the computer.
  
Start the installer (. exe) as if you were going to perform an installation frorm scratch and select the language:
+
Start the installer (.exe) as if you were going to perform an installation frorm scratch and select the language:
  
 
<center>
 
<center>
Line 400: Line 393:
 
</center>
 
</center>
  
Accept the Terms and Conditions:
+
Accept the licence terms:
  
 
<center>
 
<center>
Line 406: Line 399:
 
</center>
 
</center>
  
In the Select components section, select '''only''' the option to update the version installed.
+
In the "Select components" section, select '''only''' the option to update the version installed.
  
 
<center>
 
<center>
Line 418: Line 411:
 
</center>
 
</center>
  
Start installing the components. A warning will appear reminding you that Microsoft Visual C++ is required for the modules to function correctly.
+
Start installing the components. A warning will appear reminding you that Microsoft Visual C++ is required for the modules to work properly.
 
    
 
    
 
<center>
 
<center>
Line 424: Line 417:
 
</center>
 
</center>
  
Click Finish for the installation to complete.
+
Click "Finish" for the installation to be complete.
  
 
<center>
 
<center>
Line 432: Line 425:
 
Pandora FMS is now updated and ready to use.
 
Pandora FMS is now updated and ready to use.
  
{{Tip|Following these steps the Pandora FMS code will be updated to the latest version, among which is the substitution of Apache for '''Nginx''' as web server. If you want to keep the installation with '''Apache''', update the console with OUM packets or Update Manager Online.}}
+
{{Tip|Following these steps, the Pandora FMS code will be updated to the latest version, whose new upgrades include replacing Apache by '''Nginx''' as web server. If you want to keep the installation with '''Apache''', update the console with OUM packets or Update Manager Online.}}
  
 
= Update to a previous version  =
 
= Update to a previous version  =
  
To be able to update your software to a previous version, just downgrade Pandora FMS console. As a precaution, it is recommended to do a database and Pandora FMS configuration file backup as shown previously (poner link más arriba). The Open package must always be installed first and the Enterprise version afterwards
+
To be able to update your software to a previous version, downgrade Pandora FMS console. As a precaution, it is recommended to back up the database and Pandora FMS configuration file as shown previously. The Open package must always be installed first and the Enterprise version afterwards.
  
 
==From RPM packages==
 
==From RPM packages==
  
 
* Open console update:
 
* Open console update:
  rpm -U --force pandorafms_console_package.rpm
+
  rpm -i --force pandorafms_console_package.rpm
 
* Enterprise console update:
 
* Enterprise console update:
  rpm -U --force pandorafms_console__enterprise_package.rpm
+
  rpm -i --force pandorafms_console__enterprise_package.rpm
  
 
==From DEB packages==
 
==From DEB packages==

Latest revision as of 09:20, 2 March 2020

Go back to Pandora FMS documentation index


1 Manual Update

It is important to understand the basic components in which Pandora FMS is divided. There are three main elements: console, server and database. In Opensource installations, these three components are quickly updated, but in Enterprise installations the process will take a few more steps, since the components have extended Enterprise features that need to be updated separately.

The component breakdown is as follows:

Opensource installations:

  • Web Console.
  • Server.
  • Database.

Enterprise installations:

  • Open Web Console.
  • Enterprise Web Console (extended console functions).
  • Open Server.
  • Enterprise Server (extended server functions).
  • Database (additional charts of the Enterprise version).

Updates will always include console changes, sometimes server changes, and once in a while database changes. Let us organize the updates into two major categories: minor version upgrades, with no database changes, and major version upgrades, with database changes.

1.1 Update a minor version

These do not include any changes in the database, only in the console and sometimes in the server. E.g. updates 6.1 SP1 to 6.1 SP2.

Initial precautions:

1. Back up the database. E.g.

mysqldump -u root -p pandora > backup_pandora_X.Y.sql

2. Back up the config files: pandora_server.conf, config.php, pandora_agent.conf.

3. Back up server and agent plugins, at:

/etc/pandora/plugins
pandora_console/attachment/plugin
/usr/share/pandora_server/util/plugin

4. Suspend the following services: pandora_server, tentacle_serverd, httpd, pandora_agent and mysqld.

5. Proceed to update.

1.1.1 From RPM packages

  • Open console update:
rpm -U pandorafms_console_package.rpm
  • Enterprise console update:
rpm -U pandorafms_console_enterprise_package.rpm
  • Open server update:
rpm -U pandorafms_server_package.rpm
  • Enterprise server update:
rpm -U pandorafms_server_enterprise_package.rpm

You can find out which version you have installed at any time, before or after the installation by executing the command:

rpm -qa | grep -i pandora

1.1.2 From DEB packages

  • Open console update:
dpkg -i pandorafms_console_package.deb
  • Enterprise console update:
dpkg -i pandorafms_console_enterprise_package.deb
  • Open server update:
dpkg -i pandorafms_server_package.deb
  • Enterprise server update:
tar zxvf pandorafms_server_enterprise_package.tar.gz
cd pandora_server/
./pandora_server_installer --install

Should there be any dependency problems, they can be solved directly with:

apt-get install -f

1.1.3 From Tarball / Sources

  • Open console update:
tar xvzf pandorafms_console_package.tar.gz
cd pandora_console
./pandora_console_upgrade -p /yourconsolepath
  • Enterprise console update:
tar xvzf pandorafms_console_enterprise_package.tar.gz
cd pandora_console
./pandora_console_upgrade -p /yourconsolepath
  • Open server update:
tar xvzf pandorafms_server_package.tar.gz 
cd pandora_server
./pandora_server_upgrade --upgrade
  • Enterprise server update:
tar xvzf pandorafms_server_enterprise_package.tar.gz 
cd pandora_server
./pandora_server_upgrade --upgrade
  • Agent update:
tar xvzf pandorafms_agent_package.tar.gz
cd pandora_agent
./pandora_agent_installer --force-install

1.1.4 Version 7.0NG ( Rolling Release )

If you choose to update manually the Pandora FMS Console in version 7.0NG, (through rpms, tarball or deb) you may have to manually apply the scripts of migration between the different versions. To avoid this situation, in version 7 it is always recommended to update the console using Update Manager.

In case of having an outdated database (a rare error that should not take place under normal circumstances), administrator users will see a warning on the notification tab indicating this problem:

Mr message.png

To solve this problem, enter the server where the Pandora FMS console is installed and go to the directory named /var/www/html/pandora_console/extras/mr. There should be another directory located within labeled as 'updated'. All sqls that are already applied must be stored within the 'updated' directory, and those that are not must be stored outside. So once an sql is applied to the database, move them to the 'updated' directory. MR1 execution will serve as example. In this case, there is no MR applied on the database and the MR0 will appear in the footer of the Pandora FMS console. Version 704 has been manually installed and the MR1 must be applied executing the sql found at /var/www/html/pandora_console/extras/mr/ called 1.sql. Execute it like this:

[[email protected] mr]# cat 1.sql | mysql -u root -p pandora

The MySQL user is root and the database is labeled as pandora.

Once applied, update the MR value in the tconfig table of MySQL to cange the footer value to the current one. Execute the following command once entered MySQL:

mysql> use pandora;
mysql> update tconfig set value= XX where token='MR';

Once done, the warning message will disappear from the Console and in the footer, the MR1 will appear as applied. The next step is to move the sql to the 'updated' folder. To know which MRs should be applied, please go to the next link.

[[email protected] mr]# mv 1.sql updated/

1.2 Major release update

Major release updates always include database changes, so you need to update your database schema, e. g. updates from version 6.0 to 6.1; or 6.1 to 7.0.

1.2.1 Database updates ("Major releases")

In order to update the database, first update the Open or Enterprise console, depending on your version. These updates allow the necessary sql files to be downloaded.

Once the console is up to date, the sql scripts of the database update can be found in /extras or /enterprise (again, depending on your version) on the console. On a standard CentOS installation they can be found at:

/var/www/html/pandora_console/extras/pandoradb_migrate_X.Y_to_Z.T.mysql.sql
/var/www/html/pandora_console/enterprise/pandoradb_migrate_vX.Y_to_vZ.T.mysql.sql

Before updating it is recommended to follow the precautions described above: back up the database and the config files, and suspend the Pandora FMS server:

service pandora_server stop
  • Open database update:
mysql -u username -p -D databasename

E. g.

mysql -u pandora -p -D pandora 

Execute the following from MySQL command-line:

source /yourconsolepath/extras/pandoradb_migrate_X.Y_to_Z.T.mysql.sql;

Info.png

When executing the Open version migration, the Enterprise version will also be updated.

 


To exit the MySQL client, execute "quit". The database is now updated to the correct version.

In case you need to go back to a previous version, you can restore the backed up database by means of this procedure:

mysql -u username -p databasename
> drop database databasename;
> create database newdatabasename;
> use newdatabasename;
> source backup_pandora_X.Y.sql

E. g.

mysql -u root -p pandora
> drop database pandora;
> create database pandora;
> use pandora;
> source backup_pandora_X.Y.sql;

2 Automatic update with Update Manager

2.1 OpenSource updates

From version 4.0.2 onwards, Pandora FMS (Opensource version) allows semi-automatic weekly updates, based on improvements in the Update Manager system (previously exclusive to Enterprise). It allows an online query to be carried out, to find out if there is an update available and, if so, download it and automatically update the console.

Updates feature the following characteristics:

  • An outgoing Internet connection from the Pandora FMS console is necessary.
  • Update manager contacts our servers to find the latest version available (in Sourceforge). It sends statistical data on the number of agents used (the data is anonymous).
  • It downloads the update from Sourceforge, from the directory of weekly updates.
  • Weekly updates are not incremental, but the total content for the console, which means the download process could take a while (packet size is approximately 25MB).
  • Updates are automatic: they are not checked by the team, and cannot be guaranteed. However, in 99% of cases they present no issues.
  • Updates are only for the console, not for agents or server.

2.1.1 Console update process

It is fairly simple. Go to extensions -> Update manager. On the main screen you will see if there are any pending or available updates, plus the latest console version. Click to install.

Um online open actualizar en.png

After downloading the package, a dialog will appear with the option to accept or reject the update.

Dialog um principal en.png

Click "Ok" to begin the installation process.

Some updates contain databas modifications. The update process launches a dialog to inform about these changes, as in the following screenshot.

Dialog hay un mr en.JPG

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.

Info.png

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.

 


After the process, the main update page will appear with the updated console version displayed. Congratulations, you have successfully updated your version!

Um online open finalizado.png

2.2 Enterprise updates

Unlike Open updates, these have some additional characteristics:

  • 100% tested by our in-house development team, so you can take advantage of the latest updates (even hours after opening an incident, in some cases).
  • Specific updates (incremental) that only update out-of-date elements, without downloading heavy packages.
  • It allows "offline" updates, downloading packages from the support page, for Pandora FMS installations that do not have an Internet connection (for security reasons).

2.2.1 Configuration

To be able to use Update Manager in the Enterprise version, first the updater must be correctly configured, which has its own section in the menu:

Opciones um en.png

2.2.2 "Online" updates

Update Manager is available in the update section. If you have the Enterprise version installed, you may use this interface, otherwise the one to appear will be that of the Open version.

Um online pag principal en.JPG

From this page, you can see the current version of Pandora FMS, plus any new updates available.

To update to the last version, click on the link that shows the image in your Pandora FMS console.

A dialog will appear giving the option to continue or not.
Dialog um principal en.png

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.

Dialog hay un mr en.JPG

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.

2.2.3 "Offline" updates

"Offline" Pandora FMS updates can also be downloaded, which have .OUM extensions. Go to the official Pandora FMS support page to download them.

Upload them to the console with the following control:

Um offline pag principal en.png

Once uploaded, the file will appear. We can click on it to start the update.

Um offline pag principal cargado en.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.

Info.png

The Pandora FMS Console can be updated in the same way as with the OUMs, using zip files created by our team.

 


Template warning.png

In case of updating an installation with High Availability (HA), it will be necessary to take into account what is indicated in [this section].

 


2.3 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.

The line is:

memory_limit = 256M	; Maximum amount of memory a script may consume (16MB)

Generally on Debian/Ubuntu systems, this file may be found here: /etc/php5/apache2.

http://wiki.pandorafms.com/index.php?title=Pandora:Documentation_en

3 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 SUSE 11 to a SUSE 12 or from an Ubuntu to CentOS.

To do that, install Pandora FMS from scratch in the new system, or download the ISO that we provide and install it.

1. When Pandora FMS is running on the new system, back up the previous system's database:

mysqldump -u root -p pandora > backup_pandora_X.Y.sql

2. Then, send the backup_pandora_X.Y.sql file from the oldd system to the new one.

3. Close all running processes except for MySQL.

/etc/init.d/pandora_server stop 
/etc/init.d/pandora_agent_daemon stop 
/etc/init.d/tentacle_serverd stop 
/etc/init.d/apache2 stop  o /etc/init.d/httpd stop (for apache servers, this will vary depending on the distribution you're using)

4. Enter MySQL as root user. Access the Pandora FMS database on the new system (¨pandora¨ by default) and import the database.

#mysql -u root -p
mysql>use pandora
Database changed
mysql>source /home/artica/backup_pandora_X.Y.sql ( this path will vary depending on the directory where the backup is stored )

5. 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.

6. 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.


#mysql -u root -p
mysql>use pandora
Database changed
mysql>UPDATE tconfig SET value = '/var/www/html/pandora_console/attachment' WHERE token LIKE 'attachment_store'
mysql>UPDATE tconfig SET value = '/var/www/html/pandora_console/include/fonts/smallfont.ttf' WHERE token LIKE 'fontpath'

Keep these paths in mind in server and console configuration files (config.php and pandora_server.conf)

7. 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:

a. Replace the new files with the old ones or replace the data of the new files for the old ones.

b. Give the database permissions with the data from the new installation. E. g. with the following data; dbname=pandora, dbuser=pandora1 and dbpass=pandora2, it would be like this:

#mysql -u root -p
mysql>grant all privileges on pandora.* to 'pandora1'@'localhost' identified by 'pandora2';
mysql>flush privileges;

Restart the daemons and access Pandora FMS console, including all agents, modules, alerts, etc. already configured and, if you replace the IP of the new host by the previous one, all the local agents will report to the new system.

If it is the Enterprise version, follow the same procedure.

4 Windows client update from installer

In the installation executable of the console and the server, there is a new option that allows to update Pandora FMS if a previous version is installed in the computer.

Start the installer (.exe) as if you were going to perform an installation frorm scratch and select the language:

Pandora agent 3.0 RC3 install windows 01.png

Follow the steps in the installer:

Pandora server install windows 01.png

Accept the licence terms:

Pandora server install windows 02.png

In the "Select components" section, select only the option to update the version installed.

Pandora server update windows 01.png

Select the necessary installation path and continue. The installer will ask for the IP and the name of the Pandora FMS server.

Pandora server install windows 05.png

Start installing the components. A warning will appear reminding you that Microsoft Visual C++ is required for the modules to work properly.

Pandora server install windows 06 2.png

Click "Finish" for the installation to be complete.

Pandora server install windows 08.png

Pandora FMS is now updated and ready to use.

Info.png

Following these steps, the Pandora FMS code will be updated to the latest version, whose new upgrades include replacing Apache by Nginx as web server. If you want to keep the installation with Apache, update the console with OUM packets or Update Manager Online.

 


5 Update to a previous version

To be able to update your software to a previous version, downgrade Pandora FMS console. As a precaution, it is recommended to back up the database and Pandora FMS configuration file as shown previously. The Open package must always be installed first and the Enterprise version afterwards.

5.1 From RPM packages

  • Open console update:
rpm -i --force pandorafms_console_package.rpm
  • Enterprise console update:
rpm -i --force pandorafms_console__enterprise_package.rpm

5.2 From DEB packages

  • Open console update:
dpkg –i  --force pandorafms_console_package.rpm
  • Enterprise console update:
dpkg -i --force pandorafms_console__enterprise_package.rpm

5.3 From Tarball/Sources

  • Open console update:
tar -xvzf pandorafms_console_package.tar.gz
mv –f ./pandora_console/* /yourconsolepath
  • Enterprise console update:
tar -xvzf pandorafms_console_package.tar.gz
mv -f ./enterprise /yourconsolepath