Upgrade the extension

If one of your servers runs an operating system that is no longer supported, you cannot upgrade MBI directly. First migrate your platform to a supported operating system:

• For the central server, see our introduction to the migration process.
• For the MBI server, see Migrating the extension.

When updating from version < 18.10 to a version >= 18.10, you need to:

• Retrieve a new license from Centreon support
• Make sure your Centreon MBI server is based on a supported OS. You may use the following procedure to migrate your server: Migrate your reporting server

The upgrade of Centreon MBI consists of four steps:

• Updating the repository
• Updating the extension interface
• Updating the reporting server
• Updating the MariaDB database

Prerequisites

Upgrade your central server

See Introduction to upgrade.

Step 1: Update the repository

When you upgrade from a previous major version to 26.10.x, you first need to update the repository on your Central & Reporting servers.

You will find the new "Business" repository on the "Repositories" page in your Centreon Support account.

On the reporting server, you also need to install the 26.10 standard repository:

Alma / RHEL / Oracle Linux 9

dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
dnf clean all
dnf update -y centreon-bi\* centreon-perl-libs-common

Step 2: Upgrade the extension interface

1. Update the package, run the following commands:

dnf clean all
dnf update centreon-bi-server

2. Update through the interface: Log on to the Centreon web interface, go to Administration > Extension > Manager and click the Update button to update the extension and the widgets.

Step 3: Upgrade the reporting server

Java version requirement

Version 26.10 requires Java 25. When upgrading the MBI packages, java (OpenJDK 25) is automatically installed as a dependency, if needed. The cbis service always uses /usr/lib/jvm/java-25-openjdk on Alma / RHEL / Oracle Linux and /usr/lib/jvm/java-25-openjdk-amd64 on Debian 13. Once the upgrade is complete, you can remove the Java 17 packages left over from version 25.10, if no other application on the server uses them.

Upgrade procedure

Now you can start the upgrade process:

1. Connect to your reporting server and stop the scheduler service (CBIS):

   systemctl stop cbis

2. Then run the following commands:

dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
dnf clean all
dnf update -y centreon-bi\* centreon-perl-libs-common

3. Start the scheduler service:

   systemctl start cbis

4. Start and enable gorgoned:

   systemctl start gorgoned && systemctl enable gorgoned

Step 4: Upgrade the database

1. Stop the cbis service:

   systemctl stop cbis

2. See Upgrading MariaDB or Upgrade MySQL.

3. Check that MariaDB is running:

   systemctl is-active mariadb

The command must return active.

4. Start the cbis service:

   systemctl start cbis