Skip to main content
Version: 21.10

Upgrade from Centreon 19.10

This chapter describes how to upgrade your Centreon platform from version 19.10 to version 21.10.

If you want to migrate your Centreon server to CentOS / Oracle Linux / RHEL 8 you need to follow the migration procedure


Perform a backup​

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

  • Central server
  • Database server

Update the RPM signing key​

For security reasons, the keys used to sign Centreon RPMs are rotated regularly. The last change occurred on October 14, 2021. When upgrading from an older version, you need to go through the key rotation procedure, to remove the old key and install the new one.

Update to the latest minor version​

Update your platform to the latest available minor version of Centreon 19.10.

Upgrade the Centreon Central server​

Since 21.04, Centreon uses MariaDB 10.5.

This upgrade process will only upgrade Centreon components first.

MariaDB will be upgraded afterwards.

Update the Centreon repository​

Run the following commands:

yum install -y

If you are using a CentOS environment, you must install the Software Collections repositories with the following command:

yum install -y centos-release-scl-rh

Upgrade PHP​

Centreon 21.10 uses PHP in version 8.0.

First, you need to install the remi repository:

yum install -y yum-utils
yum install -y
yum install -y

Then, you need to enable the php 8.0 repository

yum-config-manager --enable remi-php80

Upgrade the Centreon solution​

Please, make sure all users are logged out from the Centreon web interface before starting the upgrade procedure.

If you have installed Business extensions, update the Business repository to version 21.10. Visit the support portal to get its address.

Stop the Centreon Broker process:

systemctl stop cbd

Delete existing retention files:

