Skip to main content
Version: ⭐ 25.10

Upgrade from Centreon 24.10

This chapter describes how to upgrade your Centreon platform from version 24.10 to version 25.10.

When you upgrade your central server, make sure you also upgrade all your remote servers and your pollers.

All servers in your architecture must have the same version of Centreon.

In addition, all servers must use the same version of the BBDO protocol.

If you want to migrate your Centreon platform to another server/OS, follow the migration procedure.

If you were using MySQL 8.0, you may want to upgrade to MySQL 8.4 before the end of support for version 8.0. at the end of April 2026.

Prerequisites​

Perform a backup​

Be sure that you have fully backed up your environment for the following servers:

  • Central server
  • Database server

Upgrade the Centreon Central server​

When you run a command, check its output. If you get an error message, stop the procedure and fix the issue.

Install the new repositories​

  1. Update your Centreon 24.10 to the latest minor version.

  2. Remove the repository files:

    cd /etc/yum.repos.d/
    rm -rf centreon*

  3. Install the new repository:

    dnf install -y dnf-plugins-core
    dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo
    systemctl stop cbd
    dnf clean all --enablerepo=*

If you have an offline license, also remove the old Monitoring Connectors repository, then install the new one.

You can find the address of these repositories on the support portal.

Upgrade the Centreon solution​

  1. Make sure all users are logged out from the Centreon web interface before starting the upgrade procedure.

  2. If you have installed Business extensions, delete the configuration of the 24.10 repository:

rm /etc/yum.repos.d/centreon-business-24.10.repo

  1. Install the 25.10 Business repository: visit the support portal to get its address.

  2. If your OS is Debian and you have a customized Apache configuration, perform a backup of your configuration file (/etc/apache2/sites-available/centreon.conf).

  3. Stop the Centreon Broker process:

systemctl stop cbd
  1. Delete existing retention files:
rm /var/lib/centreon-broker/* -f
  1. Clean the cache:
dnf clean all --enablerepo=*
  1. Then upgrade all the components with the following command:
dnf update centreon\* php-pecl-gnupg

Accept new GPG keys from the repositories as needed.

Update your customized Apache configuration​

This section only applies if you customized your Apache configuration.

When you upgrade your platform, the Apache configuration file is not upgraded automatically. The new configuration file brought by the rpm does not replace the old file. You must copy the changes manually to your customized configuration file.

Run a diff between the old and the new Apache configuration files:

diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew
  • 10-centreon.conf (post upgrade): this file contains the custom configuration. It does not contain anything new brought by the upgrade.
  • 10-centreon.conf.rpmnew (post upgrade): this file is provided by the rpm; it does not contain any custom configuration.

For each difference between the files, assess whether you should copy it from 10-centreon.conf.rpmnew to 10-centreon.conf.

Check that Apache is configured properly by running the following command:

apachectl configtest

The expected result is the following:

Syntax OK

Restart the Apache and PHP processes to take the new configuration into account:

systemctl restart php-fpm httpd

Then check its status:

systemctl status httpd

If everything is ok, you should have:

● httpd.service - The Apache HTTP Server
   Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
  Drop-In: /usr/lib/systemd/system/httpd.service.d
           └─php-fpm.conf
   Active: active (running) since Tue 2024-10-27 12:49:42 GMT; 2h 35min ago
     Docs: man:httpd.service(8)
 Main PID: 1483 (httpd)
   Status: "Total requests: 446; Idle/Busy workers 100/0;Requests/sec: 0.0479; Bytes served/sec: 443 B/sec"
    Tasks: 278 (limit: 5032)
   Memory: 39.6M
   CGroup: /system.slice/httpd.service
           ├─1483 /usr/sbin/httpd -DFOREGROUND
           ├─1484 /usr/sbin/httpd -DFOREGROUND
           ├─1485 /usr/sbin/httpd -DFOREGROUND
           ├─1486 /usr/sbin/httpd -DFOREGROUND
           ├─1487 /usr/sbin/httpd -DFOREGROUND
           └─1887 /usr/sbin/httpd -DFOREGROUND

Customized Apache configuration: enable text compression​

In order to improve page loading speed, you can activate text compression on the Apache server. It requires the brotli package to work. This is optional, but it provides a better user experience.

Add the following code to your Apache configuration file, in both the <VirtualHost *:80> and <VirtualHost *:443> elements:

<IfModule mod_brotli.c>
    AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json
</IfModule>
AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json

Finalizing the upgrade​

Before starting the web upgrade process, upgrade the Centreon BAM module and reload the Apache server with the following command:

systemctl reload php-fpm httpd

Then you need to finalize the upgrade process:

  1. Log on to the Centreon web interface to continue the update process. Click Next:

image

  1. Click Next:

image

  1. The release notes describe the main changes. Click Next:

image

  1. This process performs the various upgrades. Click Next:

image

  1. Your Centreon server is now up to date. Click Finish to access the login page:

image

  1. Deploy the central's configuration from the Centreon web UI by following this procedure.

Finally, restart Broker, Engine and Gorgone on the central server by running this command:

systemctl restart cbd centengine gorgoned

Update the permissions on the centreon-broker configuration files.

usermod -a -G centreon-broker apache
usermod -a -G apache centreon-broker

Refer to the Centreon MBI and Centreon MAP dedicated procedures to update these modules.

Post-upgrade actions​

  1. Upgrade extensions. From Administration > Extensions > Manager, upgrade all extensions, starting with the following:

    • License Manager,
    • Monitoring Connector Manager,
    • Auto Discovery.

    Then you can upgrade all other commercial extensions.

  2. If you were using custom commands for a poller (on the Configuration > Pollers > Pollers page, in the Monitoring Engine Information section), be aware that a new validation regex is now applied ([a-zA-Z0-9\-\_]+): your custom commands may need to be adapted. On the central server:

    • To identify commands that must be adapted, run: 
      sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run
      ```
    • To adapt the commands automatically, run: 
      sudo -u apache php /usr/share/centreon/bin/console w:m:c
      (You can also adapt them manually.)

  3. Deploy the configuration.

  4. Restart the processes:

    systemctl restart cbd centengine centreontrapd gorgoned

Upgrade the Remote Servers​

This procedure is the same as for upgrading a Centreon Central server.

At the end of the update, the configuration should be deployed from the Central server.

Upgrade the Pollers​

Update the Centreon repository​

Run the following command:

dnf install -y dnf-plugins-core
dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/24.10/el8/centreon-24.10.repo

Upgrade the Centreon solution​

Clean the cache:

dnf clean all --enablerepo=*

Then upgrade all the components with the following command:

dnf update centreon\*

Accept new GPG keys from the repositories as needed.

Restart centreon:

systemctl restart centreon

Retrieving the decryption key​

Run the following script to enable the poller to receive and process encrypted data:

/usr/share/centreon/bin/writeEngineSecrets.sh <BASE_URL> <API_ACCOUNT> <PASSWORD>

Example:

/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password

You must use the default admin account as the <API_ACCOUNT>.

Restart centengine:

systemctl restart centengine