If for any reason the update through Update Manager Online fails, we have several options to update.
Update using the Update Manager Offline.
First we must know the current version, to know this data we can look at the footer of the Pandora FMS console, where it will indicate the current version, for example: PandoraFMS v7.0NG.750 - Build 750 - MR 42
When we know which version we are in, we will have to download the .oum packages from the support website for the versions we need up to the required version. See an example:
If you have version 749 and want to upgrade to version 751, you will need to download the .oum file for version 750 and the .oum file for version 751.
Once we have the .oum files downloaded we will have to insert them into the console one by one and in ascending order (first 750 and then 751).
Important: This update method only updates the Pandora FMS console, so the server will have to update it independently.
Updating by means of packages.
The update by packages is simple. You only need to know the operating system of our server and download the appropriate packages for the installation.
We will need a total of 4 packages, 2 Opensource and 2 Enterprise, the Opensource packages will have to be downloaded from our Firefly website and the Enterprise packages from our support website.
In our example case we will need the following packages (being our Pandora FMS server a CentOS 7 64bits):
Opensource --> pandorafms_console-7.0NG.751-1.noarch.rpm Opensource --> pandorafms_server-7.0NG.751-1.noarch.rpm Enterprise --> pandorafms_console_enterprise-7.0NG.751.noarch.rpm Enterprise --> pandorafms_server_enterprise_7.0NG.751_x86_64.el7.tar.gz
Once we have the packages, we will have to insert them in the server and install them, take into account that the installation has to be in the following order: 1º Opensource packages, 2º Enterprise packages.
Installation of the packages:
To install RPM packages:
[root@PandoraFMS ~]# rpm -U --force <package_name>.rpm [root@PandoraFMS ~]# rpm -U --force --nodeps <package_name>.rpm #(in case of missing dependencies)
To install .tar.gz packages:
[root@PandoraFMS ~]# tar -zxvf <package_name>.tar.gz [root@PandoraFMS ~]# cd pandora_server/ root@PandoraFMS pandora_server]# ./<package_installation> --install [root@PandoraFMS pandora_server]# /etc/init.d/pandora_server restart
Once all the packages have been installed, we will have to make changes in the database so that the update is correct:
We move to the directory /var/www/html/pandora_console/extras/mr/
[root@PandoraFMS pandora_server]# cd /var/www/html/pandora_console/extras/mr/
Now we connect to MySQL.
[root@PandoraFMS mr]# mysql -u pandora -p pandora
Once inside the MySQL shell we will have to insert the MRs in order from the version to the one we want to update to, for example, if we are in version 749 we would need to apply MR 42 (from version 750) and MR 43 (from version 751). See Pandora FMS versioning table:
https://pandorafms.com/manual/en/documentation/08_technical_reference/10_versions
Knowing the MR to apply, we execute the following:
mysql> source 42.sql; mysql> source 43.sql;
Once the MR are applied, we should do a last step to update the database, change the footer of the console, for it we will only have to execute 2 queries, one to change the MR and another to change the version, the queries are the following ones:
mysql> update tconfig set value=43 where token='MR'; mysql> update tconfig set value ='751' where token = 'current_package_enterprise';
With these steps we would already have the Pandora FMS console and server updated to version 751.