rm /var/lib/centreon-broker/* -f

Clean yum cache:

yum clean all --enablerepo=*

Then upgrade all the components with the following command:

yum update centreon\*

Accept new GPG keys from the repositories as needed.

Enable and start the gorgoned service:

systemctl enable gorgoned
systemctl start gorgoned

The PHP timezone should be set. Run the command:

echo "date.timezone = Europe/Paris" >> /etc/php.d/50-centreon.ini

Replace Europe/Paris by your time zone. You can find the list of supported time zones here.

Execute the following commands:

systemctl stop rh-php72-php-fpm
systemctl disable rh-php72-php-fpm
systemctl enable php-fpm
systemctl start php-fpm

Update your customized Apache configuration​

This section only applies if you customized your Apache configuration. When upgrading your platform, the Apache configuration file is not upgraded automatically: the new configuration file brought by the rpm does not replace tha 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 /opt/rh/httpd24/root/etc/httpd/conf.d/10-centreon.conf /opt/rh/httpd24/root/etc/httpd/conf.d/10-centreon.conf.rpmnew
  • 10-centreon.conf (post upgrade): this file contains the custom configuration. It does not contain anthing new brought by version 21.10, e.g. the authentication string in the LocationMatch directive
  • 10-centreon.conf.rpmnew (post upgrade): this file is provided by the rpm; it contains the authentication string, but 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.

In particular, make sure your customized Apache configuration contains the following directive (with authentication).

<LocationMatch ^/centreon/(authentication|api/(latest|beta|v[0-9]+|v[0-9]+\.[0-9]+))/.*$>
ProxyPassMatch fcgi://$1

Additional actions​

Configure Apache API access​

If you had a custom apache configuration, upgrade process through RPM did not update it.

If you use https, you can follow this procedure

You'll then need to add API access section to your configuration file: /opt/rh/httpd24/root/etc/httpd/conf.d/10-centreon.conf

Only lines with "+" symbol must be taken into account.

+Alias /centreon/api /usr/share/centreon
Alias /centreon /usr/share/centreon/www/

+<LocationMatch ^/centreon/(?!api/latest/|api/beta/|api/v[0-9]+/|api/v[0-9]+\.[0-9]+/)(.*\.php(/.*)?)$>
+ ProxyPassMatch fcgi://$1

+<LocationMatch ^/centreon/(authentication|api/(latest|beta|v[0-9]+|v[0-9]+\.[0-9]+))/.*$>
+ ProxyPassMatch fcgi://$1

ProxyTimeout 300

<IfModule mod_security2.c>
SecRuleRemoveById 200003

<Directory "/usr/share/centreon/www">
DirectoryIndex index.php
Options Indexes
AllowOverride all
Order allow,deny
Allow from all
Require all granted
<IfModule mod_php5.c>
php_admin_value engine Off

+ FallbackResource /centreon/index

AddType text/plain hbs

+<Directory "/usr/share/centreon/api">
+ Options Indexes
+ AllowOverride all
+ Order allow,deny
+ Allow from all
+ Require all granted
+ <IfModule mod_php5.c>
+ php_admin_value engine Off
+ </IfModule>
+ AddType text/plain hbs

RedirectMatch ^/$ /centreon

Then, restart apache service :

systemctl restart httpd24-httpd

Finalizing the upgrade​

Before starting the web upgrade process, reload the Apache server with the following command:

systemctl reload httpd24-httpd

Then log on to the Centreon web interface to continue the upgrade process:

Click on Next:


Click on Next:


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


This process performs the various upgrades. Click on Next:


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


If the Centreon BAM module is installed, refer to the upgrade procedure.

Post-upgrade actions​

Upgrade extensions​

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

  • License Manager,
  • Plugin Packs Manager,
  • Auto Discovery.

Then you can upgrade all other commercial extensions.

Start the tasks manager​

Since 20.04, Centreon has changed his tasks manager from Centcore to Gorgone.

To act this change, run the following commands:

systemctl stop centcore
systemctl enable gorgoned
systemctl start gorgoned
systemctl disable centcore

Engine statistics that have been collected by Centcore will know be collected by Gorgone.

Change the rights on the statistics RRD files by running the following command:

chown -R centreon-gorgone /var/lib/centreon/nagios-perf/*

Restart monitoring processes​

Centreon Broker component has changed its configuration file format.

It now uses JSON instead of XML.

To make sure Broker and Engine's Broker module are using new configuration files, follow this steps:

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

  2. Restart both Broker and Engine on the Central server by running this command:

    systemctl restart cbd centengine

Upgrade the MariaDB server​

The MariaDB components can now be upgraded.

Refer to the official MariaDB documentation to know more about this process:

Update the Centreon repository​

This step is required ONLY when your environment features an architecture with a dedicated remote DBMS. If your environment features Centreon Central and MariaDB together on the same server, you SHOULD simply skip this step.

Run the following command on the dedicated DBMS server:

yum install -y 


The innodb_additional_mem_pool_size parameter has been removed since MariaDB 10.2, so you should remove it from file /etc/my.cnf.d/centreon.cnf

# Custom MySQL/MariaDB server configuration for Centreon

open_files_limit = 32000

key_buffer_size = 256M
sort_buffer_size = 32M
join_buffer_size = 4M
thread_cache_size = 64
read_buffer_size = 512K
read_rnd_buffer_size = 256K
max_allowed_packet = 8M

# For 4 Go Ram

# For 8 Go Ram

Upgrading MariaDB​

You have to uninstall then reinstall MariaDB to upgrade between major versions (i.e. to switch from version 10.1 to version 10.5).

  1. Stop the mariadb service:

    systemctl stop mariadb
  2. Uninstall the current version:

    rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-common
  3. Install version 10.5:

    yum install MariaDB-server-10.5\* MariaDB-client-10.5\* MariaDB-shared-10.5\* MariaDB-compat-10.5\* MariaDB-common-10.5\*
  4. Start the mariadb service:

    systemctl start mariadb
  5. Launch the MariaDB upgrade process:


    If your database is password-protected, enter:

    mysql_upgrade -u <database_admin_user> -p

    Example: if your database_admin_user is root, enter:

    mysql_upgrade -u root -p

    Refer to the official documentation for more information or if errors occur during this last step.

Enable MariaDB on startup​

Execute the following command:

systemctl enable mariadb

Upgrade the Remote Servers​

This procedure is the same than to upgrade a Centreon Central server.

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

Upgrade the Pollers​

This procedure applies to a poller that is attached to a Central server.

Update the Centreon repository​

Run the following command:

yum install -y

Upgrade the Centreon solution​

Clean yum cache:

yum clean all --enablerepo=*

Upgrade all the components with the following command:

yum update centreon\*

Accept new GPG keys from the repositories as needed.

Start and enable gorgoned:

systemctl start gorgoned
systemctl enable gorgoned

Post-upgrade actions​

Due to new configuration file format for Engine's Broker module, the configuration needs to be re-deployed.

Deploy Poller's configuration from the Centreon web UI by following this procedure, and choose Restart method for Engine process.


By default, the communication between Central and Pollers or Remote Servers will still be using SSH protocol.

Consider changing the communication protocol by following the Change communication from SSH to ZMQ procedure.

Secure your platform​

Don't forget to secure your Centreon platform following our recommendations