Upgrade from Centreon 21.10
This chapter describes how to upgrade your Centreon platform from version 21.10 to version 22.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 server to Oracle Linux / RHEL 8 you need to follow the migration procedure.
Prerequisitesβ
Perform a backupβ
Be sure that you have fully backed up your environment for the following servers:
- Central server
- Database server
Update to the last minor versionβ
On your 21.10 platform, replace
https://packages.centreon.com/rpm-standard
orhttps://yum.centreon.com/standard
byhttps://archives.centreon.com/standard/
in your current YUM configuration (by default,/etc/yum.repos.d/centreon.repo
).Update your Centreon 21.10 to the latest minor version.
Upgrade the Centreon Central serverβ
Update the Centreon repositoryβ
Remove the centreon.repo file:
rm /etc/yum.repos.d/centreon.repo
Run the following commands:
- Alma / RHEL / Oracle Linux 8
- CentOS 7
dnf install -y dnf-plugins-core
dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/22.10/el8/centreon-22.10.repo
yum install -y yum-utils
yum-config-manager --add-repo https://packages.centreon.com/rpm-standard/22.10/el7/centreon-22.10.repo
If you have an offline license, install the corresponding repository for the plugin packs. If you are using a Business edition, install the correct Business repository too. You can find the repositories on the support portal.
Install the MariaDB repositoryβ
cd /tmp
curl -JO https://downloads.mariadb.com/MariaDB/mariadb_repo_setup
bash ./mariadb_repo_setup
sed -ri 's/1[0-1]\.[0-9]+/10.5/' /etc/yum.repos.d/mariadb.repo
rm -f ./mariadb_repo_setup
Upgrade PHPβ
Centreon 22.10 uses PHP in version 8.1.
- RHEL 8
- Alma / Oracle Linux 8
- CentOS 7
You need to change the PHP stream from version 8.0 to 8.1 by executing the following commands and answering y to confirm:
dnf module reset php
dnf module install php:remi-8.1
You need to change the PHP stream from version 8.0 to 8.1 by executing the following commands and answering y to confirm:
dnf module reset php
dnf module install php:remi-8.1
You need to enable the php 8.1 repository
yum-config-manager --enable remi-php81
Upgrade the Centreon solutionβ
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 22.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:
- Alma / RHEL / Oracle Linux 8
- CentOS 7
yum update centreon\* php-pecl-gnupg
yum 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.
- RHEL / Oracle Linux 8
- CentOS 7
When upgrading 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 anthing 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 in account the new configuration:
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 2020-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
When upgrading 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 /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 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:
/opt/rh/httpd24/root/usr/sbin/apachectl configtest
The expected result is the following:
Syntax OK
Restart the Apache and PHP processes to take in account the new configuration:
systemctl restart php-fpm httpd24-httpd
Then check its status:
systemctl status httpd24-httpd
If everything is ok, you must have:
β httpd24-httpd.service - The Apache HTTP Server
Loaded: loaded (/usr/lib/systemd/system/httpd24-httpd.service; enabled; vendor preset: disabled)
Active: active (running) since mar. 2020-05-12 15:39:58 CEST; 25min ago
Process: 31762 ExecStop=/opt/rh/httpd24/root/usr/sbin/httpd-scl-wrapper $OPTIONS -k graceful-stop (code=exited, status=0/SUCCESS)
Main PID: 31786 (httpd)
Status: "Total requests: 850; Idle/Busy workers 50/50;Requests/sec: 0.547; Bytes served/sec: 5.1KB/sec"
CGroup: /system.slice/httpd24-httpd.service
ββ 1219 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
ββ31786 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
ββ31788 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
ββ31789 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
ββ31790 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
ββ31802 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
ββ31865 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
ββ31866 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
ββ31882 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
ββ31903 /opt/rh/httpd24/root/usr/sbin/httpd -DFOREGROUND
ββ32050 /opt/rh/httpd24/root/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β
- Alma / RHEL / Oracle Linux 8
- CentOS 7
Before starting the web upgrade process, reload the Apache server with the following command:
systemctl reload httpd
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:
As the interface layout has changed in version 22.10, you need to clear your browser cache to display the new theme.
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.
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, configuration should be deployed from the Central server.
Upgrade the Pollersβ
Update the Centreon repositoryβ
Run the following command:
- Alma / RHEL / Oracle Linux 8
- CentOS 7
dnf install -y dnf-plugins-core
dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/22.10/el8/centreon-22.10.repo
yum install -y yum-utils
yum-config-manager --add-repo https://packages.centreon.com/rpm-standard/22.10/el7/centreon-22.10.repo
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
Restart centengine:
systemctl restart centengine