LTS 777 to 800 Upgrade

In this topic, the different upgrade methods and paths available to update our Pandora FMS environment from the current LTS 777.x version to the new version 800 are described.

To enjoy Pandora FMS 800 LTS, you must meet the following minimum requirements.

To upgrade our Pandora FMS, we can use different methods:

• Warp Update Offline (Recommended).
• Warp Update Online*.
• Package installation.

This is the recommended method for any environment. It is the fastest and most efficient.

Steps to follow:

Check that the minimum requirements are met.

If you are on LTS versions lower than 777.3, download from the support website the .OUM packages of the required versions. For example, if you are on version 777, download the packages package_777.1.oum, package_777.2.oum, and package_777.3.oum.

Go to the Warp Update → Options section, activate the Allow no-consecutive patches token, and click the Update button.

Once the packages are downloaded and Allow no-consecutive patches is activated, go to the Management → Warp Update → Update offline section and apply the packages one by one, in order.

In the upgrade from 777.2 to 777.3, a couple of extra steps are required:

In the Warp Update → Update offline section, when attempting to apply the OUM package 777.3, it will request a signature; click the ignore button and wait for the update to apply.

You will know if it was successful if, upon reloading, you see a slightly different screen with information like this, where you can see an authentication hash and a link to the new Warp Update:

Note: If you are not registered, it may ask you to register with an email address.

Copy the code shown in the view and go to the link indicated by the new warp update console and authenticate with that code. You will see all the available package versions.

Note: If you are on any intermediate 777.x version, you can follow these same steps to upgrade to 800. Remember to activate the Allow no-consecutive patches token in the Warp options as indicated in the 777 to 777.3 upgrade in this same guide.

Download the packages package_777.16.LTS.fms, package_800.LTS.fms, and the server package for version pandorafms_server-780NG.800.tar.gz.

Note: It is possible that, between applying patches, you may need to clear the browser cache if something is not displayed correctly, since large version jumps like 777.3 to 777.15 or to 800 contain many console changes.

From the Manage → Warp Update → Update Offline section, first apply the package_777.16.LTS.fms package and then the package_800.LTS.fms package. If everything went correctly, now apply the pandorafms_server-780NG.800.tar.gz package.

Once these steps are completed, your environment should be fully updated; you can check the version in the About button within the Manage section.

To finish updating the server, one last manual step remains; you must connect via SSH to the Pandora server terminal and perform the following steps:

Check that the server has updated correctly. To do this, run:

/opt/pandorafms/perl5/bin/perl -MNet::SSLeay /usr/bin/pandora_server

You should have version 800 and an output similar to:

If you do not get this output, wait a couple of minutes for the package to finish installing; it may take between 1 and 5 minutes.

Once you have verified you have the new server, stop the old server with the command:

systemctl stop pandora_server

Check that the server is stopped with the command:

systemctl status pandora_server

Start the server and check the status again with the commands:

systemctl start pandora_server
systemctl status pandora_server

With this, your system should be fully updated; you can check from the server list that everything is working on version 800.

Note: If you want to maintain the consecutive package restriction in the offline warp again, you must revert the change made in the warp options section and deactivate the Allow no-consecutive patches token.

This is a viable upgrade method, but when there are so many versions in between, it can be much slower and there are more variables to take into account that could fail. Even so, if you are already on a version very close to the next LTS, such as 777.15 or 785, it can be a viable upgrade option.

Note 1: If you have a Metaconsole environment, do not use this method and upgrade using the Warp Update Offline.

Note 2: If you are on a version lower than 777.3, you must upgrade at least to this version using the Offline method.

The process is very simple. Go to Management → Warp Update → Update online. The system itself should suggest that updates are available. You can update one by one by clicking Update to next version.

Or you can click Update to latest version to update in version blocks.

The update view, when receiving changes during the process, may look a bit off; if you see that it does not update for a while, you can reload the page to show the information again.

It is important to highlight that some updates are marked as mandatory and will stop the “update latest version” process, forcing us to click the button again. This behavior is intentional, so throughout the process, you may need to click the “latest” button a couple of times depending on the version you are coming from.

Once you finish, you will have a view like this:

To finish updating the server, one last manual step remains. You must connect via SSH to the Pandora server terminal and perform the following steps:

Check that the server has updated correctly, running:

/opt/pandorafms/perl5/bin/perl -MNet::SSLeay /usr/bin/pandora_server

You should have version 800 and an output similar to:

If you do not get this output, wait a couple of minutes for the package to finish installing; it may take between 1 and 5 minutes.

Once you have verified you have the new server, stop the old server with the command:

systemctl stop pandora_server

Check that the server is stopped with the command:

systemctl status pandora_server

Start the server and check the status again with the commands:

systemctl start pandora_server
systemctl status pandora_server

With this, your system should be fully updated; you can check from the server list that everything is working on version 800.

In case you have any issues with the previous methods, the alternative of manual package upgrade remains. This is a more advanced method for which you will find detailed information in the wiki to perform this procedure, as it is the same regardless of the version.

As a recommendation, if any of the previous methods failed and before trying a package upgrade, it is recommended to contact the support team to see available options or receive assistance in the upgrade process.

After upgrading, although it is not mandatory, it is recommended to upgrade from PHP 8.3 to PHP 8.4; here are the wiki links to perform this upgrade.

Rocky/RHEL 9:

PHP 8.4 Upgrade

Ubuntu 22.04:

PHP 8.4 Upgrade

←Back to Pandora FMS documentation index