From 2c139fcf86980693b62ee2b50040a77c77fceadc Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 3 Jul 2026 18:45:41 +0200 Subject: [PATCH 001/179] 26.10 - Install/upgrade/migrate --- .../version-26.10/api/rest-api-v2.md | 8 ++--- .../developer-gorgone-rebound-mode.md | 6 ++-- .../developer/developer-module.md | 2 +- .../installation/compatibility.md | 15 +++++---- .../unattended.md | 6 ++-- .../using-packages.md | 6 ++-- .../installation-of-a-poller/unattended.md | 4 +-- .../using-packages.md | 8 ++--- .../unattended.md | 6 ++-- .../using-packages.md | 8 ++--- .../version-26.10/installation/offline.md | 4 +-- .../version-26.10/installation/technical.md | 2 +- .../version-26.10/migrate/migrate-from-3-4.md | 14 ++++----- .../migrate/migrate-from-debian-to-debian.md | 4 +-- .../migrate/migrate-from-el-to-debian.md | 4 +-- .../migrate/migrate-from-el-to-el.md | 4 +-- .../basic-objects/contacts-create.md | 2 +- .../version-26.10/releases/lifecycle.md | 1 + .../version-26.10/service-mapping/install.md | 2 +- .../update/update-centreon-platform.md | 16 +++++----- .../version-26.10/upgrade/introduction.md | 4 +-- .../upgrade/upgrade-from-20-10.md | 18 +++++------ .../upgrade/upgrade-from-21-04.md | 12 +++---- .../upgrade/upgrade-from-21-10.md | 14 ++++----- .../upgrade/upgrade-from-22-04.md | 24 +++++++------- .../upgrade/upgrade-from-22-10.md | 4 +-- .../upgrade/upgrade-from-25-10.md | 28 ++++++++--------- .../version-26.10/upgrade/upgrade-mariadb.md | 31 ++++++++++--------- .../version-26.10/upgrade/upgrade-mysql.md | 9 +++--- 29 files changed, 132 insertions(+), 134 deletions(-) diff --git a/versioned_docs/version-26.10/api/rest-api-v2.md b/versioned_docs/version-26.10/api/rest-api-v2.md index f05f687152a5..ac76e3d7b23d 100644 --- a/versioned_docs/version-26.10/api/rest-api-v2.md +++ b/versioned_docs/version-26.10/api/rest-api-v2.md @@ -3,7 +3,7 @@ id: rest-api-v2 title: Using the v2 API with Postman --- -This page describes how to use [the v2 API](https://docs-api.centreon.com/api/centreon-web/25.10/) for Centreon Web with Postman. +This page describes how to use [the v2 API](https://docs-api.centreon.com/api/centreon-web/26.10/) for Centreon Web with Postman. ## Create a Postman collection from the OpenAPI definition @@ -59,7 +59,7 @@ Then click **Add**, and select it in the environments list. > ![image](../assets/api/postman-collection-edit.png) > > In the **Variables** tab, change the *version* value to either -> "latest" or your `v.` version number, e.g. "v25.10". +> "latest" or your `v.` version number, e.g. "v26.10". > > You can obtain your "major.minor" version number using the following command: > `curl -s http://127.0.0.1:80/centreon/api/latest/platform/versions | jq '.web '` @@ -67,8 +67,8 @@ Then click **Add**, and select it in the environments list. > Here is an example of output for this command: > > \{ -> "version": "25.10.1", -> "major": "24", +> "version": "26.10.1", +> "major": "26", > "minor": "10", > "fix": "1" > \} diff --git a/versioned_docs/version-26.10/developer/developer-gorgone-rebound-mode.md b/versioned_docs/version-26.10/developer/developer-gorgone-rebound-mode.md index fa1a3a5458f5..bdbb75ab7876 100644 --- a/versioned_docs/version-26.10/developer/developer-gorgone-rebound-mode.md +++ b/versioned_docs/version-26.10/developer/developer-gorgone-rebound-mode.md @@ -74,7 +74,7 @@ Then install the Gorgone daemon using the following commands: ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo dnf clean all --enablerepo=* dnf update dnf install centreon-gorgone @@ -85,7 +85,7 @@ dnf install centreon-gorgone ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update dnf install centreon-gorgone @@ -97,7 +97,7 @@ dnf install centreon-gorgone To install the Centreon repository, execute the following command: ```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` diff --git a/versioned_docs/version-26.10/developer/developer-module.md b/versioned_docs/version-26.10/developer/developer-module.md index c5e143e52a50..6e7a6ed19387 100644 --- a/versioned_docs/version-26.10/developer/developer-module.md +++ b/versioned_docs/version-26.10/developer/developer-module.md @@ -31,7 +31,7 @@ $module_conf['dummy'] = [ // Full module's name 'rname' => 'Dummy Example Module', // Module's version - 'mod_release' => '25.10', + 'mod_release' => '26.10', // Additional information 'infos' => 'This module is a skeleton', // Allow your module to be uninstalled diff --git a/versioned_docs/version-26.10/installation/compatibility.md b/versioned_docs/version-26.10/installation/compatibility.md index fa844a94b2dc..125b67696d10 100644 --- a/versioned_docs/version-26.10/installation/compatibility.md +++ b/versioned_docs/version-26.10/installation/compatibility.md @@ -24,12 +24,11 @@ Your screen resolution must be at least 1280 x 768. Centreon supports the following operating systems: -| Version | Installation mode | -|--------------------------------|--------------------------------------------------------| -| RHEL/Oracle Linux 8 | RPM packages, sources | -| Alma Linux 8 | RPM packages, virtual machine, sources | -| RHEL/Oracle Linux/Alma Linux 9 | RPM packages, sources | -| Debian 12 (bookworm) | DEB packages | +| Version | Installation mode | +|---------------------------------|--------------------------------------------------------| +| RHEL/Oracle Linux/Alma Linux 9 | RPM packages, sources | +| RHEL/Oracle Linux/Alma Linux 10 | RPM packages, sources | +| Debian 13 (trixie) | DEB packages | See our knowledge base article [How to install Linux to host Centreon software](https://thewatch.centreon.com/product-how-to-21/how-to-install-linux-to-host-centreon-software-3759). @@ -43,8 +42,8 @@ Bear in mind that IT Edition and Business Edition modules do not work yet on uns | Software | Version | |----------|---------| -| MariaDB | 10.11.x | -| MySQL |
  • 8.4 (recommended)
  • 8.0 until its end of support (April 2026)
| +| MariaDB | 11.8 | +| MySQL | 8.4 | > You can use another DBMS based on MySQL, but it will only be supported by the community. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md index 9a15388e378a..cbb9ac1266c2 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md @@ -59,7 +59,7 @@ apt update && apt upgrade 2. Download the script using the following command: ```shell -curl -L https://download.centreon.com/25.10/unattended.sh --output /tmp/unattended.sh +curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh ``` 3. Run the following command as **root**: @@ -67,13 +67,13 @@ curl -L https://download.centreon.com/25.10/unattended.sh --output /tmp/unattend * To specify the password for the default **admin** account: ```shell -bash /tmp/unattended.sh install -t central -v 25.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` * To get an autogenerated password for the default **admin** account (the script will tell you where the password is stored): ```shell -bash /tmp/unattended.sh install -t central -v 25.10 -r stable -s -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` In both cases, you will get a full log file with all errors in your **tmp** folder, named **unattended(date).log**. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index 2c35a7dd5db0..4885c378d04f 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -345,7 +345,7 @@ Install the Centreon repository using this command: ```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -354,7 +354,7 @@ dnf update ```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -365,7 +365,7 @@ dnf update To install the Centreon repository, execute the following command: ```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md index a5ec20f85c93..64c90fee067e 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md @@ -59,13 +59,13 @@ apt update && apt upgrade 2. Download the script using the following command: ```shell -curl -L https://download.centreon.com/25.10/unattended.sh --output /tmp/unattended.sh +curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh ``` 3. Run the following command as **root**: ```shell -bash /tmp/unattended.sh install -t poller -v 25.10 -r stable -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash /tmp/unattended.sh install -t poller -v 26.10 -r stable -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` You will get a full log file with all errors in your **tmp** folder, named **unattended(date).log**. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-packages.md index 2eebdeb1e231..79f74581b9ec 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-packages.md @@ -298,7 +298,7 @@ Install the Centreon repository using this command: ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -308,7 +308,7 @@ dnf update ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -319,7 +319,7 @@ dnf update To install the Centreon repository, execute the following command line: ```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -469,7 +469,7 @@ Couldn't connect to 192.168.0.1:444; Connection refused 2023-05-20T10:42:23+02:00 [ERROR]: No route found for “POST /centreon/api/latest/platform/topology” ``` -> Your Centreon target version is invalid. It should be greater than or equal to 25.10. +> Your Centreon target version is invalid. It should be greater than or equal to 26.10. ## Step 4: Add the Poller to the configuration diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md index ec02120e7a1c..351d7184919c 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md @@ -59,7 +59,7 @@ apt update && apt upgrade 2. Download the script using the following command: ```shell -curl -L https://download.centreon.com/25.10/unattended.sh --output /tmp/unattended.sh +curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh ``` 3. Run the following command as **root**: @@ -67,13 +67,13 @@ curl -L https://download.centreon.com/25.10/unattended.sh --output /tmp/unattend * To specify the password for the default **admin** account: ```shell -bash /tmp/unattended.sh install -t central -v 25.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` * To get an autogenerated password for the default **admin** account (the script will tell you where the password is stored): ```shell -bash /tmp/unattended.sh install -t central -v 25.10 -r stable -s -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` In both cases, you will get a full log file with all errors in your **tmp** folder, named **unattended(date).log**. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md index d3244b11487b..067eab19289b 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md @@ -344,7 +344,7 @@ Install the Centreon repository using this command: ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -354,7 +354,7 @@ dnf update ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -365,7 +365,7 @@ dnf update To install the Centreon repository, execute the following command: ```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -632,7 +632,7 @@ Couldn't connect to 192.168.0.1:444; Connection refused 2020-10-20T10:42:23+02:00 [ERROR]: No route found for “POST /centreon/api/latest/platform/topology” ``` -> Your Centreon target version is invalid. It should be greater than or equal to 25.10. +> Your Centreon target version is invalid. It should be greater than or equal to 26.10. ## Step 6: Extend local DBMS rights diff --git a/versioned_docs/version-26.10/installation/offline.md b/versioned_docs/version-26.10/installation/offline.md index f10663bcb1f9..62dc0098b729 100644 --- a/versioned_docs/version-26.10/installation/offline.md +++ b/versioned_docs/version-26.10/installation/offline.md @@ -16,7 +16,7 @@ To be able to install Centreon on servers with no internet access, create a loca ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -32,7 +32,7 @@ rpm --import https://yum-gpg.centreon.com/RPM-GPG-KEY-CES ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` diff --git a/versioned_docs/version-26.10/installation/technical.md b/versioned_docs/version-26.10/installation/technical.md index 88a09cccf263..1abcc70f0ef1 100644 --- a/versioned_docs/version-26.10/installation/technical.md +++ b/versioned_docs/version-26.10/installation/technical.md @@ -203,7 +203,7 @@ For your information, the following table describes the software dependencies. E | GnuTLS | \>= 2.0 | | Net-SNMP | 5.7 | | openssl | \>= 1.0.1k | -| PHP | 8.2 | +| PHP | 8.4 | | RRDtools | 1.4.7 | | zlib | 1.2.3 | diff --git a/versioned_docs/version-26.10/migrate/migrate-from-3-4.md b/versioned_docs/version-26.10/migrate/migrate-from-3-4.md index 99814822e46c..769d582306a2 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-3-4.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-3-4.md @@ -104,7 +104,7 @@ rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/c service mysqld stop ``` -3. Export the dumps to the new Centreon 25.10 database server (make sure you +3. Export the dumps to the new Centreon 26.10 database server (make sure you have enough space for large databases dumps): ```shell @@ -112,7 +112,7 @@ have enough space for large databases dumps): rsync -avz /tmp/centreon_storage.sql root@:/tmp/ ``` -4. On the Centreon 25.10 database server, drop the original databases and +4. On the Centreon 26.10 database server, drop the original databases and create them again: ```shell @@ -170,7 +170,7 @@ installation. The main directories to synchronize are: > To run the plugins, you must first install the required dependencies. > If you still have remote Centreon Engine 1.8.1 Pollers whose -> upgrade to 25.10 you want to postpone, be aware that Centreon Web 25.10 resource +> upgrade to 26.10 you want to postpone, be aware that Centreon Web 26.10 resource > $USER1$ now points to /usr/lib64/nagios/plugins > > This is how to mitigate the issue on the 1.8.1 Pollers: @@ -204,17 +204,17 @@ The credentials of the newly created **centreon-gorgone** user need to be update ``` You can now push the poller's configuration from Centreon 25.10 whether the remote -Poller is Centreon Engine 25.10 or 1.8.1. +Poller is Centreon Engine 26.10 or 1.8.1. ### Upgrade Centreon On the new server, force the update by moving the contents of the -**/var/lib/centreon/installs/install-25.10.0-YYYYMMDD\_HHMMSS** directory to +**/var/lib/centreon/installs/install-26.10.0-YYYYMMDD\_HHMMSS** directory to the **/usr/share/centreon/www/install** directory: ```shell cd /var/lib/centreon/installs/ -mv install-25.10.0-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ +mv install-26.10.0-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ ``` > If you use the same IP address or same DNS name for the old Centreon webserver @@ -244,7 +244,7 @@ configuration of all your pollers and export it. ### Upgrade the modules Please refer to the documentation of each module to verify compatibility with -Centreon 25.10 and perform the upgrade. +Centreon 26.10 and perform the upgrade. ### Migrate your other servers diff --git a/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md b/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md index 9fe68598d801..89e7dea0b0d6 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md @@ -176,12 +176,12 @@ If you are using custom plugins, synchronize the directories that contain your c ### Step 5: Upgrade Centreon 1. On the new server, force the update by moving the contents of the -**/var/lib/centreon/installs/install-25.10.x-YYYYMMDD\_HHMMSS** directory to +**/var/lib/centreon/installs/install-26.10.x-YYYYMMDD\_HHMMSS** directory to the **/usr/share/centreon/www/install** directory (**x** is the target version number for your migrated machine): ```shell cd /var/lib/centreon/installs/ - mv install-25.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ + mv install-26.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ ``` 2. If you use the same IP address or same DNS name on the old Centreon webserver and the new one, do a full cache cleanup of your browser to avoid JS issues. diff --git a/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md b/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md index 8b7ac231407f..270cdfb227ca 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md @@ -179,12 +179,12 @@ If you are using custom plugins, synchronize the directories that contain your c ### Step 5: Upgrade Centreon 1. On the new server, force the update by moving the contents of the -**/var/lib/centreon/installs/install-25.10.x-YYYYMMDD\_HHMMSS** directory to +**/var/lib/centreon/installs/install-26.10.x-YYYYMMDD\_HHMMSS** directory to the **/usr/share/centreon/www/install** directory (**x** is the target version number for your migrated machine): ```shell cd /var/lib/centreon/installs/ - mv install-25.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ + mv install-26.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ ``` 2. If you use the same IP address or same DNS name on the old Centreon webserver and the new one, do a full cache cleanup of your browser to avoid JS issues. diff --git a/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md b/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md index c9900b0126c5..fd9b13502855 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md @@ -199,12 +199,12 @@ rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/c ### Step 5: Upgrade Centreon 1. On the new server, force the update by moving the contents of the -**/var/lib/centreon/installs/install-25.10.x-YYYYMMDD\_HHMMSS** directory to +**/var/lib/centreon/installs/install-26.10.x-YYYYMMDD\_HHMMSS** directory to the **/usr/share/centreon/www/install** directory (**x** is the target version number for your migrated machine): ```shell cd /var/lib/centreon/installs/ - mv install-25.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ + mv install-26.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ ``` 2. If you use the same IP address or same DNS name on the old Centreon webserver and the new one, do a full cache cleanup of your browser to avoid JS issues. diff --git a/versioned_docs/version-26.10/monitoring/basic-objects/contacts-create.md b/versioned_docs/version-26.10/monitoring/basic-objects/contacts-create.md index db7d0ae42d91..e9e2bba876cc 100644 --- a/versioned_docs/version-26.10/monitoring/basic-objects/contacts-create.md +++ b/versioned_docs/version-26.10/monitoring/basic-objects/contacts-create.md @@ -41,7 +41,7 @@ http://[IP_DU_SERVER_CENTRAL]/centreon/main.php?autologin=1&useralias=[login_use > The Possibility of automatic connection (auto login) should be enabled in the menu: **Administration \> Options**. * The **Authentication Source** field specifies if the connection information comes from an LDAP directory or information stored locally on the server. -* The next 3 fields are for authorizing users to perform calls to our [API v1](../../api/rest-api-v1.md#api-calls) and [API v2](https://docs-api.centreon.com/api/centreon-web/25.10/) (note: our API documentation is written for developers familiar with HTTP requests and JSON). +* The next 3 fields are for authorizing users to perform calls to our [API v1](../../api/rest-api-v1.md#api-calls) and [API v2](https://docs-api.centreon.com/api/centreon-web/26.10/) (note: our API documentation is written for developers familiar with HTTP requests and JSON). - The **Configuration API** field only applies to the v2 API as only administrators can call this API using v1. - The [**Realtime API**](../../api/rest-api-v1.md#realtime-information) can be called by a non-administrator user in both versions as long as this field is checked. - Administrators are able to call both the **Configuration API** and the [**Realtime API**](../../api/rest-api-v1.md#realtime-information) even if these fields are not checked. This is true for both v1 and v2. They are also the only ones allowed to use [**CLAPI**](../../api/clapi.md) while others can only use the Rest API. diff --git a/versioned_docs/version-26.10/releases/lifecycle.md b/versioned_docs/version-26.10/releases/lifecycle.md index 14cdd8bd9b02..7634fe1b7936 100644 --- a/versioned_docs/version-26.10/releases/lifecycle.md +++ b/versioned_docs/version-26.10/releases/lifecycle.md @@ -120,6 +120,7 @@ This diagram outlines the Centreon version lifecycle policy until version 24.04: | Product | Release | End of support| State | |----------------|--------------|---------------|---------------------| +| Centreon 26.10 | 10/2026 | 04/2029 | Supported | | Centreon 25.10 | 10/2025 | 04/2027 | Supported | | Centreon 24.10 | 10/2024 | 10/2027 | Supported | | Centreon 24.04 | 04/2024 | 04/2026 | No longer supported | diff --git a/versioned_docs/version-26.10/service-mapping/install.md b/versioned_docs/version-26.10/service-mapping/install.md index 4c931579a54a..be11f3d1b68c 100644 --- a/versioned_docs/version-26.10/service-mapping/install.md +++ b/versioned_docs/version-26.10/service-mapping/install.md @@ -15,7 +15,7 @@ import TabItem from '@theme/TabItem'; See the [software requirements](../installation/prerequisites.md#characteristics-of-the-servers). Install BAM on the central server. -The central server and Centreon BAM must be installed in the same major versions (i.e. both in 25.10.x). +The central server and Centreon BAM must be installed in the same major versions (i.e. both in 26.10.x). If you want to be able to view the Business activities monitored by a remote server, install BAM on the remote server too. When BAM is installed on a remote server, the Business activities will only include the resources monitored by the remote server. ## Installation diff --git a/versioned_docs/version-26.10/update/update-centreon-platform.md b/versioned_docs/version-26.10/update/update-centreon-platform.md index bbf90b083d94..1c912b6c3aa7 100644 --- a/versioned_docs/version-26.10/update/update-centreon-platform.md +++ b/versioned_docs/version-26.10/update/update-centreon-platform.md @@ -1,11 +1,11 @@ --- id: update-centreon-platform -title: Update a Centreon 25.10 platform +title: Update a Centreon 26.10 platform --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This chapter describes how to update your Centreon 25.10 platform (i.e. switch from version 25.10.x to version 25.10.y). +This chapter describes how to update your Centreon 26.10 platform (i.e. switch from version 26.10.x to version 26.10.y). >After updating your central server, make sure you also update all your remote servers and your pollers. > @@ -168,14 +168,14 @@ procedure](../monitoring/monitoring-servers/deploying-a-configuration.md). In our case, we have the configuration described below (you need to adapt the procedure to your configuration). - address: 10.25.XX.XX - port: 80 - - version: 25.10 + - version: 26.10 - login: Admin - password: xxxxx 2. Enter the following request: ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ + curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --data '{ @@ -324,7 +324,7 @@ You can perform an unattended update of your platform using the **unattended.sh* 1. Download the script using the following command: ```shell -curl -L https://download.centreon.com/25.10/unattended.sh -O /tmp/unattended +curl -L https://download.centreon.com/26.10/unattended.sh -O /tmp/unattended ``` 2. Run the script: @@ -332,17 +332,17 @@ curl -L https://download.centreon.com/25.10/unattended.sh -O /tmp/unattended * For a central server: ```shell -bash unattended.sh update -t central -v 25.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash unattended.sh update -t central -v 26.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` * For a remote server: ```shell -bash unattended.sh update -t central -v 25.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash unattended.sh update -t central -v 26.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` * For a poller: ```shell -bash unattended.sh update -t poller -v 25.10 -r stable -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash unattended.sh update -t poller -v 26.10 -r stable -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` diff --git a/versioned_docs/version-26.10/upgrade/introduction.md b/versioned_docs/version-26.10/upgrade/introduction.md index e665cf0b4a08..9262a1f25e2d 100644 --- a/versioned_docs/version-26.10/upgrade/introduction.md +++ b/versioned_docs/version-26.10/upgrade/introduction.md @@ -3,11 +3,11 @@ id: introduction title: Introduction to upgrade --- -This chapter describes how to upgrade your Centreon monitoring platform, i.e. switching between major versions (for instance, from 21.10 to 25.10). +This chapter describes how to upgrade your Centreon monitoring platform, i.e. switching between major versions (for instance, from 21.10 to 26.10). > As of version 23.04, Centreon no longer supports CentOS 7. If your Centreon platform was installed on CentOS 7, you cannot simply upgrade it; you must change to a [supported OS](../installation/compatibility.md#operating-systems) using a [migration procedure](../migrate/introduction.md). -> Business edition users: MAP Legacy is no longer available in Centreon 25.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). This procedure is linked to your initial version of Centreon. You will have to **use packages** if you already installed using Centreon ISO or an RPM, and diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-20-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-20-10.md index 554a25099246..693ff312f9bb 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-20-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-20-10.md @@ -6,15 +6,15 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; This chapter describes how to upgrade your Centreon platform from version 20.10 -to version 25.10. +to version 26.10. > Version 20.10 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. -You cannot simply upgrade Centreon from a version earlier than 20.10 to version 25.10, as CentOS 7 is no longer supported. You need to [migrate your platform to a supported OS](../migrate/introduction.md). +You cannot simply upgrade Centreon from a version earlier than 20.10 to version 26.10, as CentOS 7 is no longer supported. You need to [migrate your platform to a supported OS](../migrate/introduction.md). > 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](../developer/developer-broker-bbdo-switch-versions.md). -> Business edition users: MAP Legacy is no longer available in Centreon 25.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > If you want to migrate your Centreon server to Oracle Linux / RHEL 8 or 9 > you need to follow the [migration procedure](../migrate/migrate-from-el-to-el.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. @@ -22,7 +22,7 @@ You cannot simply upgrade Centreon from a version earlier than 20.10 to version > To perform this procedure, your MariaDB version must be >= 10.3.22. > If not, please follow [this](./upgrade-mariadb.md) > procedure in order to update MariaDB before you can continue with the upgrade -> from version 20.10 to version 25.10 as described by this document. +> from version 20.10 to version 26.10 as described by this document. > Warning: following the correction of a problem relating to the database schema, it will be necessary to stop the > insertion of data collected in the database during the update. These will be stored in temporary files and then @@ -113,7 +113,7 @@ Before upgrading your Centreon platform, make sure the following package reposit ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -158,7 +158,7 @@ rm /etc/yum.repos.d/centreon-business-20.10.repo -3. Install the 25.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. +3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. 5. Stop the Centreon Broker process: @@ -174,7 +174,7 @@ rm /var/lib/centreon-broker/* -f ### Upgrade PHP -Centreon 25.10 uses PHP in version 8.2. +Centreon 26.10 uses PHP in version 8.4. @@ -373,7 +373,7 @@ Run the following command on the dedicated DBMS server: ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` @@ -568,7 +568,7 @@ Run the following command: ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-21-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-21-04.md index c3f65b6c48d1..5780446b9352 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-21-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-21-04.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; This chapter describes how to upgrade your Centreon platform from version 21.04 -to version 25.10. +to version 26.10. > Version 21.04 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. @@ -15,7 +15,7 @@ to version 25.10. > If you want to migrate your Centreon server to Oracle Linux / RHEL 8 > you need to follow the [migration procedure](../migrate/migrate-from-el-to-el.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. -> Business edition users: MAP Legacy is no longer available in Centreon 25.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > Warning: If you were using the following monitoring connectors, from version 25.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: > * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) @@ -96,7 +96,7 @@ Before upgrading your Centreon platform, make sure the following package reposit ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -129,7 +129,7 @@ rm /etc/yum.repos.d/centreon-business-21.04.repo -3. Install the 25.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. +3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. 5. Stop the Centreon Broker process: @@ -145,7 +145,7 @@ rm /var/lib/centreon-broker/* -f ### Upgrade PHP -Centreon 25.10 uses PHP in version 8.2. +Centreon 26.10 uses PHP in version 8.4. @@ -445,7 +445,7 @@ Run the following command: ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-21-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-21-10.md index f40158e002d0..8fbd230d1f48 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-21-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-21-10.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; This chapter describes how to upgrade your Centreon platform from version 21.10 -to version 25.10. +to version 26.10. > Version 21.10 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. @@ -15,7 +15,7 @@ to version 25.10. > If you want to migrate your Centreon server to Oracle Linux / RHEL 8 > you need to follow the [migration procedure](../migrate/migrate-from-el-to-el.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. -> Business edition users: MAP Legacy is no longer available in Centreon 25.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > Warning: If you were using the following monitoring connectors, from version 25.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: > * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) @@ -92,7 +92,7 @@ Before upgrading your Centreon platform, make sure the following package reposit ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -125,7 +125,7 @@ rm /etc/yum.repos.d/centreon-business-21.10.repo -3. Install the 25.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. +3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. 4. Stop the Centreon Broker process: @@ -141,7 +141,7 @@ rm /var/lib/centreon-broker/* -f ### Upgrade PHP -Centreon 25.10 uses PHP in version 8.2. +Centreon 26.10 uses PHP in version 8.4. @@ -222,7 +222,7 @@ rm /etc/yum.repos.d/centreon-business-21.10.repo -3. Install the 25.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. +3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. 5. Stop the Centreon Broker process: @@ -466,7 +466,7 @@ Run the following command: ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-22-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-22-04.md index dc5bd763de4a..333e91ee0914 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-22-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-22-04.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; This chapter describes how to upgrade your Centreon platform from version 22.04 -to version 25.10. +to version 26.10. > Version 22.04 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. @@ -14,9 +14,9 @@ to version 25.10. > If you want to migrate your Centreon platform to another server/OS, follow the [migration procedure](../migrate/introduction.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. -> Business edition users: MAP Legacy is no longer available in Centreon 25.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). -> Version 25.10 means the end of support for Debian 11. If you were using Debian 11, you must first migrate to Debian 12 before you can upgrade Centreon. See [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). +> Version 26.10 means the end of support for Debian 12. If you were using Debian 12, you must first migrate to Debian 13 before you can upgrade Centreon. See [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). > Warning: If you were using the following monitoring connectors, from version 25.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: > * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) @@ -74,7 +74,7 @@ Before upgrading your Centreon platform, make sure the following package reposit ## Upgrade the Centreon Central server -Version 25.10 means the end of support for Debian 11. If you were using Debian 11, you must first migrate to Debian 12 before you can upgrade Centreon. See [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). +Version 26.10 means the end of support for Debian 12. If you were using Debian 12, you must first migrate to Debian 13 before you can upgrade Centreon. See [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). > When you run a command, check its output. If you get an error message, stop the procedure and fix the issue. @@ -102,7 +102,7 @@ Version 25.10 means the end of support for Debian 11. If you were using Debian 1 ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -115,7 +115,7 @@ Version 25.10 means the end of support for Debian 11. If you were using Debian 1 ```shell rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -165,7 +165,7 @@ rm /etc/apt/sources.list.d/centreon-business.list -3. Install the 25.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. +3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. 4. 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**). @@ -183,7 +183,7 @@ rm /var/lib/centreon-broker/* -f ### Upgrade PHP -Centreon 25.10 uses PHP in version 8.2. +Centreon 26.10 uses PHP in version 8.4. @@ -494,14 +494,14 @@ procedure](../monitoring/monitoring-servers/deploying-a-configuration.md). In our case, we have the configuration described below (you need to adapt the procedure to your configuration). - address: 10.25.XX.XX - port: 80 - - version: 25.10 + - version: 26.10 - login: Admin - password: xxxxx 2. Enter the following request: ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ + curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --data '{ @@ -645,7 +645,7 @@ Run the following command: ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` @@ -653,7 +653,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list apt update ``` diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-22-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-22-10.md index a7938ad04c6b..fad520e19c27 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-22-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-22-10.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; This chapter describes how to upgrade your Centreon platform from version 22.10 -to version 25.10. +to version 26.10. > Version 22.10 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. @@ -14,7 +14,7 @@ to version 25.10. > If you want to migrate your Centreon platform to another server/OS, follow the [migration procedure](../migrate/introduction.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. -> Business edition users: MAP Legacy is no longer available in Centreon 25.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > Version 25.10 means the end of support for Debian 11. If you were using Debian 11, you must first migrate to Debian 12 before you can upgrade Centreon. See [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index 7b2fc5a56b95..f495c554951d 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -5,7 +5,7 @@ title: Upgrade from Centreon 25.10 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This chapter describes how to upgrade your Centreon platform from version 24.10 to version 25.10. +This chapter describes how to upgrade your Centreon platform from version 25.10 to version 26.10. > When you upgrade your central server, make sure you also upgrade all your remote servers and your pollers. > @@ -15,8 +15,6 @@ This chapter describes how to upgrade your Centreon platform from version 24.10 > If you want to migrate your Centreon platform to another server/OS, follow the [migration procedure](../migrate/introduction.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. -> If you were using MySQL 8.0, you may want to [upgrade to MySQL 8.4](upgrade-mysql.md) before the end of support for version 8.0. at the end of April 2026. - ## Prerequisites ### Perform a backup @@ -70,7 +68,7 @@ Before upgrading your Centreon platform, make sure the following package reposit -1. Update your Centreon 24.10 to the latest minor version. +1. Update your Centreon 25.10 to the latest minor version. 2. Remove the repository files: @@ -83,7 +81,7 @@ Before upgrading your Centreon platform, make sure the following package reposit ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -91,12 +89,12 @@ Before upgrading your Centreon platform, make sure the following package reposit -1. Update your Centreon 24.10 to the latest minor version. +1. Update your Centreon 25.10 to the latest minor version. 2. Remove the repository files: ```shell - rm /etc/yum.repos.d/centreon-24.10.repo + rm /etc/yum.repos.d/centreon-25.10.repo rm /etc/yum.repos.d/centreon.repo ``` @@ -104,19 +102,19 @@ Before upgrading your Centreon platform, make sure the following package reposit ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` -1. Update your Centreon 24.10 to the latest minor version. +1. Update your Centreon 25.10 to the latest minor version. 2. Run the following commands: ```shell -rm -f /etc/apt/sources.list.d/centreon-25.10-stable.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list +rm -f /etc/apt/sources.list.d/centreon-26.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -166,7 +164,7 @@ rm /etc/apt/sources.list.d/centreon-business.list -3. Install the 25.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. +3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. 4. 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**). @@ -503,14 +501,14 @@ procedure](../monitoring/monitoring-servers/deploying-a-configuration.md). In our case, we have the configuration described below (you need to adapt the procedure to your configuration). - address: 10.25.XX.XX - port: 80 - - version: 25.10 + - version: 26.10 - login: Admin - password: xxxxx 2. Enter the following request: ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ + curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --data '{ @@ -675,7 +673,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/e ```shell rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard-25.10-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon.list +echo "deb https://packages.centreon.com/apt-standard-26.10-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon.list apt update ``` diff --git a/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md b/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md index 75d13fc46cc9..7f67c488e288 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md @@ -22,6 +22,7 @@ When you upgrade from one major version of Centreon to another, you must: | Centreon | MariaDB | |----------|---------| +| 26.10 | 11.8 | | 25.10 | 10.11 | | 24.10 | 10.11 | | 24.04 | 10.11 | @@ -99,7 +100,7 @@ ii mysql-common 1:10.5.17+maria~deb11 all ## Upgrading between major MariaDB versions -You must uninstall then reinstall MariaDB to upgrade between major versions (for example to switch from version 10.5 to version 10.11). +You must uninstall then reinstall MariaDB to upgrade between major versions (for example to switch from version 10.11 to version 11.8). 1. Stop the MariaDB service: @@ -139,15 +140,15 @@ rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared Mari -At the **[ Knowing your version of MariaDB](#knowing-your-version-of-mariadb)** step, the **grep** command returned the precise version of MariaDB you have. +At the **[Knowing your version of MariaDB](#knowing-your-version-of-mariadb)** step, the **grep** command returned the precise version of MariaDB you have. -* If the results of the **grep** command included “10.5”, your uninstallation command must include it too, like in the following example: +* If the results of the **grep** command included the version of MariaDB (e.g., “10.11”), your uninstallation command must include it too, like in the following example: ```shell -dpkg -r --ignore-depends=mariadb-server,mariadb-client,mariadb-shared,mariadb-compat,mariadb-common mariadb-server mariadb-server-10.5 mariadb-client mariadb-client-10.5 mariadb-client-core-10.5 mariadb-common mariadb-server-core-10.5 mysql-common +dpkg -r --ignore-depends=mariadb-server,mariadb-client,mariadb-shared,mariadb-compat,mariadb-common mariadb-server mariadb-server-10.11 mariadb-client mariadb-client-10.11 mariadb-client-core-10.11 mariadb-common mariadb-server-core-10.11 mysql-common ``` -* If the results of the **grep** command did not include “10.5”, use the following command: +* If the results of the **grep** command did not include “10.11”, use the following command: ```shell dpkg -r --ignore-depends=mariadb-server,mariadb-client,mariadb-shared,mariadb-compat,mariadb-common mariadb-server mariadb-server mariadb-client mariadb-client mariadb-client-core mariadb-common mariadb-server-core mysql-common @@ -168,45 +169,45 @@ dpkg -r --ignore-depends=mariadb-server,mariadb-client,mariadb-shared,mariadb-co > Make sure you have [installed the official MariaDB repository](https://mariadb.com/kb/en/mariadb-package-repository-setup-and-usage/) before you continue the procedure. -3. Install version 10.11: +3. Install version 11.8: ```shell -dnf module enable -y mariadb:10.11 -dnf install mariadb-server-10.11\* mariadb-10.11\* +dnf module enable -y mariadb:11.8 +dnf install mariadb-server-11.8\* mariadb-11.8\* ``` ```shell -dnf module enable -y mariadb:10.11 -dnf install mariadb-server-10.11\* mariadb-10.11\* +dnf module enable -y mariadb:11.8 +dnf install mariadb-server-11.8\* mariadb-11.8\* ``` ```shell -dnf module enable -y mariadb:10.11 -dnf install mariadb-server-10.11\* mariadb-10.11\* +dnf module enable -y mariadb:11.8 +dnf install mariadb-server-11.8\* mariadb-11.8\* ``` ```shell -dnf module enable -y mariadb:10.11 -dnf install mariadb-server-10.11\* mariadb-10.11\* +dnf module enable -y mariadb:11.8 +dnf install mariadb-server-11.8\* mariadb-11.8\* ``` ```shell -curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=12 --mariadb-server-version="mariadb-10.11" +curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=12 --mariadb-server-version="mariadb-11.8" ``` ```shell diff --git a/versioned_docs/version-26.10/upgrade/upgrade-mysql.md b/versioned_docs/version-26.10/upgrade/upgrade-mysql.md index 6cebef138a74..f3ea2b7ae32f 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-mysql.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-mysql.md @@ -5,7 +5,7 @@ title: Upgrading MySQL import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -If you were using Centreon 24.04 or 24.10 with MySQL, be aware that support for MySQL 8.0 ends at the end of April 2026. Make sure your Centreon always uses [a supported version of MySQL](#versions-of-mysql-compatible-with-centreon-2510). +If you were using Centreon 24.04 or 24.10 with MySQL, be aware that support for MySQL 8.0 ends at the end of April 2026. Make sure your Centreon always uses [a supported version of MySQL](#versions-of-mysql-compatible-with-centreon-2610). You may have several MySQL databases in your architecture. The central server has a database, each remote server has a database, and the MBI and MAP modules each have a dedicated database. Within your architecture, all databases must have the same version of MySQL. @@ -14,14 +14,13 @@ and the MBI and MAP modules each have a dedicated database. Within your architec Do not upgrade your version of Centreon and your version of MySQL at the same time. You can perform both upgrades one after the other in the order you want, however, make sure the first upgrade procedure is fully complete before you perform the second one. -## Versions of MySQL compatible with Centreon 25.10 +## Versions of MySQL compatible with Centreon 26.10 -* MySQL 8.4 is recommended for new installations. -* MySQL 8.0 can still be used until its end of support (end of April 2026), but after this date you will have to upgrade to MySQL 8.4. +* MySQL 8.4 ## Knowing your version of MySQL -To find out which version of MariaDB is installed on your machine, enter the following command: +To find out which version of MySQL is installed on your machine, enter the following command: ```shell mysql --version From 8d130fe3ef658fd92a2296c4e03b31f1a4f34575 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 3 Jul 2026 18:48:30 +0200 Subject: [PATCH 002/179] Update FR files --- .../version-26.10/api/rest-api-v2.md | 8 +++---- .../developer-gorgone-rebound-mode.md | 6 ++--- .../developer/developer-module.md | 2 +- .../unattended.md | 6 ++--- .../using-packages.md | 6 ++--- .../installation-of-a-poller/unattended.md | 4 ++-- .../using-packages.md | 8 +++---- .../unattended.md | 6 ++--- .../using-packages.md | 8 +++---- .../version-26.10/installation/offline.md | 4 ++-- .../version-26.10/migrate/migrate-from-3-4.md | 18 +++++++------- .../migrate/migrate-from-debian-to-debian.md | 4 ++-- .../migrate/migrate-from-el-to-debian.md | 4 ++-- .../migrate/migrate-from-el-to-el.md | 4 ++-- .../poller-display-to-remote-server.md | 4 ++-- .../version-26.10/releases/lifecycle.md | 1 + .../version-26.10/service-mapping/install.md | 2 +- .../update/update-centreon-platform.md | 16 ++++++------- .../version-26.10/upgrade/introduction.md | 4 ++-- .../upgrade/upgrade-from-20-10.md | 16 ++++++------- .../upgrade/upgrade-from-21-04.md | 12 +++++----- .../upgrade/upgrade-from-21-10.md | 14 +++++------ .../upgrade/upgrade-from-22-04.md | 22 ++++++++--------- .../upgrade/upgrade-from-22-10.md | 20 ++++++++-------- .../upgrade/upgrade-from-23-04.md | 24 +++++++++---------- .../upgrade/upgrade-from-23-10.md | 24 +++++++++---------- .../upgrade/upgrade-from-24-04.md | 24 +++++++++---------- .../upgrade/upgrade-from-24-10.md | 22 ++++++++--------- .../upgrade/upgrade-from-25-10.md | 24 +++++++++---------- .../version-26.10/upgrade/upgrade-mariadb.md | 1 + .../version-26.10/upgrade/upgrade-mysql.md | 7 +++--- 31 files changed, 162 insertions(+), 163 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/api/rest-api-v2.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/api/rest-api-v2.md index 3461d2922539..48868148e9c2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/api/rest-api-v2.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/api/rest-api-v2.md @@ -3,7 +3,7 @@ id: rest-api-v2 title: Utiliser l'API v2 avec Postman --- -Cette page décrit comment utiliser [l'API v2](https://docs-api.centreon.com/api/centreon-web/25.10/) de Centreon Web avec Postman +Cette page décrit comment utiliser [l'API v2](https://docs-api.centreon.com/api/centreon-web/26.10/) de Centreon Web avec Postman. ## Créer une collection Postman depuis la définition OpenAPI @@ -64,7 +64,7 @@ environnements. > ![image](../assets/api/postman-collection-edit.png) > > Dans l'onglet **Variables**, changer la valeur de *version* soit par -> "latest", soit par votre numéro de version `v.`, par exemple "v25.10". +> "latest", soit par votre numéro de version `v.`, par exemple "v26.10". > > Vous pouvez obtenir votre numéro de version "majeure.mineure" à l'aide de la commmande suivante : > `curl -s http://127.0.0.1:80/centreon/api/latest/platform/versions | jq '.web '` @@ -72,8 +72,8 @@ environnements. > Voici un exemple de résultat : > > \{ -> "version": "25.10.0", -> "major": "24", +> "version": "26.10.0", +> "major": "26", > "minor": "10", > "fix": "0" > \} diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-gorgone-rebound-mode.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-gorgone-rebound-mode.md index d0534d30f791..381149c8cd5f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-gorgone-rebound-mode.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-gorgone-rebound-mode.md @@ -76,7 +76,7 @@ Installez le démon Gorgone en utilisant les commandes suivantes : ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo dnf clean all --enablerepo=* dnf update dnf install centreon-gorgone @@ -87,7 +87,7 @@ dnf install centreon-gorgone ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update dnf install centreon-gorgone @@ -99,7 +99,7 @@ dnf install centreon-gorgone Pour installer le dépôt Centreon, exécutez la commande suivante : ```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-module.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-module.md index b908bf78d1ae..c75f3b69eabd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-module.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-module.md @@ -32,7 +32,7 @@ $module_conf['dummy'] = [ // Full module's name 'rname' => 'Dummy Example Module', // Module's version - 'mod_release' => '25.10', + 'mod_release' => '26.10', // Additional information 'infos' => 'This module is a skeleton', // Allow your module to be uninstalled diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/unattended.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/unattended.md index 3b9f6d91f683..938619ee0e4d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/unattended.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/unattended.md @@ -59,7 +59,7 @@ apt update && apt upgrade 2. Téléchargez le script à l'aide de la commande suivante : ```shell -curl -L https://download.centreon.com/25.10/unattended.sh --output /tmp/unattended.sh +curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh ``` 3. Exécutez la commande suivante en **root** : @@ -67,13 +67,13 @@ curl -L https://download.centreon.com/25.10/unattended.sh --output /tmp/unattend * Pour spécifier le mot de passe du compte **admin** par défaut : ```shell -bash /tmp/unattended.sh install -t central -v 25.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` * Pour obtenir un mot de passe autogénéré pour le compte **admin** par défaut (le script vous indiquera où le mot de passe est stocké) : ```shell -bash /tmp/unattended.sh install -t central -v 25.10 -r stable -s -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` Dans les deux cas, vous obtiendrez un fichier de log complet avec toutes les erreurs dans votre répertoire **tmp**, fichier nommé **unattended(date).log**. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index b22e94b20839..0e608b58f650 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -339,7 +339,7 @@ Installez le dépôt Centreon à l'aide de la commande suivante : ```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -348,7 +348,7 @@ dnf update ```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -357,7 +357,7 @@ dnf update ```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/unattended.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/unattended.md index 9a1cc9983055..20b33779d54a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/unattended.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/unattended.md @@ -59,13 +59,13 @@ apt update && apt upgrade 2. Téléchargez le script à l'aide de la commande suivante : ```shell -curl -L https://download.centreon.com/25.10/unattended.sh --output /tmp/unattended.sh +curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh ``` 3. Exécutez la commande suivante en **root** : ```shell -bash /tmp/unattended.sh install -t poller -v 25.10 -r stable -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash /tmp/unattended.sh install -t poller -v 26.10 -r stable -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` Vous obtiendrez un fichier de log complet avec toutes les erreurs dans votre répertoire **tmp**, fichier nommé **unattended(date).log**. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-packages.md index 4a9a98ce65bf..50daec3cc9bb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-packages.md @@ -285,7 +285,7 @@ suffisants : ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -295,7 +295,7 @@ dnf update ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -306,7 +306,7 @@ dnf update Pour installer le dépôt Centreon, exécutez la commande suivante : ```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -462,7 +462,7 @@ Failed connect to 192.168.0.1:444; Connection refused 2020-10-20T10:42:23+02:00 [ERROR]: No route found for “POST /centreon/api/latest/platform/topology” ``` -> La version Centreon du serveur distant est invalide. Elle doit être supérieure ou égale à 25.10. +> La version Centreon du serveur distant est invalide. Elle doit être supérieure ou égale à 26.10. ## Étape 4 : Ajouter le Poller à la configuration diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/unattended.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/unattended.md index 208ebcd88bde..6f4c147910ae 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/unattended.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/unattended.md @@ -59,7 +59,7 @@ apt update && apt upgrade 2. Téléchargez le script à l'aide de la commande suivante : ```shell -curl -L https://download.centreon.com/25.10/unattended.sh --output /tmp/unattended.sh +curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh ``` 3. Exécutez la commande suivante en **root** : @@ -67,13 +67,13 @@ curl -L https://download.centreon.com/25.10/unattended.sh --output /tmp/unattend * Pour spécifier le mot de passe du compte **admin** par défaut : ```shell -bash /tmp/unattended.sh install -t central -v 25.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` * Pour obtenir un mot de passe autogénéré pour le compte **admin** par défaut (le script vous indiquera où le mot de passe est stocké) : ```shell -bash /tmp/unattended.sh install -t central -v 25.10 -r stable -s -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` Dans les deux cas, vous obtiendrez un fichier de log complet avec toutes les erreurs dans votre répertoire **tmp**, fichier nommé **unattended(date).log**. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md index 7ebe8fc668f4..742c428c5317 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md @@ -338,7 +338,7 @@ Exécutez la commande suivante : ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -348,7 +348,7 @@ dnf update ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -357,7 +357,7 @@ dnf update ```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -630,7 +630,7 @@ Failed connect to 192.168.0.1:444; Connection refused 2020-10-20T10:42:23+02:00 [ERROR]: No route found for “POST /centreon/api/latest/platform/topology” ``` -> La version Centreon du serveur distant est invalide. Elle doit être supérieure ou égale à 25.10. +> La version Centreon du serveur distant est invalide. Elle doit être supérieure ou égale à 26.10. ## Étape 6 : Étendre les droits du SGBD local diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/offline.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/offline.md index 84c6af0bf105..9dbd45722f52 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/offline.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/offline.md @@ -16,7 +16,7 @@ Pour pouvoir installer Centreon sur des serveurs sans accès internet, créez un ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` @@ -32,7 +32,7 @@ rpm --import https://yum-gpg.centreon.com/RPM-GPG-KEY-CES ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-3-4.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-3-4.md index 7986170b7849..2c55380aaf97 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-3-4.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-3-4.md @@ -106,14 +106,14 @@ Centreon. ``` 3. Transférer les exports vers le nouveau serveur de base de données Centreon -25.10 : +26.10 : ```shell rsync -avz /tmp/centreon.sql root@\:/tmp/ rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` -4. Sur le serveur de base de données Centreon 25.10, supprimer les bases de +4. Sur le serveur de base de données Centreon 26.10, supprimer les bases de données vierges et les recréer : ```shell @@ -173,8 +173,8 @@ dépend de votre installation. Les principaux répertoires à synchroniser sont > sondes de supervision. > Si vous avez des Pollers en Centreon Engine 1.8.1 que vous comptez migrer plus -> tard en 25.10, attention au dossier des plugins Nagios. La macro de -> ressource $USER1$ de Centreon 25.10 pointe sur /usr/lib64/nagios/plugins +> tard en 26.10, attention au dossier des plugins Nagios. La macro de +> ressource $USER1$ de Centreon 26.10 pointe sur /usr/lib64/nagios/plugins > > A exécuter sur vos collecteurs en Centreon Engine 1.8.1 : > @@ -192,18 +192,18 @@ dépend de votre installation. Les principaux répertoires à synchroniser sont > -rwxr-xr-x 1 root root 1711288 6 avril 2018 cbmod.so > ``` -Vous pouvez générer les configurations depuis Centreon 25.10 -indifféremment vers un collecteur en 25.10 ou 1.8.1. +Vous pouvez générer les configurations depuis Centreon 26.10 +indifféremment vers un collecteur en 26.10 ou 1.8.1. ### Montée de version de la solution Centreon Forcez la montée de version du nouveau serveur en déplacant le contenu du répertoire -**/var/lib/centreon/installs/install-25.10.0-YYYYMMDD\_HHMMSS** dans le +**/var/lib/centreon/installs/install-26.10.0-YYYYMMDD\_HHMMSS** dans le répertoire **/usr/share/centreon/www/install** : ```shell cd /var/lib/centreon/installs/ -mv install-25.10.0-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ +mv install-26.10.0-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ ``` > Si vous utilisez la même adresse IP ou le même nom DNS entre l'ancien serveur @@ -252,7 +252,7 @@ la configuration de l'ensemble de la plateforme et exportez là. ### Mise à jour des modules Référez-vous à la documentation des modules installés afin de connaître leur -compatibilité avec Centreon 25.10, et pour mettre à jour ces derniers. +compatibilité avec Centreon 26.10, et pour mettre à jour ces derniers. ### Migrer vos autres serveurs diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md index ae46cb35a9fa..f8f1e98174c9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md @@ -172,12 +172,12 @@ Si vous utilisez vos propres plugins personnalisés, synchronisez les répertoir ### Étape 5 : Montée de version de la solution Centreon 1. Sur le nouveau serveur, forcez la montée de version en déplacant le contenu du répertoire - **/var/lib/centreon/installs/install-25.10.x-YYYYMMDD_HHMMSS** dans le + **/var/lib/centreon/installs/install-26.10.x-YYYYMMDD_HHMMSS** dans le répertoire **/usr/share/centreon/www/install** (**x** est le numéro de version cible pour votre machine migrée): ```shell cd /var/lib/centreon/installs/ - mv install-25.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ + mv install-26.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ ``` 2. Si vous utilisez la meme adresse IP ou le même nom DNS entre l'ancien serveur diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md index be5b2363acbe..79029d88e3ae 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md @@ -176,12 +176,12 @@ Si vous utilisez vos propres plugins personnalisés, synchronisez les répertoir ### Étape 5 : Montée de version de la solution Centreon 1. Sur le nouveau serveur, forcez la montée de version en déplacant le contenu du répertoire - **/var/lib/centreon/installs/install-25.10.x-YYYYMMDD_HHMMSS** dans le + **/var/lib/centreon/installs/install-26.10.x-YYYYMMDD_HHMMSS** dans le répertoire **/usr/share/centreon/www/install** (**x** est le numéro de version cible pour votre machine migrée): ```shell cd /var/lib/centreon/installs/ - mv install-25.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ + mv install-26.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ ``` 2. Si vous utilisez la meme adresse IP ou le même nom DNS entre l'ancien serveur diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md index 541e8845d522..0ed729a1e318 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md @@ -196,12 +196,12 @@ rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/c ### Étape 5 : Montée de version de la solution Centreon 1. Sur le nouveau serveur, forcez la montée de version en déplacant le contenu du répertoire - **/var/lib/centreon/installs/install-25.10.x-YYYYMMDD_HHMMSS** dans le + **/var/lib/centreon/installs/install-26.10.x-YYYYMMDD_HHMMSS** dans le répertoire **/usr/share/centreon/www/install** (**x** est le numéro de version cible pour votre machine migrée): ```shell cd /var/lib/centreon/installs/ - mv install-25.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ + mv install-26.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ ``` 2. Si vous utilisez la meme adresse IP ou le même nom DNS entre l'ancien serveur diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/poller-display-to-remote-server.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/poller-display-to-remote-server.md index 47f2f72d2214..691c752cc4bc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/poller-display-to-remote-server.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/poller-display-to-remote-server.md @@ -17,7 +17,7 @@ désinstallez le module **centreon-poller-display-central** ``` Puis suivez la [procédure de migration](../migrate/migrate-from-3-4.md) d'un serveur Centreon -Central vers 25.10. +Central vers 26.10. > Si vous possédez des modules Centreon EMS, il est nécessaire de mettre à jour > ces dépôts. Contactez votre support Centreon pour obtenir ces derniers. Demandez @@ -165,7 +165,7 @@ Failed connect to 192.168.0.1:444; Connection refused 2020-10-20T10:42:23+02:00 [ERROR]: No route found for “POST /centreon/api/latest/platform/topology” ``` -> La version Centreon du serveur distant est invalide. Elle doit être supérieure ou égale à 25.10. +> La version Centreon du serveur distant est invalide. Elle doit être supérieure ou égale à 26.10. 6. Ajout des droits pour l'utilsateur de base de données centreon d'utiliser la commande **LOAD DATA INFILE**: diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/releases/lifecycle.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/releases/lifecycle.md index 9e2af7b85670..6cb0f9f9c400 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/releases/lifecycle.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/releases/lifecycle.md @@ -116,6 +116,7 @@ Le schéma suivant présente le cycle de vie des produits Centreon jusqu'à la v | Produit | Sortie | Date de fin de support | État | |----------------|--------------|---------------------------|---------------------| +| Centreon 26.10 | 10/2026 | 10/2029 | Supportée | | Centreon 25.10 | 10/2025 | 04/2027 | Supportée | | Centreon 24.10 | 10/2024 | 10/2027 | Supportée | | Centreon 24.04 | 04/2024 | 04/2026 | Plus supportée | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/install.md index e481998b8c3b..426a0f1086fa 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/install.md @@ -15,7 +15,7 @@ import TabItem from '@theme/TabItem'; Voir les [prérequis logiciels](../installation/prerequisites.md#caractéristiques-des-serveurs). Installez BAM sur le serveur central. -Le serveur central et Centreon BAM doivent être dans la même version majeure (c'est-à-dire tous les deux en 25.10.x). +Le serveur central et Centreon BAM doivent être dans la même version majeure (c'est-à-dire tous les deux en 26.10.x). Si vous voulez pouvoir voir les Activités métier supervisées par un serveur distant, installez BAM également sur le serveur distant. Lorsque BAM est installé sur un serveur distant, les Activités métier n'incluent que les ressources supervisées par le serveur distant. ## Installation diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md index b8af7241ee5c..455b61b58f52 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md @@ -1,12 +1,12 @@ --- id: update-centreon-platform -title: Mise à jour d'une plateforme Centreon 25.10 +title: Mise à jour d'une plateforme Centreon 26.10 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de mise à jour de votre plate-forme Centreon -25.10 (c'est-à-dire le passage de 25.10.x à 25.10.y). +25.10 (c'est-à-dire le passage de 26.10.x à 26.10.y). > Après avoir effectué la mise à jour de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. > @@ -173,14 +173,14 @@ mise à jour. - adresse : 10.25.XX.XX - port : 80 - - version : 25.10 + - version : 26.10 - identifiant : Admin - mot de passe : xxxxx 2. Entrez la requête suivante : ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ + curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --data '{ @@ -329,7 +329,7 @@ Vous pouvez réaliser une mise à jour silencieuse de votre plateforme en utilis 1. Téléchargez le script avec la commande suivante : ```shell -curl -L https://download.centreon.com/25.10/unattended.sh -O /tmp/unattended +curl -L https://download.centreon.com/26.10/unattended.sh -O /tmp/unattended ``` 2. Lancez le script : @@ -337,17 +337,17 @@ curl -L https://download.centreon.com/25.10/unattended.sh -O /tmp/unattended * Pour un serveur central : ```shell -bash unattended.sh update -t central -v 25.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash unattended.sh update -t central -v 26.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` * Pour un serveur distant : ```shell -bash unattended.sh update -t central -v 25.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash unattended.sh update -t central -v 26.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` * Pour un collecteur : ```shell -bash unattended.sh update -t poller -v 25.10 -r stable -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log +bash unattended.sh update -t poller -v 26.10 -r stable -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/introduction.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/introduction.md index 7b73748897e6..464d7d18b4b7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/introduction.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/introduction.md @@ -3,11 +3,11 @@ id: introduction title: Introduction à la montée de version --- -Ce chapitre décrit le processus de montée de version (upgrade) d'une plateforme Centreon, c'est-à-dire le passage d'une version majeure à une autre (par exemple, 21.10 à 25.10). +Ce chapitre décrit le processus de montée de version (upgrade) d'une plateforme Centreon, c'est-à-dire le passage d'une version majeure à une autre (par exemple, 21.10 à 26.10). > à partir de la version 23.04, Centreon ne supporte plus CentOS 7. Si votre plateforme Centreon était installée sous CentOS 7, vous ne pouvez pas simplement monter de version : passez à un [OS supporté](../installation/compatibility.md#système-dexploitation) en suivant une [procédure de migration](../migrate/introduction.md). -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 25.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). La procédure dépend de la méthode d'installation de votre plate-forme Centreon. Faites une **Mise à jour RPM** si vous avez installé Centreon à partir de diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-20-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-20-10.md index a090f3846105..9366fed2382c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-20-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-20-10.md @@ -6,18 +6,18 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plate-forme -Centreon depuis la version 20.10 vers la version 25.10. +Centreon depuis la version 20.10 vers la version 26.10. > La version 20.10 n'est plus supportée. La montée de version à partir de cette version n'a pas été testée par l'équipe d'assurance qualité de Centreon. -Vous ne pouvez pas simplement monter de version depuis une version antérieure à Centreon 20.10 et vers une version 25.10, car CentOS 7 n'est plus supporté: vous devez [migrer votre plateforme vers un OS supporté](../migrate/introduction.md). +Vous ne pouvez pas simplement monter de version depuis une version antérieure à Centreon 20.10 et vers une version 26.10, car CentOS 7 n'est plus supporté: vous devez [migrer votre plateforme vers un OS supporté](../migrate/introduction.md). > Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. Dans votre architecture, tous les serveurs doivent avoir la même version de Centreon. De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). > Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux > / RHEL 8 ou 9, vous devez suivre la [procédure de migration](../migrate/migrate-from-el-to-el.md). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 25.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > Pour effectuer cette procédure, votre version de MariaDB doit être >= 10.3.22. > Si cela n'est pas le cas, merci de suivre avant le @@ -113,7 +113,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -158,7 +158,7 @@ rm /etc/yum.repos.d/centreon-business-20.10.repo -3. Installez le dépôt business en 25.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. +3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. 5. Arrêtez le processus Centreon Broker : @@ -174,7 +174,7 @@ rm /var/lib/centreon-broker/* -f ### Montée de version de PHP -Centreon 25.10 utilise PHP en version 8.2. +Centreon 26.10 utilise PHP en version 8.4. @@ -375,7 +375,7 @@ Exécutez la commande suivante sur le serveur de base de données dédié : ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` @@ -573,7 +573,7 @@ Exécutez la commande suivante : ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-04.md index e72f2b5d0db4..3c699ef6b5cf 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-04.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plate-forme -Centreon depuis la version 21.04 vers la version 25.10. +Centreon depuis la version 21.04 vers la version 26.10. > La version 21.04 n'est plus supportée. La montée de version à partir de cette version n'a pas été testée par l'équipe d'assurance qualité de Centreon. @@ -15,7 +15,7 @@ Centreon depuis la version 21.04 vers la version 25.10. > Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux > / RHEL 8, vous devez suivre la [procédure de migration](../migrate/migrate-from-el-to-el.md). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 25.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > Attention, si vous utilisiez les connecteurs suivants, à partir de la version 24.10 il est obligatoire de déclarer la configuration de tous ceux-ci [**à la page Configuration > Additional connector configurations**](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) avant de déployer la configuration du collecteur correspondant : > * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) @@ -96,7 +96,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -129,7 +129,7 @@ rm /etc/yum.repos.d/centreon-business-21.04.repo -3. Installez le dépôt business en 25.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. +3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. 4. Arrêtez le processus Centreon Broker : @@ -145,7 +145,7 @@ rm /var/lib/centreon-broker/* -f ### Montée de version de PHP -Centreon 25.10 utilise PHP en version 8.2. +Centreon 26.10 utilise PHP en version 8.4. @@ -440,7 +440,7 @@ Exécutez la commande suivante : ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-10.md index 95b01e59488c..3cb649d25a7e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-10.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 21.10 vers la version 25.10. +Centreon depuis la version 21.10 vers la version 26.10. > La version 21.10 n'est plus supportée. La montée de version à partir de cette version n'a pas été testée par l'équipe d'assurance qualité de Centreon. @@ -15,7 +15,7 @@ Centreon depuis la version 21.10 vers la version 25.10. > Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux > / RHEL 8, vous devez suivre la [procédure de migration](../migrate/migrate-from-el-to-el.md). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 25.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > Attention, si vous utilisiez les connecteurs suivants, à partir de la version 24.10 il est obligatoire de déclarer la configuration de tous ceux-ci [**à la page Configuration > Additional connector configurations**](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) avant de déployer la configuration du collecteur correspondant : > * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) @@ -92,7 +92,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -125,7 +125,7 @@ rm /etc/yum.repos.d/centreon-business-21.10.repo -3. Installez le dépôt business en 25.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. +3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. 4. Arrêtez le processus Centreon Broker : @@ -141,7 +141,7 @@ rm /var/lib/centreon-broker/* -f ### Montée de version de PHP -Centreon 25.10 utilise PHP en version 8.2. +Centreon 26.10 utilise PHP en version 8.4. @@ -222,7 +222,7 @@ rm /etc/yum.repos.d/centreon-business-21.10.repo -3. Installez le dépôt business en 25.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. +3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. 5. Arrêtez le processus Centreon Broker : @@ -469,7 +469,7 @@ Exécutez la commande suivante : ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-04.md index ec06292a67d5..3c6976b98785 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-04.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 22.04 vers la version 25.10. +Centreon depuis la version 22.04 vers la version 26.10. > La version 22.04 n'est plus supportée. La montée de version à partir de cette version n'a pas été testée par l'équipe d'assurance qualité de Centreon. @@ -16,7 +16,7 @@ Centreon depuis la version 22.04 vers la version 25.10. > / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). > Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 25.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian 11, vous devez d'abord migrer en Debian 12 avant d'upgrader Centreon. Voir [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. @@ -105,7 +105,7 @@ Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -118,7 +118,7 @@ Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian ```shell rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -168,7 +168,7 @@ rm /etc/apt/sources.list.d/centreon-business.list -3. Installez le dépôt business en 25.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. +3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. 4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). @@ -186,7 +186,7 @@ rm /var/lib/centreon-broker/* -f ### Montée de version de PHP -Centreon 25.10 utilise PHP en version 8.2. +Centreon 26.10 utilise PHP en version 8.4. @@ -230,7 +230,7 @@ dnf module reset php ```shell dnf module install php:8.2 -dnf distro-sync php\* --allowerasing --enablerepo=centreon-25.10-unstable +dnf distro-sync php\* --allowerasing --enablerepo=centreon-26.10-unstable ``` Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. @@ -504,14 +504,14 @@ mise à jour. - adresse : 10.25.XX.XX - port : 80 - - version : 25.10 + - version : 26.10 - identifiant : Admin - mot de passe : xxxxx 2. Entrez la requête suivante : ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ + curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --data '{ @@ -659,7 +659,7 @@ Exécutez la commande suivante : ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` @@ -667,7 +667,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list apt update ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-10.md index f2a234609476..6c29896f0b3c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-10.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 22.10 vers la version 25.10. +Centreon depuis la version 22.10 vers la version 26.10. > La version 22.10 n'est plus supportée. La montée de version à partir de cette version n'a pas été testée par l'équipe d'assurance qualité de Centreon. @@ -16,7 +16,7 @@ Centreon depuis la version 22.10 vers la version 25.10. > / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). > Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 25.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian 11, vous devez d'abord migrer en Debian 12 avant d'upgrader Centreon. Voir [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. @@ -102,7 +102,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -115,7 +115,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v ```shell rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -165,7 +165,7 @@ rm /etc/apt/sources.list.d/centreon-business.list -3. Installez le dépôt business en 25.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. +3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. 4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). @@ -183,7 +183,7 @@ rm /var/lib/centreon-broker/* -f ### Montée de version de PHP -Centreon 25.10 utilise PHP en version 8.2. +Centreon 26.10 utilise PHP en version 8.4. @@ -485,14 +485,14 @@ mise à jour. - adresse : 10.25.XX.XX - port : 80 - - version : 25.10 + - version : 26.10 - identifiant : Admin - mot de passe : xxxxx 2. Entrez la requête suivante : ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ + curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --data '{ @@ -638,7 +638,7 @@ Exécutez la commande suivante : ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` @@ -646,7 +646,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list apt update ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-04.md index be2caacaf11b..78a2b3555729 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-04.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 23.04 vers la version 25.10. +Centreon depuis la version 23.04 vers la version 26.10. > La version 23.04 n'est plus supportée. La montée de version à partir de cette version n'a pas été testée par l'équipe d'assurance qualité de Centreon. @@ -16,7 +16,7 @@ Centreon depuis la version 23.04 vers la version 25.10. > / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). > Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 25.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian 11, vous devez d'abord migrer en Debian 12 avant d'upgrader Centreon. Voir [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. @@ -102,7 +102,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -128,7 +128,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v 3. Installez le nouveau dépôt : ```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` @@ -139,7 +139,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -189,7 +189,7 @@ rm /etc/apt/sources.list.d/centreon-business.list -3. Installez le dépôt business en 25.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. +3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. 4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). @@ -207,7 +207,7 @@ rm /var/lib/centreon-broker/* -f ### Montée de version de PHP -Centreon 25.10 utilise PHP en version 8.2. +Centreon 26.10 utilise PHP en version 8.4. @@ -585,14 +585,14 @@ mise à jour. - adresse : 10.25.XX.XX - port : 80 - - version : 25.10 + - version : 26.10 - identifiant : Admin - mot de passe : xxxxx 2. Entrez la requête suivante : ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ + curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --data '{ @@ -746,7 +746,7 @@ Exécutez la commande suivante : ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` @@ -755,7 +755,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` @@ -763,7 +763,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list apt update ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-10.md index e251a319cb3f..999cdaa8fe5d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-10.md @@ -6,14 +6,14 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 23.10 vers la version 25.10. +Centreon depuis la version 23.10 vers la version 26.10. > Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. Dans votre architecture, tous les serveurs doivent avoir la même version de Centreon. De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). > Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux > / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 25.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian 11, vous devez d'abord migrer en Debian 12 avant d'upgrader Centreon. Voir [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. @@ -99,7 +99,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -125,7 +125,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v 3. Installez le nouveau dépôt : ```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` @@ -136,7 +136,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -186,7 +186,7 @@ rm /etc/apt/sources.list.d/centreon-business.list -3. Installez le dépôt business en 25.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. +3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. 4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). @@ -204,7 +204,7 @@ rm /var/lib/centreon-broker/* -f ### Montée de version de PHP -Centreon 25.10 utilise PHP en version 8.2. +Centreon 26.10 utilise PHP en version 8.4. @@ -582,14 +582,14 @@ mise à jour. - adresse : 10.25.XX.XX - port : 80 - - version : 25.10 + - version : 26.10 - identifiant : Admin - mot de passe : xxxxx 2. Entrez la requête suivante : ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ + curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --data '{ @@ -773,7 +773,7 @@ Exécutez la commande suivante : ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` @@ -782,7 +782,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` @@ -790,7 +790,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list apt update ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-04.md index 6cc50fcbda42..f5e1fb7185d3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-04.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 24.04 vers la version 25.10. +Centreon depuis la version 24.04 vers la version 26.10. > Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. > @@ -17,7 +17,7 @@ Centreon depuis la version 24.04 vers la version 25.10. > Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). > Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 25.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian 11, vous devez d'abord migrer en Debian 12 avant d'upgrader Centreon. Voir [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. @@ -105,7 +105,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -131,7 +131,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v 3. Installez le nouveau dépôt : ```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` @@ -142,7 +142,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -192,7 +192,7 @@ rm /etc/apt/sources.list.d/centreon-business.list -3. Installez le dépôt business en 25.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. +3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. 4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). @@ -210,7 +210,7 @@ rm /var/lib/centreon-broker/* -f ### Montée de version de PHP -Centreon 25.10 utilise PHP en version 8.2. +Centreon 26.10 utilise PHP en version 8.4. @@ -589,14 +589,14 @@ mise à jour. - adresse : 10.25.XX.XX - port : 80 - - version : 25.10 + - version : 26.10 - identifiant : Admin - mot de passe : xxxxx 2. Entrez la requête suivante : ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ + curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --data '{ @@ -776,7 +776,7 @@ Exécutez la commande suivante : ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` @@ -785,7 +785,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` @@ -793,7 +793,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list apt update ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-10.md index 18699d407f94..55786a217a9c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-10.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 24.10 vers la version 25.10. +Centreon depuis la version 24.10 vers la version 26.10. > Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. > @@ -19,7 +19,7 @@ Centreon depuis la version 24.10 vers la version 25.10. > Si vous utilisiez MySQL 8.0, prévoyez de [passer à MySQL 8.4](upgrade-mysql.md) avant la fin du support de la version 8.0, prévue fin avril 2026. -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 25.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). ## Prérequis @@ -93,7 +93,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v ```shell dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo + dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo systemctl stop cbd dnf clean all --enablerepo=* ``` @@ -120,7 +120,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v 3. Installez le nouveau dépôt : ```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` @@ -131,7 +131,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -181,7 +181,7 @@ rm /etc/apt/sources.list.d/centreon-business.list -3. Installez le dépôt business en 25.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. +3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. 4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). @@ -518,14 +518,14 @@ mise à jour. - adresse : 10.25.XX.XX - port : 80 - - version : 24.10 + - version : 26.10 - identifiant : Admin - mot de passe : xxxxx 2. Entrez la requête suivante : ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ + curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --data '{ @@ -705,7 +705,7 @@ Exécutez la commande suivante : ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo ``` @@ -714,7 +714,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` @@ -722,7 +722,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list apt update ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-25-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-25-10.md index a13a7c1c6a16..b9eaf6b89604 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 24.10 vers la version 25.10. +Centreon depuis la version 25.10 vers la version 26.10. > Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. > @@ -17,9 +17,7 @@ Centreon depuis la version 24.10 vers la version 25.10. > Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). > Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. -> Si vous utilisiez MySQL 8.0, prévoyez de [passer à MySQL 8.4](upgrade-mysql.md) avant la fin du support de la version 8.0, prévue fin avril 2026. - -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 25.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Si vous utilisiez MySQL 8.0, vous devez [passer à MySQL 8.4](upgrade-mysql.md). ## Prérequis @@ -100,25 +98,25 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v 2. Supprimez les fichiers des dépôts : ```shell - rm /etc/yum.repos.d/centreon-24.10.repo + rm /etc/yum.repos.d/centreon-25.10.repo rm /etc/yum.repos.d/centreon.repo ``` 3. Installez le nouveau dépôt : ```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` -1. Mettez à jour votre Centreon 24.10 jusqu'à la dernière version mineure. +1. Mettez à jour votre Centreon 25.10 jusqu'à la dernière version mineure. 2. Exécutez les commandes suivantes : ```shell -rm -f /etc/apt/sources.list.d/centreon-25.10-stable.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list +rm -f /etc/apt/sources.list.d/centreon-26.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -503,14 +501,14 @@ mise à jour. - adresse : 10.25.XX.XX - port : 80 - - version : 24.10 + - version : 26.10 - identifiant : Admin - mot de passe : xxxxx 2. Entrez la requête suivante : ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ + curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ --header 'Content-Type: application/json' \ --header 'Accept: application/json' \ --data '{ @@ -669,7 +667,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell dnf install -y dnf-plugins-core && \ rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` @@ -677,7 +675,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/e ```shell rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list apt update ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md index 6c32163070ff..ae8a4830bf22 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md @@ -21,6 +21,7 @@ Lorsque vous passez d'une version majeure de Centreon à une autre, vous devez : | Centreon | MariaDB | |----------|---------| +| 26.10 | 11.8 | | 25.10 | 10.11 | | 24.10 | 10.11 | | 24.04 | 10.11 | diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mysql.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mysql.md index c9e3be61e05e..7db7a7343f33 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mysql.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mysql.md @@ -5,7 +5,7 @@ title: Mettre à jour MySQL import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Si vous utilisiez Centreon 24.04 ou 24.10 avec MySQL, sachez que le support de MySQL 8.0 prendra fin en avril 2026. Assurez-vous que votre Centreon utilise toujours [une version supportée de MySQL](#versions-de-mysql-compatibles-avec-centreon-2510). +Si vous utilisiez Centreon 24.04 ou 24.10 avec MySQL, sachez que le support de MySQL 8.0 prendra fin en avril 2026. Assurez-vous que votre Centreon utilise toujours [une version supportée de MySQL](#versions-de-mysql-compatibles-avec-centreon-2610). Vous pouvez potentiellement avoir plusieurs bases MySQL dans votre architecture. Le serveur central a une base, chaque serveur distant a une base, et les modules MBI et MAP ont chacun une base dédiée. Dans une architecture, toutes les bases doivent avoir la même version de MySQL. @@ -13,10 +13,9 @@ Vous pouvez potentiellement avoir plusieurs bases MySQL dans votre architecture. Ne mettez pas à jour votre version de Centreon et votre version de MySQL en même temps. Vous pouvez effectuer les deux mises à jour l'une après l'autre dans l'ordre que vous souhaitez, mais assurez-vous que la première procédure de mise à jour soit entièrement terminée avant d'effectuer la seconde. -## Versions de MySQL compatibles avec Centreon 25.10 +## Versions de MySQL compatibles avec Centreon 26.10 -* MySQL 8.4 est recommandé pour les nouvelles installations. -* MySQL 8.0 peut encore être utilisé jusqu'à la fin de son support (fin avril 2026), mais après cette date, vous devrez passer à MySQL 8.4. +* MySQL 8.4 ## Connaître la version de MySQL From 5ac31e7a9b1940ae45deef25f5e3c0ce131adb5a Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 3 Jul 2026 18:48:47 +0200 Subject: [PATCH 003/179] Test update matrix topic --- versioned_sidebars/version-26.10-sidebars.json | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/versioned_sidebars/version-26.10-sidebars.json b/versioned_sidebars/version-26.10-sidebars.json index 0df4a804f04f..ae5562863b21 100644 --- a/versioned_sidebars/version-26.10-sidebars.json +++ b/versioned_sidebars/version-26.10-sidebars.json @@ -1124,6 +1124,10 @@ { "type": "doc", "id": "upgrade/introduction" + }, + { + "type": "doc", + "id": "upgrade/upgrade-matrix" }, { "type": "doc", From fe1381945ef10ba749029266a1d99869ce5eebe8 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 3 Jul 2026 20:55:45 +0200 Subject: [PATCH 004/179] Add upgrade matrix --- .../version-24.10/upgrade/upgrade-matrix.md | 185 +++++++++++++++ .../version-25.10/upgrade/upgrade-matrix.md | 201 ++++++++++++++++ .../version-26.10/upgrade/upgrade-matrix.md | 223 ++++++++++++++++++ .../version-24.10-sidebars.json | 4 + .../version-25.10-sidebars.json | 4 + 5 files changed, 617 insertions(+) create mode 100644 versioned_docs/version-24.10/upgrade/upgrade-matrix.md create mode 100644 versioned_docs/version-25.10/upgrade/upgrade-matrix.md create mode 100644 versioned_docs/version-26.10/upgrade/upgrade-matrix.md diff --git a/versioned_docs/version-24.10/upgrade/upgrade-matrix.md b/versioned_docs/version-24.10/upgrade/upgrade-matrix.md new file mode 100644 index 000000000000..a20c62f74675 --- /dev/null +++ b/versioned_docs/version-24.10/upgrade/upgrade-matrix.md @@ -0,0 +1,185 @@ +--- +id: upgrade-matrix +title: Matrice des montées de version possibles +--- + +Pour rappel, les [OS supportés en version 24.10](../installation/compatibility.md#operating-systems) sont les suivants : + +* RHEL/Oracle Linux/Alma Linux 8 +* RHEL/Oracle/Alma Linux 9 +* Debian 12 (bookworm) + +Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure. Pour toute autre version, vous devrez effectuer une [migration](../migrate/introduction.md). + +## Montée de version ou migration? + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Version de départOS supporté à l'époqueOS toujours supporté en 24.10 ?Procédure à suivre
24.04RHEL/Oracle Linux/Alma Linux 8OUIProcédure de montée de version
RHEL/Oracle/Alma Linux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
Debian 12 "bookworm"OUIProcédure de montée de version
23.10RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
RHEL/Oracle/AlmaLinux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
23.04RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
RHEL/Oracle/AlmaLinux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
22.10CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
22.04RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
Debian 11 "bullseye"NONProcédure de migration depuis Debian
21.10CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 8OUIProcédure de montée de version
21.04CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 8OUIProcédure de montée de version
20.10CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 8OUIProcédure de montée de version
20.04CentOS 7NONProcédure de migration depuis EL
RHEL 7NONProcédure de migration depuis EL
+ +## Cycle de vie des versions + +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). diff --git a/versioned_docs/version-25.10/upgrade/upgrade-matrix.md b/versioned_docs/version-25.10/upgrade/upgrade-matrix.md new file mode 100644 index 000000000000..d2eed6ca30dd --- /dev/null +++ b/versioned_docs/version-25.10/upgrade/upgrade-matrix.md @@ -0,0 +1,201 @@ +--- +id: upgrade-matrix +title: Matrice des montées de version possibles +--- + +Pour rappel, les [OS supportés en version 25.10](../installation/compatibility.md#operating-systems) sont les suivants : + +* RHEL/Oracle Linux/Alma Linux 8 +* RHEL/Oracle/Alma Linux 9 +* Debian 12 (bookworm) + +Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure. Pour toute autre version, vous devrez effectuer une [migration](../migrate/introduction.md). + +## Montée de version ou migration? + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Version de départOS supporté à l'époqueOS toujours supporté en 25.10 ?Procédure à suivre
24.10RHEL/Oracle Linux/Alma Linux 8OUIProcédure de montée de version
RHEL/Oracle Linux/Alma Linux 9OUIProcédure de montée de version
Debian 12 "bookworm"OUIProcédure de montée de version
24.04RHEL/Oracle Linux/Alma Linux 8OUIProcédure de montée de version
RHEL/OracleLinux/Alma Linux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
Debian 12 "bookworm"OUIProcédure de montée de version
23.10RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
RHEL/OracleLinux/AlmaLinux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
23.04RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
RHEL/OracleLinux/AlmaLinux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
22.10CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
22.04RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
Debian 11 "bullseye"NONProcédure de migration depuis Debian
21.10CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 8OUIProcédure de montée de version
21.04CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 8OUIProcédure de montée de version
20.10CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 8OUIProcédure de montée de version
20.04CentOS 7NONProcédure de migration depuis EL
RHEL 7NONProcédure de migration depuis EL
+ +## Cycle de vie des versions + +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). diff --git a/versioned_docs/version-26.10/upgrade/upgrade-matrix.md b/versioned_docs/version-26.10/upgrade/upgrade-matrix.md new file mode 100644 index 000000000000..27fe5a9d48d0 --- /dev/null +++ b/versioned_docs/version-26.10/upgrade/upgrade-matrix.md @@ -0,0 +1,223 @@ +--- +id: upgrade-matrix +title: Matrice des montées de version possibles +--- + +Pour rappel, les [OS supportés en version 26.10](../installation/compatibility.md#operating-systems) sont les suivants : + +* RHEL/Oracle Linux/Alma Linux 9 +* RHEL/Oracle Linux/Alma Linux 10 +* Debian 13 (trixie) + +Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 23.04 ou supérieure, avec certains OS. Pour toute autre version et OS, vous devrez effectuer une [migration](../migrate/introduction.md). + +## Montée de version ou migration? + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Version de départOS supporté à l'époqueOS toujours supporté en 26.10 ?Procédure à suivre
25.10RHEL/Oracle Linux/Alma Linux 8NONProcédure de migration depuis EL
RHEL/Oracle/Alma Linux 9OUIProcédure de montée de version
Debian 12 "bookworm"NONProcédure de migration depuis Debian
24.10RHEL/Oracle Linux/Alma Linux 8NONProcédure de migration depuis EL
RHEL/Oracle/Alma Linux 9OUIProcédure de montée de version
Debian 12 "bookworm"NONProcédure de migration depuis Debian
24.04RHEL/Oracle Linux/Alma Linux 8NONProcédure de migration depuis EL
RHEL/Oracle/Alma Linux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
Debian 12 "bookworm"NONProcédure de migration depuis Debian
23.10RHEL/Oracle Linux/AlmaLinux 8NONProcédure de migration depuis EL
RHEL/Oracle/AlmaLinux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
23.04RHEL/Oracle Linux/AlmaLinux 8NONProcédure de migration depuis EL
RHEL/Oracle/AlmaLinux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
22.10 et antérieuresVoir documentations correspondantesNONProcédure de migration depuis EL ou Debian
+ +## Cycle de vie des versions + +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). diff --git a/versioned_sidebars/version-24.10-sidebars.json b/versioned_sidebars/version-24.10-sidebars.json index b3cd93cea752..4b7abc6b0f6d 100644 --- a/versioned_sidebars/version-24.10-sidebars.json +++ b/versioned_sidebars/version-24.10-sidebars.json @@ -1069,6 +1069,10 @@ "type": "doc", "id": "upgrade/introduction" }, + { + "type": "doc", + "id": "upgrade/upgrade-matrix" + }, { "type": "doc", "id": "upgrade/upgrade-from-24-04" diff --git a/versioned_sidebars/version-25.10-sidebars.json b/versioned_sidebars/version-25.10-sidebars.json index ebc3b128d6c5..c29b11b62042 100644 --- a/versioned_sidebars/version-25.10-sidebars.json +++ b/versioned_sidebars/version-25.10-sidebars.json @@ -1125,6 +1125,10 @@ "type": "doc", "id": "upgrade/introduction" }, + { + "type": "doc", + "id": "upgrade/upgrade-matrix" + }, { "type": "doc", "id": "upgrade/upgrade-from-24-10" From 5f33c0823d266a0ce521c5bd45cf3a7d0a7c65d4 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 3 Jul 2026 21:07:18 +0200 Subject: [PATCH 005/179] Update --- versioned_docs/version-24.10/upgrade/upgrade-matrix.md | 2 +- versioned_docs/version-25.10/upgrade/upgrade-matrix.md | 2 +- versioned_docs/version-26.10/upgrade/upgrade-matrix.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/versioned_docs/version-24.10/upgrade/upgrade-matrix.md b/versioned_docs/version-24.10/upgrade/upgrade-matrix.md index a20c62f74675..a36672cf34bc 100644 --- a/versioned_docs/version-24.10/upgrade/upgrade-matrix.md +++ b/versioned_docs/version-24.10/upgrade/upgrade-matrix.md @@ -9,7 +9,7 @@ Pour rappel, les [OS supportés en version 24.10](../installation/compatibility. * RHEL/Oracle/Alma Linux 9 * Debian 12 (bookworm) -Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure. Pour toute autre version, vous devrez effectuer une [migration](../migrate/introduction.md). +Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 8 ou 9, ou Debian 12. Pour toute autre version ou OS, vous devrez effectuer une [migration](../migrate/introduction.md). ## Montée de version ou migration? diff --git a/versioned_docs/version-25.10/upgrade/upgrade-matrix.md b/versioned_docs/version-25.10/upgrade/upgrade-matrix.md index d2eed6ca30dd..257c94a0bff7 100644 --- a/versioned_docs/version-25.10/upgrade/upgrade-matrix.md +++ b/versioned_docs/version-25.10/upgrade/upgrade-matrix.md @@ -9,7 +9,7 @@ Pour rappel, les [OS supportés en version 25.10](../installation/compatibility. * RHEL/Oracle/Alma Linux 9 * Debian 12 (bookworm) -Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure. Pour toute autre version, vous devrez effectuer une [migration](../migrate/introduction.md). +Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 8 ou 9, ou Debian 12. Pour toute autre version ou OS, vous devrez effectuer une [migration](../migrate/introduction.md). ## Montée de version ou migration? diff --git a/versioned_docs/version-26.10/upgrade/upgrade-matrix.md b/versioned_docs/version-26.10/upgrade/upgrade-matrix.md index 27fe5a9d48d0..24ca6abc7b2f 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-matrix.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-matrix.md @@ -9,7 +9,7 @@ Pour rappel, les [OS supportés en version 26.10](../installation/compatibility. * RHEL/Oracle Linux/Alma Linux 10 * Debian 13 (trixie) -Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 23.04 ou supérieure, avec certains OS. Pour toute autre version et OS, vous devrez effectuer une [migration](../migrate/introduction.md). +Cela signifie qu'une simple montée de version n'est possible que si vous utilisiez une version 23.04 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 9. Pour toute autre version et OS, vous devrez effectuer une [migration](../migrate/introduction.md). ## Montée de version ou migration? From 0139611a14085ef62e88a7c229ca9c719de1f4a7 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 3 Jul 2026 21:53:54 +0200 Subject: [PATCH 006/179] Change .md to .mdx --- .../version-26.10/upgrade/upgrade-matrix.md | 223 ------------------ .../version-26.10/upgrade/upgrade-matrix.mdx | 137 +++++++++++ 2 files changed, 137 insertions(+), 223 deletions(-) delete mode 100644 versioned_docs/version-26.10/upgrade/upgrade-matrix.md create mode 100644 versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx diff --git a/versioned_docs/version-26.10/upgrade/upgrade-matrix.md b/versioned_docs/version-26.10/upgrade/upgrade-matrix.md deleted file mode 100644 index 24ca6abc7b2f..000000000000 --- a/versioned_docs/version-26.10/upgrade/upgrade-matrix.md +++ /dev/null @@ -1,223 +0,0 @@ ---- -id: upgrade-matrix -title: Matrice des montées de version possibles ---- - -Pour rappel, les [OS supportés en version 26.10](../installation/compatibility.md#operating-systems) sont les suivants : - -* RHEL/Oracle Linux/Alma Linux 9 -* RHEL/Oracle Linux/Alma Linux 10 -* Debian 13 (trixie) - -Cela signifie qu'une simple montée de version n'est possible que si vous utilisiez une version 23.04 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 9. Pour toute autre version et OS, vous devrez effectuer une [migration](../migrate/introduction.md). - -## Montée de version ou migration? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Version de départOS supporté à l'époqueOS toujours supporté en 26.10 ?Procédure à suivre
25.10RHEL/Oracle Linux/Alma Linux 8NONProcédure de migration depuis EL
RHEL/Oracle/Alma Linux 9OUIProcédure de montée de version
Debian 12 "bookworm"NONProcédure de migration depuis Debian
24.10RHEL/Oracle Linux/Alma Linux 8NONProcédure de migration depuis EL
RHEL/Oracle/Alma Linux 9OUIProcédure de montée de version
Debian 12 "bookworm"NONProcédure de migration depuis Debian
24.04RHEL/Oracle Linux/Alma Linux 8NONProcédure de migration depuis EL
RHEL/Oracle/Alma Linux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
Debian 12 "bookworm"NONProcédure de migration depuis Debian
23.10RHEL/Oracle Linux/AlmaLinux 8NONProcédure de migration depuis EL
RHEL/Oracle/AlmaLinux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
23.04RHEL/Oracle Linux/AlmaLinux 8NONProcédure de migration depuis EL
RHEL/Oracle/AlmaLinux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
22.10 et antérieuresVoir documentations correspondantesNONProcédure de migration depuis EL ou Debian
- -## Cycle de vie des versions - -[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). diff --git a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx new file mode 100644 index 000000000000..c0b2aca0f2c4 --- /dev/null +++ b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -0,0 +1,137 @@ +--- +id: upgrade-matrix +title: Matrice des montées de version possibles +--- + +import React, { useState } from 'react'; + +export const UpgradeTable = () => { + const [version, setVersion] = useState(''); + const [os, setOs] = useState(''); + const [compat, setCompat] = useState(''); + + const rows = [ + { version: '25.10', os: 'RHEL/Oracle/Alma Linux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '25.10', os: 'RHEL/Oracle/Alma Linux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-25-10.md' }, + { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '24.10', os: 'RHEL/Oracle/Alma Linux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '24.10', os: 'RHEL/Oracle/Alma Linux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-10.md' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'RHEL/Oracle/Alma Linux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'RHEL/Oracle/Alma Linux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '22.10 et antérieures', os: 'Voir documentations correspondantes', compat: 'NON', proc: 'Migration depuis EL ou Debian', href: '../migrate/introduction.md' }, + ]; + + const filtered = rows.filter(r => + (!version || r.version === version) && + (!os || r.os.includes(os)) && + (!compat || r.compat === compat) + ); + + return ( +
+
+ {[ + { id: 'version', value: version, setter: setVersion, label: 'Toutes les versions', options: ['25.10','24.10','24.04','23.10','23.04','22.10 et antérieures'] }, + { id: 'os', value: os, setter: setOs, label: 'Tous les OS', options: ['RHEL/Oracle/Alma Linux 8','RHEL/Oracle/Alma Linux 9','Debian 11','Debian 12'] }, + { id: 'compat', value: compat, setter: setCompat, label: 'Compatibilité 26.10', options: null }, + ].map(f => ( + + ))} +
+ +

+ {filtered.length} résultat{filtered.length > 1 ? 's' : ''} +

+ + + + + {['Version de départ', 'OS de départ', 'OS supporté en 26.10', 'Procédure à suivre'].map(h => ( + + ))} + + + + {filtered.map((r, i) => ( + + + + + + + ))} + +
{h}
{r.version}{r.os} + + {r.compat} + + + {r.proc} +
+
+ ); +}; + +Pour rappel, les [OS supportés en version 26.10](../installation/compatibility.md#operating-systems) sont les suivants : + +* RHEL/Oracle Linux/Alma Linux 9 +* RHEL/Oracle Linux/Alma Linux 10 +* Debian 13 (trixie) + +Cela signifie qu'une simple montée de version n'est possible que si vous utilisiez une version 23.04 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 9. Pour toute autre version et OS, vous devrez effectuer une [migration](../migrate/introduction.md). + +## Montée de version ou migration ? + + + +## Cycle de vie des versions + +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). \ No newline at end of file From 7d67333c133cb4bd6243dbac8138ea4a4f0884db Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 3 Jul 2026 22:16:59 +0200 Subject: [PATCH 007/179] Update --- .../version-24.10/upgrade/upgrade-matrix.md | 185 ---------------- .../version-24.10/upgrade/upgrade-matrix.mdx | 154 ++++++++++++++ .../version-25.10/upgrade/upgrade-matrix.md | 201 ------------------ .../version-25.10/upgrade/upgrade-matrix.mdx | 157 ++++++++++++++ .../version-26.10/upgrade/upgrade-matrix.mdx | 12 +- 5 files changed, 317 insertions(+), 392 deletions(-) delete mode 100644 versioned_docs/version-24.10/upgrade/upgrade-matrix.md create mode 100644 versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx delete mode 100644 versioned_docs/version-25.10/upgrade/upgrade-matrix.md create mode 100644 versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx diff --git a/versioned_docs/version-24.10/upgrade/upgrade-matrix.md b/versioned_docs/version-24.10/upgrade/upgrade-matrix.md deleted file mode 100644 index a36672cf34bc..000000000000 --- a/versioned_docs/version-24.10/upgrade/upgrade-matrix.md +++ /dev/null @@ -1,185 +0,0 @@ ---- -id: upgrade-matrix -title: Matrice des montées de version possibles ---- - -Pour rappel, les [OS supportés en version 24.10](../installation/compatibility.md#operating-systems) sont les suivants : - -* RHEL/Oracle Linux/Alma Linux 8 -* RHEL/Oracle/Alma Linux 9 -* Debian 12 (bookworm) - -Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 8 ou 9, ou Debian 12. Pour toute autre version ou OS, vous devrez effectuer une [migration](../migrate/introduction.md). - -## Montée de version ou migration? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Version de départOS supporté à l'époqueOS toujours supporté en 24.10 ?Procédure à suivre
24.04RHEL/Oracle Linux/Alma Linux 8OUIProcédure de montée de version
RHEL/Oracle/Alma Linux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
Debian 12 "bookworm"OUIProcédure de montée de version
23.10RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
RHEL/Oracle/AlmaLinux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
23.04RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
RHEL/Oracle/AlmaLinux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
22.10CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
22.04RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
Debian 11 "bullseye"NONProcédure de migration depuis Debian
21.10CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 8OUIProcédure de montée de version
21.04CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 8OUIProcédure de montée de version
20.10CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 8OUIProcédure de montée de version
20.04CentOS 7NONProcédure de migration depuis EL
RHEL 7NONProcédure de migration depuis EL
- -## Cycle de vie des versions - -[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). diff --git a/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx new file mode 100644 index 000000000000..2e84cce261d8 --- /dev/null +++ b/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx @@ -0,0 +1,154 @@ +--- +id: upgrade-matrix +title: Matrice des montées de version possibles +--- + +import React, { useState } from 'react'; + +export const UpgradeTable = () => { + const [version, setVersion] = useState(''); + const [os, setOs] = useState(''); + const [compat, setCompat] = useState(''); + + const rows = [ + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'RHEL/Oracle Linux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-10.md' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'RHEL/Oracle Linux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04.md' }, + { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'RHEL/Oracle Linux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'RHEL/Oracle Linux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'RHEL/Oracle Linux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10.md' }, + { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.04', os: 'RHEL/Oracle Linux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.04', os: 'RHEL/Oracle Linux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04.md' }, + { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.10', os: 'RHEL/Oracle Linux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.10', os: 'RHEL/Oracle Linux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10.md' }, + { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + ]; + + const versions = [...new Set(rows.map(r => r.version))]; + const osList = [...new Set(rows.map(r => r.os))]; + + const filtered = rows.filter(r => + (!version || r.version === version) && + (!os || r.os === os) && + (!compat || r.compat === compat) + ); + + const selectStyle = { + fontSize: 13, + padding: '6px 12px', + borderRadius: 4, + border: '1px solid var(--ifm-color-emphasis-300)', + background: 'var(--ifm-background-surface-color)', + color: 'var(--ifm-font-color-base)', + cursor: 'pointer', + }; + + const thStyle = { + textAlign: 'left', + padding: '10px 16px', + background: 'var(--ifm-color-emphasis-100)', + color: 'var(--ifm-color-emphasis-700)', + fontWeight: 600, + fontSize: 12, + textTransform: 'uppercase', + letterSpacing: '0.04em', + borderBottom: '1px solid var(--ifm-color-emphasis-300)', + }; + + const tdStyle = { + padding: '10px 16px', + borderBottom: '1px solid var(--ifm-color-emphasis-200)', + verticalAlign: 'middle', + }; + + return ( +
+
+ + + +
+ +

+ {filtered.length} résultat{filtered.length > 1 ? 's' : ''} +

+ + + + + + + + + + + + {filtered.map((r, i) => ( + + + + + + + ))} + +
Version de départOS supporté à l'époqueOS toujours supporté en 24.10 ?Procédure à suivre
{r.version}{r.os} + + {r.compat} + + {r.proc}
+
+ ); +}; + +Pour rappel, les [OS supportés en version 24.10](../installation/compatibility.md#operating-systems) sont les suivants : + +* RHEL/Oracle Linux/Alma Linux 8 +* RHEL/Oracle/Alma Linux 9 +* Debian 12 (bookworm) + +Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 8 ou 9, ou Debian 12. Pour toute autre version ou OS, vous devrez effectuer une [migration](../migrate/introduction.md). + +## Montée de version ou migration ? + + + +## Cycle de vie des versions + +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). \ No newline at end of file diff --git a/versioned_docs/version-25.10/upgrade/upgrade-matrix.md b/versioned_docs/version-25.10/upgrade/upgrade-matrix.md deleted file mode 100644 index 257c94a0bff7..000000000000 --- a/versioned_docs/version-25.10/upgrade/upgrade-matrix.md +++ /dev/null @@ -1,201 +0,0 @@ ---- -id: upgrade-matrix -title: Matrice des montées de version possibles ---- - -Pour rappel, les [OS supportés en version 25.10](../installation/compatibility.md#operating-systems) sont les suivants : - -* RHEL/Oracle Linux/Alma Linux 8 -* RHEL/Oracle/Alma Linux 9 -* Debian 12 (bookworm) - -Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 8 ou 9, ou Debian 12. Pour toute autre version ou OS, vous devrez effectuer une [migration](../migrate/introduction.md). - -## Montée de version ou migration? - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Version de départOS supporté à l'époqueOS toujours supporté en 25.10 ?Procédure à suivre
24.10RHEL/Oracle Linux/Alma Linux 8OUIProcédure de montée de version
RHEL/Oracle Linux/Alma Linux 9OUIProcédure de montée de version
Debian 12 "bookworm"OUIProcédure de montée de version
24.04RHEL/Oracle Linux/Alma Linux 8OUIProcédure de montée de version
RHEL/OracleLinux/Alma Linux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
Debian 12 "bookworm"OUIProcédure de montée de version
23.10RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
RHEL/OracleLinux/AlmaLinux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
23.04RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
RHEL/OracleLinux/AlmaLinux 9OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
22.10CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
Debian 11 "bullseye"NONProcédure de migration depuis Debian
22.04RHEL/Oracle Linux/AlmaLinux 8OUIProcédure de montée de version
CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
Debian 11 "bullseye"NONProcédure de migration depuis Debian
21.10CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 8OUIProcédure de montée de version
21.04CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 8OUIProcédure de montée de version
20.10CentOS 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 7NONProcédure de migration depuis EL
RHEL/Oracle Linux 8OUIProcédure de montée de version
20.04CentOS 7NONProcédure de migration depuis EL
RHEL 7NONProcédure de migration depuis EL
- -## Cycle de vie des versions - -[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). diff --git a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx new file mode 100644 index 000000000000..7a4890903eba --- /dev/null +++ b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx @@ -0,0 +1,157 @@ +--- +id: upgrade-matrix +title: Matrice des montées de version possibles +--- + +import React, { useState } from 'react'; + +export const UpgradeTable = () => { + const [version, setVersion] = useState(''); + const [os, setOs] = useState(''); + const [compat, setCompat] = useState(''); + + const rows = [ + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10.md' }, + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10.md' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10.md' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-10.md' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04.md' }, + { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10.md' }, + { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04.md' }, + { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10.md' }, + { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + ]; + + const versions = [...new Set(rows.map(r => r.version))]; + const osList = [...new Set(rows.map(r => r.os))]; + + const filtered = rows.filter(r => + (!version || r.version === version) && + (!os || r.os === os) && + (!compat || r.compat === compat) + ); + + const selectStyle = { + fontSize: 13, + padding: '6px 12px', + borderRadius: 4, + border: '1px solid var(--ifm-color-emphasis-300)', + background: 'var(--ifm-background-surface-color)', + color: 'var(--ifm-font-color-base)', + cursor: 'pointer', + }; + + const thStyle = { + textAlign: 'left', + padding: '10px 16px', + background: 'var(--ifm-color-emphasis-100)', + color: 'var(--ifm-color-emphasis-700)', + fontWeight: 600, + fontSize: 12, + textTransform: 'uppercase', + letterSpacing: '0.04em', + borderBottom: '1px solid var(--ifm-color-emphasis-300)', + }; + + const tdStyle = { + padding: '10px 16px', + borderBottom: '1px solid var(--ifm-color-emphasis-200)', + verticalAlign: 'middle', + }; + + return ( +
+
+ + + +
+ +

+ {filtered.length} résultat{filtered.length > 1 ? 's' : ''} +

+ + + + + + + + + + + + {filtered.map((r, i) => ( + + + + + + + ))} + +
Version de départOS supporté à l'époqueOS toujours supporté en 25.10 ?Procédure à suivre
{r.version}{r.os} + + {r.compat} + + {r.proc}
+
+ ); +}; + +Pour rappel, les [OS supportés en version 25.10](../installation/compatibility.md#operating-systems) sont les suivants : + +* RHEL/Oracle Linux/Alma Linux 8 +* RHEL/Oracle/Alma Linux 9 +* Debian 12 (bookworm) + +Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 8 ou 9, ou Debian 12. Pour toute autre version ou OS, vous devrez effectuer une [migration](../migrate/introduction.md). + +## Montée de version ou migration ? + + + +## Cycle de vie des versions + +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). \ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx index c0b2aca0f2c4..2197a53fa627 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -11,14 +11,14 @@ export const UpgradeTable = () => { const [compat, setCompat] = useState(''); const rows = [ - { version: '25.10', os: 'RHEL/Oracle/Alma Linux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '25.10', os: 'RHEL/Oracle/Alma Linux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-25-10.md' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-25-10.md' }, { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '24.10', os: 'RHEL/Oracle/Alma Linux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '24.10', os: 'RHEL/Oracle/Alma Linux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-10.md' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-10.md' }, { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'RHEL/Oracle/Alma Linux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'RHEL/Oracle/Alma Linux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-04.md' }, { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, From 8af70e4519204615ce8f27389934c8682e6a8447 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 09:22:30 +0200 Subject: [PATCH 008/179] Update --- .../version-24.10/upgrade/upgrade-matrix.mdx | 20 +++++++++---------- .../version-25.10/upgrade/upgrade-matrix.mdx | 4 ++-- .../version-26.10/upgrade/upgrade-matrix.mdx | 2 +- 3 files changed, 13 insertions(+), 13 deletions(-) diff --git a/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx index 2e84cce261d8..c0c5f75af9c7 100644 --- a/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx @@ -22,22 +22,22 @@ export const UpgradeTable = () => { { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'RHEL/Oracle Linux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-10.md' }, { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'RHEL/Oracle Linux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04.md' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04.md' }, { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'RHEL/Oracle Linux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'RHEL/Oracle Linux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'RHEL/Oracle Linux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10.md' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10.md' }, { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.04', os: 'RHEL/Oracle Linux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.04', os: 'RHEL/Oracle Linux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04.md' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04.md' }, { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '20.10', os: 'RHEL/Oracle Linux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '20.10', os: 'RHEL/Oracle Linux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10.md' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10.md' }, { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, ]; @@ -137,7 +137,7 @@ export const UpgradeTable = () => { ); }; -Pour rappel, les [OS supportés en version 24.10](../installation/compatibility.md#operating-systems) sont les suivants : +Pour rappel, les [OS supportés en version 24.10](../installation/compatibility.md) sont les suivants : * RHEL/Oracle Linux/Alma Linux 8 * RHEL/Oracle/Alma Linux 9 diff --git a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx index 7a4890903eba..b3fda0492224 100644 --- a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx @@ -140,10 +140,10 @@ export const UpgradeTable = () => { ); }; -Pour rappel, les [OS supportés en version 25.10](../installation/compatibility.md#operating-systems) sont les suivants : +Pour rappel, les [OS supportés en version 25.10](../installation/compatibility.md) sont les suivants : * RHEL/Oracle Linux/Alma Linux 8 -* RHEL/Oracle/Alma Linux 9 +* RHEL/Oracle Linux/Alma Linux 9 * Debian 12 (bookworm) Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 8 ou 9, ou Debian 12. Pour toute autre version ou OS, vous devrez effectuer une [migration](../migrate/introduction.md). diff --git a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx index 2197a53fa627..8082cbe1411d 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -120,7 +120,7 @@ export const UpgradeTable = () => { ); }; -Pour rappel, les [OS supportés en version 26.10](../installation/compatibility.md#operating-systems) sont les suivants : +Pour rappel, les [OS supportés en version 26.10](../installation/compatibility.md) sont les suivants : * RHEL/Oracle Linux/Alma Linux 9 * RHEL/Oracle Linux/Alma Linux 10 From ea6407a83cbfcbec60c6a11178587ffe0a4de9b6 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 11:39:19 +0200 Subject: [PATCH 009/179] Remove link --- versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx | 2 +- versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx | 2 +- versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx index c0c5f75af9c7..63ff68960a58 100644 --- a/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx @@ -137,7 +137,7 @@ export const UpgradeTable = () => { ); }; -Pour rappel, les [OS supportés en version 24.10](../installation/compatibility.md) sont les suivants : +Pour rappel, les OS supportés en version 24.10 sont les suivants : * RHEL/Oracle Linux/Alma Linux 8 * RHEL/Oracle/Alma Linux 9 diff --git a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx index b3fda0492224..adf614ff199d 100644 --- a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx @@ -140,7 +140,7 @@ export const UpgradeTable = () => { ); }; -Pour rappel, les [OS supportés en version 25.10](../installation/compatibility.md) sont les suivants : +Pour rappel, les OS supportés en version 25.10 sont les suivants : * RHEL/Oracle Linux/Alma Linux 8 * RHEL/Oracle Linux/Alma Linux 9 diff --git a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx index 8082cbe1411d..4ad3371dedbf 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -120,7 +120,7 @@ export const UpgradeTable = () => { ); }; -Pour rappel, les [OS supportés en version 26.10](../installation/compatibility.md) sont les suivants : +Pour rappel, les OS supportés en version 26.10 sont les suivants : * RHEL/Oracle Linux/Alma Linux 9 * RHEL/Oracle Linux/Alma Linux 10 From 797d1c9be1a4fb241bb669f3d1153a4fc603a2c1 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 12:02:11 +0200 Subject: [PATCH 010/179] Add FR upgrade matrix files --- .../version-24.10/upgrade/upgrade-matrix.mdx | 154 +++++++++++++++++ .../version-25.10/upgrade/upgrade-matrix.mdx | 157 ++++++++++++++++++ .../version-26.10/upgrade/upgrade-matrix.mdx | 137 +++++++++++++++ 3 files changed, 448 insertions(+) create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx new file mode 100644 index 000000000000..63ff68960a58 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx @@ -0,0 +1,154 @@ +--- +id: upgrade-matrix +title: Matrice des montées de version possibles +--- + +import React, { useState } from 'react'; + +export const UpgradeTable = () => { + const [version, setVersion] = useState(''); + const [os, setOs] = useState(''); + const [compat, setCompat] = useState(''); + + const rows = [ + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-10.md' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04.md' }, + { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10.md' }, + { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04.md' }, + { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10.md' }, + { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + ]; + + const versions = [...new Set(rows.map(r => r.version))]; + const osList = [...new Set(rows.map(r => r.os))]; + + const filtered = rows.filter(r => + (!version || r.version === version) && + (!os || r.os === os) && + (!compat || r.compat === compat) + ); + + const selectStyle = { + fontSize: 13, + padding: '6px 12px', + borderRadius: 4, + border: '1px solid var(--ifm-color-emphasis-300)', + background: 'var(--ifm-background-surface-color)', + color: 'var(--ifm-font-color-base)', + cursor: 'pointer', + }; + + const thStyle = { + textAlign: 'left', + padding: '10px 16px', + background: 'var(--ifm-color-emphasis-100)', + color: 'var(--ifm-color-emphasis-700)', + fontWeight: 600, + fontSize: 12, + textTransform: 'uppercase', + letterSpacing: '0.04em', + borderBottom: '1px solid var(--ifm-color-emphasis-300)', + }; + + const tdStyle = { + padding: '10px 16px', + borderBottom: '1px solid var(--ifm-color-emphasis-200)', + verticalAlign: 'middle', + }; + + return ( +
+
+ + + +
+ +

+ {filtered.length} résultat{filtered.length > 1 ? 's' : ''} +

+ + + + + + + + + + + + {filtered.map((r, i) => ( + + + + + + + ))} + +
Version de départOS supporté à l'époqueOS toujours supporté en 24.10 ?Procédure à suivre
{r.version}{r.os} + + {r.compat} + + {r.proc}
+
+ ); +}; + +Pour rappel, les OS supportés en version 24.10 sont les suivants : + +* RHEL/Oracle Linux/Alma Linux 8 +* RHEL/Oracle/Alma Linux 9 +* Debian 12 (bookworm) + +Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 8 ou 9, ou Debian 12. Pour toute autre version ou OS, vous devrez effectuer une [migration](../migrate/introduction.md). + +## Montée de version ou migration ? + + + +## Cycle de vie des versions + +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx new file mode 100644 index 000000000000..adf614ff199d --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx @@ -0,0 +1,157 @@ +--- +id: upgrade-matrix +title: Matrice des montées de version possibles +--- + +import React, { useState } from 'react'; + +export const UpgradeTable = () => { + const [version, setVersion] = useState(''); + const [os, setOs] = useState(''); + const [compat, setCompat] = useState(''); + + const rows = [ + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10.md' }, + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10.md' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10.md' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-10.md' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04.md' }, + { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10.md' }, + { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04.md' }, + { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10.md' }, + { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + ]; + + const versions = [...new Set(rows.map(r => r.version))]; + const osList = [...new Set(rows.map(r => r.os))]; + + const filtered = rows.filter(r => + (!version || r.version === version) && + (!os || r.os === os) && + (!compat || r.compat === compat) + ); + + const selectStyle = { + fontSize: 13, + padding: '6px 12px', + borderRadius: 4, + border: '1px solid var(--ifm-color-emphasis-300)', + background: 'var(--ifm-background-surface-color)', + color: 'var(--ifm-font-color-base)', + cursor: 'pointer', + }; + + const thStyle = { + textAlign: 'left', + padding: '10px 16px', + background: 'var(--ifm-color-emphasis-100)', + color: 'var(--ifm-color-emphasis-700)', + fontWeight: 600, + fontSize: 12, + textTransform: 'uppercase', + letterSpacing: '0.04em', + borderBottom: '1px solid var(--ifm-color-emphasis-300)', + }; + + const tdStyle = { + padding: '10px 16px', + borderBottom: '1px solid var(--ifm-color-emphasis-200)', + verticalAlign: 'middle', + }; + + return ( +
+
+ + + +
+ +

+ {filtered.length} résultat{filtered.length > 1 ? 's' : ''} +

+ + + + + + + + + + + + {filtered.map((r, i) => ( + + + + + + + ))} + +
Version de départOS supporté à l'époqueOS toujours supporté en 25.10 ?Procédure à suivre
{r.version}{r.os} + + {r.compat} + + {r.proc}
+
+ ); +}; + +Pour rappel, les OS supportés en version 25.10 sont les suivants : + +* RHEL/Oracle Linux/Alma Linux 8 +* RHEL/Oracle Linux/Alma Linux 9 +* Debian 12 (bookworm) + +Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 8 ou 9, ou Debian 12. Pour toute autre version ou OS, vous devrez effectuer une [migration](../migrate/introduction.md). + +## Montée de version ou migration ? + + + +## Cycle de vie des versions + +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx new file mode 100644 index 000000000000..4ad3371dedbf --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -0,0 +1,137 @@ +--- +id: upgrade-matrix +title: Matrice des montées de version possibles +--- + +import React, { useState } from 'react'; + +export const UpgradeTable = () => { + const [version, setVersion] = useState(''); + const [os, setOs] = useState(''); + const [compat, setCompat] = useState(''); + + const rows = [ + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-25-10.md' }, + { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-10.md' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, + { version: '22.10 et antérieures', os: 'Voir documentations correspondantes', compat: 'NON', proc: 'Migration depuis EL ou Debian', href: '../migrate/introduction.md' }, + ]; + + const filtered = rows.filter(r => + (!version || r.version === version) && + (!os || r.os.includes(os)) && + (!compat || r.compat === compat) + ); + + return ( +
+
+ {[ + { id: 'version', value: version, setter: setVersion, label: 'Toutes les versions', options: ['25.10','24.10','24.04','23.10','23.04','22.10 et antérieures'] }, + { id: 'os', value: os, setter: setOs, label: 'Tous les OS', options: ['RHEL/Oracle/Alma Linux 8','RHEL/Oracle/Alma Linux 9','Debian 11','Debian 12'] }, + { id: 'compat', value: compat, setter: setCompat, label: 'Compatibilité 26.10', options: null }, + ].map(f => ( + + ))} +
+ +

+ {filtered.length} résultat{filtered.length > 1 ? 's' : ''} +

+ + + + + {['Version de départ', 'OS de départ', 'OS supporté en 26.10', 'Procédure à suivre'].map(h => ( + + ))} + + + + {filtered.map((r, i) => ( + + + + + + + ))} + +
{h}
{r.version}{r.os} + + {r.compat} + + + {r.proc} +
+
+ ); +}; + +Pour rappel, les OS supportés en version 26.10 sont les suivants : + +* RHEL/Oracle Linux/Alma Linux 9 +* RHEL/Oracle Linux/Alma Linux 10 +* Debian 13 (trixie) + +Cela signifie qu'une simple montée de version n'est possible que si vous utilisiez une version 23.04 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 9. Pour toute autre version et OS, vous devrez effectuer une [migration](../migrate/introduction.md). + +## Montée de version ou migration ? + + + +## Cycle de vie des versions + +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). \ No newline at end of file From 4d305ce5bbea8b199688a42cd2485f86d9130298 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 12:34:20 +0200 Subject: [PATCH 011/179] Try to unbreak build --- .../version-24.10/upgrade/upgrade-matrix.mdx | 4 +- .../version-25.10/upgrade/upgrade-matrix.mdx | 4 +- .../version-26.10/upgrade/upgrade-matrix.mdx | 4 +- .../version-24.10/upgrade/upgrade-matrix.mdx | 4 +- .../version-25.10/upgrade/upgrade-matrix.mdx | 4 +- .../upgrade/upgrade-from-23-04.md | 151 +----------------- .../version-26.10/upgrade/upgrade-matrix.mdx | 4 +- .../version-26.10-sidebars.json | 24 +-- 8 files changed, 18 insertions(+), 181 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx index 63ff68960a58..697d386e45e9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx @@ -149,6 +149,6 @@ Cela signifie qu'une montée de version n'est possible que si vous utilisiez une -## Cycle de vie des versions +{/* ## Cycle de vie des versions -[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). \ No newline at end of file +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). */} \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx index adf614ff199d..f910afcce080 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx @@ -152,6 +152,6 @@ Cela signifie qu'une montée de version n'est possible que si vous utilisiez une -## Cycle de vie des versions +{/* ## Cycle de vie des versions -[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). \ No newline at end of file +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). */} \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx index 4ad3371dedbf..85ad3df4af26 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -132,6 +132,6 @@ Cela signifie qu'une simple montée de version n'est possible que si vous utilis -## Cycle de vie des versions +{/* ## Cycle de vie des versions -[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). \ No newline at end of file +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). */} \ No newline at end of file diff --git a/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx index 63ff68960a58..697d386e45e9 100644 --- a/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx @@ -149,6 +149,6 @@ Cela signifie qu'une montée de version n'est possible que si vous utilisiez une -## Cycle de vie des versions +{/* ## Cycle de vie des versions -[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). \ No newline at end of file +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). */} \ No newline at end of file diff --git a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx index adf614ff199d..f910afcce080 100644 --- a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx @@ -152,6 +152,6 @@ Cela signifie qu'une montée de version n'est possible que si vous utilisiez une -## Cycle de vie des versions +{/* ## Cycle de vie des versions -[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). \ No newline at end of file +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). */} \ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md index 74667fa366c1..11a88fd34c43 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md @@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; This chapter describes how to upgrade your Centreon platform from version 23.04 -to version 25.10. +to version 26.10. > Version 23.04 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. @@ -51,24 +51,6 @@ Before upgrading your Centreon platform, make sure the following package reposit * centreon * centreon-modules, if you are using Centreon Business Edition. - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - @@ -79,33 +61,6 @@ Before upgrading your Centreon platform, make sure the following package reposit ### Install the new repositories - - -1. Update your Centreon 23.04 to the latest minor version. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/23.04/el8/centreon-23.04-el8.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Remove the repository files: - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon-* - ``` - -3. Install the new repository: - - ```shell - 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=* - ``` - - 1. Update your Centreon 23.04 to the latest minor version. @@ -131,25 +86,6 @@ dnf install -y dnf-plugins-core dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo ``` - - - -1. Update your Centreon 23.04 to the latest minor version. -2. Run the following commands: - -```shell -rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Then import the repository key: - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - @@ -164,35 +100,17 @@ apt update 2. If you have installed Business extensions, delete the configuration of the 23.04 repository: - - -```shell -rm /etc/yum.repos.d/centreon-business-23.04.repo -``` - - - ```shell rm /etc/yum.repos.d/centreon-business-23.04.repo ``` - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - 3. Install the 25.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. -4. 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**). - 5. Stop the Centreon Broker process: ```shell @@ -207,35 +125,9 @@ rm /var/lib/centreon-broker/* -f ### Upgrade PHP -Centreon 25.10 uses PHP in version 8.2. +Centreon 26.10 uses PHP in version 8.4. - - -You need to change the PHP stream from version 8.1 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.1 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - You need to change the PHP stream from version 8.1 to 8.2 by executing the following commands and answering **y** @@ -251,16 +143,6 @@ dnf module enable php:8.2 Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - - - -```shell -systemctl stop php8.1-fpm -systemctl disable php8.1-fpm -``` - -Ensure the `memory_limit` parameter in `/etc/php/8.2/fpm/conf.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - @@ -269,53 +151,24 @@ Then, finish upgrading the Centreon solution. 1. Clean the cache: - - -```shell -dnf clean all --enablerepo=* -``` - - ```shell dnf clean all --enablerepo=* ``` - - - -```shell -apt clean all -apt update -``` - 2. Then upgrade all the components with the following command: - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - ```shell dnf update centreon\* php-pecl-gnupg ``` - - - -```shell -apt install --only-upgrade centreon -``` - diff --git a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx index 4ad3371dedbf..85ad3df4af26 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -132,6 +132,6 @@ Cela signifie qu'une simple montée de version n'est possible que si vous utilis -## Cycle de vie des versions +{/* ## Cycle de vie des versions -[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). \ No newline at end of file +[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). */} \ No newline at end of file diff --git a/versioned_sidebars/version-26.10-sidebars.json b/versioned_sidebars/version-26.10-sidebars.json index ae5562863b21..c1e5023610d0 100644 --- a/versioned_sidebars/version-26.10-sidebars.json +++ b/versioned_sidebars/version-26.10-sidebars.json @@ -1129,6 +1129,10 @@ "type": "doc", "id": "upgrade/upgrade-matrix" }, + { + "type": "doc", + "id": "upgrade/upgrade-from-25-10" + }, { "type": "doc", "id": "upgrade/upgrade-from-24-10" @@ -1145,26 +1149,6 @@ "type": "doc", "id": "upgrade/upgrade-from-23-04" }, - { - "type": "doc", - "id": "upgrade/upgrade-from-22-10" - }, - { - "type": "doc", - "id": "upgrade/upgrade-from-22-04" - }, - { - "type": "doc", - "id": "upgrade/upgrade-from-21-10" - }, - { - "type": "doc", - "id": "upgrade/upgrade-from-21-04" - }, - { - "type": "doc", - "id": "upgrade/upgrade-from-20-10" - }, { "type": "doc", "id": "upgrade/upgrade-mariadb" From e0db70893bf1579f7a01fe0f32e3c9f3d6b14e06 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 13:37:07 +0200 Subject: [PATCH 012/179] Update upgrade from 25.10 topic --- .../upgrade/upgrade-from-25-10.md | 300 +----------------- 1 file changed, 2 insertions(+), 298 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index de3624473624..21695e8478f4 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -38,24 +38,6 @@ Before upgrading your Centreon platform, make sure the following package reposit * centreon * centreon-modules, if you are using Centreon Business Edition. - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - @@ -68,27 +50,6 @@ Before upgrading your Centreon platform, make sure the following package reposit ### Install the new repositories - - -1. Update your Centreon 25.10 to the latest minor version. - -2. Remove the repository files: - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Install the new repository: - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - - 1. Update your Centreon 25.10 to the latest minor version. @@ -107,26 +68,6 @@ dnf install -y dnf-plugins-core dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` - - - -1. Update your Centreon 25.10 to the latest minor version. - -2. Run the following commands: - -```shell -rm -f /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Then import the repository key: - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - @@ -141,28 +82,12 @@ apt update 2. If you have installed Business extensions, delete the configuration of the 24.10 repository: - - -```shell -rm /etc/yum.repos.d/centreon-business-24.10.repo -``` - - - ```shell rm /etc/yum.repos.d/centreon-business-24.10.repo ``` - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - @@ -185,53 +110,24 @@ rm /var/lib/centreon-broker/* -f 7. Clean the cache: - - -```shell -dnf clean all --enablerepo=* -``` - - ```shell dnf clean all --enablerepo=* ``` - - - -```shell -apt clean all -apt update -``` - 8. Then upgrade all the components with the following command: - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - ```shell dnf update centreon\* php-pecl-gnupg ``` - - - -```shell -apt install --only-upgrade centreon -``` - @@ -242,69 +138,6 @@ apt install --only-upgrade centreon 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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 - -``` - - 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. @@ -367,54 +200,6 @@ If everything is ok, you should have: ``` - - - -Use the backup file you created in the previous step to copy your customizations to the file **/etc/apache2/sites-available/centreon.conf**. - -Check that Apache is configured properly by running the following command: - -```shell -apache2ctl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Check the status of Apache: - -```shell -systemctl status apache2 -``` - -If everything is ok, you should have: - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2024-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - @@ -437,37 +222,19 @@ Before starting the web upgrade process, upgrade the [Centreon BAM module](../se following command: - - -```shell -systemctl reload php-fpm httpd -``` - - ```shell systemctl reload php-fpm httpd ``` - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - Then you need to finalize the upgrade process: - - + + 1. Log on to the Centreon web interface to continue the update process. Click **Next**: @@ -560,14 +327,6 @@ Finally, restart Broker, Engine and Gorgone on the central server by running thi Update the permissions on the centreon-broker configuration files. - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - ```shell @@ -575,14 +334,6 @@ usermod -a -G centreon-broker apache usermod -a -G apache centreon-broker ``` - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - @@ -653,15 +404,6 @@ systemctl restart centengine Run the following command: - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - ```shell @@ -670,15 +412,6 @@ rm -f /etc/yum.repos.d/centreon* && \ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard-26.10-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon.list -apt update -``` - @@ -687,40 +420,18 @@ apt update Clean the cache: - - -```shell -dnf clean all --enablerepo=* -``` - - ```shell dnf clean all --enablerepo=* ``` - - - -```shell -apt clean all -apt update -``` - Then upgrade all the components with the following command: - - -```shell -dnf update centreon\* -``` - - ```shell @@ -729,13 +440,6 @@ dnf update centreon\* > If you installed MariaDB from their official repositiories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. - - - -```shell -apt install --only-upgrade centreon-poller -``` - From 7b65460a68940a0f5ce58b88e1fced6374e226e3 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 13:46:03 +0200 Subject: [PATCH 013/179] Update upgrade procedure --- .../upgrade/upgrade-from-25-10.md | 32 ++++++++----------- 1 file changed, 13 insertions(+), 19 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index 21695e8478f4..f223edd1d1e0 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -5,15 +5,11 @@ title: Upgrade from Centreon 25.10 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This chapter describes how to upgrade your Centreon platform from version 25.10 to version 26.10. +This chapter describes how to upgrade your Centreon platform from version 25.10 to version 26.10. Upgrading is only possible if your current OS is RHEL/Oracle/AlmaLinux 9. Other OSs are no longer supported: use a [migration procedure](../migrate/introduction.md) to switch to a supported OS. If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. -> 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](../developer/developer-broker-bbdo-switch-versions.md). - -> If you want to migrate your Centreon platform to another server/OS, follow the [migration procedure](../migrate/introduction.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. +* 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](../developer/developer-broker-bbdo-switch-versions.md). ## Prerequisites @@ -45,9 +41,9 @@ Before upgrading your Centreon platform, make sure the following package reposit > When you run a command, check its output. If you get an error message, stop the procedure and fix the issue. -> If you installed MariaDB from their official repositiories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. +> If you installed MariaDB from their official repositories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. -### Install the new repositories +### Step 1: Install the new repositories @@ -71,15 +67,13 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/e -> If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). +4. If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). -### Upgrade the Centreon solution +### Step 2: 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: +2. If you have installed Business extensions, delete the configuration of the 24.10 repository: @@ -133,9 +127,9 @@ dnf update centreon\* php-pecl-gnupg > Accept new GPG keys from the repositories as needed. -### Update your customized Apache configuration +### Step 3: Update your customized Apache configuration -This section only applies if you customized your Apache configuration. +This section only applies if you customized your Apache configuration. @@ -216,7 +210,7 @@ Add the following code to your Apache configuration file, in both the ` Extensions > Manager**, upgrade all extensions, starting with the following: From 0f1204e4295133f689db8fb0ab2a7db17a983e4a Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 13:54:52 +0200 Subject: [PATCH 014/179] Add snippet for intro --- versioned_docs/version-26.10/upgrade/_intro.mdx | 5 +++++ versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md | 7 ++----- 2 files changed, 7 insertions(+), 5 deletions(-) create mode 100644 versioned_docs/version-26.10/upgrade/_intro.mdx diff --git a/versioned_docs/version-26.10/upgrade/_intro.mdx b/versioned_docs/version-26.10/upgrade/_intro.mdx new file mode 100644 index 000000000000..e8e88e539fd5 --- /dev/null +++ b/versioned_docs/version-26.10/upgrade/_intro.mdx @@ -0,0 +1,5 @@ +This chapter describes how to upgrade your Centreon platform from version {props.type} to version 26.10. Upgrading is only possible if your current OS is RHEL/Oracle/AlmaLinux 9. Other OSs are no longer supported: use a [migration procedure](../migrate/introduction.md) to switch to a supported OS. If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. + +* 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](../developer/developer-broker-bbdo-switch-versions.md). \ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index f223edd1d1e0..028f7a541355 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -4,12 +4,9 @@ title: Upgrade from Centreon 25.10 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import intro from './_intro.mdx' -This chapter describes how to upgrade your Centreon platform from version 25.10 to version 26.10. Upgrading is only possible if your current OS is RHEL/Oracle/AlmaLinux 9. Other OSs are no longer supported: use a [migration procedure](../migrate/introduction.md) to switch to a supported OS. If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. - -* 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](../developer/developer-broker-bbdo-switch-versions.md). + ## Prerequisites From 956b542693ec6aaf97f36baf24674a46f9446588 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 13:56:25 +0200 Subject: [PATCH 015/179] Remove obsolete files --- .../upgrade/upgrade-from-20-10.md | 630 --------------- .../upgrade/upgrade-from-21-04.md | 507 ------------ .../upgrade/upgrade-from-21-10.md | 528 ------------- .../upgrade/upgrade-from-22-04.md | 737 ------------------ .../upgrade/upgrade-from-22-10.md | 727 ----------------- 5 files changed, 3129 deletions(-) delete mode 100644 versioned_docs/version-26.10/upgrade/upgrade-from-20-10.md delete mode 100644 versioned_docs/version-26.10/upgrade/upgrade-from-21-04.md delete mode 100644 versioned_docs/version-26.10/upgrade/upgrade-from-21-10.md delete mode 100644 versioned_docs/version-26.10/upgrade/upgrade-from-22-04.md delete mode 100644 versioned_docs/version-26.10/upgrade/upgrade-from-22-10.md diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-20-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-20-10.md deleted file mode 100644 index 693ff312f9bb..000000000000 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-20-10.md +++ /dev/null @@ -1,630 +0,0 @@ ---- -id: upgrade-from-20-10 -title: Upgrade from Centreon 20.10 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -This chapter describes how to upgrade your Centreon platform from version 20.10 -to version 26.10. - -> Version 20.10 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. - -You cannot simply upgrade Centreon from a version earlier than 20.10 to version 26.10, as CentOS 7 is no longer supported. You need to [migrate your platform to a supported OS](../migrate/introduction.md). - -> 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](../developer/developer-broker-bbdo-switch-versions.md). - -> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> If you want to migrate your Centreon server to Oracle Linux / RHEL 8 or 9 -> you need to follow the [migration procedure](../migrate/migrate-from-el-to-el.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. - -> To perform this procedure, your MariaDB version must be >= 10.3.22. -> If not, please follow [this](./upgrade-mariadb.md) -> procedure in order to update MariaDB before you can continue with the upgrade -> from version 20.10 to version 26.10 as described by this document. - -> Warning: following the correction of a problem relating to the database schema, it will be necessary to stop the -> insertion of data collected in the database during the update. These will be stored in temporary files and then -> installed at the end of the update process. - -> Warning: If you were using the following monitoring connectors, from version 25.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prerequisites - -> When you run a command, check its output. If you get an error message, stop the procedure and fix the issue. - -### Perform a backup - -Be sure that you have fully backed up your environment for the following -servers: - -- Central server -- Database server - -If you use Open Ticket providers with custom configurations, [make a backup of these before updating Centreon](../alerts-notifications/ticketing-install.md#creating-a-backup-of-your-custom-open-ticket-provider-configurations). - -### Check the repositories - -Before upgrading your Centreon platform, make sure the following package repositories are enabled: - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -### 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](../security/key-rotation.md#existing-installation) to remove the old key and install the new one. - -## Upgrade the Centreon Central server - -> From 24.04, Centreon uses **MariaDB 10.11**. -> -> This upgrade process will only upgrade Centreon components first. -> -> MariaDB will be upgraded afterwards. - -### Install the new repositories - -1. On your 20.10 platform, replace `https://packages.centreon.com/rpm-standard` or `https://yum.centreon.com/standard` by `https://archives.centreon.com/standard/` in your current YUM configuration (by default, `/etc/yum.repos.d/centreon.repo`). - -2. Update your Centreon 20.10 to the latest minor version. - -3. Remove the **centreon.repo** file: - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -4. Install the new repository: - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - -> If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). - -### Install the MariaDB repository - - - - -```shell -dnf module enable -y mariadb:10.11 -``` - - - - -### 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 20.10 repository: - - - - -```shell -rm /etc/yum.repos.d/centreon-business-20.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-20.10.repo -``` - - - - -3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. - -5. Stop the Centreon Broker process: - -```shell -systemctl stop cbd -``` - -6. Delete existing retention files: - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Upgrade PHP - -Centreon 26.10 uses PHP in version 8.4. - - - - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -sudo subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` - -Then, you need to change the PHP stream from version 7.3 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf module reset php -``` - -```shell -dnf module install php:8.2 -``` - - - - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Then, you need to change the PHP stream from version 7.3 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf module reset php -``` - -```shell -dnf module install php:8.2 -``` - - - - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - -Then, finish upgrading the Centreon solution - -7. Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -8. Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> 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: - -```shell -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**. - -In particular, make sure your customized Apache configuration contains the following directive (with **authentication**). - -``` - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" - -``` - -Check that Apache is configured properly by running the following command: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 -``` - - - - -#### 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 `` and `` elements: - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json -``` - -### Upgrade the MariaDB server - -The MariaDB components can now be upgraded. - -> Refer to the official MariaDB documentation for more information about this process: -> -> https://mariadb.com/kb/en/upgrading-between-major-mariadb-versions/ - -#### 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: - - - - -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -#### Upgrading MariaDB - -You must uninstall and then reinstall MariaDB to upgrade between major versions (i.e. to switch from version 10.3 to version 10.11). - -1. Stop the MariaDB service: - - ```shell - systemctl stop mariadb - ``` - -2. Uninstall the current version: - - ```shell - rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-compat MariaDB-common - ``` - - > During this uninstallation step, you may encounter an error because one or several MariaDB packages are missing. In that case, you should execute the uninstallation command without including the missing package. - - For instance, if you see the following error message: - - ```shell - package MariaDB-compat is not installed - ``` - - As **MariaDB-compat** is the missing package, please execute the same command without quoting **MariaDB-compat**: - - ```shell - rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-common - ``` - - > Make sure you have [installed the official MariaDB repository](upgrade-from-20-10.md#install-the-mariadb-repository) before you continue the procedure. - -3. Install the 10.11 version: - - ```shell - dnf module enable -y mariadb:10.11 - dnf install mariadb-server-10.11\* mariadb-10.11\* - ``` - -4. Start the MariaDB service: - - ```shell - systemctl start mariadb - ``` - -5. Launch the MariaDB upgrade process: - - ```shell - mysql_upgrade - ``` - - If your database is password-protected, enter: - - ```shell - mysql_upgrade -u -p - ``` - - Example: if your database_admin_user is `root`, enter: - - ``` - mysql_upgrade -u root -p - ``` - - > Refer to the [official documentation](https://mariadb.com/kb/en/mysql_upgrade/) - > for more information or if errors occur during this last step. - -#### Enable MariaDB on startup - -Execute the following command: - -```shell -systemctl enable mariadb -``` - -### Finalizing the upgrade - - - - -Before starting the web upgrade process, upgrade the [Centreon BAM module](../service-mapping/upgrade.md) and reload the Apache server with the -following command: -```shell -systemctl reload httpd -``` - - - - -Then log on to the Centreon web interface to continue the upgrade process: - -Click **Next**: - -![image](../assets/upgrade/web_update_1.png) - -Click **Next**: - -![image](../assets/upgrade/web_update_2.png) - -The release notes describe the main changes. Click **Next**: - -![image](../assets/upgrade/web_update_3.png) - -This process performs the various upgrades. Click **Next**: - -![image](../assets/upgrade/web_update_4.png) - -Your Centreon server is now up to date. Click **Finish** to access the login -page: - -![image](../assets/upgrade/web_update_5.png) - -> As the interface layout has changed in version 23.04, you need to clear your browser cache to display the new theme. - -Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) 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: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * To adapt the commands automatically, run: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (You can also adapt them manually.) - -3. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Restart the processes: - - ```shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Upgrade MariaDB - -Follow [this procedure](upgrade-mariadb.md) to upgrade MariaDB to version 10.11. - -## Upgrade the Remote Servers - -This procedure is the same as for upgrading a Centreon Central server with the addition of needing to retrieve the decryption key at the end. - -### Retrieving the decryption key - -Run the following script with the central server IP address to enable the remote server to receive and process encrypted data: - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -> 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: - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -### Upgrade the Centreon solution - -Clean the cache: - -```shell -dnf clean all --enablerepo=* -``` - -Upgrade all the components with the following command: - -```shell -dnf update centreon\* -``` - -> Accept new GPG keys from the repositories as needed. - -Start and enable **gorgoned**: - -```shell -systemctl start gorgoned -systemctl enable gorgoned -``` - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -### Retrieving the decryption key - -Run the following script with the correct IP address to enable the poller to receive and process encrypted data. - -The IP address to use depends on the following conditions: -- When updating pollers linked directly to the central server, use the central server's IP. -- When updating pollers linked to a remote server, use the remote server's IP. However, in this instance, you must first confirm the remote server has the correct key by checking that the value of `app_secret` in the `/etc/centreon-engine/engine-context.json` file is the same as the central server's. If this is not the case, relaunch the script with the right IP to correct the .json file. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-21-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-21-04.md deleted file mode 100644 index 5780446b9352..000000000000 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-21-04.md +++ /dev/null @@ -1,507 +0,0 @@ ---- -id: upgrade-from-21-04 -title: Upgrade from Centreon 21.04 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -This chapter describes how to upgrade your Centreon platform from version 21.04 -to version 26.10. - -> Version 21.04 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. - -> 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](../developer/developer-broker-bbdo-switch-versions.md). - -> If you want to migrate your Centreon server to Oracle Linux / RHEL 8 -> you need to follow the [migration procedure](../migrate/migrate-from-el-to-el.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. - -> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Warning: If you were using the following monitoring connectors, from version 25.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prerequisites - -### Perform a backup - -Be sure that you have fully backed up your environment for the following -servers: - -- Central server -- Database server - -If you use Open Ticket providers with custom configurations, [make a backup of these before updating Centreon](../alerts-notifications/ticketing-install.md#creating-a-backup-of-your-custom-open-ticket-provider-configurations). - -### Check the repositories - -Before upgrading your Centreon platform, make sure the following package repositories are enabled: - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -### 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](../security/key-rotation.md#existing-installation) to remove the old key and install the new one. - -## 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. On your 21.04 platform, replace `https://packages.centreon.com/rpm-standard` or `https://yum.centreon.com/standard` by `https://archives.centreon.com/standard/` in your current YUM configuration (by default, `/etc/yum.repos.d/centreon.repo`). - -2. Update your Centreon 21.04 to the latest minor version. - -3. Remove the **centreon.repo** file: - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -4. Install the new repository: - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - -> If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). - -### 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 21.04 repository: - - - - -```shell -rm /etc/yum.repos.d/centreon-business-21.04.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-21.04.repo -``` - - - - -3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. - -5. Stop the Centreon Broker process: - -```shell -systemctl stop cbd -``` - -6. Delete existing retention files: - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Upgrade PHP - -Centreon 26.10 uses PHP in version 8.4. - - - - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -sudo subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` - -Then, you need to change the PHP stream from version 7.3 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf module reset php -``` - -```shell -dnf module install php:8.2 -``` - - - - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Then, you need to change the PHP stream from version 7.3 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf module reset php -``` - -```shell -dnf module install php:8.2 -``` - - - - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - -Then, finish upgrading the Centreon solution. - -1. Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -2. Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -> Accept new GPG keys from the repositories as needed. - - - - -Execute the following commands: - -```shell -systemctl enable php-fpm -systemctl restart php-fpm -``` - - - - -### 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: - -```shell -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**. - -In particular, make sure your customized Apache configuration contains the following directive (with **authentication**). - -``` - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" - -``` - -Check that Apache is configured properly by running the following command: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 -``` - - - - -#### 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 `` and `` elements: - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -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](../service-mapping/upgrade.md) and reload the Apache server with the -following command: - -```shell -systemctl reload httpd -``` - - - - -Then log on to the Centreon web interface to continue the upgrade process: - -Click **Next**: - -![image](../assets/upgrade/web_update_1.png) - -Click **Next**: - -![image](../assets/upgrade/web_update_2.png) - -The release notes describe the main changes. Click **Next**: - -![image](../assets/upgrade/web_update_3.png) - -This process performs the various upgrades. Click **Next**: - -![image](../assets/upgrade/web_update_4.png) - -Your Centreon server is now up to date. Click **Finish** to access the login -page: - -![image](../assets/upgrade/web_update_5.png) - -> As the interface layout has changed in version 22.10, you need to clear your browser cache to display the new theme. - -Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) 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: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * To adapt the commands automatically, run: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (You can also adapt them manually.) - -3. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Restart the processes: - - ```shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Upgrade MariaDB - -Follow [this procedure](upgrade-mariadb.md) to upgrade MariaDB to version 10.11.. - -## Upgrade the Remote Servers - -This procedure is the same as for upgrading a Centreon Central server with the addition of needing to retrieve the decryption key at the end. - -### Retrieving the decryption key - -Run the following script with the central server IP address to enable the remote server to receive and process encrypted data: - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -> 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: - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -### Upgrade the Centreon solution - -Clean the cache: - -```shell -dnf clean all --enablerepo=* -``` - -Upgrade all the components with the following command: - -```shell -dnf update centreon\* -``` - -> Accept new GPG keys from the repositories as needed. - -Start and enable **gorgoned**: - -```shell -systemctl start gorgoned -systemctl enable gorgoned -``` - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -### Retrieving the decryption key - -Run the following script with the correct IP address to enable the poller to receive and process encrypted data. - -The IP address to use depends on the following conditions: -- When updating pollers linked directly to the central server, use the central server's IP. -- When updating pollers linked to a remote server, use the remote server's IP. However, in this instance, you must first confirm the remote server has the correct key by checking that the value of `app_secret` in the `/etc/centreon-engine/engine-context.json` file is the same as the central server's. If this is not the case, relaunch the script with the right IP to correct the .json file. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-21-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-21-10.md deleted file mode 100644 index 8fbd230d1f48..000000000000 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-21-10.md +++ /dev/null @@ -1,528 +0,0 @@ ---- -id: upgrade-from-21-10 -title: Upgrade from Centreon 21.10 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -This chapter describes how to upgrade your Centreon platform from version 21.10 -to version 26.10. - -> Version 21.10 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. - -> 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](../developer/developer-broker-bbdo-switch-versions.md). - -> If you want to migrate your Centreon server to Oracle Linux / RHEL 8 -> you need to follow the [migration procedure](../migrate/migrate-from-el-to-el.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. - -> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Warning: If you were using the following monitoring connectors, from version 25.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prerequisites - -### Perform a backup - -Be sure that you have fully backed up your environment for the following -servers: - -- Central server -- Database server - -If you use Open Ticket providers with custom configurations, [make a backup of these before updating Centreon](../alerts-notifications/ticketing-install.md#creating-a-backup-of-your-custom-open-ticket-provider-configurations). - -### Check the repositories - -Before upgrading your Centreon platform, make sure the following package repositories are enabled: - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## 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. On your 21.10 platform, replace `https://packages.centreon.com/rpm-standard` or `https://yum.centreon.com/standard` by `https://archives.centreon.com/standard/` in your current YUM configuration (by default, `/etc/yum.repos.d/centreon.repo`). - -2. Update your Centreon 21.10 to the latest minor version. - -3. Remove the **centreon.repo** file: - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -4. Install the new repository: - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - -> If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). - -### 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 21.10 repository: - - - - -```shell -rm /etc/yum.repos.d/centreon-business-21.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-21.10.repo -``` - - - - -3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. - -4. Stop the Centreon Broker process: - -```shell -systemctl stop cbd -``` - -5. Delete existing retention files: - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Upgrade PHP - -Centreon 26.10 uses PHP in version 8.4. - - - - -You need to change the PHP stream from version 8.0 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.0 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module install php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -You need to change the PHP stream from version 8.0 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.0 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module install php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -### 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 21.10 repository: - - - - -```shell -rm /etc/yum.repos.d/centreon-business-21.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-21.10.repo -``` - - - - -3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. - -5. Stop the Centreon Broker process: - -```shell -systemctl stop cbd -``` - -6. Delete existing retention files: - -```shell -rm /var/lib/centreon-broker/* -f -``` - -1. Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -2. Then upgrade all the components with the following command: - - - - -```shell -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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 -``` - - - - -#### 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 `` and `` elements: - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -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](../service-mapping/upgrade.md) and reload the Apache server with the -following command: -```shell -systemctl reload httpd -``` - - - - -Then log on to the Centreon web interface to continue the upgrade process: - -Click **Next**: - -![image](../assets/upgrade/web_update_1.png) - -Click **Next**: - -![image](../assets/upgrade/web_update_2.png) - -The release notes describe the main changes. Click **Next**: - -![image](../assets/upgrade/web_update_3.png) - -This process performs the various upgrades. Click **Next**: - -![image](../assets/upgrade/web_update_4.png) - -Your Centreon server is now up to date. Click **Finish** to access the login -page: - -![image](../assets/upgrade/web_update_5.png) - -> As the interface layout has changed in version 23.04, you need to clear your browser cache to display the new theme. - -Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) 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: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * To adapt the commands automatically, run: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (You can also adapt them manually.) - -3. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Restart the processes: - - ``` shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Upgrade MariaDB - -Follow [this procedure](upgrade-mariadb.md) to upgrade MariaDB to version 10.11. - -## Upgrade the Remote Servers - -This procedure is the same as for upgrading a Centreon Central server with the addition of needing to retrieve the decryption key at the end. - -### Retrieving the decryption key - -Run the following script with the central server IP address to enable the remote server to receive and process encrypted data: - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -> 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: - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -### Upgrade the Centreon solution - -Clean the cache: - -```shell -dnf clean all --enablerepo=* -``` - -Upgrade all the components with the following command: - -```shell -dnf update centreon\* -``` - -> Accept new GPG keys from the repositories as needed. - -Start and enable **gorgoned**: - -```shell -systemctl start gorgoned -systemctl enable gorgoned -``` - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -### Retrieving the decryption key - -Run the following script with the correct IP address to enable the poller to receive and process encrypted data. - -The IP address to use depends on the following conditions: -- When updating pollers linked directly to the central server, use the central server's IP. -- When updating pollers linked to a remote server, use the remote server's IP. However, in this instance, you must first confirm the remote server has the correct key by checking that the value of `app_secret` in the `/etc/centreon-engine/engine-context.json` file is the same as the central server's. If this is not the case, relaunch the script with the right IP to correct the .json file. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-22-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-22-04.md deleted file mode 100644 index 333e91ee0914..000000000000 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-22-04.md +++ /dev/null @@ -1,737 +0,0 @@ ---- -id: upgrade-from-22-04 -title: Upgrade from Centreon 22.04 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -This chapter describes how to upgrade your Centreon platform from version 22.04 -to version 26.10. - -> Version 22.04 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. - -> 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](../developer/developer-broker-bbdo-switch-versions.md). - -> If you want to migrate your Centreon platform to another server/OS, follow the [migration procedure](../migrate/introduction.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. - -> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Version 26.10 means the end of support for Debian 12. If you were using Debian 12, you must first migrate to Debian 13 before you can upgrade Centreon. See [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). - -> Warning: If you were using the following monitoring connectors, from version 25.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prerequisites - -### Perform a backup - -Be sure that you have fully backed up your environment for the following -servers: - -- Central server -- Database server - -If you use Open Ticket providers with custom configurations, [make a backup of these before updating Centreon](../alerts-notifications/ticketing-install.md#creating-a-backup-of-your-custom-open-ticket-provider-configurations). - -### Check the repositories - -Before upgrading your Centreon platform, make sure the following package repositories are enabled: - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## Upgrade the Centreon Central server - -Version 26.10 means the end of support for Debian 12. If you were using Debian 12, you must first migrate to Debian 13 before you can upgrade Centreon. See [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). - -> 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 22.04 to the latest minor version. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/22.04/el8/centreon-22.04-el8.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Remove the **centreon-22.04.repo** file: - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Install the new repository: - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - - - - -1. Update your Centreon 22.04 to the latest minor version. -2. Run the following commands: - -```shell -rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Then import the repository key: - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -> If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). - -### 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 22.04 repository: - - - - -```shell -rm /etc/yum.repos.d/centreon-business-22.04.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-22.04.repo -``` - - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - - - - -3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. - -4. 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**). - -5. Stop the Centreon Broker process: - -```shell -systemctl stop cbd -``` - -6. Delete existing retention files: - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Upgrade PHP - -Centreon 26.10 uses PHP in version 8.4. - - - - -You need to change the PHP stream from version 8.0 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.0 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module install php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -You need to change the PHP stream from version 8.0 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf module reset php -``` - -```shell -dnf module install php:8.2 -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - - - - -```shell -systemctl stop php8.0-fpm -``` - -Ensure the `memory_limit` parameter in `/etc/php/8.2/fpm/conf.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - - - - -Then, finish upgrading the Centreon solution. - -1. Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -2. Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> 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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 - -``` - - - - -Use the backup file you created in the previous step to copy your customizations to the file **/etc/apache2/sites-available/centreon.conf**. - -Check that Apache is configured properly by running the following command: - -```shell -apache2ctl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php8.0-fpm apache2 -``` - -Then check its status: - -```shell -systemctl status apache2 -``` - -If everything is ok, you should have: - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -#### 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 `` and `` elements: - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -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](../service-mapping/upgrade.md) and reload the Apache server with the -following command: - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl stop php8.0-fpm.service -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - - - - -Then you need to finalize the upgrade process: - - - - -1. Log on to the Centreon web interface to continue the update process. Click **Next**: - - ![image](../assets/upgrade/web_update_1.png) - -2. Click **Next**: - - ![image](../assets/upgrade/web_update_2.png) - -3. The release notes describe the main changes. Click **Next**: - - ![image](../assets/upgrade/web_update_3.png) - -4. This process performs the various upgrades. Click **Next**: - - ![image](../assets/upgrade/web_update_4.png) - -5. Your Centreon server is now up to date. Click **Finish** to access the login -page: - - ![image](../assets/upgrade/web_update_5.png) - -Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. - -6. Deploy the central's configuration from the Centreon web UI by following [this -procedure](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -1. Log on to the central server through your terminal to continue the update process. - - > You need an authentication token to reach the API endpoint. Perform the following procedure to get a token. - - In our case, we have the configuration described below (you need to adapt the procedure to your configuration). - - address: 10.25.XX.XX - - port: 80 - - version: 26.10 - - login: Admin - - password: xxxxx - -2. Enter the following request: - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - This is how the result should look: - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost","is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Retrieve the token number to use it in the next request. - -4. Then enter this request: - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. This request does not return any result. To check if the update has been successfully applied, read the version number displayed on the Centreon web interface login page. - - - - -Finally, restart Broker, Engine and Gorgone on the central server by running this command: - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Add the **apache** user to the **centreon-broker** group and vice versa. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - - - - -> As the interface layout has changed in version 22.10, you need to clear your browser cache to display the new theme. - -### 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: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * To adapt the commands automatically, run: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (You can also adapt them manually.) - -3. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Restart the processes: - - ``` shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Upgrade MariaDB - -Follow [this procedure](upgrade-mariadb.md) to upgrade MariaDB to version 10.11. - -## Upgrade the Remote Servers - -This procedure is the same as for upgrading a Centreon Central server with the addition of needing to retrieve the decryption key at the end. - -### Retrieving the decryption key - -Run the following script with the central server IP address to enable the remote server to receive and process encrypted data: - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -> 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: - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -apt update -``` - - - - -### Upgrade the Centreon solution - -Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean -apt update -``` - - - - -Then upgrade all the components with the following command: - - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -apt install --only-upgrade centreon-poller -``` - - - - -> Accept new GPG keys from the repositories as needed. - -Restart **centreon**: - -```shell -systemctl restart centreon -``` - -### Retrieving the decryption key - -Run the following script with the correct IP address to enable the poller to receive and process encrypted data. - -The IP address to use depends on the following conditions: -- When updating pollers linked directly to the central server, use the central server's IP. -- When updating pollers linked to a remote server, use the remote server's IP. However, in this instance, you must first confirm the remote server has the correct key by checking that the value of `app_secret` in the `/etc/centreon-engine/engine-context.json` file is the same as the central server's. If this is not the case, relaunch the script with the right IP to correct the .json file. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-22-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-22-10.md deleted file mode 100644 index fad520e19c27..000000000000 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-22-10.md +++ /dev/null @@ -1,727 +0,0 @@ ---- -id: upgrade-from-22-10 -title: Upgrade from Centreon 22.10 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -This chapter describes how to upgrade your Centreon platform from version 22.10 -to version 26.10. - -> Version 22.10 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. - -> 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](../developer/developer-broker-bbdo-switch-versions.md). - -> If you want to migrate your Centreon platform to another server/OS, follow the [migration procedure](../migrate/introduction.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. - -> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Version 25.10 means the end of support for Debian 11. If you were using Debian 11, you must first migrate to Debian 12 before you can upgrade Centreon. See [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). - -> Warning: If you were using the following monitoring connectors, from version 25.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prerequisites - -### Perform a backup - -Be sure that you have fully backed up your environment for the following -servers: - -- Central server -- Database server - -If you use Open Ticket providers with custom configurations, [make a backup of these before updating Centreon](../alerts-notifications/ticketing-install.md#creating-a-backup-of-your-custom-open-ticket-provider-configurations). - -### Check the repositories - -Before upgrading your Centreon platform, make sure the following package repositories are enabled: - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## 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 22.10 to the latest minor version. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/22.10/el8/centreon-22.10-el8.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Remove the **centreon-22.10.repo** file: - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Install the new repository: - - ```shell - 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=* - ``` - - - - -1. Update your Centreon 22.10 to the latest minor version. -2. Run the following commands: - -```shell -rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Then import the repository key: - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -> If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). - -### 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 22.10 repository: - - - - -```shell -rm /etc/yum.repos.d/centreon-business-22.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-22.10.repo -``` - - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - - - - -3. Install the 25.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. - -4. 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**). - -5. Stop the Centreon Broker process: - -```shell -systemctl stop cbd -``` - -6. Delete existing retention files: - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Upgrade PHP - -Centreon 25.10 uses PHP in version 8.2. - - - - -You need to change the PHP stream from version 8.1 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.1 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -You need to change the PHP stream from version 8.1 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - - - - -```shell -systemctl stop php8.1-fpm -systemctl disable php8.1-fpm -``` - -Ensure the `memory_limit` parameter in `/etc/php/8.2/fpm/conf.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - - - - -Then finish upgrading the Centreon solution. - -1. Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -2. Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> 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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 - -``` - - - - -Use the backup file you created in the previous step to copy your customizations to the file **/etc/apache2/sites-available/centreon.conf**. - -Check that Apache is configured properly by running the following command: - -```shell -apache2ctl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Check the status of Apache: - -```shell -systemctl status apache2 -``` - -If everything is ok, you should have: - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -#### 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 `` and `` elements: - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -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](../service-mapping/upgrade.md) and reload the Apache server with the -following command: - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - - - - -Then you need to finalize the upgrade process: - - - - -1. Log on to the Centreon web interface to continue the update process. Click **Next**: - - ![image](../assets/upgrade/web_update_1.png) - -2. Click **Next**: - - ![image](../assets/upgrade/web_update_2.png) - -3. The release notes describe the main changes. Click **Next**: - - ![image](../assets/upgrade/web_update_3.png) - -4. This process performs the various upgrades. Click **Next**: - - ![image](../assets/upgrade/web_update_4.png) - -5. Your Centreon server is now up to date. Click **Finish** to access the login -page: - - ![image](../assets/upgrade/web_update_5.png) - -Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. - -6. Deploy the central's configuration from the Centreon web UI by following [this -procedure](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -1. Log on to the central server through your terminal to continue the update process. - - > You need an authentication token to reach the API endpoint. Perform the following procedure to get a token. - - In our case, we have the configuration described below (you need to adapt the procedure to your configuration). - - address: 10.25.XX.XX - - port: 80 - - version: 25.10 - - login: Admin - - password: xxxxx - -2. Enter the following request: - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - This is how the result should look: - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost","is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Retrieve the token number to use it in the next request. - -4. Then enter this request: - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. This request does not return any result. To check if the update has been successfully applied, read the version number displayed on the Centreon web interface login page. - - - - -Finally, restart Broker, Engine and Gorgone on the central server by running this command: - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Add the **apache** user to the **centreon-broker** group and vice versa. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - - - - - -### 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: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * To adapt the commands automatically, run: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (You can also adapt them manually.) - -3. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Restart the processes: - - ``` shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Upgrade MariaDB - -Follow [this procedure](upgrade-mariadb.md) to upgrade MariaDB to version 10.11. - -## Upgrade the Remote Servers - -This procedure is the same as for upgrading a Centreon Central server with the addition of needing to retrieve the decryption key at the end. - -### Retrieving the decryption key - -Run the following script with the central server IP address to enable the remote server to receive and process encrypted data: - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -> 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: - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo -``` - - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list -apt update -``` - - - - -### Upgrade the Centreon solution - -Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean -apt update -``` - - - - -Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -apt install --only-upgrade centreon-poller -``` - - - - -> Accept new GPG keys from the repositories as needed. - -Restart **centreon**: - -```shell -systemctl restart centreon -``` - -### Retrieving the decryption key - -Run the following script with the correct IP address to enable the poller to receive and process encrypted data. - -The IP address to use depends on the following conditions: -- When updating pollers linked directly to the central server, use the central server's IP. -- When updating pollers linked to a remote server, use the remote server's IP. However, in this instance, you must first confirm the remote server has the correct key by checking that the value of `app_secret` in the `/etc/centreon-engine/engine-context.json` file is the same as the central server's. If this is not the case, relaunch the script with the right IP to correct the .json file. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` From 827487bc0b4c5e2d32fa93da4f8a537f8d1538b5 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 14:38:40 +0200 Subject: [PATCH 016/179] Update --- .../upgrade/upgrade-from-23-04.md | 205 +----------------- .../upgrade/upgrade-from-23-10.md | 14 +- .../upgrade/upgrade-from-24-04.md | 18 +- .../upgrade/upgrade-from-24-10.md | 16 +- .../upgrade/upgrade-from-25-10.md | 11 +- 5 files changed, 40 insertions(+), 224 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md index 11a88fd34c43..89a9d167c5e2 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md @@ -4,20 +4,21 @@ title: Upgrade from Centreon 23.04 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import intro from './_intro.mdx' -This chapter describes how to upgrade your Centreon platform from version 23.04 -to version 26.10. + > Version 23.04 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. -> 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](../developer/developer-broker-bbdo-switch-versions.md). +## What components need upgrading -> If you want to migrate your Centreon platform to another server/OS, follow the [migration procedure](../migrate/introduction.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. +| Component | version in 23.04 | Version in 26.10 | +| --- | --- | --- | +| PHP | 8.1 | 8.4 | +| Database | MariaDB 10.5.x | MariaDB 11.8 | > Business edition users: MAP Legacy is no longer available in Centreon 25.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). -> Version 25.10 means the end of support for Debian 11. If you were using Debian 11, you must first migrate to Debian 12 before you can upgrade Centreon. See [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). - > Warning: If you were using the following monitoring connectors, from version 25.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: > * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) > * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) @@ -179,69 +180,6 @@ dnf update centreon\* php-pecl-gnupg 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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 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. @@ -304,54 +242,6 @@ If everything is ok, you should have: ``` - - - -Use the backup file you created in the previous step to copy your customizations to the file **/etc/apache2/sites-available/centreon.conf**. - -Check that Apache is configured properly by running the following command: - -```shell -apache2ctl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Check the status of Apache: - -```shell -systemctl status apache2 -``` - -If everything is ok, you should have: - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - @@ -374,30 +264,12 @@ Before starting the web upgrade process, upgrade the [Centreon BAM module](../se following command: - - -```shell -systemctl reload php-fpm httpd -``` - - ```shell systemctl reload php-fpm httpd ``` - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - @@ -499,14 +371,6 @@ Finally, restart Broker, Engine and Gorgone on the central server by running thi Add the **apache** user to the **centreon-broker** group and vice versa. - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - ```shell @@ -514,14 +378,6 @@ usermod -a -G centreon-broker apache usermod -a -G apache centreon-broker ``` - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - @@ -594,15 +450,6 @@ systemctl restart centengine Run the following command: - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo -``` - - ```shell @@ -611,15 +458,6 @@ rm -f /etc/yum.repos.d/centreon* && \ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo ``` - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list -apt update -``` - @@ -628,53 +466,24 @@ apt update Clean the cache: - - -```shell -dnf clean all --enablerepo=* -``` - - ```shell dnf clean all --enablerepo=* ``` - - - -```shell -apt clean all -apt update -``` - Then upgrade all the components with the following command: - - -```shell -dnf update centreon\* -``` - - ```shell dnf update centreon\* ``` - - - -```shell -apt install --only-upgrade centreon-poller -``` - diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md index eb03d1ecc81b..c457aad62ade 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md @@ -4,16 +4,20 @@ title: Upgrade from Centreon 23.10 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import intro from './_intro.mdx' -This chapter describes how to upgrade your Centreon platform from version 23.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](../developer/developer-broker-bbdo-switch-versions.md). +> Version 23.10 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. -> If you want to migrate your Centreon platform to another server/OS, follow the [migration procedure](../migrate/introduction.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. +## What components need upgrading -> Business edition users: MAP Legacy is no longer available in Centreon 25.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +| Component | version in 23.10 | Version in 26.10 | +| --- | --- | --- | +| PHP | 8.1 | 8.4 | +| Database | MariaDB 10.5.x | MariaDB 11.8 | -> Version 25.10 means the end of support for Debian 11. If you were using Debian 11, you must first migrate to Debian 12 before you can upgrade Centreon. See [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). +> Business edition users: MAP Legacy is no longer available in Centreon 25.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). > Warning: If you were using the following monitoring connectors, from version 25.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: > * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md index ab971ad7ed8f..79dca8d61493 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md @@ -4,20 +4,18 @@ title: Upgrade from Centreon 24.04 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import intro from './_intro.mdx' -This chapter describes how to upgrade your Centreon platform from version 24.04 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](../developer/developer-broker-bbdo-switch-versions.md). - -> If you want to migrate your Centreon platform to another server/OS, follow the [migration procedure](../migrate/introduction.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. +> Version 24.04 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. -> Version 25.10 means the end of support for Debian 11. If you were using Debian 11, you must first migrate to Debian 12 before you can upgrade Centreon. See [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). +## What components need upgrading -> If you were using MySQL 8.0, you may want to [upgrade to MySQL 8.4](upgrade-mysql.md) before the end of support for version 8.0. at the end of April 2026. +| Component | version in 24.04 | Version in 26.10 | +| --- | --- | --- | +| PHP | 8.1 | 8.4 | +| Database | MariaDB 10.11.x | MariaDB 11.8 | > Warning: If you were using the following monitoring connectors, from version 24.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: > * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md index 264cad709454..4c5daa96b876 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md @@ -4,18 +4,16 @@ title: Upgrade from Centreon 24.10 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import intro from './_intro.mdx' -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](../developer/developer-broker-bbdo-switch-versions.md). - -> If you want to migrate your Centreon platform to another server/OS, follow the [migration procedure](../migrate/introduction.md). If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. +## What components need upgrading -> If you were using MySQL 8.0, you may want to [upgrade to MySQL 8.4](upgrade-mysql.md) before the end of support for version 8.0. at the end of April 2026. +| Component | version in 24.10 | Version in 26.10 | +| --- | --- | --- | +| PHP | 8.2 | 8.4 | +| Database |
  • MariaDB 10.11.x
  • MySQL 8.0 or 8.4
|
  • MariaDB 11.8
  • MySQL 8.4
| ## Prerequisites diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index 028f7a541355..003a0a60498b 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -8,6 +8,13 @@ import intro from './_intro.mdx' +## What components need upgrading + +| Component | version in 25.10 | Version in 26.10 | +| --- | --- | --- | +| PHP | 8.2 | 8.4 | +| Database |
  • MariaDB 10.11.x
  • MySQL 8.0 or 8.4
|
  • MariaDB 11.8
  • MySQL 8.4
| + ## Prerequisites ### Perform a backup @@ -70,13 +77,13 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/e 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: +2. If you have installed Business extensions, delete the configuration of the 25.10 repository: ```shell -rm /etc/yum.repos.d/centreon-business-24.10.repo +rm /etc/yum.repos.d/centreon-business-25.10.repo ``` From f2d5be142591b7349f9259bbf7957addaefaba80 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 14:55:16 +0200 Subject: [PATCH 017/179] Update --- .../upgrade/centreon-ha/upgrade-from-21-04.md | 559 ------------- .../upgrade/centreon-ha/upgrade-from-21-10.md | 566 ------------- .../upgrade/centreon-ha/upgrade-from-22-04.md | 404 ---------- .../upgrade/centreon-ha/upgrade-from-22-10.md | 398 --------- .../upgrade/upgrade-from-20-10.md | 629 --------------- .../upgrade/upgrade-from-21-04.md | 495 ------------ .../upgrade/upgrade-from-21-10.md | 525 ------------ .../upgrade/upgrade-from-22-04.md | 752 ------------------ .../upgrade/upgrade-from-22-10.md | 731 ----------------- .../upgrade/centreon-ha/upgrade-from-21-04.md | 559 ------------- .../upgrade/centreon-ha/upgrade-from-21-10.md | 567 ------------- .../upgrade/centreon-ha/upgrade-from-22-10.md | 398 --------- ...de-from-22-04.md => upgrade-from-25-10.md} | 157 +++- .../version-26.10/upgrade/upgrade-mysql.md | 2 +- .../version-26.10-sidebars.json | 20 +- 15 files changed, 150 insertions(+), 6612 deletions(-) delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-04.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-10.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-04.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-10.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-20-10.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-04.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-10.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-04.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-10.md delete mode 100644 versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-04.md delete mode 100644 versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-10.md delete mode 100644 versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-10.md rename versioned_docs/version-26.10/upgrade/centreon-ha/{upgrade-from-22-04.md => upgrade-from-25-10.md} (74%) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-04.md deleted file mode 100644 index 4a231e286a04..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-04.md +++ /dev/null @@ -1,559 +0,0 @@ ---- -id: upgrade-centreon-ha-from-21-04 -title: Montée de version de Centreon HA depuis Centreon 21.04 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Ce chapitre décrit comment mettre à niveau votre plate-forme Centreon HA de la version 21.04 -vers la version 25.10. - -Vous ne pouvez pas simplement monter de version une plateforme avec HA (ou Centreon Failover) depuis une version antérieure à Centreon 20.10 et vers une version 25.10, car CentOS 7 n'est plus supporté: vous devez [migrer votre plateforme vers un OS supporté](../../migrate/introduction.md), puis installer Centreon HA sur la nouvelle platforme. Contactez votre représentant commercial Centreon pour discuter de toute migration avec la HA. - -## Prérequis - -### Suspendre la gestion des ressources du cluster - -Afin d'éviter un basculement du cluster pendant la mise à jour, il est nécessaire de surpendre toutes les ressources Centreon, ainsi que MariaDB. - -```bash -pcs property set maintenance-mode=true -``` - -### Effectuer une sauvegarde - -Assurez-vous que vous avez entièrement sauvegardé votre environnement pour les éléments suivants -serveurs : - -- Serveur Central -- Serveur Database - -### Mise à jour de la clé de signature RPM - -Pour des raisons de sécurité, les clés utilisées pour signer les RPM Centreon font l'objet d'une rotation régulière. La dernière modification a eu lieu le 14 octobre 2021. Lorsque vous effectuez une mise à niveau à partir d'une version antérieure, vous devez suivre la [procédure de rotation des clés] (../../security/key-rotation.md#existing-installation), pour supprimer l'ancienne clé et installer la nouvelle. - -### Modifier le script centreon_central_sync script (MBI uniquement) - -Cette étape n'est nécessaire que si vous utilisez [MBI](../../reporting/introduction.md). Modifiez le script `/usr/share/centreon-ha/bin/centreon_central_sync` aux lignes suivantes : - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua"], -``` - -Pour que les rapports soient toujours téléchargeables, remplacez ces lignes par : - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua", "/var/lib/centreon/centreon-bi-server/archives"], -``` - -## Processus de mise à niveau - -Pour effectuer la mise à niveau, veuillez [suivre la documentation officielle](../../upgrade/upgrade-from-21-04.md) Uniquement sur le **nœud central actif** et **nœud de base de données actif si nécessaire**. - -Ensuite, exécutez les commandes suivantes uniquement sur les serveurs centraux : - - - - -```shell -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - - - - -Sur le nœud central passif, déplacez le répertoire "install" pour éviter d'obtenir l'écran "upgrade" dans le WUI en cas de nouvel échange de rôles. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-YYYY-MM-DD -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - -### Suppression des tâches cron - -La mise à jour RPM remet en place les cron jobs sur les serveurs Central et Databases. Supprimez-les pour éviter les exécutions simultanées : - -```bash -rm -rf /etc/cron.d/centreon -rm -rf /etc/cron.d/centstorage -rm -f /etc/cron.d/centreon-ha-mysql -``` - -Le cron **centreon-ha-mysql** étant supprimé, vérifiez que vous avez bien la ligne suivante dans la section **server** du fichier **/etc/my.cnf.d/server.cnf** : - -```shell -expire_logs_days=7 -``` - -Si ce n'est pas le cas, ajoutez-la et redémarrez la ressource **ms_mysql** : - -```shell -pcs resource restart ms_mysql -``` - -### Réinitialiser les autorisations pour la ressource centreon_central_sync - -La mise à jour RPM remet les permissions en place sur les serveurs **Central**. Changez-les en utilisant ces commandes : - -```bash -chmod 775 /var/log/centreon-engine/ -mkdir /var/log/centreon-engine/archives -chown centreon-engine: /var/log/centreon-engine/archives -chmod 775 /var/log/centreon-engine/archives/ -find /var/log/centreon-engine/ -type f -exec chmod 664 {} \; -find /usr/share/centreon/www/img/media -type d -exec chmod 775 {} \; -find /usr/share/centreon/www/img/media -type f \( ! -iname ".keep" ! -iname ".htaccess" \) -exec chmod 664 {} \; -``` - -## Montée de version du cluster - -Depuis Centreon 22.04, la réplication de mariaDB est maintenant basée sur [GTID](https://mariadb.com/kb/en/gtid/). -Il est nécessaire de détruire complètement le cluster et de le configurer à nouveau avec -la dernière version de Centreon et les mécanismes de réplication de MariaDB. - -### Mode maintenance et sauvegarde - -Effectuez une sauvegarde du cluster en utilisant : - -```bash -pcs config backup centreon_cluster -pcs config export pcs-commands | sed -e :a -e '/\\$/N; s/\\\n//; ta' | sed 's/-f tmp-cib.xml//' | egrep "create|group" | egrep -v "(mysql|php|cbd_rrd)" > centreon_pcs_command.sh -``` - -Vérifiez que le fichier `centreon_cluster.tar.bz2` existe avant de continuer cette procédure. - -```bash -ls -l centreon_cluster.tar.bz2 -``` - -Vous devriez obtenir un résultat comme celui-ci : - -```text --rw------- 1 root root 2777 May 3 17:49 centreon_cluster.tar.bz2 -``` - -Vérifiez ensuite le fichier centreon_pcs_command.sh, la commande d'exportation peut afficher quelques lignes d'avertissement mais elle n'est pas bloquante. - -```bash -cat centreon_pcs_command.sh -``` - -Le contenu doit ressembler à ceci : - -```text -pcs resource create vip ocf:heartbeat:IPaddr2 broadcast=@VIP_BROADCAST_IPADDR@ cidr_netmask=@VIP_CIDR_NETMASK@ flush_routes=true ip=@VIP_IPADDR@ nic=@VIP_IFNAME@ op monitor interval=10s timeout=20s start interval=0s timeout=20s stop interval=0s timeout=20s meta target-role=started -pcs resource create http systemd:httpd24-httpd op monitor interval=5s timeout=20s start interval=0s timeout=40s stop interval=0s timeout=40s meta target-role=started -pcs resource create gorgone systemd:gorgoned op monitor interval=5s timeout=20s start interval=0s timeout=90s stop interval=0s timeout=90s meta target-role=started -pcs resource create centreon_central_sync systemd:centreon-central-sync op monitor interval=5s timeout=20s start interval=0s timeout=90s stop interval=0s timeout=90s meta target-role=started -pcs resource create cbd_central_broker systemd:cbd-sql op monitor interval=5s timeout=30s start interval=0s timeout=90s stop interval=0s timeout=90s meta target-role=started -pcs resource create centengine systemd:centengine op monitor interval=5s timeout=30s start interval=0s timeout=90s stop interval=0s timeout=90s meta multiple-active=stop_start target-role=started -pcs resource create centreontrapd systemd:centreontrapd op monitor interval=5s timeout=20s start interval=0s timeout=30s stop interval=0s timeout=30s meta target-role=started -pcs resource create snmptrapd systemd:snmptrapd op monitor interval=5s timeout=20s start interval=0s timeout=30s stop interval=0s timeout=30s meta target-role=started -pcs resource group add centreon vip http gorgone centreon_central_sync cbd_central_broker centengine centreontrapd snmptrapd -``` - -Ce fichier sera nécessaire pour recréer toutes les ressources de votre cluster. - -### Supprimer les ressources - -Ces commandes ne doivent être exécutées que sur le nœud central actif : - - - - -```bash -pcs resource delete ms_mysql --force -pcs resource delete cbd_rrd --force -pcs resource delete php7 --force -pcs resource delete centreon --force -``` - - - - -```bash -pcs resource delete ms_mysql --force -pcs resource delete vip_mysql --force -pcs resource delete cbd_rrd --force -pcs resource delete php7 --force -pcs resource delete centreon --force -``` - - - - -### Reconfigurer MariaDB - -Il est nécessaire de modifier la configuration de mysql en éditant le fichier `/etc/my.cnf.d/server.cnf` : - -> Sur les 2 serveurs centraux dans les nœuds HA 2. -> Sur les 2 serveurs de bases de données en HA 4 nœuds. - -```shell -[server] -... -skip-slave-start -log-slave-updates -gtid_strict_mode=ON -expire_logs_days=7 -ignore-db-dir=lost+found -... -``` - -### Lancer la réplication GTID - -Exécutez cette commande **sur le nœud de base de données secondaire:**. - -```bash -mysqladmin -p shutdown -``` - -Il est important de s'assurer que MariaDB est complètement arrêté. Vous allez exécuter cette commande et vérifier qu'elle ne renvoie aucun résultat : - -```bash -ps -ef | grep mariadb[d] -``` - -Une fois le service arrêté **sur le nœud de base de données secondaire**, vous exécuterez le script de synchronisation **à partir du nœud de base de données primaire** : - -```bash -mysqladmin -p shutdown -systemctl restart mariadb -/usr/share/centreon-ha/bin/mysql-sync-bigdb.sh -``` - -La sortie de ce script est très verbeuse et vous ne pouvez pas vous attendre à tout comprendre, donc pour vous assurer que tout s'est bien passé, concentrez-vous sur les dernières lignes de sa sortie, en vérifiant qu'elle ressemble à ceci : - -```text -Umount and Delete LVM snapshot - Logical volume "dbbackupdatadir" successfully removed -Start MySQL Slave -Start Replication -Id User Host db Command Time State Info Progress -[variable number of lines] -``` - -La chose importante à vérifier est que `Start MySQL Slave` et `Start Replication` sont présents et qu'aucune erreur ne les suit. - -De plus, la sortie de cette commande ne doit afficher que des résultats `OK` : - -```bash -/usr/share/centreon-ha/bin/mysql-check-status.sh -``` - -Le résultat attendu est : - -```text -Connection Status '@CENTRAL_MASTER_NAME@' [OK] -Connection Status '@CENTRAL_SLAVE_NAME@' [OK] -Slave Thread Status [OK] -Position Status [OK] -``` - -### Redémarrer les processus Centreon - -Puis de redémarrer tous les processus sur le **nœud central actif** : - -```bash -systemctl restart cbd-sql cbd gorgoned centengine centreontrapd -``` - -Et sur le **nœud central passif** : - -```bash -systemctl restart cbd -``` - -### Nettoyer les fichiers de mémoire de Broker - -> **Attention:** n'exécutez cette commande que sur le **noeud central passif**. - -Avant de reprendre la gestion des ressources du cluster, pour éviter les problèmes de broker, nettoyez tous les fichiers *.memory.*, *.unprocessed.* ou *.queue.* : - -```bash -rm -rf /var/lib/centreon-broker/central-broker-master.memory* -rm -rf /var/lib/centreon-broker/central-broker-master.queue* -rm -rf /var/lib/centreon-broker/central-broker-master.unprocessed* -``` - -### Recréer les ressources du cluster - -A exécuter **seulement sur un noeud central** : - -> **Attention:** la syntaxe de la commande suivante dépend de la distribution Linux que vous utilisez. - -> Vous pouvez trouver @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ @MARIADB_REPL_USER@ -La variable @MARIADB_REPL_USER@ dans `/etc/centreon-ha/mysql-resources.sh`. - - - - -```bash -pcs resource create "ms_mysql" \ - ocf:heartbeat:mariadb-centreon \ - config="/etc/my.cnf.d/server.cnf" \ - pid="/var/lib/mysql/mysql.pid" \ - datadir="/var/lib/mysql" \ - socket="/var/lib/mysql/mysql.sock" \ - binary="/usr/bin/mysqld_safe" \ - node_list="@CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@" \ - replication_user="@MARIADB_REPL_USER@" \ - replication_passwd='@MARIADB_REPL_PASSWD@' \ - test_user="@MARIADB_REPL_USER@" \ - test_passwd="@MARIADB_REPL_PASSWD@" \ - test_table='centreon.host' -``` - - - - -> **Attention:** la syntaxe de la commande suivante dépend de la distribution Linux que vous utilisez. - - - - - - -```bash -pcs resource promotable ms_mysql \ - master-node-max="1" \ - clone_max="2" \ - globally-unique="false" \ - clone-node-max="1" \ - notify="true" -``` - - - - - - - -```bash -pcs resource promotable ms_mysql \ - master-node-max="1" \ - clone_max="2" \ - globally-unique="false" \ - clone-node-max="1" \ - notify="true" -``` - -Adresse VIP des serveurs de bases de données - -```bash -pcs resource create vip_mysql \ - ocf:heartbeat:IPaddr2 \ - ip="@VIP_SQL_IPADDR@" \ - nic="@VIP_SQL_IFNAME@" \ - cidr_netmask="@VIP_SQL_CIDR_NETMASK@" \ - broadcast="@VIP_SQL_BROADCAST_IPADDR@" \ - flush_routes="true" \ - meta target-role="stopped" \ - op start interval="0s" timeout="20s" \ - stop interval="0s" timeout="20s" \ - monitor interval="10s" timeout="20s" -``` - - - - - - -#### Resource PHP - -```bash -pcs resource create "php" \ - systemd:php-fpm \ - meta target-role="started" \ - op start interval="0s" timeout="30s" \ - stop interval="0s" timeout="30s" \ - monitor interval="5s" timeout="30s" \ - clone -``` - -#### Ressource RRD broker - -```bash -pcs resource create "cbd_rrd" \ - systemd:cbd \ - meta target-role="started" \ - op start interval="0s" timeout="90s" \ - stop interval="0s" timeout="90s" \ - monitor interval="20s" timeout="30s" \ - clone -``` - -#### Recréer le groupe de ressource *centreon* - -```bash -bash centreon_pcs_command.sh -``` - -#### Recréer les contraintes - - - - - - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint order stop centreon then demote ms_mysql-clone -``` - - - - - - -Afin de coller le rôle de la base de données primaire avec l'IP virtuelle, définissez une contrainte mutuelle : - - - - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - - - -Recréez ensuite la contrainte qui empêche les processus Centreon de s'exécuter sur les nœuds de base de données et vice-versa : - - - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - - - - - -## Reprise de la gestion des ressources du cluster - -Maintenant que la mise à jour est terminée, les ressources peuvent être gérées à nouveau : - -```bash -pcs property set maintenance-mode=false -pcs resource cleanup -``` - -## Vérifier la santé du cluster - -Vous pouvez surveiller les ressources du cluster en temps réel à l'aide de la commande `crm_mon -fr` : -> **INFO:** L'option `-fr` vous permet d'afficher toutes les ressources même si elles sont désactivées. - - - - -```text -Stack: corosync -Current DC: @CENTRAL_SLAVE_NAME@ (version 1.1.20-5.el7_7.2-3c4c782f70) - partition with quorum -Last updated: Thu Feb 20 13:14:17 2020 -Last change: Thu Feb 20 09:25:54 2020 by root via crm_attribute on @CENTRAL_MASTER_NAME@ - -2 nodes configured -14 resources configured - -Online: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @CENTRAL_MASTER_NAME@ ] - Slaves: [ @CENTRAL_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -``` - - - - -```text -[...] -4 nodes configured -21 resources configured - -Online: [@CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @DATABASE_MASTER_NAME@ ] - Slaves: [ @DATABASE_SLAVE_NAME@ ] - Stopped: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -vip_mysql (ocf::heartbeat:IPaddr2): Started @DATABASE_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ -``` - - - - -### Ressources désactivées - -Lorsque vous faites un `crm_mon -fr` et que vous avez une ressource qui est désactivée : - -```text -... - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @DATABASE_MASTER_NAME@ ] - Slaves: [ @DATABASE_SLAVE_NAME@ ] - Stopped: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -vip_mysql (ocf::heartbeat:IPaddr2): Stopped (disabled) -... -``` - -Vous devez activer la ressource avec la commande suivante : - -```bash -pcs resource enable @RESSOURCE_NAME@ -``` - -Dans notre cas : - -```bash -pcs resource enable vip_mysql -``` - -## Vérification de la stabilité de la plate-forme - -Vous devez maintenant vérifier que tout fonctionne correctement : - -* Accès aux menus de l'interface web. -* Génération de la configuration des pollers + méthode de rechargement et de redémarrage. -* Programmation des contrôles immédiats (Central + Pollers), des acquittements, des temps d'arrêt, etc. -* Déplacer les ressources ou redémarrer le serveur actif et vérifier à nouveau que tout va bien. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-10.md deleted file mode 100644 index a9668dd11922..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-10.md +++ /dev/null @@ -1,566 +0,0 @@ ---- -id: upgrade-centreon-ha-from-21-10 -title: Montée de version de Centreon HA depuis Centreon 21.10 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Ce chapitre décrit comment mettre à niveau votre plate-forme Centreon HA de la version 21.10 vers la version 25.10. - -Si vous envisagez également de migrer votre plateforme vers un autre système d’exploitation, contactez votre représentant commercial Centreon pour en discuter. - -## Prérequis - -### Suspendre la gestion des ressources du cluster - -Afin d'éviter un basculement du cluster pendant la mise à jour, il est nécessaire de suspendre toutes les ressources Centreon, ainsi que MariaDB. - -```bash -pcs property set maintenance-mode=true -``` - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance des sauvegardes de l’ensemble des serveurs centraux de votre plateforme : - -- Serveur Centreon Central -- Serveur de Base de données - -### Mettre à jour la clé de signature RPM - -Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. -Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. - -### Modifier le script centreon_central_sync script (MBI uniquement) - -Cette étape n'est nécessaire que si vous utilisez [MBI](../../reporting/introduction.md). Modifiez le script `/usr/share/centreon-ha/bin/centreon_central_sync` aux lignes suivantes : - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua"], -``` - -Pour que les rapports soient toujours téléchargeables, remplacez ces lignes par : - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua", "/var/lib/centreon/centreon-bi-server/archives"], -``` - -## Processus de mise à jour - -Pour effectuer la montée de version: - -> Pour le **nœud central actif** et **le nœud base de données actif s'il existe**, [suivez la documentation officielle](../../upgrade/upgrade-from-21-10.md) **jusqu'à l'étape "Mettre à jour MariaDB" incluse**. - -> Pour le **nœud central passif** et **le nœud base de données passif s'il existe**, [suivez la documentation officielle](../../upgrade/upgrade-from-21-10.md) **jusqu'à l'étape "Mettre à jour une configuration Apache personnalisée" incluse. Ensuite, sautez à l'étape "Mettre à jour MariaDB"**. Ne procédez pas aux étapes "Finalisation de la mise à jour" et "Actions post montée de version". - -Uniquement sur les serveurs deux nœuds centraux, restaurer le fichier `/etc/centreon-ha/centreon_central_sync.pm`. - -```bash -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -Sur le nœud central passif, déplacez le répertoire **install** pour éviter d'obtenir l'écran "upgrade" dans l'interface en cas de nouvel échange de rôles et rechargez le cache Apache. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - -### Suppression des crons - -La mise à jour RPM remet en place les crons sur les serveurs Central et Bases de données. Supprimez-les pour éviter les exécutions simultanées : - -```bash -rm -rf /etc/cron.d/centreon -rm -rf /etc/cron.d/centstorage -rm -f /etc/cron.d/centreon-ha-mysql -``` - -Le cron **centreon-ha-mysql** étant supprimé, vérifiez que vous avez bien la ligne suivante dans la section **server** du fichier **/etc/my.cnf.d/server.cnf** : - -```shell -expire_logs_days=7 -``` - -Si ce n'est pas le cas, ajoutez-la et redémarrez la ressource **ms_mysql** : - -```shell -pcs resource restart ms_mysql -``` - -### Réinitialiser les autorisations de la ressource centreon_central_sync - -L'upgrade RPM remet les permissions en place sur les serveurs centraux. Modifiez-les en utilisant ces commandes : - -```bash -chmod 775 /var/log/centreon-engine/ -mkdir /var/log/centreon-engine/archives -chown centreon-engine: /var/log/centreon-engine/archives -chmod 775 /var/log/centreon-engine/archives/ -find /var/log/centreon-engine/ -type f -exec chmod 664 {} \; -find /usr/share/centreon/www/img/media -type d -exec chmod 775 {} \; -find /usr/share/centreon/www/img/media -type f \( ! -iname ".keep" ! -iname ".htaccess" \) -exec chmod 664 {} \; -``` - -## Ugprade du cluster - -Depuis Centreon 22.04, la réplication de MariaDB est maintenant basée sur [GTID](https://mariadb.com/kb/en/gtid/). -Il est nécessaire de détruire complètement le cluster et de le configurer à nouveau avec la dernière version de Centreon et les mécanismes de réplication de MariaDB GTID. - -### Mode maintenance et sauvegarde - -Réalisez une sauvegarde du cluster en exécutant les commandes suivantes : - - - - -```bash -pcs config backup centreon_cluster -pcs resource config --output-format=cmd | sed -e :a -e '/\\$/N; s/\\\n//; ta' | sed 's/-f tmp-cib.xml//' | egrep "create|group" | egrep -v "(mysql|php|cbd_rrd)" > centreon_pcs_command.sh -``` - - - - -Vérifiez que le fichier `centreon_cluster.tar.bz2` existe avant de continuer cette procédure. - -```bash -ls -l centreon_cluster.tar.bz2 -``` - -Vous devriez obtenir un résultat comme celui-ci : - -```text --rw------- 1 root root 2777 May 3 17:49 centreon_cluster.tar.bz2 -``` - -Vérifiez ensuite le fichier centreon_pcs_command.sh, la commande d'exportation peut afficher quelques lignes d'avertissement mais elle n'est pas bloquante. - -```bash -cat centreon_pcs_command.sh -``` - -Le contenu doit ressembler à ceci : - - - - -```text -pcs resource create --no-default-ops --force -- vip ocf:heartbeat:IPaddr2 broadcast=@VIP_BROADCAST_IPADDR@ cidr_netmask=@VIP_CIDR_NETMASK@ flush_routes=true ip=@VIP_IPADDR@ nic=@VIP_IFNAME@ op monitor interval=10s id=vip-monitor-interval-10s timeout=20s start interval=0s id=vip-start-interval-0s timeout=20s stop interval=0s id=vip-stop-interval-0s timeout=20s meta target-role=started; -pcs resource create --no-default-ops --force -- http systemd:httpd op monitor interval=5s id=http-monitor-interval-5s timeout=20s start interval=0s id=http-start-interval-0s timeout=40s stop interval=0s id=http-stop-interval-0s timeout=40s meta target-role=started; -pcs resource create --no-default-ops --force -- gorgone systemd:gorgoned op monitor interval=5s id=gorgone-monitor-interval-5s timeout=20s start interval=0s id=gorgone-start-interval-0s timeout=90s stop interval=0s id=gorgone-stop-interval-0s timeout=90s meta target-role=started; -pcs resource create --no-default-ops --force -- centreon_central_sync systemd:centreon-central-sync op monitor interval=5s id=centreon_central_sync-monitor-interval-5s timeout=20s start interval=0s id=centreon_central_sync-start-interval-0s timeout=90s stop interval=0s id=centreon_central_sync-stop-interval-0s timeout=90s meta target-role=started; -pcs resource create --no-default-ops --force -- cbd_central_broker systemd:cbd-sql op monitor interval=5s id=cbd_central_broker-monitor-interval-5s timeout=30s start interval=0s id=cbd_central_broker-start-interval-0s timeout=90s stop interval=0s id=cbd_central_broker-stop-interval-0s timeout=90s meta target-role=started; -pcs resource create --no-default-ops --force -- centengine systemd:centengine op monitor interval=5s id=centengine-monitor-interval-5s timeout=30s start interval=0s id=centengine-start-interval-0s timeout=90s stop interval=0s id=centengine-stop-interval-0s timeout=90s meta multiple-active=stop_start target-role=started; -pcs resource create --no-default-ops --force -- centreontrapd systemd:centreontrapd op monitor interval=5s id=centreontrapd-monitor-interval-5s timeout=20s start interval=0s id=centreontrapd-start-interval-0s timeout=30s stop interval=0s id=centreontrapd-stop-interval-0s timeout=30s meta target-role=started; -pcs resource create --no-default-ops --force -- snmptrapd systemd:snmptrapd op monitor interval=5s id=snmptrapd-monitor-interval-5s timeout=20s start interval=0s id=snmptrapd-start-interval-0s timeout=30s stop interval=0s id=snmptrapd-stop-interval-0s timeout=30s meta target-role=started; -pcs resource group add centreon vip http gorgone centreon_central_sync cbd_central_broker centengine centreontrapd snmptrapd; -``` - - - - -Ce fichier sera nécessaire pour recréer toutes les ressources de votre cluster. - -### Supprimer les ressources - -Ces commandes ne doivent être exécutées que sur le nœud central actif : - - - - -```bash -pcs resource delete ms_mysql --force -pcs resource delete cbd_rrd --force -pcs resource delete php --force -pcs resource delete centreon --force -``` - - - - -```bash -pcs resource delete ms_mysql --force -pcs resource delete vip_mysql --force -pcs resource delete cbd_rrd --force -pcs resource delete php --force -pcs resource delete centreon --force -``` - - - - -### Reconfigure MariaDB - -Il est nécessaire de modifier la configuration de MySQL en éditant `/etc/my.cnf.d/server.cnf` : - -> Sur les 2 serveurs centraux dans une HA 2 nœuds -> Sur les 2 serveurs de base de données dans une HA 4 noeuds. - -```bash -[server] -... -skip-slave-start -log-slave-updates -gtid_strict_mode=ON -expire_logs_days=7 -ignore-db-dir=lost+found -... -``` - -### Lancer la réplication GTID - -Exécutez cette commande **sur le nœud de base de données secondaire:**. - -```bash -mysqladmin -p shutdown -``` - -Il est important de s'assurer que MariaDB est complètement arrêté. Vous allez exécuter cette commande et vérifier qu'elle ne renvoie aucun résultat : - -```bash -ps -ef | grep mariadb[d] -``` - -Une fois le service arrêté **sur le nœud de base de données secondaire**, vous allez exécuter le script de synchronisation **depuis le nœud de base de données primaire** : - -```bash -mysqladmin -p shutdown -systemctl restart mariadb -/usr/share/centreon-ha/bin/mysql-sync-bigdb.sh -``` - -La sortie de ce script est très verbeuse : pour vous assurer que tout s'est bien passé, concentrez-vous sur les dernières lignes de la sortie, en vérifiant qu'elles ressemblent à ceci : - -```text -Umount and Delete LVM snapshot - Logical volume "dbbackupdatadir" successfully removed -Start MySQL Slave -Start Replication -Id User Host db Command Time State Info Progress -[variable number of lines] -``` - -La chose importante à vérifier est que `Start MySQL Slave` et `Start Replication` sont présents et qu'aucune erreur ne les suit. - -De plus, la sortie de cette commande ne doit afficher que des résultats `OK` : - -```bash -/usr/share/centreon-ha/bin/mysql-check-status.sh -``` - -La sortie attendue est : - -```text -Connection MASTER Status '@CENTRAL_MASTER_NAME@' [OK] -Connection SLAVE Status '@CENTRAL_SLAVE_NAME@' [OK] -Slave Thread Status [OK] -Position Status [OK] -``` - -### Redémarrer les processus de Centreon - -Puis de redémarrer tous les processus sur le **nœud central actif** : - -```bash -systemctl restart cbd-sql cbd gorgoned centengine centreontrapd -``` - -Et sur le **nœud central passif** : - -```bash -systemctl restart cbd -``` - -### Nettoyer les fichiers de mémoire de broker - -> **WARNING:** exécuter cette commande uniquement sur le noeud central passif. - -Avant de reprendre la gestion des ressources du cluster, pour éviter les problèmes de broker, il faut nettoyer tous les fichiers *.memory.*, *.unprocessed.* ou *.queue.* : - -```bash -rm -rf /var/lib/centreon-broker/central-broker-master.memory* -rm -rf /var/lib/centreon-broker/central-broker-master.queue* -rm -rf /var/lib/centreon-broker/central-broker-master.unprocessed* -``` - -### Recréer les ressources du cluster - -À exécuter **seulement sur un nœud central** : - -> **WARNING:** la syntaxe de la commande suivante dépend de la distribution Linux que vous utilisez. - -> Vous pouvez trouver les variables @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ @MARIADB_REPL_USER@ @MARIADB_REPL_USER@ dans `/etc/centreon-ha/mysql-resources.sh`. - - - - -```bash -pcs resource create "ms_mysql" \ - ocf:heartbeat:mariadb-centreon \ - config="/etc/my.cnf.d/server.cnf" \ - pid="/var/lib/mysql/mysql.pid" \ - datadir="/var/lib/mysql" \ - socket="/var/lib/mysql/mysql.sock" \ - binary="/usr/bin/mysqld_safe" \ - node_list="@CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@" \ - replication_user="@MARIADB_REPL_USER@" \ - replication_passwd='@MARIADB_REPL_PASSWD@' \ - test_user="@MARIADB_REPL_USER@" \ - test_passwd="@MARIADB_REPL_PASSWD@" \ - test_table='centreon.host' -``` - - - - -> **WARNING:** la syntaxe de la commande suivante dépend de la distribution Linux que vous utilisez. - - - - - - -```bash -pcs resource promotable ms_mysql \ - master-node-max="1" \ - clone_max="2" \ - globally-unique="false" \ - clone-node-max="1" \ - notify="true" -``` - - - - - - - -```bash -pcs resource promotable ms_mysql \ - master-node-max="1" \ - clone_max="2" \ - globally-unique="false" \ - clone-node-max="1" \ - notify="true" -``` - -Adresse VIP des serveurs de bases de données - -```bash -pcs resource create vip_mysql \ - ocf:heartbeat:IPaddr2 \ - ip="@VIP_SQL_IPADDR@" \ - nic="@VIP_SQL_IFNAME@" \ - cidr_netmask="@VIP_SQL_CIDR_NETMASK@" \ - broadcast="@VIP_SQL_BROADCAST_IPADDR@" \ - flush_routes="true" \ - meta target-role="stopped" \ - op start interval="0s" timeout="20s" \ - stop interval="0s" timeout="20s" \ - monitor interval="10s" timeout="20s" -``` - - - - - - -#### PHP ressource - -```bash -pcs resource create "php" \ - systemd:php-fpm \ - meta target-role="started" \ - op start interval="0s" timeout="30s" \ - stop interval="0s" timeout="30s" \ - monitor interval="5s" timeout="30s" \ - clone -``` - -#### Ressource RRD broker - -```bash -pcs resource create "cbd_rrd" \ - systemd:cbd \ - meta target-role="started" \ - op start interval="0s" timeout="90s" \ - stop interval="0s" timeout="90s" \ - monitor interval="20s" timeout="30s" \ - clone -``` - -#### Recréer le groupe de ressources *centreon* - -```bash -bash centreon_pcs_command.sh -``` - -#### Recréer les contraintes - - - - - - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - - - - - -Afin de fixer le rôle de la base de données primaire avec l'IP virtuelle, définissez une contrainte mutuelle : - - - - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - - - -Recréez ensuite les contraintes qui empêchent les processus Centreon de s'exécuter sur les nœuds de base de données et vice-versa : - - - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - - - - - -## Reprise de la gestion des ressources du cluster - -Maintenant que la mise à jour est terminée, les ressources peuvent être gérées à nouveau : - -```bash -pcs property set maintenance-mode=false -pcs resource cleanup ms_mysql -``` - -## Vérifier la santé du cluster - -Vous pouvez surveiller les ressources du cluster en temps réel en utilisant la commande `crm_mon -fr` : -> **INFO:** L'option `-fr` vous permet d'afficher toutes les resources même si elles sont disable. - - - - -```text -Stack: corosync -Current DC: @CENTRAL_SLAVE_NAME@ (version 1.1.20-5.el7_7.2-3c4c782f70) - partition with quorum -Last updated: Thu Feb 20 13:14:17 2020 -Last change: Thu Feb 20 09:25:54 2020 by root via crm_attribute on @CENTRAL_MASTER_NAME@ - -2 nodes configured -14 resources configured - -Online: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @CENTRAL_MASTER_NAME@ ] - Slaves: [ @CENTRAL_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -``` - - - - -```text -[...] -4 nodes configured -21 resources configured - -Online: [@CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @DATABASE_MASTER_NAME@ ] - Slaves: [ @DATABASE_SLAVE_NAME@ ] - Stopped: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -vip_mysql (ocf::heartbeat:IPaddr2): Started @DATABASE_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ -``` - - - - -### Ressources désactivées - -Lorsque vous faite une `crm_mon -fr` et que vous une ressource qui est disable : - -```text -... - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @DATABASE_MASTER_NAME@ ] - Slaves: [ @DATABASE_SLAVE_NAME@ ] - Stopped: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -vip_mysql (ocf::heartbeat:IPaddr2): Stopped (disabled) -... -``` - -Vous devez faire enable la resource avec la commande suivante : - -```bash -pcs resource enable @RESSOURCE_NAME@ -``` - -Dans notre cas : - -```bash -pcs resource enable vip_mysql -``` - -## Vérification de la stabilité de la plate-forme - -Vous devez maintenant vérifier que tout fonctionne bien : - -* Accès aux menus de l'interface utilisateur web. -* Génération de la configuration des pollers + méthode de rechargement et de redémarrage. -* Planification des contrôles immédiats (Central + Pollers), des accusés de réception, des temps d'arrêt, etc. -* Déplacer des ressources ou redémarrer le serveur actif et vérifier à nouveau que tout va bien. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-04.md deleted file mode 100644 index 39484becbf13..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-04.md +++ /dev/null @@ -1,404 +0,0 @@ ---- -id: upgrade-centreon-ha-from-22-04 -title: Montée de version de Centreon HA depuis Centreon 22.04 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Ce chapitre décrit comment mettre à niveau votre plate-forme Centreon HA de la version 22.04 vers la version 25.10. - -> Si vous utilisiez Debian 11, vous ne pouvez pas directement monter à la version 25.10. Vous devez [migrer votre platforme vers Debian 12](migrate/migrate-from-debian-to-debian.md) d'abord, puis réinstaller la HA. Contactez votre représentant commercial Centreon pour discuter de toute migration avec la HA. - -## Prérequis - -### Suspendre la gestion des ressources du cluster - -Afin d'éviter un basculement du cluster pendant la mise à jour, il est nécessaire de surpendre toutes les ressources Centreon, ainsi que MariaDB. - -```bash -pcs property set maintenance-mode=true -``` - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance des sauvegardes de l’ensemble des serveurs centraux de votre plateforme : - -- Serveur Centreon Central -- Serveur de Base de données - -### Mettre à jour la clé de signature RPM - -Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. -Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. - -### Modifier le script centreon_central_sync script (MBI uniquement) - -Cette étape n'est nécessaire que si vous utilisez [MBI](../../reporting/introduction.md). Modifiez le script `/usr/share/centreon-ha/bin/centreon_central_sync` aux lignes suivantes : - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua"], -``` - -Pour que les rapports soient toujours téléchargeables, remplacez ces lignes par : - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua", "/var/lib/centreon/centreon-bi-server/archives"], -``` - -## Processus de mise à jour - -Avant de procéder à la montée de version, arrêter Centreon-Broker-SQL sur le **nœud central primaire**: - -```bash -systemctl stop cbd-sql -``` - -Maintenant, pour effectuer la montée de version: - -> Pour le **nœud central actif** et **le nœud base de données actif s'il existe**, [suivez la documentation officielle](../../upgrade/upgrade-from-22-04.md) **jusqu'à l'étape "Mettre à jour MariaDB" incluse**. - -> Pour le **nœud central passif** et **le nœud base de données passif s'il existe**, [suivez la documentation officielle](../../upgrade/upgrade-from-22-04.md) **jusqu'à l'étape "Mettre à jour une configuration Apache personnalisée" incluse. Ensuite, sautez à l'étape "Mettre à jour MariaDB"**. Ne procédez pas aux étapes "Finalisation de la mise à jour" et "Actions post montée de version". - - - - -Uniquement sur les serveurs deux nœuds centraux, restaurer le fichier `/etc/centreon-ha/centreon_central_sync.pm`. - -```bash -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -Sur le **nœud central passif**, déplacez le répertoire **install** pour éviter d'obtenir l'écran "upgrade" dans l'interface en cas de nouvel échange de rôles et rechargez le cache Apache. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - - - - -### Suppression des crons - -La mise à jour RPM remet en place les crons sur les serveurs Central et Bases de données. Supprimez-les pour éviter les exécutions simultanées : - -```bash -rm -f /etc/cron.d/centreon -rm -f /etc/cron.d/centstorage -rm -f /etc/cron.d/centreon-ha-mysql -``` - -puis redémarrer le service cron: - - - - -```bash -systemctl restart crond -``` - - - - -Le cron **centreon-ha-mysql** étant supprimé, vérifiez que vous avez bien la ligne suivante dans la section **server** du fichier **/etc/my.cnf.d/server.cnf**, il est normalement déjà en place depuis 22.04 et la réplication GTID : - -```shell -expire_logs_days=7 -``` - -### Réinitialiser les autorisations de la ressource centreon_central_sync - -L'upgrade RPM remet les permissions en place sur les serveurs centraux. Modifiez-les en utilisant ces commandes : - -```bash -chmod 775 /var/log/centreon-engine/ -mkdir /var/log/centreon-engine/archives -chown centreon-engine: /var/log/centreon-engine/archives -chmod 775 /var/log/centreon-engine/archives/ -find /var/log/centreon-engine/ -type f -exec chmod 664 {} \; -find /usr/share/centreon/www/img/media -type d -exec chmod 775 {} \; -find /usr/share/centreon/www/img/media -type f \( ! -iname ".keep" ! -iname ".htaccess" \) -exec chmod 664 {} \; -``` - -## Ugprade du cluster - -Depuis Centreon 22.04, la réplication de MariaDB est maintenant basée sur [GTID](https://mariadb.com/kb/en/gtid/). - -Cependant, certains changements doivent toujours être apportés. - - - - -### Sauvegarder la configuration - -Effectuez une sauvegarde du cluster sur le nœud central maître en utilisant: - -```bash -pcs config backup centreon_cluster -cibadmin -Q > export_cluster.xml -``` - -Vérifiez que le fichier `centreon_cluster.tar.bz2` existe avant de continuer cette procédure. - -```bash -ls -l centreon_cluster.tar.bz2 -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text --rw------- 1 root root 2777 May 3 17:49 centreon_cluster.tar.bz2 -``` - -### Modification de l'ordre des ressources sur le groupe centreon - -Pour optimiser la gestion des ressources et éviter de redémarrer cbd-sql quand on veut juste redémarrer gorgone, il faut changer leur ordre dans le groupe. - -```bash -pcs resource group remove centreon cbd_central_broker -pcs resource group add centreon cbd_central_broker --before gorgone -``` - - - - -### Nettoyer les fichiers de mémoire de broker - -> **WARNING:** exécuter cette commande uniquement sur le nœud central passif. - -Avant de reprendre la gestion des ressources du cluster, pour éviter les problèmes de broker, il faut nettoyer tous les fichiers *.memory.*, *.unprocessed.* ou *.queue.*: - -```bash -rm -f /var/lib/centreon-broker/central-broker-master.memory* -rm -f /var/lib/centreon-broker/central-broker-master.queue* -rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* -``` - -#### Recréer les contraintes - - - - - - -Commencez par extraire tous les identifiants des contraintes: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -Vous devriez obtenir un résultat similaire: - -```text -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-centreon-INFINITY -colocation-centreon-ms_mysql-clone-INFINITY -``` - -et supprimer **toutes** les contraintes, **adapter les ID avec les vôtres** - -```bash -pcs constraint delete order-centreon-ms_mysql-clone-mandatory -pcs constraint delete colocation-ms_mysql-clone-centreon-INFINITY -pcs constraint delete colocation-centreon-ms_mysql-clone-INFINITY -``` - -Vérifier que toutes les contraintes ont bien été supprimées: - -```bash -pcs constraint -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -Si c'est le cas, recréez uniquement les contraintes nécessaires. - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - - - - - - - -Extraire d'abord tous les identifiants de contraintes: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -Vous devriez obtenir un résultat similaire en fonction de vos noms d'hôtes : - -```text -location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -location-centreon-cc-ha-bdd2-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web1-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web2-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd2-2210-alma8--INFINITY -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-vip_mysql-INFINITY -colocation-centreon-vip-INFINITY -``` - -et supprimer **toutes** les contraintes, **adapter les ids avec les vôtres** - -```bash -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -pcs constraint delete location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -... -``` - -Vérifier que toutes les contraintes sont bien supprimées: - -```bash -pcs constraint -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -Si c'est le cas, recréez uniquement les contraintes nécessaires. - -Afin de coller le rôle de base de données primaire avec l'IP virtuelle, définissez une contrainte mutuelle: - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - - - -Recréez ensuite la contrainte qui empêche les processus Centreon de s'exécuter sur les nœuds de la base de données et vice-et-versa.: - - - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - - - - - -## Reprise de la gestion des ressources du cluster - -Maintenant que la mise à jour est terminée, les ressources peuvent être gérées à nouveau : - -```bash -pcs property set maintenance-mode=false -pcs resource cleanup -``` - -## Vérifier la santé du cluster - -Vous pouvez surveiller les ressources du cluster en temps réel en utilisant la commande `crm_mon -fr` : -> **INFO:** L'option `-fr` vous permet d'afficher toutes les resources même si elles sont disable. - - - - -```text -Stack: corosync -Current DC: @CENTRAL_SLAVE_NAME@ (version 1.1.20-5.el7_7.2-3c4c782f70) - partition with quorum -Last updated: Thu Feb 20 13:14:17 2020 -Last change: Thu Feb 20 09:25:54 2020 by root via crm_attribute on @CENTRAL_MASTER_NAME@ - -2 nodes configured -14 resources configured - -Online: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @CENTRAL_MASTER_NAME@ ] - Slaves: [ @CENTRAL_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -``` - - - - -```text -[...] -4 nodes configured -21 resources configured - -Online: [@CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @DATABASE_MASTER_NAME@ ] - Slaves: [ @DATABASE_SLAVE_NAME@ ] - Stopped: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -vip_mysql (ocf::heartbeat:IPaddr2): Started @DATABASE_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ -``` - - - - -## Vérification de la stabilité de la plate-forme - -Vous devez maintenant vérifier que tout fonctionne bien : - -* Accès aux menus de l'interface utilisateur web. -* Génération de la configuration des pollers + méthode de rechargement et de redémarrage. -* Planification des contrôles immédiats (Central + Pollers), des accusés de réception, des temps d'arrêt, etc. -* Déplacer des ressources ou redémarrer le serveur actif et vérifier à nouveau que tout va bien. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-10.md deleted file mode 100644 index d489f2ee23b4..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-10.md +++ /dev/null @@ -1,398 +0,0 @@ ---- -id: upgrade-centreon-ha-from-22-10 -title: Montée de version de Centreon HA depuis Centreon 22.10 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Ce chapitre décrit comment mettre à niveau votre plate-forme Centreon HA de la version 22.10 vers la version 25.10. - -> Si vous utilisiez Debian 11, vous ne pouvez pas directement monter à la version 25.10. Vous devez [migrer votre platforme vers Debian 12](migrate/migrate-from-debian-to-debian.md) d'abord, puis réinstaller la HA. Contactez votre représentant commercial Centreon pour discuter de toute migration avec la HA. - -## Prérequis - -### Suspendre la gestion des ressources du cluster - -Afin d'éviter un basculement du cluster pendant la mise à jour, il est nécessaire de suspendre toutes les ressources Centreon, ainsi que MariaDB. - -```bash -pcs property set maintenance-mode=true -``` - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance des sauvegardes de l’ensemble des serveurs centraux de votre plateforme : - -- Serveur Centreon Central -- Serveur de Base de données - -### Mettre à jour la clé de signature RPM - -Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. -Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. - -### Modifier le script centreon_central_sync script (MBI uniquement) - -Cette étape n'est nécessaire que si vous utilisez [MBI](../../reporting/introduction.md). Modifiez le script `/usr/share/centreon-ha/bin/centreon_central_sync` aux lignes suivantes : - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua"], -``` - -Pour que les rapports soient toujours téléchargeables, remplacez ces lignes par : - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua", "/var/lib/centreon/centreon-bi-server/archives"], -``` - -## Processus de mise à jour - -Avant de procéder à la montée de version, arrêter Centreon-Broker-SQL sur le **nœud central primaire**: - -```bash -systemctl stop cbd-sql -``` - -Maintenant, pour effectuer la montée de version: - -> Pour le **nœud central actif** et **le nœud base de données actif s'il existe**, [suivez la documentation officielle](../../upgrade/upgrade-from-22-10.md) **jusqu'à l'étape "Mettre à jour MariaDB" incluse**. - -> Pour le **nœud central passif** et **le nœud base de données passif s'il existe**, [suivez la documentation officielle](../../upgrade/upgrade-from-22-10.md) **jusqu'à l'étape "Mettre à jour une configuration Apache personnalisée" incluse. Ensuite, sautez à l'étape "Mettre à jour MariaDB"**. Ne procédez pas aux étapes "Finalisation de la mise à jour" et "Actions post montée de version". - - - - -Uniquement sur les serveurs deux nœuds centraux, restaurer le fichier `/etc/centreon-ha/centreon_central_sync.pm`. - -```bash -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -Sur le **nœud central passif**, déplacez le répertoire **install** pour éviter d'obtenir l'écran "upgrade" dans l'interface en cas de nouvel échange de rôles et rechargez le cache Apache. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - - - - -### Suppression des crons - -La mise à jour RPM remet en place les crons sur les serveurs Central et Bases de données. Supprimez-les pour éviter les exécutions simultanées : - -```bash -rm -f /etc/cron.d/centreon -rm -f /etc/cron.d/centstorage -rm -f /etc/cron.d/centreon-ha-mysql -``` - -puis redémarrer le service cron: - - - - -```bash -systemctl restart crond -``` - - - - -Le cron **centreon-ha-mysql** étant supprimé, vérifiez que vous avez bien la ligne suivante dans la section **server** du fichier **/etc/my.cnf.d/server.cnf**, il est normalement déjà en place depuis 22.04 et la réplication GTID : - -```shell -expire_logs_days=7 -``` - -### Réinitialiser les autorisations de la ressource centreon_central_sync - -L'upgrade RPM remet les permissions en place sur les serveurs centraux. Modifiez-les en utilisant ces commandes : - -```bash -chmod 775 /var/log/centreon-engine/ -mkdir /var/log/centreon-engine/archives -chown centreon-engine: /var/log/centreon-engine/archives -chmod 775 /var/log/centreon-engine/archives/ -find /var/log/centreon-engine/ -type f -exec chmod 664 {} \; -find /usr/share/centreon/www/img/media -type d -exec chmod 775 {} \; -find /usr/share/centreon/www/img/media -type f \( ! -iname ".keep" ! -iname ".htaccess" \) -exec chmod 664 {} \; -``` - -## Ugprade du cluster - -Depuis Centreon 22.04, la réplication de MariaDB est maintenant basée sur [GTID](https://mariadb.com/kb/en/gtid/). - -Cependant, certains changements doivent toujours être apportés. - -### Sauvegarder la configuration - -Effectuez une sauvegarde du cluster sur le nœud central maître en utilisant: - -```bash -pcs config backup centreon_cluster -cibadmin -Q > export_cluster.xml -``` - -Vérifiez que le fichier `centreon_cluster.tar.bz2` existe avant de continuer cette procédure. - -```bash -ls -l centreon_cluster.tar.bz2 -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text --rw------- 1 root root 2777 May 3 17:49 centreon_cluster.tar.bz2 -``` - -### Modification de l'ordre des ressources sur le groupe centreon - -Pour optimiser la gestion des ressources et éviter de redémarrer cbd-sql quand on veut juste redémarrer gorgone, il faut changer leur ordre dans le groupe. - -```bash -pcs resource group remove centreon cbd_central_broker -pcs resource group add centreon cbd_central_broker --before gorgone -``` - -### Nettoyer les fichiers de mémoire de broker - -> **WARNING:** exécuter cette commande uniquement sur le noeud central passif. - -Avant de reprendre la gestion des ressources du cluster, pour éviter les problèmes de broker, il faut nettoyer tous les fichiers *.memory.*, *.unprocessed.* ou *.queue.* : - -```bash -rm -f /var/lib/centreon-broker/central-broker-master.memory* -rm -f /var/lib/centreon-broker/central-broker-master.queue* -rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* -``` - -#### Recréer les contraintes - - - - - - -Commencez par extraire tous les identifiants des contraintes: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -Vous devriez obtenir un résultat similaire: - -```text -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-centreon-INFINITY -colocation-centreon-ms_mysql-clone-INFINITY -``` - -et supprimer **toutes** les contraintes, **adapter les ID avec les vôtres** - -```bash -pcs constraint delete order-centreon-ms_mysql-clone-mandatory -pcs constraint delete colocation-ms_mysql-clone-centreon-INFINITY -pcs constraint delete colocation-centreon-ms_mysql-clone-INFINITY -``` - -Vérifier que toutes les contraintes ont bien été supprimées: - -```bash -pcs constraint -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -Si c'est le cas, recréez uniquement les contraintes nécessaires. - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - - - - - - - -Extraire d'abord tous les identifiants de contraintes: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -Vous devriez obtenir un résultat similaire en fonction de vos noms d'hôtes : - -```text -location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -location-centreon-cc-ha-bdd2-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web1-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web2-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd2-2210-alma8--INFINITY -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-vip_mysql-INFINITY -colocation-centreon-vip-INFINITY -``` - -et supprimer **toutes** les contraintes, **adapter les ids avec les vôtres** - -```bash -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -pcs constraint delete location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -... -``` - -Vérifier que toutes les contraintes sont bien supprimées: - -```bash -pcs constraint -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -Si c'est le cas, recréez uniquement les contraintes nécessaires. - -Afin de coller le rôle de base de données primaire avec l'IP virtuelle, définissez une contrainte mutuelle: - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - - - -Recréez ensuite la contrainte qui empêche les processus Centreon de s'exécuter sur les nœuds de la base de données et vice-et-versa.: - - - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - - - - - -## Reprise de la gestion des ressources du cluster - -Maintenant que la mise à jour est terminée, les ressources peuvent être gérées à nouveau : - -```bash -pcs property set maintenance-mode=false -pcs resource cleanup -``` - -## Vérifier la santé du cluster - -Vous pouvez surveiller les ressources du cluster en temps réel en utilisant la commande `crm_mon -fr` : -> **INFO:** L'option `-fr` vous permet d'afficher toutes les resources même si elles sont disable. - - - - -```text -Stack: corosync -Current DC: @CENTRAL_SLAVE_NAME@ (version 1.1.20-5.el7_7.2-3c4c782f70) - partition with quorum -Last updated: Thu Feb 20 13:14:17 2020 -Last change: Thu Feb 20 09:25:54 2020 by root via crm_attribute on @CENTRAL_MASTER_NAME@ - -2 nodes configured -14 resources configured - -Online: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @CENTRAL_MASTER_NAME@ ] - Slaves: [ @CENTRAL_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -``` - - - - -```text -[...] -4 nodes configured -21 resources configured - -Online: [@CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @DATABASE_MASTER_NAME@ ] - Slaves: [ @DATABASE_SLAVE_NAME@ ] - Stopped: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -vip_mysql (ocf::heartbeat:IPaddr2): Started @DATABASE_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ -``` - - - - -## Vérification de la stabilité de la plate-forme - -Vous devez maintenant vérifier que tout fonctionne bien : - -* Accès aux menus de l'interface utilisateur web. -* Génération de la configuration des pollers + méthode de rechargement et de redémarrage. -* Planification des contrôles immédiats (Central + Pollers), des accusés de réception, des temps d'arrêt, etc. -* Déplacer des ressources ou redémarrer le serveur actif et vérifier à nouveau que tout va bien. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-20-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-20-10.md deleted file mode 100644 index 9366fed2382c..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-20-10.md +++ /dev/null @@ -1,629 +0,0 @@ ---- -id: upgrade-from-20-10 -title: Montée de version depuis Centreon 20.10 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Ce chapitre décrit la procédure de montée de version de votre plate-forme -Centreon depuis la version 20.10 vers la version 26.10. - -> La version 20.10 n'est plus supportée. La montée de version à partir de cette version n'a pas été testée par l'équipe d'assurance qualité de Centreon. - -Vous ne pouvez pas simplement monter de version depuis une version antérieure à Centreon 20.10 et vers une version 26.10, car CentOS 7 n'est plus supporté: vous devez [migrer votre plateforme vers un OS supporté](../migrate/introduction.md). - -> Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. Dans votre architecture, tous les serveurs doivent avoir la même version de Centreon. De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). - -> Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux -> / RHEL 8 ou 9, vous devez suivre la [procédure de migration](../migrate/migrate-from-el-to-el.md). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. - -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Pour effectuer cette procédure, votre version de MariaDB doit être >= 10.3.22. -> Si cela n'est pas le cas, merci de suivre avant le -> [chapitre de mise à jour de MariaDB](./upgrade-mariadb.md) - -> Attention, suite à la correction d'un problème relatif au schéma de base de données, il sera nécessaire -> d'arrêter l'insertion en base de données des données collectées le temps de la mise à jour. Celles-ci seront stockées -> dans des fichiers temporaires puis insérées à la fin du processus de mise à jour. - -> Attention, si vous utilisiez les connecteurs suivants, à partir de la version 24.10 il est obligatoire de déclarer la configuration de tous ceux-ci [**à la page Configuration > Additional connector configurations**](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) avant de déployer la configuration du collecteur correspondant : -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prérequis - -> Lorsque vous lancez une commande, vérifiez les messages obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance -des sauvegardes de l’ensemble des serveurs centraux de votre plate-forme : - -- Serveur Centreon Central, -- Serveur de gestion de base de données. - -Si vous utilisez un fournisseur Open Ticket avec des configurations personnalisées, [sauvegardez-les avant de mettre à jour Centreon](../alerts-notifications/ticketing-install.md#sauvegarder-votre-configuration-personnalisée-de-fournisseur-openticket). - -### Vérifier les dépôts - -Avant de réaliser la montée de version de votre plateforme Centreon, assurez-vous que les dépôts de paquets suivants sont activés : - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -### Mettre à jour la clé de signature RPM - -> Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. - -## Montée de version du serveur Centreon Central - -> Depuis la version 24.04, Centreon utilise **MariaDB 10.11**. -> -> Le processus suivant met seulement à jour les composants Centreon pour le -> moment. -> -> MariaDB sera mis à jour après. - -### Installer les nouveaux dépôts - -1. Sur votre plateforme 20.10, remplacez `https://packages.centreon.com/rpm-standard` ou `https://yum.centreon.com/standard/` par `https://archives.centreon.com/standard/` dans votre configuration YUM (par défaut, `/etc/yum.repos.d/centreon.repo`). - -2. Mettez à jour votre Centreon 20.10 jusqu'à la dernière version mineure. - -3. Supprimez le fichier **centreon.repo** : - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -4. Installez le nouveau dépôt : - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - -> Si vous avez une [licence offline](../administration/licenses.md#types-de-licences), supprimez également l'ancien dépôt des connecteurs de supervision, puis installez le nouveau dépôt. -> -> Vous pouvez trouver l'adresse des dépôts sur le [portail support Centreon](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). - -### Installer le dépôt MariaDB - - - - -```shell -dnf module enable -y mariadb:10.11 -``` - - - - -### Montée de version de la solution Centreon - -1. Assurez-vous que tous les utilisateurs sont déconnectés avant de commencer la procédure de mise à jour. - -2. Si vous avez des extensions Business installées, supprimez la configuration du dépôt 20.10 : - - - - -```shell -rm /etc/yum.repos.d/centreon-business-20.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-20.10.repo -``` - - - - -3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. - -5. Arrêtez le processus Centreon Broker : - -```shell -systemctl stop cbd -``` - -6. Supprimez les fichiers de rétention présents : - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Montée de version de PHP - -Centreon 26.10 utilise PHP en version 8.4. - - - - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -sudo subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` - -Ensuite, vous devez changer le flux PHP de la version 7.3 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf module reset php -``` - -```shell -dnf module install php:8.2 -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - - - - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Ensuite, vous devez changer le flux PHP de la version 7.3 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf module reset php -``` - -```shell -dnf module install php:8.2 -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - - - - -Puis terminez la montée de version de la solution Centreon. - -1. Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -2. Mettez à jour l'ensemble des composants : - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - - - - -Exécutez les commandes suivantes : - -```shell -systemctl enable php-fpm -systemctl restart php-fpm -``` - - - - -### Mettre à jour une configuration Apache personnalisée - -Cette section s'applique uniquement si vous avez personnalisé votre configuration Apache. - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -#### Configuration Apache personnalisée : activer la compression du texte - -Pour améliorer le temps de chargement des pages, vous pouvez activer la compression du texte sur le serveur Apache. Le paquet **brotli** est nécessaire. Cette configuration est optionnelle mais vous fournira une meilleure expérience utilisateur. - -Ajoutez le code suivant à votre fichier de configuration Apache, dans les éléments `` et `` : - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json -``` - -### Montée de version du serveur MariaDB - -Les composants MariaDB peuvent maintenant être mis à jour. - -> Référez vous à la documentation officielle de MariaDB pour en savoir -> davantage sur ce processus : -> -> https://mariadb.com/kb/en/upgrading-between-major-mariadb-versions/ - -#### Mettre à jour le dépôt Centreon - -> Cette étape est nécessaire seulement si votre environnement comprend une base de données déportée. -> Si le serveur central Centreon et -> MariaDB sont hébergés sur le même serveur, sautez cette étape. - -Exécutez la commande suivante sur le serveur de base de données dédié : - - - - -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -#### Mettre à jour MariaDB - -Il est nécessaire de désinstaller puis réinstaller MariaDB pour changer de version majeure (c'est-à-dire pour passer d'une version 10.3 à une version 10.11). - -1. Arrêtez le service mariadb : - - ```shell - systemctl stop mariadb - ``` - -2. Désinstallez la version actuelle : - - ```shell - rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-compat MariaDB-common - ``` - - > Pendant cette étape de désinstallation, vous pouvez rencontrer une erreur parce qu'un ou plusieurs paquets MariaDB sont manquants. Dans ce cas, vous devez exécuter la commande de désinstallation sans inclure le paquet manquant. - - Par exemple, vous obtenez le message d'erreur suivant : - - ```shell - package MariaDB-compat is not installed - ``` - - Comme le paquet **MariaDB-compat** est manquant, vous devez exécuter la même commande sans citer **MariaDB-compat** : - - ```shell - rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-common - ``` - - > Assurez-vous d'avoir [installé le dépôt officiel de MariaDB](./upgrade-from-20-10.md#installer-le-dépôt-mariadb) avant de poursuivre la procédure. - -3. Installez la version 10.11 : - - ```shell - dnf module enable -y mariadb:10.11 - dnf install mariadb-server-10.11\* mariadb-10.11\* - ``` - -4. Démarrer le service mariadb : - - ```shell - systemctl start mariadb - ``` - -5. Lancez le processus de mise à jour MariaDB : - - ```shell - mysql_upgrade - ``` - - Si votre base de données est protégée par mot de passe, entrez : - - ```shell - mysql_upgrade -u -p - ``` - - Exemple : si votre utilisateur_admin_bdd est `root`, entrez: - - ```shell - mysql_upgrade -u root -p - ``` - - > Référez vous à la [documentation officielle](https://mariadb.com/kb/en/mysql_upgrade/) - > pour plus d'informations ou si des erreurs apparaissent pendant cette dernière étape. - -#### Activer MariaDB au démarrage automatique - -Exécutez la commande suivante : - -```shell -systemctl enable mariadb -``` - -### Finalisation de la mise à jour - - - - -Avant de démarrer la montée de version via l'interface web, mettez à jour [Centreon BAM avec cette procédure](../service-mapping/upgrade.md) puis rechargez le serveur Apache avec la commande suivante : - -```shell -systemctl reload httpd -``` - - - - -Connectez-vous ensuite à l'interface web Centreon pour démarrer le processus de -mise à jour : - -Cliquez sur **Next** : - -![image](../assets/upgrade/web_update_1.png) - -Cliquez sur **Next** : - -![image](../assets/upgrade/web_update_2.png) - -La note de version présente les principaux changements, cliquez sur **Next** : - -![image](../assets/upgrade/web_update_3.png) - -Le processus réalise les différentes mises à jour, cliquez sur **Next** : - -![image](../assets/upgrade/web_update_4.png) - -Votre serveur Centreon est maintenant à jour, cliquez sur **Finish** pour -accéder à la page de connexion : - -![image](../assets/upgrade/web_update_5.png) - -> La présentation de l'interface ayant été modifiée dans la version 22.10, vous devez vider le cache de votre navigateur pour afficher le nouveau thème. - -Référez-vous à la documentation de mise à jour pour [Centreon MBI](../reporting/update.md) et [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. - -### Actions post montée de version - -1. Montée de version des extensions : - - Depuis le menu **Administration > Extensions > Gestionnaire**, mettez à jour - toutes les extensions, en commençant par les suivantes : - - - License Manager, - - Gestionnaire de connecteurs de supervision, - - Auto Discovery. - - Vous pouvez alors mettre à jour toutes les autres extensions commerciales. - -2. Si vous utilisiez des commandes personnalisées pour un collecteur (sur la page **Configuration > Collecteurs > Collecteurs**, dans la section **Monitoring Engine Information**), sachez qu'une nouvelle expression régulière de validation est désormais appliquée (`[a-zA-Z0-9\-\_]+`) : vos commandes personnalisées devront peut-être être adaptées. Sur le serveur central : - * Pour identifier les commandes qui doivent être adaptées, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * Pour adapter automatiquement les commandes, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (Vous pouvez également les adapter manuellement.) - -3. [Déployer la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Redémarrez les processus Centreon : - - ```shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Mettre à jour MariaDB - -Suivez [cette procédure](upgrade-mariadb.md) pour monter de version MariaDB en 10.11. - -## Montée de version des serveurs distants - -Cette procédure est identique à celle utilisée pour effectuer la montée de version d'un serveur Centreon Central, avec en plus la nécessité de récupérer la clé de déchiffrement à la fin. - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP du serveur central afin de permettre au serveur distant de recevoir et traiter des données chiffrées : - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` - -> En fin de mise à jour, la configuration doit être déployée depuis le serveur Central. - -## Montée de version des collecteurs - -### Mise à jour des dépôts - -Exécutez la commande suivante : - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -### Montée de version de la solution Centreon - -Videz le cache : - -```shell -dnf clean all --enablerepo=* -``` - -Mettez à jour l'ensemble des composants : - -```shell -dnf update centreon\* -``` - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -Démarrez et activez **gorgoned**: - -```shell -systemctl start gorgoned -systemctl enable gorgoned -``` - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP correspondante afin de permettre au collecteur de recevoir et traiter des données chiffrées. - -L'adresse IP à utiliser varie selon les conditions suivantes : -- Lorsque vous mettez à jour un collecteur lié directement au server central, utilisez l'adresse IP du serveur central. -- Lorsque vous mettez à jour un collecteur lié à un serveur distant, utilisez l'adresse IP du serveur distant. Cependant, dans ce cas, confirmez d'abord que le server distant a la bonne clé. Vérifiez que la valeur de `app_secret` dans le fichier `/etc/centreon-engine/engine-context.json` du serveur distant est la même que pour le serveur central. Si ce n'est pas le cas, relancez le script avec l'adresse IP pour corriger le fichier .json. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-04.md deleted file mode 100644 index 3c699ef6b5cf..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-04.md +++ /dev/null @@ -1,495 +0,0 @@ ---- -id: upgrade-from-21-04 -title: Montée de version depuis Centreon 21.04 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Ce chapitre décrit la procédure de montée de version de votre plate-forme -Centreon depuis la version 21.04 vers la version 26.10. - -> La version 21.04 n'est plus supportée. La montée de version à partir de cette version n'a pas été testée par l'équipe d'assurance qualité de Centreon. - -> Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. Dans votre architecture, tous les serveurs doivent avoir la même version de Centreon. De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). - -> Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux -> / RHEL 8, vous devez suivre la [procédure de migration](../migrate/migrate-from-el-to-el.md). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. - -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Attention, si vous utilisiez les connecteurs suivants, à partir de la version 24.10 il est obligatoire de déclarer la configuration de tous ceux-ci [**à la page Configuration > Additional connector configurations**](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) avant de déployer la configuration du collecteur correspondant : -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prérequis - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance -des sauvegardes de l’ensemble des serveurs centraux de votre plate-forme : - -- Serveur Centreon Central, -- Serveur de gestion de base de données. - -Si vous utilisez un fournisseur Open Ticket avec des configurations personnalisées, [sauvegardez-les avant de mettre à jour Centreon](../alerts-notifications/ticketing-install.md#sauvegarder-votre-configuration-personnalisée-de-fournisseur-openticket). - -### Vérifier les dépôts - -Avant de réaliser la montée de version de votre plateforme Centreon, assurez-vous que les dépôts de paquets suivants sont activés : - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -### Mettre à jour la clé de signature RPM - -> Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. - -## Montée de version du serveur Centreon Central - -> Lorsque vous lancez une commande, vérifiez les messages obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. - -### Installer les nouveaux dépôts - -1. Sur votre plateforme 21.04, remplacez `https://packages.centreon.com/rpm-standard` ou `https://yum.centreon.com/standard/` par `https://archives.centreon.com/standard/` dans votre configuration YUM (par défaut, `/etc/yum.repos.d/centreon.repo`). - -2. Mettez à jour votre Centreon 21.04 jusqu'à la dernière version mineure. - -3. Supprimez le fichier **centreon.repo** : - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -4. Installez le nouveau dépôt : - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - -> Si vous avez une [licence offline](../administration/licenses.md#types-de-licences), supprimez également l'ancien dépôt des connecteurs de supervision, puis installez le nouveau dépôt. -> -> Vous pouvez trouver l'adresse des dépôts sur le [portail support Centreon](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). - -### Montée de version de la solution Centreon - -1. Assurez-vous que tous les utilisateurs sont déconnectés avant de commencer la procédure de mise à jour. - -2. Si vous avez des extensions Business installées, supprimez la configuration du dépôt 21.04 : - - - - -```shell -rm /etc/yum.repos.d/centreon-business-21.04.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-21.04.repo -``` - - - - -3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. - -4. Arrêtez le processus Centreon Broker : - -```shell -systemctl stop cbd -``` - -5. Supprimez les fichiers de rétention présents : - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Montée de version de PHP - -Centreon 26.10 utilise PHP en version 8.4. - - - - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -sudo subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` - -Ensuite, vous devez changer le flux PHP de la version 7.3 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf module reset php -``` - -```shell -dnf module install php:8.2 -``` - - - - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -``` - -Ensuite, vous devez changer le flux PHP de la version 7.3 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf module reset php -``` - -```shell -dnf module install php:8.2 -``` - - - - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - -Puis, finissez la montée de version de la solution Centreon. - -1. Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -2. Mettez à jour l'ensemble des composants : - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - - - - -Exécutez les commandes suivantes : - -```shell -systemctl enable php-fpm -systemctl restart php-fpm -``` - - - - -### Mettre à jour une configuration Apache personnalisée - -Cette section s'applique uniquement si vous avez personnalisé votre configuration Apache. - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -#### Configuration Apache personnalisée : activer la compression du texte - -Pour améliorer le temps de chargement des pages, vous pouvez activer la compression du texte sur le serveur Apache. Le paquet **brotli** est nécessaire. Cette configuration est optionnelle mais vous fournira une meilleure expérience utilisateur. - -Ajoutez le code suivant à votre fichier de configuration Apache, dans les éléments `` et `` : - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json -``` - -### Finalisation de la mise à jour - - - - -Avant de démarrer la montée de version via l'interface web, mettez à jour [Centreon BAM avec cette procédure](../service-mapping/upgrade.md) puis rechargez le serveur Apache avec la commande suivante : - -```shell -systemctl reload httpd -``` - - - - -Connectez-vous ensuite à l'interface web Centreon pour démarrer le processus de -mise à jour : - -Cliquez sur **Next** : - -![image](../assets/upgrade/web_update_1.png) - -Cliquez sur **Next** : - -![image](../assets/upgrade/web_update_2.png) - -La note de version présente les principaux changements, cliquez sur **Next** : - -![image](../assets/upgrade/web_update_3.png) - -Le processus réalise les différentes mises à jour, cliquez sur **Next** : - -![image](../assets/upgrade/web_update_4.png) - -Votre serveur Centreon est maintenant à jour, cliquez sur **Finish** pour -accéder à la page de connexion : - -![image](../assets/upgrade/web_update_5.png) - -> La présentation de l'interface ayant été modifiée dans la version 22.10, vous devez vider le cache de votre navigateur pour afficher le nouveau thème. - -Référez-vous à la documentation de mise à jour pour [Centreon MBI](../reporting/update.md) et [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. - -### Actions post montée de version - -1. Montée de version des extensions : - - Depuis le menu **Administration > Extensions > Gestionnaire**, mettez à jour - toutes les extensions, en commençant par les suivantes : - - - License Manager, - - Gestionnaire de connecteurs de supervision, - - Auto Discovery. - - Vous pouvez alors mettre à jour toutes les autres extensions commerciales. - -2. Si vous utilisiez des commandes personnalisées pour un collecteur (sur la page **Configuration > Collecteurs > Collecteurs**, dans la section **Monitoring Engine Information**), sachez qu'une nouvelle expression régulière de validation est désormais appliquée (`[a-zA-Z0-9\-\_]+`) : vos commandes personnalisées devront peut-être être adaptées. Sur le serveur central : - * Pour identifier les commandes qui doivent être adaptées, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * Pour adapter automatiquement les commandes, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (Vous pouvez également les adapter manuellement.) - -3. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Redémarrez les processus Centreon : - - ```shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Mettre à jour MariaDB - -Suivez [cette procédure](upgrade-mariadb.md) pour monter de version MariaDB en 10.11. - -## Montée de version des serveurs distants - -Cette procédure est identique à celle utilisée pour effectuer la montée de version d'un serveur Centreon Central, avec en plus la nécessité de récupérer la clé de déchiffrement à la fin. - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP du serveur central afin de permettre au serveur distant de recevoir et traiter des données chiffrées : - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` - -> En fin de mise à jour, la configuration doit être déployée depuis le serveur Central. - -## Montée de version des collecteurs - -### Mise à jour des dépôts - -Exécutez la commande suivante : - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -### Montée de version de la solution Centreon - -Videz le cache : - -```shell -dnf clean all --enablerepo=* -``` - -Mettez à jour l'ensemble des composants : - -```shell -dnf update centreon\* -``` - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -Démarrez et activez **gorgoned**: - -```shell -systemctl start gorgoned -systemctl enable gorgoned -``` -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP correspondante afin de permettre au collecteur de recevoir et traiter des données chiffrées. - -L'adresse IP à utiliser varie selon les conditions suivantes : -- Lorsque vous mettez à jour un collecteur lié directement au server central, utilisez l'adresse IP du serveur central. -- Lorsque vous mettez à jour un collecteur lié à un serveur distant, utilisez l'adresse IP du serveur distant. Cependant, dans ce cas, confirmez d'abord que le server distant a la bonne clé. Vérifiez que la valeur de `app_secret` dans le fichier `/etc/centreon-engine/engine-context.json` du serveur distant est la même que pour le serveur central. Si ce n'est pas le cas, relancez le script avec l'adresse IP pour corriger le fichier .json. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-10.md deleted file mode 100644 index 3cb649d25a7e..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-21-10.md +++ /dev/null @@ -1,525 +0,0 @@ ---- -id: upgrade-from-21-10 -title: Montée de version depuis Centreon 21.10 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 21.10 vers la version 26.10. - -> La version 21.10 n'est plus supportée. La montée de version à partir de cette version n'a pas été testée par l'équipe d'assurance qualité de Centreon. - -> Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. Dans votre architecture, tous les serveurs doivent avoir la même version de Centreon. De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). - -> Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux -> / RHEL 8, vous devez suivre la [procédure de migration](../migrate/migrate-from-el-to-el.md). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. - -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Attention, si vous utilisiez les connecteurs suivants, à partir de la version 24.10 il est obligatoire de déclarer la configuration de tous ceux-ci [**à la page Configuration > Additional connector configurations**](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) avant de déployer la configuration du collecteur correspondant : -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prérequis - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance -des sauvegardes de l’ensemble des serveurs centraux de votre plate-forme : - -- Serveur Centreon Central, -- Serveur de gestion de base de données. - -Si vous utilisez un fournisseur Open Ticket avec des configurations personnalisées, [sauvegardez-les avant de mettre à jour Centreon](../alerts-notifications/ticketing-install.md#sauvegarder-votre-configuration-personnalisée-de-fournisseur-openticket). - -### Vérifier les dépôts - -Avant de réaliser la montée de version de votre plateforme Centreon, assurez-vous que les dépôts de paquets suivants sont activés : - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## Montée de version du serveur Centreon Central - -> Lorsque vous lancez une commande, vérifiez les messages obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. - -### Installer les nouveaux dépôts - -1. Sur votre plateforme 21.10, remplacez `https://packages.centreon.com/rpm-standard` ou `https://yum.centreon.com/standard/` par `https://archives.centreon.com/standard/` dans votre configuration YUM (par défaut, `/etc/yum.repos.d/centreon.repo`). - -2. Mettez à jour votre Centreon 21.10 jusqu'à la dernière version mineure. - -3. Supprimez le fichier **centreon.repo** : - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -4. Installez le nouveau dépôt : - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - -> Si vous avez une [licence offline](../administration/licenses.md#types-de-licences), supprimez également l'ancien dépôt des connecteurs de supervision, puis installez le nouveau dépôt. -> -> Vous pouvez trouver l'adresse des dépôts sur le [portail support Centreon](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). - -### Montée de version de la solution Centreon - -1. Assurez-vous que tous les utilisateurs sont déconnectés avant de commencer la procédure de mise à jour. - -2. Si vous avez des extensions Business installées, supprimez la configuration du dépôt 21.10 : - - - - -```shell -rm /etc/yum.repos.d/centreon-business-21.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-21.10.repo -``` - - - - -3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. - -4. Arrêtez le processus Centreon Broker : - -```shell -systemctl stop cbd -``` - -5. Supprimez les fichiers de rétention présents : - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Montée de version de PHP - -Centreon 26.10 utilise PHP en version 8.4. - - - - -Vous devez changer le flux PHP de la version 8.0 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.1 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module install php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -Vous devez changer le flux PHP de la version 8.0 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.1 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module install php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -### Montée de version de la solution Centreon - -1. Assurez-vous que tous les utilisateurs sont déconnectés avant de commencer la procédure de mise à jour. - -2. Si vous avez des extensions Business installées, supprimez la configuration du dépôt 21.10 : - - - - -```shell -rm /etc/yum.repos.d/centreon-business-21.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-21.10.repo -``` - - - - -3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. - -5. Arrêtez le processus Centreon Broker : - -```shell -systemctl stop cbd -``` - -6. Supprimez les fichiers de rétention présents : - -```shell -rm /var/lib/centreon-broker/* -f -``` - -1. Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -2. Mettez à jour l'ensemble des composants : - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -### Mettre à jour une configuration Apache personnalisée - -Cette section s'applique uniquement si vous avez personnalisé votre configuration Apache. - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -#### Configuration Apache personnalisée : activer la compression du texte - -Pour améliorer le temps de chargement des pages, vous pouvez activer la compression du texte sur le serveur Apache. Le paquet **brotli** est nécessaire. Cette configuration est optionnelle mais vous fournira une meilleure expérience utilisateur. - -Ajoutez le code suivant à votre fichier de configuration Apache, dans les éléments `` et `` : - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json -``` - -### Finalisation de la mise à jour - - - - -Avant de démarrer la montée de version via l'interface web, mettez à jour [Centreon BAM avec cette procédure](../service-mapping/upgrade.md) puis rechargez le serveur Apache avec la commande suivante : -```shell -systemctl reload httpd -``` - - - - -Connectez-vous ensuite à l'interface web Centreon pour démarrer le processus de -mise à jour : - -Cliquez sur **Next** : - -![image](../assets/upgrade/web_update_1.png) - -Cliquez sur **Next** : - -![image](../assets/upgrade/web_update_2.png) - -La note de version présente les principaux changements, cliquez sur **Next** : - -![image](../assets/upgrade/web_update_3.png) - -Le processus réalise les différentes mises à jour, cliquez sur **Next** : - -![image](../assets/upgrade/web_update_4.png) - -Votre serveur Centreon est maintenant à jour, cliquez sur **Finish** pour -accéder à la page de connexion : - -![image](../assets/upgrade/web_update_5.png) - -> La présentation de l'interface ayant été modifiée dans la version 22.10, vous devez vider le cache de votre navigateur pour afficher le nouveau thème. - -Référez-vous à la documentation de mise à jour pour [Centreon MBI](../reporting/update.md) et [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. - -### Actions post montée de version - -1. Montée de version des extensions : - - Depuis le menu **Administration > Extensions > Gestionnaire**, mettez à jour - toutes les extensions, en commençant par les suivantes : - - - License Manager, - - Gestionnaire de connecteurs de supervision, - - Auto Discovery. - - Vous pouvez alors mettre à jour toutes les autres extensions commerciales. - -2. Si vous utilisiez des commandes personnalisées pour un collecteur (sur la page **Configuration > Collecteurs > Collecteurs**, dans la section **Monitoring Engine Information**), sachez qu'une nouvelle expression régulière de validation est désormais appliquée (`[a-zA-Z0-9\-\_]+`) : vos commandes personnalisées devront peut-être être adaptées. Sur le serveur central : - * Pour identifier les commandes qui doivent être adaptées, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * Pour adapter automatiquement les commandes, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (Vous pouvez également les adapter manuellement.) - -3. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Redémarrez les processus Centreon : - - ```shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Mettre à jour MariaDB - -Suivez [cette procédure](upgrade-mariadb.md) pour monter de version MariaDB en 10.11. - -## Montée de version des serveurs distants - -Cette procédure est identique à celle utilisée pour effectuer la montée de version d'un serveur Centreon Central, avec en plus la nécessité de récupérer la clé de déchiffrement à la fin. - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP du serveur central afin de permettre au serveur distant de recevoir et traiter des données chiffrées : - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` - -> En fin de mise à jour, la configuration doit être déployée depuis le serveur Central. - -## Montée de version des collecteurs - -### Mise à jour des dépôts - -Exécutez la commande suivante : - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -### Montée de version de la solution Centreon - -Videz le cache : - -```shell -dnf clean all --enablerepo=* -``` - -Mettez à jour l'ensemble des composants : - -```shell -dnf update centreon\* -``` - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -Démarrez et activez **gorgoned**: - -```shell -systemctl start gorgoned -systemctl enable gorgoned -``` - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP correspondante afin de permettre au collecteur de recevoir et traiter des données chiffrées. - -L'adresse IP à utiliser varie selon les conditions suivantes : -- Lorsque vous mettez à jour un collecteur lié directement au server central, utilisez l'adresse IP du serveur central. -- Lorsque vous mettez à jour un collecteur lié à un serveur distant, utilisez l'adresse IP du serveur distant. Cependant, dans ce cas, confirmez d'abord que le server distant a la bonne clé. Vérifiez que la valeur de `app_secret` dans le fichier `/etc/centreon-engine/engine-context.json` du serveur distant est la même que pour le serveur central. Si ce n'est pas le cas, relancez le script avec l'adresse IP pour corriger le fichier .json. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-04.md deleted file mode 100644 index 3c6976b98785..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-04.md +++ /dev/null @@ -1,752 +0,0 @@ ---- -id: upgrade-from-22-04 -title: Montée de version depuis Centreon 22.04 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 22.04 vers la version 26.10. - -> La version 22.04 n'est plus supportée. La montée de version à partir de cette version n'a pas été testée par l'équipe d'assurance qualité de Centreon. - -> Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. Dans votre architecture, tous les serveurs doivent avoir la même version de Centreon. De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). - -> Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux -> / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). -> Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. - -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian 11, vous devez d'abord migrer en Debian 12 avant d'upgrader Centreon. Voir [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. - -> Attention, si vous utilisiez les connecteurs suivants, à partir de la version 24.10 il est obligatoire de déclarer la configuration de tous ceux-ci [**à la page Configuration > Additional connector configurations**](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) avant de déployer la configuration du collecteur correspondant : -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prérequis - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance -des sauvegardes de l’ensemble des serveurs centraux de votre plate-forme : - -- Serveur Centreon Central, -- Serveur de gestion de base de données. - -Si vous utilisez un fournisseur Open Ticket avec des configurations personnalisées, [sauvegardez-les avant de mettre à jour Centreon](../alerts-notifications/ticketing-install.md#sauvegarder-votre-configuration-personnalisée-de-fournisseur-openticket). - -### Vérifier les dépôts - -Avant de réaliser la montée de version de votre plateforme Centreon, assurez-vous que les dépôts de paquets suivants sont activés : - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## Montée de version du serveur Centreon Central - -Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian 11, vous devez d'abord migrer en Debian 12 avant d'upgrader Centreon. Voir [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). - -> Lorsque vous lancez une commande, vérifiez les messages obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. - -### Installer les nouveaux dépôts - - - - -1. Mettez à jour votre Centreon 22.04 jusqu'à la dernière version mineure. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/22.04/el8/centreon-22.04-el8.repo - dnf clean all --enablerepo=* - dnf update - ``` - - -2. Supprimez le fichier **centreon-22.04.repo** : - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Installez le nouveau dépôt : - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - - - - -1. Mettez à jour votre Centreon 22.04 jusqu'à la dernière version mineure. -2. Exécutez les commandes suivantes : - -```shell -rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Ensuite, importez la clé du dépôt : - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -> Si vous avez une [licence offline](../administration/licenses.md#types-de-licences), supprimez également l'ancien dépôt des connecteurs de supervision, puis installez le nouveau dépôt. -> -> Vous pouvez trouver l'adresse des dépôts sur le [portail support Centreon](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). - -### Montée de version de la solution Centreon - -1. Assurez-vous que tous les utilisateurs sont déconnectés avant de commencer la procédure de mise à jour. - -2. Si vous avez des extensions Business installées, supprimez la configuration du dépôt 22.04 : - - - - -```shell -rm /etc/yum.repos.d/centreon-business-22.04.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-22.04.repo -``` - - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - - - - -3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. - -4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). - -5. Arrêtez le processus Centreon Broker : - -```shell -systemctl stop cbd -``` - -6. Supprimez les fichiers de rétention présents : - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Montée de version de PHP - -Centreon 26.10 utilise PHP en version 8.4. - - - - -Vous devez changer le flux PHP de la version 8.0 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.1 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module install php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -Vous devez changer le flux PHP de la version 8.0 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.1 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module install php:8.2 -dnf distro-sync php\* --allowerasing --enablerepo=centreon-26.10-unstable -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -```shell -systemctl stop php8.0-fpm -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - - - - -Puis, finissez, la montée de version de la solution Centreon. - -1. Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -2. Mettez à jour l'ensemble des composants : - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -### Mettre à jour une configuration Apache personnalisée - -Cette section s'applique uniquement si vous avez personnalisé votre configuration Apache. - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -Utilisez la sauvegarde que vous avez effectuée à l'étape précédente pour reporter vos personnalisations dans le fichier **/etc/apache2/sites-available/centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apache2ctl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php8.2-fpm apache2 -``` - -Puis vérifiez le statut : - -```shell -systemctl status apache2 -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -#### Configuration Apache personnalisée : activer la compression du texte - -Pour améliorer le temps de chargement des pages, vous pouvez activer la compression du texte sur le serveur Apache. Le paquet **brotli** est nécessaire. Cette configuration est optionnelle mais vous fournira une meilleure expérience utilisateur. - -Ajoutez le code suivant à votre fichier de configuration Apache, dans les éléments `` et `` : - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json -``` - -### Finalisation de la mise à jour - -Avant de démarrer la montée de version via l'interface web, mettez à jour [Centreon BAM avec cette procédure](../service-mapping/upgrade.md) puis rechargez le serveur Apache avec les commandes suivantes : - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl stop php8.0-fpm.service -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - - - - -Vous devez ensuite finaliser le processus de mise à jour : - - - - -1. Connectez-vous à l'interface web Centreon, l'assistant d'interface s'affiche. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_1.png) - -2. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_2.png) - -3. La note de version présente les principaux changements, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_3.png) - -4. Le processus réalise les différentes mises à jour, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_4.png) - -5. Votre serveur Centreon est maintenant à jour, cliquez sur **Finish** pour -accéder à la page de connexion : - - ![image](../assets/upgrade/web_update_5.png) - - - - - -1. Connectez-vous au serveur Central via le terminal pour poursuivre le processus de -mise à jour. - - > Vous avez besoin d'un token d'authentification pour accéder à l'endpoint de l'API. Suivez la procédure ci-dessous pour obtenir un token. - - Dans notre cas, nous avons la configuration décrite ci-dessous (vous devez adapter la procédure à votre configuration). - - - adresse : 10.25.XX.XX - - port : 80 - - version : 26.10 - - identifiant : Admin - - mot de passe : xxxxx - -2. Entrez la requête suivante : - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - Voici à quoi ressemble le résultat : - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost", "is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Récupérez le numéro du token pour l'utiliser lors de la prochaine requête. - -4. Entrez ensuite cette requête : - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. Cette requête ne renvoie aucun résultat. Pour vérifier que la mise à jour a bien été appliquée, consultez le numéro de version affiché sur la page de connexion à l'interface web Centreon. - - - - -Enfin, redémarrez Broker, Engine et Gorgone sur le serveur Central en exécutant la commande suivante : - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Ajoutez l'utilisateur **apache** au groupe **centreon-broker** et vice versa. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - - - - -> La présentation de l'interface ayant été modifiée dans la version 22.10, vous devez vider le cache de votre navigateur pour afficher le nouveau thème. - -Référez-vous à la documentation de mise à jour pour [Centreon MBI](../reporting/update.md) et [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. - -### Actions post montée de version - -1. Montée de version des extensions : - - Depuis le menu **Administration > Extensions > Gestionnaire**, mettez à jour - toutes les extensions, en commençant par les suivantes : - - - License Manager, - - Gestionnaire de connecteurs de supervision, - - Auto Discovery. - - Vous pouvez alors mettre à jour toutes les autres extensions commerciales. - -2. Si vous utilisiez des commandes personnalisées pour un collecteur (sur la page **Configuration > Collecteurs > Collecteurs**, dans la section **Monitoring Engine Information**), sachez qu'une nouvelle expression régulière de validation est désormais appliquée (`[a-zA-Z0-9\-\_]+`) : vos commandes personnalisées devront peut-être être adaptées. Sur le serveur central : - * Pour identifier les commandes qui doivent être adaptées, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * Pour adapter automatiquement les commandes, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (Vous pouvez également les adapter manuellement.) - -3. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Redémarrez les processus Centreon : - - ```shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Mettre à jour MariaDB - -Suivez [cette procédure](upgrade-mariadb.md) pour monter de version MariaDB en 10.11. - -## Montée de version des serveurs distants - -Cette procédure est identique à celle utilisée pour effectuer la montée de version d'un serveur Centreon Central, avec en plus la nécessité de récupérer la clé de déchiffrement à la fin. - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP du serveur central afin de permettre au serveur distant de recevoir et traiter des données chiffrées : - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` - -> En fin de mise à jour, la configuration doit être déployée depuis le serveur Central. - -## Montée de version des collecteurs - -### Mise à jour des dépôts - -Exécutez la commande suivante : - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -apt update -``` - - - - -### Montée de version de la solution Centreon - -Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean -apt update -``` - - - - -Mettez à jour l'ensemble des composants : - - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -apt install --only-upgrade centreon-poller -``` - - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -Redémarrez **centreon** : - -```shell -systemctl restart centreon -``` - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP correspondante afin de permettre au collecteur de recevoir et traiter des données chiffrées. - -L'adresse IP à utiliser varie selon les conditions suivantes : -- Lorsque vous mettez à jour un collecteur lié directement au server central, utilisez l'adresse IP du serveur central. -- Lorsque vous mettez à jour un collecteur lié à un serveur distant, utilisez l'adresse IP du serveur distant. Cependant, dans ce cas, confirmez d'abord que le server distant a la bonne clé. Vérifiez que la valeur de `app_secret` dans le fichier `/etc/centreon-engine/engine-context.json` du serveur distant est la même que pour le serveur central. Si ce n'est pas le cas, relancez le script avec l'adresse IP pour corriger le fichier .json. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-10.md deleted file mode 100644 index 6c29896f0b3c..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-22-10.md +++ /dev/null @@ -1,731 +0,0 @@ ---- -id: upgrade-from-22-10 -title: Montée de version depuis Centreon 22.10 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 22.10 vers la version 26.10. - -> La version 22.10 n'est plus supportée. La montée de version à partir de cette version n'a pas été testée par l'équipe d'assurance qualité de Centreon. - -> Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. Dans votre architecture, tous les serveurs doivent avoir la même version de Centreon. De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). - -> Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux -> / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). -> Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. - -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian 11, vous devez d'abord migrer en Debian 12 avant d'upgrader Centreon. Voir [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. - -> Attention, si vous utilisiez les connecteurs suivants, à partir de la version 24.10 il est obligatoire de déclarer la configuration de tous ceux-ci [**à la page Configuration > Additional connector configurations**](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) avant de déployer la configuration du collecteur correspondant : -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prérequis - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance -des sauvegardes de l’ensemble des serveurs centraux de votre plate-forme : - -- Serveur Centreon Central, -- Serveur de gestion de base de données. - -Si vous utilisez un fournisseur Open Ticket avec des configurations personnalisées, [sauvegardez-les avant de mettre à jour Centreon](../alerts-notifications/ticketing-install.md#sauvegarder-votre-configuration-personnalisée-de-fournisseur-openticket). - -### Vérifier les dépôts - -Avant de réaliser la montée de version de votre plateforme Centreon, assurez-vous que les dépôts de paquets suivants sont activés : - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## Montée de version du serveur Centreon Central - -> Lorsque vous lancez une commande, vérifiez les messages obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. - -### Installation du nouveau dépôt Centreon - - - - -1. Mettez à jour votre Centreon 22.10 jusqu'à la dernière version mineure. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/22.10/el8/centreon-22.10-el8.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Supprimez le fichier **centreon-22.10.repo** : - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Installez le nouveau dépôt : - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - - - - -1. Mettez à jour votre Centreon 22.10 jusqu'à la dernière version mineure. -2. Exécutez les commandes suivantes : - -```shell -rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Ensuite, importez la clé du dépôt : - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -> Si vous avez une [licence offline](../administration/licenses.md#types-de-licences), supprimez également l'ancien dépôt des connecteurs de supervision, puis installez le nouveau dépôt. -> -> Vous pouvez trouver l'adresse des dépôts sur le [portail support Centreon](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). - -### Montée de version de la solution Centreon - -1. Assurez-vous que tous les utilisateurs sont déconnectés avant de commencer la procédure de mise à jour. - -2. Si vous avez des extensions Business installées, supprimez la configuration du dépôt 22.10 : - - - - -```shell -rm /etc/yum.repos.d/centreon-business-22.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-22.10.repo -``` - - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - - - - -3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. - -4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). - -5. Arrêtez le processus Centreon Broker : - -```shell -systemctl stop cbd -``` - -6. Supprimez les fichiers de rétention présents : - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Montée de version de PHP - -Centreon 26.10 utilise PHP en version 8.4. - - - - -Vous devez changer le flux PHP de la version 8.1 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.1 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -Vous devez changer le flux PHP de la version 8.1 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - - - - -```shell -systemctl stop php8.1-fpm -systemctl disable php8.1-fpm -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php/8.2/fpm/conf.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - - - - -Puis, terminez la montée de version de la solution Centreon. - -1. Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -2. Mettez à jour l'ensemble des composants : - - - - -```shell -yum update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -### Mettre à jour une configuration Apache personnalisée - -Cette section s'applique uniquement si vous avez personnalisé votre configuration Apache. - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -Utilisez la sauvegarde que vous avez effectuée à l'étape précédente pour reporter vos personnalisations dans le fichier **/etc/apache2/sites-available/centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apache2ctl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Vérifiez le statut d'Apache : - -```shell -systemctl status apache2 -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2024-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -#### Configuration Apache personnalisée : activer la compression du texte - -Pour améliorer le temps de chargement des pages, vous pouvez activer la compression du texte sur le serveur Apache. Le paquet **brotli** est nécessaire. Cette configuration est optionnelle mais vous fournira une meilleure expérience utilisateur. - -Ajoutez le code suivant à votre fichier de configuration Apache, dans les éléments `` et `` : - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json -``` - -### Finalisation de la mise à jour - -Avant de démarrer la montée de version via l'interface web, mettez à jour [Centreon BAM avec cette procédure](../service-mapping/upgrade.md) puis rechargez le serveur Apache avec les commandes suivantes : - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - - - - -Vous devez ensuite finaliser le processus de mise à jour : - - - - -1. Connectez-vous à l'interface web Centreon, l'assistant d'interface s'affiche. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_1.png) - -2. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_2.png) - -3. La note de version présente les principaux changements, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_3.png) - -4. Le processus réalise les différentes mises à jour, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_4.png) - -5. Votre serveur Centreon est maintenant à jour, cliquez sur **Finish** pour -accéder à la page de connexion : - - ![image](../assets/upgrade/web_update_5.png) - - - - - -1. Connectez-vous au serveur Central via le terminal pour poursuivre le processus de -mise à jour. - - > Vous avez besoin d'un token d'authentification pour accéder à l'endpoint de l'API. Suivez la procédure ci-dessous pour obtenir un token. - - Dans notre cas, nous avons la configuration décrite ci-dessous (vous devez adapter la procédure à votre configuration). - - - adresse : 10.25.XX.XX - - port : 80 - - version : 26.10 - - identifiant : Admin - - mot de passe : xxxxx - -2. Entrez la requête suivante : - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - Voici à quoi ressemble le résultat : - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost", "is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Récupérez le numéro du token pour l'utiliser lors de la prochaine requête. - -4. Entrez ensuite cette requête : - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. Cette requête ne renvoie aucun résultat. Pour vérifier que la mise à jour a bien été appliquée, consultez le numéro de version affiché sur la page de connexion à l'interface web Centreon. - - - - -Enfin, redémarrez Broker, Engine et Gorgone sur le serveur Central en exécutant la commande suivante : - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Ajoutez l'utilisateur **apache** au groupe **centreon-broker** et vice versa. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - - - - -Référez-vous à la documentation de mise à jour pour [Centreon MBI](../reporting/update.md) et [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. - -### Actions post montée de version - -1. Montée de version des extensions : - - Depuis le menu **Administration > Extensions > Gestionnaire**, mettez à jour - toutes les extensions, en commençant par les suivantes : - - - License Manager, - - Monitoring Connector Manager, - - Auto Discovery. - - Vous pouvez alors mettre à jour toutes les autres extensions commerciales. - -2. Si vous utilisiez des commandes personnalisées pour un collecteur (sur la page **Configuration > Collecteurs > Collecteurs**, dans la section **Monitoring Engine Information**), sachez qu'une nouvelle expression régulière de validation est désormais appliquée (`[a-zA-Z0-9\-\_]+`) : vos commandes personnalisées devront peut-être être adaptées. Sur le serveur central : - * Pour identifier les commandes qui doivent être adaptées, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * Pour adapter automatiquement les commandes, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (Vous pouvez également les adapter manuellement.) - -3. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Redémarrez les processus Centreon : - - ```shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Mettre à jour MariaDB - -Suivez [cette procédure](upgrade-mariadb.md) pour monter de version MariaDB en 10.11. - -## Montée de version des serveurs distants - -Cette procédure est identique à celle utilisée pour effectuer la montée de version d'un serveur Centreon Central, avec en plus la nécessité de récupérer la clé de déchiffrement à la fin. - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP du serveur central afin de permettre au serveur distant de recevoir et traiter des données chiffrées : - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` - -> En fin de mise à jour, la configuration doit être déployée depuis le serveur Central. - -## Montée de version des collecteurs - -### Mise à jour des dépôts - -Exécutez la commande suivante : - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -apt update -``` - - - - -### Montée de version de la solution Centreon - -Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean -apt update -``` - - - - -Mettez à jour l'ensemble des composants : - - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -apt install --only-upgrade centreon-poller -``` - - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -Redémarrez **centreon** : - -```shell -systemctl restart centreon -``` - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP correspondante afin de permettre au collecteur de recevoir et traiter des données chiffrées. - -L'adresse IP à utiliser varie selon les conditions suivantes : -- Lorsque vous mettez à jour un collecteur lié directement au server central, utilisez l'adresse IP du serveur central. -- Lorsque vous mettez à jour un collecteur lié à un serveur distant, utilisez l'adresse IP du serveur distant. Cependant, dans ce cas, confirmez d'abord que le server distant a la bonne clé. Vérifiez que la valeur de `app_secret` dans le fichier `/etc/centreon-engine/engine-context.json` du serveur distant est la même que pour le serveur central. Si ce n'est pas le cas, relancez le script avec l'adresse IP pour corriger le fichier .json. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-04.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-04.md deleted file mode 100644 index ee2d853708ba..000000000000 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-04.md +++ /dev/null @@ -1,559 +0,0 @@ ---- -id: upgrade-centreon-ha-from-21-04 -title: Upgrade Centreon HA from Centreon 21.04 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -This chapter describes how to upgrade your Centreon HA platform from version 21.04 -to version 25.10. - -You cannot simply upgrade a platform with Centreon HA (or Centreon Failover) from a version earlier than 21.04 to version 25.10, as CentOS 7 is no longer supported. You need to [migrate your platform to a supported OS](../../migrate/introduction.md), then install Centreon HA on the new platform. Contact your Centreon sales representative to discuss any migration with HA. - -## Prerequisites - -### Suspend cluster resources management - -In order to avoid a failover of the cluster during the update, it is necessary to unmanage all Centreon resources, as well as MariaDB. - -```bash -pcs property set maintenance-mode=true -``` - -### 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](../../security/key-rotation.md#existing-installation), to remove the old key and install the new one. - -### Update the centreon_central_sync script (MBI only) - -This step is only necessary if you use [MBI](../../reporting/introduction.md). Update the script `/usr/share/centreon-ha/bin/centreon_central_sync` at the following lines: - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua"], -``` - -For MBI reports to still be downloadable later on, the lines must be updated like this: - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua", "/var/lib/centreon/centreon-bi-server/archives"], -``` - -## Upgrade process - -To perform the upgrade, please [follow the official documentation](../../upgrade/upgrade-from-21-04.md) only on the **active central node** and **active database node if needed**. - -Then perform the following commands only on the Central Servers: - - - - -```shell -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - - - - -On the passive central node, move the "install" directory to avoid getting the "upgrade" screen in the WUI in the event of a further exchange of roles. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-YYYY-MM-DD -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - -### Removing cron jobs - -The RPM upgrade puts cron jobs back in place on the central and database servers. Remove them to avoid concurrent executions: - -```bash -rm -rf /etc/cron.d/centreon -rm -rf /etc/cron.d/centstorage -rm -f /etc/cron.d/centreon-ha-mysql -``` - -As you have deleted the **centreon-ha-mysql** cron, check that the following line appears in the **server** section of the **/etc/my.cnf.d/server.cnf** file: - -```shell -expire_logs_days=7 -``` - -If the line is not there, add it, then restart the **ms_mysql** resource: - -```shell -pcs resource restart ms_mysql -``` - -### Reset the permissions for centreon_central_sync resource - -The RPM upgrade puts the permissions back in place on the **central servers**. Change them using these commands: - -```bash -chmod 775 /var/log/centreon-engine/ -mkdir /var/log/centreon-engine/archives -chown centreon-engine: /var/log/centreon-engine/archives -chmod 775 /var/log/centreon-engine/archives/ -find /var/log/centreon-engine/ -type f -exec chmod 664 {} \; -find /usr/share/centreon/www/img/media -type d -exec chmod 775 {} \; -find /usr/share/centreon/www/img/media -type f \( ! -iname ".keep" ! -iname ".htaccess" \) -exec chmod 664 {} \; -``` - -## Cluster upgrade - -From Centreon 22.04, MariaDB Replication is based on [GTID](https://mariadb.com/kb/en/gtid/). -It is necessary to destroy the cluster completely and then reconfigure it with -the latest version of the Centreon and MariaDB Replication mechanisms. - -### Maintenance mode and backup - -Perform a backup of the cluster using: - -```bash -pcs config backup centreon_cluster -pcs config export pcs-commands | sed -e :a -e '/\\$/N; s/\\\n//; ta' | sed 's/-f tmp-cib.xml//' | egrep "create|group" | egrep -v "(mysql|php|cbd_rrd)" > centreon_pcs_command.sh -``` - -Check that the file `centreon_cluster.tar.bz2` exists before continuing this procedure. - -```bash -ls -l centreon_cluster.tar.bz2 -``` - -You should have a result like this: - -```text --rw------- 1 root root 2777 May 3 17:49 centreon_cluster.tar.bz2 -``` - -Then check the file centreon_pcs_command.sh. The export command may display some warning lines, but this is not blocking. - -```bash -cat centreon_pcs_command.sh -``` - -The content should looks like this: - -```text -pcs resource create vip ocf:heartbeat:IPaddr2 broadcast=@VIP_BROADCAST_IPADDR@ cidr_netmask=@VIP_CIDR_NETMASK@ flush_routes=true ip=@VIP_IPADDR@ nic=@VIP_IFNAME@ op monitor interval=10s timeout=20s start interval=0s timeout=20s stop interval=0s timeout=20s meta target-role=started -pcs resource create http systemd:httpd24-httpd op monitor interval=5s timeout=20s start interval=0s timeout=40s stop interval=0s timeout=40s meta target-role=started -pcs resource create gorgone systemd:gorgoned op monitor interval=5s timeout=20s start interval=0s timeout=90s stop interval=0s timeout=90s meta target-role=started -pcs resource create centreon_central_sync systemd:centreon-central-sync op monitor interval=5s timeout=20s start interval=0s timeout=90s stop interval=0s timeout=90s meta target-role=started -pcs resource create cbd_central_broker systemd:cbd-sql op monitor interval=5s timeout=30s start interval=0s timeout=90s stop interval=0s timeout=90s meta target-role=started -pcs resource create centengine systemd:centengine op monitor interval=5s timeout=30s start interval=0s timeout=90s stop interval=0s timeout=90s meta multiple-active=stop_start target-role=started -pcs resource create centreontrapd systemd:centreontrapd op monitor interval=5s timeout=20s start interval=0s timeout=30s stop interval=0s timeout=30s meta target-role=started -pcs resource create snmptrapd systemd:snmptrapd op monitor interval=5s timeout=20s start interval=0s timeout=30s stop interval=0s timeout=30s meta target-role=started -pcs resource group add centreon vip http gorgone centreon_central_sync cbd_central_broker centengine centreontrapd snmptrapd -``` - -This file will be necessary to recreate all the resources of your cluster. - -### Delete the resources - -These commands should run only on the active central node: - - - - -```bash -pcs resource delete ms_mysql --force -pcs resource delete cbd_rrd --force -pcs resource delete php7 --force -pcs resource delete centreon --force -``` - - - - -```bash -pcs resource delete ms_mysql --force -pcs resource delete vip_mysql --force -pcs resource delete cbd_rrd --force -pcs resource delete php7 --force -pcs resource delete centreon --force -``` - - - - -### Reconfigure MariaDB - -It is necessary to modify the mysql configuration by editing the file `/etc/my.cnf.d/server.cnf`: - -> On the 2 Central servers in HA 2 nodes -> On the 2 Database servers in HA 4 nodes. - -```shell -[server] -... -skip-slave-start -log-slave-updates -gtid_strict_mode=ON -expire_logs_days=7 -ignore-db-dir=lost+found -... -``` - -### Launch GTID replication - -Run this command **on the secondary database node**: - -```bash -mysqladmin -p shutdown -``` - -It is important to make sure that MariaDB is completely shut down. Run this command and check that it returns no output: - -```bash -ps -ef | grep mariadb[d] -``` - -Once the service is stopped **on the secondary database node**, run the synchronization script **from the primary database node**: - -```bash -mysqladmin -p shutdown -systemctl restart mariadb -/usr/share/centreon-ha/bin/mysql-sync-bigdb.sh -``` - -This script's output is very verbose and you can't expect to understand everything, so to make sure it went well, focus on the last lines of its output, checking that it looks like this: - -```text -Umount and Delete LVM snapshot - Logical volume "dbbackupdatadir" successfully removed -Start MySQL Slave -Start Replication -Id User Host db Command Time State Info Progress -[variable number of lines] -``` - -The important thing to check is that `Start MySQL Slave` and `Start Replication` are present and are not followed by any errors. - -In addition, the output of this command must display only `OK` results: - -```bash -/usr/share/centreon-ha/bin/mysql-check-status.sh -``` - -The expected output is: - -```text -Connection Status '@CENTRAL_MASTER_NAME@' [OK] -Connection Status '@CENTRAL_SLAVE_NAME@' [OK] -Slave Thread Status [OK] -Position Status [OK] -``` - -### Restart Centreon process - -Then to restart all the processes on the **active central node**: - -```bash -systemctl restart cbd-sql cbd gorgoned centengine centreontrapd -``` - -And on the **passive central node**: - -```bash -systemctl restart cbd -``` - -### Clean broker memory files - -> **WARNING:** perform this command only on the **passive central node**. - -Before resuming cluster resource management, to avoid broker issues, clean up all the *.memory.*, *.unprocessed.* or *.queue.* files: - -```bash -rm -rf /var/lib/centreon-broker/central-broker-master.memory* -rm -rf /var/lib/centreon-broker/central-broker-master.queue* -rm -rf /var/lib/centreon-broker/central-broker-master.unprocessed* -``` - -### Recreate the cluster resources - -To be run **only on one central node**: - -> **WARNING:** the syntax of the following command depends on the Linux Distribution you are using. - -> You can find @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ @MARIADB_REPL_USER@ -@MARIADB_REPL_USER@ variable in `/etc/centreon-ha/mysql-resources.sh`. - - - - -```bash -pcs resource create "ms_mysql" \ - ocf:heartbeat:mariadb-centreon \ - config="/etc/my.cnf.d/server.cnf" \ - pid="/var/lib/mysql/mysql.pid" \ - datadir="/var/lib/mysql" \ - socket="/var/lib/mysql/mysql.sock" \ - binary="/usr/bin/mysqld_safe" \ - node_list="@CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@" \ - replication_user="@MARIADB_REPL_USER@" \ - replication_passwd='@MARIADB_REPL_PASSWD@' \ - test_user="@MARIADB_REPL_USER@" \ - test_passwd="@MARIADB_REPL_PASSWD@" \ - test_table='centreon.host' -``` - - - - -> **WARNING:** the syntax of the following command depends on the Linux Distribution you are using. - - - - - - -```bash -pcs resource promotable ms_mysql \ - master-node-max="1" \ - clone_max="2" \ - globally-unique="false" \ - clone-node-max="1" \ - notify="true" -``` - - - - - - - -```bash -pcs resource promotable ms_mysql \ - master-node-max="1" \ - clone_max="2" \ - globally-unique="false" \ - clone-node-max="1" \ - notify="true" -``` - -VIP Address of database servers - -```bash -pcs resource create vip_mysql \ - ocf:heartbeat:IPaddr2 \ - ip="@VIP_SQL_IPADDR@" \ - nic="@VIP_SQL_IFNAME@" \ - cidr_netmask="@VIP_SQL_CIDR_NETMASK@" \ - broadcast="@VIP_SQL_BROADCAST_IPADDR@" \ - flush_routes="true" \ - meta target-role="stopped" \ - op start interval="0s" timeout="20s" \ - stop interval="0s" timeout="20s" \ - monitor interval="10s" timeout="20s" -``` - - - - - - -#### PHP resource - -```bash -pcs resource create "php" \ - systemd:php-fpm \ - meta target-role="started" \ - op start interval="0s" timeout="30s" \ - stop interval="0s" timeout="30s" \ - monitor interval="5s" timeout="30s" \ - clone -``` - -#### RRD broker resource - -```bash -pcs resource create "cbd_rrd" \ - systemd:cbd \ - meta target-role="started" \ - op start interval="0s" timeout="90s" \ - stop interval="0s" timeout="90s" \ - monitor interval="20s" timeout="30s" \ - clone -``` - -#### Recreating the *centreon* resource group - -```bash -bash centreon_pcs_command.sh -``` - -#### Recreating the constraint - - - - - - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint order stop centreon then demote ms_mysql-clone -``` - - - - - - -In order to bind the primary database role to the Virtual IP, define a mutual constraint: - - - - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - - - -Then recreate the constraint that prevents Centreon processes from running on database nodes and vice-versa: - - - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - - - - - -## Resuming cluster resource management - -Now that the update is finished, the resources can be managed again: - -```bash -pcs property set maintenance-mode=false -pcs resource cleanup -``` - -## Check the health of the cluster - -You can monitor the cluster's resources in real time using the `crm_mon -fr` command: -> **INFO:** The `-fr` option allows you to display all resources even if they are disabled. - - - - -```text -Stack: corosync -Current DC: @CENTRAL_SLAVE_NAME@ (version 1.1.20-5.el7_7.2-3c4c782f70) - partition with quorum -Last updated: Thu Feb 20 13:14:17 2020 -Last change: Thu Feb 20 09:25:54 2020 by root via crm_attribute on @CENTRAL_MASTER_NAME@ - -2 nodes configured -14 resources configured - -Online: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @CENTRAL_MASTER_NAME@ ] - Slaves: [ @CENTRAL_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -``` - - - - -```text -[...] -4 nodes configured -21 resources configured - -Online: [@CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @DATABASE_MASTER_NAME@ ] - Slaves: [ @DATABASE_SLAVE_NAME@ ] - Stopped: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -vip_mysql (ocf::heartbeat:IPaddr2): Started @DATABASE_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ -``` - - - - -### Disabled resources - -When you do a `crm_mon -fr` and you have a resource that is disabled: - -```text -... - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @DATABASE_MASTER_NAME@ ] - Slaves: [ @DATABASE_SLAVE_NAME@ ] - Stopped: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -vip_mysql (ocf::heartbeat:IPaddr2): Stopped (disabled) -... -``` - -You must enable the resource with the following command: - -```bash -pcs resource enable @RESSOURCE_NAME@ -``` - -In our case: - -```bash -pcs resource enable vip_mysql -``` - -## Verifying platform stability - -You should now check that everything works fine: - -* Access to the web UI menus. -* Poller configuration generation + reload and restart method. -* Schedule immediate checks (Central + Pollers) , acknowledgements, downtime, etc. -* Move resources or reboot the active server and check again that everything is fine. diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-10.md deleted file mode 100644 index cd2f0e777072..000000000000 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-21-10.md +++ /dev/null @@ -1,567 +0,0 @@ ---- -id: upgrade-centreon-ha-from-21-10 -title: Upgrade Centreon HA from Centreon 21.10 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -This chapter describes how to upgrade your Centreon HA platform from version 21.10 to version 25.10. - -> If you were considering migrating your platform to another OS too, contact your Centreon sales representative to discuss this. - -## Prerequisites - -### Suspend cluster resources management - -In order to avoid a failover of the cluster during the update, it is necessary to unmanage all Centreon resources, as well as MariaDB. - -```bash -pcs property set maintenance-mode=true -``` - -### 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](../../security/key-rotation.md#existing-installation), to remove the old key and install the new one. - -### Update the centreon_central_sync script (MBI only) - -This step is only necessary if you use [MBI](../../reporting/introduction.md). Update the script `/usr/share/centreon-ha/bin/centreon_central_sync` at the following lines: - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua"], -``` - -For MBI reports to still be downloadable later on, the lines must be updated like this: - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua", "/var/lib/centreon/centreon-bi-server/archives"], -``` - -## Upgrade process - -To perform the upgrade: - -> For the **active central node** and **active database node if needed** please [follow the official documentation](../../upgrade/upgrade-from-21-10.md) **until the "Upgrade MariaDB" step included**. - -> For the **passive central node** and **passive database node if needed**, please [follow the official documentation](../../upgrade/upgrade-from-21-10.md) **until the "Update your customized Apache configuration" step included**. Then, skip to the "Upgrade MariaDB" step and follow its instructions. **Do not follow "Finalizing the upgrade" and "Post-upgrade actions"**. - -Then on the two central nodes, restore the file `/etc/centreon-ha/centreon_central_sync.pm`: - -```shell -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -On the passive central node, move the "install" directory to avoid getting the "upgrade" screen in the interface in the event of a further exchange of roles. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - -### Removing cron jobs - -The RPM upgrade puts cron jobs back in place on the central and database servers. Remove them to avoid concurrent executions on central and database nodes: - -```bash -rm -rf /etc/cron.d/centreon -rm -rf /etc/cron.d/centstorage -rm -f /etc/cron.d/centreon-ha-mysql -``` - -As you have deleted the **centreon-ha-mysql** cron, check that the following line appears in the **server** section of the **/etc/my.cnf.d/server.cnf** file: - -```shell -expire_logs_days=7 -``` - -If the line is not there, add it, then restart the **ms_mysql** resource: - -```shell -pcs resource restart ms_mysql -``` - -### Reset the permissions for centreon_central_sync resource - -The RPM upgrade puts the permissions back in place on the two **central servers**. Change them using these commands: - -```bash -chmod 775 /var/log/centreon-engine/ -mkdir /var/log/centreon-engine/archives -chown centreon-engine: /var/log/centreon-engine/archives -chmod 775 /var/log/centreon-engine/archives/ -find /var/log/centreon-engine/ -type f -exec chmod 664 {} \; -find /usr/share/centreon/www/img/media -type d -exec chmod 775 {} \; -find /usr/share/centreon/www/img/media -type f \( ! -iname ".keep" ! -iname ".htaccess" \) -exec chmod 664 {} \; -``` - -## Cluster upgrade - -From Centreon 22.04, MariaDB Replication is based on [GTID](https://mariadb.com/kb/en/gtid/). -It is necessary to destroy the cluster completely and then reconfigure it with the latest version of Centreon and MariaDB replication mechanisms. - -### Maintenance mode and backup - -Perform a backup of the cluster using: - - - - -```bash -pcs config backup centreon_cluster -pcs resource config --output-format=cmd | sed -e :a -e '/\\$/N; s/\\\n//; ta' | sed 's/-f tmp-cib.xml//' | egrep "create|group" | egrep -v "(mysql|php|cbd_rrd)" > centreon_pcs_command.sh -``` - - - - -Check that the file `centreon_cluster.tar.bz2` exists before continuing this procedure. - -```bash -ls -l centreon_cluster.tar.bz2 -``` - -You should have a result like this: - -```text --rw------- 1 root root 2777 May 3 17:49 centreon_cluster.tar.bz2 -``` - -Then check the file centreon_pcs_command.sh. The export command may display some warning lines, but this is not blocking. - -```bash -cat centreon_pcs_command.sh -``` - -The content should looks like this: - - - - -```text -pcs resource create --no-default-ops --force -- vip ocf:heartbeat:IPaddr2 broadcast=@VIP_BROADCAST_IPADDR@ cidr_netmask=@VIP_CIDR_NETMASK@ flush_routes=true ip=@VIP_IPADDR@ nic=@VIP_IFNAME@ op monitor interval=10s id=vip-monitor-interval-10s timeout=20s start interval=0s id=vip-start-interval-0s timeout=20s stop interval=0s id=vip-stop-interval-0s timeout=20s meta target-role=started; -pcs resource create --no-default-ops --force -- http systemd:httpd op monitor interval=5s id=http-monitor-interval-5s timeout=20s start interval=0s id=http-start-interval-0s timeout=40s stop interval=0s id=http-stop-interval-0s timeout=40s meta target-role=started; -pcs resource create --no-default-ops --force -- gorgone systemd:gorgoned op monitor interval=5s id=gorgone-monitor-interval-5s timeout=20s start interval=0s id=gorgone-start-interval-0s timeout=90s stop interval=0s id=gorgone-stop-interval-0s timeout=90s meta target-role=started; -pcs resource create --no-default-ops --force -- centreon_central_sync systemd:centreon-central-sync op monitor interval=5s id=centreon_central_sync-monitor-interval-5s timeout=20s start interval=0s id=centreon_central_sync-start-interval-0s timeout=90s stop interval=0s id=centreon_central_sync-stop-interval-0s timeout=90s meta target-role=started; -pcs resource create --no-default-ops --force -- cbd_central_broker systemd:cbd-sql op monitor interval=5s id=cbd_central_broker-monitor-interval-5s timeout=30s start interval=0s id=cbd_central_broker-start-interval-0s timeout=90s stop interval=0s id=cbd_central_broker-stop-interval-0s timeout=90s meta target-role=started; -pcs resource create --no-default-ops --force -- centengine systemd:centengine op monitor interval=5s id=centengine-monitor-interval-5s timeout=30s start interval=0s id=centengine-start-interval-0s timeout=90s stop interval=0s id=centengine-stop-interval-0s timeout=90s meta multiple-active=stop_start target-role=started; -pcs resource create --no-default-ops --force -- centreontrapd systemd:centreontrapd op monitor interval=5s id=centreontrapd-monitor-interval-5s timeout=20s start interval=0s id=centreontrapd-start-interval-0s timeout=30s stop interval=0s id=centreontrapd-stop-interval-0s timeout=30s meta target-role=started; -pcs resource create --no-default-ops --force -- snmptrapd systemd:snmptrapd op monitor interval=5s id=snmptrapd-monitor-interval-5s timeout=20s start interval=0s id=snmptrapd-start-interval-0s timeout=30s stop interval=0s id=snmptrapd-stop-interval-0s timeout=30s meta target-role=started; -pcs resource group add centreon vip http gorgone centreon_central_sync cbd_central_broker centengine centreontrapd snmptrapd; -``` - - - - -This file will be necessary to recreate all the resources of your cluster. - -### Delete the resources - -These commands should run only on the active central node: - - - - -```bash -pcs resource delete ms_mysql --force -pcs resource delete cbd_rrd --force -pcs resource delete php --force -pcs resource delete centreon --force -``` - - - - -```bash -pcs resource delete ms_mysql --force -pcs resource delete vip_mysql --force -pcs resource delete cbd_rrd --force -pcs resource delete php --force -pcs resource delete centreon --force -``` - - - - -### Reconfigure MariaDB - -It is necessary to modify the mysql configuration by editing the file `/etc/my.cnf.d/server.cnf`: - -> On the 2 Central servers in HA 2 nodes -> On the 2 Database servers in HA 4 nodes. - -```shell -[server] -... -skip-slave-start -log-slave-updates -gtid_strict_mode=ON -expire_logs_days=7 -ignore-db-dir=lost+found -... -``` - -### Launch GTID replication - -Run this command **on the secondary database node**: - -```bash -mysqladmin -p shutdown -``` - -It is important to make sure that MariaDB is completely shut down. Run this command and check that it returns no output: - -```bash -ps -ef | grep mariadb[d] -``` - -Once the service is stopped **on the secondary database node**, run the synchronization script **from the primary database node**: - -```bash -mysqladmin -p shutdown -systemctl restart mariadb -/usr/share/centreon-ha/bin/mysql-sync-bigdb.sh -``` - -This script's output is very verbose. To make sure it went well, focus on the last lines of its output, checking that it looks like this: - -```text -Umount and Delete LVM snapshot - Logical volume "dbbackupdatadir" successfully removed -Start MySQL Slave -Start Replication -Id User Host db Command Time State Info Progress -[variable number of lines] -``` - -The important thing to check is that `Start MySQL Slave` and `Start Replication` are present and are not followed by any errors. - -In addition, the output of this command must display only `OK` results: - -```bash -/usr/share/centreon-ha/bin/mysql-check-status.sh -``` - -The expected output is: - -```text -Connection MASTER Status '@CENTRAL_MASTER_NAME@' [OK] -Connection SLAVE Status '@CENTRAL_SLAVE_NAME@' [OK] -Slave Thread Status [OK] -Position Status [OK] -``` - -### Restart Centreon process - -Then to restart all the processes on the **active central node**: - -```bash -systemctl restart cbd-sql cbd gorgoned centengine centreontrapd -``` - -And on the **passive central node**: - -```bash -systemctl restart cbd -``` - -### Clean broker memory files - -> **WARNING:** perform this command only on the **passive central node**. - -Before resuming cluster resource management, to avoid broker issues, clean up all the *.memory.*, *.unprocessed.* or *.queue.* files: - -```bash -rm -rf /var/lib/centreon-broker/central-broker-master.memory* -rm -rf /var/lib/centreon-broker/central-broker-master.queue* -rm -rf /var/lib/centreon-broker/central-broker-master.unprocessed* -``` - -### Recreate the cluster resources - -To be run **only on one central node**: - -> **WARNING:** the syntax of the following command depends on the Linux distribution you are using. - -> You can find the @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ @MARIADB_REPL_USER@ @MARIADB_REPL_USER@ variables in `/etc/centreon-ha/mysql-resources.sh` - - - - -```bash -pcs resource create "ms_mysql" \ - ocf:heartbeat:mariadb-centreon \ - config="/etc/my.cnf.d/server.cnf" \ - pid="/var/lib/mysql/mysql.pid" \ - datadir="/var/lib/mysql" \ - socket="/var/lib/mysql/mysql.sock" \ - binary="/usr/bin/mysqld_safe" \ - node_list="@CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@" \ - replication_user="@MARIADB_REPL_USER@" \ - replication_passwd='@MARIADB_REPL_PASSWD@' \ - test_user="@MARIADB_REPL_USER@" \ - test_passwd="@MARIADB_REPL_PASSWD@" \ - test_table='centreon.host' -``` - - - - -> **WARNING:** the syntax of the following command depends on the Linux distribution you are using. - - - - - - -```bash -pcs resource promotable ms_mysql \ - master-node-max="1" \ - clone_max="2" \ - globally-unique="false" \ - clone-node-max="1" \ - notify="true" -``` - - - - - - - - -```bash -pcs resource promotable ms_mysql \ - master-node-max="1" \ - clone_max="2" \ - globally-unique="false" \ - clone-node-max="1" \ - notify="true" -``` - -VIP Address of database servers - -```bash -pcs resource create vip_mysql \ - ocf:heartbeat:IPaddr2 \ - ip="@VIP_SQL_IPADDR@" \ - nic="@VIP_SQL_IFNAME@" \ - cidr_netmask="@VIP_SQL_CIDR_NETMASK@" \ - broadcast="@VIP_SQL_BROADCAST_IPADDR@" \ - flush_routes="true" \ - meta target-role="stopped" \ - op start interval="0s" timeout="20s" \ - stop interval="0s" timeout="20s" \ - monitor interval="10s" timeout="20s" -``` - - - - - - -#### PHP resource - -```bash -pcs resource create "php" \ - systemd:php-fpm \ - meta target-role="started" \ - op start interval="0s" timeout="30s" \ - stop interval="0s" timeout="30s" \ - monitor interval="5s" timeout="30s" \ - clone -``` - -#### RRD broker resource - -```bash -pcs resource create "cbd_rrd" \ - systemd:cbd \ - meta target-role="started" \ - op start interval="0s" timeout="90s" \ - stop interval="0s" timeout="90s" \ - monitor interval="20s" timeout="30s" \ - clone -``` - -#### Recreating the *centreon* resource group - -```bash -bash centreon_pcs_command.sh -``` - -#### Recreating the constraint - - - - - - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - - - - - -In order to bind the primary database role to the Virtual IP, define a mutual constraint: - - - - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - - - -Then recreate the constraint that prevents Centreon processes from running on database nodes and vice-versa: - - - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - - - - - -## Resuming cluster resource management - -Now that the update is finished, the resources can be managed again: - -```bash -pcs property set maintenance-mode=false -pcs resource cleanup -``` - -## Check the health of the cluster - -You can monitor the cluster's resources in real time using the `crm_mon -fr` command: -> **INFO:** The `-fr` option allows you to display all resources even if they are disabled. - - - - -```text -Stack: corosync -Current DC: @CENTRAL_SLAVE_NAME@ (version 1.1.20-5.el7_7.2-3c4c782f70) - partition with quorum -Last updated: Thu Feb 20 13:14:17 2020 -Last change: Thu Feb 20 09:25:54 2020 by root via crm_attribute on @CENTRAL_MASTER_NAME@ - -2 nodes configured -14 resources configured - -Online: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @CENTRAL_MASTER_NAME@ ] - Slaves: [ @CENTRAL_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -``` - - - - -```text -[...] -4 nodes configured -21 resources configured - -Online: [@CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @DATABASE_MASTER_NAME@ ] - Slaves: [ @DATABASE_SLAVE_NAME@ ] - Stopped: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -vip_mysql (ocf::heartbeat:IPaddr2): Started @DATABASE_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ -``` - - - - -### Disabled resources - -When you do a `crm_mon -fr` and you have a resource that is disabled: - -```text -... - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @DATABASE_MASTER_NAME@ ] - Slaves: [ @DATABASE_SLAVE_NAME@ ] - Stopped: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -vip_mysql (ocf::heartbeat:IPaddr2): Stopped (disabled) -... -``` - -You must enable the resource with the following command: - -```bash -pcs resource enable @RESSOURCE_NAME@ -``` - -In our case: - -```bash -pcs resource enable vip_mysql -``` - -## Verifying platform stability - -You should now check that everything works fine: - -* Access to the web UI menus. -* Poller configuration generation + reload and restart method. -* Schedule immediate checks (Central + Pollers) , acknowledgements, downtime, etc. -* Move resources or reboot the active server and check again that everything is fine. diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-10.md deleted file mode 100644 index 5b5bcae5d88f..000000000000 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-10.md +++ /dev/null @@ -1,398 +0,0 @@ ---- -id: upgrade-centreon-ha-from-22-10 -title: Upgrade Centreon HA from Centreon 22.10 ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -This chapter describes how to upgrade your Centreon HA platform from version 22.10 to version 25.10. - -> If you were using Debian 11, you cannot upgrade your platform directly to version 25.10. You need to [migrate your platform to Debian 12](migrate/migrate-from-debian-to-debian.md) first, then reinstall HA. Contact your Centreon sales representative to discuss any migration with HA. - -## Prerequisites - -### Suspend cluster resources management - -In order to avoid a failover of the cluster during the update, it is necessary to unmanage all Centreon resources, as well as MariaDB. - -```bash -pcs property set maintenance-mode=true -``` - -### 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](../../security/key-rotation.md#existing-installation), to remove the old key and install the new one. - -### Update the centreon_central_sync script (MBI only) - -This step is only necessary if you use [MBI](../../reporting/introduction.md). Update the script `/usr/share/centreon-ha/bin/centreon_central_sync` at the following lines: - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua"], -``` - -For MBI reports to still be downloadable later on, the lines must be updated like this: - -```shell -rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", - "/etc/centreon/license.d", "/usr/share/centreon-broker/lua", "/var/lib/centreon/centreon-bi-server/archives"], -``` - -## Upgrade process - -Before process the upgrade, stop Centreon-Broker-SQL on the **central master node**: - -```bash -systemctl stop cbd-sql -``` - -Now, to perform the upgrade: - -> For the **active central node** and **active database node if needed** please [follow the official documentation](../../upgrade/upgrade-from-22-10.md) **until the "Upgrade MariaDB" step included**. - -> For the **passive central node** and **passive database node if needed**, please [follow the official documentation](../../upgrade/upgrade-from-22-10.md) **until the "Update your customized Apache configuration" step included**. Then, skip to the "Upgrade MariaDB" step and follow its instructions. **Do not follow "Finalizing the upgrade" and "Post-upgrade actions"**. - - - - -Then on the **two central nodes**, restore the file `/etc/centreon-ha/centreon_central_sync.pm`: - -```shell -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -On the **passive central node**, move the "install" directory to avoid getting the "upgrade" screen in the interface in the event of a further exchange of roles. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - - - - -### Removing cron jobs - -The RPM upgrade puts cron jobs back in place on the central and databases servers. Remove them to avoid concurrent executions on central and database nodes: - -```bash -rm -f /etc/cron.d/centreon -rm -f /etc/cron.d/centstorage -rm -f /etc/cron.d/centreon-ha-mysql -``` - -and restart the cron daemon: - - - - -```bash -systemctl restart crond -``` - - - - -As you have deleted the **centreon-ha-mysql** cron, check that the following line appears in the **server** section of the **/etc/my.cnf.d/server.cnf** file, it is normally already in place since 22.04 and GTID replication: - -```shell -expire_logs_days=7 -``` - -### Reset the permissions for centreon_central_sync resource - -The RPM upgrade puts the permissions back in place on the two **central servers**. Change them using these commands: - -```bash -chmod 775 /var/log/centreon-engine/ -mkdir /var/log/centreon-engine/archives -chown centreon-engine: /var/log/centreon-engine/archives -chmod 775 /var/log/centreon-engine/archives/ -find /var/log/centreon-engine/ -type f -exec chmod 664 {} \; -find /usr/share/centreon/www/img/media -type d -exec chmod 775 {} \; -find /usr/share/centreon/www/img/media -type f \( ! -iname ".keep" ! -iname ".htaccess" \) -exec chmod 664 {} \; -``` - -## Cluster ugprade - -Since Centreon 22.04, The mariaDB Replication is now based on [GTID](https://mariadb.com/kb/en/gtid/). - -However, some changes must always be done. - -### Backup the configuration - -Perform a backup of the cluster on central master node using: - -```bash -pcs config backup centreon_cluster -cibadmin -Q > export_cluster.xml -``` - -Check the file `centreon_cluster.tar.bz2` exist before continuing this procedure. - -```bash -ls -l centreon_cluster.tar.bz2 -``` - -You should have a result like this: - -```text --rw------- 1 root root 2777 May 3 17:49 centreon_cluster.tar.bz2 -``` - -### Modifying order of resources on centreon group - -To optimize managment of resources and to avoid restart cbd-sql when we just want to restart gorgone, we must change there order in the group. - -```bash -pcs resource group remove centreon cbd_central_broker -pcs resource group add centreon cbd_central_broker --before gorgone -``` - -### Clean broker memory files - -> **WARNING:** perform this command only the **passive central node**. - -Before resuming the cluster resources management, to avoid broker issues, cleanup all the *.memory.*, *.unprocessed.* or *.queue.* files: - -```bash -rm -f /var/lib/centreon-broker/central-broker-master.memory* -rm -f /var/lib/centreon-broker/central-broker-master.queue* -rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* -``` - -#### Recreating the constraint - - - - - - -First extract all contraint IDs: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -You should have a similar result: - -```text -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-centreon-INFINITY -colocation-centreon-ms_mysql-clone-INFINITY -``` - -and delete **all** constraints, **adapt IDs with your own** - -```bash -pcs constraint delete order-centreon-ms_mysql-clone-mandatory -pcs constraint delete colocation-ms_mysql-clone-centreon-INFINITY -pcs constraint delete colocation-centreon-ms_mysql-clone-INFINITY -``` - -Verify if all constraint are well deleted: - -```bash -pcs constraint -``` - -You should have a result like this: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -If it's OK, then recreate only needed constraints - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - - - - - - - -First extract all contraint IDs: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -You should have a similar result depending of your host names: - -```text -location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -location-centreon-cc-ha-bdd2-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web1-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web2-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd2-2210-alma8--INFINITY -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-vip_mysql-INFINITY -colocation-centreon-vip-INFINITY -``` - -and delete **all** constraints, **adapt IDs with your own** - -```bash -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -pcs constraint delete location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -... -``` - -Verify if all constraint are well deleted: - -```bash -pcs constraint -``` - -You should have a result like this: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -If it's OK, then recreate only needed constraints. - -In order to glue the Primary Database role with the Virtual IP, define a mutual Constraint: - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - - - -Then recreate the Constraint that prevent Centreon Processes to run on Database nodes and vice-et-versa: - - - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - - - - - -## Resuming the cluster resources management - -Now that the update is finished, the resources can be managed again: - -```bash -pcs property set maintenance-mode=false -pcs resource cleanup -``` - -## Check cluster's health - -You can monitor the cluster's resources in real time using the `crm_mon -fr` command: -> **INFO:** The `-fr` option allows you to display all resources even if they are disable. - - - - -```text -Stack: corosync -Current DC: @CENTRAL_SLAVE_NAME@ (version 1.1.20-5.el7_7.2-3c4c782f70) - partition with quorum -Last updated: Thu Feb 20 13:14:17 2020 -Last change: Thu Feb 20 09:25:54 2020 by root via crm_attribute on @CENTRAL_MASTER_NAME@ - -2 nodes configured -14 resources configured - -Online: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @CENTRAL_MASTER_NAME@ ] - Slaves: [ @CENTRAL_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -``` - - - - -```text -[...] -4 nodes configured -21 resources configured - -Online: [@CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@] - -Active resources: - - Master/Slave Set: ms_mysql-master [ms_mysql] - Masters: [ @DATABASE_MASTER_NAME@ ] - Slaves: [ @DATABASE_SLAVE_NAME@ ] - Stopped: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] -vip_mysql (ocf::heartbeat:IPaddr2): Started @DATABASE_MASTER_NAME@ - Clone Set: php-clone [php] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Clone Set: cbd_rrd-clone [cbd_rrd] - Started: [ @CENTRAL_MASTER_NAME@ @CENTRAL_SLAVE_NAME@ ] - Stopped: [ @DATABASE_MASTER_NAME@ @DATABASE_SLAVE_NAME@ ] - Resource Group: centreon - vip (ocf::heartbeat:IPaddr2): Started @CENTRAL_MASTER_NAME@ - http (systemd:httpd24-httpd): Started @CENTRAL_MASTER_NAME@ - gorgone (systemd:gorgoned): Started @CENTRAL_MASTER_NAME@ - centreon_central_sync (systemd:centreon-central-sync): Started @CENTRAL_MASTER_NAME@ - cbd_central_broker (systemd:cbd-sql): Started @CENTRAL_MASTER_NAME@ - centengine (systemd:centengine): Started @CENTRAL_MASTER_NAME@ - centreontrapd (systemd:centreontrapd): Started @CENTRAL_MASTER_NAME@ - snmptrapd (systemd:snmptrapd): Started @CENTRAL_MASTER_NAME@ -``` - - - - -## Verifying the platform stability - -You should now check that eveything works fine: - -* Access to the web UI menus. -* Poller configuration generation + reload and restart method. -* Schedule immediate checks (Central + Pollers) , acknowledgements, downtimes, etc. -* Move resources or reboot active server and check again that everything is fine. diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-04.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md similarity index 74% rename from versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-04.md rename to versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md index f23c140eaece..ad5322277277 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-22-04.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md @@ -1,13 +1,13 @@ --- -id: upgrade-centreon-ha-from-22-04 -title: Upgrade Centreon HA from Centreon 22.04 +id: upgrade-centreon-ha-from-25-10 +title: Upgrade Centreon HA from Centreon 25.10 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This chapter describes how to upgrade your Centreon HA platform from version 22.04 to version 25.10. +This chapter describes how to upgrade your Centreon HA platform from version 25.10 to version 26.10. -> If you were using Debian 11, you cannot upgrade your platform directly to version 25.10. You need to [migrate your platform to Debian 12](migrate/migrate-from-debian-to-debian.md) first, then reinstall HA. Contact your Centreon sales representative to discuss any migration with HA. +> If you were considering migrating your platform to another OS too, contact your Centreon sales representative to discuss this. ## Prerequisites @@ -57,9 +57,9 @@ systemctl stop cbd-sql Now, to perform the upgrade: -> For the **active central node** and **active database node if needed** please [follow the official documentation](../../upgrade/upgrade-from-22-04.md) **until the "Upgrade MariaDB" step included**. +> For the **active central node** and **active database node if needed** please [follow the official documentation](../../upgrade/upgrade-from-24-10.md) **until the "Upgrade MariaDB" step included**. -> For the **passive central node** and **passive database node if needed**, please [follow the official documentation](../../upgrade/upgrade-from-22-04.md) **until the "Update your customized Apache configuration" step included**. Then, skip to the "Upgrade MariaDB" step and follow its instructions. **Do not follow "Finalizing the upgrade" and "Post-upgrade actions"**. +> For the **passive central node** and **passive database node if needed**, please [follow the official documentation](../../upgrade/upgrade-from-24-10.md) **until the "Update your customized Apache configuration" step included**. Then, skip to the "Upgrade MariaDB" step and follow its instructions. **Do not follow "Finalizing the upgrade" and "Post-upgrade actions"**. @@ -77,6 +77,22 @@ mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`da sudo -u apache /usr/share/centreon/bin/console cache:clear ``` + + + +Then on the **two central nodes**, restore the file `/etc/centreon-ha/centreon_central_sync.pm`: + +```shell +mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm +``` + +On the **passive central node**, move the "install" directory to avoid getting the "upgrade" screen in the interface in the event of a further exchange of roles. + +```bash +mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` +sudo -u apache /usr/share/centreon/bin/console cache:clear +``` + @@ -99,6 +115,13 @@ and restart the cron daemon: systemctl restart crond ``` + + + +```bash +systemctl restart crond +``` + @@ -128,9 +151,6 @@ Since Centreon 22.04, The mariaDB Replication is now based on [GTID](https://mar However, some changes must always be done. - - - ### Backup the configuration Perform a backup of the cluster on central master node using: @@ -161,9 +181,6 @@ pcs resource group remove centreon cbd_central_broker pcs resource group add centreon cbd_central_broker --before gorgone ``` - - - ### Clean broker memory files > **WARNING:** perform this command only the **passive central node**. @@ -227,6 +244,54 @@ pcs constraint colocation add master "ms_mysql-clone" with "centreon" pcs constraint colocation add master "centreon" with "ms_mysql-clone" ``` + + + +First extract all contraint IDs: + +```bash +pcs constraint config --full +``` + +You should have a similar result: + +```text +Colocation Constraints: + Promoted resource 'centreon' with Started resource 'ms_mysql-clone' (id: colocation-centreon-ms_mysql-clone-INFINITY) + score=INFINITY + Promoted resource 'ms_mysql-clone' with Started resource 'centreon' (id: colocation-ms_mysql-clone-centreon-INFINITY) + score=INFINITY +``` + +and delete **all** constraints, **adapt IDs with your own** + +```bash +pcs constraint delete colocation-centreon-ms_mysql-clone-INFINITY +pcs constraint delete colocation-ms_mysql-clone-centreon-INFINITY +``` + +Verify if all constraint are well deleted: + +```bash +pcs constraint +``` + +You should have a result like this: + +```text +Location Constraints: +Ordering Constraints: +Colocation Constraints: +Ticket Constraints: +``` + +If it's OK, then recreate only needed constraints + +```bash +pcs constraint colocation add master "ms_mysql-clone" with "centreon" +pcs constraint colocation add master "centreon" with "ms_mysql-clone" +``` + @@ -289,6 +354,64 @@ pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" ``` + + + +First extract all contraint IDs: + +```bash +pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' +``` + +You should have a similar result depending of your host names: + +```text +location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY +location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY +location-centreon-cc-ha-bdd1-2210-alma8--INFINITY +location-centreon-cc-ha-bdd2-2210-alma8--INFINITY +location-ms_mysql-clone-cc-ha-web1-2210-alma8--INFINITY +location-ms_mysql-clone-cc-ha-web2-2210-alma8--INFINITY +location-php-clone-cc-ha-bdd1-2210-alma8--INFINITY +location-php-clone-cc-ha-bdd2-2210-alma8--INFINITY +order-centreon-ms_mysql-clone-mandatory +colocation-ms_mysql-clone-vip_mysql-INFINITY +colocation-centreon-vip-INFINITY +``` + +and delete **all** constraints, **adapt IDs with your own** + +```bash +pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY +pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY +pcs constraint delete location-centreon-cc-ha-bdd1-2210-alma8--INFINITY +... +``` + +Verify if all constraint are well deleted: + +```bash +pcs constraint +``` + +You should have a result like this: + +```text +Location Constraints: +Ordering Constraints: +Colocation Constraints: +Ticket Constraints: +``` + +If it's OK, then recreate only needed constraints. + +In order to glue the Primary Database role with the Virtual IP, define a mutual Constraint: + +```bash +pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" +pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" +``` + @@ -304,6 +427,16 @@ pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DA pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY ``` + + + +```bash +pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY +pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY +pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY +pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY +``` + diff --git a/versioned_docs/version-26.10/upgrade/upgrade-mysql.md b/versioned_docs/version-26.10/upgrade/upgrade-mysql.md index f3ea2b7ae32f..b1f63a0f7df6 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-mysql.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-mysql.md @@ -5,7 +5,7 @@ title: Upgrading MySQL import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -If you were using Centreon 24.04 or 24.10 with MySQL, be aware that support for MySQL 8.0 ends at the end of April 2026. Make sure your Centreon always uses [a supported version of MySQL](#versions-of-mysql-compatible-with-centreon-2610). +If you were using Centreon 24.04 or 24.10 with MySQL, be aware that support for MySQL 8.0 ended at the end of April 2026. Make sure your Centreon always uses [a supported version of MySQL](#versions-of-mysql-compatible-with-centreon-2610). You may have several MySQL databases in your architecture. The central server has a database, each remote server has a database, and the MBI and MAP modules each have a dedicated database. Within your architecture, all databases must have the same version of MySQL. diff --git a/versioned_sidebars/version-26.10-sidebars.json b/versioned_sidebars/version-26.10-sidebars.json index c1e5023610d0..e10eeae9ca1d 100644 --- a/versioned_sidebars/version-26.10-sidebars.json +++ b/versioned_sidebars/version-26.10-sidebars.json @@ -1622,6 +1622,10 @@ "type": "generated-index" }, "items": [ + { + "type": "doc", + "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-25-10" + }, { "type": "doc", "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-24-10" @@ -1637,22 +1641,6 @@ { "type": "doc", "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-23-04" - }, - { - "type": "doc", - "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-22-10" - }, - { - "type": "doc", - "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-22-04" - }, - { - "type": "doc", - "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-21-10" - }, - { - "type": "doc", - "id": "upgrade/centreon-ha/upgrade-centreon-ha-from-21-04" } ] } From b2aa7ad0a5be66abbf3d90e6e152ee6c1de9cfba Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 15:10:28 +0200 Subject: [PATCH 018/179] Workaround for zombie link --- .../version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md index ad5322277277..188e99cfdca3 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md @@ -29,7 +29,7 @@ Be sure that you have fully backed up your environment for the following servers ### 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](../../security/key-rotation.md#existing-installation), to remove the old key and install the new one. +When upgrading from an older version, you need to go through the [key rotation procedure](https://docs.centreon.com/docs/security/key-rotation/#existing-installation), to remove the old key and install the new one. ### Update the centreon_central_sync script (MBI only) From a6936d4f5eda82fc28ec27340f69d14ec043b566 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 15:22:13 +0200 Subject: [PATCH 019/179] Workaround for zombie link --- .../version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md index 188e99cfdca3..ce16890f14d9 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md @@ -33,7 +33,7 @@ When upgrading from an older version, you need to go through the [key rotation p ### Update the centreon_central_sync script (MBI only) -This step is only necessary if you use [MBI](../../reporting/introduction.md). Update the script `/usr/share/centreon-ha/bin/centreon_central_sync` at the following lines: +This step is only necessary if you use [MBI](https://docs.centreon.com/docs/reporting/introduction.md). Update the script `/usr/share/centreon-ha/bin/centreon_central_sync` at the following lines: ```shell rsync_dir => ["/etc/centreon-broker", "/etc/centreon-engine", "/var/log/centreon-engine", "/var/lib/centreon/centplugins", From c49e12d316b1c42f5d9bb531ff41c79fd8b76cc3 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 15:59:07 +0200 Subject: [PATCH 020/179] Workaround for zombie link --- .../version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md index ce16890f14d9..18a5f0bdf102 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md @@ -57,9 +57,9 @@ systemctl stop cbd-sql Now, to perform the upgrade: -> For the **active central node** and **active database node if needed** please [follow the official documentation](../../upgrade/upgrade-from-24-10.md) **until the "Upgrade MariaDB" step included**. +> For the **active central node** and **active database node if needed** please [follow the official documentation](https://docs.centreon.com/docs/upgrade/upgrade-from-25-10.md) **until the "Upgrade MariaDB" step included**. -> For the **passive central node** and **passive database node if needed**, please [follow the official documentation](../../upgrade/upgrade-from-24-10.md) **until the "Update your customized Apache configuration" step included**. Then, skip to the "Upgrade MariaDB" step and follow its instructions. **Do not follow "Finalizing the upgrade" and "Post-upgrade actions"**. +> For the **passive central node** and **passive database node if needed**, please [follow the official documentation](https://docs.centreon.com/docs/upgrade/upgrade-from-25-10.md) **until the "Update your customized Apache configuration" step included**. Then, skip to the "Upgrade MariaDB" step and follow its instructions. **Do not follow "Finalizing the upgrade" and "Post-upgrade actions"**. From 535e78faaba8659c15ba11a9dcbd10e5ba3c99ed Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 6 Jul 2026 16:42:06 +0200 Subject: [PATCH 021/179] Fix tag --- .../version-26.10/upgrade/upgrade-from-23-04.md | 8 ++++---- .../version-26.10/upgrade/upgrade-from-23-10.md | 8 ++++---- .../version-26.10/upgrade/upgrade-from-24-04.md | 8 ++++---- .../version-26.10/upgrade/upgrade-from-24-10.md | 8 ++++---- .../version-26.10/upgrade/upgrade-from-25-10.md | 8 ++++---- 5 files changed, 20 insertions(+), 20 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md index 89a9d167c5e2..33c70cfb196f 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md @@ -4,15 +4,15 @@ title: Upgrade from Centreon 23.04 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -import intro from './_intro.mdx' +import Intro from './_intro.mdx' - + > Version 23.04 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. -## What components need upgrading +## Which components need upgrading -| Component | version in 23.04 | Version in 26.10 | +| Component | Version in 23.04 | Version in 26.10 | | --- | --- | --- | | PHP | 8.1 | 8.4 | | Database | MariaDB 10.5.x | MariaDB 11.8 | diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md index c457aad62ade..f3aa4e2a39c1 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md @@ -4,15 +4,15 @@ title: Upgrade from Centreon 23.10 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -import intro from './_intro.mdx' +import Intro from './_intro.mdx' - + > Version 23.10 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. -## What components need upgrading +## Which components need upgrading -| Component | version in 23.10 | Version in 26.10 | +| Component | Version in 23.10 | Version in 26.10 | | --- | --- | --- | | PHP | 8.1 | 8.4 | | Database | MariaDB 10.5.x | MariaDB 11.8 | diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md index 79dca8d61493..40ccbef7ffca 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md @@ -4,15 +4,15 @@ title: Upgrade from Centreon 24.04 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -import intro from './_intro.mdx' +import Intro from './_intro.mdx' - + > Version 24.04 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. -## What components need upgrading +## Which components need upgrading -| Component | version in 24.04 | Version in 26.10 | +| Component | Version in 24.04 | Version in 26.10 | | --- | --- | --- | | PHP | 8.1 | 8.4 | | Database | MariaDB 10.11.x | MariaDB 11.8 | diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md index 4c5daa96b876..0afacdf2fb00 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md @@ -4,13 +4,13 @@ title: Upgrade from Centreon 24.10 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -import intro from './_intro.mdx' +import Intro from './_intro.mdx' - + -## What components need upgrading +## Which components need upgrading -| Component | version in 24.10 | Version in 26.10 | +| Component | Version in 24.10 | Version in 26.10 | | --- | --- | --- | | PHP | 8.2 | 8.4 | | Database |
  • MariaDB 10.11.x
  • MySQL 8.0 or 8.4
|
  • MariaDB 11.8
  • MySQL 8.4
| diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index 003a0a60498b..a493ac66e9c3 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -4,13 +4,13 @@ title: Upgrade from Centreon 25.10 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -import intro from './_intro.mdx' +import Intro from './_intro.mdx' - + -## What components need upgrading +## Which components need upgrading -| Component | version in 25.10 | Version in 26.10 | +| Component | Version in 25.10 | Version in 26.10 | | --- | --- | --- | | PHP | 8.2 | 8.4 | | Database |
  • MariaDB 10.11.x
  • MySQL 8.0 or 8.4
|
  • MariaDB 11.8
  • MySQL 8.4
| From 1ecc5cb02642fde862b501027214353ad1b19e15 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 7 Jul 2026 12:32:46 +0200 Subject: [PATCH 022/179] Update --- .../version-26.10/upgrade/_intro.mdx | 4 +- .../upgrade/upgrade-from-25-10.md | 65 ++++++++++++++----- 2 files changed, 51 insertions(+), 18 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/_intro.mdx b/versioned_docs/version-26.10/upgrade/_intro.mdx index e8e88e539fd5..8674a2bb7057 100644 --- a/versioned_docs/version-26.10/upgrade/_intro.mdx +++ b/versioned_docs/version-26.10/upgrade/_intro.mdx @@ -1,4 +1,6 @@ -This chapter describes how to upgrade your Centreon platform from version {props.type} to version 26.10. Upgrading is only possible if your current OS is RHEL/Oracle/AlmaLinux 9. Other OSs are no longer supported: use a [migration procedure](../migrate/introduction.md) to switch to a supported OS. If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. +This chapter describes how to upgrade your Centreon platform from version {props.type} to version 26.10. + +Upgrading is only possible if your current OS is RHEL/Oracle/AlmaLinux 9. Other OSs are no longer supported: use a [migration procedure](../migrate/introduction.md) to switch to a supported OS. If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. * 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. diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index a493ac66e9c3..cb94c64a7da9 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -105,6 +105,31 @@ systemctl stop cbd rm /var/lib/centreon-broker/* -f ``` +### Step 3: Upgrade PHP + +Centreon 26.10 uses PHP in version 8.4. + + + + +You need to change the PHP stream from version 8.2 to 8.4 by executing the following commands and answering **y** +to confirm: + +```shell +dnf module reset php +``` + +```shell +dnf module enable php:8.4 +``` + + + + +> Accept new GPG keys from the repositories as needed. + +Then, finish upgrading the Centreon solution. + 7. Clean the cache: @@ -131,7 +156,7 @@ dnf update centreon\* php-pecl-gnupg > Accept new GPG keys from the repositories as needed. -### Step 3: Update your customized Apache configuration +### Step 4: Update your customized Apache configuration This section only applies if you customized your Apache configuration. @@ -214,46 +239,46 @@ Add the following code to your Apache configuration file, in both the ` - + + -```shell -systemctl reload php-fpm httpd -``` + ```shell + systemctl reload php-fpm httpd + ``` - - + + -Then you need to finalize the upgrade process: +2. Finalize the upgrade process: 1. Log on to the Centreon web interface to continue the update process. Click **Next**: - ![image](../assets/upgrade/web_update_1.png) + ![image](../assets/upgrade/web_update_1.png) 2. Click **Next**: - ![image](../assets/upgrade/web_update_2.png) + ![image](../assets/upgrade/web_update_2.png) 3. The release notes describe the main changes. Click **Next**: - ![image](../assets/upgrade/web_update_3.png) + ![image](../assets/upgrade/web_update_3.png) 4. This process performs the various upgrades. Click **Next**: - ![image](../assets/upgrade/web_update_4.png) + ![image](../assets/upgrade/web_update_4.png) 5. Your Centreon server is now up to date. Click **Finish** to access the login page: - ![image](../assets/upgrade/web_update_5.png) + ![image](../assets/upgrade/web_update_5.png) 6. Deploy the central's configuration from the Centreon web UI by following [this procedure](../monitoring/monitoring-servers/deploying-a-configuration.md). @@ -337,7 +362,7 @@ usermod -a -G apache centreon-broker Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. -### Step 5: Post-upgrade actions +### Step 6: Post-upgrade actions 1. Upgrade extensions. From **Administration > Extensions > Manager**, upgrade all extensions, starting with the following: @@ -367,6 +392,12 @@ with the following: systemctl restart cbd centengine centreontrapd gorgoned ``` +### Step 7: Upgrade the database + +* If you were using MariaDB, [upgrade it](upgrade-mariadb.md) to version 11.8. +* If you were using MySQL 8.0, [upgrade it to version 8.4](upgrade-mysql.md). +* If you were already using MySQL 8.4, you don't need to do anything. + ## Upgrade the Remote Servers This procedure is the same as for upgrading a Centreon Central server with the addition of needing to retrieve the decryption key at the end. From 4c624adc6fc1ad6b4c1b343e72a1aec8f71f418d Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 7 Jul 2026 18:34:11 +0200 Subject: [PATCH 023/179] Single-source upgrade to 26.10 procedure --- .../upgrade/_upgrade-central.mdx | 354 ++++++++++++++ .../upgrade/_upgrade-pollers.mdx | 81 ++++ .../upgrade/_upgrade-remotes.mdx | 27 ++ .../upgrade/upgrade-from-25-10.md | 456 +----------------- .../version-26.10/upgrade/upgrade-mariadb.md | 8 +- 5 files changed, 472 insertions(+), 454 deletions(-) create mode 100644 versioned_docs/version-26.10/upgrade/_upgrade-central.mdx create mode 100644 versioned_docs/version-26.10/upgrade/_upgrade-pollers.mdx create mode 100644 versioned_docs/version-26.10/upgrade/_upgrade-remotes.mdx diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx new file mode 100644 index 000000000000..66d59730d185 --- /dev/null +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -0,0 +1,354 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import CodeBlock from '@theme/CodeBlock'; + +### Step 1: Install the new repositories + + + + +1. Update your Centreon {props.centreonVersion} to the latest minor version. + +2. Remove the repository files: + + + {`rm /etc/yum.repos.d/centreon-${props.centreonVersion}.repo\nrm /etc/yum.repos.d/centreon.repo`} + + +3. Install the new repository: + +```shell +dnf install -y dnf-plugins-core +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo +``` + + + + +4. If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). + +### Step 2: Start upgrading 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 {props.centreonVersion} repository: + + + + +{`rm /etc/yum.repos.d/centreon-business-${props.centreonVersion}.repo`} + + + + +3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. + +4. 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**). + +5. Stop the Centreon Broker process: + +```shell +systemctl stop cbd +``` + +6. Delete existing retention files: + +```shell +rm /var/lib/centreon-broker/* -f +``` + +### Step 3: Upgrade PHP + +Centreon 26.10 uses PHP in version 8.4. + + + + +You need to change the PHP stream from version {props.phpVersion} to 8.4 by executing the following commands and answering **y** +to confirm: + +```shell +dnf module reset php +``` + +```shell +dnf module enable php:8.4 +``` + + + + +> Accept new GPG keys from the repositories as needed. + +### Step 4: Finish upgrading the Centreon solution + +Then, finish upgrading the Centreon solution. + +1. Clean the cache: + + + + +```shell +dnf clean all --enablerepo=* +``` + + + + +2. Then upgrade all the components with the following command: + + + + +```shell +dnf update centreon\* php-pecl-gnupg +``` + + + + +> Accept new GPG keys from the repositories as needed. + +### Step 5: 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: + +```shell +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: + +```shell +apachectl configtest +``` + +The expected result is the following: + +```shell +Syntax OK +``` + +Restart the Apache and PHP processes to take the new configuration into account: + +```shell +systemctl restart php-fpm httpd +``` + +Then check its status: + +```shell +systemctl status httpd +``` + +If everything is ok, you should have: + +```shell +● 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 `` and `` elements: + +```shell + + AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json + +AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json +``` + +### Step 6: Finalize the upgrade + +1. Before starting the web upgrade process, upgrade the [Centreon BAM module](../service-mapping/upgrade.md) and reload the Apache server with the +following command: + + + + + ```shell + systemctl reload php-fpm httpd + ``` + + + + +2. Finalize the upgrade process: + + + + +1. Log on to the Centreon web interface to continue the update process. Click **Next**: + + ![image](../assets/upgrade/web_update_1.png) + +2. Click **Next**: + + ![image](../assets/upgrade/web_update_2.png) + +3. The release notes describe the main changes. Click **Next**: + + ![image](../assets/upgrade/web_update_3.png) + +4. This process performs the various upgrades. Click **Next**: + + ![image](../assets/upgrade/web_update_4.png) + +5. Your Centreon server is now up to date. Click **Finish** to access the login +page: + + ![image](../assets/upgrade/web_update_5.png) + +6. [Deploy the central's configuration from the Centreon web UI](../monitoring/monitoring-servers/deploying-a-configuration.md). + + + + +1. Log on to the central server through your terminal to continue the update process. + + > You need an authentication token to reach the API endpoint. Perform the following procedure to get a token. + + In our case, we have the configuration described below (you need to adapt the procedure to your configuration). + - address: 10.25.XX.XX + - port: 80 + - version: 26.10 + - login: Admin + - password: xxxxx + +2. Enter the following request: + + ```shell + curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ + --header 'Content-Type: application/json' \ + --header 'Accept: application/json' \ + --data '{ + "security": { + "credentials": { + "login": "Admin", + "password": "xxxxx" + } + } + }' + ``` + + This is how the result should look: + + ```shell + {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost","is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} + ``` + +3. Retrieve the token number to use it in the next request. + +4. Then enter this request: + + ```shell + curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ + --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ + --header 'Content-Type: application/json' \ + --data '{ + "components": [ + { + "name": "centreon-web" + } + ] + }' + ``` + +5. This request does not return any result. To check if the update has been successfully applied, read the version number displayed on the Centreon web interface login page. + + + + +Finally, restart Broker, Engine and Gorgone on the central server by running this command: + + ```shell + systemctl restart cbd centengine gorgoned + ``` + +Update the permissions on the centreon-broker configuration files. + + + + +```shell +usermod -a -G centreon-broker apache +usermod -a -G apache centreon-broker +``` + + + + +Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. + +### Step 7: 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: + ```shell + sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run + ``` + * To adapt the commands automatically, run: + ```shell + sudo -u apache php /usr/share/centreon/bin/console w:m:c + ``` + (You can also adapt them manually.) + +3. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). + +4. Restart the processes: + + ``` shell + systemctl restart cbd centengine centreontrapd gorgoned + ``` + +### Step 8: Upgrade the database + +
    +
  • If you were using MariaDB {props.oldMariadbVersion}, [upgrade it](upgrade-mariadb.md) to version 11.8.
    • + {props.showSecondPoint &&
  • If you were using MySQL 8.0, [upgrade it to version 8.4](upgrade-mysql.md).
    • } + {props.showThirdPoint &&
  • If you were already using MySQL 8.4, you don't need to do anything.
    • } +
\ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-pollers.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-pollers.mdx new file mode 100644 index 000000000000..449ef892cc40 --- /dev/null +++ b/versioned_docs/version-26.10/upgrade/_upgrade-pollers.mdx @@ -0,0 +1,81 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +## Upgrade the Pollers + +### Update the Centreon repository + +Run the following command: + + + + +```shell +dnf install -y dnf-plugins-core && \ +rm -f /etc/yum.repos.d/centreon* && \ +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo +``` + + + + +### Upgrade the Centreon solution + +Clean the cache: + + + + +```shell +dnf clean all --enablerepo=* +``` + + + + +Then upgrade all the components with the following command: + + + + +```shell +dnf update centreon\* +``` + +> If you installed MariaDB from their official repositories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. + + + + +> Accept new GPG keys from the repositories as needed. + +Restart **centreon**: + +```shell +systemctl restart centreon +``` +### Retrieving the decryption key + +Run the following script with the correct IP address to enable the poller to receive and process encrypted data. + +The IP address to use depends on the following conditions: +- When updating pollers linked directly to the central server, use the central server's IP. +- When updating pollers linked to a remote server, use the remote server's IP. However, in this instance, you must first confirm the remote server has the correct key by checking that the value of `app_secret` in the `/etc/centreon-engine/engine-context.json` file is the same as the central server's. If this is not the case, relaunch the script with the right IP to correct the .json file. + +```shell +/usr/share/centreon/bin/writeEngineSecrets.sh +``` + +Example: + +``` shell +/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password +``` + +> You must use **admin** as the **\**. + +Restart **centengine**: + +```shell +systemctl restart centengine +``` diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-remotes.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-remotes.mdx new file mode 100644 index 000000000000..fc510db2dd41 --- /dev/null +++ b/versioned_docs/version-26.10/upgrade/_upgrade-remotes.mdx @@ -0,0 +1,27 @@ +## Upgrade the Remote Servers + +This procedure is the same as for upgrading a Centreon Central server with the addition of needing to retrieve the decryption key at the end. + +### Retrieving the decryption key + +Run the following script with the central server IP address to enable the remote server to receive and process encrypted data: + +```shell +/usr/share/centreon/bin/writeEngineSecrets.sh +``` + +Example: + +``` shell +/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password +``` + +> You must use **admin** as the **\**. + +Restart **centengine**: + +```shell +systemctl restart centengine +``` + +> At the end of the update, the configuration should be deployed from the Central server. \ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index cb94c64a7da9..bd594529acd8 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -5,6 +5,8 @@ title: Upgrade from Centreon 25.10 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import Intro from './_intro.mdx' +import UpgradeCentral from './_upgrade-central.mdx' +import UpgradeRemotes from './_upgrade-remotes.mdx' @@ -47,460 +49,14 @@ Before upgrading your Centreon platform, make sure the following package reposit > If you installed MariaDB from their official repositories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. -### Step 1: Install the new repositories + - - - -1. Update your Centreon 25.10 to the latest minor version. - -2. Remove the repository files: - - ```shell - rm /etc/yum.repos.d/centreon-25.10.repo - rm /etc/yum.repos.d/centreon.repo - ``` - -3. Install the new repository: - -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -4. If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). - -### Step 2: 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 25.10 repository: - - - - -```shell -rm /etc/yum.repos.d/centreon-business-25.10.repo -``` - - - - -3. Install the 26.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. - -4. 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**). - -5. Stop the Centreon Broker process: - -```shell -systemctl stop cbd -``` - -6. Delete existing retention files: - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Step 3: Upgrade PHP - -Centreon 26.10 uses PHP in version 8.4. - - - - -You need to change the PHP stream from version 8.2 to 8.4 by executing the following commands and answering **y** -to confirm: - -```shell -dnf module reset php -``` - -```shell -dnf module enable php:8.4 -``` - - - - -> Accept new GPG keys from the repositories as needed. - -Then, finish upgrading the Centreon solution. - -7. Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -8. Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -> Accept new GPG keys from the repositories as needed. - -### Step 4: 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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 `` and `` elements: - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json -``` - -### Step 5: Finalize the upgrade - -1. Before starting the web upgrade process, upgrade the [Centreon BAM module](../service-mapping/upgrade.md) and reload the Apache server with the -following command: - - - - - ```shell - systemctl reload php-fpm httpd - ``` - - - - -2. Finalize the upgrade process: - - - - -1. Log on to the Centreon web interface to continue the update process. Click **Next**: - - ![image](../assets/upgrade/web_update_1.png) - -2. Click **Next**: - - ![image](../assets/upgrade/web_update_2.png) - -3. The release notes describe the main changes. Click **Next**: - - ![image](../assets/upgrade/web_update_3.png) - -4. This process performs the various upgrades. Click **Next**: - - ![image](../assets/upgrade/web_update_4.png) - -5. Your Centreon server is now up to date. Click **Finish** to access the login -page: - - ![image](../assets/upgrade/web_update_5.png) - -6. Deploy the central's configuration from the Centreon web UI by following [this -procedure](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -1. Log on to the central server through your terminal to continue the update process. - - > You need an authentication token to reach the API endpoint. Perform the following procedure to get a token. - - In our case, we have the configuration described below (you need to adapt the procedure to your configuration). - - address: 10.25.XX.XX - - port: 80 - - version: 26.10 - - login: Admin - - password: xxxxx - -2. Enter the following request: - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - This is how the result should look: - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost","is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Retrieve the token number to use it in the next request. - -4. Then enter this request: - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. This request does not return any result. To check if the update has been successfully applied, read the version number displayed on the Centreon web interface login page. - - - - -Finally, restart Broker, Engine and Gorgone on the central server by running this command: - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Update the permissions on the centreon-broker configuration files. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. - -### Step 6: 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: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * To adapt the commands automatically, run: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (You can also adapt them manually.) - -3. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Restart the processes: - - ``` shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -### Step 7: Upgrade the database +### Step 8: Upgrade the database * If you were using MariaDB, [upgrade it](upgrade-mariadb.md) to version 11.8. * If you were using MySQL 8.0, [upgrade it to version 8.4](upgrade-mysql.md). * If you were already using MySQL 8.4, you don't need to do anything. -## Upgrade the Remote Servers - -This procedure is the same as for upgrading a Centreon Central server with the addition of needing to retrieve the decryption key at the end. - -### Retrieving the decryption key - -Run the following script with the central server IP address to enable the remote server to receive and process encrypted data: - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -> 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: - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -### Upgrade the Centreon solution - -Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* -``` - -> If you installed MariaDB from their official repositiories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. - - - - -> Accept new GPG keys from the repositories as needed. - -Restart **centreon**: - -```shell -systemctl restart centreon -``` -### Retrieving the decryption key - -Run the following script with the correct IP address to enable the poller to receive and process encrypted data. - -The IP address to use depends on the following conditions: -- When updating pollers linked directly to the central server, use the central server's IP. -- When updating pollers linked to a remote server, use the remote server's IP. However, in this instance, you must first confirm the remote server has the correct key by checking that the value of `app_secret` in the `/etc/centreon-engine/engine-context.json` file is the same as the central server's. If this is not the case, relaunch the script with the right IP to correct the .json file. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: + -```shell -systemctl restart centengine -``` + diff --git a/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md b/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md index 7f67c488e288..d462986490ad 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md @@ -47,7 +47,7 @@ To find out which version of MariaDB is installed on your machine, enter the fol rpm -qa |grep MariaDB ``` -The results should look like this: +The results should look like this example: ```shell MariaDB-client-10.5.8-1.el8.centos.x86_64 @@ -64,7 +64,7 @@ MariaDB-compat-10.5.8-1.el8.centos.x86_64 rpm -qa |grep MariaDB ``` -The results should look like this: +The results should look like this example: ```shell MariaDB-client-10.5.8-1.el9.centos.x86_64 @@ -81,7 +81,7 @@ MariaDB-compat-10.5.8-1.el9.centos.x86_64 dpkg -l |grep MariaDB ``` -The results should look like this: +The results should look like this example: ```shell ii libdbd-mysql-perl:amd64 4.050-3+b1 amd64 Perl5 database interface to the MariaDB/MySQL database @@ -100,7 +100,7 @@ ii mysql-common 1:10.5.17+maria~deb11 all ## Upgrading between major MariaDB versions -You must uninstall then reinstall MariaDB to upgrade between major versions (for example to switch from version 10.11 to version 11.8). +You must uninstall then reinstall MariaDB to upgrade between major versions. In this example, we will switch from version 10.11 to version 11.8. Adapt the procedure if you are upgrading from another version. 1. Stop the MariaDB service: From 1dfa74fa384fbdb784d8f786ce9ffb53adf5c40b Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 7 Jul 2026 18:34:51 +0200 Subject: [PATCH 024/179] Remove duplicate paragraph --- versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index bd594529acd8..82b0527431c4 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -51,12 +51,6 @@ Before upgrading your Centreon platform, make sure the following package reposit -### Step 8: Upgrade the database - -* If you were using MariaDB, [upgrade it](upgrade-mariadb.md) to version 11.8. -* If you were using MySQL 8.0, [upgrade it to version 8.4](upgrade-mysql.md). -* If you were already using MySQL 8.4, you don't need to do anything. - From 60d3bbc7bcde363fced29969d44cfc94f534afda Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 7 Jul 2026 18:47:21 +0200 Subject: [PATCH 025/179] Update single sourcing for "upgrade for 25.10" procedure --- .../version-26.10/upgrade/_intro.mdx | 40 ++++++++++++++++- .../upgrade/_upgrade-central.mdx | 16 ++++--- .../upgrade/upgrade-from-25-10.md | 43 +------------------ 3 files changed, 51 insertions(+), 48 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/_intro.mdx b/versioned_docs/version-26.10/upgrade/_intro.mdx index 8674a2bb7057..86412bf95da3 100644 --- a/versioned_docs/version-26.10/upgrade/_intro.mdx +++ b/versioned_docs/version-26.10/upgrade/_intro.mdx @@ -1,7 +1,43 @@ -This chapter describes how to upgrade your Centreon platform from version {props.type} to version 26.10. +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +This chapter describes how to upgrade your Centreon platform from version {props.oldCentreonVersion} to version 26.10. Upgrading is only possible if your current OS is RHEL/Oracle/AlmaLinux 9. Other OSs are no longer supported: use a [migration procedure](../migrate/introduction.md) to switch to a supported OS. If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. * 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](../developer/developer-broker-bbdo-switch-versions.md). \ No newline at end of file +* In addition, all servers must use the same [version of the BBDO protocol](../developer/developer-broker-bbdo-switch-versions.md). + +## Components other than Centreon that need upgrading + +| Component | Version in {props.oldCentreonVersion} | Version in 26.10 | +| --- | --- | --- | +| PHP | {props.oldPhpVersion} | 8.4 | +| Database |
  • {props.oldMariadbVersion}
  • {props.oldMysqlVersion}
|
  • MariaDB 11.8
  • MySQL 8.4
| + +## Prerequisites + +### Perform a backup + +Be sure that you have fully backed up your environment for the following +servers: + +- Central server +- Database server + +### Check the repositories + +Before upgrading your Centreon platform, make sure the following package repositories are enabled: + + + + +* EPEL +* BaseOS +* AppStream +* centreon +* centreon-modules, if you are using Centreon Business Edition. + + + \ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index 66d59730d185..155b2bf28330 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -2,17 +2,23 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import CodeBlock from '@theme/CodeBlock'; +## 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. + +> If you installed MariaDB from their official repositories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. + ### Step 1: Install the new repositories -1. Update your Centreon {props.centreonVersion} to the latest minor version. +1. Update your Centreon {props.oldCentreonVersion} to the latest minor version. 2. Remove the repository files: - {`rm /etc/yum.repos.d/centreon-${props.centreonVersion}.repo\nrm /etc/yum.repos.d/centreon.repo`} + {`rm /etc/yum.repos.d/centreon-${props.oldCentreonVersion}.repo\nrm /etc/yum.repos.d/centreon.repo`} 3. Install the new repository: @@ -31,12 +37,12 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/e 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 {props.centreonVersion} repository: +2. If you have installed Business extensions, delete the configuration of the {props.oldCentreonVersion} repository: -{`rm /etc/yum.repos.d/centreon-business-${props.centreonVersion}.repo`} +{`rm /etc/yum.repos.d/centreon-business-${props.oldCentreonVersion}.repo`} @@ -64,7 +70,7 @@ Centreon 26.10 uses PHP in version 8.4. -You need to change the PHP stream from version {props.phpVersion} to 8.4 by executing the following commands and answering **y** +You need to change the PHP stream from version {props.oldPhpVersion} to 8.4 by executing the following commands and answering **y** to confirm: ```shell diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index 82b0527431c4..ee377f32edaf 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -8,48 +8,9 @@ import Intro from './_intro.mdx' import UpgradeCentral from './_upgrade-central.mdx' import UpgradeRemotes from './_upgrade-remotes.mdx' - + -## Which components need upgrading - -| Component | Version in 25.10 | Version in 26.10 | -| --- | --- | --- | -| PHP | 8.2 | 8.4 | -| Database |
  • MariaDB 10.11.x
  • MySQL 8.0 or 8.4
|
  • MariaDB 11.8
  • MySQL 8.4
| - -## Prerequisites - -### Perform a backup - -Be sure that you have fully backed up your environment for the following -servers: - -- Central server -- Database server - -### Check the repositories - -Before upgrading your Centreon platform, make sure the following package repositories are enabled: - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## 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. - -> If you installed MariaDB from their official repositories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. - - + From 89c6c7fac0ff90947e2e3665356174110c284310 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 7 Jul 2026 18:53:29 +0200 Subject: [PATCH 026/179] Finish single sourcing all "upgrade to 26.10" procedures --- .../upgrade/upgrade-from-23-04.md | 518 +--------- .../upgrade/upgrade-from-23-10.md | 887 +----------------- .../upgrade/upgrade-from-24-04.md | 887 +----------------- .../upgrade/upgrade-from-24-10.md | 813 +--------------- .../upgrade/upgrade-from-25-10.md | 1 + 5 files changed, 29 insertions(+), 3077 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md index 33c70cfb196f..947bc4b5ff6d 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md @@ -5,518 +5,14 @@ title: Upgrade from Centreon 23.04 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import Intro from './_intro.mdx' +import UpgradeCentral from './_upgrade-central.mdx' +import UpgradeRemotes from './_upgrade-remotes.mdx' +import UpgradePollers from './_upgrade-pollers.mdx' - + -> Version 23.04 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. + -## Which components need upgrading + -| Component | Version in 23.04 | Version in 26.10 | -| --- | --- | --- | -| PHP | 8.1 | 8.4 | -| Database | MariaDB 10.5.x | MariaDB 11.8 | - -> Business edition users: MAP Legacy is no longer available in Centreon 25.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Warning: If you were using the following monitoring connectors, from version 25.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prerequisites - -### Perform a backup - -Be sure that you have fully backed up your environment for the following -servers: - -- Central server -- Database server - -If you use Open Ticket providers with custom configurations, [make a backup of these before updating Centreon](../alerts-notifications/ticketing-install.md#creating-a-backup-of-your-custom-open-ticket-provider-configurations). - -### Check the repositories - -Before upgrading your Centreon platform, make sure the following package repositories are enabled: - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## 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 23.04 to the latest minor version. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/23.04/el9/centreon-23.04-el9.repo - dnf clean all --enablerepo=* - dnf update - ``` - - -2. Remove the repository files: - - ```shell - rm /etc/yum.repos.d/centreon-23.04.repo - rm /etc/yum.repos.d/centreon.repo - ``` - -3. Install the new repository: - -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo -``` - - - - -> If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). - -### 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 23.04 repository: - - - - -```shell -rm /etc/yum.repos.d/centreon-business-23.04.repo -``` - - - - -3. Install the 25.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. - -5. Stop the Centreon Broker process: - -```shell -systemctl stop cbd -``` - -6. Delete existing retention files: - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Upgrade PHP - -Centreon 26.10 uses PHP in version 8.4. - - - - -You need to change the PHP stream from version 8.1 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - - - - -Then, finish upgrading the Centreon solution. - -1. Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -2. Then upgrade all the components with the following command: - - - - -```shell -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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 - -``` - - - - -#### 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 `` and `` elements: - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -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](../service-mapping/upgrade.md) and reload the Apache server with the -following command: - - - - -```shell -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](../assets/upgrade/web_update_1.png) - -2. Click **Next**: - - ![image](../assets/upgrade/web_update_2.png) - -3. The release notes describe the main changes. Click **Next**: - - ![image](../assets/upgrade/web_update_3.png) - -4. This process performs the various upgrades. Click **Next**: - - ![image](../assets/upgrade/web_update_4.png) - -5. Your Centreon server is now up to date. Click **Finish** to access the login -page: - - ![image](../assets/upgrade/web_update_5.png) - -Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. - -6. Deploy the central's configuration from the Centreon web UI by following [this -procedure](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -1. Log on to the central server through your terminal to continue the update process. - - > You need an authentication token to reach the API endpoint. Perform the following procedure to get a token. - - In our case, we have the configuration described below (you need to adapt the procedure to your configuration). - - address: 10.25.XX.XX - - port: 80 - - version: 25.10 - - login: Admin - - password: xxxxx - -2. Enter the following request: - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - This is how the result should look: - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost","is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Retrieve the token number to use it in the next request. - -4. Then enter this request: - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. This request does not return any result. To check if the update has been successfully applied, read the version number displayed on the Centreon web interface login page. - - - - -Finally, restart Broker, Engine and Gorgone on the central server by running this command: - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Add the **apache** user to the **centreon-broker** group and vice versa. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -### 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: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * To adapt the commands automatically, run: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (You can also adapt them manually.) - -3. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Restart the processes: - - ``` shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Upgrade MariaDB - -Follow [this procedure](upgrade-mariadb.md) to upgrade MariaDB to version 10.11. - -## Upgrade the Remote Servers - -This procedure is the same as for upgrading a Centreon Central server with the addition of needing to retrieve the decryption key at the end. - -### Retrieving the decryption key - -Run the following script with the central server IP address to enable the remote server to receive and process encrypted data: - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -> 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: - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo -``` - - - - -### Upgrade the Centreon solution - -Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* -``` - - - - -> Accept new GPG keys from the repositories as needed. - -Restart **centreon**: - -```shell -systemctl restart centreon -``` - -### Retrieving the decryption key - -Run the following script with the correct IP address to enable the poller to receive and process encrypted data. - -The IP address to use depends on the following conditions: -- When updating pollers linked directly to the central server, use the central server's IP. -- When updating pollers linked to a remote server, use the remote server's IP. However, in this instance, you must first confirm the remote server has the correct key by checking that the value of `app_secret` in the `/etc/centreon-engine/engine-context.json` file is the same as the central server's. If this is not the case, relaunch the script with the right IP to correct the .json file. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` + \ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md index f3aa4e2a39c1..92f2b960cd14 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md @@ -5,887 +5,14 @@ title: Upgrade from Centreon 23.10 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import Intro from './_intro.mdx' +import UpgradeCentral from './_upgrade-central.mdx' +import UpgradeRemotes from './_upgrade-remotes.mdx' +import UpgradePollers from './_upgrade-pollers.mdx' - + -> Version 23.10 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. + -## Which components need upgrading + -| Component | Version in 23.10 | Version in 26.10 | -| --- | --- | --- | -| PHP | 8.1 | 8.4 | -| Database | MariaDB 10.5.x | MariaDB 11.8 | - -> Business edition users: MAP Legacy is no longer available in Centreon 25.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Warning: If you were using the following monitoring connectors, from version 25.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prerequisites - -### Perform a backup - -Be sure that you have fully backed up your environment for the following -servers: - -- Central server -- Database server - -If you use Open Ticket providers with custom configurations, [make a backup of these before updating Centreon](../alerts-notifications/ticketing-install.md#creating-a-backup-of-your-custom-open-ticket-provider-configurations). - -### Check the repositories - -Before upgrading your Centreon platform, make sure the following package repositories are enabled: - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## 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 23.10 to the latest minor version. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/23.10/el8/centreon-23.10-el8.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Remove the repository files: - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Install the new repository: - - ```shell - 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=* - ``` - - - - -1. Update your Centreon 23.10 to the latest minor version. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/23.10/el9/centreon-23.10-el9.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Remove the repository files: - - ```shell - rm /etc/yum.repos.d/centreon-23.10.repo - rm /etc/yum.repos.d/centreon.repo - ``` - -3. Install the new repository: - -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo -``` - - - - -1. Update your Centreon 23.10 to the latest minor version. -2. Run the following commands: - -```shell -rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Then import the repository key: - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -> If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). - -### 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 23.10 repository: - - - - -```shell -rm /etc/yum.repos.d/centreon-business-23.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-23.10.repo -``` - - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - - - - -3. Install the 25.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. - -4. 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**). - -5. Stop the Centreon Broker process: - -```shell -systemctl stop cbd -``` - -6. Delete existing retention files: - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Upgrade PHP - -Centreon 25.10 uses PHP in version 8.2. - - - - -You need to change the PHP stream from version 8.1 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.1 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -You need to change the PHP stream from version 8.1 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - - - - -```shell -systemctl stop php8.1-fpm -systemctl disable php8.1-fpm -``` - -Ensure the `memory_limit` parameter in `/etc/php/8.2/fpm/conf.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - - - - -Then, finish upgrading the Centreon solution. - -1. Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -2. Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> 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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 - -``` - - - - -Use the backup file you created in the previous step to copy your customizations to the file **/etc/apache2/sites-available/centreon.conf**. - -Check that Apache is configured properly by running the following command: - -```shell -apache2ctl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Check the status of Apache: - -```shell -systemctl status apache2 -``` - -If everything is ok, you should have: - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -#### 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 `` and `` elements: - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -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](../service-mapping/upgrade.md) and reload the Apache server with the -following command: - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - - - - -Then you need to finalize the upgrade process: - - - - -1. Log on to the Centreon web interface to continue the update process. Click **Next**: - - ![image](../assets/upgrade/web_update_1.png) - -2. Click **Next**: - - ![image](../assets/upgrade/web_update_2.png) - -3. The release notes describe the main changes. Click **Next**: - - ![image](../assets/upgrade/web_update_3.png) - -4. This process performs the various upgrades. Click **Next**: - - ![image](../assets/upgrade/web_update_4.png) - -5. Your Centreon server is now up to date. Click **Finish** to access the login -page: - - ![image](../assets/upgrade/web_update_5.png) - -Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. - -6. Deploy the central's configuration from the Centreon web UI by following [this -procedure](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -1. Log on to the central server through your terminal to continue the update process. - - > You need an authentication token to reach the API endpoint. Perform the following procedure to get a token. - - In our case, we have the configuration described below (you need to adapt the procedure to your configuration). - - address: 10.25.XX.XX - - port: 80 - - version: 25.10 - - login: Admin - - password: xxxxx - -2. Enter the following request: - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - This is how the result should look: - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost","is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Retrieve the token number to use it in the next request. - -4. Then enter this request: - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. This request does not return any result. To check if the update has been successfully applied, read the version number displayed on the Centreon web interface login page. - - - - -Finally, restart Broker, Engine and Gorgone on the central server by running this command: - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Add the **apache** user to the **centreon-broker** group and vice versa. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - - - - - -### 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: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * To adapt the commands automatically, run: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (You can also adapt them manually.) - -3. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -> Starting with version 25.10, dynamic substitution of variables (also called string interpolation) is no longer allowed in auto-discovery commands related to connectors. -> -> If you use custom commands that rely on string interpolation, you must update them to remain compatible. -> -> This new rule is enforced in `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml.rpm` via the `no_shell_interpretation: true` parameter. If you previously customized this file, your version will be saved in the same directory as `41-autodiscovery.yaml.rpmnew` and must be manually merged to include this parameter. - - - - -> Starting with version 25.10, dynamic substitution of variables (also called string interpolation) is no longer allowed in auto-discovery commands related to connectors. -> -> If you use custom commands that rely on string interpolation, you must update them to remain compatible. -> -> This new rule is enforced in `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml.rpm` via the `no_shell_interpretation: true` parameter. If you previously customized this file, your version will be saved in the same directory as `41-autodiscovery.yaml.rpmnew` and must be manually merged to include this parameter. - - - - -> Starting with version 25.10, dynamic substitution of variables (also called string interpolation) is no longer allowed in auto-discovery commands related to connectors. -> -> If you use custom commands that rely on string interpolation, you must update them to remain compatible. -> -> This new rule is enforced in `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml` via the `no_shell_interpretation: true` parameter. If you previously customized this file, you will be prompted to resolve the potential conflicts. - - - - -4. Restart the processes: - - ``` shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Upgrade MariaDB - -Follow [this procedure](upgrade-mariadb.md) to upgrade MariaDB to version 10.11. - -## Upgrade the Remote Servers - -This procedure is the same as for upgrading a Centreon Central server with the addition of needing to retrieve the decryption key at the end. - -### Retrieving the decryption key - -Run the following script with the central server IP address to enable the remote server to receive and process encrypted data: - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -> 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: - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo -``` - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo -``` - - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list -apt update -``` - - - - -### Upgrade the Centreon solution - -Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -apt install --only-upgrade centreon-poller -``` - - - - -> Accept new GPG keys from the repositories as needed. - -Restart **centreon**: - -```shell -systemctl restart centreon -``` - -### Retrieving the decryption key - -Run the following script with the correct IP address to enable the poller to receive and process encrypted data. - -The IP address to use depends on the following conditions: -- When updating pollers linked directly to the central server, use the central server's IP. -- When updating pollers linked to a remote server, use the remote server's IP. However, in this instance, you must first confirm the remote server has the correct key by checking that the value of `app_secret` in the `/etc/centreon-engine/engine-context.json` file is the same as the central server's. If this is not the case, relaunch the script with the right IP to correct the .json file. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` + \ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md index 40ccbef7ffca..7f74ce5790e8 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md @@ -5,887 +5,14 @@ title: Upgrade from Centreon 24.04 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import Intro from './_intro.mdx' +import UpgradeCentral from './_upgrade-central.mdx' +import UpgradeRemotes from './_upgrade-remotes.mdx' +import UpgradePollers from './_upgrade-pollers.mdx' - + -> Version 24.04 is no longer supported. Upgrade from this version has not been tested by the Centreon QA team. + -## Which components need upgrading + -| Component | Version in 24.04 | Version in 26.10 | -| --- | --- | --- | -| PHP | 8.1 | 8.4 | -| Database | MariaDB 10.11.x | MariaDB 11.8 | - -> Warning: If you were using the following monitoring connectors, from version 24.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prerequisites - -### Perform a backup - -Be sure that you have fully backed up your environment for the following -servers: - -- Central server -- Database server - -If you use Open Ticket providers with custom configurations, [make a backup of these before updating Centreon](../alerts-notifications/ticketing-install.md#creating-a-backup-of-your-custom-open-ticket-provider-configurations). - -### Check the repositories - -Before upgrading your Centreon platform, make sure the following package repositories are enabled: - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## 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. - -> If you installed MariaDB from their official repositiories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. - -### Install the new repositories - - - - -1. Update your Centreon 24.04 to the latest minor version. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/24.04/el8/centreon-24.04.repo - dnf clean all --enablerepo=* - dnf update - ``` - - -2. Remove the repository files: - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Install the new repository: - - ```shell - 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=* - ``` - - - - -1. Update your Centreon 24.04 to the latest minor version. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/24.04/el9/centreon-24.04.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Remove the repository files: - - ```shell - rm /etc/yum.repos.d/centreon-24.04.repo - rm /etc/yum.repos.d/centreon.repo - ``` - -3. Install the new repository: - -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo -``` - - - - -1. Update your Centreon 24.04 to the latest minor version. - -2. Run the following commands: - -```shell -rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Then import the repository key: - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -> If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). - -### 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.04 repository: - - - - -```shell -rm /etc/yum.repos.d/centreon-business-24.04.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-24.04.repo -``` - - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - - - - -3. Install the 25.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. - -4. 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**). - -5. Stop the Centreon Broker process: - -```shell -systemctl stop cbd -``` - -6. Delete existing retention files: - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Upgrade PHP - -Centreon 25.10 uses PHP in version 8.2. - - - - -You need to change the PHP stream from version 8.1 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.1 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -You need to change the PHP stream from version 8.1 to 8.2 by executing the following commands and answering **y** -to confirm: - -```shell -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - - - - -```shell -systemctl stop php8.1-fpm -systemctl disable php8.1-fpm -``` - -Ensure the `memory_limit` parameter in `/etc/php/8.2/fpm/conf.d/50-centreon.ini` is set to at least 256mb. If it isn't, insert it manually. - - - - -Then, finish upgrading the Centreon solution. - -1. Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -2. Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> 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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 - -``` - - - - -Use the backup file you created in the previous step to copy your customizations to the file **/etc/apache2/sites-available/centreon.conf**. - -Check that Apache is configured properly by running the following command: - -```shell -apache2ctl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Check the status of Apache: - -```shell -systemctl status apache2 -``` - -If everything is ok, you should have: - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -#### 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 `` and `` elements: - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -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](../service-mapping/upgrade.md) and reload the Apache server with the -following command: - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - - - - -Then you need to finalize the upgrade process: - - - - -1. Log on to the Centreon web interface to continue the update process. Click **Next**: - - ![image](../assets/upgrade/web_update_1.png) - -2. Click **Next**: - - ![image](../assets/upgrade/web_update_2.png) - -3. The release notes describe the main changes. Click **Next**: - - ![image](../assets/upgrade/web_update_3.png) - -4. This process performs the various upgrades. Click **Next**: - - ![image](../assets/upgrade/web_update_4.png) - -5. Your Centreon server is now up to date. Click **Finish** to access the login -page: - - ![image](../assets/upgrade/web_update_5.png) - -Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. - -6. Deploy the central's configuration from the Centreon web UI by following [this -procedure](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -1. Log on to the central server through your terminal to continue the update process. - - > You need an authentication token to reach the API endpoint. Perform the following procedure to get a token. - - In our case, we have the configuration described below (you need to adapt the procedure to your configuration). - - address: 10.25.XX.XX - - port: 80 - - version: 25.10 - - login: Admin - - password: xxxxx - -2. Enter the following request: - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - This is how the result should look: - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost","is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Retrieve the token number to use it in the next request. - -4. Then enter this request: - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. This request does not return any result. To check if the update has been successfully applied, read the version number displayed on the Centreon web interface login page. - - - - -Finally, restart Broker, Engine and Gorgone on the central server by running this command: - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Add the **apache** user to the **centreon-broker** group and vice versa. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - - - - - -### 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: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * To adapt the commands automatically, run: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (You can also adapt them manually.) - -3. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -> Starting with version 25.10, dynamic substitution of variables (also called string interpolation) is no longer allowed in auto-discovery commands related to connectors. -> -> If you use custom commands that rely on string interpolation, you must update them to remain compatible. -> -> This new rule is enforced in `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml.rpm` via the `no_shell_interpretation: true` parameter. If you previously customized this file, your version will be saved in the same directory as `41-autodiscovery.yaml.rpmnew` and must be manually merged to include this parameter. - - - - -> Starting with version 25.10, dynamic substitution of variables (also called string interpolation) is no longer allowed in auto-discovery commands related to connectors. -> -> If you use custom commands that rely on string interpolation, you must update them to remain compatible. -> -> This new rule is enforced in `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml.rpm` via the `no_shell_interpretation: true` parameter. If you previously customized this file, your version will be saved in the same directory as `41-autodiscovery.yaml.rpmnew` and must be manually merged to include this parameter. - - - - -> Starting with version 25.10, dynamic substitution of variables (also called string interpolation) is no longer allowed in auto-discovery commands related to connectors. -> -> If you use custom commands that rely on string interpolation, you must update them to remain compatible. -> -> This new rule is enforced in `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml` via the `no_shell_interpretation: true` parameter. If you previously customized this file, you will be prompted to resolve the potential conflicts. - - - - -4. Restart the processes: - - ``` shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Upgrade the Remote Servers - -This procedure is the same as for upgrading a Centreon Central server with the addition of needing to retrieve the decryption key at the end. - -### Retrieving the decryption key - -Run the following script with the central server IP address to enable the remote server to receive and process encrypted data: - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -> 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: - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo -``` - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo -``` - - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list -apt update -``` - - - - -### Upgrade the Centreon solution - -Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -dnf update centreon\* -``` - -> If you installed MariaDB from their official repositiories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. - - - - -```shell -apt install --only-upgrade centreon-poller -``` - - - - -> Accept new GPG keys from the repositories as needed. - -Restart **centreon**: - -```shell -systemctl restart centreon -``` - -### Retrieving the decryption key - -Run the following script with the correct IP address to enable the poller to receive and process encrypted data. - -The IP address to use depends on the following conditions: -- When updating pollers linked directly to the central server, use the central server's IP. -- When updating pollers linked to a remote server, use the remote server's IP. However, in this instance, you must first confirm the remote server has the correct key by checking that the value of `app_secret` in the `/etc/centreon-engine/engine-context.json` file is the same as the central server's. If this is not the case, relaunch the script with the right IP to correct the .json file. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` + \ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md index 0afacdf2fb00..b51807bfeabc 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md @@ -5,813 +5,14 @@ title: Upgrade from Centreon 24.10 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import Intro from './_intro.mdx' +import UpgradeCentral from './_upgrade-central.mdx' +import UpgradeRemotes from './_upgrade-remotes.mdx' +import UpgradePollers from './_upgrade-pollers.mdx' - + -## Which components need upgrading + -| Component | Version in 24.10 | Version in 26.10 | -| --- | --- | --- | -| PHP | 8.2 | 8.4 | -| Database |
  • MariaDB 10.11.x
  • MySQL 8.0 or 8.4
|
  • MariaDB 11.8
  • MySQL 8.4
| + -## Prerequisites - -### Perform a backup - -Be sure that you have fully backed up your environment for the following -servers: - -- Central server -- Database server - -### Check the repositories - -Before upgrading your Centreon platform, make sure the following package repositories are enabled: - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## 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. - -> If you installed MariaDB from their official repositiories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. - -### Install the new repositories - - - - -1. Update your Centreon 24.10 to the latest minor version. - - ```shell - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/24.10/el8/centreon-24.10.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Remove the repository files: - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Install the new repository: - - ```shell - 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=* - ``` - - - - -1. Update your Centreon 24.10 to the latest minor version. - - ```shell - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/24.10/el9/centreon-24.10.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Remove the repository files: - - ```shell - rm /etc/yum.repos.d/centreon-24.10.repo - rm /etc/yum.repos.d/centreon.repo - ``` - -3. Install the new repository: - -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo -``` - - - - -1. Update your Centreon 24.10 to the latest minor version. - -2. Run the following commands: - -```shell -rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Then import the repository key: - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -> If you have an [offline license](../administration/licenses.md#types-of-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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). - -### 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: - - - - -```shell -rm /etc/yum.repos.d/centreon-business-24.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-24.10.repo -``` - - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - - - - -3. Install the 25.10 Business repository: visit the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) to get its address. - -4. 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**). - -5. Stop the Centreon Broker process: - -```shell -systemctl stop cbd -``` - -6. Delete existing retention files: - -```shell -rm /var/lib/centreon-broker/* -f -``` - -Ensure the `memory_limit` parameter in `/etc/php.d/50-centreon.ini` (`/etc/php/8.2/fpm/conf.d/50-centreon.ini` for Debian) is set to at least 256mb. If it isn't, insert it manually. - -7. Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -8. Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -```shell -dnf update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> 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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 - -``` - - - - -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: - -```shell -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: - -```shell -apachectl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Restart the Apache and PHP processes to take the new configuration into account: - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 - -``` - - - - -Use the backup file you created in the previous step to copy your customizations to the file **/etc/apache2/sites-available/centreon.conf**. - -Check that Apache is configured properly by running the following command: - -```shell -apache2ctl configtest -``` - -The expected result is the following: - -```shell -Syntax OK -``` - -Check the status of Apache: - -```shell -systemctl status apache2 -``` - -If everything is ok, you should have: - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2024-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -#### 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 `` and `` elements: - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -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](../service-mapping/upgrade.md) and reload the Apache server with the -following command: - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - - - - -Then you need to finalize the upgrade process: - - - - -1. Log on to the Centreon web interface to continue the update process. Click **Next**: - - ![image](../assets/upgrade/web_update_1.png) - -2. Click **Next**: - - ![image](../assets/upgrade/web_update_2.png) - -3. The release notes describe the main changes. Click **Next**: - - ![image](../assets/upgrade/web_update_3.png) - -4. This process performs the various upgrades. Click **Next**: - - ![image](../assets/upgrade/web_update_4.png) - -5. Your Centreon server is now up to date. Click **Finish** to access the login -page: - - ![image](../assets/upgrade/web_update_5.png) - -6. Deploy the central's configuration from the Centreon web UI by following [this -procedure](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -1. Log on to the central server through your terminal to continue the update process. - - > You need an authentication token to reach the API endpoint. Perform the following procedure to get a token. - - In our case, we have the configuration described below (you need to adapt the procedure to your configuration). - - address: 10.25.XX.XX - - port: 80 - - version: 25.10 - - login: Admin - - password: xxxxx - -2. Enter the following request: - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v25.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - This is how the result should look: - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost","is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Retrieve the token number to use it in the next request. - -4. Then enter this request: - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. This request does not return any result. To check if the update has been successfully applied, read the version number displayed on the Centreon web interface login page. - - - - -Finally, restart Broker, Engine and Gorgone on the central server by running this command: - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Update the permissions on the centreon-broker configuration files. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - - - - -Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) 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: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * To adapt the commands automatically, run: - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (You can also adapt them manually.) - -3. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -> Starting with version 25.10, dynamic substitution of variables (also called string interpolation) is no longer allowed in auto-discovery commands related to connectors. -> -> If you use custom commands that rely on string interpolation, you must update them to remain compatible. -> -> This new rule is enforced in `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml.rpm` via the `no_shell_interpretation: true` parameter. If you previously customized this file, your version will be saved in the same directory as `41-autodiscovery.yaml.rpmnew` and must be manually merged to include this parameter. - - - - -> Starting with version 25.10, dynamic substitution of variables (also called string interpolation) is no longer allowed in auto-discovery commands related to connectors. -> -> If you use custom commands that rely on string interpolation, you must update them to remain compatible. -> -> This new rule is enforced in `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml.rpm` via the `no_shell_interpretation: true` parameter. If you previously customized this file, your version will be saved in the same directory as `41-autodiscovery.yaml.rpmnew` and must be manually merged to include this parameter. - - - - -> Starting with version 25.10, dynamic substitution of variables (also called string interpolation) is no longer allowed in auto-discovery commands related to connectors. -> -> If you use custom commands that rely on string interpolation, you must update them to remain compatible. -> -> This new rule is enforced in `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml` via the `no_shell_interpretation: true` parameter. If you previously customized this file, you will be prompted to resolve the potential conflicts. - - - - -4. Restart the processes: - - ``` shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Upgrade the Remote Servers - -This procedure is the same as for upgrading a Centreon Central server with the addition of needing to retrieve the decryption key at the end. - -### Retrieving the decryption key - -Run the following script with the central server IP address to enable the remote server to receive and process encrypted data: - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` - -> 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: - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard-25.10-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon.list -apt update -``` - - - - -### Upgrade the Centreon solution - -Clean the cache: - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -Then upgrade all the components with the following command: - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -dnf update centreon\* -``` - -> If you installed MariaDB from their official repositiories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. - - - - -```shell -apt install --only-upgrade centreon-poller -``` - - - - -> Accept new GPG keys from the repositories as needed. - -Restart **centreon**: - -```shell -systemctl restart centreon -``` -### Retrieving the decryption key - -Run the following script with the correct IP address to enable the poller to receive and process encrypted data. - -The IP address to use depends on the following conditions: -- When updating pollers linked directly to the central server, use the central server's IP. -- When updating pollers linked to a remote server, use the remote server's IP. However, in this instance, you must first confirm the remote server has the correct key by checking that the value of `app_secret` in the `/etc/centreon-engine/engine-context.json` file is the same as the central server's. If this is not the case, relaunch the script with the right IP to correct the .json file. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Example: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> You must use **admin** as the **\**. - -Restart **centengine**: - -```shell -systemctl restart centengine -``` + diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index ee377f32edaf..06a9599e8663 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -7,6 +7,7 @@ import TabItem from '@theme/TabItem'; import Intro from './_intro.mdx' import UpgradeCentral from './_upgrade-central.mdx' import UpgradeRemotes from './_upgrade-remotes.mdx' +import UpgradePollers from './_upgrade-pollers.mdx' From 76681b18213eb1ee38bef41ea9d4e2e1170bdbf8 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 7 Jul 2026 19:01:52 +0200 Subject: [PATCH 027/179] Fix variable --- versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md | 2 +- versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md | 2 +- versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md | 2 +- versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md | 2 +- versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md index 947bc4b5ff6d..d9bc33aba596 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md @@ -11,7 +11,7 @@ import UpgradePollers from './_upgrade-pollers.mdx' - + diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md index 92f2b960cd14..5d5a8187fae3 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md @@ -11,7 +11,7 @@ import UpgradePollers from './_upgrade-pollers.mdx' - + diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md index 7f74ce5790e8..84ba99abbefb 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md @@ -11,7 +11,7 @@ import UpgradePollers from './_upgrade-pollers.mdx' - + diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md index b51807bfeabc..b693ba88a32b 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md @@ -11,7 +11,7 @@ import UpgradePollers from './_upgrade-pollers.mdx' - + diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index 06a9599e8663..e8015c44c842 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -11,7 +11,7 @@ import UpgradePollers from './_upgrade-pollers.mdx' - + From fbe5127fc88cc362f58afc130b744ab6a91c74a8 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 9 Jul 2026 10:29:26 +0200 Subject: [PATCH 028/179] Update --- .../version-26.10/upgrade/_intro.mdx | 2 +- .../upgrade/_upgrade-central.mdx | 67 +++++-------------- 2 files changed, 19 insertions(+), 50 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/_intro.mdx b/versioned_docs/version-26.10/upgrade/_intro.mdx index 86412bf95da3..f6829bde408a 100644 --- a/versioned_docs/version-26.10/upgrade/_intro.mdx +++ b/versioned_docs/version-26.10/upgrade/_intro.mdx @@ -3,7 +3,7 @@ import TabItem from '@theme/TabItem'; This chapter describes how to upgrade your Centreon platform from version {props.oldCentreonVersion} to version 26.10. -Upgrading is only possible if your current OS is RHEL/Oracle/AlmaLinux 9. Other OSs are no longer supported: use a [migration procedure](../migrate/introduction.md) to switch to a supported OS. If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. +Upgrading is only possible if your current OS is RHEL/Oracle/AlmaLinux 9. [Other OSs are no longer supported](upgrade-matrix.mdx): use a [migration procedure](../migrate/introduction.md) to switch to a supported OS. If your Centreon platform has HA, please contact your Centreon sales representative to discuss any migration scenario. * 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. diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index 155b2bf28330..3c5099c1357a 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -245,46 +245,15 @@ page: -1. Log on to the central server through your terminal to continue the update process. +1. Go to **Administration > Authentication tokens**, then click **Add**. - > You need an authentication token to reach the API endpoint. Perform the following procedure to get a token. +3. Copy the token to use it in the next request. Store it carefully, as it will not be displayed twice. - In our case, we have the configuration described below (you need to adapt the procedure to your configuration). - - address: 10.25.XX.XX - - port: 80 - - version: 26.10 - - login: Admin - - password: xxxxx - -2. Enter the following request: - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - This is how the result should look: - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost","is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Retrieve the token number to use it in the next request. - -4. Then enter this request: +4. In your terminal, enter this request, using the correct IP address for your platform, and replacing **mytoken** with your actual token: ```shell curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ + --header 'X-AUTH-TOKEN: mytoken' \ --header 'Content-Type: application/json' \ --data '{ "components": [ @@ -300,26 +269,26 @@ page: -Finally, restart Broker, Engine and Gorgone on the central server by running this command: +6. Finally, restart Broker, Engine and Gorgone on the central server by running this command: - ```shell - systemctl restart cbd centengine gorgoned - ``` + ```shell + systemctl restart cbd centengine gorgoned + ``` -Update the permissions on the centreon-broker configuration files. +7. Update the permissions on the centreon-broker configuration files. - - + + -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` + ```shell + usermod -a -G centreon-broker apache + usermod -a -G apache centreon-broker + ``` - - + + -Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. +8. Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. ### Step 7: Post-upgrade actions From 9da51c3aa8d3175d91eb534b01670e51647bf4b3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?St=C3=A9phane=20Chapron?= <34628915+sc979@users.noreply.github.com> Date: Thu, 9 Jul 2026 11:16:04 +0200 Subject: [PATCH 029/179] ignore example login token --- .gitleaks.toml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.gitleaks.toml b/.gitleaks.toml index 2790eed72300..76fbe6758633 100644 --- a/.gitleaks.toml +++ b/.gitleaks.toml @@ -20,5 +20,6 @@ regexTarget = "match" regexes = [ '''ABCDEFG1234567890''', '''deactivation/expiration/revocation''', - '''78e64233e09d3d8ec7bf73c4d9ea8a8851badbd216''' # token example + '''78e64233e09d3d8ec7bf73c4d9ea8a8851badbd216''', # token example, + '''hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S''' # example token generated at centreon login ] From c30d7ed0a645c034ac4e39a22a312420e58a4635 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 9 Jul 2026 17:34:25 +0200 Subject: [PATCH 030/179] Add VMWare and MAP Legacy warnings --- .../version-26.10/upgrade/_intro.mdx | 20 +++++++++++++++++++ .../upgrade/upgrade-from-23-04.md | 2 +- .../upgrade/upgrade-from-23-10.md | 2 +- .../upgrade/upgrade-from-24-04.md | 2 +- 4 files changed, 23 insertions(+), 3 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/_intro.mdx b/versioned_docs/version-26.10/upgrade/_intro.mdx index f6829bde408a..91374e3a43bf 100644 --- a/versioned_docs/version-26.10/upgrade/_intro.mdx +++ b/versioned_docs/version-26.10/upgrade/_intro.mdx @@ -9,6 +9,26 @@ Upgrading is only possible if your current OS is RHEL/Oracle/AlmaLinux 9. [Other * 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](../developer/developer-broker-bbdo-switch-versions.md). +{props.showMapLegacyWarning && ( + +> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/24.10/graph-views/map-legacy-eol/). + +)} + +{props.showVmwareWarning && ( +<> + +> Warning: If you were using the following monitoring connectors, from version 24.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: +> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) +> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) +> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) +> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) +> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) +> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) + + +)} + ## Components other than Centreon that need upgrading | Component | Version in {props.oldCentreonVersion} | Version in 26.10 | diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md index d9bc33aba596..8845b51aff70 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md @@ -9,7 +9,7 @@ import UpgradeCentral from './_upgrade-central.mdx' import UpgradeRemotes from './_upgrade-remotes.mdx' import UpgradePollers from './_upgrade-pollers.mdx' - + diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md index 5d5a8187fae3..40e7e1816e72 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md @@ -9,7 +9,7 @@ import UpgradeCentral from './_upgrade-central.mdx' import UpgradeRemotes from './_upgrade-remotes.mdx' import UpgradePollers from './_upgrade-pollers.mdx' - + diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md index 84ba99abbefb..c47ac4b6b187 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md @@ -9,7 +9,7 @@ import UpgradeCentral from './_upgrade-central.mdx' import UpgradeRemotes from './_upgrade-remotes.mdx' import UpgradePollers from './_upgrade-pollers.mdx' - + From ce280d72d8ab159e31fad54b33b2f169da8231be Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 9 Jul 2026 18:22:25 +0200 Subject: [PATCH 031/179] Fix snippet --- versioned_docs/version-26.10/upgrade/_intro.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/versioned_docs/version-26.10/upgrade/_intro.mdx b/versioned_docs/version-26.10/upgrade/_intro.mdx index 91374e3a43bf..266ec8ad2cc5 100644 --- a/versioned_docs/version-26.10/upgrade/_intro.mdx +++ b/versioned_docs/version-26.10/upgrade/_intro.mdx @@ -10,9 +10,11 @@ Upgrading is only possible if your current OS is RHEL/Oracle/AlmaLinux 9. [Other * In addition, all servers must use the same [version of the BBDO protocol](../developer/developer-broker-bbdo-switch-versions.md). {props.showMapLegacyWarning && ( +<> > Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/24.10/graph-views/map-legacy-eol/). + )} {props.showVmwareWarning && ( From 0e12d251e83176081ace5d76b182d9b411849c44 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 10 Jul 2026 13:24:35 +0200 Subject: [PATCH 032/179] Fix syntax --- .../version-26.10/upgrade/_intro.mdx | 22 ++++++++++--------- 1 file changed, 12 insertions(+), 10 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/_intro.mdx b/versioned_docs/version-26.10/upgrade/_intro.mdx index 266ec8ad2cc5..7b09b0b13dfd 100644 --- a/versioned_docs/version-26.10/upgrade/_intro.mdx +++ b/versioned_docs/version-26.10/upgrade/_intro.mdx @@ -12,22 +12,24 @@ Upgrading is only possible if your current OS is RHEL/Oracle/AlmaLinux 9. [Other {props.showMapLegacyWarning && ( <> -> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/24.10/graph-views/map-legacy-eol/). +
Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/24.10/graph-views/map-legacy-eol/).
)} {props.showVmwareWarning && ( <> - -> Warning: If you were using the following monitoring connectors, from version 24.10 you must declare all of their configurations using [the **Configuration \> Additional connector configurations** page](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) before deploying the configuration of the corresponding poller: -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - +
+

Warning: If you were using the following monitoring connectors, from version 24.10 you must declare all of their configurations using the Configuration > Additional connector configurations page before deploying the configuration of the corresponding poller:

+ +
)} From a32ac08b9a95728890b259a302acbca81d13fa3f Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 10 Jul 2026 17:40:31 +0200 Subject: [PATCH 033/179] Fix Debian update command --- .../version-26.10/update/update-centreon-platform.md | 2 +- versioned_docs/version-26.10/update/update-centreon-platform.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md index 455b61b58f52..31028569bb65 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md @@ -122,7 +122,7 @@ Videz le cache : Mettez à jour l'ensemble des composants : ```shell - apt install --only-upgrade centreon + apt install --only-upgrade "centreon*" ``` diff --git a/versioned_docs/version-26.10/update/update-centreon-platform.md b/versioned_docs/version-26.10/update/update-centreon-platform.md index 1c912b6c3aa7..96eb52d0fc4e 100644 --- a/versioned_docs/version-26.10/update/update-centreon-platform.md +++ b/versioned_docs/version-26.10/update/update-centreon-platform.md @@ -121,7 +121,7 @@ Clean the cache: Then upgrade all the components with the following command: ```shell - apt install --only-upgrade centreon + apt install --only-upgrade "centreon*" ``` From 21cf50a1c5cf8c09450aed7bc9a224ad3b5ca9ca Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 15 Jul 2026 11:07:13 +0200 Subject: [PATCH 034/179] HA update command for Debian --- .../version-26.10/update/update-centreon-ha.md | 2 +- versioned_docs/version-26.10/update/update-centreon-ha.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-ha.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-ha.md index 95670d4485d1..3769cb2fd5a2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-ha.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-ha.md @@ -85,7 +85,7 @@ apt update Mettez à jour l'ensemble des composants : ```shell -apt install --only-upgrade centreon\* +apt install --only-upgrade "centreon*" ``` diff --git a/versioned_docs/version-26.10/update/update-centreon-ha.md b/versioned_docs/version-26.10/update/update-centreon-ha.md index 6b9d25d12dd4..ff225fd4fa57 100644 --- a/versioned_docs/version-26.10/update/update-centreon-ha.md +++ b/versioned_docs/version-26.10/update/update-centreon-ha.md @@ -85,7 +85,7 @@ apt update Update all components: ```shell -apt install --only-upgrade centreon\* +apt install --only-upgrade "centreon*" ``` From 7ad03367d2f4fffa7e0734e593dac131165eb836 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 16 Jul 2026 17:37:09 +0200 Subject: [PATCH 035/179] List allowed special characters for admin password --- .../version-26.10/installation/web-and-post-installation.md | 2 +- .../version-26.10/installation/web-and-post-installation.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md index a5f9b7468ebc..3d47b555d28b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md @@ -42,7 +42,7 @@ Puis cliquez sur **Next**. ### Étape 5 : Admin information -Définissez les informations nécessaires pour la création de l'utilisateur par défaut, **admin**. Vous utiliserez ce compte pour vous connecter à Centreon la première fois. Le mot de passe doit être conforme à la politique de sécurité de mot de passe par défaut : 12 caractères minimum, lettres minuscules et majuscules, chiffres et caractères spéciaux. Vous pourrez changer cette politique par la suite. +Définissez les informations nécessaires pour la création de l'utilisateur par défaut, **admin**. Vous utiliserez ce compte pour vous connecter à Centreon la première fois. Le mot de passe doit être conforme à la politique de sécurité de mot de passe par défaut : 12 caractères minimum, lettres minuscules et majuscules, chiffres et caractères spéciaux (au moins l'un des caractères suivants : @$!%*?&). Vous pourrez changer cette politique par la suite. ![image](../assets/installation/aadmininfo.png) diff --git a/versioned_docs/version-26.10/installation/web-and-post-installation.md b/versioned_docs/version-26.10/installation/web-and-post-installation.md index e8280c613c5d..0cfd1af67a71 100644 --- a/versioned_docs/version-26.10/installation/web-and-post-installation.md +++ b/versioned_docs/version-26.10/installation/web-and-post-installation.md @@ -40,7 +40,7 @@ Then click **Next**. ### Step 5: Admin information -Define the information needed to create the default admin account. This is the account you will use to log in to Centreon for the first time. The password must comply with the default password security policy: at least 12 characters, lower and upper case letters, numbers and special characters. You can change this policy later. +Define the information needed to create the default admin account. This is the account you will use to log in to Centreon for the first time. The password must comply with the default password security policy: at least 12 characters, lower and upper case letters, numbers and special characters (at least one of these: @$!%*?&). You can change this policy later. ![image](../assets/installation/aadmininfo.png) From 30fcf93265b1dc93b74a68b8a2b4274f187b0af2 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 29 Jul 2026 18:27:00 +0200 Subject: [PATCH 036/179] MON-155363 prerequisites --- .../graph-views/map-web-install.md | 23 +- .../installation/prerequisites.md | 184 +++++++--------- .../version-26.10/reporting/installation.md | 35 ++- .../graph-views/map-web-install.md | 23 +- .../installation/prerequisites.md | 200 +++++++----------- .../version-26.10/reporting/installation.md | 24 ++- 6 files changed, 236 insertions(+), 253 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index 4ead77b1dc55..d6c9bc6c3a78 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -48,7 +48,7 @@ Voir les [prérequis logiciels](../installation/prerequisites.md#caractéristiqu #### Matériel - + | Élément | Valeur | @@ -146,7 +146,26 @@ Votre serveur MAP doit être partitionné de la manière suivante : | vg_data | | Espace libre (non alloué) | 2 Go | - + + +| Élément | Valeur | +| ------- | ------ | +| CPU | 8 vCPU | +| RAM | 16 Go | + +Voici comment votre serveur MAP doit être partitionné : + +| Groupe de volumes (LVM) | Partition | Description | Taille | +| ----------------------- | ------------------- | ----------------------------------- | ------ | +| | /boot | images de boot | 2 Go | +| vg_root | / | racine du système | 20 Go | +| vg_root | swap | swap | 8 Go | +| vg_root | /var/log | contient tous les fichiers de log | 10 Go | +| vg_data | /var/lib/mysql | base de données | 5 Go | +| vg_data | | espace libre (non alloué) | 2 Go | + + + Pour de grosses volumétries de données, contactez votre commercial Centreon. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/prerequisites.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/prerequisites.md index 0cf7b8758dc2..6fa359427254 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/prerequisites.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/prerequisites.md @@ -1,11 +1,12 @@ --- id: prerequisites title: Prérequis +description: "Recommandations de dimensionnement pour votre plateforme Centreon" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Cette page vous donne des recommandations générales afin de déterminer la taille de votre plateforme. +Cette page vous donne des recommandations générales afin de déterminer la taille de votre plateforme. Voir aussi les sections prérequis pour [MAP](../graph-views/map-web-install.md#prérequis) et [MBI](../reporting/installation.md#couche-matériel). ## Architecture @@ -32,6 +33,8 @@ Les données ci-après sont des estimations en fonction des critères suivants : Adaptez les chiffres suivants à vos valeurs réelles. Au cours du temps, vous serez peut-être amenés à ajuster la taille de votre plateforme au fur et à mesure que vous ajoutez plus d'hôtes. +## Architecture et dimensionnement du serveur central et de la base de données + @@ -42,6 +45,8 @@ Serveur central seul : | CPU | 4 vCPU | | RAM | 4 Go | +> Si vous préférez, vous pouvez également superviser vos 500 hôtes à l'aide d'un [collecteur](#dimensionnement-dun-collecteur) rattaché à un serveur central. + Votre serveur central doit être partitionné de la manière suivante : | Groupe de volumes (LVM) | Partition | Description | Taille | @@ -67,9 +72,9 @@ Dans certains cas, il peut être nécessaire de mettre en place une architecture Architecture distribuée : * 1 serveur central -* 1 collecteur par tranche de 500 hôtes +* 1 [collecteur](#dimensionnement-dun-collecteur) par tranche de 500 hôtes -**Serveur central** +### Serveur central | Élément | Valeur | | ----------------------------| --------- | @@ -93,47 +98,15 @@ Votre serveur central doit être partitionné de la manière suivante : > Votre système doit utiliser LVM pour gérer vos partitions. -**Collecteurs** - -* Pour traiter des environnements de test ou des petits périmètres (jusqu'à 2000 services avec des contrôles toutes les 5 minutes et 500 services avec des contrôles toutes les minutes) : - -| Élément | Valeur | -| ----------------------------| --------- | -| CPU (cœur logique à 3Ghz) | 2 vCPU | -| RAM | 2 GB | -| HDD | 40 GB | - -* Pour traiter des environnements de production (jusqu'à 7000 services avec des contrôles toutes les 5 minutes) : - -| Élément | Valeur | -| ----------------------------| --------- | -| CPU (cœur logique à 3Ghz) | 4 vCPU | -| RAM | 4 GB | -| HDD | 40 GB | - -Vos collecteurs doivent être partitionnés de la manière suivante : - -| Groupe de volumes (LVM) | Partition | Description | Taille | -|-------------------------|----------------------------|-------------|----------------------------------------------------------| -| | /boot | images de boot | 1 Go | -| vg_root | / | racine du système | 20 Go | -| vg_root | swap | swap | 4 Go | -| vg_root | /var/log | contient tous les fichiers de log | 10 Go | -| vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | - -> Votre système doit utiliser LVM pour gérer vos partitions. - -> Le nombre de vCPU par collecteur dépend principalement de la complexité des contrôles. Si vous utilisez des connecteurs ou réalisez de nombreux appels vers des applications tierces, ajoutez des vCPU supplémentaires. - Architecture distribuée : * 1 serveur central -* 1 collecteur par tranche de 500 hôtes +* 1 [collecteur](#dimensionnement-dun-collecteur) par tranche de 500 hôtes -**Serveur central** +### Serveur central | Élément | Valeur | | ----------------------------| --------- | @@ -157,38 +130,6 @@ Votre serveur central doit être partitionné de la manière suivante : > Votre système doit utiliser LVM pour gérer vos partitions. -**Collecteurs** - -* Pour traiter des environnements de test ou des petits périmètres (jusqu'à 2000 services avec des contrôles toutes les 5 minutes et 500 services avec des contrôles toutes les minutes) : - -| Élément | Valeur | -| ----------------------------| --------- | -| CPU (cœur logique à 3Ghz) | 2 vCPU | -| RAM | 2 GB | -| HDD | 40 GB | - -* Pour traiter des environnements de production (jusqu'à 7000 services avec des contrôles toutes les 5 minutes) : - -| Élément | Valeur | -| ----------------------------| --------- | -| CPU (cœur logique à 3Ghz) | 4 vCPU | -| RAM | 4 GB | -| HDD | 40 GB | - -Vos collecteurs doivent être partitionnés de la manière suivante : - -| Groupe de volumes (LVM) | Partition | Description | Taille | -|-------------------------|----------------------------|-------------|----------------------------------------------------------| -| | /boot | images de boot | 1 Go | -| vg_root | / | racine du système | 20 Go | -| vg_root | swap | swap | 4 Go | -| vg_root | /var/log | contient tous les fichiers de log | 10 Go | -| vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | - -> Votre système doit utiliser LVM pour gérer vos partitions. - -> Le nombre de vCPU par collecteur dépend principalement de la complexité des contrôles. Si vous utilisez des connecteurs ou réalisez de nombreux appels vers des applications tierces, ajoutez des vCPU supplémentaires. - @@ -196,9 +137,9 @@ Architecture distribuée : * 1 serveur central sans base de données * 1 serveur de base de données -* 1 collecteur par tranche de 500 hôtes +* 1 [collecteur](#dimensionnement-dun-collecteur) par tranche de 500 hôtes -**Serveur central** +### Serveur central | Élément | Valeur | | ----------------------------| --------- | @@ -218,7 +159,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
  • taille de la partition /var/lib/mysql * 0,6
  • valable pour 1 sauvegarde complète et 6 partielles
  • attention, cela reste une estimation et n'exclut pas un contrôle humain
| -**Serveur de bases de données** +### Serveur de bases de données | Élément | Valeur | | ----------------------------| --------- | @@ -238,90 +179,117 @@ Votre serveur doit être partitionné de la manière suivante : > Votre système doit utiliser LVM pour gérer vos partitions. -**Collecteurs** + + -* Pour traiter des environnements de test ou des petits périmètres (jusqu'à 2000 services avec des contrôles toutes les 5 minutes et 500 services avec des contrôles toutes les minutes) : +Architecture distribuée : + +* 1 serveur central sans base de données +* 1 serveur de base de données +* 1 [collecteur](#dimensionnement-dun-collecteur) par tranche de 500 hôtes + +### Serveur central | Élément | Valeur | | ----------------------------| --------- | -| CPU (cœur logique à 3Ghz) | 2 vCPU | -| RAM | 2 GB | -| HDD | 40 GB | +| CPU (cœur logique à 3Ghz) | 8 vCPU | +| RAM | 8 Go | -* Pour traiter des environnements de production (jusqu'à 7000 services avec des contrôles toutes les 5 minutes) : +Votre serveur central doit être partitionné de la manière suivante : + +| Groupe de volumes (LVM) | Partition | Description | Taille | +|---------| ---------------------------|-------------|----------------------------------------------------------| +| | /boot | images de boot | 1 Go | +| vg_root | / | racine du système | 20 Go | +| vg_root | swap | swap | 4 Go | +| vg_root | /var/log | contient tous les fichiers de log | 10 Go | +| vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 677 Go | +| vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | +| vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | +| vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
  • taille de la partition /var/lib/mysql * 0,6
  • valable pour 1 sauvegarde complète et 6 partielles
  • attention, cela reste une estimation et n'exclut pas un contrôle humain
| + +> Votre système doit utiliser LVM pour gérer vos partitions. + +### Serveur de bases de données | Élément | Valeur | | ----------------------------| --------- | -| CPU (cœur logique à 3Ghz) | 4 vCPU | -| RAM | 4 GB | -| HDD | 40 GB | +| CPU | 8 vCPU | +| RAM | 8 Go | -Vos collecteurs doivent être partitionnés de la manière suivante : +Votre serveur doit être partitionné de la manière suivante : -| Groupe de volumes (LVM) | Partition | Description | Taille | -|-------------------------|----------------------------|-------------|----------------------------------------------------------| -| | /boot | images de boot | 1 Go | -| vg_root | / | racine du système | 20 Go | -| vg_root | swap | swap | 4 Go | -| vg_root | /var/log | contient tous les fichiers de log | 10 Go | -| vg_data| /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | +| Groupe de volumes (LVM) | Partition | Description | Taille | +|---------| ---------------------------|-------------|----------------------------------------------------------| +| | /boot | images de boot | 1 Go | +| vg_root | / | racine du système | 20 Go | +| vg_root | swap | swap | 4 Go | +| vg_root | /var/log | contient tous les fichiers de log | 10 Go | +| vg_data | /var/lib/mysql | base de données | 2257 Go | +| vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. -> Le nombre de vCPU par collecteur dépend principalement de la complexité des contrôles. Si vous utilisez des connecteurs ou réalisez de nombreux appels vers des applications tierces, ajoutez des vCPU supplémentaires. - - + Architecture distribuée : * 1 serveur central sans base de données * 1 serveur de base de données -* 1 collecteur par tranche de 500 hôtes +* 1 [collecteur](#dimensionnement-dun-collecteur) par tranche de 500 hôtes -**Serveur central** +### Serveur central | Élément | Valeur | | ----------------------------| --------- | | CPU (cœur logique à 3Ghz) | 8 vCPU | -| RAM | 8 Go | +| RAM | 16 Go | Votre serveur central doit être partitionné de la manière suivante : | Groupe de volumes (LVM) | Partition | Description | Taille | |---------| ---------------------------|-------------|----------------------------------------------------------| -| | /boot | images de boot | 1 Go | +| | /boot | images de boot | 2 Go | | vg_root | / | racine du système | 20 Go | -| vg_root | swap | swap | 4 Go | +| vg_root | swap | swap | 8 Go | | vg_root | /var/log | contient tous les fichiers de log | 10 Go | -| vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 677 Go | +| vg_data | /var/lib/centreon | contient en majorité des fichiers RRD | 1355 Go | | vg_data | /var/lib/centreon-broker | contient les fichiers de rétention de Broker | 50 Go | | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
  • taille de la partition /var/lib/mysql * 0,6
  • valable pour 1 sauvegarde complète et 6 partielles
  • attention, cela reste une estimation et n'exclut pas un contrôle humain
| > Votre système doit utiliser LVM pour gérer vos partitions. -**Serveur de bases de données** +### Serveur de bases de données | Élément | Valeur | | ----------------------------| --------- | | CPU | 8 vCPU | -| RAM | 8 Go | +| RAM | 16 Go | Votre serveur doit être partitionné de la manière suivante : | Groupe de volumes (LVM) | Partition | Description | Taille | |---------| ---------------------------|-------------|----------------------------------------------------------| -| | /boot | images de boot | 1 Go | +| | /boot | images de boot | 2 Go | | vg_root | / | racine du système | 20 Go | -| vg_root | swap | swap | 4 Go | +| vg_root | swap | swap | 8 Go | | vg_root | /var/log | contient tous les fichiers de log | 10 Go | -| vg_data | /var/lib/mysql | base de données | 2257 Go | +| vg_data | /var/lib/mysql | base de données | 4500 Go | | vg_data | | Espace libre (non alloué) | 5 Go | > Votre système doit utiliser LVM pour gérer vos partitions. -**Collecteurs** + + + +Pour de grosses volumétries de données, contactez votre commercial Centreon. + + + + +## Dimensionnement d'un collecteur * Pour traiter des environnements de test ou des petits périmètres (jusqu'à 2000 services avec des contrôles toutes les 5 minutes et 500 services avec des contrôles toutes les minutes) : @@ -353,14 +321,6 @@ Vos collecteurs doivent être partitionnés de la manière suivante : > Le nombre de vCPU par collecteur dépend principalement de la complexité des contrôles. Si vous utilisez des connecteurs ou réalisez de nombreux appels vers des applications tierces, ajoutez des vCPU supplémentaires. - - - -Pour de grosses volumétries de données, contactez votre commercial Centreon. - - - - ## Flux réseau Si vous avez des pare-feu ou des équipements de sécurité en place, vérifiez le [tableau des flux réseau](./technical.md#tableaux-des-flux-réseau). diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/installation.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/installation.md index 5f5334892716..fff0fa2f76a7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/installation.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/installation.md @@ -1,6 +1,7 @@ --- id: installation title: Installer MBI +description: "Installer et configurer le serveur de reporting et l'interface de Centreon MBI" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; @@ -53,14 +54,6 @@ entre le serveur BI dédié, le serveur Centreon et les bases de données : | CBIS | Serveur de reporting | Serveur Centreon | 80 | HTTP* | | CBIS | Centreon | Serveur de reporting | 1234 | TCP | | Widgets | Serveur central Centreon | Serveur de reporting | 3306 | TCP | -======= -| **Application** | **Source** | **Destination** | **Port** | **Protocole** | **Objet** | -|-----------------|--------------------------|--------------------------------------|--------------|--------------------|------------------------------------------------------------| -| ETL/CBIS | Reporting server | Centreon database server | 3306 | TCP | Récupérer la configuration et d'autres données de Centreon | -| SSH | Reporting server | Centreon Server | 22 | TCP | Envoyer les rapports générés au serveur central | -| CBIS | Reporting server | Centreon Server | 80/443 | HTTP*/HTTPS | Authentification et récupération des données | -| CBIS | Centreon | Reporting server | 1234 | TCP | Utilisé pour contacter CBIS afin de créer des jobs | -| Widgets | Centreon central server | Reporting server | 3306 | TCP | Récupération des données agrégées pour les widgets | \**Uniquement requis pour les rapports Host-Graph-v2 et Hostgroup-Graph-v2 qui utilisent l'API Centreon pour générer des graphiques.* @@ -152,7 +145,7 @@ Voir les [prérequis logiciels](../installation/prerequisites.md#caractéristiqu #### Couche Matériel - + | Élément | Valeur | @@ -253,7 +246,27 @@ Votre serveur MBI doit être partitionné de la manière suivante : | vg_data | | Espace libre (non alloué) | 5 Go | - + + +| Élément | Valeur | +| ------- | ------- | +| CPU | 16 vCPU | +| RAM | 64 Go | + +Voici comment votre serveur MBI doit être partitionné : + +| Groupe de volumes (LVM) | Partition | Description | Taille | +| ----------------------- | ------------------- | ----------------------------------- | -------- | +| | /boot | images de boot | 2 Go | +| vg_root | / | racine du système | 20 Go | +| vg_root | swap | swap | 8 Go | +| vg_root | /var/log | contient tous les fichiers de log | 10 Go | +| vg_data | /var/lib/mysql | base de données | 8 462 Go | +| vg_data | /var/backup | répertoire de sauvegarde | 10 Go | +| vg_data | | espace libre (non alloué) | 5 Go | + + + Pour de grosses volumétries de données, contactez votre commercial Centreon. @@ -1233,7 +1246,7 @@ suivantes : | Une base de données MariaDB dédiée au reporting a été mise en place. | Oui. Vous devez avoir un serveur de reporting dédié. | | Espace de stockage des fichiers temporaires sur le serveur de reporting * | Dossier sur le serveur de reporting dans lequel les dumps de données seront positionnés | | Type de statistiques à traiter | Sélectionnez « Disponibilité uniquement » si vous utilisez uniquement les rapports de disponibilité. Sélectionnez « Performance et capacité uniquement» si vous souhaitez utiliser uniquement les rapports de capacité et de performance. Sélectionnez «Tous» afin de calculer les statistiques pour les deux types de rapports. | -| Activer le stockage des tables temporaires en mémoire (uniquement si la mémoire physique allouée au serveur de reporting est suffisante) | Crée des tables temporaires en utilisant de la RAM plutôt que de les créer sur disque. Non recommandé si vous disposez de bases de données avec moins de 64Go de RAM. | +| Activer le stockage des tables temporaires en mémoire (uniquement si la mémoire physique allouée au serveur de reporting est suffisante) | Crée des tables temporaires en utilisant de la RAM plutôt que de les créer sur disque. Non recommandé si vous disposez de bases de données avec moins de 64Go de RAM. | | **Sélection du périmètre du reporting** | | | Groupes d'hôtes | Sélectionnez les groupes d’hôtes pour lesquels vous souhaitez conserver les statistiques. | | Catégories d'hôtes | Sélectionnez les catégories d’hôtes pour lesquels vous souhaitez conserver les statistiques. | diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index c58d6a69b3fd..234bba24e199 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -50,7 +50,7 @@ See the [software requirements](../installation/prerequisites.md#characteristics #### Hardware - + | Element | Value | @@ -148,7 +148,26 @@ This is how your MAP server should be partitioned: | vg_data | | Free space (unallocated) | 2 GB | - + + +| Element | Value | +| ----------------------------| --------- | +| CPU | 8 vCPU | +| RAM | 16 GB | + +This is how your MAP server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +|-| ----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 2 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 8 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/mysql | database | 5 GB | +| vg_data | | Free space (unallocated) | 2 GB | + + + For very large amounts of data, contact your sales representative. diff --git a/versioned_docs/version-26.10/installation/prerequisites.md b/versioned_docs/version-26.10/installation/prerequisites.md index 3ba10738d781..6cd1fed50b6d 100644 --- a/versioned_docs/version-26.10/installation/prerequisites.md +++ b/versioned_docs/version-26.10/installation/prerequisites.md @@ -5,7 +5,7 @@ title: Prerequisites import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This topic gives you broad guidelines to determine the size of your platform. +This topic gives you broad guidelines to determine the size of your platform. See also the prerequisites sections for [MAP](../graph-views/map-web-install.md#prerequisites) and [MBI](../reporting/installation.md#hardware-layer). ## Architecture @@ -32,6 +32,8 @@ The following data is meant for: You need to adapt the following figures to your actual values. Bear in mind that you may need to adjust the size of your platform as you add more hosts over time. +## Architecture and central/database sizing + @@ -42,6 +44,8 @@ Standalone central server: | CPU | 4 vCPU | | RAM | 4 GB | +> If you prefer, you can also monitor your 500 hosts using a [poller](#poller-sizing) attached to a central. + This is how your central server should be partitioned: | Volume group (LVM) | File system | Description | Size | @@ -54,7 +58,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-broker | contains broker retention files | 5 GB | | vg_data | /var/lib/centreon-engine | contains engine retention files | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 106 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0,6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0.6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -67,9 +71,9 @@ In some cases, you may want to set up a distributed architecture, even for fewer Distributed architecture: * 1 central server -* 1 poller for every 500 hosts +* 1 [poller](#poller-sizing) for every 500 hosts -**Central server** +### Central server | Element | Value | | ----------------------------| --------- | @@ -85,10 +89,10 @@ This is how your central server should be partitioned: | vg_root | swap | swap | 4 GB | | vg_root | /var/log | contains all log files | 10 GB | | vg_data | /var/lib/centreon | contains mostly RRD files | 68 GB | -| vg_data | /var/lib/centreon-broker | contains retention files | 10 GB | +| vg_data | /var/lib/centreon-broker | contains Broker retention files | 10 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 213 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0,6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0.6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -96,49 +100,15 @@ This is how your central server should be partitioned: > At least 1 GB of non-allocated free space must be available for the **volume group** containing **/var/lib/mysql**, > if you wish to use **snapshot LVM** as a backup method. -**Pollers** - -* To handle testing or small environments (up to 2000 services with checks every 5 minutes, or up to 500 services with checks every minute): - -| Element | Value | -| ----------------------------| --------- | -| CPU (logical core at 3 GHz) | 2 vCPU | -| RAM | 2 GB | -| HDD | 40 GB | - -* To handle production environments (up to 7000 services with checks every 5 minutes): - -| Element | Value | -| ----------------------------| --------- | -| CPU (logical core at 3 GHz) | 4 vCPU | -| RAM | 4 GB | -| HDD | 40 GB | - -This is how the pollers should be partitioned: - -| Volume group (LVM) | File system | Description | Size | -|-| ----------------------------|-------------|----------------------------------------------------------| -| | /boot | boot images | 1 GB | -| vg_root | / | system root | 20 GB | -| vg_root | swap | swap | 4 GB | -| vg_root | /var/log | contains all log files | 10 GB | -| vg_data | /var/lib/centreon-engine | | 5 GB | - -> Your system must use LVM to manage the file system. - -> The number of -> vCPU depends of the complexity of the checks. If you use connectors or perform a large number of system/third-party -> binary calls, you should add more vCPU. - Distributed architecture: * 1 central server -* 1 poller for every 500 hosts +* 1 [poller](#poller-sizing) for every 500 hosts -**Central server** +### Central server | Element | Value | | ----------------------------| --------- | @@ -154,10 +124,10 @@ This is how your central server should be partitioned: | vg_root | swap | swap | 4 GB | | vg_root | /var/log | contains all log files | 10 GB | | vg_data | /var/lib/centreon | contains mostly RRD files | 169 GB | -| vg_data | /var/lib/centreon-broker | contains retention files | 25 GB | +| vg_data | /var/lib/centreon-broker | contains Broker retention files | 25 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 538 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0,6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0.6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -165,40 +135,6 @@ This is how your central server should be partitioned: > At least 1 GB of non-allocated free space must be available for the **volume group** containing **/var/lib/mysql**, > if you wish to use **snapshot LVM** as a backup method. -**Pollers** - -* To handle testing or small environments (up to 2000 services with checks every 5 minutes, or up to 500 services with checks every minute): - -| Element | Value | -| ----------------------------| --------- | -| CPU (logical core at 3 GHz) | 2 vCPU | -| RAM | 2 GB | -| HDD | 40 GB | - -* To handle production environments (up to 7000 services with checks every 5 minutes): - -| Element | Value | -| ----------------------------| --------- | -| CPU (logical core at 3 GHz) | 4 vCPU | -| RAM | 4 GB | -| HDD | 40 GB | - -This is how the pollers should be partitioned: - -| Volume group (LVM) | File system | Description | Size | -|-| ----------------------------|-------------|----------------------------------------------------------| -| | /boot | boot images | 1 GB | -| vg_root | / | system root | 20 GB | -| vg_root | swap | swap | 4 GB | -| vg_root | /var/log | contains all log files | 10 GB | -| vg_data | /var/lib/centreon-engine | | 5 GB | - -> Your system must use LVM to manage the file system. - -> The number of -> vCPU depends of the complexity of the checks. If you use connectors or perform a large number of system/third-party -> binary calls, you should add more vCPU. - @@ -206,9 +142,9 @@ Distributed architecture: * 1 central server without a database * 1 database server -* 1 poller for every 500 hosts +* 1 [poller](#poller-sizing) for every 500 hosts -**Central server** +### Central server | Element | Value | | ----------------------------| --------- | @@ -224,11 +160,11 @@ This is how your central server should be partitioned: | vg_root | swap | swap | 4 GB | | vg_root | /var/log | contains all log files | 10 GB | | vg_data | /var/lib/centreon | contains mostly RRD files | 339 GB | -| vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | +| vg_data | /var/lib/centreon-broker | contains Broker retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0,6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0.6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| -**Database server** +### Database server | Element | Value | | ----------------------------| --------- | @@ -244,7 +180,6 @@ This is how the database server should be partitioned: | vg_root | swap | swap | 4 GB | | vg_root | /var/log | contains all log files | 10 GB | | vg_data | /var/lib/mysql | database | 1094 GB | - | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -252,85 +187,102 @@ This is how the database server should be partitioned: > At least 1 GB of non-allocated free space must be available for the **volume group** containing **/var/lib/mysql**, > if you wish to use **snapshot LVM** as a backup method. -**Pollers** + + +Distributed architecture: -* To handle testing or small environments (up to 2000 services with checks every 5 minutes, or up to 500 services with checks every minute): +* 1 central server without a database +* 1 database server +* 1 [poller](#poller-sizing) for every 500 hosts + +### Central server | Element | Value | | ----------------------------| --------- | -| CPU (logical core at 3 GHz) | 2 vCPU | -| RAM | 2 GB | -| HDD | 40 GB | +| CPU | 8 vCPU | +| RAM | 8 GB | -* To handle production environments (up to 7000 services with checks every 5 minutes): +This is how your central server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +| - |----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 1 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 4 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/centreon | contains mostly RRD files | 677 GB | +| vg_data | /var/lib/centreon-broker | contains broker retention files | 50 GB | +| vg_data | /var/lib/centreon-engine | | 5 GB | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0.6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| + +### Database server | Element | Value | | ----------------------------| --------- | -| CPU (logical core at 3 GHz) | 4 vCPU | -| RAM | 4 GB | -| HDD | 40 GB | +| CPU | 8 vCPU | +| RAM | 8 GB | -This is how the pollers should be partitioned: +This is how the database server should be partitioned: | Volume group (LVM) | File system | Description | Size | -|-| ----------------------------|-------------|----------------------------------------------------------| +| - |----------------------------|-------------|----------------------------------------------------------| | | /boot | boot images | 1 GB | -| vg_root | / | system root | 20 GB | +| vg_root | / | system root | 20 GB | | vg_root | swap | swap | 4 GB | | vg_root | /var/log | contains all log files | 10 GB | -| vg_data | /var/lib/centreon-engine | | 5 GB | +| vg_data | /var/lib/mysql | database | 2257 GB | +| vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. -> The number of -> vCPU depends of the complexity of the checks. If you use connectors or perform a large number of system/third-party -> binary calls, you should add more vCPU. +> At least 1 GB of non-allocated free space must be available for the **volume group** containing **/var/lib/mysql**, +> if you wish to use **snapshot LVM** as a backup method. - + Distributed architecture: * 1 central server without a database * 1 database server -* 1 poller for every 500 hosts +* 1 [poller](#poller-sizing) for every 500 hosts -**Central server** +### Central server | Element | Value | | ----------------------------| --------- | | CPU | 8 vCPU | -| RAM | 8 GB | +| RAM | 16 GB | This is how your central server should be partitioned: | Volume group (LVM) | File system | Description | Size | | - |----------------------------|-------------|----------------------------------------------------------| -| | /boot | boot images | 1 GB | +| | /boot | boot images | 2 GB | | vg_root | / | system root | 20 GB | -| vg_root | swap | swap | 4 GB | +| vg_root | swap | swap | 8 GB | | vg_root | /var/log | contains all log files | 10 GB | -| vg_data | /var/lib/centreon | contains mostly RRD files | 677 GB | -| vg_data | /var/lib/centreon-broker | contains retention files | 50 GB | +| vg_data | /var/lib/centreon | contains mostly RRD files | 1355 GB | +| vg_data | /var/lib/centreon-broker | contains broker retention files | 50 GB | | vg_data | /var/lib/centreon-engine | | 5 GB | -| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0,6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0.6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| -**Database server** +### Database server | Element | Value | | ----------------------------| --------- | | CPU | 8 vCPU | -| RAM | 8 GB | +| RAM | 16 GB | This is how the database server should be partitioned: | Volume group (LVM) | File system | Description | Size | | - |----------------------------|-------------|----------------------------------------------------------| -| | /boot | boot images | 1 GB | +| | /boot | boot images | 2 GB | | vg_root | / | system root | 20 GB | -| vg_root | swap | swap | 4 GB | +| vg_root | swap | swap | 8 GB | | vg_root | /var/log | contains all log files | 10 GB | -| vg_data | /var/lib/mysql | database | 2257 GB | +| vg_data | /var/lib/mysql | database | 4500 GB | | vg_data | | Free space (unallocated) | 5 GB | > Your system must use LVM to manage the file system. @@ -338,7 +290,15 @@ This is how the database server should be partitioned: > At least 1 GB of non-allocated free space must be available for the **volume group** containing **/var/lib/mysql**, > if you wish to use **snapshot LVM** as a backup method. -**Pollers** + + + +For very large amounts of data, contact your sales representative. + + + + +## Poller sizing * To handle testing or small environments (up to 2000 services with checks every 5 minutes, or up to 500 services with checks every minute): @@ -369,17 +329,9 @@ This is how the pollers should be partitioned: > Your system must use LVM to manage the file system. > The number of -> vCPU depends of the complexity of the checks. If you use connectors or perform a large number of system/third-party +> vCPU depends on the complexity of the checks. If you use connectors or perform a large number of system/third-party > binary calls, you should add more vCPU. - - - -For very large amounts of data, contact your sales representative. - - - - ## Network flows If you have firewalls or security resources in place, check the [table of network flows](./technical.md#tables-of-network-flows). diff --git a/versioned_docs/version-26.10/reporting/installation.md b/versioned_docs/version-26.10/reporting/installation.md index 5ebcf97fb43a..085b5e33101c 100644 --- a/versioned_docs/version-26.10/reporting/installation.md +++ b/versioned_docs/version-26.10/reporting/installation.md @@ -146,7 +146,7 @@ considerations. #### Hardware layer - + | Element | Value | @@ -247,7 +247,27 @@ This is how your MBI server should be partitioned: | vg_data | | Free space (unallocated) | 5 GB | - + + +| Element | Value | +| ----------------------------| --------- | +| CPU | 16 vCPU | +| RAM | 64 GB | + +This is how your MBI server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +|-| ----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 2 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 8 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/mysql | database | 8462 GB | +| vg_data | /var/backup | backup directory | 10 GB | +| vg_data | | Free space (unallocated) | 5 GB | + + + For very large amounts of data, contact your sales representative. From 9fbd27cb3b11270c2bbf622fafe912c01912113f Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 31 Jul 2026 16:24:43 +0200 Subject: [PATCH 037/179] Updates --- .../graph-views/map-web-install.md | 2 +- .../installation/prerequisites.md | 16 ++++----- .../graph-views/map-web-install.md | 2 +- .../installation/_database-local-install.mdx | 2 +- .../installation/_database-repository.mdx | 15 ++++++--- .../using-packages.md | 33 ++++++------------- .../using-containers.md | 7 ++++ .../installation/prerequisites.md | 16 ++++----- .../version-26.10-sidebars.json | 4 +++ 9 files changed, 50 insertions(+), 47 deletions(-) create mode 100644 versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers.md diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index 29064ce7cd35..c71b719f138e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -154,7 +154,7 @@ Votre serveur MAP doit être partitionné de la manière suivante : | Élément | Valeur | | ------- | ------ | | CPU | 8 vCPU | -| RAM | 16 Go | +| RAM | 18 Go | Voici comment votre serveur MAP doit être partitionné : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/prerequisites.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/prerequisites.md index 6fa359427254..1166da769a45 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/prerequisites.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/prerequisites.md @@ -74,7 +74,7 @@ Architecture distribuée : * 1 serveur central * 1 [collecteur](#dimensionnement-dun-collecteur) par tranche de 500 hôtes -### Serveur central +#### Serveur central | Élément | Valeur | | ----------------------------| --------- | @@ -106,7 +106,7 @@ Architecture distribuée : * 1 serveur central * 1 [collecteur](#dimensionnement-dun-collecteur) par tranche de 500 hôtes -### Serveur central +#### Serveur central | Élément | Valeur | | ----------------------------| --------- | @@ -139,7 +139,7 @@ Architecture distribuée : * 1 serveur de base de données * 1 [collecteur](#dimensionnement-dun-collecteur) par tranche de 500 hôtes -### Serveur central +#### Serveur central | Élément | Valeur | | ----------------------------| --------- | @@ -159,7 +159,7 @@ Votre serveur central doit être partitionné de la manière suivante : | vg_data | /var/lib/centreon-engine | contient les fichiers de rétention d'Engine | 5 Go | | vg_data | /var/cache/centreon/backup | répertoire de sauvegarde | 10 Go
Si vous utilisez la fonctionnalité de sauvegarde, prévoyez les caractéristiques suivantes :
  • taille de la partition /var/lib/mysql * 0,6
  • valable pour 1 sauvegarde complète et 6 partielles
  • attention, cela reste une estimation et n'exclut pas un contrôle humain
| -### Serveur de bases de données +#### Serveur de bases de données | Élément | Valeur | | ----------------------------| --------- | @@ -188,7 +188,7 @@ Architecture distribuée : * 1 serveur de base de données * 1 [collecteur](#dimensionnement-dun-collecteur) par tranche de 500 hôtes -### Serveur central +#### Serveur central | Élément | Valeur | | ----------------------------| --------- | @@ -210,7 +210,7 @@ Votre serveur central doit être partitionné de la manière suivante : > Votre système doit utiliser LVM pour gérer vos partitions. -### Serveur de bases de données +#### Serveur de bases de données | Élément | Valeur | | ----------------------------| --------- | @@ -239,7 +239,7 @@ Architecture distribuée : * 1 serveur de base de données * 1 [collecteur](#dimensionnement-dun-collecteur) par tranche de 500 hôtes -### Serveur central +#### Serveur central | Élément | Valeur | | ----------------------------| --------- | @@ -261,7 +261,7 @@ Votre serveur central doit être partitionné de la manière suivante : > Votre système doit utiliser LVM pour gérer vos partitions. -### Serveur de bases de données +#### Serveur de bases de données | Élément | Valeur | | ----------------------------| --------- | diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index 68c1212e2fd2..e32aadd34248 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -156,7 +156,7 @@ This is how your MAP server should be partitioned: | Element | Value | | ----------------------------| --------- | | CPU | 8 vCPU | -| RAM | 16 GB | +| RAM | 18 GB | This is how your MAP server should be partitioned: diff --git a/versioned_docs/version-26.10/installation/_database-local-install.mdx b/versioned_docs/version-26.10/installation/_database-local-install.mdx index 98595f2f182e..0ba8481fa8a7 100644 --- a/versioned_docs/version-26.10/installation/_database-local-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-local-install.mdx @@ -65,7 +65,7 @@ systemctl restart mysqld ``` - + ```shell apt update diff --git a/versioned_docs/version-26.10/installation/_database-repository.mdx b/versioned_docs/version-26.10/installation/_database-repository.mdx index 7bf98ff19e35..9b7b5bdb7250 100644 --- a/versioned_docs/version-26.10/installation/_database-repository.mdx +++ b/versioned_docs/version-26.10/installation/_database-repository.mdx @@ -33,8 +33,6 @@ curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- - -For new installations, the recommended version of MySQL is 8.4. - @@ -51,12 +49,19 @@ dnf install https://dev.mysql.com/get/mysql84-community-release-el9-1.noarch.rpm ``` - + ```shell -wget https://dev.mysql.com/get/mysql-apt-config_0.8.36-1_all.deb -sudo dpkg -i mysql-apt-config_0.8.36-1_all.deb +mysql_apt_config="mysql-apt-config_0.8.34-1_all.deb" +curl -fJLO "https://dev.mysql.com/get/$mysql_apt_config" +echo "mysql-apt-config mysql-apt-config/select-server select mysql-8.4-lts" | debconf-set-selections +export DEBIAN_FRONTEND="noninteractive" +apt install -y "./$mysql_apt_config" +mysql_keyring=$(grep -ohm1 'signed-by=[^] ]*' /etc/apt/sources.list.d/mysql.list 2>/dev/null | cut -d= -f2) +[ -z "$mysql_keyring" ] && mysql_keyring=/etc/apt/trusted.gpg.d/mysql.gpg +( set -o pipefail; curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2025 | gpg --dearmor --yes -o "$mysql_keyring" ) apt update +apt install -y mysql-server mysql-common ``` diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index 497c0967d35b..ff2fe78edff7 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -13,7 +13,7 @@ import DatabaseEnableRestart from '../_database-enable-restart.mdx'; Centreon provides RPM and DEB packages for its products through the Centreon Open Source version available free of charge in our repository. -These packages can be installed on Alma/RHEL/Oracle Linux 8 and 9 and on Debian 12. +These packages can be installed on Alma/RHEL/Oracle Linux 9 and 10 and on Debian 13. You must run the installation procedure as a privileged user. @@ -25,7 +25,7 @@ After installing your server, update your operating system using the following command: - + ```shell dnf update @@ -73,7 +73,7 @@ locale -a ``` - + ```shell apt update && apt upgrade @@ -149,9 +149,9 @@ Disabled > **Note that this deactivation should be temporary.** SELinux should be [reenabled after installation](../../administration/secure-platform.md#activate-selinux) for security reasons. - + -SELinux is not installed on Debian 12, continue. +SELinux is not installed on Debian 13, continue. @@ -304,29 +304,14 @@ dnf module install php:8.2 ``` - + #### Install dependencies Install the following dependencies: ```shell -apt update && apt install lsb-release ca-certificates apt-transport-https software-properties-common wget gnupg2 curl -``` - -#### Add Sury APT repository for PHP 8.2 - -To install the Sury repository, execute the following command: - -```shell -echo "deb https://packages.sury.org/php/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/sury-php.list -``` - -Then import the repository key: - -```shell -wget -O- https://packages.sury.org/php/apt.gpg | gpg --dearmor | tee /etc/apt/trusted.gpg.d/php.gpg > /dev/null 2>&1 -apt update +apt update && apt install -y lsb-release ca-certificates apt-transport-https wget gnupg2 curl sudo ``` @@ -361,7 +346,7 @@ dnf update ``` - + To install the Centreon repository, execute the following command: @@ -380,6 +365,8 @@ apt update +## Step 2: HTTPS? + ## Step 2: Installation This section describes how to install a Centreon central server. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers.md new file mode 100644 index 000000000000..01a7e5998f86 --- /dev/null +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers.md @@ -0,0 +1,7 @@ +--- +id: using-containers +title: Installing a poller on a container +description: "Install a Centreon poller using docker-compose" +--- + +L'utilitaire docker-compose doit être disponible sur le système de conteneurisation où vous voulez installer le collecteur. \ No newline at end of file diff --git a/versioned_docs/version-26.10/installation/prerequisites.md b/versioned_docs/version-26.10/installation/prerequisites.md index 6712271bfa5f..99df65efc99a 100644 --- a/versioned_docs/version-26.10/installation/prerequisites.md +++ b/versioned_docs/version-26.10/installation/prerequisites.md @@ -74,7 +74,7 @@ Distributed architecture: * 1 central server * 1 [poller](#poller-sizing) for every 500 hosts -### Central server +#### Central server | Element | Value | | ----------------------------| --------- | @@ -109,7 +109,7 @@ Distributed architecture: * 1 central server * 1 [poller](#poller-sizing) for every 500 hosts -### Central server +#### Central server | Element | Value | | ----------------------------| --------- | @@ -145,7 +145,7 @@ Distributed architecture: * 1 database server * 1 [poller](#poller-sizing) for every 500 hosts -### Central server +#### Central server | Element | Value | | ----------------------------| --------- | @@ -165,7 +165,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0.6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| -### Database server +#### Database server | Element | Value | | ----------------------------| --------- | @@ -196,7 +196,7 @@ Distributed architecture: * 1 database server * 1 [poller](#poller-sizing) for every 500 hosts -### Central server +#### Central server | Element | Value | | ----------------------------| --------- | @@ -216,7 +216,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0.6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| -### Database server +#### Database server | Element | Value | | ----------------------------| --------- | @@ -248,7 +248,7 @@ Distributed architecture: * 1 database server * 1 [poller](#poller-sizing) for every 500 hosts -### Central server +#### Central server | Element | Value | | ----------------------------| --------- | @@ -268,7 +268,7 @@ This is how your central server should be partitioned: | vg_data | /var/lib/centreon-engine | | 5 GB | | vg_data | /var/cache/centreon/backup | backup directory | 10 GB
If you perform backups, use the following characteristics:
  • size of the /var/lib/mysql partition * 0.6
  • this size is meant for 1 full backup and 6 partial ones
  • this is only an estimate, size should be checked manually
| -### Database server +#### Database server | Element | Value | | ----------------------------| --------- | diff --git a/versioned_sidebars/version-26.10-sidebars.json b/versioned_sidebars/version-26.10-sidebars.json index f58e48b2d8ee..d3bc2c30197f 100644 --- a/versioned_sidebars/version-26.10-sidebars.json +++ b/versioned_sidebars/version-26.10-sidebars.json @@ -153,6 +153,10 @@ "type": "doc", "id": "installation/installation-of-a-poller/using-packages" }, + { + "type": "doc", + "id": "installation/installation-of-a-poller/using-containers" + }, { "type": "doc", "id": "installation/installation-of-a-poller/unattended-install-poller" From 52d71a0be31d6640688b151dd57cbead5371e36e Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 31 Jul 2026 16:46:15 +0200 Subject: [PATCH 038/179] Fix tabs --- .../using-packages.md | 110 +----------------- 1 file changed, 1 insertion(+), 109 deletions(-) diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index ff2fe78edff7..7c5c18e9e149 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -49,7 +49,7 @@ locale -a ``` - + ```shell dnf update @@ -89,36 +89,6 @@ apt update && apt upgrade ### Disable SELinux - - -During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace -**enforcing** with **disabled**. You can also run the following command: - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Reboot your operating system to apply the change. - -```shell -reboot -``` - -After system startup, perform a quick check of the SELinux status: - -```shell -getenforce -``` - -You should have this result: - -```shell -Disabled -``` - -> **Note that this deactivation should be temporary.** SELinux should be [reenabled after installation](../../administration/secure-platform.md#activate-selinux) for security reasons. - - During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace @@ -169,75 +139,6 @@ systemctl disable firewalld ### Install the repositories - - - -Run the following commands: - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -dnf config-manager --set-enabled 'powertools' -``` - -Enable PHP 8.2 using the following commands: - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -#### CodeReady Builder repository - -To install Centreon you will need to install the **CodeReady Builder** repository. - -Run the following commands: - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` - -If your server is a Cloud RHEL instance, you will have to execute the following command: - -```shell -dnf config-manager --set-enabled codeready-builder-for-rhel-8-rhui-rpms -``` - -Enable PHP 8.2 using the following commands: - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -#### CodeReady Builder repository - -To install Centreon you will need to install the **CodeReady Builder** repository. - -Run the following commands: - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -dnf config-manager --set-enabled ol8_codeready_builder -``` - -Enable PHP 8.2 using the following commands: - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - To install Centreon you will need to install the **CodeReady Builder** repository. @@ -328,15 +229,6 @@ To install Centreon software, you should first install the Centreon repository. Install the Centreon repository using this command: - - -```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -dnf clean all --enablerepo=* -dnf update -``` - - ```shell From 563a32b4981caadfd0e7c14521014f1de496a8c9 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 20 Aug 2026 17:12:59 +0200 Subject: [PATCH 039/179] TLS part of installation procedure --- .../installation/_database-configuration.mdx | 2 +- .../installation/_database-enable-restart.mdx | 11 +- .../installation/_database-local-install.mdx | 34 +- .../installation/_database-remote-install.mdx | 46 +- .../installation/_database-repository.mdx | 38 +- .../installation/_database-tls-conf.mdx | 620 ++++++++++++++++++ .../using-packages.md | 395 +++++++++-- .../upgrade/_upgrade-central.mdx | 10 +- 8 files changed, 1033 insertions(+), 123 deletions(-) create mode 100644 versioned_docs/version-26.10/installation/_database-tls-conf.mdx diff --git a/versioned_docs/version-26.10/installation/_database-configuration.mdx b/versioned_docs/version-26.10/installation/_database-configuration.mdx index 1738750757fd..cd9fcf874009 100644 --- a/versioned_docs/version-26.10/installation/_database-configuration.mdx +++ b/versioned_docs/version-26.10/installation/_database-configuration.mdx @@ -141,7 +141,7 @@ We recommend you consult your database administrator for a configuration that fi Please note that the following configuration is only an example for an 8 GB of RAM infrastructure. It is up to each user to adapt the database configuration to fit their needs. We recommend you consult your database administrator for a configuration that fits your needs. - + > ```shell diff --git a/versioned_docs/version-26.10/installation/_database-enable-restart.mdx b/versioned_docs/version-26.10/installation/_database-enable-restart.mdx index 6fa5e6da5c31..e18ae5333ae3 100644 --- a/versioned_docs/version-26.10/installation/_database-enable-restart.mdx +++ b/versioned_docs/version-26.10/installation/_database-enable-restart.mdx @@ -1,7 +1,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; - + ```shell @@ -12,8 +12,8 @@ systemctl restart mariadb - - + + ```shell systemctl enable mysqld @@ -21,15 +21,14 @@ systemctl restart mysqld ``` - + ```shell systemctl enable mysqld -systemctl restart mysqld ``` - + ```shell systemctl enable mysql diff --git a/versioned_docs/version-26.10/installation/_database-local-install.mdx b/versioned_docs/version-26.10/installation/_database-local-install.mdx index 0ba8481fa8a7..6f056f256c5e 100644 --- a/versioned_docs/version-26.10/installation/_database-local-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-local-install.mdx @@ -1,33 +1,45 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; - + - - + + ```shell dnf install -y centreon-mariadb centreon +``` + +```shell +à déplacer systemctl daemon-reload systemctl restart mariadb ``` - + ```shell dnf install -y centreon-mariadb centreon +``` + +```shell +à déplacer systemctl daemon-reload systemctl restart mariadb ``` - + ```shell apt update apt install -y centreon-mariadb centreon +``` + +```shell +à déplacer systemctl daemon-reload systemctl restart mariadb ``` @@ -38,8 +50,8 @@ systemctl restart mariadb - - + + ```shell dnf install -y mysql-server mysql @@ -52,16 +64,10 @@ systemctl restart mysqld ``` - + ```shell -dnf install -y mysql-server mysql dnf install -y centreon-mysql centreon -systemctl enable --now mysqld -echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf -sed -Ei 's/LimitNOFILE\s\=\s[0-9]{1,}/LimitNOFILE = 32000/' /usr/lib/systemd/system/$mysql_service_name.service -systemctl daemon-reload -systemctl restart mysqld ``` diff --git a/versioned_docs/version-26.10/installation/_database-remote-install.mdx b/versioned_docs/version-26.10/installation/_database-remote-install.mdx index 80d0c4eece09..f16dbb1ab8c8 100644 --- a/versioned_docs/version-26.10/installation/_database-remote-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-remote-install.mdx @@ -5,24 +5,24 @@ import DatabaseConfiguration from './_database-configuration.mdx'; > If installing the database on a dedicated server, this server should also have > the prerequisite repositories. -Run the following command on the Central server: +Run the following command on the central server: - - + + ```shell dnf install -y centreon-central ``` - + ```shell dnf install -y centreon-central ``` - + ```shell apt update @@ -34,11 +34,11 @@ apt install -y centreon-central Then run the following commands on the dedicated server for your database: - + - - + + ```shell dnf install -y centreon-mariadb @@ -47,7 +47,7 @@ systemctl restart mariadb ``` - + ```shell dnf install -y centreon-mariadb @@ -56,7 +56,7 @@ systemctl restart mariadb ``` - + ```shell apt update @@ -71,19 +71,24 @@ systemctl restart mariadb - - + + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el8-1.noarch.rpm -dnf config-manager --enable mysql-8.4-lts-community -dnf module disable mysql -dnf install mysql-community-server -systemctl start mysqld +dnf install -y mysql-server mysql +dnf install -y centreon-mysql centreon +systemctl enable --now mysqld +echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf +systemctl daemon-reload +systemctl restart mysqld +systemctl list-units --type=service | grep -i mysql +sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld +sudo systemctl start mysqld +sudo systemctl status mysqld ``` - + ```shell dnf install -y mysql-server mysql @@ -99,13 +104,12 @@ sudo systemctl status mysqld ``` - + ```shell apt update apt install -y centreon-mysql -apt install -y centreon -# Selectionner "Use Legacy Authentication Method" +# Sélectionner "Use Legacy Authentication Method" systemctl daemon-reload systemctl restart mysql ``` diff --git a/versioned_docs/version-26.10/installation/_database-repository.mdx b/versioned_docs/version-26.10/installation/_database-repository.mdx index 9b7b5bdb7250..3ddc2e1ce6a4 100644 --- a/versioned_docs/version-26.10/installation/_database-repository.mdx +++ b/versioned_docs/version-26.10/installation/_database-repository.mdx @@ -6,25 +6,24 @@ import TabItem from '@theme/TabItem'; - - + ```shell -dnf module enable -y mariadb:10.11 +curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | bash -s -- --os-type=rhel --os-version=9 --mariadb-server-version=mariadb-11.8 --skip-maxscale ``` - + ```shell -dnf module enable -y mariadb:10.11 +curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | bash -s -- --os-type=rhel --os-version=10 --mariadb-server-version=mariadb-11.8 --skip-maxscale ``` - + ```shell -curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=12 --mariadb-server-version="mariadb-10.11" +curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=13 --mariadb-server-version="mariadb-11.8" --skip-maxscale ``` @@ -33,19 +32,32 @@ curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- - - - - + + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el8-1.noarch.rpm -y +dnf install -y "https://dev.mysql.com/get/mysql84-community-release-el9-1.noarch.rpm" +curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2025 -o /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 +old_mysql_key=$(rpm -q gpg-pubkey 2>/dev/null | grep -i a8d3785c || true) +if [ -n "$old_mysql_key" ]; then rpm -e $old_mysql_key 2>/dev/null || true; fi +rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 +# install_weak_deps=False: the distro mariadb stack is only a Recommends here; without it dnf +# pulls mariadb alongside Oracle MySQL and they collide on /usr/bin/mysql. +dnf install -y --setopt=install_weak_deps=False mysql-server ``` - + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el9-1.noarch.rpm -y +dnf install -y "https://dev.mysql.com/get/mysql84-community-release-el10-1.noarch.rpm" +curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2025 -o /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 +old_mysql_key=$(rpm -q gpg-pubkey 2>/dev/null | grep -i a8d3785c || true) +if [ -n "$old_mysql_key" ]; then rpm -e $old_mysql_key 2>/dev/null || true; fi +rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 +# install_weak_deps=False: the distro mariadb stack is only a Recommends here; without it dnf +# pulls mariadb alongside Oracle MySQL and they collide on /usr/bin/mysql. +dnf install -y --setopt=install_weak_deps=False mysql-server ``` diff --git a/versioned_docs/version-26.10/installation/_database-tls-conf.mdx b/versioned_docs/version-26.10/installation/_database-tls-conf.mdx new file mode 100644 index 000000000000..06f2a6dd0fbe --- /dev/null +++ b/versioned_docs/version-26.10/installation/_database-tls-conf.mdx @@ -0,0 +1,620 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + + + + + + + + +1. ... + ssl_ca set + require_secure_transport=OFF (same convention as the MySQL runbooks; OFF keeps +plaintext allowed until every component speaks TLS — flip to ON once the stack is TLS-only). + +```shell +cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' +[mariadb] +ssl_ca = /etc/pki/centreon-tls/rootCA.pem +ssl_cert = /etc/pki/centreon-tls/server.pem +ssl_key = /etc/pki/centreon-tls/server-key.pem +require_secure_transport = OFF +tls_version = TLSv1.2,TLSv1.3 +EOF +``` + +2. Give the following permissions on the key so that it is readable by the **mysql** user only: + +```shell +chown root:mysql /etc/pki/centreon-tls/server-key.pem +chmod 0640 /etc/pki/centreon-tls/server-key.pem +``` + +3. Configure MariaDB CLI to use TLS (you will need it later). + +```shell +cat > /etc/my.cnf.d/centreon-tls-client.cnf <<'EOF' +[client] +ssl-ca=/etc/pki/centreon-tls/rootCA.pem +ssl-verify-server-cert +EOF +``` + +4. Start MariaDB: + +```shell +systemctl daemon-reload +systemctl enable --now mariadb +systemctl restart mariadb +``` + +5. Secure the installation: + +```shell +mariadb-secure-installation +``` + +6. Check that the server is using the certificates you defined (not the certificates it generates automatically when it starts). + +```shell +mariadb -e "SHOW GLOBAL VARIABLES WHERE Variable_name IN ('have_ssl','ssl_ca','ssl_cert','ssl_key');" +``` + +The expected result is: + +```shell +have_ssl YES and ssl_ca /etc/pki/centreon-tls/rootCA.pem +``` + +7. Set the environment variables that will be used by PHP to communicate with the database in TLS mode. + +```shell +for f in /etc/centreon/.env /usr/share/centreon/.env; do + mkdir -p "$(dirname "$f")" + cat >> "$f" <<'EOF' +DATABASE_SSL_ENABLED=1 +DATABASE_VERIFY_SERVER_CERT=1 +DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +EOF +done +``` + + + + +1. ... + ssl_ca set + require_secure_transport=OFF (same convention as the MySQL runbooks; OFF keeps +plaintext allowed until every component speaks TLS — flip to ON once the stack is TLS-only). + +```shell +cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' +[mariadb] +ssl_ca = /etc/pki/centreon-tls/rootCA.pem +ssl_cert = /etc/pki/centreon-tls/server.pem +ssl_key = /etc/pki/centreon-tls/server-key.pem +require_secure_transport = OFF +tls_version = TLSv1.2,TLSv1.3 +EOF +``` + +2. Give the following permissions on the key so that it is readable by the **mysql** user only: + +```shell +chown root:mysql /etc/pki/centreon-tls/server-key.pem +chmod 0640 /etc/pki/centreon-tls/server-key.pem +``` + +3. Configure MariaDB CLI to use TLS (you will need it later). + +```shell +cat > /etc/my.cnf.d/centreon-tls-client.cnf <<'EOF' +[client] +ssl-ca=/etc/pki/centreon-tls/rootCA.pem +ssl-verify-server-cert +EOF +``` + +4. Start MariaDB: + +```shell +systemctl daemon-reload +systemctl enable --now mariadb +systemctl restart mariadb +``` + +5. Secure the installation: + +```shell +mariadb-secure-installation +``` + +6. Check that the server is using the certificates you defined (not the certificates it generates automatically when it starts). + +```shell +mariadb -e "SHOW GLOBAL VARIABLES WHERE Variable_name IN ('have_ssl','ssl_ca','ssl_cert','ssl_key');" +``` + +The expected result is: + +```shell +have_ssl YES and ssl_ca /etc/pki/centreon-tls/rootCA.pem +``` + +7. Set the environment variables that will be used by PHP to communicate with the database in TLS mode. + +```shell +for f in /etc/centreon/.env /usr/share/centreon/.env; do + mkdir -p "$(dirname "$f")" + cat >> "$f" <<'EOF' +DATABASE_SSL_ENABLED=1 +DATABASE_VERIFY_SERVER_CERT=1 +DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +EOF +done +``` + + + + +1. Store the certificates in a location the database service can read. (By default, MariaDB on Debian only reads certificates under **/etc/mysql/**). + +```shell +install -d -o root -g mysql -m 0750 /etc/mysql/centreon-tls +cp /etc/pki/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem +cp /etc/pki/centreon-tls/server.pem /etc/mysql/centreon-tls/server.pem +cp /etc/pki/centreon-tls/server-key.pem /etc/mysql/centreon-tls/server-key.pem +chown root:mysql /etc/mysql/centreon-tls/*.pem +chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/server.pem +chmod 0640 /etc/mysql/centreon-tls/server-key.pem +``` + +2. Configure the database service to start in TLS mode and specify the certificate locations. + +```shell +mapfile -t inc < <(grep -oP '^\s*!includedir\s+\K\S+' /etc/mysql/my.cnf) +[ "${#inc[@]}" -eq 0 ] && echo "WARNING: no !includedir in /etc/mysql/my.cnf" >&2 +for d in "${inc[@]}"; do + mkdir -p "$d" + cat > "$d/99-centreon-tls.cnf" <<'EOF' +[mysqld] +ssl_ca = /etc/mysql/centreon-tls/rootCA.pem +ssl_cert = /etc/mysql/centreon-tls/server.pem +ssl_key = /etc/mysql/centreon-tls/server-key.pem +require_secure_transport = OFF +tls_version = TLSv1.2,TLSv1.3 +EOF + chmod 0644 "$d/99-centreon-tls.cnf" +done +``` + +3. Configure MariaDB CLI to use TLS (you will need it later). + +```shell +cat > /etc/mysql/conf.d/centreon-tls-client.cnf <<'EOF' +[client] +ssl-ca=/etc/mysql/centreon-tls/rootCA.pem +ssl-verify-server-cert +``` + +4. Start MySQL. + +```shell +systemctl daemon-reload +systemctl enable --now mariadb +systemctl restart mariadb +``` + +5. Check that the server is using the certificates you defined (not the certificates it generates automatically when it starts). + +```shell +mariadb -e "SHOW GLOBAL VARIABLES WHERE Variable_name IN ('have_ssl','ssl_ca','ssl_cert','ssl_key');" +``` + +The results should be as follows: + +```shell +have_ssl YES and ssl_ca /etc/mysql/centreon-tls/rootCA.pem +``` + +6. Set the environment variables that will be used by PHP to communicate with the database in TLS mode. + +```shell +for f in /etc/centreon/.env /usr/share/centreon/.env; do + mkdir -p "$(dirname "$f")" + cat >> "$f" <<'EOF' +DATABASE_SSL_ENABLED=1 +DATABASE_VERIFY_SERVER_CERT=1 +DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +EOF +done +``` + + + + + + + + + + + + +1. ... + +```shell +cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' +[mysqld] +ssl_ca = /etc/pki/centreon-tls/rootCA.pem +ssl_cert = /etc/pki/centreon-tls/server.pem +ssl_key = /etc/pki/centreon-tls/server-key.pem +require_secure_transport = OFF +tls_version = TLSv1.2,TLSv1.3 +EOF +``` + +2. Give the following permissions on the key so that it is readable by the **mysql** user only: + +```shell +chown root:mysql /etc/pki/centreon-tls/server-key.pem +chmod 0640 /etc/pki/centreon-tls/server-key.pem +``` + +3. Configure MySQL CLI to use TLS (you will need it later). + +```shell +cat > /etc/my.cnf.d/centreon-tls-client.cnf <<'EOF' +[client] +ssl-ca=/etc/pki/centreon-tls/rootCA.pem +ssl-mode=VERIFY_CA +EOF +``` + +4. Start MySQL: + +```shell +systemctl daemon-reload +systemctl enable --now mysqld +systemctl restart mysqld +``` + +5. Check that the server is using the certificates you defined (not the certificates it generates automatically when it starts). + +```shell +my_print_defaults mysqld | grep -iE 'ssl|tls' +mysql --ssl-mode=DISABLED -u root -e \ + "SHOW GLOBAL STATUS WHERE Variable_name IN ('Current_tls_ca','Current_tls_cert','Current_tls_key');" +``` + +The results should be as follows: + +```shell +Current_tls_ca /etc/pki/centreon-tls/rootCA.pem +``` + +6. Secure the installation (replace **my_password** by your own in the following command). Define the password you want: + +```shell +db_root_password='ChangeMeStrong#2026' +mysql_root_auth=(--ssl-mode=DISABLED -u root) +if ! mysql --ssl-mode=DISABLED -u root -e "SELECT 1" >/dev/null 2>&1; then + mysql_temp_pw=$(grep 'temporary password is generated for root@localhost' /var/log/mysqld.log \ + 2>/dev/null | tail -1 | sed -E 's/.*root@localhost: //') + if [ -z "$mysql_temp_pw" ]; then + echo "Could not authenticate to MySQL as root" >&2 + exit 1 + fi + mysql_root_auth=(--ssl-mode=DISABLED --connect-expired-password -u root -p"${mysql_temp_pw}") +fi +``` + +Then replace the default autogenerated password with yours. + +```shell +mysql "${mysql_root_auth[@]}" --verbose <> "$f" <<'EOF' +DATABASE_SSL_ENABLED=1 +DATABASE_VERIFY_SERVER_CERT=1 +DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +EOF +done +``` + + + + + +1. ... + +```shell +cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' +[mysqld] +ssl_ca = /etc/pki/centreon-tls/rootCA.pem +ssl_cert = /etc/pki/centreon-tls/server.pem +ssl_key = /etc/pki/centreon-tls/server-key.pem +require_secure_transport = OFF +tls_version = TLSv1.2,TLSv1.3 +EOF +``` + +2. Give the following permissions on the key so that it is readable by the **mysql** user only: + +```shell +chown root:mysql /etc/pki/centreon-tls/server-key.pem +chmod 0640 /etc/pki/centreon-tls/server-key.pem +``` + +3. Configure MySQL CLI to use TLS (you will need it later). + +```shell +cat > /etc/my.cnf.d/centreon-tls-client.cnf <<'EOF' +[client] +ssl-ca=/etc/pki/centreon-tls/rootCA.pem +ssl-mode=VERIFY_CA +EOF +``` + +4. Start MySQL: + +```shell +systemctl daemon-reload +systemctl enable --now mysqld +systemctl restart mysqld +``` + +5. Check that the server is using the certificates you defined (not the certificates it generates automatically when it starts). + +```shell +my_print_defaults mysqld | grep -iE 'ssl|tls' +mysql --ssl-mode=DISABLED -u root -e \ + "SHOW GLOBAL STATUS WHERE Variable_name IN ('Current_tls_ca','Current_tls_cert','Current_tls_key');" +``` + +The results should be as follows: + +```shell +Current_tls_ca /etc/pki/centreon-tls/rootCA.pem +``` + +6. Secure the installation (replace **my_password** by your own in the following command). Define the password you want: + +```shell +db_root_password='my_password' +mysql_root_auth=(--ssl-mode=DISABLED -u root) +if ! mysql --ssl-mode=DISABLED -u root -e "SELECT 1" >/dev/null 2>&1; then + mysql_temp_pw=$(grep 'temporary password is generated for root@localhost' /var/log/mysqld.log \ + 2>/dev/null | tail -1 | sed -E 's/.*root@localhost: //') + if [ -z "$mysql_temp_pw" ]; then + echo "Could not authenticate to MySQL as root" >&2 + exit 1 + fi + mysql_root_auth=(--ssl-mode=DISABLED --connect-expired-password -u root -p"${mysql_temp_pw}") +fi +``` + +Then replace the default autogenerated password with yours. + +```shell +mysql "${mysql_root_auth[@]}" --verbose <> "$f" <<'EOF' +DATABASE_SSL_ENABLED=1 +DATABASE_VERIFY_SERVER_CERT=1 +DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +EOF +done +``` + + + + + +1. Store the certificates in a location the database service can read. (By default, MySQL on Debian only reads certs under **/etc/mysql/**). + +```shell +install -d -o root -g mysql -m 0750 /etc/mysql/centreon-tls +cp /etc/pki/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem +cp /etc/pki/centreon-tls/server.pem /etc/mysql/centreon-tls/server.pem +cp /etc/pki/centreon-tls/server-key.pem /etc/mysql/centreon-tls/server-key.pem +chown root:mysql /etc/mysql/centreon-tls/*.pem +chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/server.pem +chmod 0640 /etc/mysql/centreon-tls/server-key.pem +``` + +2. Configure the database service to start in TLS mode and specify the certificate locations. + +```shell +mapfile -t inc < <(grep -oP '^\s*!includedir\s+\K\S+' /etc/mysql/my.cnf) +[ "${#inc[@]}" -eq 0 ] && echo "WARNING: no !includedir in /etc/mysql/my.cnf" >&2 +for d in "${inc[@]}"; do + mkdir -p "$d" + cat > "$d/99-centreon-tls.cnf" <<'EOF' +[mysqld] +ssl_ca = /etc/mysql/centreon-tls/rootCA.pem +ssl_cert = /etc/mysql/centreon-tls/server.pem +ssl_key = /etc/mysql/centreon-tls/server-key.pem +require_secure_transport = OFF +tls_version = TLSv1.2,TLSv1.3 +EOF + chmod 0644 "$d/99-centreon-tls.cnf" +done +``` + +3. Configure MySQL CLI to use TLS (you will need it later). + +```shell +cat > /etc/mysql/conf.d/centreon-tls-client.cnf <<'EOF' +[client] +ssl-ca=/etc/mysql/centreon-tls/rootCA.pem +ssl-mode=VERIFY_CA +EOF +``` + +4. Start MySQL. + +```shell +systemctl daemon-reload +systemctl enable --now mysql +systemctl restart mysql +``` + +5. Check that the server is using the certificates you defined (not the certificates it generates automatically when it starts). + +```shell +my_print_defaults mysqld | grep -iE 'ssl|tls' +mysql --ssl-mode=DISABLED -u root -N -e \ + "SHOW GLOBAL STATUS WHERE Variable_name IN ('Current_tls_ca','Current_tls_cert','Current_tls_key');" +``` + +The results should be as follows: + +```shell +Current_tls_ca /etc/mysql/centreon-tls/rootCA.pem +``` + +6. Secure the installation (replace **my_password** by your own in the following command). Define the password you want: + +```shell +db_root_password='my_password' +mysql_root_auth=(--ssl-mode=DISABLED -u root) +if ! mysql --ssl-mode=DISABLED -u root -e "SELECT 1" >/dev/null 2>&1; then + mysql_temp_pw=$(grep 'temporary password is generated for root@localhost' /var/log/mysql/error.log \ + 2>/dev/null | tail -1 | sed -E 's/.*root@localhost: //') + if [ -z "$mysql_temp_pw" ]; then + echo "Could not authenticate to MySQL as root" >&2 + exit 1 + fi + mysql_root_auth=(--ssl-mode=DISABLED --connect-expired-password -u root -p"${mysql_temp_pw}") +fi +``` + +Then replace the default autogenerated password with yours. + +```shell +mysql "${mysql_root_auth[@]}" --verbose <> "$f" <<'EOF' +DATABASE_SSL_ENABLED=1 +DATABASE_VERIFY_SERVER_CERT=1 +DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +EOF +done +``` + + + + + + \ No newline at end of file diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index 7c5c18e9e149..aa202685120b 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -9,11 +9,7 @@ import DatabaseRepository from '../_database-repository.mdx'; import DatabaseLocalInstall from '../_database-local-install.mdx'; import DatabaseRemoteInstall from '../_database-remote-install.mdx'; import DatabaseEnableRestart from '../_database-enable-restart.mdx'; - -Centreon provides RPM and DEB packages for its products through the Centreon Open -Source version available free of charge in our repository. - -These packages can be installed on Alma/RHEL/Oracle Linux 9 and 10 and on Debian 13. +import DatabaseTlsConf from '../_database-tls-conf.mdx'; You must run the installation procedure as a privileged user. @@ -24,7 +20,7 @@ You must run the installation procedure as a privileged user. After installing your server, update your operating system using the following command: - + ```shell @@ -88,7 +84,7 @@ apt update && apt upgrade ### Disable SELinux - + During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace @@ -118,6 +114,36 @@ Disabled > **Note that this deactivation should be temporary.** SELinux should be [reenabled after installation](../../administration/secure-platform.md#activate-selinux) for security reasons. + + + +During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace +**enforcing** with **disabled**. You can also run the following command: + +```shell +sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config +``` + +Reboot your operating system to apply the change. + +```shell +reboot +``` + +After system startup, perform a quick check of the SELinux status: + +```shell +getenforce +``` + +You should have this result: + +```shell +Disabled +``` + +> **Note that this deactivation should be temporary.** SELinux should be [reenabled after installation](../../administration/secure-platform.md#activate-selinux) for security reasons. + @@ -138,12 +164,10 @@ systemctl disable firewalld ### Install the repositories - - - -To install Centreon you will need to install the **CodeReady Builder** repository. +#### Dependencies -Run the following commands: + + ```shell dnf install dnf-plugins-core @@ -151,20 +175,16 @@ dnf install epel-release dnf config-manager --set-enabled crb ``` -Enable PHP 8.2 using the following commands: +Install and enable PHP 8.4 using the following commands: ```shell -dnf module reset php -dnf module install php:8.2 +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y ``` -To install Centreon you will need to install the **CodeReady Builder** repository. - -Run the following commands: - ```shell dnf install -y dnf-plugins-core dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm @@ -177,39 +197,86 @@ If your server is a Cloud RHEL instance, you will have to execute the following dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms ``` -Enable PHP 8.2 using the following commands: +Install and enable PHP 8.4 using the following commands: ```shell -dnf module reset php -dnf module install php:8.2 +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y ``` -To install Centreon you will need to install the **CodeReady Builder** repository. - -Run the following commands: - ```shell dnf install dnf-plugins-core dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm dnf config-manager --set-enabled ol9_codeready_builder ``` -Enable PHP 8.2 using the following commands: +Install and enable PHP 8.4 using the following commands: ```shell -dnf module reset php -dnf module install php:8.2 +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y ``` - + + +```shell +dnf install dnf-plugins-core -y +dnf install epel-release -y +dnf config-manager --set-enabled crb +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +``` + +Install and enable PHP 8.4 using the following commands: -#### Install dependencies +```shell +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y +``` -Install the following dependencies: + + + +```shell +dnf install dnf-plugins-core -y +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms +``` + +If your server is a Cloud RHEL instance, you will have to execute the following command: + +```shell +dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms +``` + +Install and enable PHP 8.4 using the following commands: + +```shell +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y +``` + + + + +```shell +dnf install dnf-plugins-core -y +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +dnf config-manager --set-enabled ol10_codeready_builder +``` + +Install and enable PHP 8.4 using the following commands: + +```shell +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y +``` + + + ```shell apt update && apt install -y lsb-release ca-certificates apt-transport-https wget gnupg2 curl sudo @@ -228,7 +295,7 @@ To install Centreon software, you should first install the Centreon repository. Install the Centreon repository using this command: - + ```shell @@ -237,10 +304,19 @@ dnf clean all --enablerepo=* dnf update ``` + + + +```shell +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon.repo +dnf clean all --enablerepo=* +dnf update -y +``` + -To install the Centreon repository, execute the following command: +To install the Centreon repositories, execute the following command: ```shell echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list @@ -257,13 +333,87 @@ apt update -## Step 2: HTTPS? +## Step 2: Generate the certificates + +Generate the certificates the platform will need to connect to the web interface and to the database. + +1. On the central server, install **openssl**. + + + + + ```shell + dnf install openssl -y + ``` + + + + + ```shell + dnf install openssl -y + ``` + + + + + ```shell + apt install -y openssl + ``` + + + + +2. Download the **entrypoint.sh** script. + +3. Run the script to generate a root CA and a certificate for this host. Replace \ by the IP address of your machine: + + ```shell + mkdir -p /etc/pki/centreon-tls + OUT=/etc/pki/centreon-tls \ + entrypoint.sh localhost 127.0.0.1 + cd / + ``` + + The command outputs the following files in **/etc/pki/centreon-tls/**: + + * rootCA.pem (public) + * server.pem (server certificate) + * server-key.pem (server private key) + * CA/rootCA.\{key,pem\} (set the following permissions root:root, mode 0400) + +4. Install the root CA into the OS trust store: + + + + + ```shell + cp /etc/pki/centreon-tls/rootCA.pem /etc/pki/ca-trust/source/anchors/centreon-dev.crt + update-ca-trust extract + ``` -## Step 2: Installation + + -This section describes how to install a Centreon central server. + ```shell + cp /etc/pki/centreon-tls/rootCA.pem /etc/pki/ca-trust/source/anchors/centreon-dev.crt + update-ca-trust extract + ``` -You can install this server with a local database on the server or + + + + ```shell + cp /etc/pki/centreon-tls/rootCA.pem /usr/local/share/ca-certificates/centreon-dev.crt + ``` + + + + +5. If you are using a remote database, also execute this procedure on the machine that will host the remote database, then copy the root CA certificate of the database machine to the central server's trust store. + +## Step 3: Install the central server and the database + +You can install the central server with a local database on the server or a remote database on a dedicated server. @@ -275,17 +425,139 @@ a remote database on a dedicated server. -## Step 3: Configuration +## Step 4: Set up the TLS configuration + +### For the database + + + +### For the web interface + + + + +1. Configure Apache TLS: + +```shell +dnf install -y mod_ssl +echo 'Listen 443 https' > /etc/httpd/conf.d/ssl.conf +``` + +2. Enter the correct certificate paths in Centreon's Apache HTTPS configuration: + +```shell +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ + /usr/share/centreon/examples/centreon-apache-https.conf \ + > /etc/httpd/conf.d/00-centreon-tls.conf +``` + +3. Enable and restart Centreon services: + +```shell +systemctl daemon-reload +``` + + + + + +```shell +systemctl restart mariadb +``` + + + + +```shell +systemctl restart mysqld +``` + + + + + + + +1. Configure Apache TLS: + +```shell +dnf install -y mod_ssl +echo 'Listen 443 https' > /etc/httpd/conf.d/ssl.conf +``` + +2. Enter the correct certificate paths in Centreon's Apache HTTPS configuration: + +```shell +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ + /usr/share/centreon/examples/centreon-apache-https.conf \ + > /etc/httpd/conf.d/00-centreon-tls.conf +``` + +3. Enable and restart Centreon services: + +```shell +systemctl daemon-reload +``` + + + + + +```shell +systemctl restart mariadb +``` + + + + +```shell +systemctl restart mysqld +``` + + + + + + + + +Enable every module the official Centreon HTTPS references: + +```shell +a2enmod ssl proxy proxy_fcgi headers deflate rewrite +``` + +Enter the correct certificate paths in Centreon's Apache HTTPS configuration: + +```shell +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ + /usr/share/centreon/examples/centreon-apache-https.conf \ + > /etc/apache2/sites-available/00-centreon-tls.conf +``` + +Enable the configuration you just applied. + +```shell +a2ensite 00-centreon-tls +``` + + + + +## Step 5: Configuration -### Server name +### Change the server name (optional) -If you want to change the server's hostname, use the following command: +If you want to change the server's hostname, use the following command, replacing **new-server-name** with the name of your choice: ```shell hostnamectl set-hostname new-server-name ``` -Replace **new-server-name** with the name of your choice. Example: +Example: ```shell hostnamectl set-hostname central @@ -298,8 +570,8 @@ You are required to set the PHP time zone. > Replace **Europe/Paris** with your time zone. You can find the list of > supported time zones [here](http://php.net/manual/en/timezones.php). - - + + Run the following command as `root`: @@ -314,7 +586,7 @@ systemctl restart php-fpm ``` - + Run the following command as `root`: @@ -329,18 +601,18 @@ systemctl restart php-fpm ``` - + ```shell -echo "date.timezone = Europe/Paris" >> /etc/php/8.2/mods-available/centreon.ini +echo "date.timezone = Europe/Paris" >> /etc/php/8.4/mods-available/centreon.ini ``` > The PHP timezone was defined during the installation process by retrieving the timezone configured on the operating system. -After saving the file, restart the PHP8.2-FPM service: +After saving the file, restart the PHP8.4-FPM service: ```shell -systemctl restart php8.2-fpm +systemctl restart php8.4-fpm ``` @@ -351,8 +623,8 @@ systemctl restart php8.2-fpm To make services start automatically during system bootup, run these commands on the central server: - - + + ```shell systemctl enable php-fpm httpd centreon cbd centengine gorgoned snmptrapd centreontrapd snmpd @@ -361,19 +633,20 @@ systemctl start crond ``` - + ```shell systemctl enable php-fpm httpd centreon cbd centengine gorgoned snmptrapd centreontrapd snmpd -systemctl enable crond +systemctl enable --now crond systemctl start crond ``` - + ```shell -systemctl enable php8.2-fpm apache2 centreon cbd centengine gorgoned centreontrapd snmpd snmptrapd +systemctl enable apache2 php8.4-fpm centreon cbd centengine gorgoned snmptrapd centreontrapd snmpd +systemctl enable --now cron ``` @@ -388,7 +661,7 @@ Then execute the following command (on the central server if you are using a loc It is mandatory to secure the database's root access before installing Centreon. If you are using a local database, run the following command on the central server: - + ```shell @@ -418,27 +691,27 @@ mysql_secure_installation > For more information, please see the [official MariaDB documentation](https://mariadb.com/kb/en/mysql_secure_installation/). -## Step 4: Web installation +## Step 6: Web installation 1. Start the Apache server with the following command: - - + + ```shell systemctl start httpd ``` - + ```shell systemctl start httpd ``` - + ```shell systemctl start apache2 diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index 3c5099c1357a..71b520b7acd2 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -70,15 +70,11 @@ Centreon 26.10 uses PHP in version 8.4. -You need to change the PHP stream from version {props.oldPhpVersion} to 8.4 by executing the following commands and answering **y** -to confirm: +You need to install the Remi repo and the switch the PHP stream from version {props.oldPhpVersion} to 8.4 by executing the following commands: ```shell -dnf module reset php -``` - -```shell -dnf module enable php:8.4 +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y ``` From 4daf552664059ca1861acf3b53e7472310128e7e Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 20 Aug 2026 17:32:50 +0200 Subject: [PATCH 040/179] Fix link --- .../version-26.10/installation/web-and-post-installation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/installation/web-and-post-installation.md b/versioned_docs/version-26.10/installation/web-and-post-installation.md index 09625dd77a2d..7dc1eef431b1 100644 --- a/versioned_docs/version-26.10/installation/web-and-post-installation.md +++ b/versioned_docs/version-26.10/installation/web-and-post-installation.md @@ -54,7 +54,7 @@ Provide the information needed to connect to the database instance. - **Database Host Address**: If you are using a local database, leave the field blank (the default value is **localhost**). Otherwise, enter the IP address of your remote database. - **Root user/password**: this is the account that will be used to install the databases. - if this is the default account (**root**), the root password of the database is the password [you have defined](installation-of-a-central-server/using-packages.md#secure-the-database) when executing `mysql_secure_installation`. - - if you have defined a custom user with root privileges on all databases (e.g. during the process of installing a [remote database](../installation/installation-of-a-central-server/using-packages.md#step-2-installation)), use this one. This user can be deleted once the web installation process is finished. + - if you have defined a custom user with root privileges on all databases (e.g. during the process of installing a [remote database](../installation/installation-of-a-central-server/using-packages.md#step-3-install-the-central-server-and-the-database)), use this one. This user can be deleted once the web installation process is finished. - **Database user name/password**: the credentials of the account that will be used to interact with the Centreon databases. The account will be created when the database is installed. From ddd62e0bdd4e5a5ca75e2bb66e035d536f524781 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 27 Aug 2026 15:43:34 +0200 Subject: [PATCH 041/179] Rework central unattended topic --- .../unattended.md | 183 ++++++++++++------ 1 file changed, 129 insertions(+), 54 deletions(-) diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md index 31e6ecf2d361..2ad8f9b4e36e 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md @@ -5,87 +5,162 @@ description: "Install a central server quickly using an unattended script" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import CodeBlock from '@theme/CodeBlock'; -To install a central server quicker, you can use a script. This will carry out the full installation procedure, including the web installation. +An unattended installation lets you install a central server by passing all the required settings as options when you run the installation script. The script uses those values to complete the installation on its own, so the process is quick and requires little effort. -## Installation procedure +This is useful when you need to install several central servers with identical settings, when you install from a deployment tool or CI pipeline, or when you have no interactive access to the target machine. + +> An unattended installation always sets up the central server with a local database. To use a remote database, [install the central server from packages](using-packages.md). + +## Prerequisites 1. Update your system: - - + + -```shell -dnf update -subscription-manager register --username my_username --password my_password --auto-attach --force -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms + ``` -> Replace **my_username** and **my_password** with the credentials of your RedHat account. + Replace **my_username** and **my_password** with your Red Hat account credentials. - + + - + ```shell + dnf update + ``` -```shell -dnf update -``` + + - - + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms + ``` -```shell -dnf update -subscription-manager register --username my_username --password my_password --auto-attach --force -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms -``` + Replace **my_username** and **my_password** with your Red Hat account credentials. - - + + -```shell -dnf update -``` + ```shell + dnf update + ``` - - + + -```shell -apt update && apt upgrade -``` + ```shell + apt update && apt upgrade + ``` - - + + + +2. Download the script: -2. Download the script using the following command: + ```shell + curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh + ``` -```shell -curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh -``` +## Installation -3. Run the following command as **root**: +1. As **root**, run the script with the options you want. The script writes a full log, including any errors, to `/var/log/centreon-unattended-.log`. -* To specify the password for the default **admin** account: + Here is the basic command (installs MariaDB with no TLS): -```shell -bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log -``` + ```shell + bash /tmp/unattended.sh install -t central -v 26.10 + ``` -* To get an autogenerated password for the default **admin** account (the script will tell you where the password is stored): + And here are the options you can pass (see the [examples](#examples) below): -```shell -bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log -``` + | Option | Description | + |--------|-------------| + | `-d ` | Database to install. By default, the script installs MariaDB: use `-d mysql` to install MySQL instead. | + | `--tls enabled` | Installs the central server in TLS mode: the connections to the web interface and to the database are encrypted. Without this option, the central server is installed without TLS. | + | `-p ` | Password of the default **admin** database account. If you omit this option, the script generates a password and tells you where it is stored. | + | `-s` | Silent installation: the script does not prompt you for anything. | + | `-l ` | Level of detail of the log file: `DEBUG`, `INFO`, `WARN` or `ERROR`. | -In both cases, you will get a full log file with all errors in your **tmp** folder, named **unattended(date).log**. + To display the full list of options, run: -> To get help on the script, use the following command: `bash unattended.sh -h` + ```shell + bash /tmp/unattended.sh -h + ``` -4. Configure Centreon +2. Go to http(s)://\/centreon (where \ is your server's IP address) and log in. Then follow the + [initialization of the monitoring](../web-and-post-installation.md#initialization-of-the-monitoring) steps. -Log in to the Centreon web interface via the URL `http://[SERVER_IP]/centreon` where [SERVER_IP] is the real IP address of your server. -Once you are logged in, follow the steps described [here](../../web-and-post-installation/#initialization-of-the-monitoring). +3. Start using Centreon: follow our [Getting started](../../getting-started/welcome.md) guide to start monitoring your resources. -5. Start using Centreon +## Examples -Follow our [quick start guide](../../getting-started/welcome.md) to start your monitoring. + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
SettingsCommand
Using MariaDB and no TLSbash /tmp/unattended.sh install -t central -v 26.10
Using MySQL and no TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql
Using MariaDB and TLSbash /tmp/unattended.sh install -t central -v 26.10 -s --tls enabled
Using MySQL and TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql --tls enabled
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
SettingsCommand (replace XXXXX with the password of your choice)
Using MariaDB and no TLSbash /tmp/unattended.sh install -t central -v 26.10 -p XXXXX
Using MySQL and no TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql -p XXXXX
Using MariaDB and TLSbash /tmp/unattended.sh install -t central -v 26.10 -s --tls enabled -p XXXXX
Using MySQL and TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql --tls enabled -p XXXXX
+ + + From 7348496cb18e93ff240eb716e874d7c1c5edda6b Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 27 Aug 2026 15:54:01 +0200 Subject: [PATCH 042/179] Unattended procedure for a poller --- .../installation-of-a-poller/unattended.md | 95 ++++++++++--------- 1 file changed, 51 insertions(+), 44 deletions(-) diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md index 74123467ba27..440fd9681430 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md @@ -6,72 +6,79 @@ description: "Install a poller quickly using an unattended script" import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -To install a poller quicker, you can use a script. This will perform all installation steps. You must then register the poller and attach it to the central server or the remote server. +To install a poller quickly, you can use a script. -## Installation procedure +This is useful when you need to install several pollers with identical settings, when you install from a deployment tool or CI pipeline, or when you have no interactive access to the target machine. + +The script will perform all installation steps. You must then [register the poller](./using-packages.md#step-3-register-the-server), then [attach the poller to the central server or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). + +## Prerequisites 1. Update your system: - - + + -```shell -dnf update -subscription-manager register --username my_username --password my_password --auto-attach --force -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms + ``` -> Replace **my_username** and **my_password** with the credentials of your RedHat account. + Replace **my_username** and **my_password** with your Red Hat account credentials. - + + - + ```shell + dnf update + ``` -```shell -dnf update -``` + + - - + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms + ``` -```shell -dnf update -subscription-manager register --username my_username --password my_password --auto-attach --force -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms -``` + Replace **my_username** and **my_password** with your Red Hat account credentials. - - + + -```shell -dnf update -``` + ```shell + dnf update + ``` - - + + -```shell -apt update && apt upgrade -``` + ```shell + apt update && apt upgrade + ``` - - + + -2. Download the script using the following command: +2. Download the script: -```shell -curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh -``` + ```shell + curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh + ``` -3. Run the following command as **root**: +## Installation procedure -```shell -bash /tmp/unattended.sh install -t poller -v 26.10 -r stable -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log -``` +1. Run the following command as **root**: + + ```shell + bash /tmp/unattended.sh install -t poller -v 26.10 -r stable -l DEBUG 2>&1 + ``` - You will get a full log file with all errors in your **tmp** folder, named **unattended(date).log**. + The script writes a full log, including any errors, to `/var/log/centreon-unattended-.log`. -4. Once the script has run, carry out [steps 3 to 5 of the standard installation procedure for a poller](./using-packages.md#step-3-register-the-server). +2. Once the script has run, [register the poller](./using-packages.md#step-3-register-the-server), then [attach the poller to the central or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). ## Help From a44df7c50c9ba6795f6a75aad8ea3f44446f8439 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 27 Aug 2026 15:54:50 +0200 Subject: [PATCH 043/179] Change topic order --- versioned_sidebars/version-26.10-sidebars.json | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/versioned_sidebars/version-26.10-sidebars.json b/versioned_sidebars/version-26.10-sidebars.json index d3bc2c30197f..e952f09a3731 100644 --- a/versioned_sidebars/version-26.10-sidebars.json +++ b/versioned_sidebars/version-26.10-sidebars.json @@ -126,11 +126,11 @@ "items": [ { "type": "doc", - "id": "installation/installation-of-a-central-server/using-packages" + "id": "installation/installation-of-a-central-server/unattended-install-central" }, { "type": "doc", - "id": "installation/installation-of-a-central-server/unattended-install-central" + "id": "installation/installation-of-a-central-server/using-packages" }, { "type": "doc", @@ -151,15 +151,15 @@ "items": [ { "type": "doc", - "id": "installation/installation-of-a-poller/using-packages" + "id": "installation/installation-of-a-poller/unattended-install-poller" }, { "type": "doc", - "id": "installation/installation-of-a-poller/using-containers" + "id": "installation/installation-of-a-poller/using-packages" }, { "type": "doc", - "id": "installation/installation-of-a-poller/unattended-install-poller" + "id": "installation/installation-of-a-poller/using-containers" } ] }, @@ -172,11 +172,11 @@ "items": [ { "type": "doc", - "id": "installation/installation-of-a-remote-server/using-packages" - }, + "id": "installation/installation-of-a-remote-server/unattended-install-remote" + }, { "type": "doc", - "id": "installation/installation-of-a-remote-server/unattended-install-remote" + "id": "installation/installation-of-a-remote-server/using-packages" } ] }, From d0cc006d1bf65db01d4d4b6e927638c04722322b Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 7 Sep 2026 13:05:05 +0200 Subject: [PATCH 044/179] Update --- .../installation/_database-tls-conf.mdx | 10 +- .../unattended.md | 2 +- .../using-packages.md | 95 +++------ .../using-virtual-machines.md | 2 +- .../unattended.md | 180 ++++++++++++------ 5 files changed, 156 insertions(+), 133 deletions(-) diff --git a/versioned_docs/version-26.10/installation/_database-tls-conf.mdx b/versioned_docs/version-26.10/installation/_database-tls-conf.mdx index 06f2a6dd0fbe..e83a60c2bc06 100644 --- a/versioned_docs/version-26.10/installation/_database-tls-conf.mdx +++ b/versioned_docs/version-26.10/installation/_database-tls-conf.mdx @@ -1,6 +1,8 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +This section describes how to set up a TLS connection between the central server and the database. + @@ -8,9 +10,7 @@ import TabItem from '@theme/TabItem'; -1. ... - ssl_ca set + require_secure_transport=OFF (same convention as the MySQL runbooks; OFF keeps -plaintext allowed until every component speaks TLS — flip to ON once the stack is TLS-only). +1. Create the configuration file for the database to start in TLS. ```shell cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' @@ -82,9 +82,7 @@ done -1. ... - ssl_ca set + require_secure_transport=OFF (same convention as the MySQL runbooks; OFF keeps -plaintext allowed until every component speaks TLS — flip to ON once the stack is TLS-only). +1. Create the configuration file for the database to start in TLS. ```shell cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md index 2ad8f9b4e36e..2e105f2babc6 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md @@ -84,7 +84,7 @@ This is useful when you need to install several central servers with identical s | Option | Description | |--------|-------------| | `-d ` | Database to install. By default, the script installs MariaDB: use `-d mysql` to install MySQL instead. | - | `--tls enabled` | Installs the central server in TLS mode: the connections to the web interface and to the database are encrypted. Without this option, the central server is installed without TLS. | + | `--tls enabled` | Installs the central server in TLS mode: the connections to the web interface and to the database are encrypted. Without this option, the central server is installed without TLS. Note that on some OSs, cryptographic policies may prevent the script from running correctly. | | `-p ` | Password of the default **admin** database account. If you omit this option, the script generates a password and tells you where it is stored. | | `-s` | Silent installation: the script does not prompt you for anything. | | `-l ` | Level of detail of the log file: `DEBUG`, `INFO`, `WARN` or `ERROR`. | diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index aa202685120b..d07ed028d38b 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -15,6 +15,8 @@ You must run the installation procedure as a privileged user. > When you run a command, check its output. If you get an error message, stop the procedure and fix the issue. +We recommend encrypting the communications of both the web server and the database, even though these steps are not required for Centreon to work. The procedure below sets up this encryption. In some cases (e.g. when running quick tests), you may want a non-secure setup: just skip [step 3: Set up the TLS configuration](#step-3-set-up-the-tls-configuration). + ## Prerequisites After installing your server, update your operating system using the following @@ -333,7 +335,23 @@ apt update -## Step 2: Generate the certificates +## Step 2: Install the central server and the database + +You can install the central server with a local database on the server or +a remote database on a dedicated server. + + + + + + + + + + +## Step 3: Set up the TLS configuration + +### Generate the certificates Generate the certificates the platform will need to connect to the web interface and to the database. @@ -411,28 +429,14 @@ Generate the certificates the platform will need to connect to the web interface 5. If you are using a remote database, also execute this procedure on the machine that will host the remote database, then copy the root CA certificate of the database machine to the central server's trust store. -## Step 3: Install the central server and the database - -You can install the central server with a local database on the server or -a remote database on a dedicated server. - - - - - - - - - - -## Step 4: Set up the TLS configuration - ### For the database ### For the web interface +This section describes how to set up a TLS connection between the central server and the web interface. + @@ -458,24 +462,6 @@ sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ systemctl daemon-reload ``` - - - - -```shell -systemctl restart mariadb -``` - - - - -```shell -systemctl restart mysqld -``` - - - - @@ -547,7 +533,7 @@ a2ensite 00-centreon-tls -## Step 5: Configuration +## Step 4: Configuration ### Change the server name (optional) @@ -656,42 +642,7 @@ Then execute the following command (on the central server if you are using a loc -### Secure the database - -It is mandatory to secure the database's root access before installing Centreon. -If you are using a local database, run the following command on the central server: - - - - -```shell -mariadb-secure-installation -``` - - - - -Retrieve the temporary password created by MySQL: - -```shell -grep 'temporary password' /var/log/mysqld.log -``` - -Then change it when prompted by the following command: - -```shell -mysql_secure_installation -``` - - - - -* Answer **yes** to all the questions except "Disallow root login remotely?". -* It is mandatory to set a password for the **root** user of the database. You will need this password during the [web installation](../web-and-post-installation.md). - -> For more information, please see the [official MariaDB documentation](https://mariadb.com/kb/en/mysql_secure_installation/). - -## Step 6: Web installation +## Step 5: Web installation 1. Start the Apache server with the following command: diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-virtual-machines.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-virtual-machines.md index d41b54f3a901..bfe3778a3107 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-virtual-machines.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-virtual-machines.md @@ -6,7 +6,7 @@ description: "Install a central server using a ready-to-use virtual machine" import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -On its [download page](https://download.centreon.com), Centreon provides ready-to-use virtual machines. These virtual machines are available for VMware environments and for Oracle VirtualBox. They are based on the **Alma Linux 8 and 9** and **Debian 12** operating systems and include a Centreon installation that allows you to easily start your first monitoring. +On its [download page](https://download.centreon.com), Centreon provides ready-to-use virtual machines. These virtual machines are available for VMware environments and for Oracle VirtualBox. They are based on the [supported operating systems](../compatibility.md#operating-systems) and include a Centreon installation that allows you to easily start your first monitoring. > Virtual machines are only suitable to use Centreon IT-100 or to test the solution. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md index ed852ea517da..08326fe524a9 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md @@ -8,83 +8,157 @@ import TabItem from '@theme/TabItem'; To install a remote server quicker, you can use a script. This will perform all installation steps. You must then register the remote server and attach it to the central server. -## Installation procedure +## Prerequisites 1. Update your system: - - + + -```shell -dnf update -subscription-manager register --username my_username --password my_password --auto-attach --force -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms + ``` -> Replace **my_username** and **my_password** with the credentials of your RedHat account. + Replace **my_username** and **my_password** with your Red Hat account credentials. - + + - + ```shell + dnf update + ``` -```shell -dnf update -``` + + - - + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms + ``` -```shell -dnf update -subscription-manager register --username my_username --password my_password --auto-attach --force -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms -``` + Replace **my_username** and **my_password** with your Red Hat account credentials. - - + + -```shell -dnf update -``` + ```shell + dnf update + ``` - - + + -```shell -apt update && apt upgrade -``` + ```shell + apt update && apt upgrade + ``` - - + + + +2. Download the script: -2. Download the script using the following command: + ```shell + curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh + ``` -```shell -curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh -``` +## Installation -3. Run the following command as **root**: +1. As **root**, run the script with the options you want. The script writes a full log, including any errors, to `/var/log/centreon-unattended-.log`. -* To specify the password for the default **admin** account: + Here is the basic command (installs MariaDB with no TLS): -```shell -bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log -``` + ```shell + bash /tmp/unattended.sh install -t central -v 26.10 + ``` -* To get an autogenerated password for the default **admin** account (the script will tell you where the password is stored): + And here are the options you can pass (see the [examples](#examples) below): -```shell -bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log -``` + | Option | Description | + |--------|-------------| + | `-d ` | Database to install. By default, the script installs MariaDB: use `-d mysql` to install MySQL instead. | + | `--tls enabled` | Installs the central server in TLS mode: the connections to the web interface and to the database are encrypted. Without this option, the central server is installed without TLS. Note that on some OSs, cryptographic policies may prevent the script from running correctly. | + | `-p ` | Password of the default **admin** database account. If you omit this option, the script generates a password and tells you where it is stored. | + | `-s` | Silent installation: the script does not prompt you for anything. | + | `-l ` | Level of detail of the log file: `DEBUG`, `INFO`, `WARN` or `ERROR`. | -In both cases, you will get a full log file with all errors in your **tmp** folder, named **unattended(date).log**. + To display the full list of options, run: -4. Once the script has run, carry out [steps 4 to 8 of the standard installation procedure for a remote server](./using-packages.md#step-5-register-the-server). + ```shell + bash /tmp/unattended.sh -h + ``` -## Help +2. Go to http(s)://\/centreon (where \ is your server's IP address) and log in. Then follow the + [initialization of the monitoring](../web-and-post-installation.md#initialization-of-the-monitoring) steps. -To get help on the script, use the following command: + 4. Once the script has run, carry out [steps 4 to 8 of the standard installation procedure for a remote server](./using-packages.md#step-5-register-the-server). -```shell -bash unattended.sh -h -``` + +3. Start using Centreon: follow our [Getting started](../../getting-started/welcome.md) guide to start monitoring your resources. + +## Examples + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
SettingsCommand
Using MariaDB and no TLSbash /tmp/unattended.sh install -t central -v 26.10
Using MySQL and no TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql
Using MariaDB and TLSbash /tmp/unattended.sh install -t central -v 26.10 -s --tls enabled
Using MySQL and TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql --tls enabled
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
SettingsCommand (replace XXXXX with the password of your choice)
Using MariaDB and no TLSbash /tmp/unattended.sh install -t central -v 26.10 -p XXXXX
Using MySQL and no TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql -p XXXXX
Using MariaDB and TLSbash /tmp/unattended.sh install -t central -v 26.10 -s --tls enabled -p XXXXX
Using MySQL and TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql --tls enabled -p XXXXX
+ + + From 7a882c5e47052e3f1d3ba07c7978406198cab446 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 7 Sep 2026 14:55:34 +0200 Subject: [PATCH 045/179] Update for VMs --- .../using-virtual-machines.md | 16 +++++++++------- .../using-virtual-machines.md | 14 ++++++++------ 2 files changed, 17 insertions(+), 13 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-virtual-machines.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-virtual-machines.md index 18d82e14e897..7edb70448559 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-virtual-machines.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-virtual-machines.md @@ -9,13 +9,15 @@ import TabItem from '@theme/TabItem'; Sur sa [page de téléchargement](https://download.centreon.com), Centreon fournit des machines virtuelles prêtes à l’emploi. Ces machines virtuelles sont disponibles pour les environnements VMware et pour l'outil Oracle VirtualBox. -Elles sont basées sur les systèmes d'exploitation **Alma Linux 8 et 9** et **Debian 12** et incluent +Elles sont basées sur les systèmes d'exploitation **Alma Linux 9 et 10** et **Debian 13**, et incluent une installation de Centreon permettant de démarrer en toute simplicité votre première supervision. > L'installation par machine virtuelle n'est adaptée que pour utiliser IT-100, ou à des fins de test. Les VMs sont configurées en **Thin Provision** pour économiser autant d'espace libre que possible sur le disque (meilleure pratique). +Les VMs sont installées en mode TLS : les connexions à l'interface web et à la base de données sont chiffrées. + ## Prérequis La machine hôte doit avoir les caractéristiques suivantes : @@ -124,7 +126,7 @@ cliquez sur **Download**. configuration. - + Définissez les paramètres suivants : @@ -178,7 +180,7 @@ changer, utilisez la commande suivante : ``` - + Définissez les paramètres suivants : @@ -207,7 +209,7 @@ Définissez les paramètres suivants : 1. Ouvrez le fichier suivant : ```shell - /etc/php/8.2/mods-available/centreon.ini + /etc/php/4/mods-available/centreon.ini ``` 2. Après date.timezone, entrez le fuseau horaire désiré. @@ -215,7 +217,7 @@ Définissez les paramètres suivants : 3. Redémarrez le serveur PHP : ```shell - systemctl restart php8.2-fpm.service + systemctl restart php8.4-fpm.service ``` - Le hostname de votre serveur (facultatif). Le nom par défaut du serveur est centreon-central. Pour le @@ -274,8 +276,8 @@ fonctionnera pas si vous ne l’exécutez pas. >`/etc/profile.d/centreon.sh` 6. Connectez-vous à l’interface web : dans votre navigateur, entrez l’adresse du serveur au format -`http://addresse_ip/centreon` ou `http://FQDN/centreon`. (Par exemple, une URL valide serait -`http://192.168.1.44/centreon`.) +`https://addresse_ip/centreon` ou `https://FQDN/centreon`. (Par exemple, une URL valide serait +`https://192.168.1.44/centreon`.) La connexion est chiffrée avec un certificat autosigné : votre navigateur affichera une alerte de sécurité. 7. Connectez-vous en utilisant les informations suivantes : Login: `admin`, password: `Centreon!123`. Par défaut, votre serveur offre une configuration prédéfinie qui permet de le superviser lui-même. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-virtual-machines.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-virtual-machines.md index bfe3778a3107..214f048d73fb 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-virtual-machines.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-virtual-machines.md @@ -6,12 +6,14 @@ description: "Install a central server using a ready-to-use virtual machine" import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -On its [download page](https://download.centreon.com), Centreon provides ready-to-use virtual machines. These virtual machines are available for VMware environments and for Oracle VirtualBox. They are based on the [supported operating systems](../compatibility.md#operating-systems) and include a Centreon installation that allows you to easily start your first monitoring. +On its [download page](https://download.centreon.com), Centreon provides ready-to-use virtual machines. These virtual machines are available for VMware environments and for Oracle VirtualBox. They are based on Alma 9, Alma 10 and Debian 13, and include a Centreon installation that allows you to easily start your first monitoring. > Virtual machines are only suitable to use Centreon IT-100 or to test the solution. The VMs use the **Thin Provision** option to save as much free space as possible on the disk (this is best practice). +The VMs are installed in TLS mode: the connections to the web interface and to the database are encrypted. + ## Prerequisites The host machine must have the following characteristics: @@ -111,7 +113,7 @@ The host machine must have the following characteristics: 4. The first time you connect to the server, instructions are displayed to help you complete the configuration. - + Change the following settings: @@ -164,7 +166,7 @@ Change the following settings: ``` - + Change the following settings: @@ -193,7 +195,7 @@ Change the following settings: 1. Open the following file: ```shell - /etc/php/8.2/mods-available/centreon.ini + /etc/php/8.4/mods-available/centreon.ini ``` 2. In `date.timezone`, define the time zone you want. @@ -201,7 +203,7 @@ Change the following settings: 3. Restart the PHP server: ```shell - systemctl restart php8.2-fpm.service + systemctl restart php8.4-fpm.service ``` - The hostname of your server (this is optional). The default name is `centreon-central`. To change it, use the following command: @@ -255,7 +257,7 @@ Change the following settings: > >`/etc/profile.d/centreon.sh` -6. To log in to the web interface, go to `http://ip_address/centreon` or `http://FQDN/centreon`. (For example, a valid URL would be `http://192.168.1.44/centreon`.) +6. To log in to the web interface, go to `https://ip_address/centreon` or `https://FQDN/centreon`. (For example, a valid URL would be `https://192.168.1.44/centreon`.) The connection is encrypted using a self-signed certificate, so your browser will display a security warning. 7. Log in using the following credentials: Login: `admin`, password: `Centreon!123`. By default, your server has a predefined configuration to monitor the Centreon server itself. From a08444db907d562dd30da09940883d5a3970a8d5 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 7 Sep 2026 15:01:54 +0200 Subject: [PATCH 046/179] Fix build --- .../installation/installation-of-a-remote-server/unattended.md | 1 + 1 file changed, 1 insertion(+) diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md index 08326fe524a9..9618397f4ecd 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md @@ -5,6 +5,7 @@ description: "Install a remote server quickly using an unattended script" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import CodeBlock from '@theme/CodeBlock'; To install a remote server quicker, you can use a script. This will perform all installation steps. You must then register the remote server and attach it to the central server. From f5f0790a072eb13a139788ca85a169d2133e9fbe Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 8 Sep 2026 15:24:07 +0200 Subject: [PATCH 047/179] Update --- .../installation/_database-configuration.mdx | 2 +- .../installation/_database-local-install.mdx | 16 +++++++++++--- .../using-packages.md | 21 ------------------- .../installation-of-a-poller/unattended.md | 2 +- .../installation/web-and-post-installation.md | 4 ++-- 5 files changed, 17 insertions(+), 28 deletions(-) diff --git a/versioned_docs/version-26.10/installation/_database-configuration.mdx b/versioned_docs/version-26.10/installation/_database-configuration.mdx index cd9fcf874009..4929b38d9af2 100644 --- a/versioned_docs/version-26.10/installation/_database-configuration.mdx +++ b/versioned_docs/version-26.10/installation/_database-configuration.mdx @@ -3,7 +3,7 @@ import TabItem from '@theme/TabItem'; > It is mandatory to set a password for the root user of the database. -Secure your database root access by executing the following command: +Set a password for the root user of the database by executing the following command: diff --git a/versioned_docs/version-26.10/installation/_database-local-install.mdx b/versioned_docs/version-26.10/installation/_database-local-install.mdx index 6f056f256c5e..b14122bbaff3 100644 --- a/versioned_docs/version-26.10/installation/_database-local-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-local-install.mdx @@ -12,7 +12,6 @@ dnf install -y centreon-mariadb centreon ``` ```shell -à déplacer systemctl daemon-reload systemctl restart mariadb ``` @@ -25,7 +24,6 @@ dnf install -y centreon-mariadb centreon ``` ```shell -à déplacer systemctl daemon-reload systemctl restart mariadb ``` @@ -39,7 +37,6 @@ apt install -y centreon-mariadb centreon ``` ```shell -à déplacer systemctl daemon-reload systemctl restart mariadb ``` @@ -47,6 +44,12 @@ systemctl restart mariadb +Set a password for the root user of the database by executing the following command: + +```shell +mariadb-secure-installation +``` + @@ -85,5 +88,12 @@ systemctl restart mysql + +Set a password for the root user of the database by executing the following command: + +```shell +mysql-secure-installation +``` + diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index d07ed028d38b..aa9a5cb19795 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -232,13 +232,6 @@ dnf config-manager --set-enabled crb dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm ``` -Install and enable PHP 8.4 using the following commands: - -```shell -dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm -dnf module switch-to php:remi-8.4/common -y -``` - @@ -254,13 +247,6 @@ If your server is a Cloud RHEL instance, you will have to execute the following dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms ``` -Install and enable PHP 8.4 using the following commands: - -```shell -dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm -dnf module switch-to php:remi-8.4/common -y -``` - @@ -270,13 +256,6 @@ dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noar dnf config-manager --set-enabled ol10_codeready_builder ``` -Install and enable PHP 8.4 using the following commands: - -```shell -dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm -dnf module switch-to php:remi-8.4/common -y -``` - diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md index 440fd9681430..42f8c9fa0f77 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md @@ -78,7 +78,7 @@ The script will perform all installation steps. You must then [register the poll The script writes a full log, including any errors, to `/var/log/centreon-unattended-.log`. -2. Once the script has run, [register the poller](./using-packages.md#step-3-register-the-server), then [attach the poller to the central or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). +2. Once the script has run, [register the poller](./using-packages.md#step-3-register-the-server), then [attach the poller to the central server or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). ## Help diff --git a/versioned_docs/version-26.10/installation/web-and-post-installation.md b/versioned_docs/version-26.10/installation/web-and-post-installation.md index 7dc1eef431b1..e7ad24709134 100644 --- a/versioned_docs/version-26.10/installation/web-and-post-installation.md +++ b/versioned_docs/version-26.10/installation/web-and-post-installation.md @@ -53,8 +53,8 @@ Provide the information needed to connect to the database instance. - **Database Host Address**: If you are using a local database, leave the field blank (the default value is **localhost**). Otherwise, enter the IP address of your remote database. - **Root user/password**: this is the account that will be used to install the databases. - - if this is the default account (**root**), the root password of the database is the password [you have defined](installation-of-a-central-server/using-packages.md#secure-the-database) when executing `mysql_secure_installation`. - - if you have defined a custom user with root privileges on all databases (e.g. during the process of installing a [remote database](../installation/installation-of-a-central-server/using-packages.md#step-3-install-the-central-server-and-the-database)), use this one. This user can be deleted once the web installation process is finished. + - if this is the default account (**root**), the root password of the database is the password [you have defined](installation-of-a-central-server/using-packages.md#step-2-install-the-central-server-and-the-database) when executing `mysql_secure_installation` or `mariadb_secure_installation`. + - if you have defined a custom user with root privileges on all databases (e.g. during the process of installing a [remote database](../installation/installation-of-a-central-server/using-packages.md#step-2-install-the-central-server-and-the-database)), use this one. This user can be deleted once the web installation process is finished. - **Database user name/password**: the credentials of the account that will be used to interact with the Centreon databases. The account will be created when the database is installed. From 9819fb92bc0f7fb10931c2f9e11828615ca1c419 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 8 Sep 2026 15:29:22 +0200 Subject: [PATCH 048/179] Fix incorrect repo URL --- .../installation-of-a-central-server/using-packages.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index aa9a5cb19795..91d6f472231e 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -289,7 +289,7 @@ dnf update ```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo dnf clean all --enablerepo=* dnf update -y ``` From 93b63268d29f3f37ae7be00440a2331475024353 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 8 Sep 2026 17:54:35 +0200 Subject: [PATCH 049/179] Single-source common part of install procedure (central, poller, remote) --- .../installation/_install-common.mdx | 148 ++++++++++++++ .../using-packages.md | 150 +------------- .../installation-of-a-poller/unattended.md | 8 - .../using-packages.md | 184 ++---------------- .../unattended.md | 5 +- .../using-packages.md | 155 +-------------- .../installation/web-and-post-installation.md | 2 +- 7 files changed, 176 insertions(+), 476 deletions(-) create mode 100644 versioned_docs/version-26.10/installation/_install-common.mdx diff --git a/versioned_docs/version-26.10/installation/_install-common.mdx b/versioned_docs/version-26.10/installation/_install-common.mdx new file mode 100644 index 000000000000..981e778033db --- /dev/null +++ b/versioned_docs/version-26.10/installation/_install-common.mdx @@ -0,0 +1,148 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +## Prerequisites + +After installing your host server, update your operating system using the following +command: + + + + +```shell +dnf update +``` + +### Additional configuration for EL 9 + +If you intend to use Centreon in French, Spanish, Portuguese or German, install the corresponding packages: + +```shell +dnf install glibc-langpack-fr +dnf install glibc-langpack-es +dnf install glibc-langpack-pt +dnf install glibc-langpack-de +``` + +Use the following command to check which languages are installed on your system: + +```shell +locale -a +``` + + + + +```shell +dnf update +``` + +### Additional configuration for EL 10 +If you intend to use Centreon in French, Spanish, Portuguese or German, install the corresponding packages: + +```shell +dnf install glibc-langpack-fr +dnf install glibc-langpack-es +dnf install glibc-langpack-pt +dnf install glibc-langpack-de +``` + +Use the following command to check which languages are installed on your system: + +```shell +locale -a +``` + + + + +```shell +apt update && apt upgrade +``` + + + + +> Accept all GPG keys and reboot your server if a kernel update is proposed. + +## Step 1: Pre-installation + +### Disable SELinux + + + + +During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace +**enforcing** with **disabled**. You can also run the following command: + +```shell +sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config +``` + +Reboot your operating system to apply the change. + +```shell +reboot +``` + +After system startup, perform a quick check of the SELinux status: + +```shell +getenforce +``` + +You should have this result: + +```shell +Disabled +``` + +> **Note that this deactivation should be temporary.** SELinux should be [reenabled after installation](../administration/secure-platform.md#activate-selinux) for security reasons. + + + + +During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace +**enforcing** with **disabled**. You can also run the following command: + +```shell +sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config +``` + +Reboot your operating system to apply the change. + +```shell +reboot +``` + +After system startup, perform a quick check of the SELinux status: + +```shell +getenforce +``` + +You should have this result: + +```shell +Disabled +``` + +> **Note that this deactivation should be temporary.** SELinux should be [reenabled after installation](../administration/secure-platform.md#activate-selinux) for security reasons. + + + + +SELinux is not installed on Debian 13, continue. + + + + +### Configure or disable the firewall + +If your firewall is active, add [firewall rules](../administration/secure-platform.md#enable-firewalld). +You can also disable the firewall during installation by running the following commands: + +```shell +systemctl stop firewalld +systemctl disable firewalld +``` \ No newline at end of file diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index 91d6f472231e..5bb5a5ab021d 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -1,6 +1,6 @@ --- id: using-packages -title: Using packages +title: Using packages (central server) description: "Install a Centreon central server using RPM or DEB packages" --- import Tabs from '@theme/Tabs'; @@ -10,6 +10,7 @@ import DatabaseLocalInstall from '../_database-local-install.mdx'; import DatabaseRemoteInstall from '../_database-remote-install.mdx'; import DatabaseEnableRestart from '../_database-enable-restart.mdx'; import DatabaseTlsConf from '../_database-tls-conf.mdx'; +import InstallCommon from '../_install-common.mdx'; You must run the installation procedure as a privileged user. @@ -17,152 +18,7 @@ You must run the installation procedure as a privileged user. We recommend encrypting the communications of both the web server and the database, even though these steps are not required for Centreon to work. The procedure below sets up this encryption. In some cases (e.g. when running quick tests), you may want a non-secure setup: just skip [step 3: Set up the TLS configuration](#step-3-set-up-the-tls-configuration). -## Prerequisites - -After installing your server, update your operating system using the following -command: - - - - -```shell -dnf update -``` - -### Additional configuration - -If you intend to use Centreon in French, Spanish, Portuguese or German, install the corresponding packages: - -```shell -dnf install glibc-langpack-fr -dnf install glibc-langpack-es -dnf install glibc-langpack-pt -dnf install glibc-langpack-de -``` - -Use the following command to check which languages are installed on your system: - -```shell -locale -a -``` - - - - -```shell -dnf update -``` - -### Additional configuration - -If you intend to use Centreon in French, Spanish, Portuguese or German, install the corresponding packages: - -```shell -dnf install glibc-langpack-fr -dnf install glibc-langpack-es -dnf install glibc-langpack-pt -dnf install glibc-langpack-de -``` - -Use the following command to check which languages are installed on your system: - -```shell -locale -a -``` - - - - -```shell -apt update && apt upgrade -``` - - - - -> Accept all GPG keys and reboot your server if a kernel update is proposed. - -## Step 1: Pre-installation - -### Disable SELinux - - - - -During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace -**enforcing** with **disabled**. You can also run the following command: - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Reboot your operating system to apply the change. - -```shell -reboot -``` - -After system startup, perform a quick check of the SELinux status: - -```shell -getenforce -``` - -You should have this result: - -```shell -Disabled -``` - -> **Note that this deactivation should be temporary.** SELinux should be [reenabled after installation](../../administration/secure-platform.md#activate-selinux) for security reasons. - - - - -During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace -**enforcing** with **disabled**. You can also run the following command: - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Reboot your operating system to apply the change. - -```shell -reboot -``` - -After system startup, perform a quick check of the SELinux status: - -```shell -getenforce -``` - -You should have this result: - -```shell -Disabled -``` - -> **Note that this deactivation should be temporary.** SELinux should be [reenabled after installation](../../administration/secure-platform.md#activate-selinux) for security reasons. - - - - -SELinux is not installed on Debian 13, continue. - - - - -### Configure or disable the firewall - -If your firewall is active, add [firewall rules](../../administration/secure-platform.md#enable-firewalld). -You can also disable the firewall during installation by running the following commands: - -```shell -systemctl stop firewalld -systemctl disable firewalld -``` + ### Install the repositories diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md index 42f8c9fa0f77..dc72852cc8d8 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md @@ -79,11 +79,3 @@ The script will perform all installation steps. You must then [register the poll The script writes a full log, including any errors, to `/var/log/centreon-unattended-.log`. 2. Once the script has run, [register the poller](./using-packages.md#step-3-register-the-server), then [attach the poller to the central server or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). - -## Help - -To get help on the script, use the following command: - -```shell -bash unattended.sh -h -``` diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-packages.md index 3aceb77e16fb..96fd8c2b8d73 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-packages.md @@ -1,167 +1,17 @@ --- id: using-packages -title: Using packages +title: Using packages (poller) description: "Install and register a poller using RPM or DEB packages" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; - -Centreon provides RPM and DEB packages for its products through the Centreon Open -Source version available free of charge in our repository. - -These packages can be installed on Alma/RHEL/Oracle Linux 8 and 9 and on Debian 12. +import InstallCommon from '../_install-common.mdx'; You must run the installation procedure as a privileged user. > When you run a command, check its output. If you get an error message, stop the procedure and fix the issue. -## Prerequisites - -After installing your server, update your operating system using the following -command: - - - - -```shell -dnf update -``` - -### Additional configuration - -If you intend to use Centreon in French, Spanish, Portuguese or German, install the corresponding packages: - -```shell -dnf install glibc-langpack-fr -dnf install glibc-langpack-es -dnf install glibc-langpack-pt -dnf install glibc-langpack-de -``` - -Use the following command to check which languages are installed on your system: - -```shell -locale -a -``` - - - - -```shell -dnf update -``` - -### Additional configuration - -If you intend to use Centreon in French, Spanish, Portuguese or German, install the corresponding packages: - -```shell -dnf install glibc-langpack-fr -dnf install glibc-langpack-es -dnf install glibc-langpack-pt -dnf install glibc-langpack-de -``` - -Use the following command to check which languages are installed on your system: - -```shell -locale -a -``` - - - - -```shell -apt update && apt upgrade -``` - - - - -> Accept all GPG keys and reboot your server if a kernel update is proposed. - -## Step 1: Pre-installation - -### Disable SELinux - - - - -During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace -**enforcing** with **disabled**. You can also run the following command: - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Reboot your operating system to apply the change. - -```shell -reboot -``` - -After system startup, perform a quick check of the SELinux status: - -```shell -getenforce -``` - -You should have this result: - -```shell -Disabled -``` - -> **Note that this deactivation should be temporary.** SELinux should be [reenabled after installation](../../administration/secure-platform.md#activate-selinux) for security reasons. - - - - - -During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace -**enforcing** with **disabled**. You can also run the following command: - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Reboot your operating system to apply the change. - -```shell -reboot -``` - -After system startup, perform a quick check of the SELinux status: - -```shell -getenforce -``` - -You should have this result: - -```shell -Disabled -``` - -> **Note that this deactivation should be temporary.** SELinux should be [reenabled after installation](../../administration/secure-platform.md#activate-selinux) for security reasons. - - - - -SELinux is not installed on Debian 12, continue. - - - - -### Configure or disable the firewall - -If your firewall is active, add [firewall rules](../../administration/secure-platform.md#enable-firewalld). -You can also disable the firewall during installation by running the following commands: - -```shell -systemctl stop firewalld -systemctl disable firewalld -``` + ### Server name @@ -295,27 +145,27 @@ To install Centreon software, you should first install the Centreon repository. Install the Centreon repository using this command: - + ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` - + ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` - + To install the Centreon repository, execute the following command line: @@ -336,7 +186,7 @@ apt update ## Step 2: Installation -To install the monitoring engine, run the command: +To install the monitoring engine, run the following command: @@ -364,26 +214,29 @@ apt install -y --no-install-recommends centreon-poller To make services start automatically during system bootup, run the following command: + ``` shell systemctl enable centreon centengine centreontrapd snmptrapd gorgoned ``` Passive monitoring services can be started: + ```shell systemctl start centreontrapd snmptrapd gorgoned ``` Restart Centreon Engine: + ```shell systemctl restart centengine ``` -## Step 3: Register the server +## Step 3: Register the poller -To turn the server into a poller and to register it to the Central server or a Remote server, execute the following command on the future poller: +To turn the server into a poller and to register it to the central server or a remote server, execute the following command on the future poller: ``` shell -/usr/share/centreon/bin/registerServerTopology.sh -u \ +/usr/share/centreon/bin/registerServerTopology.sh -u admin \ -t poller -h -n ``` @@ -393,14 +246,13 @@ Example: /usr/share/centreon/bin/registerServerTopology.sh -u admin -t poller -h 192.168.0.1 -n poller-1 ``` -> Replace **\** with the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller) - -> You must use the default **admin** account as the **\**. +> Replace **\** with the IP of the central server or remote server that you want to link the poller to (IP as seen by the poller). > If you need to change the HTTP method or the port, you can use the following format for the **-h** option: > `HTTPS://:PORT` Then follow instructions by + 1. Entering your password: ``` shell @@ -472,7 +324,7 @@ Couldn't connect to 192.168.0.1:444; Connection refused > Your Centreon target version is invalid. It should be greater than or equal to 26.10. -## Step 4: Add the Poller to the configuration +## Step 4: Attach the poller to a central or remote server Go to [Attach a poller to a central or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md index 9618397f4ecd..ccd463ae8f96 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md @@ -94,10 +94,9 @@ To install a remote server quicker, you can use a script. This will perform all 2. Go to http(s)://\/centreon (where \ is your server's IP address) and log in. Then follow the [initialization of the monitoring](../web-and-post-installation.md#initialization-of-the-monitoring) steps. - 4. Once the script has run, carry out [steps 4 to 8 of the standard installation procedure for a remote server](./using-packages.md#step-5-register-the-server). + 3. Once the script has run, carry out [steps 4 to 8 of the standard installation procedure for a remote server](./using-packages.md#step-5-register-the-server). - -3. Start using Centreon: follow our [Getting started](../../getting-started/welcome.md) guide to start monitoring your resources. +4. Start using Centreon: follow our [Getting started](../../getting-started/welcome.md) guide to start monitoring your resources. ## Examples diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md index 781a9b05ae91..9778cdd95aba 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md @@ -1,6 +1,6 @@ --- id: using-packages -title: Using packages +title: Using packages (remote server) description: "Install and register a remote server using RPM or DEB packages" --- import Tabs from '@theme/Tabs'; @@ -9,162 +9,15 @@ import DatabaseRepository from '../_database-repository.mdx'; import DatabaseLocalInstall from '../_database-local-install.mdx'; import DatabaseRemoteInstall from '../_database-remote-install.mdx'; import DatabaseEnableRestart from '../_database-enable-restart.mdx'; - -Centreon provides RPM and DEB packages for its products through the Centreon Open -Source version available free of charge in our repository. - -These packages can be installed on Alma/RHEL/Oracle Linux 8 and 9 and on Debian 12. +import InstallCommon from '../_install-common.mdx'; You must run the installation procedure as a privileged user. > When you run a command, check its output. If you get an error message, stop the procedure and fix the issue. -## Prerequisites - -After installing your server, update your operating system using the following -command: - - - - -``` shell -dnf update -``` - -### Additional configuration - -If you intend to use Centreon in French, Spanish, Portuguese or German, install the corresponding packages: - -```shell -dnf install glibc-langpack-fr -dnf install glibc-langpack-es -dnf install glibc-langpack-pt -dnf install glibc-langpack-de -``` - -Use the following command to check which languages are installed on your system: - -```shell -locale -a -``` - - - - -```shell -dnf update -``` - -### Additional configuration - -If you intend to use Centreon in French, Spanish, Portuguese or German, install the corresponding packages: - -```shell -dnf install glibc-langpack-fr -dnf install glibc-langpack-es -dnf install glibc-langpack-pt -dnf install glibc-langpack-de -``` +We recommend encrypting the communications of both the web server and the database, even though these steps are not required for Centreon to work. The procedure below sets up this encryption. In some cases (e.g. when running quick tests), you may want a non-secure setup: just skip [step 3: Set up the TLS configuration](#step-3-set-up-the-tls-configuration). -Use the following command to check which languages are installed on your system: - -```shell -locale -a -``` - - - - -``` shell -apt update && apt upgrade -``` - - - - -> Accept all GPG keys and consider rebooting your server if a kernel update is proposed. - -## Step 1: Pre-installation - -### Disable SELinux - - - - -During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace -**enforcing** with **disabled**. You can also run the following command: - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Reboot your operating system to apply the change. - -```shell -reboot -``` - -After the system reboot, perform a quick check of the SELinux status: - -```shell -getenforce -``` - -You should have this result: - -```shell -Disabled -``` - -> **Note that this deactivation should be temporary.** SELinux should be [reenabled after installation](../../administration/secure-platform.md#activate-selinux) for security reasons. - - - - -During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace -**enforcing** with **disabled**. You can also run the following command: - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Reboot your operating system to apply the change. - -```shell -reboot -``` - -After system startup, perform a quick check of the SELinux status: - -```shell -getenforce -``` - -You should have this result: - -```shell -Disabled -``` - -> **Note that this deactivation should be temporary.** SELinux should be [reenabled after installation](../../administration/secure-platform.md#activate-selinux) for security reasons. - - - - -SELinux is not installed on Debian 12, continue. - - - - -### Configure or disable the firewall - -If your firewall is active, add [firewall rules](../../administration/secure-platform.md#enable-firewalld). -You can also disable the firewall during installation by running the following commands: - -```shell -systemctl stop firewalld -systemctl disable firewalld -``` + ### Install the repositories diff --git a/versioned_docs/version-26.10/installation/web-and-post-installation.md b/versioned_docs/version-26.10/installation/web-and-post-installation.md index e7ad24709134..84ca20a69196 100644 --- a/versioned_docs/version-26.10/installation/web-and-post-installation.md +++ b/versioned_docs/version-26.10/installation/web-and-post-installation.md @@ -6,7 +6,7 @@ description: "Complete the web setup wizard and initialize your monitoring" ## Web installation -Log in to Centreon web interface via the URL `http:///centreon`. +Log in to Centreon web interface via the URL `http(s):///centreon`. ### Step 1: Welcome to Centreon setup From 3445bac7bd9171614137f67664d3ccb4a4ba90d1 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 8 Sep 2026 18:11:20 +0200 Subject: [PATCH 050/179] Fix build --- .../installation/installation-of-a-poller/unattended.md | 2 +- .../installation-of-a-remote-server/using-packages.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md index dc72852cc8d8..dc2d9bcad308 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md @@ -10,7 +10,7 @@ To install a poller quickly, you can use a script. This is useful when you need to install several pollers with identical settings, when you install from a deployment tool or CI pipeline, or when you have no interactive access to the target machine. -The script will perform all installation steps. You must then [register the poller](./using-packages.md#step-3-register-the-server), then [attach the poller to the central server or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). +The script will perform all installation steps. You must then [register the poller](./using-packages.md#step-3-register-the-poller), then [attach the poller to the central server or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). ## Prerequisites diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md index 9778cdd95aba..d18e21e5ac6e 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md @@ -15,7 +15,7 @@ You must run the installation procedure as a privileged user. > When you run a command, check its output. If you get an error message, stop the procedure and fix the issue. -We recommend encrypting the communications of both the web server and the database, even though these steps are not required for Centreon to work. The procedure below sets up this encryption. In some cases (e.g. when running quick tests), you may want a non-secure setup: just skip [step 3: Set up the TLS configuration](#step-3-set-up-the-tls-configuration). +We recommend encrypting the communications of both the web server and the database, even though these steps are not required for Centreon to work. The procedure below sets up this encryption. In some cases (e.g. when running quick tests), you may want a non-secure setup: just skip step 3: Set up the TLS configuration. From 92ee0878edb79b3c8da0cbdb175204b7b3402f68 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 8 Sep 2026 18:20:12 +0200 Subject: [PATCH 051/179] Unbreak build --- .../installation/installation-of-a-poller/unattended.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md index dc2d9bcad308..8c3c99304796 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md @@ -78,4 +78,4 @@ The script will perform all installation steps. You must then [register the poll The script writes a full log, including any errors, to `/var/log/centreon-unattended-.log`. -2. Once the script has run, [register the poller](./using-packages.md#step-3-register-the-server), then [attach the poller to the central server or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). +2. Once the script has run, [register the poller](./using-packages.md#step-3-register-the-poller), then [attach the poller to the central server or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). From ec08e0dabee26a77bbab7343b6666f54ec4ef0b0 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 10 Sep 2026 18:15:02 +0200 Subject: [PATCH 052/179] Single-source parts of the install procedure + updates --- .../installation/_centreon-repository.mdx | 38 +++ .../installation/_dependencies-repository.mdx | 99 ++++++ .../installation/_interface-tls-conf.mdx | 98 ++++++ .../installation/_tls-certificates.mdx | 78 +++++ .../using-packages.md | 318 +----------------- .../using-packages.md | 112 ++---- .../using-packages.md | 289 +++------------- .../migrate/migrate-from-debian-to-debian.md | 41 ++- .../migrate/migrate-from-el-to-debian.md | 30 +- .../migrate/migrate-from-el-to-el.md | 47 ++- 10 files changed, 494 insertions(+), 656 deletions(-) create mode 100644 versioned_docs/version-26.10/installation/_centreon-repository.mdx create mode 100644 versioned_docs/version-26.10/installation/_dependencies-repository.mdx create mode 100644 versioned_docs/version-26.10/installation/_interface-tls-conf.mdx create mode 100644 versioned_docs/version-26.10/installation/_tls-certificates.mdx diff --git a/versioned_docs/version-26.10/installation/_centreon-repository.mdx b/versioned_docs/version-26.10/installation/_centreon-repository.mdx new file mode 100644 index 000000000000..acbfbd0feb4b --- /dev/null +++ b/versioned_docs/version-26.10/installation/_centreon-repository.mdx @@ -0,0 +1,38 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + + + + +```shell +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo +dnf clean all --enablerepo=* +dnf update +``` + + + + +```shell +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo +dnf clean all --enablerepo=* +dnf update -y +``` + + + + +```shell +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list +echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list +``` + +Then import the repository key: + +```shell +wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 +apt update +``` + + + \ No newline at end of file diff --git a/versioned_docs/version-26.10/installation/_dependencies-repository.mdx b/versioned_docs/version-26.10/installation/_dependencies-repository.mdx new file mode 100644 index 000000000000..3e89470754b3 --- /dev/null +++ b/versioned_docs/version-26.10/installation/_dependencies-repository.mdx @@ -0,0 +1,99 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + + + + +```shell +dnf install dnf-plugins-core +dnf install epel-release +dnf config-manager --set-enabled crb +``` + +Install and enable PHP 8.4 using the following commands: + +```shell +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y +``` + + + + +```shell +dnf install -y dnf-plugins-core +dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms +``` + +If your server is a Cloud RHEL instance, you will have to execute the following command: + +```shell +dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms +``` + +Install and enable PHP 8.4 using the following commands: + +```shell +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y +``` + + + + +```shell +dnf install dnf-plugins-core +dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +dnf config-manager --set-enabled ol9_codeready_builder +``` + +Install and enable PHP 8.4 using the following commands: + +```shell +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y +``` + + + + +```shell +dnf install dnf-plugins-core -y +dnf config-manager --set-enabled crb +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +``` + + + + +```shell +dnf install dnf-plugins-core -y +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms +``` + +If your server is a Cloud RHEL instance, you will have to execute the following command: + +```shell +dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms +``` + + + + +```shell +dnf install dnf-plugins-core -y +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +dnf config-manager --set-enabled ol10_codeready_builder +``` + + + + +```shell +apt update && apt install -y lsb-release ca-certificates apt-transport-https wget gnupg2 curl sudo +``` + + + diff --git a/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx b/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx new file mode 100644 index 000000000000..f84256a593d9 --- /dev/null +++ b/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx @@ -0,0 +1,98 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + + + + +1. Configure Apache TLS: + +```shell +dnf install -y mod_ssl +echo 'Listen 443 https' > /etc/httpd/conf.d/ssl.conf +``` + +2. Enter the correct certificate paths in Centreon's Apache HTTPS configuration: + +```shell +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ + /usr/share/centreon/examples/centreon-apache-https.conf \ + > /etc/httpd/conf.d/00-centreon-tls.conf +``` + +3. Enable and restart Centreon services: + +```shell +systemctl daemon-reload +``` + + + + +1. Configure Apache TLS: + +```shell +dnf install -y mod_ssl +echo 'Listen 443 https' > /etc/httpd/conf.d/ssl.conf +``` + +2. Enter the correct certificate paths in Centreon's Apache HTTPS configuration: + +```shell +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ + /usr/share/centreon/examples/centreon-apache-https.conf \ + > /etc/httpd/conf.d/00-centreon-tls.conf +``` + +3. Enable and restart Centreon services: + +```shell +systemctl daemon-reload +``` + + + + + +```shell +systemctl restart mariadb +``` + + + + +```shell +systemctl restart mysqld +``` + + + + + + + + +Enable every module the official Centreon HTTPS references: + +```shell +a2enmod ssl proxy proxy_fcgi headers deflate rewrite +``` + +Enter the correct certificate paths in Centreon's Apache HTTPS configuration: + +```shell +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ + /usr/share/centreon/examples/centreon-apache-https.conf \ + > /etc/apache2/sites-available/00-centreon-tls.conf +``` + +Enable the configuration you just applied. + +```shell +a2ensite 00-centreon-tls +``` + + + diff --git a/versioned_docs/version-26.10/installation/_tls-certificates.mdx b/versioned_docs/version-26.10/installation/_tls-certificates.mdx new file mode 100644 index 000000000000..e11608b4a4cb --- /dev/null +++ b/versioned_docs/version-26.10/installation/_tls-certificates.mdx @@ -0,0 +1,78 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +Generate the certificates the platform will need to connect to the web interface and to the database. + +1. On the central server, install **openssl**. + + + + + ```shell + dnf install openssl -y + ``` + + + + + ```shell + dnf install openssl -y + ``` + + + + + ```shell + apt install -y openssl + ``` + + + + +2. Download the **entrypoint.sh** script. + +3. Run the script to generate a root CA and a certificate for this host. Replace \ by the IP address of your machine: + + ```shell + mkdir -p /etc/pki/centreon-tls + OUT=/etc/pki/centreon-tls \ + entrypoint.sh localhost 127.0.0.1 + cd / + ``` + + The command outputs the following files in **/etc/pki/centreon-tls/**: + + * rootCA.pem (public) + * server.pem (server certificate) + * server-key.pem (server private key) + * CA/rootCA.\{key,pem\} (set the following permissions root:root, mode 0400) + +4. Install the root CA into the OS trust store: + + + + + ```shell + cp /etc/pki/centreon-tls/rootCA.pem /etc/pki/ca-trust/source/anchors/centreon-dev.crt + update-ca-trust extract + ``` + + + + + ```shell + cp /etc/pki/centreon-tls/rootCA.pem /etc/pki/ca-trust/source/anchors/centreon-dev.crt + update-ca-trust extract + ``` + + + + + ```shell + cp /etc/pki/centreon-tls/rootCA.pem /usr/local/share/ca-certificates/centreon-dev.crt + ``` + + + + +5. If you are using a remote database, also execute this procedure on the machine that will host the remote database, then copy the root CA certificate of the database machine to the central server's trust store. \ No newline at end of file diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index 5bb5a5ab021d..ea006440bdd1 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -11,6 +11,10 @@ import DatabaseRemoteInstall from '../_database-remote-install.mdx'; import DatabaseEnableRestart from '../_database-enable-restart.mdx'; import DatabaseTlsConf from '../_database-tls-conf.mdx'; import InstallCommon from '../_install-common.mdx'; +import TlsCertificates from '../_tls-certificates.mdx'; +import InterfaceTlsConf from '../_interface-tls-conf.mdx'; +import CentreonRepository from '../_centreon-repository.mdx'; +import DependenciesRepository from '../_dependencies-repository.mdx'; You must run the installation procedure as a privileged user. @@ -24,103 +28,7 @@ We recommend encrypting the communications of both the web server and the databa #### Dependencies - - - -```shell -dnf install dnf-plugins-core -dnf install epel-release -dnf config-manager --set-enabled crb -``` - -Install and enable PHP 8.4 using the following commands: - -```shell -dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm -dnf module switch-to php:remi-8.4/common -y -``` - - - - -```shell -dnf install -y dnf-plugins-core -dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms -``` - -If your server is a Cloud RHEL instance, you will have to execute the following command: - -```shell -dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms -``` - -Install and enable PHP 8.4 using the following commands: - -```shell -dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm -dnf module switch-to php:remi-8.4/common -y -``` - - - - -```shell -dnf install dnf-plugins-core -dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -dnf config-manager --set-enabled ol9_codeready_builder -``` - -Install and enable PHP 8.4 using the following commands: - -```shell -dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm -dnf module switch-to php:remi-8.4/common -y -``` - - - - -```shell -dnf install dnf-plugins-core -y -dnf install epel-release -y -dnf config-manager --set-enabled crb -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm -``` - - - - -```shell -dnf install dnf-plugins-core -y -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms -``` - -If your server is a Cloud RHEL instance, you will have to execute the following command: - -```shell -dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms -``` - - - - -```shell -dnf install dnf-plugins-core -y -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm -dnf config-manager --set-enabled ol10_codeready_builder -``` - - - - -```shell -apt update && apt install -y lsb-release ca-certificates apt-transport-https wget gnupg2 curl sudo -``` - - - + #### Database repository @@ -128,47 +36,7 @@ apt update && apt install -y lsb-release ca-certificates apt-transport-https wge #### Centreon repository -To install Centreon software, you should first install the Centreon repository. - -Install the Centreon repository using this command: - - - - -```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -dnf clean all --enablerepo=* -dnf update -``` - - - - -```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo -dnf clean all --enablerepo=* -dnf update -y -``` - - - - -To install the Centreon repositories, execute the following command: - -```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -Then import the repository key: - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - + ## Step 2: Install the central server and the database @@ -188,81 +56,7 @@ a remote database on a dedicated server. ### Generate the certificates -Generate the certificates the platform will need to connect to the web interface and to the database. - -1. On the central server, install **openssl**. - - - - - ```shell - dnf install openssl -y - ``` - - - - - ```shell - dnf install openssl -y - ``` - - - - - ```shell - apt install -y openssl - ``` - - - - -2. Download the **entrypoint.sh** script. - -3. Run the script to generate a root CA and a certificate for this host. Replace \ by the IP address of your machine: - - ```shell - mkdir -p /etc/pki/centreon-tls - OUT=/etc/pki/centreon-tls \ - entrypoint.sh localhost 127.0.0.1 - cd / - ``` - - The command outputs the following files in **/etc/pki/centreon-tls/**: - - * rootCA.pem (public) - * server.pem (server certificate) - * server-key.pem (server private key) - * CA/rootCA.\{key,pem\} (set the following permissions root:root, mode 0400) - -4. Install the root CA into the OS trust store: - - - - - ```shell - cp /etc/pki/centreon-tls/rootCA.pem /etc/pki/ca-trust/source/anchors/centreon-dev.crt - update-ca-trust extract - ``` - - - - - ```shell - cp /etc/pki/centreon-tls/rootCA.pem /etc/pki/ca-trust/source/anchors/centreon-dev.crt - update-ca-trust extract - ``` - - - - - ```shell - cp /etc/pki/centreon-tls/rootCA.pem /usr/local/share/ca-certificates/centreon-dev.crt - ``` - - - - -5. If you are using a remote database, also execute this procedure on the machine that will host the remote database, then copy the root CA certificate of the database machine to the central server's trust store. + ### For the database @@ -270,103 +64,9 @@ Generate the certificates the platform will need to connect to the web interface ### For the web interface -This section describes how to set up a TLS connection between the central server and the web interface. - - - - -1. Configure Apache TLS: - -```shell -dnf install -y mod_ssl -echo 'Listen 443 https' > /etc/httpd/conf.d/ssl.conf -``` - -2. Enter the correct certificate paths in Centreon's Apache HTTPS configuration: - -```shell -sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ - -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ - /usr/share/centreon/examples/centreon-apache-https.conf \ - > /etc/httpd/conf.d/00-centreon-tls.conf -``` - -3. Enable and restart Centreon services: - -```shell -systemctl daemon-reload -``` - - - - -1. Configure Apache TLS: +This section describes how to set up a TLS connection between the central server and its web interface. -```shell -dnf install -y mod_ssl -echo 'Listen 443 https' > /etc/httpd/conf.d/ssl.conf -``` - -2. Enter the correct certificate paths in Centreon's Apache HTTPS configuration: - -```shell -sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ - -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ - /usr/share/centreon/examples/centreon-apache-https.conf \ - > /etc/httpd/conf.d/00-centreon-tls.conf -``` - -3. Enable and restart Centreon services: - -```shell -systemctl daemon-reload -``` - - - - - -```shell -systemctl restart mariadb -``` - - - - -```shell -systemctl restart mysqld -``` - - - - - - - - -Enable every module the official Centreon HTTPS references: - -```shell -a2enmod ssl proxy proxy_fcgi headers deflate rewrite -``` - -Enter the correct certificate paths in Centreon's Apache HTTPS configuration: - -```shell -sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ - -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ - /usr/share/centreon/examples/centreon-apache-https.conf \ - > /etc/apache2/sites-available/00-centreon-tls.conf -``` - -Enable the configuration you just applied. - -```shell -a2ensite 00-centreon-tls -``` - - - + ## Step 4: Configuration diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-packages.md index 96fd8c2b8d73..d16d920b65f6 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-packages.md @@ -13,7 +13,7 @@ You must run the installation procedure as a privileged user. -### Server name + ### Install the repositories - - - -#### Redhat PowerTools repository +#### Dependencies -To install Centreon, you will need to enable the official PowerTools repository -supported by Redhat. + + -Enable the PowerTools repository using these commands: ```shell -dnf -y install dnf-plugins-core epel-release -dnf config-manager --set-enabled powertools +dnf install dnf-plugins-core +dnf install epel-release +dnf config-manager --set-enabled crb ``` - - -#### Redhat CodeReady Builder repository - -To install Centreon, you will need to enable the official CodeReady Builder -supported by Redhat. - -Enable the CodeReady Builder repository using these commands: + ```shell -dnf -y install dnf-plugins-core https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms +dnf install -y dnf-plugins-core +dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms ``` If your server is a Cloud RHEL instance, you will have to execute the following command: ```shell -dnf config-manager --set-enabled codeready-builder-for-rhel-8-rhui-rpms +dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms ``` - - - -#### Oracle CodeReady Builder repository - -To install Centreon, you will need to enable the official Oracle CodeReady -Builder repository supported by Oracle. - -Enable the repository using these commands: + ```shell -dnf install dnf-plugins-core -dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -dnf config-manager --set-enabled ol8_codeready_builder +dnf install -y dnf-plugins-core +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +dnf config-manager --set-enabled ol9_codeready_builder ``` - - -To install Centreon you will need to install the **CodeReady Builder** repository. - -Run the following commands: + ```shell -dnf install dnf-plugins-core -dnf install epel-release +dnf install dnf-plugins-core -y dnf config-manager --set-enabled crb +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm ``` - - -To install Centreon you will need to install the **CodeReady Builder** repository. - -Run the following commands: + ```shell -dnf install -y dnf-plugins-core -dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms +dnf install dnf-plugins-core -y +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms ``` If your server is a Cloud RHEL instance, you will have to execute the following command: @@ -113,23 +88,16 @@ dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms ``` - - -To install Centreon you will need to install the **CodeReady Builder** repository. - -Run the following commands: + ```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -dnf config-manager --set-enabled ol9_codeready_builder -dnf install -y epel-release +dnf install dnf-plugins-core -y +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +dnf config-manager --set-enabled ol10_codeready_builder ``` - - -Install the following dependencies: + ```shell apt update && apt install lsb-release ca-certificates apt-transport-https software-properties-common wget gnupg2 curl @@ -140,10 +108,6 @@ apt update && apt install lsb-release ca-certificates apt-transport-https softwa #### Centreon repository -To install Centreon software, you should first install the Centreon repository. - -Install the Centreon repository using this command: - @@ -167,8 +131,6 @@ dnf update -To install the Centreon repository, execute the following command line: - ```shell echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list @@ -184,26 +146,26 @@ apt update -## Step 2: Installation +## Step 2: Install the server To install the monitoring engine, run the following command: - + ```shell dnf install -y centreon-poller ``` - + ```shell dnf install -y centreon-poller ``` - + ```shell apt install -y --no-install-recommends centreon-poller @@ -231,7 +193,7 @@ Restart Centreon Engine: systemctl restart centengine ``` -## Step 3: Register the poller + -## Step 4: Attach the poller to a central or remote server +## Step 3: Attach the poller to a central or remote server Go to [Attach a poller to a central or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). -## Step 5: Secure your platform +## Step 4: Secure your platform Remember to secure your Centreon platform following our [recommendations](../../administration/secure-platform.md). diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md index d18e21e5ac6e..cc1348d42682 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md @@ -9,179 +9,24 @@ import DatabaseRepository from '../_database-repository.mdx'; import DatabaseLocalInstall from '../_database-local-install.mdx'; import DatabaseRemoteInstall from '../_database-remote-install.mdx'; import DatabaseEnableRestart from '../_database-enable-restart.mdx'; +import DatabaseTlsConf from '../_database-tls-conf.mdx'; import InstallCommon from '../_install-common.mdx'; +import TlsCertificates from '../_tls-certificates.mdx'; +import InterfaceTlsConf from '../_interface-tls-conf.mdx'; +import CentreonRepository from '../_centreon-repository.mdx'; +import DependenciesRepository from '../_dependencies-repository.mdx'; You must run the installation procedure as a privileged user. > When you run a command, check its output. If you get an error message, stop the procedure and fix the issue. -We recommend encrypting the communications of both the web server and the database, even though these steps are not required for Centreon to work. The procedure below sets up this encryption. In some cases (e.g. when running quick tests), you may want a non-secure setup: just skip step 3: Set up the TLS configuration. +We recommend encrypting the communications of both the web server and the database, even though these steps are not required for Centreon to work. The procedure below sets up this encryption. In some cases (e.g. when running quick tests), you may want a non-secure setup: just skip [step 3: Set up the TLS configuration](#step-3-set-up-the-tls-configuration). -### Install the repositories +#### Dependencies - - - -Run the following commands: - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -dnf config-manager --set-enabled 'powertools' -``` - -Enable PHP 8.2 using the following commands: - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -#### CodeReady Builder repository - -To install Centreon you will need to install the **CodeReady Builder** repository. - -Run the following commands: - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` - -If your server is a Cloud RHEL instance, you will have to execute the following command: - -```shell -dnf config-manager --set-enabled codeready-builder-for-rhel-8-rhui-rpms -``` - -Enable PHP 8.2 using the following commands: - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -#### CodeReady Builder repository - -To install Centreon you will need to install the **CodeReady Builder** repository. - -Run the following commands: - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -dnf config-manager --set-enabled ol8_codeready_builder -``` - -Enable PHP 8.2 using the following commands: -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -To install Centreon you will need to install the **CodeReady Builder** repository. - -Run the following commands: - -```shell -dnf install dnf-plugins-core -dnf install epel-release -dnf config-manager --set-enabled crb -``` - -Enable PHP 8.2 using the following commands: - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -To install Centreon you will need to install the **CodeReady Builder** repository. - -Run the following commands: - -```shell -dnf install -y dnf-plugins-core -dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms -``` - -If your server is a Cloud RHEL instance, you will have to execute the following command: - -```shell -dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms -``` - -Enable PHP 8.2 using the following commands: - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -To install Centreon you will need to install the **CodeReady Builder** repository. - -Run the following commands: - -```shell -dnf install dnf-plugins-core -dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -dnf config-manager --set-enabled ol9_codeready_builder -``` - -Enable PHP 8.2 using the following commands: - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -#### Install dependencies - -Install the following dependencies: - -```shell -apt update && apt install lsb-release ca-certificates apt-transport-https software-properties-common wget gnupg2 curl -``` - -#### Add Sury APT repository for PHP 8.2 - -To install the Sury repository, execute the following command: - -```shell -echo "deb https://packages.sury.org/php/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/sury-php.list -``` - -Then import the repository key: - -```shell -wget -O- https://packages.sury.org/php/apt.gpg | gpg --dearmor | tee /etc/apt/trusted.gpg.d/php.gpg > /dev/null 2>&1 -apt update -``` - - - + #### Database repository @@ -189,53 +34,11 @@ apt update #### Centreon repository -To install Centreon software, you should first install the Centreon repository. + -Install the Centreon repository using this command: +## Step 2: Install the server - - - -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -dnf clean all --enablerepo=* -dnf update -``` - - - - -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -dnf clean all --enablerepo=* -dnf update -``` - - - - -To install the Centreon repository, execute the following command: - -```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -Then import the repository key: - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -## Step 2: Installation - -This section describes how to install a Centreon Remote Server. +This section describes how to install a Centreon remote server. You can install this server with a local database on the server or a remote database on a dedicated server. @@ -252,7 +55,23 @@ You can now move on to the [next step](#step-3-configuration). -## Step 3: Configuration +## Step 3: Set up the TLS configuration + +### Generate the certificates + + + +### For the database + + + +### For the web interface + +This section describes how to set up a TLS connection between the remote server and its web interface. + + + +## Step 4: Configuration ### Server name @@ -272,7 +91,7 @@ To make services start automatically during system bootup, run these commands on the central server: - + ```shell systemctl enable php-fpm httpd centreon cbd centengine gorgoned snmptrapd centreontrapd snmpd @@ -281,7 +100,7 @@ systemctl start crond ``` - + ```shell systemctl enable php-fpm httpd centreon cbd centengine gorgoned snmptrapd centreontrapd snmpd @@ -290,7 +109,7 @@ systemctl start crond ``` - + ```shell systemctl enable php8.2-fpm apache2 centreon cbd centengine gorgoned centreontrapd snmpd snmptrapd @@ -303,53 +122,27 @@ Then execute the following command (on the remote server if you are using a loca -### Secure the database - -If you have installed the Centreon server with a local database, it is mandatory to secure the database's root access before installing Centreon. Run the following command: - - - - -```shell -mariadb-secure-installation -``` - - - - -```shell -mysql_secure_installation -``` - - - - -* Answer **yes** to all questions except "Disallow root login remotely?". -* It is mandatory to set a password for the **root** user of the database. You will need this password during the [web installation](../web-and-post-installation.md). - -> For more information, please see the [official MariaDB documentation](https://mariadb.com/kb/en/mysql_secure_installation/). - -## Step 4: Web installation +## Step 5: Web installation 1. Start the Apache server with the following command: - + ```shell systemctl start httpd ``` - + ```shell systemctl start httpd ``` - + ```shell systemctl start apache2 @@ -365,7 +158,7 @@ systemctl start apache2 > In the step **Initialization of the monitoring**, only actions 6 to 8 need to be done. -## Step 5: Register the server + ## Step 6: Extend local DBMS rights @@ -502,12 +295,12 @@ SET GLOBAL local_infile=1; exit ``` -## Step 7: Add the Remote Server to the configuration +## Step 7: Attach the remote server to the central server -Go to the -[Add a Remote Server to configuration](../../monitoring/monitoring-servers/add-a-remote-server-to-configuration.md). +Go to +[Attach a remote server to a central server](../../monitoring/monitoring-servers/add-a-remote-server-to-configuration.md). ## Step 8: Secure your platform Remember to secure your Centreon platform following our -[recommendations](../../administration/secure-platform.md) +[recommendations](../../administration/secure-platform.md). diff --git a/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md b/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md index bb142b48bd18..aa4a91acc232 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md @@ -1,19 +1,18 @@ --- id: migrate-from-debian-to-debian -title: Migrate from Debian 11 to Debian 12 -description: "Migrate a Centreon platform from Debian 11 to Debian 12" +title: Migrate to a newer Debian version +description: "Migrate a Centreon platform to a newer Debian version" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; ## Prerequisites -This procedure only applies if you wish to migrate from Debian 11 to Debian 12, on another server. +This procedure only applies if you wish to migrate from Debian to a newer version of Debian, on another server. All servers (central, remote and pollers) in your architecture must have the same major version of Centreon. It is also recommended that they have the same minor version. -Be sure that you have fully backed up your environment for the following -servers: +Be sure that you have fully backed up your environment for the following servers: - Central server - Database server @@ -26,7 +25,7 @@ If you use Open Ticket providers with custom configurations, [make a backup of t ### Step 1: Install the new central server -1. Install your new Debian 12 OS. +1. Install your new Debian OS. 2. Install a new Centreon central server from [packages](../installation/installation-of-a-central-server/using-packages.md), until you complete the installation process by connecting to the Centreon web interface. @@ -94,12 +93,25 @@ complete the installation process by connecting to the Centreon web interface. mysqldump -u root -p centreon_storage > /tmp/centreon_storage.sql ``` -2. On the old server, stop MariaDB: +2. On the old server, stop your database: + + + ```shell systemctl stop mariadb ``` + + + + ```shell + systemctl stop mysql + ``` + + + + 3. On the old server, export the dumps to the new Centreon database server (make sure you have enough space for large database dumps): @@ -148,12 +160,25 @@ create them again:: mysql_upgrade -u root -p ``` -7. Start the MariaDB process on the new server: +7. Start the database process on the new server: + + + ```shell systemctl start mariadb ``` + + + + ```shell + systemctl start mysql + ``` + + + + > Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md b/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md index f7f374bc1d41..14effc3486a4 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md @@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem'; This procedure only applies if the following conditions are met: -- You wish to migrate from a 64-bit EL-type OS to Debian. For instance, if you want to migrate from CentOS 7 to Debian 12. +- You wish to migrate from a 64-bit EL-type OS to Debian. For instance, if you want to migrate from CentOS 7 to Debian 13. - Your version of Centreon is 18.10 or newer and you wish to upgrade to the latest version of Centreon. If you wish to migrate from an older version, [contact the Centreon support team](https://support.centreon.com). All servers (central, remote and pollers) in your architecture must have the same major version of Centreon. It is also recommended that they have the same minor version. @@ -97,12 +97,25 @@ complete the installation process by connecting to the Centreon web interface. mysqldump -u root -p centreon_storage > /tmp/centreon_storage.sql ``` -2. On the old server, stop MariaDB: +2. On the old server, stop the database: + + + ```shell systemctl stop mariadb ``` + + + + ```shell + systemctl stop mysql + ``` + + + + 3. On the old server, export the dumps to the new Centreon database server (make sure you have enough space for large database dumps): @@ -153,10 +166,23 @@ create them again:: 7. Start the MariaDB process on the new server: + + + ```shell systemctl start mariadb ``` + + + + ```shell + systemctl start mysql + ``` + + + + > Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins diff --git a/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md b/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md index 622fbf20d6d5..b4fa14a8dd4c 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md @@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem'; This procedure only applies if the following conditions are met: -- You wish to migrate from a 64-bit EL-type OS to another supported 64-bit EL-type OS. For instance, if you want to migrate from a CentOS 7 to an Alma 8 or 9. +- You wish to migrate from a 64-bit EL-type OS to another supported 64-bit EL-type OS. For instance, if you want to migrate from a CentOS 7 to an Alma 9. - Your version of Centreon is 18.10 or newer. All servers (central, remote and pollers) in your architecture must have the same major version of Centreon. It is also recommended that they have the same minor version. @@ -40,14 +40,14 @@ complete the installation process by connecting to the Centreon web interface. 3. Perform software and system updates: - + ```shell dnf update ``` - + ```shell dnf update @@ -99,12 +99,25 @@ dnf update mysqldump -u root -p centreon_storage > /tmp/centreon_storage.sql ``` -2. On the old server, stop MariaDB: +2. On the old server, stop the database: + + + ```shell systemctl stop mariadb ``` + + + + ```shell + systemctl stop mysql + ``` + + + + 3. On the old server, export the dumps to the new Centreon database server (make sure you have enough space for large database dumps): @@ -153,12 +166,25 @@ create them again: mysql_upgrade -u root -p ``` -7. Start the MariaDB process on the new server: +7. Start the database process on the new server: + + + ```shell systemctl start mariadb ``` + + + + ```shell + systemctl start mysql + ``` + + + + > Replace **\** by the IP address of the new Centreon server. ### Step 4: Synchronize the plugins @@ -166,13 +192,6 @@ create them again: If you only use Centreon plugins, reinstall them on the new server: - - -```shell -dnf install centreon-plugin-\* -``` - - ```shell @@ -180,10 +199,10 @@ dnf install centreon-plugin-\* ``` - + ```shell -apt install centreon-plugin-\* +dnf install centreon-plugin-\* ``` From 77946642b523d514583ede1b5906850b8b8cedc9 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 11 Sep 2026 15:34:40 +0200 Subject: [PATCH 053/179] Unbreak build --- .../installation/installation-of-a-poller/unattended.md | 2 +- .../installation/installation-of-a-remote-server/unattended.md | 2 +- .../installation-of-a-remote-server/using-packages.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md index 8c3c99304796..4377409bca3c 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md @@ -10,7 +10,7 @@ To install a poller quickly, you can use a script. This is useful when you need to install several pollers with identical settings, when you install from a deployment tool or CI pipeline, or when you have no interactive access to the target machine. -The script will perform all installation steps. You must then [register the poller](./using-packages.md#step-3-register-the-poller), then [attach the poller to the central server or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). +The script will perform all installation steps. You must then [attach the poller to the central server or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). ## Prerequisites diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md index ccd463ae8f96..5c171b219970 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md @@ -94,7 +94,7 @@ To install a remote server quicker, you can use a script. This will perform all 2. Go to http(s)://\/centreon (where \ is your server's IP address) and log in. Then follow the [initialization of the monitoring](../web-and-post-installation.md#initialization-of-the-monitoring) steps. - 3. Once the script has run, carry out [steps 4 to 8 of the standard installation procedure for a remote server](./using-packages.md#step-5-register-the-server). + 3. Once the script has run, carry out [steps 5 to 8 of the standard installation procedure for a remote server](./using-packages.md#step-5-web-installation). 4. Start using Centreon: follow our [Getting started](../../getting-started/welcome.md) guide to start monitoring your resources. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md index cc1348d42682..b4ccc984ee64 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md @@ -47,7 +47,7 @@ a remote database on a dedicated server. -You can now move on to the [next step](#step-3-configuration). +You can now move on to the [next step](#step-3-set-up-the-tls-configuration). From 08e7c3cde66b9904cb3b3972db865b2e22f47451 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 11 Sep 2026 15:45:36 +0200 Subject: [PATCH 054/179] Fix link --- .../installation/installation-of-a-poller/unattended.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md index 4377409bca3c..d451b7f204ee 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/unattended.md @@ -78,4 +78,4 @@ The script will perform all installation steps. You must then [attach the poller The script writes a full log, including any errors, to `/var/log/centreon-unattended-.log`. -2. Once the script has run, [register the poller](./using-packages.md#step-3-register-the-poller), then [attach the poller to the central server or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). +2. Once the script has run, [attach the poller to the central server or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). From adeefdd2510b37c51018806b1042cc9fbb4e97d0 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 15 Sep 2026 10:17:13 +0200 Subject: [PATCH 055/179] MON-209138 sourceguardian --- versioned_docs/version-26.10/upgrade/_upgrade-central.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index 71b520b7acd2..cc399a0b7cf7 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -74,6 +74,7 @@ You need to install the Remi repo and the switch the PHP stream from version {pr ```shell dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +rpm -e --nodeps php-sourceguardian-loader dnf module switch-to php:remi-8.4/common -y ``` From fa8d326ca32d5a7bbcef06df5a7d469fffd5e4be Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 15 Sep 2026 15:29:22 +0200 Subject: [PATCH 056/179] Translate upgrade matrix into English + fix 26.10 dropdown --- .../version-26.10/upgrade/upgrade-matrix.mdx | 2 +- .../version-24.10/upgrade/upgrade-matrix.mdx | 96 ++++++++--------- .../version-25.10/upgrade/upgrade-matrix.mdx | 100 +++++++++--------- .../version-26.10/upgrade/upgrade-matrix.mdx | 64 +++++------ 4 files changed, 131 insertions(+), 131 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx index 85ad3df4af26..38257c40ac23 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -41,7 +41,7 @@ export const UpgradeTable = () => {
{[ { id: 'version', value: version, setter: setVersion, label: 'Toutes les versions', options: ['25.10','24.10','24.04','23.10','23.04','22.10 et antérieures'] }, - { id: 'os', value: os, setter: setOs, label: 'Tous les OS', options: ['RHEL/Oracle/Alma Linux 8','RHEL/Oracle/Alma Linux 9','Debian 11','Debian 12'] }, + { id: 'os', value: os, setter: setOs, label: 'Tous les OS', options: ['RHEL/Oracle/AlmaLinux 8','RHEL/Oracle/AlmaLinux 9','Debian 11','Debian 12'] }, { id: 'compat', value: compat, setter: setCompat, label: 'Compatibilité 26.10', options: null }, ].map(f => ( setVersion(e.target.value)}> - + {versions.map(v => )}

- {filtered.length} résultat{filtered.length > 1 ? 's' : ''} + {filtered.length} result{filtered.length > 1 ? 's' : ''}

- - - - + + + + @@ -122,8 +122,8 @@ export const UpgradeTable = () => { borderRadius: 12, fontSize: 12, fontWeight: 600, - background: r.compat === 'OUI' ? 'var(--ifm-color-success-contrast-background)' : 'var(--ifm-color-danger-contrast-background)', - color: r.compat === 'OUI' ? 'var(--ifm-color-success-dark)' : 'var(--ifm-color-danger-dark)', + background: r.compat === 'YES' ? 'var(--ifm-color-success-contrast-background)' : 'var(--ifm-color-danger-contrast-background)', + color: r.compat === 'YES' ? 'var(--ifm-color-success-dark)' : 'var(--ifm-color-danger-dark)', }}> {r.compat} @@ -137,18 +137,18 @@ export const UpgradeTable = () => { ); }; -Pour rappel, les OS supportés en version 24.10 sont les suivants : +As a reminder, the OSs supported in version 24.10 are the following: * RHEL/Oracle Linux/Alma Linux 8 -* RHEL/Oracle/Alma Linux 9 +* RHEL/Oracle Linux/Alma Linux 9 * Debian 12 (bookworm) -Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 8 ou 9, ou Debian 12. Pour toute autre version ou OS, vous devrez effectuer une [migration](../migrate/introduction.md). +This means that an upgrade is only possible if you were using version 20.10 or later, on RHEL/Oracle Linux/Alma Linux 8 or 9, or Debian 12. For any other version or OS, you will need to perform a [migration](../migrate/introduction.md). -## Montée de version ou migration ? +## Upgrade or migration? -{/* ## Cycle de vie des versions +{/* ## Version lifecycle -[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). */} \ No newline at end of file +[See the table of supported Centreon versions](../releases/lifecycle.md#maintenance-table-for-centreon-versions). */} \ No newline at end of file diff --git a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx index f910afcce080..aa484dc2c19e 100644 --- a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx @@ -1,6 +1,6 @@ --- id: upgrade-matrix -title: Matrice des montées de version possibles +title: Upgrade matrix --- import React, { useState } from 'react'; @@ -11,38 +11,38 @@ export const UpgradeTable = () => { const [compat, setCompat] = useState(''); const rows = [ - { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10.md' }, - { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10.md' }, - { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10.md' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-10.md' }, - { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04.md' }, - { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10.md' }, - { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04.md' }, - { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10.md' }, - { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-10.md' }, + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-10.md' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-10.md' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04.md' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-10.md' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-04.md' }, + { version: '22.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-10.md' }, + { version: '21.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-04.md' }, + { version: '20.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-20-10.md' }, + { version: '20.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '20.04', os: 'RHEL 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, ]; const versions = [...new Set(rows.map(r => r.version))]; @@ -86,31 +86,31 @@ export const UpgradeTable = () => {

- {filtered.length} résultat{filtered.length > 1 ? 's' : ''} + {filtered.length} result{filtered.length > 1 ? 's' : ''}

Version de départOS supporté à l'époqueOS toujours supporté en 24.10 ?Procédure à suivreStarting versionOS supported at the timeOS still supported in 24.10?Procedure to follow
- - - - + + + + @@ -125,8 +125,8 @@ export const UpgradeTable = () => { borderRadius: 12, fontSize: 12, fontWeight: 600, - background: r.compat === 'OUI' ? 'var(--ifm-color-success-contrast-background)' : 'var(--ifm-color-danger-contrast-background)', - color: r.compat === 'OUI' ? 'var(--ifm-color-success-dark)' : 'var(--ifm-color-danger-dark)', + background: r.compat === 'YES' ? 'var(--ifm-color-success-contrast-background)' : 'var(--ifm-color-danger-contrast-background)', + color: r.compat === 'YES' ? 'var(--ifm-color-success-dark)' : 'var(--ifm-color-danger-dark)', }}> {r.compat} @@ -140,18 +140,18 @@ export const UpgradeTable = () => { ); }; -Pour rappel, les OS supportés en version 25.10 sont les suivants : +As a reminder, the OSs supported in version 25.10 are the following: * RHEL/Oracle Linux/Alma Linux 8 * RHEL/Oracle Linux/Alma Linux 9 * Debian 12 (bookworm) -Cela signifie qu'une montée de version n'est possible que si vous utilisiez une version 20.10 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 8 ou 9, ou Debian 12. Pour toute autre version ou OS, vous devrez effectuer une [migration](../migrate/introduction.md). +This means that an upgrade is only possible if you were using version 20.10 or later, on RHEL/Oracle Linux/Alma Linux 8 or 9, or Debian 12. For any other version or OS, you will need to perform a [migration](../migrate/introduction.md). -## Montée de version ou migration ? +## Upgrade or migration? -{/* ## Cycle de vie des versions +{/* ## Version lifecycle -[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). */} \ No newline at end of file +[See the table of supported Centreon versions](../releases/lifecycle.md#maintenance-table-for-centreon-versions). */} \ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx index 85ad3df4af26..d754ac84cbba 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -1,6 +1,6 @@ --- id: upgrade-matrix -title: Matrice des montées de version possibles +title: Upgrade matrix --- import React, { useState } from 'react'; @@ -11,23 +11,23 @@ export const UpgradeTable = () => { const [compat, setCompat] = useState(''); const rows = [ - { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-25-10.md' }, - { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-10.md' }, - { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '22.10 et antérieures', os: 'Voir documentations correspondantes', compat: 'NON', proc: 'Migration depuis EL ou Debian', href: '../migrate/introduction.md' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction.md' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-25-10.md' }, + { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction.md' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction.md' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-24-10.md' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-24-04.md' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction.md' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction.md' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-23-10.md' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction.md' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction.md' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-23-04.md' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction.md' }, + { version: '22.10 and earlier', os: 'See the corresponding documentation', compat: 'NO', proc: 'Migration from EL or Debian', href: '../migrate/introduction.md' }, ]; const filtered = rows.filter(r => @@ -40,9 +40,9 @@ export const UpgradeTable = () => {
{[ - { id: 'version', value: version, setter: setVersion, label: 'Toutes les versions', options: ['25.10','24.10','24.04','23.10','23.04','22.10 et antérieures'] }, - { id: 'os', value: os, setter: setOs, label: 'Tous les OS', options: ['RHEL/Oracle/Alma Linux 8','RHEL/Oracle/Alma Linux 9','Debian 11','Debian 12'] }, - { id: 'compat', value: compat, setter: setCompat, label: 'Compatibilité 26.10', options: null }, + { id: 'version', value: version, setter: setVersion, label: 'All versions', options: ['25.10','24.10','24.04','23.10','23.04','22.10 and earlier'] }, + { id: 'os', value: os, setter: setOs, label: 'All OSs', options: ['RHEL/Oracle/AlmaLinux 8','RHEL/Oracle/AlmaLinux 9','Debian 11','Debian 12'] }, + { id: 'compat', value: compat, setter: setCompat, label: '26.10 compatibility', options: null }, ].map(f => ( @@ -70,13 +70,13 @@ export const UpgradeTable = () => {

- {filtered.length} résultat{filtered.length > 1 ? 's' : ''} + {filtered.length} result{filtered.length > 1 ? 's' : ''}

Version de départOS supporté à l'époqueOS toujours supporté en 25.10 ?Procédure à suivreStarting versionOS supported at the timeOS still supported in 25.10?Procedure to follow
- {['Version de départ', 'OS de départ', 'OS supporté en 26.10', 'Procédure à suivre'].map(h => ( + {['Starting version', 'Starting OS', 'OS supported in 26.10', 'Procedure to follow'].map(h => ( + ))} diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx index dae65a6548b8..a67d74c2bd86 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx @@ -4,45 +4,51 @@ title: Matrice des montées de version possibles --- import React, { useState } from 'react'; +import Link from '@docusaurus/Link'; +import { useLocation } from '@docusaurus/router'; export const UpgradeTable = () => { const [version, setVersion] = useState(''); const [os, setOs] = useState(''); const [compat, setCompat] = useState(''); + // Resolve links against the docs root of the current version/locale instead of + // the browser URL: with trailingSlash, relative hrefs resolve one level too deep. + const docsRoot = useLocation().pathname.split('/upgrade/upgrade-matrix')[0] + '/'; + const rows = [ - { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10' }, - { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10' }, - { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, - { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-10' }, - { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, - { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04' }, - { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, - { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10' }, - { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04' }, - { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10' }, - { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-24-10' }, + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-24-10' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-24-10' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-24-04' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-24-04' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: 'migrate/introduction' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-24-04' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-23-10' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-23-10' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: 'migrate/introduction' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-23-04' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-23-04' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: 'migrate/introduction' }, + { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-22-10' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: 'migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-22-04' }, + { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: 'migrate/introduction' }, + { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-21-10' }, + { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-21-04' }, + { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-20-10' }, + { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, ]; const versions = [...new Set(rows.map(r => r.version))]; @@ -131,7 +137,7 @@ export const UpgradeTable = () => { {r.compat} - + ))} diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx index 79c4637a26cc..db077be1cce3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -4,30 +4,36 @@ title: Matrice des montées de version possibles --- import React, { useState } from 'react'; +import Link from '@docusaurus/Link'; +import { useLocation } from '@docusaurus/router'; export const UpgradeTable = () => { const [version, setVersion] = useState(''); const [os, setOs] = useState(''); const [compat, setCompat] = useState(''); + // Resolve links against the docs root of the current version/locale instead of + // the browser URL: with trailingSlash, relative hrefs resolve one level too deep. + const docsRoot = useLocation().pathname.split('/upgrade/upgrade-matrix')[0] + '/'; + const rows = [ - { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction' }, - { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-25-10' }, - { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction' }, - { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction' }, - { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-10' }, - { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction' }, - { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction' }, - { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-04' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction' }, - { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction' }, - { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-23-10' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction' }, - { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction' }, - { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-23-04' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction' }, - { version: '22.10 et antérieures', os: 'Voir documentations correspondantes', compat: 'NON', proc: 'Migration depuis EL ou Debian', href: '../migrate/introduction' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: 'migrate/introduction' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade/upgrade-from-25-10' }, + { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: 'migrate/introduction' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: 'migrate/introduction' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade/upgrade-from-24-10' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: 'migrate/introduction' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: 'migrate/introduction' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade/upgrade-from-24-04' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: 'migrate/introduction' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: 'migrate/introduction' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: 'migrate/introduction' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade/upgrade-from-23-10' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: 'migrate/introduction' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: 'migrate/introduction' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade/upgrade-from-23-04' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: 'migrate/introduction' }, + { version: '22.10 et antérieures', os: 'Voir documentations correspondantes', compat: 'NON', proc: 'Migration depuis EL ou Debian', href: 'migrate/introduction' }, ]; const filtered = rows.filter(r => @@ -110,7 +116,7 @@ export const UpgradeTable = () => { ))} diff --git a/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx index b581732c3657..6b23435f09f2 100644 --- a/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx @@ -4,42 +4,48 @@ title: Upgrade matrix --- import React, { useState } from 'react'; +import Link from '@docusaurus/Link'; +import { useLocation } from '@docusaurus/router'; export const UpgradeTable = () => { const [version, setVersion] = useState(''); const [os, setOs] = useState(''); const [compat, setCompat] = useState(''); + // Resolve links against the docs root of the current version/locale instead of + // the browser URL: with trailingSlash, relative hrefs resolve one level too deep. + const docsRoot = useLocation().pathname.split('/upgrade/upgrade-matrix')[0] + '/'; + const rows = [ - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, - { version: '22.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-10' }, - { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, - { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-04' }, - { version: '22.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, - { version: '21.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-10' }, - { version: '21.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-04' }, - { version: '20.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-20-10' }, - { version: '20.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '20.04', os: 'RHEL 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-24-04' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-24-04' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: 'migrate/introduction' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-24-04' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-23-10' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-23-10' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: 'migrate/introduction' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-23-04' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-23-04' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: 'migrate/introduction' }, + { version: '22.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-22-10' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: 'migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-22-04' }, + { version: '22.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: 'migrate/introduction' }, + { version: '21.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-21-10' }, + { version: '21.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-21-04' }, + { version: '20.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-20-10' }, + { version: '20.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '20.04', os: 'RHEL 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, ]; const versions = [...new Set(rows.map(r => r.version))]; @@ -128,7 +134,7 @@ export const UpgradeTable = () => { {r.compat} - + ))} diff --git a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx index 59b256f13026..7e2ce2e327f0 100644 --- a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx @@ -4,45 +4,51 @@ title: Upgrade matrix --- import React, { useState } from 'react'; +import Link from '@docusaurus/Link'; +import { useLocation } from '@docusaurus/router'; export const UpgradeTable = () => { const [version, setVersion] = useState(''); const [os, setOs] = useState(''); const [compat, setCompat] = useState(''); + // Resolve links against the docs root of the current version/locale instead of + // the browser URL: with trailingSlash, relative hrefs resolve one level too deep. + const docsRoot = useLocation().pathname.split('/upgrade/upgrade-matrix')[0] + '/'; + const rows = [ - { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-10' }, - { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-10' }, - { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-10' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, - { version: '22.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-10' }, - { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, - { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-04' }, - { version: '22.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, - { version: '21.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-10' }, - { version: '21.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-04' }, - { version: '20.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-20-10' }, - { version: '20.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, - { version: '20.04', os: 'RHEL 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-24-10' }, + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-24-10' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-24-10' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-24-04' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-24-04' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: 'migrate/introduction' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-24-04' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-23-10' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-23-10' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: 'migrate/introduction' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-23-04' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-23-04' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: 'migrate/introduction' }, + { version: '22.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-22-10' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: 'migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-22-04' }, + { version: '22.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: 'migrate/introduction' }, + { version: '21.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-21-10' }, + { version: '21.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-21-04' }, + { version: '20.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade/upgrade-from-20-10' }, + { version: '20.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, + { version: '20.04', os: 'RHEL 7', compat: 'NO', proc: 'Migration procedure from EL', href: 'migrate/introduction' }, ]; const versions = [...new Set(rows.map(r => r.version))]; @@ -131,7 +137,7 @@ export const UpgradeTable = () => { {r.compat} - + ))} diff --git a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx index e193b5a78806..dc10a1eeb228 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -4,30 +4,36 @@ title: Upgrade matrix --- import React, { useState } from 'react'; +import Link from '@docusaurus/Link'; +import { useLocation } from '@docusaurus/router'; export const UpgradeTable = () => { const [version, setVersion] = useState(''); const [os, setOs] = useState(''); const [compat, setCompat] = useState(''); + // Resolve links against the docs root of the current version/locale instead of + // the browser URL: with trailingSlash, relative hrefs resolve one level too deep. + const docsRoot = useLocation().pathname.split('/upgrade/upgrade-matrix')[0] + '/'; + const rows = [ - { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction' }, - { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-25-10' }, - { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction' }, - { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction' }, - { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-24-10' }, - { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction' }, - { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction' }, - { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-24-04' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction' }, - { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction' }, - { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-23-10' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction' }, - { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction' }, - { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-23-04' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction' }, - { version: '22.10 and earlier', os: 'See the corresponding documentation', compat: 'NO', proc: 'Migration from EL or Debian', href: '../migrate/introduction' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: 'migrate/introduction' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade/upgrade-from-25-10' }, + { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: 'migrate/introduction' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: 'migrate/introduction' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade/upgrade-from-24-10' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: 'migrate/introduction' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: 'migrate/introduction' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade/upgrade-from-24-04' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: 'migrate/introduction' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: 'migrate/introduction' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: 'migrate/introduction' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade/upgrade-from-23-10' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: 'migrate/introduction' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: 'migrate/introduction' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade/upgrade-from-23-04' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: 'migrate/introduction' }, + { version: '22.10 and earlier', os: 'See the corresponding documentation', compat: 'NO', proc: 'Migration from EL or Debian', href: 'migrate/introduction' }, ]; const filtered = rows.filter(r => @@ -110,7 +116,7 @@ export const UpgradeTable = () => { ))} From 78324778ce5c6f36dc4a16ba3897316f2068f817 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 17 Sep 2026 14:55:45 +0200 Subject: [PATCH 059/179] Move section about generating self-signed certificates --- .../administration/secure-platform.md | 851 ------------------ .../administration/self-signed-certificate.md | 142 +++ 2 files changed, 142 insertions(+), 851 deletions(-) create mode 100644 versioned_docs/version-26.10/administration/self-signed-certificate.md diff --git a/versioned_docs/version-26.10/administration/secure-platform.md b/versioned_docs/version-26.10/administration/secure-platform.md index 0f665030af25..4d18be7af0ab 100644 --- a/versioned_docs/version-26.10/administration/secure-platform.md +++ b/versioned_docs/version-26.10/administration/secure-platform.md @@ -517,857 +517,6 @@ Status for the jail: centreon > For more information, go to the [official website](http://www.fail2ban.org). -## Secure the web server with HTTPS - -By default, Centreon installs a web server in HTTP mode. It is strongly recommended that you switch to HTTPS mode by adding your certificate. It is also recommended that you use a certificate validated by an authority rather than a self-signed one. - -- If you already have a certificate validated by an authority, you can go directly to this [step](#activating-https-mode-on-your-web-server) to activate HTTPS mode on your Apache server. - -- If you do not have a certificate validated by an authority, you can generate one on platforms such as [Let's Encrypt](https://letsencrypt.org/). - -- If you need to create a certificate with the self-signed method, follow this [step](#creating-a-self-signed-certificate) before activating HTTPS mode on your server. - -### Creating a self-signed certificate - -> This procedure allows you to create: -- A private key for the server: **centreon7.key** in our case. It will be used by the Apache service. -- A CSR (Certificate Signing Request) file: **centreon7.csr** in our case. -- A private key for the certificate of the certification authority: **ca_demo.key** in our case. -- A x509 certificate to sign your certificate for the server: **ca-demo.crt** in our case. -- A certificate for the server: **centreon7.crt** in our case. - -Let's assume that you have a Centreon server with a **centreon7.localdomain** FQDN address. - -1. Prepare the OpenSSL configuration: - - Due to a policy change at Google, self-signed certificates may be rejected by the Google Chrome browser (it is not even possible to add an exception). To continue using this browser, you must change the OpenSSL configuration. - - - - - Open the file **/etc/pki/tls/openssl.cnf**. The goal here is to edit this file in order to inform the various IPs and FQDNs for the server. - - - - - - Open the file **/etc/pki/tls/openssl.cnf**. The goal here is to edit this file in order to inform the various IPs and FQDNs for the server. - - - - - Open the file **/etc/ssl/openssl.cnf**. The goal here is to edit this file in order to inform the various IPs and FQDNs for the server. - - - - - Find the ```[v3_ca]``` section in order to add a new ```alt_names``` tag: - - ```text - # Add the alt_names tag that allows you to inform our various IPs and FQDNs for the server - [ alt_names ] - IP.1 = xxx.xxx.xxx.xxx - DNS.1 = centreon7.localdomain - # If you have several IP (HA: vip + ip) - # IP.2 = xxx.xxx.xxx.xxx - [ v3_ca ] - subjectAltName = @alt_names - ``` - - Here is an example of how the file should look: - ```text - [ alt_names ] - IP.1 = 10.25.11.73 - DNS.1 = centreon7.localdomain - - [ v3_ca ] - subjectAltName = @alt_names - ``` - -2. Create a private key for the server: - - Let's create a private key named **centreon7.key** without a password so that it can be used by the Apache service. - ```text - openssl genrsa -out centreon7.key 2048 - ``` - - Protect your file by limiting rights: - ```text - chmod 400 centreon7.key - ``` - -3. Create a Certificate Signing Request file: - - From the key you created, create a CSR (Certificate Signing Request) file: **centreon7.csr** in our case. Fill in the fields according to your company. The **Common Name** field must be identical to the hostname of your Apache server (in our case it is **centreon7.localdomain**). - ```text - openssl req -new -key centreon7.key -out centreon7.csr - ``` - -4. Create a private key for the certificate of certification authority: - - Create a private key for this authority: **ca_demo.key** in our case. We add the **-aes256** option to encrypt the output key and include a password. This password will be requested each time this key is used. - ```text - openssl genrsa -aes256 2048 > ca_demo.key - ``` - -5. Create an x509 certificate from the private key of the certificate of certification authority: - - Create an x509 certificate that will be valid for one year: **ca_demo.crt** in our case. - - > Note that it is necessary to simulate a trusted third party, so the **Common Name** field must be different from the server certificate. - ```text - openssl req -new -x509 -days 365 -key ca_demo.key -out ca_demo.crt - ``` - - The certificate being created will enable you to sign your server certificate. - -6. Create a certificate for the server: - - Create your certificate for the server by using the x509 certificate (**ca_demo.crt**) to sign it. - - - - - ```text - openssl x509 -req -in centreon7.csr -out centreon7.crt -CA ca_demo.crt -CAkey ca_demo.key -CAcreateserial -CAserial ca_demo.srl -extfile /etc/pki/tls/openssl.cnf -extensions v3_ca - ``` - - - - - - ```text - openssl x509 -req -in centreon7.csr -out centreon7.crt -CA ca_demo.crt -CAkey ca_demo.key -CAcreateserial -CAserial ca_demo.srl -extfile /etc/pki/tls/openssl.cnf -extensions v3_ca - ``` - - - - - ```text - openssl x509 -req -in centreon7.csr -out centreon7.crt -CA ca_demo.crt -CAkey ca_demo.key -CAcreateserial -CAserial ca_demo.srl -extfile /etc/ssl/openssl.cnf -extensions v3_ca - ``` - - - - - The password created at step **Create a private key for the certificate of certification authority** must be entered. You get your server certificate named **centreon7.crt**. - - You can view the contents of the file: - ```text - less centreon7.crt - ``` - -7. You must then retrieve the x509 certificate file (**ca_demo.crt**) and import it into your browser's certificate manager. - -Now that you have your self-signed certificate, you can perform the following procedure to activate HTTPS mode on your Apache server. - -### Activating HTTPS mode on your web server - -1. Install the SSL module for Apache: - - - - -```shell -dnf install mod_ssl openssl -``` - -2. Install your certificates: - -Install your certificates (**centreon7.key** and **centreon7.crt** in our example, and the CA certificate) by copying them to the Apache configuration: - -```shell -cp centreon7.key /etc/pki/tls/private/ -cp centreon7.crt /etc/pki/tls/certs/ -cp ca_demo.crt /etc/pki/tls/certs/ -``` - - - - -```shell -dnf install mod_ssl openssl -``` - -2. Install your certificates: - -Install your certificates (**centreon7.key** and **centreon7.crt** in our example, and the CA certificate) by copying them to the Apache configuration: - -```shell -cp centreon7.key /etc/pki/tls/private/ -cp centreon7.crt /etc/pki/tls/certs/ -cp ca_demo.crt /etc/pki/tls/certs/ -``` - - - - -```shell -curl -sSL https://packages.sury.org/apache2/README.txt | sudo bash -x -apt update -a2enmod ssl -a2enmod security2 -systemctl restart apache2 -``` - -2. Install your certificates: - -Install your certificates (**centreon7.key** and **centreon7.crt** in our example, and the CA certificate) by copying them to the Apache configuration: - -```shell -cp centreon7.key /etc/ssl/private/ -cp centreon7.crt /etc/ssl/certs/ -cp ca_demo.crt /etc/ssl/certs/ -``` - - - - -3. Back up the previous Apache configuration for Centreon: - - - - -```shell -cp /etc/httpd/conf.d/10-centreon.conf{,.origin} -``` - - - - -```shell -cp /etc/httpd/conf.d/10-centreon.conf{,.origin} -``` - - - - -```shell -cp /etc/apache2/sites-available/centreon.conf{,.origin} -``` - - - - -4. Edit the Centreon Apache configuration: - -> Centreon offers an example of a configuration file to enable HTTPS, available in the following directory: -> **/usr/share/centreon/examples/centreon.apache.https.conf** - - - - -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. - - - - -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. - - - - -Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **\** section. - - - -```apacheconf -Define base_uri "/centreon" -Define install_dir "/usr/share/centreon" - -ServerTokens Prod - - - RewriteEngine On - RewriteCond %{HTTPS} off - RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - -``` - -This is how the file should look: - - - - -```apacheconf -Define base_uri "/centreon" -Define install_dir "/usr/share/centreon" - -ServerTokens Prod - - - RewriteEngine On - RewriteCond %{HTTPS} off - RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - - - - ##################### - # SSL configuration # - ##################### - SSLEngine On - SSLProtocol All -SSLv3 -SSLv2 -TLSv1 -TLSv1.1 - SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA - SSLHonorCipherOrder On - SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/ca.crt - SSLCertificateKeyFile /etc/pki/tls/private/ca.key - - Header set X-Frame-Options: "sameorigin" - Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict - Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" - ServerSignature Off - TraceEnable Off - - Alias ${base_uri}/api ${install_dir} - Alias ${base_uri} ${install_dir}/www/ - - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/www/$1" - - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" - - - ProxyTimeout 300 - ErrorDocument 404 ${base_uri}/index.html - Options -Indexes +FollowSymLinks - - - # https://github.com/SpiderLabs/ModSecurity/issues/652 - SecRuleRemoveById 200003 - - - - DirectoryIndex index.php - AllowOverride none - Require all granted - FallbackResource ${base_uri}/index.html - - - - AllowOverride none - Require all granted - - - - RedirectMatch ^/$ ${base_uri} - - -``` - -> Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your -> certificate and key. In our case: **SSLCertificateFile /etc/pki/tls/certs/centreon7.crt** and **SSLCertificateKeyFile /etc/pki/tls/private/centreon7.key**. - - - - -```apacheconf -Define base_uri "/centreon" -Define install_dir "/usr/share/centreon" - -ServerTokens Prod - - - RewriteEngine On - RewriteCond %{HTTPS} off - RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - - - - ##################### - # SSL configuration # - ##################### - SSLEngine On - SSLProtocol All -SSLv3 -SSLv2 -TLSv1 -TLSv1.1 - SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA - SSLHonorCipherOrder On - SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/ca.crt - SSLCertificateKeyFile /etc/pki/tls/private/ca.key - - Header set X-Frame-Options: "sameorigin" - Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict - Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" - ServerSignature Off - TraceEnable Off - - Alias ${base_uri}/api ${install_dir} - Alias ${base_uri} ${install_dir}/www/ - - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/www/$1" - - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" - - - ProxyTimeout 300 - ErrorDocument 404 ${base_uri}/index.html - Options -Indexes +FollowSymLinks - - - # https://github.com/SpiderLabs/ModSecurity/issues/652 - SecRuleRemoveById 200003 - - - - DirectoryIndex index.php - AllowOverride none - Require all granted - FallbackResource ${base_uri}/index.html - - - - AllowOverride none - Require all granted - - - - RedirectMatch ^/$ ${base_uri} - - -``` - -> Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your -> certificate and key. In our case: **SSLCertificateFile /etc/pki/tls/certs/centreon7.crt** and **SSLCertificateKeyFile /etc/pki/tls/private/centreon7.key**. - - - - -```apacheconf -Define base_uri "/centreon" -Define install_dir "/usr/share/centreon" - -ServerTokens Prod - - - RewriteEngine On - RewriteCond %{HTTPS} off - RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - - - - ##################### - # SSL configuration # - ##################### - SSLEngine On - SSLProtocol All -SSLv3 -SSLv2 -TLSv1 -TLSv1.1 - SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA - SSLHonorCipherOrder On - SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/ca.crt - SSLCertificateKeyFile /etc/pki/tls/private/ca.key - - Header set X-Frame-Options: "sameorigin" - Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict - Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" - ServerSignature Off - TraceEnable Off - - Alias ${base_uri}/api ${install_dir} - Alias ${base_uri} ${install_dir}/www/ - - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/www/$1" - - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" - - - ProxyTimeout 300 - ErrorDocument 404 ${base_uri}/index.html - Options -Indexes +FollowSymLinks - - - # https://github.com/SpiderLabs/ModSecurity/issues/652 - SecRuleRemoveById 200003 - - - - DirectoryIndex index.php - AllowOverride none - Require all granted - FallbackResource ${base_uri}/index.html - - - - AllowOverride none - Require all granted - - - - RedirectMatch ^/$ ${base_uri} - - -``` - -> Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your -> certificate and key. In our case: **SSLCertificateFile /etc/ssl/certs/centreon7.crt** and **SSLCertificateKeyFile /etc/ssl/private/centreon7.key**. - - - - -5. Enable HttpOnly / Secure flags and hide the Apache server signature: - - - - -Edit the **/etc/httpd/conf.d/10-centreon.conf** file and add the following lines before the `` tag: - -```apacheconf -Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict -Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" -ServerSignature Off -ServerTokens Prod -``` - -Edit the **/etc/php.d/50-centreon.ini** file: - -* Make sure that the `expose_php` parameter is disabled: - -```phpconf -expose_php = Off -``` - -* Add the path to the CA certificate that was used to sign the server's certificate: - - ```text - openssl.cafile=/etc/pki/tls/certs/ca_demo.crt - curl.cainfo=/etc/pki/tls/certs/ca_demo.crt - ``` - - - - -Edit the **/etc/httpd/conf.d/10-centreon.conf** file and add the following lines before the `` tag: - -```apacheconf -Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict -Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" -ServerSignature Off -ServerTokens Prod -``` - -Edit the **/etc/php.d/50-centreon.ini** file: - -* Make sure that the `expose_php` parameter is disabled: - -```phpconf -expose_php = Off -``` - -* Add the path to the CA certificate that was used to sign the server's certificate: - - ```text - openssl.cafile=/etc/pki/tls/certs/ca_demo.crt - curl.cainfo=/etc/pki/tls/certs/ca_demo.crt - ``` - - - - -Edit the **/etc/apache2/sites-available/centreon.conf** file and add the following lines before the `` tag: - -```apacheconf -Header set X-Frame-Options: "sameorigin" -Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict -Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" -ServerSignature Off -ServerTokens Prod -TraceEnable Off -``` - -Edit the **/etc/php/8.2/mods-available/centreon.ini** file and add the following lines: - -```text -openssl.cafile=/etc/ssl/certs/ca_demo.crt -curl.cainfo=/etc/ssl/certs/ca_demo.crt -``` - - - - -6. Hide the default **/icons** directory: - - - - -Edit the **/etc/httpd/conf.d/autoindex.conf** file and comment the following line: - -```apacheconf -#Alias /icons/ "/usr/share/httpd/icons/" -``` - - - - -Edit the **/etc/httpd/conf.d/autoindex.conf** file and comment the following line: - -```apacheconf -#Alias /icons/ "/usr/share/httpd/icons/" -``` - - - - -Edit the **/etc/apache2/mods-available/autoindex.conf** file and comment the following line: - -> The default icons directory is already hidden. - - - - -7. You can perform this test to check that Apache is properly configured, by running the following command: - - - - -```apacheconf -apachectl configtest -``` - -The expected result is the following: - -```apacheconf -Syntax OK -``` - - - - -```apacheconf -apachectl configtest -``` - -The expected result is the following: - -```apacheconf -Syntax OK -``` - - - - -```apacheconf -apache2ctl configtest -``` - -The expected result is the following: - -```apacheconf -Syntax OK -``` - - - - -8. Restart the Apache and PHP processes to take the new configuration into account: - - - - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 - -``` - - - - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 - -``` - - - - -```shell -systemctl restart php8.2-fpm apache2 -``` - -Then check its status: - -```shell -systemctl status apache2 -``` - -If everything is ok, you should have: - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -Now you can access your platform with your browser in HTTPS mode. - -> Once your web server is set to HTTPS mode, if you have a MAP server on your platform, you must set the `centreon.url=https://` inside the **/etc/centreon-map/map-config.properties** file to use HTTPS instead of HTTP. Otherwise recent web browsers may block communication between the two servers. The procedure is detailed [here](../graph-views/secure-your-map-platform.md#configure-httpstls-on-the-map-server). - -9. Gorgone API configuration - -Replace **127.0.0.1** with the FQDN of your central server in the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file: - -```text -gorgone: - tpapi: - - name: centreonv2 - base_url: "http://centreon7.localdomain/centreon/api/latest/" - username: "centreon-gorgone" - password: "bpltc4aY" - - name: clapi - username: "centreon-gorgone" - password: "bpltc4aY" -``` - -Then restart the Gorgone daemon: - -```shell -systemctl restart gorgoned -``` - -Then check its status: - -```shell -systemctl status gorgoned -``` - -If everything is ok, you should have: - -```shell -● gorgoned.service - Centreon Gorgone - Loaded: loaded (/etc/systemd/system/gorgoned.service; enabled; vendor preset: disabled) - Active: active (running) since Mon 2023-03-06 15:58:10 CET; 27min ago - Main PID: 1791096 (perl) - Tasks: 124 (limit: 23040) - Memory: 595.3M - CGroup: /system.slice/gorgoned.service - ├─1791096 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=info - ├─1791109 gorgone-statistics - ├─1791112 gorgone-legacycmd - ├─1791117 gorgone-engine - ├─1791118 gorgone-audit - ├─1791125 gorgone-nodes - ├─1791138 gorgone-action - ├─1791151 gorgone-cron - ├─1791158 gorgone-dbcleaner - ├─1791159 gorgone-autodiscovery - ├─1791166 gorgone-httpserver - ├─1791180 gorgone-proxy - ├─1791181 gorgone-proxy - ├─1791182 gorgone-proxy - ├─1791189 gorgone-proxy - └─1791190 gorgone-proxy - -mars 06 15:58:10 ito-central systemd[1]: gorgoned.service: Succeeded. -mars 06 15:58:10 ito-central systemd[1]: Stopped Centreon Gorgone. -mars 06 15:58:10 ito-central systemd[1]: Started Centreon Gorgone. -``` - -You should see the following line in the Gorgone daemon log file **/var/log/centreon-gorgone/gorgoned.log**: - -```text -2023-03-06 15:58:12 - INFO - [autodiscovery] -class- host discovery - sync started -``` - ## Custom URI It is possible to customize the URI for your Centreon platform. For example, **/centreon** can be replaced by **/monitoring**. diff --git a/versioned_docs/version-26.10/administration/self-signed-certificate.md b/versioned_docs/version-26.10/administration/self-signed-certificate.md new file mode 100644 index 000000000000..f4909fd8710f --- /dev/null +++ b/versioned_docs/version-26.10/administration/self-signed-certificate.md @@ -0,0 +1,142 @@ +--- +id: self-signed-certificate +title: Create a self-signed certificate +description: "Create a self-signed certificate with OpenSSL to enable HTTPS on your Centreon server" +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +### Creating a self-signed certificate + +> This procedure allows you to create: + +- A private key for the server: **centreon7.key** in our case. It will be used by the Apache service. +- A CSR (Certificate Signing Request) file: **centreon7.csr** in our case. +- A private key for the certificate of the certification authority: **ca_demo.key** in our case. +- A x509 certificate to sign your certificate for the server: **ca-demo.crt** in our case. +- A certificate for the server: **centreon7.crt** in our case. + +Let's assume that you have a Centreon server with a **centreon7.localdomain** FQDN address. + +1. Prepare the OpenSSL configuration: + + Due to a policy change at Google, self-signed certificates may be rejected by the Google Chrome browser (it is not even possible to add an exception). To continue using this browser, you must change the OpenSSL configuration. + + + + + Open the file **/etc/pki/tls/openssl.cnf**. The goal here is to edit this file in order to inform the various IPs and FQDNs for the server. + + + + + + Open the file **/etc/pki/tls/openssl.cnf**. The goal here is to edit this file in order to inform the various IPs and FQDNs for the server. + + + + + Open the file **/etc/ssl/openssl.cnf**. The goal here is to edit this file in order to inform the various IPs and FQDNs for the server. + + + + + Find the ```[v3_ca]``` section in order to add a new ```alt_names``` tag: + + ```text + # Add the alt_names tag that allows you to inform our various IPs and FQDNs for the server + [ alt_names ] + IP.1 = xxx.xxx.xxx.xxx + DNS.1 = centreon7.localdomain + # If you have several IP (HA: vip + ip) + # IP.2 = xxx.xxx.xxx.xxx + [ v3_ca ] + subjectAltName = @alt_names + ``` + + Here is an example of how the file should look: + ```text + [ alt_names ] + IP.1 = 10.25.11.73 + DNS.1 = centreon7.localdomain + + [ v3_ca ] + subjectAltName = @alt_names + ``` + +2. Create a private key for the server: + + Let's create a private key named **centreon7.key** without a password so that it can be used by the Apache service. + ```text + openssl genrsa -out centreon7.key 2048 + ``` + + Protect your file by limiting rights: + ```text + chmod 400 centreon7.key + ``` + +3. Create a Certificate Signing Request file: + + From the key you created, create a CSR (Certificate Signing Request) file: **centreon7.csr** in our case. Fill in the fields according to your company. The **Common Name** field must be identical to the hostname of your Apache server (in our case it is **centreon7.localdomain**). + ```text + openssl req -new -key centreon7.key -out centreon7.csr + ``` + +4. Create a private key for the certificate of certification authority: + + Create a private key for this authority: **ca_demo.key** in our case. We add the **-aes256** option to encrypt the output key and include a password. This password will be requested each time this key is used. + ```text + openssl genrsa -aes256 2048 > ca_demo.key + ``` + +5. Create an x509 certificate from the private key of the certificate of certification authority: + + Create an x509 certificate that will be valid for one year: **ca_demo.crt** in our case. + + > Note that it is necessary to simulate a trusted third party, so the **Common Name** field must be different from the server certificate. + ```text + openssl req -new -x509 -days 365 -key ca_demo.key -out ca_demo.crt + ``` + + The certificate being created will enable you to sign your server certificate. + +6. Create a certificate for the server: + + Create your certificate for the server by using the x509 certificate (**ca_demo.crt**) to sign it. + + + + + ```text + openssl x509 -req -in centreon7.csr -out centreon7.crt -CA ca_demo.crt -CAkey ca_demo.key -CAcreateserial -CAserial ca_demo.srl -extfile /etc/pki/tls/openssl.cnf -extensions v3_ca + ``` + + + + + + ```text + openssl x509 -req -in centreon7.csr -out centreon7.crt -CA ca_demo.crt -CAkey ca_demo.key -CAcreateserial -CAserial ca_demo.srl -extfile /etc/pki/tls/openssl.cnf -extensions v3_ca + ``` + + + + + ```text + openssl x509 -req -in centreon7.csr -out centreon7.crt -CA ca_demo.crt -CAkey ca_demo.key -CAcreateserial -CAserial ca_demo.srl -extfile /etc/ssl/openssl.cnf -extensions v3_ca + ``` + + + + + The password created at step **Create a private key for the certificate of certification authority** must be entered. You get your server certificate named **centreon7.crt**. + + You can view the contents of the file: + ```text + less centreon7.crt + ``` + +7. You must then retrieve the x509 certificate file (**ca_demo.crt**) and import it into your browser's certificate manager. + +Now that you have your self-signed certificate, you can perform the following procedure to activate HTTPS mode on your Apache server. From cedfdd4b11f8e9c4675cb2f4a0e6a3c28144c475 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 17 Sep 2026 15:47:54 +0200 Subject: [PATCH 060/179] Rejig HTTPS procedures --- .../administration/secure-platform.md | 721 +++++++++++++++++- .../graph-views/secure-your-map-platform.md | 4 +- .../installation/_tls-certificates.mdx | 47 +- .../using-packages.md | 2 +- .../version-26.10-sidebars.json | 4 + 5 files changed, 734 insertions(+), 44 deletions(-) diff --git a/versioned_docs/version-26.10/administration/secure-platform.md b/versioned_docs/version-26.10/administration/secure-platform.md index 4d18be7af0ab..e76adb02f9f5 100644 --- a/versioned_docs/version-26.10/administration/secure-platform.md +++ b/versioned_docs/version-26.10/administration/secure-platform.md @@ -517,6 +517,725 @@ Status for the jail: centreon > For more information, go to the [official website](http://www.fail2ban.org). +## Secure the web server with HTTPS + +The [standard installation procedure from packages](../installation/installation-of-a-central-server/using-packages.md) lets you install your central server in HTTPS mode. If for some reason you chose to install it in HTTP mode, or you upgraded an HTTP central server and now want to switch to HTTPS, follow this procedure. + +It is strongly recommended that you switch to HTTPS mode. Use a certificate issued by a trusted authority. Self-signed certificates must not be used in production. + +- If you already have a certificate validated by an authority, you can go directly to this [step](#activating-https-mode-on-your-web-server) to activate HTTPS mode on your Apache server. + +- If you do not have a certificate validated by an authority, you can generate one on platforms such as [Let's Encrypt](https://letsencrypt.org/). + +- If, for test purposes, you want to use a self-signed certificate, follow [this procedure](./self-signed-certificate.md) before activating HTTPS mode on your server. + +### Activating HTTPS mode on your web server + +1. Install the SSL module for Apache: + + + + +```shell +dnf install mod_ssl openssl +``` + +2. Install your certificates: + +Install your certificates (**centreon7.key** and **centreon7.crt** in our example, and the CA certificate) by copying them to the Apache configuration: + +```shell +cp centreon7.key /etc/pki/tls/private/ +cp centreon7.crt /etc/pki/tls/certs/ +cp ca_demo.crt /etc/pki/tls/certs/ +``` + + + + +```shell +dnf install mod_ssl openssl +``` + +2. Install your certificates: + +Install your certificates (**centreon7.key** and **centreon7.crt** in our example, and the CA certificate) by copying them to the Apache configuration: + +```shell +cp centreon7.key /etc/pki/tls/private/ +cp centreon7.crt /etc/pki/tls/certs/ +cp ca_demo.crt /etc/pki/tls/certs/ +``` + + + + +```shell +curl -sSL https://packages.sury.org/apache2/README.txt | sudo bash -x +apt update +a2enmod ssl +a2enmod security2 +systemctl restart apache2 +``` + +2. Install your certificates: + +Install your certificates (**centreon7.key** and **centreon7.crt** in our example, and the CA certificate) by copying them to the Apache configuration: + +```shell +cp centreon7.key /etc/ssl/private/ +cp centreon7.crt /etc/ssl/certs/ +cp ca_demo.crt /etc/ssl/certs/ +``` + + + + +3. Back up the previous Apache configuration for Centreon: + + + + +```shell +cp /etc/httpd/conf.d/10-centreon.conf{,.origin} +``` + + + + +```shell +cp /etc/httpd/conf.d/10-centreon.conf{,.origin} +``` + + + + +```shell +cp /etc/apache2/sites-available/centreon.conf{,.origin} +``` + + + + +4. Edit the Centreon Apache configuration: + +> Centreon offers an example of a configuration file to enable HTTPS, available in the following directory: +> **/usr/share/centreon/examples/centreon.apache.https.conf** + + + + +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. + + + + +Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. + + + + +Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **\** section. + + + +```apacheconf +Define base_uri "/centreon" +Define install_dir "/usr/share/centreon" + +ServerTokens Prod + + + RewriteEngine On + RewriteCond %{HTTPS} off + RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} + +``` + +This is how the file should look: + + + + +```apacheconf +Define base_uri "/centreon" +Define install_dir "/usr/share/centreon" + +ServerTokens Prod + + + RewriteEngine On + RewriteCond %{HTTPS} off + RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} + + + + ##################### + # SSL configuration # + ##################### + SSLEngine On + SSLProtocol All -SSLv3 -SSLv2 -TLSv1 -TLSv1.1 + SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA + SSLHonorCipherOrder On + SSLCompression Off + SSLCertificateFile /etc/pki/tls/certs/ca.crt + SSLCertificateKeyFile /etc/pki/tls/private/ca.key + + Header set X-Frame-Options: "sameorigin" + Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict + Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" + ServerSignature Off + TraceEnable Off + + Alias ${base_uri}/api ${install_dir} + Alias ${base_uri} ${install_dir}/www/ + + + AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json + + + AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json + + + ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/www/$1" + + + + ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" + + + ProxyTimeout 300 + ErrorDocument 404 ${base_uri}/index.html + Options -Indexes +FollowSymLinks + + + # https://github.com/SpiderLabs/ModSecurity/issues/652 + SecRuleRemoveById 200003 + + + + DirectoryIndex index.php + AllowOverride none + Require all granted + FallbackResource ${base_uri}/index.html + + + + AllowOverride none + Require all granted + + + + RedirectMatch ^/$ ${base_uri} + + +``` + +> Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your +> certificate and key. In our case: **SSLCertificateFile /etc/pki/tls/certs/centreon7.crt** and **SSLCertificateKeyFile /etc/pki/tls/private/centreon7.key**. + + + + +```apacheconf +Define base_uri "/centreon" +Define install_dir "/usr/share/centreon" + +ServerTokens Prod + + + RewriteEngine On + RewriteCond %{HTTPS} off + RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} + + + + ##################### + # SSL configuration # + ##################### + SSLEngine On + SSLProtocol All -SSLv3 -SSLv2 -TLSv1 -TLSv1.1 + SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA + SSLHonorCipherOrder On + SSLCompression Off + SSLCertificateFile /etc/pki/tls/certs/ca.crt + SSLCertificateKeyFile /etc/pki/tls/private/ca.key + + Header set X-Frame-Options: "sameorigin" + Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict + Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" + ServerSignature Off + TraceEnable Off + + Alias ${base_uri}/api ${install_dir} + Alias ${base_uri} ${install_dir}/www/ + + + AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json + + + AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json + + + ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/www/$1" + + + + ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" + + + ProxyTimeout 300 + ErrorDocument 404 ${base_uri}/index.html + Options -Indexes +FollowSymLinks + + + # https://github.com/SpiderLabs/ModSecurity/issues/652 + SecRuleRemoveById 200003 + + + + DirectoryIndex index.php + AllowOverride none + Require all granted + FallbackResource ${base_uri}/index.html + + + + AllowOverride none + Require all granted + + + + RedirectMatch ^/$ ${base_uri} + + +``` + +> Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your +> certificate and key. In our case: **SSLCertificateFile /etc/pki/tls/certs/centreon7.crt** and **SSLCertificateKeyFile /etc/pki/tls/private/centreon7.key**. + + + + +```apacheconf +Define base_uri "/centreon" +Define install_dir "/usr/share/centreon" + +ServerTokens Prod + + + RewriteEngine On + RewriteCond %{HTTPS} off + RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} + + + + ##################### + # SSL configuration # + ##################### + SSLEngine On + SSLProtocol All -SSLv3 -SSLv2 -TLSv1 -TLSv1.1 + SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA + SSLHonorCipherOrder On + SSLCompression Off + SSLCertificateFile /etc/pki/tls/certs/ca.crt + SSLCertificateKeyFile /etc/pki/tls/private/ca.key + + Header set X-Frame-Options: "sameorigin" + Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict + Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" + ServerSignature Off + TraceEnable Off + + Alias ${base_uri}/api ${install_dir} + Alias ${base_uri} ${install_dir}/www/ + + + AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json + + + AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json + + + ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/www/$1" + + + + ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" + + + ProxyTimeout 300 + ErrorDocument 404 ${base_uri}/index.html + Options -Indexes +FollowSymLinks + + + # https://github.com/SpiderLabs/ModSecurity/issues/652 + SecRuleRemoveById 200003 + + + + DirectoryIndex index.php + AllowOverride none + Require all granted + FallbackResource ${base_uri}/index.html + + + + AllowOverride none + Require all granted + + + + RedirectMatch ^/$ ${base_uri} + + +``` + +> Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your +> certificate and key. In our case: **SSLCertificateFile /etc/ssl/certs/centreon7.crt** and **SSLCertificateKeyFile /etc/ssl/private/centreon7.key**. + + + + +5. Enable HttpOnly / Secure flags and hide the Apache server signature: + + + + +Edit the **/etc/httpd/conf.d/10-centreon.conf** file and add the following lines before the `` tag: + +```apacheconf +Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict +Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" +ServerSignature Off +ServerTokens Prod +``` + +Edit the **/etc/php.d/50-centreon.ini** file: + +* Make sure that the `expose_php` parameter is disabled: + +```phpconf +expose_php = Off +``` + +* Add the path to the CA certificate that was used to sign the server's certificate: + + ```text + openssl.cafile=/etc/pki/tls/certs/ca_demo.crt + curl.cainfo=/etc/pki/tls/certs/ca_demo.crt + ``` + + + + +Edit the **/etc/httpd/conf.d/10-centreon.conf** file and add the following lines before the `` tag: + +```apacheconf +Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict +Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" +ServerSignature Off +ServerTokens Prod +``` + +Edit the **/etc/php.d/50-centreon.ini** file: + +* Make sure that the `expose_php` parameter is disabled: + +```phpconf +expose_php = Off +``` + +* Add the path to the CA certificate that was used to sign the server's certificate: + + ```text + openssl.cafile=/etc/pki/tls/certs/ca_demo.crt + curl.cainfo=/etc/pki/tls/certs/ca_demo.crt + ``` + + + + +Edit the **/etc/apache2/sites-available/centreon.conf** file and add the following lines before the `` tag: + +```apacheconf +Header set X-Frame-Options: "sameorigin" +Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict +Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" +ServerSignature Off +ServerTokens Prod +TraceEnable Off +``` + +Edit the **/etc/php/8.2/mods-available/centreon.ini** file and add the following lines: + +```text +openssl.cafile=/etc/ssl/certs/ca_demo.crt +curl.cainfo=/etc/ssl/certs/ca_demo.crt +``` + + + + +6. Hide the default **/icons** directory: + + + + +Edit the **/etc/httpd/conf.d/autoindex.conf** file and comment the following line: + +```apacheconf +#Alias /icons/ "/usr/share/httpd/icons/" +``` + + + + +Edit the **/etc/httpd/conf.d/autoindex.conf** file and comment the following line: + +```apacheconf +#Alias /icons/ "/usr/share/httpd/icons/" +``` + + + + +Edit the **/etc/apache2/mods-available/autoindex.conf** file and comment the following line: + +> The default icons directory is already hidden. + + + + +7. You can perform this test to check that Apache is properly configured, by running the following command: + + + + +```apacheconf +apachectl configtest +``` + +The expected result is the following: + +```apacheconf +Syntax OK +``` + + + + +```apacheconf +apachectl configtest +``` + +The expected result is the following: + +```apacheconf +Syntax OK +``` + + + + +```apacheconf +apache2ctl configtest +``` + +The expected result is the following: + +```apacheconf +Syntax OK +``` + + + + +8. Restart the Apache and PHP processes to take the new configuration into account: + + + + +```shell +systemctl restart php-fpm httpd +``` + +Then check its status: + +```shell +systemctl status httpd +``` + +If everything is ok, you should have: + +```shell +● 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 + +``` + + + + +```shell +systemctl restart php-fpm httpd +``` + +Then check its status: + +```shell +systemctl status httpd +``` + +If everything is ok, you should have: + +```shell +● 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 + +``` + + + + +```shell +systemctl restart php8.2-fpm apache2 +``` + +Then check its status: + +```shell +systemctl status apache2 +``` + +If everything is ok, you should have: + +```shell +● apache2.service - The Apache HTTP Server + Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> + Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago + Docs: https://httpd.apache.org/docs/2.4/ + Main PID: 518 (apache2) + Tasks: 11 (limit: 2356) + Memory: 18.1M + CPU: 1.491s + CGroup: /system.slice/apache2.service + ├─ 518 /usr/sbin/apache2 -k start + ├─1252 /usr/sbin/apache2 -k start + ├─1254 /usr/sbin/apache2 -k start + ├─1472 /usr/sbin/apache2 -k start + ├─3857 /usr/sbin/apache2 -k start + ├─3858 /usr/sbin/apache2 -k start + ├─3859 /usr/sbin/apache2 -k start + ├─3860 /usr/sbin/apache2 -k start + ├─3876 /usr/sbin/apache2 -k start + ├─6261 /usr/sbin/apache2 -k start + └─6509 /usr/sbin/apache2 -k start +``` + + + + +Now you can access your platform with your browser in HTTPS mode. + +> Once your web server is set to HTTPS mode, if you have a MAP server on your platform, you must set the `centreon.url=https://` inside the **/etc/centreon-map/map-config.properties** file to use HTTPS instead of HTTP. Otherwise recent web browsers may block communication between the two servers. The procedure is detailed [here](../graph-views/secure-your-map-platform.md#configure-httpstls-on-the-map-server). + +9. Gorgone API configuration + +Replace **127.0.0.1** with the FQDN of your central server in the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file: + +```text +gorgone: + tpapi: + - name: centreonv2 + base_url: "http://centreon7.localdomain/centreon/api/latest/" + username: "centreon-gorgone" + password: "bpltc4aY" + - name: clapi + username: "centreon-gorgone" + password: "bpltc4aY" +``` + +Then restart the Gorgone daemon: + +```shell +systemctl restart gorgoned +``` + +Then check its status: + +```shell +systemctl status gorgoned +``` + +If everything is ok, you should have: + +```shell +● gorgoned.service - Centreon Gorgone + Loaded: loaded (/etc/systemd/system/gorgoned.service; enabled; vendor preset: disabled) + Active: active (running) since Mon 2023-03-06 15:58:10 CET; 27min ago + Main PID: 1791096 (perl) + Tasks: 124 (limit: 23040) + Memory: 595.3M + CGroup: /system.slice/gorgoned.service + ├─1791096 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=info + ├─1791109 gorgone-statistics + ├─1791112 gorgone-legacycmd + ├─1791117 gorgone-engine + ├─1791118 gorgone-audit + ├─1791125 gorgone-nodes + ├─1791138 gorgone-action + ├─1791151 gorgone-cron + ├─1791158 gorgone-dbcleaner + ├─1791159 gorgone-autodiscovery + ├─1791166 gorgone-httpserver + ├─1791180 gorgone-proxy + ├─1791181 gorgone-proxy + ├─1791182 gorgone-proxy + ├─1791189 gorgone-proxy + └─1791190 gorgone-proxy + +mars 06 15:58:10 ito-central systemd[1]: gorgoned.service: Succeeded. +mars 06 15:58:10 ito-central systemd[1]: Stopped Centreon Gorgone. +mars 06 15:58:10 ito-central systemd[1]: Started Centreon Gorgone. +``` + +You should see the following line in the Gorgone daemon log file **/var/log/centreon-gorgone/gorgoned.log**: + +```text +2023-03-06 15:58:12 - INFO - [autodiscovery] -class- host discovery - sync started +``` + ## Custom URI It is possible to customize the URI for your Centreon platform. For example, **/centreon** can be replaced by **/monitoring**. @@ -592,7 +1311,7 @@ To use http2, you need to follow these steps: -1. [Configure https on Centreon](#secure-the-web-server-with-https) +1. [Configure https on Centreon](../installation/installation-of-a-central-server/using-packages.md#step-3-set-up-the-tls-configuration) 2. Install the nghttp2 module: diff --git a/versioned_docs/version-26.10/graph-views/secure-your-map-platform.md b/versioned_docs/version-26.10/graph-views/secure-your-map-platform.md index 023de2ceeb65..0e81d34269f0 100644 --- a/versioned_docs/version-26.10/graph-views/secure-your-map-platform.md +++ b/versioned_docs/version-26.10/graph-views/secure-your-map-platform.md @@ -8,7 +8,7 @@ import TabItem from '@theme/TabItem'; This chapter describes advanced procedures to secure your Centreon MAP platform. -> If you want to use MAP in HTTPS, you must both secure your Centreon platform and MAP. Follow this [procedure](../administration/secure-platform.md#secure-the-web-server-with-https) if you need to secure your Centreon platform. +> If you want to use MAP in HTTPS, you must both secure your Centreon platform and MAP. If necessary, follow this [procedure](../administration/secure-platform.md#secure-the-web-server-with-https) to secure your Centreon platform. > Mistakes when editing configuration files can lead to malfunctions of the software. We recommend that you make a backup of the file before editing it and that you only change the settings advised by Centreon. @@ -283,7 +283,7 @@ will show the following error: ## Configure TLS for the connection to Centreon Central -> You must [secure your Centreon platform with HTTPS](../administration/secure-platform.md#secure-the-web-server-with-https). +> If it is not already done, [secure your Centreon platform with HTTPS](../administration/secure-platform.md#secure-the-web-server-with-https). Set the **centreon.url** parameter inside **/etc/centreon-map/map-config.properties** to use HTTPS instead of HTTP: diff --git a/versioned_docs/version-26.10/installation/_tls-certificates.mdx b/versioned_docs/version-26.10/installation/_tls-certificates.mdx index e11608b4a4cb..46c7c4722f25 100644 --- a/versioned_docs/version-26.10/installation/_tls-certificates.mdx +++ b/versioned_docs/version-26.10/installation/_tls-certificates.mdx @@ -1,53 +1,20 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Generate the certificates the platform will need to connect to the web interface and to the database. +Use a certificate issued by a trusted authority. Self-signed certificates must not be used in production. -1. On the central server, install **openssl**. +* If you already have a certificate validated by an authority, you can activate HTTPS mode on your Apache server. +* If you do not have a certificate validated by an authority, you can generate one on platforms such as [Let's Encrypt](https://letsencrypt.org/). +* If, for test purposes, you want to use a self-signed certificate, follow [this procedure](./self-signed-certificate.md) before activating HTTPS mode on your server. - - - - ```shell - dnf install openssl -y - ``` - - - - - ```shell - dnf install openssl -y - ``` - - - - - ```shell - apt install -y openssl - ``` - - - - -2. Download the **entrypoint.sh** script. - -3. Run the script to generate a root CA and a certificate for this host. Replace \ by the IP address of your machine: - - ```shell - mkdir -p /etc/pki/centreon-tls - OUT=/etc/pki/centreon-tls \ - entrypoint.sh localhost 127.0.0.1 - cd / - ``` - - The command outputs the following files in **/etc/pki/centreon-tls/**: +Let's say you have the following files in **/etc/pki/centreon-tls/**: * rootCA.pem (public) * server.pem (server certificate) * server-key.pem (server private key) * CA/rootCA.\{key,pem\} (set the following permissions root:root, mode 0400) -4. Install the root CA into the OS trust store: +1. Install the root CA into the OS trust store: @@ -75,4 +42,4 @@ Generate the certificates the platform will need to connect to the web interface -5. If you are using a remote database, also execute this procedure on the machine that will host the remote database, then copy the root CA certificate of the database machine to the central server's trust store. \ No newline at end of file +2. If you are using a remote database, also execute this procedure on the machine that will host the remote database, then copy the root CA certificate of the database machine to the central server's trust store. \ No newline at end of file diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index ea006440bdd1..26a10134800b 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -54,7 +54,7 @@ a remote database on a dedicated server. ## Step 3: Set up the TLS configuration -### Generate the certificates +### Prepare the certificates diff --git a/versioned_sidebars/version-26.10-sidebars.json b/versioned_sidebars/version-26.10-sidebars.json index e952f09a3731..1a851843d734 100644 --- a/versioned_sidebars/version-26.10-sidebars.json +++ b/versioned_sidebars/version-26.10-sidebars.json @@ -233,6 +233,10 @@ { "type": "doc", "id": "reporting/secure-your-mbi-platform" + }, + { + "type": "doc", + "id": "graph-views/self-signed-certificate" } ] }, From edb7bdd26e69b1104a638d4f90d7ab3cc231c2aa Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 17 Sep 2026 16:18:00 +0200 Subject: [PATCH 061/179] Fix sidebar --- versioned_sidebars/version-26.10-sidebars.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_sidebars/version-26.10-sidebars.json b/versioned_sidebars/version-26.10-sidebars.json index 1a851843d734..192d036176e1 100644 --- a/versioned_sidebars/version-26.10-sidebars.json +++ b/versioned_sidebars/version-26.10-sidebars.json @@ -236,7 +236,7 @@ }, { "type": "doc", - "id": "graph-views/self-signed-certificate" + "id": "administration/self-signed-certificate" } ] }, From 3ea40180c5cee1bb059d2d236d2cb9af252c4aa8 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 17 Sep 2026 16:27:16 +0200 Subject: [PATCH 062/179] Fix link + add unattended to "which install" --- .../version-26.10/getting-started/which-install.md | 10 +++++++--- .../version-26.10/installation/_tls-certificates.mdx | 2 +- 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/versioned_docs/version-26.10/getting-started/which-install.md b/versioned_docs/version-26.10/getting-started/which-install.md index 4a08bf146fb7..c7d260ec64df 100644 --- a/versioned_docs/version-26.10/getting-started/which-install.md +++ b/versioned_docs/version-26.10/getting-started/which-install.md @@ -12,9 +12,13 @@ There are several ways to install Centreon. Which one suits your needs best? ## To install Centreon in production -- Use [RPM or DEB packages](../installation/installation-of-a-central-server/using-packages.md): if you already have the - OS and you only want to install Centreon. See the list of [supported operating systems](../installation/compatibility.md#operating-systems). +If you already have the OS and you only want to install Centreon, use either of these: + +* [Unattended installation](../installation/installation-of-a-central-server/unattended.md), donc by running a script. +* [RPM or DEB packages](../installation/installation-of-a-central-server/using-packages.md). + +See the list of [supported operating systems](../installation/compatibility.md#operating-systems). ## See also -See also the [installation prerequisites](../installation/prerequisites.md). \ No newline at end of file +See also the [installation prerequisites](../installation/prerequisites.md). diff --git a/versioned_docs/version-26.10/installation/_tls-certificates.mdx b/versioned_docs/version-26.10/installation/_tls-certificates.mdx index 46c7c4722f25..d78ed9d03322 100644 --- a/versioned_docs/version-26.10/installation/_tls-certificates.mdx +++ b/versioned_docs/version-26.10/installation/_tls-certificates.mdx @@ -5,7 +5,7 @@ Use a certificate issued by a trusted authority. Self-signed certificates must n * If you already have a certificate validated by an authority, you can activate HTTPS mode on your Apache server. * If you do not have a certificate validated by an authority, you can generate one on platforms such as [Let's Encrypt](https://letsencrypt.org/). -* If, for test purposes, you want to use a self-signed certificate, follow [this procedure](./self-signed-certificate.md) before activating HTTPS mode on your server. +* If, for test purposes, you want to use a self-signed certificate, follow [this procedure](../administration/self-signed-certificate.md) before activating HTTPS mode on your server. Let's say you have the following files in **/etc/pki/centreon-tls/**: From 1818f5ee71c62cbbe594ac1b1937a4c86627029d Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 17 Sep 2026 17:04:16 +0200 Subject: [PATCH 063/179] Update --- .../administration/self-signed-certificate.md | 2 +- .../version-26.10/installation/_tls-certificates.mdx | 10 +++++----- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/versioned_docs/version-26.10/administration/self-signed-certificate.md b/versioned_docs/version-26.10/administration/self-signed-certificate.md index f4909fd8710f..ac3840ec0600 100644 --- a/versioned_docs/version-26.10/administration/self-signed-certificate.md +++ b/versioned_docs/version-26.10/administration/self-signed-certificate.md @@ -8,7 +8,7 @@ import TabItem from '@theme/TabItem'; ### Creating a self-signed certificate -> This procedure allows you to create: +This procedure allows you to create: - A private key for the server: **centreon7.key** in our case. It will be used by the Apache service. - A CSR (Certificate Signing Request) file: **centreon7.csr** in our case. diff --git a/versioned_docs/version-26.10/installation/_tls-certificates.mdx b/versioned_docs/version-26.10/installation/_tls-certificates.mdx index d78ed9d03322..418517e11bd4 100644 --- a/versioned_docs/version-26.10/installation/_tls-certificates.mdx +++ b/versioned_docs/version-26.10/installation/_tls-certificates.mdx @@ -1,20 +1,20 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Use a certificate issued by a trusted authority. Self-signed certificates must not be used in production. +Use a certificate issued by a trusted authority. Self-signed certificates may be used for test purposes, but they MUST NOT be used in production. -* If you already have a certificate validated by an authority, you can activate HTTPS mode on your Apache server. +* If you already have a certificate validated by an authority, you can proceed to the next step. * If you do not have a certificate validated by an authority, you can generate one on platforms such as [Let's Encrypt](https://letsencrypt.org/). -* If, for test purposes, you want to use a self-signed certificate, follow [this procedure](../administration/self-signed-certificate.md) before activating HTTPS mode on your server. +* If, for test purposes, you want to use a self-signed certificate, follow [this procedure](../administration/self-signed-certificate.md). Let's say you have the following files in **/etc/pki/centreon-tls/**: * rootCA.pem (public) * server.pem (server certificate) * server-key.pem (server private key) - * CA/rootCA.\{key,pem\} (set the following permissions root:root, mode 0400) + * CA/rootCA.\{key,pem\} (set the following permissions: root:root, mode 0400) -1. Install the root CA into the OS trust store: +1. Install the root CA into the OS trust store of the central server's host machine: From 720322a0ec36972a78ce0729e329ec59c7a71ac2 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 17 Sep 2026 17:25:50 +0200 Subject: [PATCH 064/179] Warning about self-signed certificates --- .../version-26.10/administration/self-signed-certificate.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/administration/self-signed-certificate.md b/versioned_docs/version-26.10/administration/self-signed-certificate.md index ac3840ec0600..bcd82483db8e 100644 --- a/versioned_docs/version-26.10/administration/self-signed-certificate.md +++ b/versioned_docs/version-26.10/administration/self-signed-certificate.md @@ -6,7 +6,7 @@ description: "Create a self-signed certificate with OpenSSL to enable HTTPS on y import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -### Creating a self-signed certificate +> Self-signed certificates are for test purposes only. You MUST NOT use them in production. This procedure allows you to create: From 85df8ac3593b4eb2360848d961911b8665df9653 Mon Sep 17 00:00:00 2001 From: smau Date: Tue, 22 Sep 2026 15:41:38 +0200 Subject: [PATCH 065/179] update --- .../graph-views/map-web-install.md | 27 +++---------------- 1 file changed, 4 insertions(+), 23 deletions(-) diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index e32aadd34248..1a2dd35d6810 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -8,7 +8,7 @@ import TabItem from '@theme/TabItem'; This topic describes how to install Centreon MAP. We recommend that you install MAP on a dedicated server. However, if you do not have large volumes of data, you can install it on the central server. -> If you plan to use MAP in HTTPS, please note that securing the HTTPS protocol requires configuration on both the Centreon platform and the MAP server. It is therefore easier to plan for this before beginning the installation. See the [Secure MAP in HTTPS](#secure-map-in-https) section for the full procedure. +> If you plan to use MAP in HTTPS, please note that securing the HTTPS protocol requires configuration on both the Centreon platform and the MAP server. It is therefore easier to plan for this before beginning the installation. See the [Secure MAP in HTTPS](#secure-map-in-https) page for the full procedure. ## License @@ -53,7 +53,7 @@ See the [software requirements](../installation/prerequisites.md#characteristics #### Hardware - + | Element | Value | @@ -151,26 +151,7 @@ This is how your MAP server should be partitioned: | vg_data | | Free space (unallocated) | 2 GB | - - -| Element | Value | -| ----------------------------| --------- | -| CPU | 8 vCPU | -| RAM | 18 GB | - -This is how your MAP server should be partitioned: - -| Volume group (LVM) | File system | Description | Size | -|-| ----------------------------|-------------|----------------------------------------------------------| -| | /boot | boot images | 2 GB | -| vg_root | / | system root | 20 GB | -| vg_root | swap | swap | 8 GB | -| vg_root | /var/log | contains all log files | 10 GB | -| vg_data | /var/lib/mysql | database | 5 GB | -| vg_data | | Free space (unallocated) | 2 GB | - - - + For very large amounts of data, contact your sales representative. @@ -478,7 +459,7 @@ apt update && apt install mariadb-server -Then enable and restart mariadb +Then enable and restart mariadb. ```shell systemctl enable mariadb From 9ded89b7f70a092e91ada14bf44fd49fc06acda8 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 22 Sep 2026 17:59:47 +0200 Subject: [PATCH 066/179] Fix EN upgrade docs --- .../version-26.10/upgrade/introduction.md | 14 +- .../upgrade/upgrade-from-23-04.md | 2 +- .../upgrade/upgrade-from-23-10.md | 2 +- .../upgrade/upgrade-from-24-04.md | 2 +- .../upgrade/upgrade-from-24-10.md | 2 +- .../upgrade/upgrade-from-25-10.md | 2 +- .../version-26.10/upgrade/upgrade-mariadb.md | 126 +----------------- .../version-26.10/upgrade/upgrade-mysql.md | 26 ++-- 8 files changed, 20 insertions(+), 156 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/introduction.md b/versioned_docs/version-26.10/upgrade/introduction.md index 572b91d171c1..189a716ac834 100644 --- a/versioned_docs/version-26.10/upgrade/introduction.md +++ b/versioned_docs/version-26.10/upgrade/introduction.md @@ -4,16 +4,13 @@ title: Introduction to upgrade description: "Introduction to upgrading Centreon between major versions" --- -This chapter describes how to upgrade your Centreon monitoring platform, i.e. switching between major versions (for instance, from 21.10 to 26.10). +This chapter describes how to upgrade your Centreon monitoring platform, i.e. switching between major versions (for instance, from 23.10 to 26.10). -> As of version 23.04, Centreon no longer supports CentOS 7. If your Centreon platform was installed on CentOS 7, you cannot simply upgrade it; you must change to a [supported OS](../installation/compatibility.md#operating-systems) using a [migration procedure](../migrate/introduction.md). +> Please note that [some OSs are no longer supported](./upgrade-matrix.mdx): you must change to a [supported OS](../installation/compatibility.md#operating-systems) using a [migration procedure](../migrate/introduction.md). -> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Business edition users: MAP Legacy is no longer available in Centreon 26.10. If you are still using MAP Legacy, you will need to migrate to MAP. See [MAP Legacy end of life](https://docs.centreon.com/docs/24.10/graph-views/map-legacy-eol/). -This procedure is linked to your initial version of Centreon. You will have to -**use packages** if you already installed using Centreon ISO or an RPM, and -source files if you installed from sources. Before upgrading Centreon, remember -to make a backup of your system. +Before you upgrade Centreon, make sure you back up your platform. > If you are using at least one of the BAM, MAP or MBI modules, you must install > their new repository to avoid dependency problems. @@ -21,6 +18,3 @@ to make a backup of your system. > If you want to change the OS of the host server, follow the [migration procedure](../migrate/introduction.md). (If you want to migrate a platform that uses **Centreon Poller Display 1.6.x**, refer > to the corresponding [migration procedure](../migrate/poller-display-to-remote-server.md).) - -> The upgrade process can start only from versions **2.8.0** and later. If you -> have an earlier version, please update to the latest *2.8.x* version first. diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md index f6e0bb63a55c..84e9f0a8c51a 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-04.md @@ -1,7 +1,7 @@ --- id: upgrade-from-23-04 title: Upgrade from Centreon 23.04 -description: "Upgrade a Centreon platform from version 23.04 to 25.10" +description: "Upgrade a Centreon platform from version 23.04 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md index e5753d51768c..4f1d824a681f 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-23-10.md @@ -1,7 +1,7 @@ --- id: upgrade-from-23-10 title: Upgrade from Centreon 23.10 -description: "Upgrade a Centreon platform from version 23.10 to 25.10" +description: "Upgrade a Centreon platform from version 23.10 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md b/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md index c2c70045fa97..107c9bf82553 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-24-04.md @@ -1,7 +1,7 @@ --- id: upgrade-from-24-04 title: Upgrade from Centreon 24.04 -description: "Upgrade a Centreon platform from version 24.04 to 25.10" +description: "Upgrade a Centreon platform from version 24.04 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md index 55a5b63ca353..d0f347084805 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-24-10.md @@ -1,7 +1,7 @@ --- id: upgrade-from-24-10 title: Upgrade from Centreon 24.10 -description: "Upgrade a Centreon platform from version 24.10 to 25.10" +description: "Upgrade a Centreon platform from version 24.10 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; diff --git a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md index 7b7e4f149436..3699a6fe0776 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -1,7 +1,7 @@ --- id: upgrade-from-25-10 title: Upgrade from Centreon 25.10 -description: "Upgrade a Centreon platform from version 25.10 to a newer release" +description: "Upgrade a Centreon platform from version 25.10 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; diff --git a/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md b/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md index 734b9736f3db..3ac2c5cc316f 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md @@ -13,7 +13,7 @@ and the MBI and MAP modules each have a dedicated database. Within your architec When you upgrade from one major version of Centreon to another, you must: -1. Upgrade Centreon (packages, web installation, deploying the configuration). +1. Upgrade Centreon (packages, web installation, deploying the configuration). Note that you can only upgrade Centreon [from a supported OS](upgrade-matrix.mdx). 2. Upgrade MariaDB. > Refer to the official MariaDB documentation for more information about this process: @@ -29,43 +29,19 @@ When you upgrade from one major version of Centreon to another, you must: | 24.04 | 10.11 | | 23.10 | 10.5 | | 23.04 | 10.5 | -| 22.10 | 10.5 | -| 22.04 | 10.5 | -| 21.10 | 10.5 | -| 21.04 | 10.5 | -| 20.10 | 10.3.x | -| 20.04 | 10.3.x | -| 19.10 | 10.1.x | ## Knowing your version of MariaDB To find out which version of MariaDB is installed on your machine, enter the following command: - - -```shell -rpm -qa |grep MariaDB -``` - -The results should look like this example: - -```shell -MariaDB-client-10.5.8-1.el8.centos.x86_64 -MariaDB-server-10.5.8-1.el8.centos.x86_64 -MariaDB-common-10.5.8-1.el8.centos.x86_64 -MariaDB-shared-10.5.8-1.el8.centos.x86_64 -MariaDB-compat-10.5.8-1.el8.centos.x86_64 -``` - - ```shell rpm -qa |grep MariaDB ``` -The results should look like this example: +The results may look like this example: ```shell MariaDB-client-10.5.8-1.el9.centos.x86_64 @@ -75,27 +51,6 @@ MariaDB-shared-10.5.8-1.el9.centos.x86_64 MariaDB-compat-10.5.8-1.el9.centos.x86_64 ``` - - - -```shell -dpkg -l |grep MariaDB -``` - -The results should look like this example: - -```shell -ii libdbd-mysql-perl:amd64 4.050-3+b1 amd64 Perl5 database interface to the MariaDB/MySQL database -ii libmariadb3:amd64 1:10.5.17+maria~deb11 amd64 MariaDB database client library -ii mariadb-client-10.5 1:10.5.17+maria~deb11 amd64 MariaDB database client binaries -ii mariadb-client-core-10.5 1:10.5.17+maria~deb11 amd64 MariaDB database core client binaries -ii mariadb-common 1:10.5.17+maria~deb11 all MariaDB common configuration files -ii mariadb-server 1:10.5.17+maria~deb11 all MariaDB database server (metapackage depending on the latest version) -ii mariadb-server-10.5 1:10.5.17+maria~deb11 amd64 MariaDB database server binaries -ii mariadb-server-core-10.5 1:10.5.17+maria~deb11 amd64 MariaDB database core server files -ii mysql-common 1:10.5.17+maria~deb11 all MariaDB database common files (e.g. /etc/mysql/my.cnf) -``` - @@ -112,19 +67,6 @@ You must uninstall then reinstall MariaDB to upgrade between major versions. In 2. Uninstall the current version: - - -```shell -rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-compat MariaDB-common -``` - - - - -```shell -rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-common -``` - ```shell @@ -138,23 +80,6 @@ rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared Mari rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-common ``` - - - -At the **[Knowing your version of MariaDB](#knowing-your-version-of-mariadb)** step, the **grep** command returned the precise version of MariaDB you have. - -* If the results of the **grep** command included the version of MariaDB (e.g., “10.11”), your uninstallation command must include it too, like in the following example: - -```shell -dpkg -r --ignore-depends=mariadb-server,mariadb-client,mariadb-shared,mariadb-compat,mariadb-common mariadb-server mariadb-server-10.11 mariadb-client mariadb-client-10.11 mariadb-client-core-10.11 mariadb-common mariadb-server-core-10.11 mysql-common -``` - -* If the results of the **grep** command did not include “10.11”, use the following command: - -```shell -dpkg -r --ignore-depends=mariadb-server,mariadb-client,mariadb-shared,mariadb-compat,mariadb-common mariadb-server mariadb-server mariadb-client mariadb-client mariadb-client-core mariadb-common mariadb-server-core mysql-common -``` - @@ -173,22 +98,6 @@ dpkg -r --ignore-depends=mariadb-server,mariadb-client,mariadb-shared,mariadb-co 3. Install version 11.8: - - -```shell -dnf module enable -y mariadb:11.8 -dnf install mariadb-server-11.8\* mariadb-11.8\* -``` - - - - -```shell -dnf module enable -y mariadb:11.8 -dnf install mariadb-server-11.8\* mariadb-11.8\* -``` - - ```shell @@ -204,23 +113,6 @@ dnf module enable -y mariadb:11.8 dnf install mariadb-server-11.8\* mariadb-11.8\* ``` - - - -```shell -curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=12 --mariadb-server-version="mariadb-11.8" -``` - -```shell -sudo apt-get install mariadb-server galera-4 mariadb-client libmariadb3 mariadb-backup mariadb-common -``` - -If an error message informs you that one or several MariaDB packages are missing, you will need to specify the missing packages in the command, like in the following example: - -```shell -sudo apt-get install mariadb-server galera-4 mariadb-client libmariadb3 mariadb-backup mariadb-common MISSING-PACKAGE_A MISSING-PACKAGE_B -``` - @@ -295,26 +187,12 @@ Follow these steps to upgrade between minor versions of MariaDB (for example, to 1. Update MariaDB: - - -```shell -dnf update MariaDB-* -``` - - ```shell dnf update MariaDB-* ``` - - - -```shell -apt update MariaDB-* -``` - diff --git a/versioned_docs/version-26.10/upgrade/upgrade-mysql.md b/versioned_docs/version-26.10/upgrade/upgrade-mysql.md index 2e089a66ba50..334f66b3c464 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-mysql.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-mysql.md @@ -15,9 +15,16 @@ and the MBI and MAP modules each have a dedicated database. Within your architec Do not upgrade your version of Centreon and your version of MySQL at the same time. You can perform both upgrades one after the other in the order you want, however, make sure the first upgrade procedure is fully complete before you perform the second one. -## Versions of MySQL compatible with Centreon 26.10 +## Version of MySQL for each version of Centreon -* MySQL 8.4 +| Centreon | MySQL | +|----------|---------| +| 26.10 | 8.4 | +| 25.10 | 8.4 (recommended)
8.0 until its end of support (April 2026) | +| 24.10 | 8.4 (recommended)
8.0 until its end of support (April 2026) | +| 24.04 | 8.0 | +| 23.10 | not supported | +| 23.04 | not supported | ## Knowing your version of MySQL @@ -48,25 +55,10 @@ mysql Ver 8.0.x for Linux on x86_64 2. If you are using MBI: - - - In the **/etc/my.cnf.d/mysql-server.cnf** file, add `log_bin_trust_function_creators=1`. - - In the **/etc/my.cnf.d/mysql-server.cnf** file, add `log_bin_trust_function_creators=1`. - - - - In the `/etc/mysql/mysql.cnf` file, add: - - ```shell - [mysqld] - log_bin_trust_function_creators=1 - ``` - From af4a41c9afee6b8c657b26fbdde219b3cfce43a8 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 22 Sep 2026 18:00:23 +0200 Subject: [PATCH 067/179] FR version of upgrade topics --- .../version-26.10/upgrade/introduction.md | 26 +- .../upgrade/upgrade-from-23-04.md | 864 +---------------- .../upgrade/upgrade-from-23-10.md | 891 +---------------- .../upgrade/upgrade-from-24-04.md | 896 +----------------- .../upgrade/upgrade-from-24-10.md | 825 +--------------- .../upgrade/upgrade-from-25-10.md | 778 +-------------- .../version-26.10/upgrade/upgrade-mariadb.md | 125 +-- .../version-26.10/upgrade/upgrade-mysql.md | 26 +- 8 files changed, 70 insertions(+), 4361 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/introduction.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/introduction.md index 01e9040d1b91..1ee70e3568df 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/introduction.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/introduction.md @@ -4,25 +4,17 @@ title: Introduction à la montée de version description: "Introduction à la montée de version de Centreon entre versions majeures" --- -Ce chapitre décrit le processus de montée de version (upgrade) d'une plateforme Centreon, c'est-à-dire le passage d'une version majeure à une autre (par exemple, 21.10 à 26.10). +Ce chapitre décrit comment monter de version votre plateforme de supervision Centreon, c'est-à-dire passer d'une version majeure à une autre (par exemple, de 23.10 à 26.10). -> à partir de la version 23.04, Centreon ne supporte plus CentOS 7. Si votre plateforme Centreon était installée sous CentOS 7, vous ne pouvez pas simplement monter de version : passez à un [OS supporté](../installation/compatibility.md#système-dexploitation) en suivant une [procédure de migration](../migrate/introduction.md). +> Attention, [certains OS ne sont plus supportés](./upgrade-matrix.mdx) : passez à un [OS supporté](../installation/compatibility.md#système-dexploitation) en suivant une [procédure de migration](../migrate/introduction.md). -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). +> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/24.10/graph-views/map-legacy-eol/). -La procédure dépend de la méthode d'installation de votre plate-forme Centreon. -Faites une **Mise à jour RPM** si vous avez installé Centreon à partir de -l'ISO ou des RPMS, et utilisez les fichiers source si vous avez installé Centreon à partir des sources. Avant de mettre -à jour, réalisez une sauvegarde. +Avant de monter Centreon de version, pensez à réaliser une sauvegarde de votre plateforme. -> Si vous utilisez au moins un des modules BAM, MAP ou MBI, vous devez mettre -> en place leur nouveau dépôt afin d'éviter les problèmes de dépendances. -> Voir [cette page](../reporting/upgrade.md#étape-1--montée-de-version-du-paquet) -> qui vous indique comment le récupérer. +> Si vous utilisez au moins un des modules BAM, MAP ou MBI, vous devez installer +> leur nouveau dépôt afin d'éviter les problèmes de dépendances. +> Consultez [cette page](../reporting/upgrade.md#étape-1--montée-de-version-du-paquet). -> Si vous souhaitez changer l'OS du serveur hôte, suivez la [procédure de migration](../migrate/introduction.md). (Idem en cas de migration d'une plate-forme disposant du module **[Centreon Poller -> Display 1.6.x](../migrate/poller-display-to-remote-server.md)**). - -> Le processus de mise à jour ne peut démarrer qu'à partir des versions **2.8.0** -> et ultérieures. Si vous avez une version précédente, veuillez d'abord mettre à -> jour vers la dernière version 2.8.x. +> Si vous souhaitez changer l'OS du serveur hôte, suivez la [procédure de migration](../migrate/introduction.md). (Si vous souhaitez migrer une plateforme qui utilise **Centreon Poller Display 1.6.x**, consultez la +> [procédure de migration](../migrate/poller-display-to-remote-server.md) correspondante.) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-04.md index f6ada54eb677..97804a22d3d7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-04.md @@ -1,863 +1,19 @@ --- id: upgrade-from-23-04 -title: Montée de version depuis Centreon 23.04 -description: "Passer une plateforme Centreon de la version 23.04 à la 25.10" +title: Monter de version depuis Centreon 23.04 +description: "Monter une plateforme Centreon de la version 23.04 vers la version 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Intro from './_intro.mdx' +import UpgradeCentral from './_upgrade-central.mdx' +import UpgradeRemotes from './_upgrade-remotes.mdx' +import UpgradePollers from './_upgrade-pollers.mdx' -Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 23.04 vers la version 26.10. + -> La version 23.04 n'est plus supportée. La montée de version à partir de cette version n'a pas été testée par l'équipe d'assurance qualité de Centreon. + -> Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. Dans votre architecture, tous les serveurs doivent avoir la même version de Centreon. De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). + -> Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux -> / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). -> Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. - -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian 11, vous devez d'abord migrer en Debian 12 avant d'upgrader Centreon. Voir [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. - -> Attention, si vous utilisiez les connecteurs suivants, à partir de la version 24.10 il est obligatoire de déclarer la configuration de tous ceux-ci [**à la page Configuration > Additional connector configurations**](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) avant de déployer la configuration du collecteur correspondant : -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prérequis - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance -des sauvegardes de l’ensemble des serveurs centraux de votre plate-forme : - -- Serveur Centreon Central, -- Serveur de gestion de base de données. - -Si vous utilisez un fournisseur Open Ticket avec des configurations personnalisées, [sauvegardez-les avant de mettre à jour Centreon](../alerts-notifications/ticketing-install.md#sauvegarder-votre-configuration-personnalisée-de-fournisseur-openticket). - -### Vérifier les dépôts - -Avant de réaliser la montée de version de votre plateforme Centreon, assurez-vous que les dépôts de paquets suivants sont activés : - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## Montée de version du serveur Centreon Central - -> Lorsque vous lancez une commande, vérifiez les messages obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. - -### Installation du nouveau dépôt Centreon - - - - -1. Mettez à jour votre Centreon 23.04 jusqu'à la dernière version mineure. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/23.04/el8/centreon-23.04-el8.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Supprimez les fichiers des dépôts : - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Installez le nouveau dépôt : - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - - - - -1. Mettez à jour votre Centreon 23.04 jusqu'à la dernière version mineure. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/23.04/el9/centreon-23.04-el9.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Supprimez les fichiers des dépôts : - - ```shell - rm /etc/yum.repos.d/centreon-23.04.repo - rm /etc/yum.repos.d/centreon.repo - ``` - -3. Installez le nouveau dépôt : - -```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -1. Mettez à jour votre Centreon 23.04 jusqu'à la dernière version mineure. -2. Exécutez les commandes suivantes : - -```shell -rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Ensuite, importez la clé du dépôt : - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -> Si vous avez une [licence offline](../administration/licenses.md#types-de-licences), supprimez également l'ancien dépôt des connecteurs de supervision, puis installez le nouveau dépôt. -> -> Vous pouvez trouver l'adresse des dépôts sur le [portail support Centreon](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). - -### Montée de version de la solution Centreon - -1. Assurez-vous que tous les utilisateurs sont déconnectés avant de commencer la procédure de mise à jour. - -2. Si vous avez des extensions Business installées, supprimez la configuration du dépôt 23.04 : - - - - -```shell -rm /etc/yum.repos.d/centreon-business-23.04.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-23.04.repo -``` - - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - - - - -3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. - -4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). - -5. Arrêtez le processus Centreon Broker : - -```shell -systemctl stop cbd -``` - -6. Supprimez les fichiers de rétention présents : - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Montée de version de PHP - -Centreon 26.10 utilise PHP en version 8.4. - - - - -Vous devez changer le flux PHP de la version 8.1 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.1 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -Vous devez changer le flux PHP de la version 8.1 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - - - - -```shell -systemctl stop php8.1-fpm -systemctl disable php8.1-fpm -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php/8.2/fpm/conf.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - - - - -Puis, terminez la montée de version de la solution Centreon. - -1. Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -2. Mettez à jour l'ensemble des composants : - - - - -```shell -yum update centreon\* php-pecl-gnupg -``` - - - - -```shell -yum update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -### Mettre à jour une configuration Apache personnalisée - -Cette section s'applique uniquement si vous avez personnalisé votre configuration Apache. - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -Utilisez la sauvegarde que vous avez effectuée à l'étape précédente pour reporter vos personnalisations dans le fichier **/etc/apache2/sites-available/centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apache2ctl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Vérifiez le statut d'Apache : - -```shell -systemctl status apache2 -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -#### Configuration Apache personnalisée : activer la compression du texte - -Pour améliorer le temps de chargement des pages, vous pouvez activer la compression du texte sur le serveur Apache. Le paquet **brotli** est nécessaire. Cette configuration est optionnelle mais vous fournira une meilleure expérience utilisateur. - -Ajoutez le code suivant à votre fichier de configuration Apache, dans les éléments `` et `` : - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json -``` - -### Finalisation de la mise à jour - -Avant de démarrer la montée de version via l'interface web, mettez à jour [Centreon BAM avec cette procédure](../service-mapping/upgrade.md) puis rechargez le serveur Apache avec les commandes suivantes : - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - - - - -Vous devez ensuite finaliser le processus de mise à jour : - - - - -1. Connectez-vous à l'interface web Centreon, l'assistant d'interface s'affiche. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_1.png) - -2. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_2.png) - -3. La note de version présente les principaux changements, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_3.png) - -4. Le processus réalise les différentes mises à jour, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_4.png) - -5. Votre serveur Centreon est maintenant à jour, cliquez sur **Finish** pour -accéder à la page de connexion : - - ![image](../assets/upgrade/web_update_5.png) - - - - -1. Connectez-vous au serveur Central via le terminal pour poursuivre le processus de -mise à jour. - - > Vous avez besoin d'un token d'authentification pour accéder à l'endpoint de l'API. Suivez la procédure ci-dessous pour obtenir un token. - - Dans notre cas, nous avons la configuration décrite ci-dessous (vous devez adapter la procédure à votre configuration). - - - adresse : 10.25.XX.XX - - port : 80 - - version : 26.10 - - identifiant : Admin - - mot de passe : xxxxx - -2. Entrez la requête suivante : - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - Voici à quoi ressemble le résultat : - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost", "is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Récupérez le numéro du token pour l'utiliser lors de la prochaine requête. - -4. Entrez ensuite cette requête : - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. Cette requête ne renvoie aucun résultat. Pour vérifier que la mise à jour a bien été appliquée, consultez le numéro de version affiché sur la page de connexion à l'interface web Centreon. - - - - -Enfin, redémarrez Broker, Engine et Gorgone sur le serveur Central en exécutant la commande suivante : - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Ajoutez l'utilisateur **apache** au groupe **centreon-broker** et vice versa. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - - - - -Référez-vous à la documentation de mise à jour pour [Centreon MBI](../reporting/update.md) et [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. - -### Actions post montée de version - -1. Montée de version des extensions : - - Depuis le menu **Administration > Extensions > Gestionnaire**, mettez à jour - toutes les extensions, en commençant par les suivantes : - - - License Manager, - - Monitoring Connector Manager, - - Auto Discovery. - - Vous pouvez alors mettre à jour toutes les autres extensions commerciales. - -2. Si vous utilisiez des commandes personnalisées pour un collecteur (sur la page **Configuration > Collecteurs > Collecteurs**, dans la section **Monitoring Engine Information**), sachez qu'une nouvelle expression régulière de validation est désormais appliquée (`[a-zA-Z0-9\-\_]+`) : vos commandes personnalisées devront peut-être être adaptées. Sur le serveur central : - * Pour identifier les commandes qui doivent être adaptées, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * Pour adapter automatiquement les commandes, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (Vous pouvez également les adapter manuellement.) - -3. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Redémarrez les processus Centreon : - - ```shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Mettre à jour MariaDB - -Suivez [cette procédure](upgrade-mariadb.md) pour monter de version MariaDB en 10.11. - -## Montée de version des serveurs distants - -Cette procédure est identique à celle utilisée pour effectuer la montée de version d'un serveur Centreon Central, avec en plus la nécessité de récupérer la clé de déchiffrement à la fin. - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP du serveur central afin de permettre au serveur distant de recevoir et traiter des données chiffrées : - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` - -> En fin de mise à jour, la configuration doit être déployée depuis le serveur Central. - -## Montée de version des collecteurs - -### Mise à jour des dépôts - -Exécutez la commande suivante : - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -apt update -``` - - - - -### Montée de version de la solution Centreon - -Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -Mettez à jour l'ensemble des composants : - - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -apt install --only-upgrade centreon-poller -``` - - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -Redémarrez **centreon** : - -```shell -systemctl restart centreon -``` - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP correspondante afin de permettre au collecteur de recevoir et traiter des données chiffrées. - -L'adresse IP à utiliser varie selon les conditions suivantes : -- Lorsque vous mettez à jour un collecteur lié directement au server central, utilisez l'adresse IP du serveur central. -- Lorsque vous mettez à jour un collecteur lié à un serveur distant, utilisez l'adresse IP du serveur distant. Cependant, dans ce cas, confirmez d'abord que le server distant a la bonne clé. Vérifiez que la valeur de `app_secret` dans le fichier `/etc/centreon-engine/engine-context.json` du serveur distant est la même que pour le serveur central. Si ce n'est pas le cas, relancez le script avec l'adresse IP pour corriger le fichier .json. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` + \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-10.md index 8d3f25013645..4b966082eecb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-23-10.md @@ -1,890 +1,19 @@ --- id: upgrade-from-23-10 -title: Montée de version depuis Centreon 23.10 -description: "Passer une plateforme Centreon de la version 23.10 à la 25.10" +title: Monter de version depuis Centreon 23.10 +description: "Monter une plateforme Centreon de la version 23.10 vers la version 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Intro from './_intro.mdx' +import UpgradeCentral from './_upgrade-central.mdx' +import UpgradeRemotes from './_upgrade-remotes.mdx' +import UpgradePollers from './_upgrade-pollers.mdx' -Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 23.10 vers la version 26.10. + -> Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. Dans votre architecture, tous les serveurs doivent avoir la même version de Centreon. De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). + -> Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux -> / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. + -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian 11, vous devez d'abord migrer en Debian 12 avant d'upgrader Centreon. Voir [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. - -> Attention, si vous utilisiez les connecteurs suivants, à partir de la version 24.10 il est obligatoire de déclarer la configuration de tous ceux-ci [**à la page Configuration > Additional connector configurations**](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) avant de déployer la configuration du collecteur correspondant : -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prérequis - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance -des sauvegardes de l’ensemble des serveurs centraux de votre plate-forme : - -- Serveur Centreon Central, -- Serveur de gestion de base de données. - -Si vous utilisez un fournisseur Open Ticket avec des configurations personnalisées, [sauvegardez-les avant de mettre à jour Centreon](../alerts-notifications/ticketing-install.md#sauvegarder-votre-configuration-personnalisée-de-fournisseur-openticket). - -### Vérifier les dépôts - -Avant de réaliser la montée de version de votre plateforme Centreon, assurez-vous que les dépôts de paquets suivants sont activés : - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## Montée de version du serveur Centreon Central - -> Lorsque vous lancez une commande, vérifiez les messages obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. - -### Installation du nouveau dépôt Centreon - - - - -1. Mettez à jour votre Centreon 23.10 jusqu'à la dernière version mineure. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/23.10/el8/centreon-23.10-el8.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Supprimez les fichiers des dépôts : - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Installez le nouveau dépôt : - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - - - - -1. Mettez à jour votre Centreon 23.10 jusqu'à la dernière version mineure. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/23.10/el9/centreon-23.10-el9.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Supprimez les fichiers des dépôts : - - ```shell - rm /etc/yum.repos.d/centreon-23.10.repo - rm /etc/yum.repos.d/centreon.repo - ``` - -3. Installez le nouveau dépôt : - -```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -1. Mettez à jour votre Centreon 23.10 jusqu'à la dernière version mineure. -2. Exécutez les commandes suivantes : - -```shell -rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Ensuite, importez la clé du dépôt : - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -> Si vous avez une [licence offline](../administration/licenses.md#types-de-licences), supprimez également l'ancien dépôt des connecteurs de supervision, puis installez le nouveau dépôt. -> -> Vous pouvez trouver l'adresse des dépôts sur le [portail support Centreon](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). - -### Montée de version de la solution Centreon - -1. Assurez-vous que tous les utilisateurs sont déconnectés avant de commencer la procédure de mise à jour. - -2. Si vous avez des extensions Business installées, supprimez la configuration du dépôt 23.10 : - - - - -```shell -rm /etc/yum.repos.d/centreon-business-23.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-23.10.repo -``` - - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - - - - -3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. - -4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). - -5. Arrêtez le processus Centreon Broker : - -```shell -systemctl stop cbd -``` - -6. Supprimez les fichiers de rétention présents : - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Montée de version de PHP - -Centreon 26.10 utilise PHP en version 8.4. - - - - -Vous devez changer le flux PHP de la version 8.1 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.1 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -Vous devez changer le flux PHP de la version 8.1 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - - - - -```shell -systemctl stop php8.1-fpm -systemctl disable php8.1-fpm -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php/8.2/fpm/conf.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - - - - -Puis, terminez la montée de version de la solution Centreon. - -1. Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -2. Mettez à jour l'ensemble des composants : - - - - -```shell -yum update centreon\* php-pecl-gnupg -``` - - - - -```shell -yum update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -### Mettre à jour une configuration Apache personnalisée - -Cette section s'applique uniquement si vous avez personnalisé votre configuration Apache. - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -Utilisez la sauvegarde que vous avez effectuée à l'étape précédente pour reporter vos personnalisations dans le fichier **/etc/apache2/sites-available/centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apache2ctl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Vérifiez le statut d'Apache : - -```shell -systemctl status apache2 -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -#### Configuration Apache personnalisée : activer la compression du texte - -Pour améliorer le temps de chargement des pages, vous pouvez activer la compression du texte sur le serveur Apache. Le paquet **brotli** est nécessaire. Cette configuration est optionnelle mais vous fournira une meilleure expérience utilisateur. - -Ajoutez le code suivant à votre fichier de configuration Apache, dans les éléments `` et `` : - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json -``` - -### Finalisation de la mise à jour - -Avant de démarrer la montée de version via l'interface web, mettez à jour [Centreon BAM avec cette procédure](../service-mapping/upgrade.md) puis rechargez le serveur Apache avec les commandes suivantes : - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - - - - -Vous devez ensuite finaliser le processus de mise à jour : - - - - -1. Connectez-vous à l'interface web Centreon, l'assistant d'interface s'affiche. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_1.png) - -2. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_2.png) - -3. La note de version présente les principaux changements, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_3.png) - -4. Le processus réalise les différentes mises à jour, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_4.png) - -5. Votre serveur Centreon est maintenant à jour, cliquez sur **Finish** pour -accéder à la page de connexion : - - ![image](../assets/upgrade/web_update_5.png) - - - - -1. Connectez-vous au serveur Central via le terminal pour poursuivre le processus de -mise à jour. - - > Vous avez besoin d'un token d'authentification pour accéder à l'endpoint de l'API. Suivez la procédure ci-dessous pour obtenir un token. - - Dans notre cas, nous avons la configuration décrite ci-dessous (vous devez adapter la procédure à votre configuration). - - - adresse : 10.25.XX.XX - - port : 80 - - version : 26.10 - - identifiant : Admin - - mot de passe : xxxxx - -2. Entrez la requête suivante : - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - Voici à quoi ressemble le résultat : - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost", "is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Récupérez le numéro du token pour l'utiliser lors de la prochaine requête. - -4. Entrez ensuite cette requête : - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. Cette requête ne renvoie aucun résultat. Pour vérifier que la mise à jour a bien été appliquée, consultez le numéro de version affiché sur la page de connexion à l'interface web Centreon. - - - - -Enfin, redémarrez Broker, Engine et Gorgone sur le serveur Central en exécutant la commande suivante : - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Ajoutez l'utilisateur **apache** au groupe **centreon-broker** et vice versa. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - - - - -Référez-vous à la documentation de mise à jour pour [Centreon MBI](../reporting/update.md) et [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. - -### Actions post montée de version - -1. Montée de version des extensions : - - Depuis le menu **Administration > Extensions > Gestionnaire**, mettez à jour - toutes les extensions, en commençant par les suivantes : - - - License Manager, - - Monitoring Connector Manager, - - Auto Discovery. - - Vous pouvez alors mettre à jour toutes les autres extensions commerciales. - -2. Si vous utilisiez des commandes personnalisées pour un collecteur (sur la page **Configuration > Collecteurs > Collecteurs**, dans la section **Monitoring Engine Information**), sachez qu'une nouvelle expression régulière de validation est désormais appliquée (`[a-zA-Z0-9\-\_]+`) : vos commandes personnalisées devront peut-être être adaptées. Sur le serveur central : - * Pour identifier les commandes qui doivent être adaptées, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * Pour adapter automatiquement les commandes, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (Vous pouvez également les adapter manuellement.) - -3. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -> À partir de la version 25.10, la substitution dynamique de variables (ou interpolation) n'est plus autorisée dans les commandes d'auto-découverte de services associées aux connecteurs. -> -> Si vous utilisez des commandes personnalisées qui contiennent de l'interpolation, vous devez les adapter de manière à ce qu'elles n'utilisent que des informations issues des macros. -> -> Cette nouvelle règle est appliquée dans `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml.rpm` via le paramètre : `no_shell_interpretation: true`. Si vous aviez modifié ce fichier, votre version sera sauvegardée dans le même répertoire en tant que `41-autodiscovery.yaml.rpmnew` et devra être manuellement fusionnée pour intégrer ce paramètre. - - - - -> À partir de la version 25.10, la substitution dynamique de variables (ou interpolation) n'est plus autorisée dans les commandes d'auto-découverte de services associées aux connecteurs. -> -> Si vous utilisez des commandes personnalisées qui contiennent de l'interpolation, vous devez les adapter de manière à ce qu'elles n'utilisent que des informations issues des macros. -> -> Cette nouvelle règle est appliquée dans `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml.rpm` via le paramètre : `no_shell_interpretation: true`. Si vous aviez modifié ce fichier, votre version sera sauvegardée dans le même répertoire en tant que `41-autodiscovery.yaml.rpmnew` et devra être manuellement fusionnée pour intégrer ce paramètre. - - - - -> À partir de la version 25.10, la substitution dynamique de variables (ou interpolation) n'est plus autorisée dans les commandes d'auto-découverte de services associées aux connecteurs. -> -> Si vous utilisez des commandes personnalisées qui contiennent de l'interpolation, vous devez les adapter de manière à ce qu'elles n'utilisent que des informations issues des macros. -> -> Cette nouvelle règle est appliquée dans `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml` via le paramètre : `no_shell_interpretation: true`. Si vous aviez antérieurement modifié ce fichier, vous serez invité à résoudre les potentiels conflits entre les deux versions. - - - - -4. Redémarrez les processus Centreon : - - ```shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Mettre à jour MariaDB - -Suivez [cette procédure](upgrade-mariadb.md) pour monter de version MariaDB en 10.11. - -## Montée de version des serveurs distants - -Cette procédure est identique à celle utilisée pour effectuer la montée de version d'un serveur Centreon Central, avec en plus la nécessité de récupérer la clé de déchiffrement à la fin. - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP du serveur central afin de permettre au serveur distant de recevoir et traiter des données chiffrées : - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` - -> En fin de mise à jour, la configuration doit être déployée depuis le serveur Central. - -## Montée de version des collecteurs - -### Mise à jour des dépôts - -Exécutez la commande suivante : - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -apt update -``` - - - - -### Montée de version de la solution Centreon - -Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -Mettez à jour l'ensemble des composants : - - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -apt install --only-upgrade centreon-poller -``` - - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -Redémarrez **centreon** : - -```shell -systemctl restart centreon -``` - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP correspondante afin de permettre au collecteur de recevoir et traiter des données chiffrées. - -L'adresse IP à utiliser varie selon les conditions suivantes : -- Lorsque vous mettez à jour un collecteur lié directement au server central, utilisez l'adresse IP du serveur central. -- Lorsque vous mettez à jour un collecteur lié à un serveur distant, utilisez l'adresse IP du serveur distant. Cependant, dans ce cas, confirmez d'abord que le server distant a la bonne clé. Vérifiez que la valeur de `app_secret` dans le fichier `/etc/centreon-engine/engine-context.json` du serveur distant est la même que pour le serveur central. Si ce n'est pas le cas, relancez le script avec l'adresse IP pour corriger le fichier .json. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` + \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-04.md index c53b76332b5d..2c6ff30bd7f8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-04.md @@ -1,895 +1,19 @@ --- id: upgrade-from-24-04 -title: Montée de version depuis Centreon 24.04 -description: "Passer une plateforme Centreon de la version 24.04 à la 25.10" +title: Monter de version depuis Centreon 24.04 +description: "Monter une plateforme Centreon de la version 24.04 vers la version 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Intro from './_intro.mdx' +import UpgradeCentral from './_upgrade-central.mdx' +import UpgradeRemotes from './_upgrade-remotes.mdx' +import UpgradePollers from './_upgrade-pollers.mdx' -Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 24.04 vers la version 26.10. + -> Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. -> -> Dans votre architecture, tous les serveurs doivent avoir la même version de Centreon. -> -> De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). + -> Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). -> Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. + -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -> Debian 11 n'est plus supporté depuis la version 24.10. Si vous utilisiez Debian 11, vous devez d'abord migrer en Debian 12 avant d'upgrader Centreon. Voir [How to migrate from Debian 11 to Debian 12](https://thewatch.centreon.com/product-how-to-21/how-to-migrate-from-debian-11-to-debian-12-3874). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. - -> Si vous utilisiez MySQL 8.0, prévoyez de [passer à MySQL 8.4](upgrade-mysql.md) avant la fin du support de la version 8.0, prévue fin avril 2026. - -> Attention, si vous utilisiez les connecteurs suivants, à partir de la version 24.10 il est obligatoire de déclarer la configuration de tous ceux-ci [**à la page Configuration > Additional connector configurations**](/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration) avant de déployer la configuration du collecteur correspondant : -> * [VMware ESX](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx/) -> * [VMware vCenter](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-generic/) -> * [VMware VM](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vm/) -> * [VMware vCenter v4](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-4/) -> * [VMware vCenter v5](https://docs.centreon.com/fr/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-5/) -> * [VMware vCenter v6](https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-vmware2-vcenter-6/) - -## Prérequis - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance -des sauvegardes de l’ensemble des serveurs centraux de votre plate-forme : - -- Serveur Centreon Central, -- Serveur de gestion de base de données. - -Si vous utilisez un fournisseur Open Ticket avec des configurations personnalisées, [sauvegardez-les avant de mettre à jour Centreon](../alerts-notifications/ticketing-install.md#sauvegarder-votre-configuration-personnalisée-de-fournisseur-openticket). - -### Vérifier les dépôts - -Avant de réaliser la montée de version de votre plateforme Centreon, assurez-vous que les dépôts de paquets suivants sont activés : - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## Montée de version du serveur Centreon Central - -> Lorsque vous lancez une commande, vérifiez les messages obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. - -### Installation du nouveau dépôt Centreon - - - - -1. Mettez à jour votre Centreon 24.04 jusqu'à la dernière version mineure. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/24.04/el8/centreon-24.04.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Supprimez les fichiers des dépôts : - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Installez le nouveau dépôt : - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - - - - -1. Mettez à jour votre Centreon 24.04 jusqu'à la dernière version mineure. - - ```shell - dnf config-manager --add-repo https://archives.centreon.com/standard/24.04/el9/centreon-24.04.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Supprimez les fichiers des dépôts : - - ```shell - rm /etc/yum.repos.d/centreon-24.04.repo - rm /etc/yum.repos.d/centreon.repo - ``` - -3. Installez le nouveau dépôt : - -```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -1. Mettez à jour votre Centreon 24.04 jusqu'à la dernière version mineure. -2. Exécutez les commandes suivantes : - -```shell -rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Ensuite, importez la clé du dépôt : - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -> Si vous avez une [licence offline](../administration/licenses.md#types-de-licences), supprimez également l'ancien dépôt des connecteurs de supervision, puis installez le nouveau dépôt. -> -> Vous pouvez trouver l'adresse des dépôts sur le [portail support Centreon](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). - -### Montée de version de la solution Centreon - -1. Assurez-vous que tous les utilisateurs sont déconnectés avant de commencer la procédure de mise à jour. - -2. Si vous avez des extensions Business installées, supprimez la configuration du dépôt 24.04 : - - - - -```shell -rm /etc/yum.repos.d/centreon-business-24.04.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-24.04.repo -``` - - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - - - - -3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. - -4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). - -5. Arrêtez le processus Centreon Broker : - -```shell -systemctl stop cbd -``` - -6. Supprimez les fichiers de rétention présents : - -```shell -rm /var/lib/centreon-broker/* -f -``` - -### Montée de version de PHP - -Centreon 26.10 utilise PHP en version 8.4. - - - - -Vous devez changer le flux PHP de la version 8.1 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf config-manager --disable remi-modular remi-safe -dnf module disable composer:2 -dnf module disable php:remi-8.1 -rm -rf /etc/yum.repos.d/remi* -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -dnf distro-sync php\* --allowerasing -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - - -```shell -su - apache -s /bin/bash -c "/usr/share/centreon/bin/console cache:clear" -systemctl restart php-fpm -``` - - - - -Vous devez changer le flux PHP de la version 8.1 à 8.2 en exécutant les commandes suivantes et en répondant **y** -pour confirmer : - -```shell -dnf module reset php -``` - -```shell -dnf module enable php:8.2 -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - - - - -```shell -systemctl stop php8.1-fpm -systemctl disable php8.1-fpm -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php/8.2/fpm/conf.d/50-centreon.ini` est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - - - - -Puis, terminez la montée de version de la solution Centreon. - -1. Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -2. Mettez à jour l'ensemble des composants : - - - - -```shell -yum update centreon\* php-pecl-gnupg -``` - - - - -```shell -yum update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -### Mettre à jour une configuration Apache personnalisée - -Cette section s'applique uniquement si vous avez personnalisé votre configuration Apache. - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -Utilisez la sauvegarde que vous avez effectuée à l'étape précédente pour reporter vos personnalisations dans le fichier **/etc/apache2/sites-available/centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apache2ctl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Vérifiez le statut d'Apache : - -```shell -systemctl status apache2 -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -#### Configuration Apache personnalisée : activer la compression du texte - -Pour améliorer le temps de chargement des pages, vous pouvez activer la compression du texte sur le serveur Apache. Le paquet **brotli** est nécessaire. Cette configuration est optionnelle mais vous fournira une meilleure expérience utilisateur. - -Ajoutez le code suivant à votre fichier de configuration Apache, dans les éléments `` et `` : - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json -``` - -### Finalisation de la mise à jour - -Avant de démarrer la montée de version via l'interface web, mettez à jour [Centreon BAM avec cette procédure](../service-mapping/upgrade.md) puis rechargez le serveur Apache avec les commandes suivantes : - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - - - - -Vous devez ensuite finaliser le processus de mise à jour : - - - - -1. Connectez-vous à l'interface web Centreon, l'assistant d'interface s'affiche. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_1.png) - -2. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_2.png) - -3. La note de version présente les principaux changements, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_3.png) - -4. Le processus réalise les différentes mises à jour, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_4.png) - -5. Votre serveur Centreon est maintenant à jour, cliquez sur **Finish** pour -accéder à la page de connexion : - - ![image](../assets/upgrade/web_update_5.png) - - - - -1. Connectez-vous au serveur Central via le terminal pour poursuivre le processus de -mise à jour. - - > Vous avez besoin d'un token d'authentification pour accéder à l'endpoint de l'API. Suivez la procédure ci-dessous pour obtenir un token. - - Dans notre cas, nous avons la configuration décrite ci-dessous (vous devez adapter la procédure à votre configuration). - - - adresse : 10.25.XX.XX - - port : 80 - - version : 26.10 - - identifiant : Admin - - mot de passe : xxxxx - -2. Entrez la requête suivante : - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - Voici à quoi ressemble le résultat : - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost", "is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Récupérez le numéro du token pour l'utiliser lors de la prochaine requête. - -4. Entrez ensuite cette requête : - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. Cette requête ne renvoie aucun résultat. Pour vérifier que la mise à jour a bien été appliquée, consultez le numéro de version affiché sur la page de connexion à l'interface web Centreon. - - - - -Enfin, redémarrez Broker, Engine et Gorgone sur le serveur Central en exécutant la commande suivante : - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Ajoutez l'utilisateur **apache** au groupe **centreon-broker** et vice versa. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - - - - -Référez-vous à la documentation de mise à jour pour [Centreon MBI](../reporting/update.md) et [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. - -### Actions post montée de version - -1. Montée de version des extensions : - - Depuis le menu **Administration > Extensions > Gestionnaire**, mettez à jour - toutes les extensions, en commençant par les suivantes : - - - License Manager, - - Monitoring Connector Manager, - - Auto Discovery. - - Vous pouvez alors mettre à jour toutes les autres extensions commerciales. - -2. Si vous utilisiez des commandes personnalisées pour un collecteur (sur la page **Configuration > Collecteurs > Collecteurs**, dans la section **Monitoring Engine Information**), sachez qu'une nouvelle expression régulière de validation est désormais appliquée (`[a-zA-Z0-9\-\_]+`) : vos commandes personnalisées devront peut-être être adaptées. Sur le serveur central : - * Pour identifier les commandes qui doivent être adaptées, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * Pour adapter automatiquement les commandes, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (Vous pouvez également les adapter manuellement.) - -3. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -> À partir de la version 25.10, la substitution dynamique de variables (ou interpolation) n'est plus autorisée dans les commandes d'auto-découverte de services associées aux connecteurs. -> -> Si vous utilisez des commandes personnalisées qui contiennent de l'interpolation, vous devez les adapter de manière à ce qu'elles n'utilisent que des informations issues des macros. -> -> Cette nouvelle règle est appliquée dans `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml.rpm` via le paramètre : `no_shell_interpretation: true`. Si vous aviez modifié ce fichier, votre version sera sauvegardée dans le même répertoire en tant que `41-autodiscovery.yaml.rpmnew` et devra être manuellement fusionnée pour intégrer ce paramètre. - - - - -> À partir de la version 25.10, la substitution dynamique de variables (ou interpolation) n'est plus autorisée dans les commandes d'auto-découverte de services associées aux connecteurs. -> -> Si vous utilisez des commandes personnalisées qui contiennent de l'interpolation, vous devez les adapter de manière à ce qu'elles n'utilisent que des informations issues des macros. -> -> Cette nouvelle règle est appliquée dans `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml.rpm` via le paramètre : `no_shell_interpretation: true`. Si vous aviez modifié ce fichier, votre version sera sauvegardée dans le même répertoire en tant que `41-autodiscovery.yaml.rpmnew` et devra être manuellement fusionnée pour intégrer ce paramètre. - - - - -> À partir de la version 25.10, la substitution dynamique de variables (ou interpolation) n'est plus autorisée dans les commandes d'auto-découverte de services associées aux connecteurs. -> -> Si vous utilisez des commandes personnalisées qui contiennent de l'interpolation, vous devez les adapter de manière à ce qu'elles n'utilisent que des informations issues des macros. -> -> Cette nouvelle règle est appliquée dans `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml` via le paramètre : `no_shell_interpretation: true`. Si vous aviez antérieurement modifié ce fichier, vous serez invité à résoudre les potentiels conflits entre les deux versions. - - - - -4. Redémarrez les processus Centreon : - - ```shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Montée de version des serveurs distants - -Cette procédure est identique à celle utilisée pour effectuer la montée de version d'un serveur Centreon Central, avec en plus la nécessité de récupérer la clé de déchiffrement à la fin. - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP du serveur central afin de permettre au serveur distant de recevoir et traiter des données chiffrées : - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` - -> En fin de mise à jour, la configuration doit être déployée depuis le serveur Central. - -## Montée de version des collecteurs - -### Mise à jour des dépôts - -Exécutez la commande suivante : - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -apt update -``` - - - - -### Montée de version de la solution Centreon - -Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -Mettez à jour l'ensemble des composants : - - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -dnf update centreon\* -``` - -> Si vous avez installé MariaDB depuis leurs dépôts officiels, il se peut que vous rencontriez des problèmes de conflits. Suivez notre [procédure sur le sujet](../resources/known-issues.md#vous-avez-un-conflit-entre-les-paquets-mysql-common-et-mariadb-common) pour une solution de contournement. - - - - -```shell -apt install --only-upgrade centreon-poller -``` - - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -Redémarrez **centreon** : - -```shell -systemctl restart centreon -``` - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP correspondante afin de permettre au collecteur de recevoir et traiter des données chiffrées. - -L'adresse IP à utiliser varie selon les conditions suivantes : -- Lorsque vous mettez à jour un collecteur lié directement au server central, utilisez l'adresse IP du serveur central. -- Lorsque vous mettez à jour un collecteur lié à un serveur distant, utilisez l'adresse IP du serveur distant. Cependant, dans ce cas, confirmez d'abord que le server distant a la bonne clé. Vérifiez que la valeur de `app_secret` dans le fichier `/etc/centreon-engine/engine-context.json` du serveur distant est la même que pour le serveur central. Si ce n'est pas le cas, relancez le script avec l'adresse IP pour corriger le fichier .json. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` + \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-10.md index d589116a7262..dab7584805ec 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-24-10.md @@ -1,824 +1,19 @@ --- id: upgrade-from-24-10 -title: Montée de version depuis Centreon 24.10 -description: "Passer une plateforme Centreon de la version 24.10 à la 25.10" +title: Monter de version depuis Centreon 24.10 +description: "Monter une plateforme Centreon de la version 24.10 vers la version 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Intro from './_intro.mdx' +import UpgradeCentral from './_upgrade-central.mdx' +import UpgradeRemotes from './_upgrade-remotes.mdx' +import UpgradePollers from './_upgrade-pollers.mdx' -Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 24.10 vers la version 26.10. + -> Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. -> -> Dans votre architecture, tous les serveurs doivent avoir la même version de Centreon. -> -> De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). + -> Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). -> Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. + -> Si vous utilisiez MySQL 8.0, prévoyez de [passer à MySQL 8.4](upgrade-mysql.md) avant la fin du support de la version 8.0, prévue fin avril 2026. - -> Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisiez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/graph-views/map-legacy-eol/). - -## Prérequis - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance -des sauvegardes de l’ensemble des serveurs centraux de votre plate-forme : - -- Serveur Centreon Central, -- Serveur de gestion de base de données. - -### Vérifier les dépôts - -Avant de réaliser la montée de version de votre plateforme Centreon, assurez-vous que les dépôts de paquets suivants sont activés : - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## Montée de version du serveur Centreon Central - -> Lorsque vous lancez une commande, vérifiez les messages obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. - -### Installation du nouveau dépôt Centreon - - - - -1. Mettez à jour votre Centreon 24.10 jusqu'à la dernière version mineure. - - ```shell - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/24.10/el8/centreon-24.10.repo - dnf clean all --enablerepo=* - dnf update - ``` - -2. Supprimez les fichiers des dépôts : - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Installez le nouveau dépôt : - - ```shell - dnf install -y dnf-plugins-core - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo - systemctl stop cbd - dnf clean all --enablerepo=* - ``` - - - - -1. Mettez à jour votre Centreon 24.10 jusqu'à la dernière version mineure. - - ```shell - dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/24.10/el9/centreon-24.10.repo - dnf clean all --enablerepo=* - dnf update - ``` - - -2. Supprimez les fichiers des dépôts : - - ```shell - rm /etc/yum.repos.d/centreon-24.10.repo - rm /etc/yum.repos.d/centreon.repo - ``` - -3. Installez le nouveau dépôt : - -```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -1. Mettez à jour votre Centreon 24.10 jusqu'à la dernière version mineure. -2. Exécutez les commandes suivantes : - -```shell -rm -f /etc/apt/sources.list.d/centreon.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Ensuite, importez la clé du dépôt : - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -> Si vous avez une [licence offline](../administration/licenses.md#types-de-licences), supprimez également l'ancien dépôt des connecteurs de supervision, puis installez le nouveau dépôt. -> -> Vous pouvez trouver l'adresse des dépôts sur le [portail support Centreon](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). - -### Montée de version de la solution Centreon - -1. Assurez-vous que tous les utilisateurs sont déconnectés avant de commencer la procédure de mise à jour. - -2. Si vous avez des extensions Business installées, supprimez la configuration du dépôt 24.10 : - - - - -```shell -rm /etc/yum.repos.d/centreon-business-24.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-24.10.repo -``` - - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - - - - -3. Installez le dépôt business en 26.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. - -4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). - -5. Arrêtez le processus Centreon Broker : - -```shell -systemctl stop cbd -``` - -6. Supprimez les fichiers de rétention présents : - -```shell -rm /var/lib/centreon-broker/* -f -``` - -Assurez vous que le paramètre `memory_limit` contenu dans `/etc/php.d/50-centreon.ini` (`/etc/php/8.2/fpm/conf.d/50-centreon.ini` pour Debian) est fixé à au moins 256mb. Ajoutez cette limite manuellement si nécessaire. - -7. Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -8. Mettez à jour l'ensemble des composants : - - - - -```shell -yum update centreon\* php-pecl-gnupg -``` - - - - -```shell -yum update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -### Mettre à jour une configuration Apache personnalisée - -Cette section s'applique uniquement si vous avez personnalisé votre configuration Apache. - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -Utilisez la sauvegarde que vous avez effectuée à l'étape précédente pour reporter vos personnalisations dans le fichier **/etc/apache2/sites-available/centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apache2ctl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Vérifiez le statut d'Apache : - -```shell -systemctl status apache2 -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2024-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -#### Configuration Apache personnalisée : activer la compression du texte - -Pour améliorer le temps de chargement des pages, vous pouvez activer la compression du texte sur le serveur Apache. Le paquet **brotli** est nécessaire. Cette configuration est optionnelle mais vous fournira une meilleure expérience utilisateur. - -Ajoutez le code suivant à votre fichier de configuration Apache, dans les éléments `` et `` : - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json -``` - -### Finalisation de la mise à jour - -Avant de démarrer la montée de version via l'interface web, mettez à jour [Centreon BAM avec cette procédure](../service-mapping/upgrade.md) puis rechargez le serveur Apache avec les commandes suivantes : - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - - - - -Vous devez ensuite finaliser le processus de mise à jour : - - - - -1. Connectez-vous à l'interface web Centreon, l'assistant d'interface s'affiche. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_1.png) - -2. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_2.png) - -3. La note de version présente les principaux changements, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_3.png) - -4. Le processus réalise les différentes mises à jour, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_4.png) - -5. Votre serveur Centreon est maintenant à jour, cliquez sur **Finish** pour -accéder à la page de connexion : - - ![image](../assets/upgrade/web_update_5.png) - - - - -1. Connectez-vous au serveur Central via le terminal pour poursuivre le processus de -mise à jour. - - > Vous avez besoin d'un token d'authentification pour accéder à l'endpoint de l'API. Suivez la procédure ci-dessous pour obtenir un token. - - Dans notre cas, nous avons la configuration décrite ci-dessous (vous devez adapter la procédure à votre configuration). - - - adresse : 10.25.XX.XX - - port : 80 - - version : 26.10 - - identifiant : Admin - - mot de passe : xxxxx - -2. Entrez la requête suivante : - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - Voici à quoi ressemble le résultat : - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost", "is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Récupérez le numéro du token pour l'utiliser lors de la prochaine requête. - -4. Entrez ensuite cette requête : - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. Cette requête ne renvoie aucun résultat. Pour vérifier que la mise à jour a bien été appliquée, consultez le numéro de version affiché sur la page de connexion à l'interface web Centreon. - - - - -Enfin, redémarrez Broker, Engine et Gorgone sur le serveur Central en exécutant la commande suivante : - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Mettez à jour les permissions sur les fichiers de configurations de centreon-broker. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - - - - -Référez-vous à la documentation de mise à jour pour [Centreon MBI](../reporting/update.md) et [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. - -### Actions post montée de version - -1. Montée de version des extensions : - - Depuis le menu **Administration > Extensions > Gestionnaire**, mettez à jour - toutes les extensions, en commençant par les suivantes : - - - License Manager, - - Monitoring Connector Manager, - - Auto Discovery. - - Vous pouvez alors mettre à jour toutes les autres extensions commerciales. - -2. Si vous utilisiez des commandes personnalisées pour un collecteur (sur la page **Configuration > Collecteurs > Collecteurs**, dans la section **Monitoring Engine Information**), sachez qu'une nouvelle expression régulière de validation est désormais appliquée (`[a-zA-Z0-9\-\_]+`) : vos commandes personnalisées devront peut-être être adaptées. Sur le serveur central : - * Pour identifier les commandes qui doivent être adaptées, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * Pour adapter automatiquement les commandes, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (Vous pouvez également les adapter manuellement.) - -3. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - - - - -> À partir de la version 25.10, la substitution dynamique de variables (ou interpolation) n'est plus autorisée dans les commandes d'auto-découverte de services associées aux connecteurs. -> -> Si vous utilisez des commandes personnalisées qui contiennent de l'interpolation, vous devez les adapter de manière à ce qu'elles n'utilisent que des informations issues des macros. -> -> Cette nouvelle règle est appliquée dans `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml.rpm` via le paramètre : `no_shell_interpretation: true`. Si vous aviez modifié ce fichier, votre version sera sauvegardée dans le même répertoire en tant que `41-autodiscovery.yaml.rpmnew` et devra être manuellement fusionnée pour intégrer ce paramètre. - - - - -> À partir de la version 25.10, la substitution dynamique de variables (ou interpolation) n'est plus autorisée dans les commandes d'auto-découverte de services associées aux connecteurs. -> -> Si vous utilisez des commandes personnalisées qui contiennent de l'interpolation, vous devez les adapter de manière à ce qu'elles n'utilisent que des informations issues des macros. -> -> Cette nouvelle règle est appliquée dans `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml.rpm` via le paramètre : `no_shell_interpretation: true`. Si vous aviez modifié ce fichier, votre version sera sauvegardée dans le même répertoire en tant que `41-autodiscovery.yaml.rpmnew` et devra être manuellement fusionnée pour intégrer ce paramètre. - - - - -> À partir de la version 25.10, la substitution dynamique de variables (ou interpolation) n'est plus autorisée dans les commandes d'auto-découverte de services associées aux connecteurs. -> -> Si vous utilisez des commandes personnalisées qui contiennent de l'interpolation, vous devez les adapter de manière à ce qu'elles n'utilisent que des informations issues des macros. -> -> Cette nouvelle règle est appliquée dans `/etc/centreon-gorgone/config.d/41-autodiscovery.yaml` via le paramètre : `no_shell_interpretation: true`. Si vous aviez antérieurement modifié ce fichier, vous serez invité à résoudre les potentiels conflits entre les deux versions. - - - - -4. Redémarrez les processus Centreon : - - ```shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Montée de version des serveurs distants - -Cette procédure est identique à celle utilisée pour effectuer la montée de version d'un serveur Centreon Central, avec en plus la nécessité de récupérer la clé de déchiffrement à la fin. - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP du serveur central afin de permettre au serveur distant de recevoir et traiter des données chiffrées : - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` - -> En fin de mise à jour, la configuration doit être déployée depuis le serveur Central. - -## Montée de version des collecteurs - -### Mise à jour des dépôts - -Exécutez la commande suivante : - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -``` - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -apt update -``` - - - - -### Montée de version de la solution Centreon - -Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -Mettez à jour l'ensemble des composants : - - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -dnf update centreon\* -``` - -> Si vous avez installé MariaDB depuis leurs dépôts officiels, il se peut que vous rencontriez des problèmes de conflits. Suivez notre [procédure sur le sujet](../resources/known-issues.md#vous-avez-un-conflit-entre-les-paquets-mysql-common-et-mariadb-common) pour une solution de contournement. - - - - -```shell -apt install --only-upgrade centreon-poller -``` - - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -Redémarrez **centreon** : - -```shell -systemctl restart centreon -``` - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP correspondante afin de permettre au collecteur de recevoir et traiter des données chiffrées. - -L'adresse IP à utiliser varie selon les conditions suivantes : -- Lorsque vous mettez à jour un collecteur lié directement au server central, utilisez l'adresse IP du serveur central. -- Lorsque vous mettez à jour un collecteur lié à un serveur distant, utilisez l'adresse IP du serveur distant. Cependant, dans ce cas, confirmez d'abord que le server distant a la bonne clé. Vérifiez que la valeur de `app_secret` dans le fichier `/etc/centreon-engine/engine-context.json` du serveur distant est la même que pour le serveur central. Si ce n'est pas le cas, relancez le script avec l'adresse IP pour corriger le fichier .json. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` + diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-25-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-25-10.md index 1eda02a8d60a..be3e7d88193f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-25-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-from-25-10.md @@ -1,777 +1,19 @@ --- id: upgrade-from-25-10 -title: Montée de version depuis Centreon 25.10 -description: "Passer une plateforme Centreon de la version 25.10 vers une version ultérieure" +title: Monter de version depuis Centreon 25.10 +description: "Monter une plateforme Centreon de la version 25.10 vers la version 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Intro from './_intro.mdx' +import UpgradeCentral from './_upgrade-central.mdx' +import UpgradeRemotes from './_upgrade-remotes.mdx' +import UpgradePollers from './_upgrade-pollers.mdx' -Ce chapitre décrit la procédure de montée de version de votre plateforme -Centreon depuis la version 25.10 vers la version 26.10. + -> Lorsque vous effectuez la montée de version de votre serveur central, assurez-vous d'également mettre à jour tous vos serveurs distants et vos collecteurs. -> -> Dans votre architecture, tous les serveurs doivent avoir la même version de Centreon. -> -> De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). + -> Si vous souhaitez migrer votre serveur Centreon vers Oracle Linux / RHEL 8, vous devez suivre la [procédure de migration](../migrate/introduction.md). -> Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. + -> Si vous utilisiez MySQL 8.0, vous devez [passer à MySQL 8.4](upgrade-mysql.md). - -## Prérequis - -### Sauvegarde - -Avant toute chose, il est préférable de s’assurer de l’état et de la consistance -des sauvegardes de l’ensemble des serveurs centraux de votre plate-forme : - -- Serveur Centreon Central, -- Serveur de gestion de base de données. - -### Vérifier les dépôts - -Avant de réaliser la montée de version de votre plateforme Centreon, assurez-vous que les dépôts de paquets suivants sont activés : - - - - -* EPEL -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bullseye, bullseye-updates, bullseye-backports and bullseye security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -* bookworm, bookworm-updates, bookworm-backports and bookworm security -* BaseOS -* AppStream -* centreon -* centreon-modules, if you are using Centreon Business Edition. - - - - -## Montée de version du serveur Centreon Central - -> Lorsque vous lancez une commande, vérifiez les messages obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. - -### Installation du nouveau dépôt Centreon - - - - -1. Mettez à jour votre Centreon 24.10 jusqu'à la dernière version mineure. - -2. Supprimez les fichiers des dépôts : - - ```shell - cd /etc/yum.repos.d/ - rm -rf centreon* - ``` - -3. Installez le nouveau dépôt : - - ```shell - 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=* - ``` - - - - -1. Mettez à jour votre Centreon 24.10 jusqu'à la dernière version mineure. - -2. Supprimez les fichiers des dépôts : - - ```shell - rm /etc/yum.repos.d/centreon-25.10.repo - rm /etc/yum.repos.d/centreon.repo - ``` - -3. Installez le nouveau dépôt : - -```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -1. Mettez à jour votre Centreon 25.10 jusqu'à la dernière version mineure. -2. Exécutez les commandes suivantes : - -```shell -rm -f /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` - -3. Ensuite, importez la clé du dépôt : - -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` - - - - -> Si vous avez une [licence offline](../administration/licenses.md#types-de-licences), supprimez également l'ancien dépôt des connecteurs de supervision, puis installez le nouveau dépôt. -> -> Vous pouvez trouver l'adresse des dépôts sur le [portail support Centreon](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). - -### Montée de version de la solution Centreon - -1. Assurez-vous que tous les utilisateurs sont déconnectés avant de commencer la procédure de mise à jour. - -2. Si vous avez des extensions Business installées, supprimez la configuration du dépôt 24.10 : - - - - -```shell -rm /etc/yum.repos.d/centreon-business-24.10.repo -``` - - - - - -```shell -rm /etc/yum.repos.d/centreon-business-24.10.repo -``` - - - - - -```shell -rm /etc/apt/sources.list.d/centreon-business.list -``` - - - - -3. Installez le dépôt business en 25.10. Rendez-vous sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts) pour en récupérer l'adresse. - -4. Si votre système d'exploitation est Debian et que vous utilisez une configuration Apache personnalisée, faites une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). - -5. Arrêtez le processus Centreon Broker : - -```shell -systemctl stop cbd -``` - -6. Supprimez les fichiers de rétention présents : - -```shell -rm /var/lib/centreon-broker/* -f -``` - -7. Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -8. Mettez à jour l'ensemble des composants : - - - - -```shell -yum update centreon\* php-pecl-gnupg -``` - - - - -```shell -yum update centreon\* php-pecl-gnupg -``` - - - - -```shell -apt install --only-upgrade centreon -``` - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -### Mettre à jour une configuration Apache personnalisée - -Cette section s'applique uniquement si vous avez personnalisé votre configuration Apache. - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration amené par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisée. - -Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : - -``` -diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew -``` - -* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. -* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm; il ne contient pas la configuration personnalisée. - -Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Redémarrez Apache pour appliquer les modifications : - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -Utilisez la sauvegarde que vous avez effectuée à l'étape précédente pour reporter vos personnalisations dans le fichier **/etc/apache2/sites-available/centreon.conf**. - -Vérifiez qu'Apache est bien configuré, en exécutant la commande suivante : - -```shell -apache2ctl configtest -``` - -Le résultat attendu est le suivant : - -```shell -Syntax OK -``` - -Vérifiez le statut d'Apache : - -```shell -systemctl status apache2 -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2024-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -#### Configuration Apache personnalisée : activer la compression du texte - -Pour améliorer le temps de chargement des pages, vous pouvez activer la compression du texte sur le serveur Apache. Le paquet **brotli** est nécessaire. Cette configuration est optionnelle mais vous fournira une meilleure expérience utilisateur. - -Ajoutez le code suivant à votre fichier de configuration Apache, dans les éléments `` et `` : - -```shell - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - -AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json -``` - -### Finalisation de la mise à jour - -Avant de démarrer la montée de version via l'interface web, mettez à jour [Centreon BAM avec cette procédure](../service-mapping/upgrade.md) puis rechargez le serveur Apache avec les commandes suivantes : - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -systemctl reload php-fpm httpd -``` - - - - -```shell -apt autoremove -systemctl daemon-reload -systemctl enable php8.2-fpm -systemctl start php8.2-fpm -systemctl restart apache2 -``` - - - - -Vous devez ensuite finaliser le processus de mise à jour : - - - - -1. Connectez-vous à l'interface web Centreon, l'assistant d'interface s'affiche. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_1.png) - -2. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_2.png) - -3. La note de version présente les principaux changements, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_3.png) - -4. Le processus réalise les différentes mises à jour, cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_4.png) - -5. Votre serveur Centreon est maintenant à jour, cliquez sur **Finish** pour -accéder à la page de connexion : - - ![image](../assets/upgrade/web_update_5.png) - - - - -1. Connectez-vous au serveur Central via le terminal pour poursuivre le processus de -mise à jour. - - > Vous avez besoin d'un token d'authentification pour accéder à l'endpoint de l'API. Suivez la procédure ci-dessous pour obtenir un token. - - Dans notre cas, nous avons la configuration décrite ci-dessous (vous devez adapter la procédure à votre configuration). - - - adresse : 10.25.XX.XX - - port : 80 - - version : 26.10 - - identifiant : Admin - - mot de passe : xxxxx - -2. Entrez la requête suivante : - - ```shell - curl --location --request POST '10.25.XX.XX:80/centreon/api/v26.10/login' \ - --header 'Content-Type: application/json' \ - --header 'Accept: application/json' \ - --data '{ - "security": { - "credentials": { - "login": "Admin", - "password": "xxxxx" - } - } - }' - ``` - - Voici à quoi ressemble le résultat : - - ```shell - {"contact":{"id":1,"name":"Admin Centreon","alias":"admin","email":"admin@localhost", "is_admin":true},"security":{"token":"hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S"}} - ``` - -3. Récupérez le numéro du token pour l'utiliser lors de la prochaine requête. - -4. Entrez ensuite cette requête : - - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: hwwE7w/ukiiMce2lwhNi2mcFxLNYPhB9bYSKVP3xeTRUeN8FuGQms3RhpLreDX/S' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` - -5. Cette requête ne renvoie aucun résultat. Pour vérifier que la mise à jour a bien été appliquée, consultez le numéro de version affiché sur la page de connexion à l'interface web Centreon. - - - - -Enfin, redémarrez Broker, Engine et Gorgone sur le serveur Central en exécutant la commande suivante : - - ```shell - systemctl restart cbd centengine gorgoned - ``` - -Mettez à jour les permissions sur les fichiers de configurations de centreon-broker. - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker apache -usermod -a -G apache centreon-broker -``` - - - - -```shell -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -``` - - - - -Référez-vous à la documentation de mise à jour pour [Centreon MBI](../reporting/update.md) et [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. - -### Actions post montée de version - -1. Montée de version des extensions : - - Depuis le menu **Administration > Extensions > Gestionnaire**, mettez à jour - toutes les extensions, en commençant par les suivantes : - - - License Manager, - - Monitoring Connector Manager, - - Auto Discovery. - - Vous pouvez alors mettre à jour toutes les autres extensions commerciales. - -2. Si vous utilisiez des commandes personnalisées pour un collecteur (sur la page **Configuration > Collecteurs > Collecteurs**, dans la section **Monitoring Engine Information**), sachez qu'une nouvelle expression régulière de validation est désormais appliquée (`[a-zA-Z0-9\-\_]+`) : vos commandes personnalisées devront peut-être être adaptées. Sur le serveur central : - * Pour identifier les commandes qui doivent être adaptées, exécutez : - ````shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run - ``` - * Pour adapter automatiquement les commandes, exécutez : - ```shell - sudo -u apache php /usr/share/centreon/bin/console w:m:c - ``` - (Vous pouvez également les adapter manuellement.) - -3. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). - -4. Redémarrez les processus Centreon : - - ```shell - systemctl restart cbd centengine centreontrapd gorgoned - ``` - -## Montée de version des serveurs distants - -Cette procédure est identique à celle utilisée pour effectuer la montée de version d'un serveur Centreon Central, avec en plus la nécessité de récupérer la clé de déchiffrement à la fin. - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP du serveur central afin de permettre au serveur distant de recevoir et traiter des données chiffrées : - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` - -> En fin de mise à jour, la configuration doit être déployée depuis le serveur Central. - -## Montée de version des collecteurs - -### Mise à jour des dépôts - -Exécutez la commande suivante : - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo -``` - - - - -```shell -dnf install -y dnf-plugins-core && \ -rm -f /etc/yum.repos.d/centreon* && \ -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -``` - - - - -```shell -rm -f /etc/apt/sources.list.d/centreon* -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -apt update -``` - - - - -### Montée de version de la solution Centreon - -Videz le cache : - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf clean all --enablerepo=* -``` - - - - -```shell -apt clean all -apt update -``` - - - - -Mettez à jour l'ensemble des composants : - - - - - -```shell -dnf update centreon\* -``` - - - - -```shell -dnf update centreon\* -``` - -> Si vous avez installé MariaDB depuis leurs dépôts officiels, il se peut que vous rencontriez des problèmes de conflits. Suivez notre [procédure sur le sujet](../resources/known-issues.md#vous-avez-un-conflit-entre-les-paquets-mysql-common-et-mariadb-common) pour une solution de contournement. - - - - -```shell -apt install --only-upgrade centreon-poller -``` - - - - - -> Acceptez les nouvelles clés GPG des dépôts si nécessaire. - -Redémarrez **centreon** : - -```shell -systemctl restart centreon -``` - -### Récupération de la clé de déchiffrement - -Exécutez le script suivant avec l'adresse IP correspondante afin de permettre au collecteur de recevoir et traiter des données chiffrées. - -L'adresse IP à utiliser varie selon les conditions suivantes : -- Lorsque vous mettez à jour un collecteur lié directement au server central, utilisez l'adresse IP du serveur central. -- Lorsque vous mettez à jour un collecteur lié à un serveur distant, utilisez l'adresse IP du serveur distant. Cependant, dans ce cas, confirmez d'abord que le server distant a la bonne clé. Vérifiez que la valeur de `app_secret` dans le fichier `/etc/centreon-engine/engine-context.json` du serveur distant est la même que pour le serveur central. Si ce n'est pas le cas, relancez le script avec l'adresse IP pour corriger le fichier .json. - -```shell -/usr/share/centreon/bin/writeEngineSecrets.sh -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password -``` - -> Vous devez utiliser **admin** comme valeur pour **\**. - -Redémarrez **centengine**: - -```shell -systemctl restart centengine -``` + diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md index af21a06c54f3..57f1d4004a9b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md @@ -12,7 +12,7 @@ Vous pouvez potentiellement avoir plusieurs bases MariaDB dans votre architectur Lorsque vous passez d'une version majeure de Centreon à une autre, vous devez : -1. Upgrader Centreon (paquets, installation web, déploiement de la configuration). +1. Upgrader Centreon (paquets, installation web, déploiement de la configuration). NOtez que vous ne pouvez upgrader Centreon [qu'à partir d'un OS encore supporté](upgrade-matrix.mdx). 2. Upgrader MariaDB. > Référez vous à la documentation officielle de MariaDB pour en savoir davantage sur le processus de mise à jour : @@ -28,43 +28,19 @@ Lorsque vous passez d'une version majeure de Centreon à une autre, vous devez : | 24.04 | 10.11 | | 23.10 | 10.5 | | 23.04 | 10.5 | -| 22.10 | 10.5 | -| 22.04 | 10.5 | -| 21.10 | 10.5 | -| 21.04 | 10.5 | -| 20.10 | 10.3.x | -| 20.04 | 10.3.x | -| 19.10 | 10.1.x | ## Connaître la version de MariaDB Pour connaître la version de MariaDB installée sur une machine, tapez la commande suivante : - - -```shell -rpm -qa |grep MariaDB -``` - -Le résultat doit ressembler à ça : - -```shell -MariaDB-client-10.5.8-1.el8.centos.x86_64 -MariaDB-server-10.5.8-1.el8.centos.x86_64 -MariaDB-common-10.5.8-1.el8.centos.x86_64 -MariaDB-shared-10.5.8-1.el8.centos.x86_64 -MariaDB-compat-10.5.8-1.el8.centos.x86_64 -``` - - ```shell rpm -qa |grep MariaDB ``` -Le résultat doit ressembler à ça : +Le résultat pourra ressembler à cet exemple : ```shell MariaDB-client-10.5.8-1.el9.centos.x86_64 @@ -74,27 +50,6 @@ MariaDB-shared-10.5.8-1.el9.centos.x86_64 MariaDB-compat-10.5.8-1.el9.centos.x86_64 ``` - - - -```shell -dpkg -l |grep MariaDB -``` - -Le résultat doit ressembler à ça : - -```shell -ii libdbd-mysql-perl:amd64 4.050-3+b1 amd64 Perl5 database interface to the MariaDB/MySQL database -ii libmariadb3:amd64 1:10.5.17+maria~deb11 amd64 MariaDB database client library -ii mariadb-client-10.5 1:10.5.17+maria~deb11 amd64 MariaDB database client binaries -ii mariadb-client-core-10.5 1:10.5.17+maria~deb11 amd64 MariaDB database core client binaries -ii mariadb-common 1:10.5.17+maria~deb11 all MariaDB common configuration files -ii mariadb-server 1:10.5.17+maria~deb11 all MariaDB database server (metapackage depending on the latest version) -ii mariadb-server-10.5 1:10.5.17+maria~deb11 amd64 MariaDB database server binaries -ii mariadb-server-core-10.5 1:10.5.17+maria~deb11 amd64 MariaDB database core server files -ii mysql-common 1:10.5.17+maria~deb11 all MariaDB database common files (e.g. /etc/mysql/my.cnf) -``` - @@ -111,20 +66,6 @@ Il est nécessaire de désinstaller puis réinstaller MariaDB pour changer de ve 2. Désinstallez la version actuelle : - - -```shell -rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-compat MariaDB-common -``` - - - - -```shell -rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-common -``` - - ```shell @@ -138,23 +79,6 @@ rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared Mari rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-common ``` - - - -Lors de l'étape **[Connaître la version de MariaDB](#connaître-la-version-de-mariadb)**, la commande **grep** vous a renvoyé la version précise de votre MariaDB. - -* Si votre résultat incluait l'indication de version “10.5”, votre commande de désinstallation doit inclure celle-ci, comme dans l’exemple ci-dessous : - -```shell -dpkg -r --ignore-depends=mariadb-server,mariadb-client,mariadb-shared,mariadb-compat,mariadb-common mariadb-server mariadb-server-10.5 mariadb-client mariadb-client-10.5 mariadb-client-core-10.5 mariadb-common mariadb-server-core-10.5 mysql-common -``` - -* Si votre résultat n’incluait pas l'indication de version “10.5”, utilisez la commande suivante : - -```shell -dpkg -r --ignore-depends=mariadb-server,mariadb-client,mariadb-shared,mariadb-compat,mariadb-common mariadb-server mariadb-server mariadb-client mariadb-client mariadb-client-core mariadb-common mariadb-server-core mysql-common -``` - @@ -173,20 +97,6 @@ dpkg -r --ignore-depends=mariadb-server,mariadb-client,mariadb-shared,mariadb-co 3. Installez la version 10.11 : - - -```shell -dnf install mariadb-server-10.11\* mariadb-10.11\* -``` - - - - -```shell -dnf install mariadb-server-10.11\* mariadb-10.11\* -``` - - ```shell @@ -200,23 +110,6 @@ dnf install mariadb-server-10.11\* mariadb-10.11\* dnf install mariadb-server-10.11\* mariadb-10.11\* ``` - - - -```shell -curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=12 --mariadb-server-version="mariadb-10.11" -``` - -```shell -sudo apt-get install mariadb-server galera-4 mariadb-client libmariadb3 mariadb-backup mariadb-common -``` - -Si vous obtenez un message d’erreur indiquant qu’un ou plusieurs paquets MariaDB sont manquants, il faudra modifier la commande afin d’intégrer ces paquets manquants, comme dans l’exemple ci-dessous : - -```shell -sudo apt-get install mariadb-server galera-4 mariadb-client libmariadb3 mariadb-backup mariadb-common PAQUET-MANQUANT_A PAQUET-MANQUANT_B -``` - @@ -291,26 +184,12 @@ Suivez ces étapes pour changer de version mineure de MariaDB (par exemple, pour 1. Mettez à jour MariaDB : - - -```shell -dnf update MariaDB-* -``` - - ```shell dnf update MariaDB-* ``` - - - -```shell -apt update MariaDB-* -``` - diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mysql.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mysql.md index 66b6c927e0c6..f886ebb28c2e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mysql.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mysql.md @@ -14,9 +14,16 @@ Vous pouvez potentiellement avoir plusieurs bases MySQL dans votre architecture. Ne mettez pas à jour votre version de Centreon et votre version de MySQL en même temps. Vous pouvez effectuer les deux mises à jour l'une après l'autre dans l'ordre que vous souhaitez, mais assurez-vous que la première procédure de mise à jour soit entièrement terminée avant d'effectuer la seconde. -## Versions de MySQL compatibles avec Centreon 26.10 +## Version de MySQL pour chaque version de Centreon -* MySQL 8.4 +| Centreon | MySQL | +|----------|---------| +| 26.10 | 8.4 | +| 25.10 | 8.4 (recommandé)
8.0 jusqu'à sa fin de support (avril 2026) | +| 24.10 | 8.4 (recommandé)
8.0 jusqu'à sa fin de support (avril 2026) | +| 24.04 | 8.0 | +| 23.10 | non supporté | +| 23.04 | non supporté | ## Connaître la version de MySQL @@ -47,25 +54,10 @@ mysql Ver 8.0.x for Linux on x86_64 2. Si vous utilisez MBI: - - - Dans le fichier **/etc/my.cnf.d/mysql-server.cnf**, ajoutez `log_bin_trust_function_creators=1`. - - Dans le fichier **/etc/my.cnf.d/mysql-server.cnf**, ajoutez `log_bin_trust_function_creators=1`. - - - - Dans le fichier `/etc/mysql/mysql.cnf`, ajoutez: - - ```shell - [mysqld] - log_bin_trust_function_creators=1 - ``` - From 3d43d52a75f38dd89939499fd96f444e69285886 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 22 Sep 2026 18:01:02 +0200 Subject: [PATCH 068/179] FR upgrade files (2) --- .../upgrade/_upgrade-central.mdx | 326 ++++++++++++++++++ .../upgrade/_upgrade-pollers.mdx | 81 +++++ .../upgrade/_upgrade-remotes.mdx | 27 ++ 3 files changed, 434 insertions(+) create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-pollers.mdx create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-remotes.mdx diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx new file mode 100644 index 000000000000..36da84403296 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx @@ -0,0 +1,326 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import CodeBlock from '@theme/CodeBlock'; + +## Montée de version du serveur Centreon Central + +> Lorsque vous exécutez une commande, vérifiez ce qu'elle affiche. En cas de message d'erreur, arrêtez la procédure et corrigez le problème. + +> Si vous avez installé MariaDB à partir de ses dépôts officiels, vous pouvez rencontrer un conflit. Consultez notre [procédure dédiée](../resources/known-issues.md#vous-avez-un-conflit-entre-les-paquets-mysql-common-et-mariadb-common) pour le contourner. + +### Étape 1 : Installer les nouveaux dépôts + + + + +1. Mettez à jour votre Centreon {props.oldCentreonVersion} jusqu'à la dernière version mineure. + +2. Supprimez les fichiers des dépôts : + + + {`rm /etc/yum.repos.d/centreon-${props.oldCentreonVersion}.repo\nrm /etc/yum.repos.d/centreon.repo`} + + +3. Installez le nouveau dépôt : + +```shell +dnf install -y dnf-plugins-core +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo +``` + + + + +4. Si vous disposez d'une [licence hors ligne](../administration/licenses.md#types-de-licences), supprimez également l'ancien dépôt des connecteurs de supervision, puis installez le nouveau. Vous trouverez l'adresse de ces dépôts sur le [portail du support](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). + +### Étape 2 : Démarrer la montée de version de la solution Centreon + +1. Assurez-vous que tous les utilisateurs sont déconnectés de l'interface web de Centreon avant de démarrer la procédure de montée de version. + +2. Si vous avez installé des extensions Business, supprimez la configuration du dépôt {props.oldCentreonVersion} : + + + + +{`rm /etc/yum.repos.d/centreon-business-${props.oldCentreonVersion}.repo`} + + + + +3. Installez le dépôt Business 26.10 : rendez-vous sur le [portail du support](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories) pour en obtenir l'adresse. + +4. Si votre OS est Debian et que vous avez personnalisé votre configuration Apache, réalisez une sauvegarde de votre fichier de configuration (**/etc/apache2/sites-available/centreon.conf**). + +5. Arrêtez le processus Centreon Broker : + +```shell +systemctl stop cbd +``` + +6. Supprimez les fichiers de rétention existants : + +```shell +rm /var/lib/centreon-broker/* -f +``` + +### Étape 3 : Monter PHP de version + +Centreon 26.10 utilise PHP en version 8.4. + + + + +Vous devez installer le dépôt Remi, puis basculer le flux PHP de la version {props.oldPhpVersion} vers la version 8.4 en exécutant les commandes suivantes : + +```shell +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +rpm -e --nodeps php-sourceguardian-loader +dnf module switch-to php:remi-8.4/common -y +``` + + + + +> Acceptez les nouvelles clés GPG des dépôts si elles vous sont proposées. + +### Étape 4 : Terminer la montée de version de la solution Centreon + +Terminez ensuite la montée de version de la solution Centreon. + +1. Videz le cache : + + + + +```shell +dnf clean all --enablerepo=* +``` + + + + +2. Montez ensuite tous les composants de version à l'aide de la commande suivante : + + + + +```shell +dnf update centreon\* php-pecl-gnupg +``` + + + + +> Acceptez les nouvelles clés GPG des dépôts si elles vous sont proposées. + +### Étape 5 : Mettre à jour votre configuration Apache personnalisée + +Cette section s'applique uniquement si vous avez personnalisé votre configuration Apache. + + + + +Lors de la montée de version, le fichier de configuration Apache n'est pas mis à jour automatiquement : le nouveau fichier de configuration apporté par le rpm ne remplace pas l'ancien. Vous devez reporter les changements manuellement dans votre fichier de configuration personnalisé. + +Faites un diff entre l'ancien et le nouveau fichier de configuration Apache : + +```shell +diff -u /etc/httpd/conf.d/10-centreon.conf /etc/httpd/conf.d/10-centreon.conf.rpmnew +``` + +* **10-centreon.conf** (post montée de version) : ce fichier contient la configuration personnalisée. Il ne contient pas les nouveautés apportées par la montée de version. +* **10-centreon.conf.rpmnew** (post montée de version) : ce fichier est fourni par le rpm ; il ne contient pas la configuration personnalisée. + +Pour chaque différence entre les fichiers, évaluez si celle-ci doit être reportée du fichier **10-centreon.conf.rpmnew** au fichier **10-centreon.conf**. + +Vérifiez qu'Apache est bien configuré en exécutant la commande suivante : + +```shell +apachectl configtest +``` + +Le résultat attendu est le suivant : + +```shell +Syntax OK +``` + +Redémarrez les processus Apache et PHP pour prendre en compte la nouvelle configuration : + +```shell +systemctl restart php-fpm httpd +``` + +Puis vérifiez le statut : + +```shell +systemctl status httpd +``` + +Si tout est correct, vous devriez obtenir : + +```shell +● 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 + +``` + + + + +#### Configuration Apache personnalisée : activer la compression du texte + +Afin d'améliorer la vitesse de chargement des pages, vous pouvez activer la compression du texte sur le serveur Apache. Le paquet **brotli** est nécessaire à son fonctionnement. Cette étape est facultative, mais elle offre une meilleure expérience utilisateur. + +Ajoutez le code suivant à votre fichier de configuration Apache, dans les éléments `` et `` : + +```shell + + AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json + +AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json +``` + +### Étape 6 : Finaliser la montée de version + +1. Avant de démarrer la montée de version via l'interface web, montez de version le [module Centreon BAM](../service-mapping/upgrade.md), puis rechargez le serveur Apache à l'aide de la +commande suivante : + + + + + ```shell + systemctl reload php-fpm httpd + ``` + + + + +2. Finalisez le processus de montée de version : + + + + +1. Connectez-vous à l'interface web de Centreon pour poursuivre le processus de mise à jour. Cliquez sur **Next** : + + ![image](../assets/upgrade/web_update_1.png) + +2. Cliquez sur **Next** : + + ![image](../assets/upgrade/web_update_2.png) + +3. Les notes de version décrivent les principaux changements. Cliquez sur **Next** : + + ![image](../assets/upgrade/web_update_3.png) + +4. Ce processus réalise les différentes mises à jour. Cliquez sur **Next** : + + ![image](../assets/upgrade/web_update_4.png) + +5. Votre serveur Centreon est maintenant à jour. Cliquez sur **Finish** pour accéder à la page +de connexion : + + ![image](../assets/upgrade/web_update_5.png) + +6. [Déployez la configuration du serveur central depuis l'interface web de Centreon](../monitoring/monitoring-servers/deploying-a-configuration.md). + + + + +1. Rendez-vous à la page **Administration > Jetons d'authentification**, puis cliquez sur **Ajouter**. + +3. Copiez le jeton afin de l'utiliser dans la requête suivante. Conservez-le précieusement : il ne sera pas affiché une seconde fois. + +4. Dans votre terminal, saisissez cette requête en utilisant l'adresse IP de votre plateforme et en remplaçant **mytoken** par votre jeton : + + ```shell + curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ + --header 'X-AUTH-TOKEN: mytoken' \ + --header 'Content-Type: application/json' \ + --data '{ + "components": [ + { + "name": "centreon-web" + } + ] + }' + ``` + +5. Cette requête ne renvoie aucun résultat. Pour vérifier que la mise à jour a bien été appliquée, consultez le numéro de version affiché sur la page de connexion de l'interface web de Centreon. + + + + +6. Enfin, redémarrez Broker, Engine et Gorgone sur le serveur central à l'aide de cette commande : + + ```shell + systemctl restart cbd centengine gorgoned + ``` + +7. Mettez à jour les permissions sur les fichiers de configuration de centreon-broker. + + + + + ```shell + usermod -a -G centreon-broker apache + usermod -a -G apache centreon-broker + ``` + + + + +8. Consultez les procédures dédiées à [Centreon MBI](../reporting/update.md) et à [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. + +### Étape 7 : Actions post montée de version + +1. Montez de version les extensions. Depuis le menu **Administration > Extensions > Gestionnaire**, mettez à jour toutes les extensions, en commençant +par les suivantes : + + - License Manager, + - Monitoring Connector Manager, + - Auto Discovery. + + Vous pouvez ensuite mettre à jour toutes les autres extensions commerciales. + +2. Si vous utilisiez des commandes personnalisées pour un collecteur (sur la page **Configuration > Collecteurs > Collecteurs**, dans la section **Monitoring Engine Information**), sachez qu'une nouvelle expression régulière de validation est désormais appliquée (`[a-zA-Z0-9\-\_]+`) : vos commandes personnalisées devront peut-être être adaptées. Sur le serveur central : + * Pour identifier les commandes qui doivent être adaptées, exécutez : + ```shell + sudo -u apache php /usr/share/centreon/bin/console w:m:c --dry-run + ``` + * Pour adapter automatiquement les commandes, exécutez : + ```shell + sudo -u apache php /usr/share/centreon/bin/console w:m:c + ``` + (Vous pouvez également les adapter manuellement.) + +3. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). + +4. Redémarrez les processus : + + ``` shell + systemctl restart cbd centengine centreontrapd gorgoned + ``` + +### Étape 8 : Monter la base de données de version + +
    +
  • Si vous utilisiez MariaDB {props.oldMariadbVersion}, [montez-la de version](upgrade-mariadb.md) vers la version 11.8.
    • + {props.showSecondPoint &&
  • Si vous utilisiez MySQL 8.0, [montez-la de version vers la 8.4](upgrade-mysql.md).
    • } + {props.showThirdPoint &&
  • Si vous utilisiez déjà MySQL 8.4, vous n'avez rien à faire.
    • } +
diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-pollers.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-pollers.mdx new file mode 100644 index 000000000000..365f321d9675 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-pollers.mdx @@ -0,0 +1,81 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +## Montée de version des collecteurs + +### Mise à jour du dépôt Centreon + +Exécutez la commande suivante : + + + + +```shell +dnf install -y dnf-plugins-core && \ +rm -f /etc/yum.repos.d/centreon* && \ +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo +``` + + + + +### Montée de version de la solution Centreon + +Videz le cache : + + + + +```shell +dnf clean all --enablerepo=* +``` + + + + +Montez ensuite tous les composants de version à l'aide de la commande suivante : + + + + +```shell +dnf update centreon\* +``` + +> Si vous avez installé MariaDB à partir de ses dépôts officiels, vous pouvez rencontrer un conflit. Consultez notre [procédure dédiée](../resources/known-issues.md#vous-avez-un-conflit-entre-les-paquets-mysql-common-et-mariadb-common) pour le contourner. + + + + +> Acceptez les nouvelles clés GPG des dépôts si elles vous sont proposées. + +Redémarrez **centreon** : + +```shell +systemctl restart centreon +``` +### Récupération de la clé de déchiffrement + +Exécutez le script suivant avec la bonne adresse IP afin de permettre au collecteur de recevoir et de traiter des données chiffrées. + +L'adresse IP à utiliser dépend des conditions suivantes : +- Pour les collecteurs rattachés directement au serveur central, utilisez l'adresse IP du serveur central. +- Pour les collecteurs rattachés à un serveur distant, utilisez l'adresse IP du serveur distant. Dans ce cas, vous devez toutefois vérifier au préalable que le serveur distant dispose de la bonne clé, en contrôlant que la valeur d'`app_secret` dans le fichier `/etc/centreon-engine/engine-context.json` est identique à celle du serveur central. Si ce n'est pas le cas, relancez le script avec la bonne adresse IP pour corriger le fichier .json. + +```shell +/usr/share/centreon/bin/writeEngineSecrets.sh +``` + +Exemple : + +``` shell +/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password +``` + +> Vous devez utiliser **admin** comme valeur pour **\**. + +Redémarrez **centengine** : + +```shell +systemctl restart centengine +``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-remotes.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-remotes.mdx new file mode 100644 index 000000000000..5fae289385d1 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-remotes.mdx @@ -0,0 +1,27 @@ +## Montée de version des serveurs distants + +Cette procédure est identique à celle utilisée pour monter de version un serveur Centreon Central, avec en plus la nécessité de récupérer la clé de déchiffrement à la fin. + +### Récupération de la clé de déchiffrement + +Exécutez le script suivant avec l'adresse IP du serveur central afin de permettre au serveur distant de recevoir et de traiter des données chiffrées : + +```shell +/usr/share/centreon/bin/writeEngineSecrets.sh +``` + +Exemple : + +``` shell +/usr/share/centreon/bin/writeEngineSecrets.sh https://10.10.10.10/centreon admin password +``` + +> Vous devez utiliser **admin** comme valeur pour **\**. + +Redémarrez **centengine** : + +```shell +systemctl restart centengine +``` + +> En fin de mise à jour, la configuration doit être déployée depuis le serveur central. From 7d0ed93d4b4587c4240d5a1fbca299bf03761a32 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 22 Sep 2026 18:02:33 +0200 Subject: [PATCH 069/179] Update install files, including FR --- .../installation/_centreon-repository.mdx | 38 ++ .../installation/_database-configuration.mdx | 29 +- .../installation/_database-enable-restart.mdx | 11 +- .../installation/_database-local-install.mdx | 48 +- .../installation/_database-remote-install.mdx | 44 +- .../installation/_database-repository.mdx | 49 +- .../installation/_database-tls-conf.mdx | 618 ++++++++++++++++++ .../installation/_dependencies-repository.mdx | 99 +++ .../installation/_install-common.mdx | 148 +++++ .../installation/_interface-tls-conf.mdx | 98 +++ .../installation/_tls-certificates.mdx | 45 ++ .../unattended.md | 185 ++++-- .../using-packages.md | 471 ++----------- .../installation-of-a-poller/unattended.md | 101 ++- .../using-packages.md | 339 +++------- .../unattended.md | 183 ++++-- .../using-packages.md | 542 +++------------ .../version-26.10/upgrade/_intro.mdx | 67 ++ .../installation/_database-configuration.mdx | 12 +- .../installation/_database-tls-conf.mdx | 12 +- .../installation/_tls-certificates.mdx | 10 +- .../unattended.md | 2 +- .../using-packages.md | 6 +- 23 files changed, 1784 insertions(+), 1373 deletions(-) create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_centreon-repository.mdx create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_dependencies-repository.mdx create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_centreon-repository.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_centreon-repository.mdx new file mode 100644 index 000000000000..fa783eccef66 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_centreon-repository.mdx @@ -0,0 +1,38 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + + + + +```shell +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo +dnf clean all --enablerepo=* +dnf update +``` + + + + +```shell +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo +dnf clean all --enablerepo=* +dnf update -y +``` + + + + +```shell +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list +echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list +``` + +Importez ensuite la clé du dépôt : + +```shell +wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 +apt update +``` + + + diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx index 71478c44f36e..85125bbfd35d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx @@ -3,7 +3,7 @@ import TabItem from '@theme/TabItem'; > Il est obligatoire de définir un mot de passe pour l'utilisateur root de la base de données. -Sécurisez l'accès root à MariaDB en exécutant la commande suivante : +Définissez un mot de passe pour l'utilisateur root de la base de données en exécutant la commande suivante : @@ -23,7 +23,7 @@ mysql_secure_installation Ensuite, dans la base de données distante, créez un utilisateur avec des privilèges **root**. Vous devrez entrer cet utilisateur pendant -le processus d'installation web (à [étape 6](./web-and-post-installation.md#étape-6--database-information), +le processus d'installation web (à l'[étape 6](./web-and-post-installation.md#étape-6--database-information), dans les champs **Root user** et **Root password**). ```SQL @@ -72,11 +72,11 @@ DROP USER 'dbadmin'@''; * Idem pour la directive MariaDB **open_files_limit** : -Veuillez noter que les configurations suivantes ne sont que des exemples des possibilités pour une infrastructure avec 8 Go de RAM. Il appartient à chaque utilisateur d'adapter la configuration de la base de données à ses besoins. -Nous vous invitons à vous rapprocher de votre administrateur de base de données pour avoir une configuration qui répond à vos besoins. +Veuillez noter que la configuration suivante n'est qu'un exemple, pour une infrastructure disposant de 8 Go de RAM. Il appartient à chaque utilisateur d'adapter la configuration de la base de données à ses besoins. +Nous vous invitons à vous rapprocher de votre administrateur de base de données pour obtenir une configuration qui réponde à vos besoins. - + > ```shell > $ cat /etc/my.cnf.d/centreon.cnf @@ -96,7 +96,7 @@ Nous vous invitons à vous rapprocher de votre administrateur de base de donnée > ``` - + > ```shell > $ cat /etc/mysql/mariadb.conf.d/80-centreon.cnf @@ -136,11 +136,11 @@ Nous vous invitons à vous rapprocher de votre administrateur de base de donnée * Idem pour la directive MySQL **open_files_limit** : -Veuillez noter que la configuration suivante n'est qu'un exemple pour une infrastructure avec 8 Go de RAM. Il appartient à chaque utilisateur d'adapter la configuration de la base de données à ses besoins. -Nous vous invitons à vous rapprocher de votre administrateur de base de données pour avoir une configuration qui répond à vos besoins. +Veuillez noter que la configuration suivante n'est qu'un exemple, pour une infrastructure disposant de 8 Go de RAM. Il appartient à chaque utilisateur d'adapter la configuration de la base de données à ses besoins. +Nous vous invitons à vous rapprocher de votre administrateur de base de données pour obtenir une configuration qui réponde à vos besoins. - - + + > ```shell > $ cat /etc/my.cnf.d/centreon.cnf @@ -160,7 +160,7 @@ Nous vous invitons à vous rapprocher de votre administrateur de base de donnée > ``` - + > ```shell > $ cat /etc/mysql/mysql.conf.d/80-centreon.cnf @@ -200,12 +200,11 @@ Nous vous invitons à vous rapprocher de votre administrateur de base de donnée > max_allowed_packet = 128M > ``` > -> En option, régler l'utilisation de la mémoire et des tampons du moteur InnoDB alimentant les -> tables. L'exemple ci-dessous s'applique à un serveur de base de données avec 8 Go de RAM. +> Vous pouvez également ajuster l'utilisation de la mémoire et des tampons des tables gérées par le moteur +> InnoDB. L'exemple ci-dessous s'applique à un serveur de base de données disposant de 8 Go de RAM. > > ```shell > innodb_buffer_pool_size=1G > ``` > - -> N'oubliez pas de redémarrer la base de données après modification de la configuration. +> N'oubliez pas de redémarrer la base de données après avoir modifié la configuration. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-enable-restart.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-enable-restart.mdx index 6fa5e6da5c31..e18ae5333ae3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-enable-restart.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-enable-restart.mdx @@ -1,7 +1,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; - + ```shell @@ -12,8 +12,8 @@ systemctl restart mariadb - - + + ```shell systemctl enable mysqld @@ -21,15 +21,14 @@ systemctl restart mysqld ``` - + ```shell systemctl enable mysqld -systemctl restart mysqld ``` - + ```shell systemctl enable mysql diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx index 155330a03fac..d9665f7c2021 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx @@ -1,33 +1,42 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; - + - - + + ```shell dnf install -y centreon-mariadb centreon +``` + +```shell systemctl daemon-reload systemctl restart mariadb ``` - + ```shell dnf install -y centreon-mariadb centreon +``` + +```shell systemctl daemon-reload systemctl restart mariadb ``` - + ```shell apt update apt install -y centreon-mariadb centreon +``` + +```shell systemctl daemon-reload systemctl restart mariadb ``` @@ -35,11 +44,17 @@ systemctl restart mariadb +Définissez un mot de passe pour l'utilisateur root de la base de données en exécutant la commande suivante : + +```shell +mariadb-secure-installation +``` + - - + + ```shell dnf install -y mysql-server mysql @@ -52,26 +67,20 @@ systemctl restart mysqld ``` - + ```shell -dnf install -y mysql-server mysql dnf install -y centreon-mysql centreon -systemctl enable --now mysqld -echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf -sed -Ei 's/LimitNOFILE\s\=\s[0-9]{1,}/LimitNOFILE = 32000/' /usr/lib/systemd/system/$mysql_service_name.service -systemctl daemon-reload -systemctl restart mysqld ``` - + ```shell apt update apt install -y centreon-mysql apt install -y centreon -# Selectionner "Use Legacy Authentication Method" +# Sélectionner "Use Legacy Authentication Method" systemctl daemon-reload systemctl restart mysql ``` @@ -79,5 +88,12 @@ systemctl restart mysql + +Définissez un mot de passe pour l'utilisateur root de la base de données en exécutant la commande suivante : + +```shell +mysql-secure-installation +``` + diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx index 0038d0c6d9d8..d89b10209e5e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx @@ -7,22 +7,22 @@ import DatabaseConfiguration from './_database-configuration.mdx'; Exécutez la commande suivante sur le serveur central : - - + + ```shell dnf install -y centreon-central ``` - + ```shell dnf install -y centreon-central ``` - + ```shell apt update @@ -34,11 +34,11 @@ apt install -y centreon-central Exécutez ensuite les commandes suivantes sur le serveur dédié à votre base de données : - + - - + + ```shell dnf install -y centreon-mariadb @@ -47,7 +47,7 @@ systemctl restart mariadb ``` - + ```shell dnf install -y centreon-mariadb @@ -56,7 +56,7 @@ systemctl restart mariadb ``` - + ```shell apt update @@ -71,19 +71,24 @@ systemctl restart mariadb - - + + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el8-1.noarch.rpm -dnf config-manager --enable mysql-8.4-lts-community -dnf module disable mysql -dnf install mysql-community-server -systemctl start mysqld +dnf install -y mysql-server mysql +dnf install -y centreon-mysql centreon +systemctl enable --now mysqld +echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf +systemctl daemon-reload +systemctl restart mysqld +systemctl list-units --type=service | grep -i mysql +sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld +sudo systemctl start mysqld +sudo systemctl status mysqld ``` - + ```shell dnf install -y mysql-server mysql @@ -99,13 +104,12 @@ sudo systemctl status mysqld ``` - + ```shell apt update apt install -y centreon-mysql -apt install -y centreon -# Selectionner "Use Legacy Authentication Method" +# Sélectionner "Use Legacy Authentication Method" systemctl daemon-reload systemctl restart mysql ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-repository.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-repository.mdx index 16209bcb2211..c62e849147c6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-repository.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-repository.mdx @@ -6,25 +6,24 @@ import TabItem from '@theme/TabItem'; - - + ```shell -dnf module enable -y mariadb:10.11 +curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | bash -s -- --os-type=rhel --os-version=9 --mariadb-server-version=mariadb-11.8 --skip-maxscale ``` - + ```shell -dnf module enable -y mariadb:10.11 +curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | bash -s -- --os-type=rhel --os-version=10 --mariadb-server-version=mariadb-11.8 --skip-maxscale ``` - + ```shell -curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=12 --mariadb-server-version="mariadb-10.11" +curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=13 --mariadb-server-version="mariadb-11.8" --skip-maxscale ``` @@ -34,27 +33,47 @@ curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- - - - + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el8-1.noarch.rpm -y +dnf install -y "https://dev.mysql.com/get/mysql84-community-release-el9-1.noarch.rpm" +curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2025 -o /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 +old_mysql_key=$(rpm -q gpg-pubkey 2>/dev/null | grep -i a8d3785c || true) +if [ -n "$old_mysql_key" ]; then rpm -e $old_mysql_key 2>/dev/null || true; fi +rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 +# install_weak_deps=False : ici, la pile mariadb de la distribution n'est qu'une dépendance recommandée ; +# sans cette option, dnf installe mariadb à côté d'Oracle MySQL et les deux entrent en conflit sur /usr/bin/mysql. +dnf install -y --setopt=install_weak_deps=False mysql-server ``` - + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el9-1.noarch.rpm -y +dnf install -y "https://dev.mysql.com/get/mysql84-community-release-el10-1.noarch.rpm" +curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2025 -o /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 +old_mysql_key=$(rpm -q gpg-pubkey 2>/dev/null | grep -i a8d3785c || true) +if [ -n "$old_mysql_key" ]; then rpm -e $old_mysql_key 2>/dev/null || true; fi +rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 +# install_weak_deps=False : ici, la pile mariadb de la distribution n'est qu'une dépendance recommandée ; +# sans cette option, dnf installe mariadb à côté d'Oracle MySQL et les deux entrent en conflit sur /usr/bin/mysql. +dnf install -y --setopt=install_weak_deps=False mysql-server ``` - + ```shell -wget https://dev.mysql.com/get/mysql-apt-config_0.8.36-1_all.deb -sudo dpkg -i mysql-apt-config_0.8.36-1_all.deb +mysql_apt_config="mysql-apt-config_0.8.34-1_all.deb" +curl -fJLO "https://dev.mysql.com/get/$mysql_apt_config" +echo "mysql-apt-config mysql-apt-config/select-server select mysql-8.4-lts" | debconf-set-selections +export DEBIAN_FRONTEND="noninteractive" +apt install -y "./$mysql_apt_config" +mysql_keyring=$(grep -ohm1 'signed-by=[^] ]*' /etc/apt/sources.list.d/mysql.list 2>/dev/null | cut -d= -f2) +[ -z "$mysql_keyring" ] && mysql_keyring=/etc/apt/trusted.gpg.d/mysql.gpg +( set -o pipefail; curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2025 | gpg --dearmor --yes -o "$mysql_keyring" ) apt update +apt install -y mysql-server mysql-common ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx new file mode 100644 index 000000000000..f81c4b81ae8c --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx @@ -0,0 +1,618 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +Cette section décrit comment mettre en place une connexion TLS entre le serveur central et la base de données. + + + + + + + + +1. Créez le fichier de configuration permettant à la base de données de démarrer en TLS et indiquant les chemins des certificats. + +```shell +cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' +[mariadb] +ssl_ca = /etc/pki/centreon-tls/rootCA.pem +ssl_cert = /etc/pki/centreon-tls/server.pem +ssl_key = /etc/pki/centreon-tls/server-key.pem +require_secure_transport = OFF +tls_version = TLSv1.2,TLSv1.3 +EOF +``` + +2. Attribuez les permissions suivantes à la clé afin qu'elle soit lisible uniquement par l'utilisateur **mysql** : + +```shell +chown root:mysql /etc/pki/centreon-tls/server-key.pem +chmod 0640 /etc/pki/centreon-tls/server-key.pem +``` + +3. Configurez le client MariaDB en ligne de commande pour qu'il utilise TLS (vous en aurez besoin par la suite). + +```shell +cat > /etc/my.cnf.d/centreon-tls-client.cnf <<'EOF' +[client] +ssl-ca=/etc/pki/centreon-tls/rootCA.pem +ssl-verify-server-cert +EOF +``` + +4. Démarrez MariaDB : + +```shell +systemctl daemon-reload +systemctl enable --now mariadb +systemctl restart mariadb +``` + +5. Sécurisez l'installation : + +```shell +mariadb-secure-installation +``` + +6. Vérifiez que le serveur utilise bien les certificats que vous avez définis, et non ceux qu'il génère automatiquement à son démarrage. + +```shell +mariadb -e "SHOW GLOBAL VARIABLES WHERE Variable_name IN ('have_ssl','ssl_ca','ssl_cert','ssl_key');" +``` + +Le résultat attendu est le suivant : + +```shell +have_ssl YES and ssl_ca /etc/pki/centreon-tls/rootCA.pem +``` + +7. Définissez les variables d'environnement que PHP utilisera pour communiquer avec la base de données en mode TLS. + +```shell +for f in /etc/centreon/.env /usr/share/centreon/.env; do + mkdir -p "$(dirname "$f")" + cat >> "$f" <<'EOF' +DATABASE_SSL_ENABLED=1 +DATABASE_VERIFY_SERVER_CERT=1 +DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +EOF +done +``` + + + + +1. Créez le fichier de configuration permettant à la base de données de démarrer en TLS et indiquant les chemins des certificats. + +```shell +cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' +[mariadb] +ssl_ca = /etc/pki/centreon-tls/rootCA.pem +ssl_cert = /etc/pki/centreon-tls/server.pem +ssl_key = /etc/pki/centreon-tls/server-key.pem +require_secure_transport = OFF +tls_version = TLSv1.2,TLSv1.3 +EOF +``` + +2. Attribuez les permissions suivantes à la clé afin qu'elle soit lisible uniquement par l'utilisateur **mysql** : + +```shell +chown root:mysql /etc/pki/centreon-tls/server-key.pem +chmod 0640 /etc/pki/centreon-tls/server-key.pem +``` + +3. Configurez le client MariaDB en ligne de commande pour qu'il utilise TLS (vous en aurez besoin par la suite). + +```shell +cat > /etc/my.cnf.d/centreon-tls-client.cnf <<'EOF' +[client] +ssl-ca=/etc/pki/centreon-tls/rootCA.pem +ssl-verify-server-cert +EOF +``` + +4. Démarrez MariaDB : + +```shell +systemctl daemon-reload +systemctl enable --now mariadb +systemctl restart mariadb +``` + +5. Sécurisez l'installation : + +```shell +mariadb-secure-installation +``` + +6. Vérifiez que le serveur utilise bien les certificats que vous avez définis, et non ceux qu'il génère automatiquement à son démarrage. + +```shell +mariadb -e "SHOW GLOBAL VARIABLES WHERE Variable_name IN ('have_ssl','ssl_ca','ssl_cert','ssl_key');" +``` + +Le résultat attendu est le suivant : + +```shell +have_ssl YES and ssl_ca /etc/pki/centreon-tls/rootCA.pem +``` + +7. Définissez les variables d'environnement que PHP utilisera pour communiquer avec la base de données en mode TLS. + +```shell +for f in /etc/centreon/.env /usr/share/centreon/.env; do + mkdir -p "$(dirname "$f")" + cat >> "$f" <<'EOF' +DATABASE_SSL_ENABLED=1 +DATABASE_VERIFY_SERVER_CERT=1 +DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +EOF +done +``` + + + + +1. Placez les certificats dans un emplacement accessible en lecture par le service de base de données. (Par défaut, sur Debian, MariaDB ne lit que les certificats situés sous **/etc/mysql/**). + +```shell +install -d -o root -g mysql -m 0750 /etc/mysql/centreon-tls +cp /etc/pki/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem +cp /etc/pki/centreon-tls/server.pem /etc/mysql/centreon-tls/server.pem +cp /etc/pki/centreon-tls/server-key.pem /etc/mysql/centreon-tls/server-key.pem +chown root:mysql /etc/mysql/centreon-tls/*.pem +chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/server.pem +chmod 0640 /etc/mysql/centreon-tls/server-key.pem +``` + +2. Configurez le service de base de données pour qu'il démarre en mode TLS et indiquez l'emplacement des certificats. + +```shell +mapfile -t inc < <(grep -oP '^\s*!includedir\s+\K\S+' /etc/mysql/my.cnf) +[ "${#inc[@]}" -eq 0 ] && echo "WARNING: no !includedir in /etc/mysql/my.cnf" >&2 +for d in "${inc[@]}"; do + mkdir -p "$d" + cat > "$d/99-centreon-tls.cnf" <<'EOF' +[mysqld] +ssl_ca = /etc/mysql/centreon-tls/rootCA.pem +ssl_cert = /etc/mysql/centreon-tls/server.pem +ssl_key = /etc/mysql/centreon-tls/server-key.pem +require_secure_transport = OFF +tls_version = TLSv1.2,TLSv1.3 +EOF + chmod 0644 "$d/99-centreon-tls.cnf" +done +``` + +3. Configurez le client MariaDB en ligne de commande pour qu'il utilise TLS (vous en aurez besoin par la suite). + +```shell +cat > /etc/mysql/conf.d/centreon-tls-client.cnf <<'EOF' +[client] +ssl-ca=/etc/mysql/centreon-tls/rootCA.pem +ssl-verify-server-cert +``` + +4. Démarrez MySQL. + +```shell +systemctl daemon-reload +systemctl enable --now mariadb +systemctl restart mariadb +``` + +5. Vérifiez que le serveur utilise bien les certificats que vous avez définis, et non ceux qu'il génère automatiquement à son démarrage. + +```shell +mariadb -e "SHOW GLOBAL VARIABLES WHERE Variable_name IN ('have_ssl','ssl_ca','ssl_cert','ssl_key');" +``` + +Les résultats doivent être les suivants : + +```shell +have_ssl YES and ssl_ca /etc/mysql/centreon-tls/rootCA.pem +``` + +6. Définissez les variables d'environnement que PHP utilisera pour communiquer avec la base de données en mode TLS. + +```shell +for f in /etc/centreon/.env /usr/share/centreon/.env; do + mkdir -p "$(dirname "$f")" + cat >> "$f" <<'EOF' +DATABASE_SSL_ENABLED=1 +DATABASE_VERIFY_SERVER_CERT=1 +DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +EOF +done +``` + + + + + + + + + + + + +1. Créez le fichier de configuration permettant à la base de données de démarrer en TLS et indiquant les chemins des certificats. + +```shell +cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' +[mysqld] +ssl_ca = /etc/pki/centreon-tls/rootCA.pem +ssl_cert = /etc/pki/centreon-tls/server.pem +ssl_key = /etc/pki/centreon-tls/server-key.pem +require_secure_transport = OFF +tls_version = TLSv1.2,TLSv1.3 +EOF +``` + +2. Attribuez les permissions suivantes à la clé afin qu'elle soit lisible uniquement par l'utilisateur **mysql** : + +```shell +chown root:mysql /etc/pki/centreon-tls/server-key.pem +chmod 0640 /etc/pki/centreon-tls/server-key.pem +``` + +3. Configurez le client MySQL en ligne de commande pour qu'il utilise TLS (vous en aurez besoin par la suite). + +```shell +cat > /etc/my.cnf.d/centreon-tls-client.cnf <<'EOF' +[client] +ssl-ca=/etc/pki/centreon-tls/rootCA.pem +ssl-mode=VERIFY_CA +EOF +``` + +4. Démarrez MySQL : + +```shell +systemctl daemon-reload +systemctl enable --now mysqld +systemctl restart mysqld +``` + +5. Vérifiez que le serveur utilise bien les certificats que vous avez définis, et non ceux qu'il génère automatiquement à son démarrage. + +```shell +my_print_defaults mysqld | grep -iE 'ssl|tls' +mysql --ssl-mode=DISABLED -u root -e \ + "SHOW GLOBAL STATUS WHERE Variable_name IN ('Current_tls_ca','Current_tls_cert','Current_tls_key');" +``` + +Les résultats doivent être les suivants : + +```shell +Current_tls_ca /etc/pki/centreon-tls/rootCA.pem +``` + +6. Sécurisez l'installation (dans la commande suivante, remplacez **my_password** par votre propre mot de passe). Définissez le mot de passe de votre choix : + +```shell +db_root_password='ChangeMeStrong#2026' +mysql_root_auth=(--ssl-mode=DISABLED -u root) +if ! mysql --ssl-mode=DISABLED -u root -e "SELECT 1" >/dev/null 2>&1; then + mysql_temp_pw=$(grep 'temporary password is generated for root@localhost' /var/log/mysqld.log \ + 2>/dev/null | tail -1 | sed -E 's/.*root@localhost: //') + if [ -z "$mysql_temp_pw" ]; then + echo "Could not authenticate to MySQL as root" >&2 + exit 1 + fi + mysql_root_auth=(--ssl-mode=DISABLED --connect-expired-password -u root -p"${mysql_temp_pw}") +fi +``` + +Remplacez ensuite le mot de passe généré automatiquement par défaut par le vôtre. + +```shell +mysql "${mysql_root_auth[@]}" --verbose <> "$f" <<'EOF' +DATABASE_SSL_ENABLED=1 +DATABASE_VERIFY_SERVER_CERT=1 +DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +EOF +done +``` + + + + + +1. Créez le fichier de configuration permettant à la base de données de démarrer en TLS et indiquant les chemins des certificats. + +```shell +cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' +[mysqld] +ssl_ca = /etc/pki/centreon-tls/rootCA.pem +ssl_cert = /etc/pki/centreon-tls/server.pem +ssl_key = /etc/pki/centreon-tls/server-key.pem +require_secure_transport = OFF +tls_version = TLSv1.2,TLSv1.3 +EOF +``` + +2. Attribuez les permissions suivantes à la clé afin qu'elle soit lisible uniquement par l'utilisateur **mysql** : + +```shell +chown root:mysql /etc/pki/centreon-tls/server-key.pem +chmod 0640 /etc/pki/centreon-tls/server-key.pem +``` + +3. Configurez le client MySQL en ligne de commande pour qu'il utilise TLS (vous en aurez besoin par la suite). + +```shell +cat > /etc/my.cnf.d/centreon-tls-client.cnf <<'EOF' +[client] +ssl-ca=/etc/pki/centreon-tls/rootCA.pem +ssl-mode=VERIFY_CA +EOF +``` + +4. Démarrez MySQL : + +```shell +systemctl daemon-reload +systemctl enable --now mysqld +systemctl restart mysqld +``` + +5. Vérifiez que le serveur utilise bien les certificats que vous avez définis, et non ceux qu'il génère automatiquement à son démarrage. + +```shell +my_print_defaults mysqld | grep -iE 'ssl|tls' +mysql --ssl-mode=DISABLED -u root -e \ + "SHOW GLOBAL STATUS WHERE Variable_name IN ('Current_tls_ca','Current_tls_cert','Current_tls_key');" +``` + +Les résultats doivent être les suivants : + +```shell +Current_tls_ca /etc/pki/centreon-tls/rootCA.pem +``` + +6. Sécurisez l'installation (dans la commande suivante, remplacez **my_password** par votre propre mot de passe). Définissez le mot de passe de votre choix : + +```shell +db_root_password='my_password' +mysql_root_auth=(--ssl-mode=DISABLED -u root) +if ! mysql --ssl-mode=DISABLED -u root -e "SELECT 1" >/dev/null 2>&1; then + mysql_temp_pw=$(grep 'temporary password is generated for root@localhost' /var/log/mysqld.log \ + 2>/dev/null | tail -1 | sed -E 's/.*root@localhost: //') + if [ -z "$mysql_temp_pw" ]; then + echo "Could not authenticate to MySQL as root" >&2 + exit 1 + fi + mysql_root_auth=(--ssl-mode=DISABLED --connect-expired-password -u root -p"${mysql_temp_pw}") +fi +``` + +Remplacez ensuite le mot de passe généré automatiquement par défaut par le vôtre. + +```shell +mysql "${mysql_root_auth[@]}" --verbose <> "$f" <<'EOF' +DATABASE_SSL_ENABLED=1 +DATABASE_VERIFY_SERVER_CERT=1 +DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +EOF +done +``` + + + + + +1. Placez les certificats dans un emplacement accessible en lecture par le service de base de données. (Par défaut, sur Debian, MySQL ne lit que les certificats situés sous **/etc/mysql/**). + +```shell +install -d -o root -g mysql -m 0750 /etc/mysql/centreon-tls +cp /etc/pki/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem +cp /etc/pki/centreon-tls/server.pem /etc/mysql/centreon-tls/server.pem +cp /etc/pki/centreon-tls/server-key.pem /etc/mysql/centreon-tls/server-key.pem +chown root:mysql /etc/mysql/centreon-tls/*.pem +chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/server.pem +chmod 0640 /etc/mysql/centreon-tls/server-key.pem +``` + +2. Configurez le service de base de données pour qu'il démarre en mode TLS et indiquez l'emplacement des certificats. + +```shell +mapfile -t inc < <(grep -oP '^\s*!includedir\s+\K\S+' /etc/mysql/my.cnf) +[ "${#inc[@]}" -eq 0 ] && echo "WARNING: no !includedir in /etc/mysql/my.cnf" >&2 +for d in "${inc[@]}"; do + mkdir -p "$d" + cat > "$d/99-centreon-tls.cnf" <<'EOF' +[mysqld] +ssl_ca = /etc/mysql/centreon-tls/rootCA.pem +ssl_cert = /etc/mysql/centreon-tls/server.pem +ssl_key = /etc/mysql/centreon-tls/server-key.pem +require_secure_transport = OFF +tls_version = TLSv1.2,TLSv1.3 +EOF + chmod 0644 "$d/99-centreon-tls.cnf" +done +``` + +3. Configurez le client MySQL en ligne de commande pour qu'il utilise TLS (vous en aurez besoin par la suite). + +```shell +cat > /etc/mysql/conf.d/centreon-tls-client.cnf <<'EOF' +[client] +ssl-ca=/etc/mysql/centreon-tls/rootCA.pem +ssl-mode=VERIFY_CA +EOF +``` + +4. Démarrez MySQL. + +```shell +systemctl daemon-reload +systemctl enable --now mysql +systemctl restart mysql +``` + +5. Vérifiez que le serveur utilise bien les certificats que vous avez définis, et non ceux qu'il génère automatiquement à son démarrage. + +```shell +my_print_defaults mysqld | grep -iE 'ssl|tls' +mysql --ssl-mode=DISABLED -u root -N -e \ + "SHOW GLOBAL STATUS WHERE Variable_name IN ('Current_tls_ca','Current_tls_cert','Current_tls_key');" +``` + +Les résultats doivent être les suivants : + +```shell +Current_tls_ca /etc/mysql/centreon-tls/rootCA.pem +``` + +6. Sécurisez l'installation (dans la commande suivante, remplacez **my_password** par votre propre mot de passe). Définissez le mot de passe de votre choix : + +```shell +db_root_password='my_password' +mysql_root_auth=(--ssl-mode=DISABLED -u root) +if ! mysql --ssl-mode=DISABLED -u root -e "SELECT 1" >/dev/null 2>&1; then + mysql_temp_pw=$(grep 'temporary password is generated for root@localhost' /var/log/mysql/error.log \ + 2>/dev/null | tail -1 | sed -E 's/.*root@localhost: //') + if [ -z "$mysql_temp_pw" ]; then + echo "Could not authenticate to MySQL as root" >&2 + exit 1 + fi + mysql_root_auth=(--ssl-mode=DISABLED --connect-expired-password -u root -p"${mysql_temp_pw}") +fi +``` + +Remplacez ensuite le mot de passe généré automatiquement par défaut par le vôtre. + +```shell +mysql "${mysql_root_auth[@]}" --verbose <> "$f" <<'EOF' +DATABASE_SSL_ENABLED=1 +DATABASE_VERIFY_SERVER_CERT=1 +DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +EOF +done +``` + + + + + + diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_dependencies-repository.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_dependencies-repository.mdx new file mode 100644 index 000000000000..18d0cd2e89e6 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_dependencies-repository.mdx @@ -0,0 +1,99 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + + + + +```shell +dnf install dnf-plugins-core +dnf install epel-release +dnf config-manager --set-enabled crb +``` + +Installez et activez PHP 8.4 à l'aide des commandes suivantes : + +```shell +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y +``` + + + + +```shell +dnf install -y dnf-plugins-core +dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms +``` + +Si votre serveur est une instance RHEL dans le cloud, vous devez exécuter la commande suivante : + +```shell +dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms +``` + +Installez et activez PHP 8.4 à l'aide des commandes suivantes : + +```shell +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y +``` + + + + +```shell +dnf install dnf-plugins-core +dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +dnf config-manager --set-enabled ol9_codeready_builder +``` + +Installez et activez PHP 8.4 à l'aide des commandes suivantes : + +```shell +dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm +dnf module switch-to php:remi-8.4/common -y +``` + + + + +```shell +dnf install dnf-plugins-core -y +dnf config-manager --set-enabled crb +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +``` + + + + +```shell +dnf install dnf-plugins-core -y +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms +``` + +Si votre serveur est une instance RHEL dans le cloud, vous devez exécuter la commande suivante : + +```shell +dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms +``` + + + + +```shell +dnf install dnf-plugins-core -y +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +dnf config-manager --set-enabled ol10_codeready_builder +``` + + + + +```shell +apt update && apt install -y lsb-release ca-certificates apt-transport-https wget gnupg2 curl sudo +``` + + + diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx new file mode 100644 index 000000000000..23d0ceaa1d13 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx @@ -0,0 +1,148 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +## Prérequis + +Après avoir installé votre serveur hôte, mettez à jour votre système d'exploitation à l'aide de la +commande suivante : + + + + +```shell +dnf update +``` + +### Configuration supplémentaire pour EL 9 + +Pour utiliser Centreon en français, espagnol, portugais ou allemand, installez les paquets correspondants : + +```shell +dnf install glibc-langpack-fr +dnf install glibc-langpack-es +dnf install glibc-langpack-pt +dnf install glibc-langpack-de +``` + +Utilisez la commande suivante pour vérifier quelles langues sont installées sur votre système : + +```shell +locale -a +``` + + + + +```shell +dnf update +``` + +### Configuration supplémentaire pour EL 10 +Pour utiliser Centreon en français, espagnol, portugais ou allemand, installez les paquets correspondants : + +```shell +dnf install glibc-langpack-fr +dnf install glibc-langpack-es +dnf install glibc-langpack-pt +dnf install glibc-langpack-de +``` + +Utilisez la commande suivante pour vérifier quelles langues sont installées sur votre système : + +```shell +locale -a +``` + + + + +```shell +apt update && apt upgrade +``` + + + + +> Acceptez toutes les clés GPG proposées et redémarrez votre serveur si une mise à jour du noyau est proposée. + +## Étape 1 : Pré-installation + +### Désactiver SELinux + + + + +Pendant l'installation, SELinux doit être désactivé. Éditez le fichier **/etc/selinux/config** et remplacez +**enforcing** par **disabled**, ou bien exécutez la commande suivante : + +```shell +sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config +``` + +Redémarrez votre système d'exploitation pour prendre en compte le changement. + +```shell +reboot +``` + +Après le démarrage du système, effectuez une vérification rapide de l'état de SELinux : + +```shell +getenforce +``` + +Vous devriez obtenir ce résultat : + +```shell +Disabled +``` + +> **Notez que cette désactivation doit être temporaire.** SELinux doit être [réactivé après l'installation](../administration/secure-platform.md#activer-selinux-1) pour des raisons de sécurité. + + + + +Pendant l'installation, SELinux doit être désactivé. Éditez le fichier **/etc/selinux/config** et remplacez +**enforcing** par **disabled**, ou bien exécutez la commande suivante : + +```shell +sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config +``` + +Redémarrez votre système d'exploitation pour prendre en compte le changement. + +```shell +reboot +``` + +Après le démarrage du système, effectuez une vérification rapide de l'état de SELinux : + +```shell +getenforce +``` + +Vous devriez obtenir ce résultat : + +```shell +Disabled +``` + +> **Notez que cette désactivation doit être temporaire.** SELinux doit être [réactivé après l'installation](../administration/secure-platform.md#activer-selinux-1) pour des raisons de sécurité. + + + + +SELinux n'est pas installé sur Debian 13, continuez. + + + + +### Configurer ou désactiver le pare-feu + +Si votre pare-feu est actif, ajoutez les [règles de pare-feu](../administration/secure-platform.md#activer-firewalld). +Vous pouvez également le désactiver le temps de l'installation en exécutant les commandes suivantes : + +```shell +systemctl stop firewalld +systemctl disable firewalld +``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx new file mode 100644 index 000000000000..d9be72accf15 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx @@ -0,0 +1,98 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + + + + +1. Configurez Apache pour TLS : + +```shell +dnf install -y mod_ssl +echo 'Listen 443 https' > /etc/httpd/conf.d/ssl.conf +``` + +2. Renseignez les chemins des certificats dans la configuration HTTPS d'Apache pour Centreon : + +```shell +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ + /usr/share/centreon/examples/centreon-apache-https.conf \ + > /etc/httpd/conf.d/00-centreon-tls.conf +``` + +3. Activez et redémarrez les services Centreon : + +```shell +systemctl daemon-reload +``` + + + + +1. Configurez Apache pour TLS : + +```shell +dnf install -y mod_ssl +echo 'Listen 443 https' > /etc/httpd/conf.d/ssl.conf +``` + +2. Renseignez les chemins des certificats dans la configuration HTTPS d'Apache pour Centreon : + +```shell +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ + /usr/share/centreon/examples/centreon-apache-https.conf \ + > /etc/httpd/conf.d/00-centreon-tls.conf +``` + +3. Activez et redémarrez les services Centreon : + +```shell +systemctl daemon-reload +``` + + + + + +```shell +systemctl restart mariadb +``` + + + + +```shell +systemctl restart mysqld +``` + + + + + + + + +Activez tous les modules référencés par la configuration HTTPS officielle de Centreon : + +```shell +a2enmod ssl proxy proxy_fcgi headers deflate rewrite +``` + +Renseignez les chemins des certificats dans la configuration HTTPS d'Apache pour Centreon : + +```shell +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ + /usr/share/centreon/examples/centreon-apache-https.conf \ + > /etc/apache2/sites-available/00-centreon-tls.conf +``` + +Activez la configuration que vous venez d'appliquer. + +```shell +a2ensite 00-centreon-tls +``` + + + diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx new file mode 100644 index 000000000000..c8fc67862b8e --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx @@ -0,0 +1,45 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +Utilisez un certificat délivré par une autorité de confiance. Les certificats auto-signés peuvent être utilisés à des fins de test, mais ils NE DOIVENT PAS être utilisés en production. + +* Si vous disposez déjà d'un certificat validé par une autorité, passez à l'étape suivante. +* Si vous ne disposez pas d'un certificat validé par une autorité, vous pouvez en générer un sur des plateformes telles que [Let's Encrypt](https://letsencrypt.org/). +* Si, à des fins de test, vous souhaitez utiliser un certificat auto-signé, suivez [cette procédure](../administration/self-signed-certificate.md). + +Supposons que vous disposiez des fichiers suivants dans **/etc/pki/centreon-tls/** : + + * rootCA.pem (public) + * server.pem (certificat du serveur) + * server-key.pem (clé privée du serveur) + * CA/rootCA.\{key,pem\} (définissez les permissions suivantes : root:root, mode 0400) + +1. Installez l'autorité de certification racine dans le trust store du système d'exploitation de la machine hébergeant le serveur central : + + + + + ```shell + cp /etc/pki/centreon-tls/rootCA.pem /etc/pki/ca-trust/source/anchors/centreon-dev.crt + update-ca-trust extract + ``` + + + + + ```shell + cp /etc/pki/centreon-tls/rootCA.pem /etc/pki/ca-trust/source/anchors/centreon-dev.crt + update-ca-trust extract + ``` + + + + + ```shell + cp /etc/pki/centreon-tls/rootCA.pem /usr/local/share/ca-certificates/centreon-dev.crt + ``` + + + + +2. Si vous utilisez une base de données distante, exécutez également cette procédure sur la machine qui hébergera la base de données distante, puis copiez le certificat de l'autorité de certification racine de cette machine dans le trust store de la machine hôte du serveur central. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/unattended.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/unattended.md index 361edad96bed..5b50ffde40cd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/unattended.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/unattended.md @@ -1,91 +1,166 @@ --- id: unattended-install-central title: Installation silencieuse d'un serveur central -description: "Installer rapidement un serveur central à l'aide d'un script" +description: "Installer rapidement un serveur central à l'aide d'un script d'installation silencieuse" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import CodeBlock from '@theme/CodeBlock'; -Pour installer un serveur central plus rapidement, vous pouvez utiliser un script. Le script exécutera la procédure d'installation complète, installation web incluse. +Une installation silencieuse vous permet d'installer un serveur central en passant tous les paramètres requis sous forme d'options au script d'installation. Le script se sert de ces valeurs pour réaliser l'installation par lui-même : la procédure est donc rapide et ne demande presque aucune intervention. -## Procédure d'installation +C'est utile lorsque vous devez installer plusieurs serveurs centraux avec des paramètres identiques, lorsque vous installez depuis un outil de déploiement ou une chaîne d'intégration continue, ou lorsque vous n'avez pas d'accès interactif à la machine cible. + +> Une installation silencieuse configure toujours le serveur central avec une base de données locale. Pour utiliser une base de données distante, [installez le serveur central à partir des paquets](using-packages.md). + +## Prérequis 1. Mettez votre système à jour : - - + + -```shell -dnf update -subscription-manager register --username my_username --password my_password --auto-attach --force -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms + ``` -> Remplacez **my_username** et **my_password** par les identifiants de votre compte RedHat. + Remplacez **my_username** et **my_password** par les identifiants de votre compte Red Hat. - + + - + ```shell + dnf update + ``` -```shell -dnf update -``` + + - - + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms + ``` -```shell -dnf update -subscription-manager register --username my_username --password my_password --auto-attach --force -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms -``` + Remplacez **my_username** et **my_password** par les identifiants de votre compte Red Hat. - - + + -```shell -dnf update -``` + ```shell + dnf update + ``` - - + + -```shell -apt update && apt upgrade -``` + ```shell + apt update && apt upgrade + ``` - - + + + +2. Téléchargez le script : -2. Téléchargez le script à l'aide de la commande suivante : + ```shell + curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh + ``` -```shell -curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh -``` +## Installation -3. Exécutez la commande suivante en **root** : +1. En tant que **root**, exécutez le script avec les options souhaitées. Le script écrit un log complet, comprenant les éventuelles erreurs, dans `/var/log/centreon-unattended-.log`. -* Pour spécifier le mot de passe du compte **admin** par défaut : + Voici la commande de base (elle installe MariaDB et n'utilise pas TLS) : -```shell -bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log -``` + ```shell + bash /tmp/unattended.sh install -t central -v 26.10 + ``` -* Pour obtenir un mot de passe autogénéré pour le compte **admin** par défaut (le script vous indiquera où le mot de passe est stocké) : + Et voici les options que vous pouvez passer (voir les [exemples](#exemples) ci-dessous) : -```shell -bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log -``` + | Option | Description | + |--------|-------------| + | `-d ` | Base de données à installer. Par défaut, le script installe MariaDB : utilisez `-d mysql` pour installer MySQL à la place. | + | `--tls enabled` | Installe le serveur central en mode TLS : les connexions à l'interface web et à la base de données sont chiffrées. Sans cette option, le serveur central est installé sans TLS. Notez que sur certains systèmes d'exploitation, les politiques cryptographiques peuvent empêcher le script de s'exécuter correctement. | + | `-p ` | Mot de passe du compte **admin** par défaut de la base de données. Si vous omettez cette option, le script génère un mot de passe et vous indique où il est stocké. | + | `-s` | Installation silencieuse : le script ne vous demande rien. | + | `-l ` | Niveau de détail du fichier de log : `DEBUG`, `INFO`, `WARN` ou `ERROR`. | -Dans les deux cas, vous obtiendrez un fichier de log complet avec toutes les erreurs dans votre répertoire **tmp**, fichier nommé **unattended(date).log**. + Pour afficher la liste complète des options, exécutez : -> Pour obtenir de l'aide sur le script, utilisez la commande suivante :`bash unattended.sh -h` + ```shell + bash /tmp/unattended.sh -h + ``` -4. Configurez Centreon +2. Rendez-vous sur http(s)://\/centreon (où \ est l'adresse IP de votre serveur) et connectez-vous. Suivez ensuite les étapes + d'[initialisation de la supervision](../web-and-post-installation.md#initialisation-de-la-supervision). -Connectez-vous à l'interface web de Centreon avec l'URL `http://[SERVER_IP]/centreon` en remplaçant [SERVER_IP] par l'adresse IP de votre serveur. -Une fois connecté, suivez les instructions décrites [ici](../web-and-post-installation.md#initialisation-de-la-supervision). +3. Commencez à utiliser Centreon : suivez notre [guide de démarrage](../../getting-started/welcome.md) pour commencer à superviser vos ressources. -5. Commencez à utiliser Centreon +## Exemples -Suivez notre [guide de démarrage](../../getting-started/welcome.md) pour commencer à superviser. + + + +
{ borderRadius: 12, fontSize: 12, fontWeight: 600, - background: r.compat === 'OUI' ? 'var(--ifm-color-success-contrast-background)' : 'var(--ifm-color-danger-contrast-background)', - color: r.compat === 'OUI' ? 'var(--ifm-color-success-dark)' : 'var(--ifm-color-danger-dark)', + background: r.compat === 'YES' ? 'var(--ifm-color-success-contrast-background)' : 'var(--ifm-color-danger-contrast-background)', + color: r.compat === 'YES' ? 'var(--ifm-color-success-dark)' : 'var(--ifm-color-danger-dark)', }}> {r.compat} @@ -120,18 +120,18 @@ export const UpgradeTable = () => { ); }; -Pour rappel, les OS supportés en version 26.10 sont les suivants : +As a reminder, the OSs supported in version 26.10 are the following: * RHEL/Oracle Linux/Alma Linux 9 * RHEL/Oracle Linux/Alma Linux 10 * Debian 13 (trixie) -Cela signifie qu'une simple montée de version n'est possible que si vous utilisiez une version 23.04 ou supérieure, avec RHEL/Oracle Linux/Alma Linux 9. Pour toute autre version et OS, vous devrez effectuer une [migration](../migrate/introduction.md). +This means that a simple upgrade is only possible if you were using version 23.04 or later, on RHEL/Oracle Linux/Alma Linux 9. For any other version and OS, you will need to perform a [migration](../migrate/introduction.md). -## Montée de version ou migration ? +## Upgrade or migration? -{/* ## Cycle de vie des versions +{/* ## Version lifecycle -[Voir le tableau des versions de Centreon supportées](../releases/lifecycle.md#maintenance-table-for-centreon-versions). */} \ No newline at end of file +[See the table of supported Centreon versions](../releases/lifecycle.md#maintenance-table-for-centreon-versions). */} From 2f7ce3da78783b717d175f4c5abd9207a3aa1de0 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 16 Sep 2026 13:35:20 +0200 Subject: [PATCH 057/179] MON-209662 Fix upgrade matrix links --- .../version-24.10/upgrade/upgrade-matrix.mdx | 58 ++++++++--------- .../version-25.10/upgrade/upgrade-matrix.mdx | 64 +++++++++---------- .../version-26.10/upgrade/upgrade-matrix.mdx | 34 +++++----- .../version-24.10/upgrade/upgrade-matrix.mdx | 58 ++++++++--------- .../version-25.10/upgrade/upgrade-matrix.mdx | 64 +++++++++---------- .../version-26.10/upgrade/upgrade-matrix.mdx | 34 +++++----- 6 files changed, 156 insertions(+), 156 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx index 697d386e45e9..f8a9125c647a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx @@ -11,35 +11,35 @@ export const UpgradeTable = () => { const [compat, setCompat] = useState(''); const rows = [ - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-10.md' }, - { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04.md' }, - { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10.md' }, - { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04.md' }, - { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10.md' }, - { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, + { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-10' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04' }, + { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, + { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10' }, + { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04' }, + { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10' }, + { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, ]; const versions = [...new Set(rows.map(r => r.version))]; diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx index f910afcce080..dae65a6548b8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/upgrade/upgrade-matrix.mdx @@ -11,38 +11,38 @@ export const UpgradeTable = () => { const [compat, setCompat] = useState(''); const rows = [ - { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10.md' }, - { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10.md' }, - { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10.md' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04.md' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-10.md' }, - { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04.md' }, - { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10.md' }, - { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04.md' }, - { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10.md' }, - { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, - { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction.md' }, + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10' }, + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-10' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, + { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-10' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04' }, + { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, + { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10' }, + { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04' }, + { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10' }, + { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, ]; const versions = [...new Set(rows.map(r => r.version))]; diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx index 38257c40ac23..79c4637a26cc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -11,23 +11,23 @@ export const UpgradeTable = () => { const [compat, setCompat] = useState(''); const rows = [ - { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-25-10.md' }, - { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-10.md' }, - { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction.md' }, - { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction.md' }, - { version: '22.10 et antérieures', os: 'Voir documentations correspondantes', compat: 'NON', proc: 'Migration depuis EL ou Debian', href: '../migrate/introduction.md' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-25-10' }, + { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-10' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-24-04' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-23-10' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NON', proc: 'Migration depuis EL', href: '../migrate/introduction' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'OUI', proc: 'Montée de version', href: 'upgrade-from-23-04' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Migration depuis Debian', href: '../migrate/introduction' }, + { version: '22.10 et antérieures', os: 'Voir documentations correspondantes', compat: 'NON', proc: 'Migration depuis EL ou Debian', href: '../migrate/introduction' }, ]; const filtered = rows.filter(r => diff --git a/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx index 52036b379c1e..b581732c3657 100644 --- a/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-24.10/upgrade/upgrade-matrix.mdx @@ -11,35 +11,35 @@ export const UpgradeTable = () => { const [compat, setCompat] = useState(''); const rows = [ - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04.md' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-10.md' }, - { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-04.md' }, - { version: '22.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-10.md' }, - { version: '21.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-04.md' }, - { version: '20.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-20-10.md' }, - { version: '20.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '20.04', os: 'RHEL 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, + { version: '22.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-10' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-04' }, + { version: '22.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, + { version: '21.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-10' }, + { version: '21.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-04' }, + { version: '20.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-20-10' }, + { version: '20.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '20.04', os: 'RHEL 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, ]; const versions = [...new Set(rows.map(r => r.version))]; diff --git a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx index aa484dc2c19e..59b256f13026 100644 --- a/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-25.10/upgrade/upgrade-matrix.mdx @@ -11,38 +11,38 @@ export const UpgradeTable = () => { const [compat, setCompat] = useState(''); const rows = [ - { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-10.md' }, - { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-10.md' }, - { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-10.md' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04.md' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-10.md' }, - { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-04.md' }, - { version: '22.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-10.md' }, - { version: '21.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-04.md' }, - { version: '20.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-20-10.md' }, - { version: '20.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, - { version: '20.04', os: 'RHEL 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction.md' }, + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-10' }, + { version: '24.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-10' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-10' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-24-04' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-10' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-23-04' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, + { version: '22.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-10' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-22-04' }, + { version: '22.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration procedure from Debian', href: '../migrate/introduction' }, + { version: '21.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-10' }, + { version: '21.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-21-04' }, + { version: '20.10', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'YES', proc: 'Upgrade procedure', href: 'upgrade-from-20-10' }, + { version: '20.04', os: 'CentOS 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, + { version: '20.04', os: 'RHEL 7', compat: 'NO', proc: 'Migration procedure from EL', href: '../migrate/introduction' }, ]; const versions = [...new Set(rows.map(r => r.version))]; diff --git a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx index d754ac84cbba..e193b5a78806 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx +++ b/versioned_docs/version-26.10/upgrade/upgrade-matrix.mdx @@ -11,23 +11,23 @@ export const UpgradeTable = () => { const [compat, setCompat] = useState(''); const rows = [ - { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction.md' }, - { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-25-10.md' }, - { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction.md' }, - { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction.md' }, - { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-24-10.md' }, - { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-24-04.md' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction.md' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction.md' }, - { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction.md' }, - { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-23-10.md' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction.md' }, - { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction.md' }, - { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-23-04.md' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction.md' }, - { version: '22.10 and earlier', os: 'See the corresponding documentation', compat: 'NO', proc: 'Migration from EL or Debian', href: '../migrate/introduction.md' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction' }, + { version: '25.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-25-10' }, + { version: '25.10', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction' }, + { version: '24.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-24-10' }, + { version: '24.10', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction' }, + { version: '24.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-24-04' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction' }, + { version: '23.10', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-23-10' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 8', compat: 'NO', proc: 'Migration from EL', href: '../migrate/introduction' }, + { version: '23.04', os: 'RHEL/Oracle/AlmaLinux 9', compat: 'YES', proc: 'Upgrade', href: 'upgrade-from-23-04' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NO', proc: 'Migration from Debian', href: '../migrate/introduction' }, + { version: '22.10 and earlier', os: 'See the corresponding documentation', compat: 'NO', proc: 'Migration from EL or Debian', href: '../migrate/introduction' }, ]; const filtered = rows.filter(r => From 29092bc23ec7ddeeb5f57a957b1c5f46fc177970 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 16 Sep 2026 15:46:17 +0200 Subject: [PATCH 058/179] Fix upgrade matrix links --- .../version-24.10/upgrade/upgrade-matrix.mdx | 66 +++++++++-------- .../version-25.10/upgrade/upgrade-matrix.mdx | 72 ++++++++++--------- .../version-26.10/upgrade/upgrade-matrix.mdx | 42 ++++++----- .../version-24.10/upgrade/upgrade-matrix.mdx | 66 +++++++++-------- .../version-25.10/upgrade/upgrade-matrix.mdx | 72 ++++++++++--------- .../version-26.10/upgrade/upgrade-matrix.mdx | 42 ++++++----- 6 files changed, 198 insertions(+), 162 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx index f8a9125c647a..9601a47b4fcd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/upgrade/upgrade-matrix.mdx @@ -4,42 +4,48 @@ title: Matrice des montées de version possibles --- import React, { useState } from 'react'; +import Link from '@docusaurus/Link'; +import { useLocation } from '@docusaurus/router'; export const UpgradeTable = () => { const [version, setVersion] = useState(''); const [os, setOs] = useState(''); const [compat, setCompat] = useState(''); + // Resolve links against the docs root of the current version/locale instead of + // the browser URL: with trailingSlash, relative hrefs resolve one level too deep. + const docsRoot = useLocation().pathname.split('/upgrade/upgrade-matrix')[0] + '/'; + const rows = [ - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04' }, - { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04' }, - { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, - { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-24-04' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10' }, - { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-10' }, - { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04' }, - { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-23-04' }, - { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, - { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-10' }, - { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, - { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-22-04' }, - { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: '../migrate/introduction' }, - { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-10' }, - { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-21-04' }, - { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade-from-20-10' }, - { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, - { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: '../migrate/introduction' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-24-04' }, + { version: '24.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-24-04' }, + { version: '24.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: 'migrate/introduction' }, + { version: '24.04', os: 'Debian 12 "bookworm"', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-24-04' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-23-10' }, + { version: '23.10', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-23-10' }, + { version: '23.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: 'migrate/introduction' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-23-04' }, + { version: '23.04', os: 'RHEL/OracleLinux/AlmaLinux 9', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-23-04' }, + { version: '23.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: 'migrate/introduction' }, + { version: '22.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '22.10', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-22-10' }, + { version: '22.10', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: 'migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux/AlmaLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-22-04' }, + { version: '22.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '22.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '22.04', os: 'Debian 11 "bullseye"', compat: 'NON', proc: 'Procédure de migration depuis Debian', href: 'migrate/introduction' }, + { version: '21.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '21.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-21-10' }, + { version: '21.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '21.04', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-21-04' }, + { version: '20.10', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '20.10', os: 'RHEL/OracleLinux 8', compat: 'OUI', proc: 'Procédure de montée de version', href: 'upgrade/upgrade-from-20-10' }, + { version: '20.04', os: 'CentOS 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, + { version: '20.04', os: 'RHEL 7', compat: 'NON', proc: 'Procédure de migration depuis EL', href: 'migrate/introduction' }, ]; const versions = [...new Set(rows.map(r => r.version))]; @@ -128,7 +134,7 @@ export const UpgradeTable = () => { {r.compat} - {r.proc}{r.proc}
{r.proc}{r.proc}
- {r.proc} + {r.proc}
{r.proc}{r.proc}
{r.proc}{r.proc}
- {r.proc} + {r.proc}
+ + + + + + + + + + + + + + + + + + + + + + + + +
ParamètresCommande
Avec MariaDB, sans TLSbash /tmp/unattended.sh install -t central -v 26.10
Avec MySQL, sans TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql
Avec MariaDB et TLSbash /tmp/unattended.sh install -t central -v 26.10 -s --tls enabled
Avec MySQL et TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql --tls enabled
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParamètresCommande (remplacez XXXXX par le mot de passe de votre choix)
Avec MariaDB, sans TLSbash /tmp/unattended.sh install -t central -v 26.10 -p XXXXX
Avec MySQL, sans TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql -p XXXXX
Avec MariaDB et TLSbash /tmp/unattended.sh install -t central -v 26.10 -s --tls enabled -p XXXXX
Avec MySQL et TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql --tls enabled -p XXXXX
+ + + diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index 797d70663baf..e8afb68eacc0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -1,6 +1,6 @@ --- id: using-packages -title: À partir des paquets +title: À partir des paquets (serveur central) description: "Installer un serveur central Centreon à partir des paquets RPM ou DEB" --- import Tabs from '@theme/Tabs'; @@ -9,322 +9,26 @@ import DatabaseRepository from '../_database-repository.mdx'; import DatabaseLocalInstall from '../_database-local-install.mdx'; import DatabaseRemoteInstall from '../_database-remote-install.mdx'; import DatabaseEnableRestart from '../_database-enable-restart.mdx'; +import DatabaseTlsConf from '../_database-tls-conf.mdx'; +import InstallCommon from '../_install-common.mdx'; +import TlsCertificates from '../_tls-certificates.mdx'; +import InterfaceTlsConf from '../_interface-tls-conf.mdx'; +import CentreonRepository from '../_centreon-repository.mdx'; +import DependenciesRepository from '../_dependencies-repository.mdx'; -Centreon fournit des paquets RPM et DEB pour ses produits via la version Centreon Open Source disponible gratuitement dans notre dépôt. +Vous devez exécuter la procédure d'installation en tant qu'utilisateur privilégié. -Ces paquets peuvent être installés sur Alma/RHEL/Oracle Linux 8 et 9 et sur Debian 12. +> Lorsque vous exécutez une commande, vérifiez les messages obtenus. En cas de message d'erreur, arrêtez la procédure et corrigez le problème. -> Vous devez exécuter la procédure d'installation en tant qu'utilisateur privilégié. +Nous vous recommandons de chiffrer les communications du serveur web comme celles de la base de données, même si ces étapes ne sont pas nécessaires au fonctionnement de Centreon. La procédure ci-dessous met en place ce chiffrement. Dans certains cas (par exemple pour réaliser des tests rapides), vous pouvez préférer une installation non sécurisée : il vous suffit alors d'ignorer l'[étape 3 : Mettre en place la configuration TLS](#étape-3--mettre-en-place-la-configuration-tls). -> Lorsque vous lancez une commande, vérifiez les messagez obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. - -## Prérequis - -Après avoir installé votre serveur, mettez à jour votre système d'exploitation à l'aide de la commande suivante : - - - - -```shell -dnf update -``` - -### Configuration spécifique - -Pour utiliser Centreon en français, espagnol, portugais ou allemand, installez les paquets correspondants : - -```shell -dnf install glibc-langpack-fr -dnf install glibc-langpack-es -dnf install glibc-langpack-pt -dnf install glibc-langpack-de -``` - -Utilisez la commande suivante pour vérifier quelles langues sont installées sur votre système : - -```shell -locale -a -``` - - - - -```shell -dnf update -``` - -### Configuration spécifique - -Pour utiliser Centreon en français, espagnol, portugais ou allemand, installez les paquets correspondants : - -```shell -dnf install glibc-langpack-fr -dnf install glibc-langpack-es -dnf install glibc-langpack-pt -dnf install glibc-langpack-de -``` - -Utilisez la commande suivante pour vérifier quelles langues sont installées sur votre système : - -```shell -locale -a -``` - - - - -```shell -apt update && apt upgrade -``` - - - - -> Acceptez toutes les clés GPG proposées et redémarrez votre serveur -> si une mise à jour du noyau est proposée. - -## Étape 1 : Pré-installation - -### Désactiver SELinux - - - - -Pendant l'installation, SELinux doit être désactivé. Éditez le fichier -**/etc/selinux/config** et remplacez **enforcing** par **disabled**, ou bien -exécutez la commande suivante : - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Redémarrez votre système d'exploitation pour prendre en compte le changement. - -```shell -reboot -``` - -Après le redémarrage, une vérification rapide permet de confirmer le statut de -SELinux : - -```shell -$ getenforce -``` - -Vous devriez obtenir ce résultat : - -```shell -Disabled -``` - -> **Notez que cette désactivation doit être temporaire.** SELinux doit être [réactivé après l'installation](../../administration/secure-platform.md#activer-selinux-1) pour des raisons de sécurité. - - - - -Pendant l'installation, SELinux doit être désactivé. Éditez le fichier -**/etc/selinux/config** et remplacez **enforcing** par **disabled**, ou bien -exécutez la commande suivante : - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Redémarrez votre système d'exploitation pour prendre en compte le changement. - -```shell -reboot -``` - -Après le démarrage du système, effectuez une vérification rapide de l'état de SELinux : - -```shell -getenforce -``` - -Vous devriez obtenir ce résultat : - -```shell -Disabled -``` - -> **Notez que cette désactivation doit être temporaire.** SELinux doit être [réactivé après l'installation](../../administration/secure-platform.md#activer-selinux-1) pour des raisons de sécurité. - - - - -SELinux n'est pas installé sur Debian 12, continuez. - - - - -### Configurer ou désactiver le pare-feu - -Si votre pare-feu système est actif, [paramétrez-le](../../administration/secure-platform.md#activer-firewalld). -Vous pouvez également le désactiver le temps de l'installation : - -```shell -systemctl stop firewalld -systemctl disable firewalld -``` + ### Installer les dépôts - - - -Exécutez les commandes suivantes : - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -dnf config-manager --set-enabled 'powertools' -``` - -Activez PHP 8.2 en utilisant les commandes suivantes : - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -#### Dépôt CodeReady Builder - -Pour installer Centreon, vous devez installer le dépôt **CodeReady Builder**. - -Exécutez les commandes suivantes : - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` - -S'il s'agit d'une instance Cloud RHEL, vous devrez exécuter la commande suivante : - -```shell -dnf config-manager --set-enabled codeready-builder-for-rhel-8-rhui-rpms -``` +#### Dépendances -Activez PHP 8.2 en utilisant les commandes suivantes : - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -#### Dépôt CodeReady Builder - -Pour installer Centreon, vous devez installer le dépôt **CodeReady Builder**. - -Exécutez les commandes suivantes : - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -dnf config-manager --set-enabled ol8_codeready_builder -``` - -Activez PHP 8.2 en utilisant les commandes suivantes : - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -Exécutez les commandes suivantes : - -```shell -dnf install dnf-plugins-core -dnf install epel-release -dnf config-manager --set-enabled crb -``` - -Activez PHP 8.2 avec la commande suivante : - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -Exécutez les commandes suivantes : - -```shell -dnf install -y dnf-plugins-core -dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms -``` - -S'il s'agit d'une instance Cloud RHEL, vous devrez exécuter la commande suivante : - -```shell -dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms -``` - -Activez PHP 8.2 avec la commande suivante : - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -Exécutez les commandes suivantes : - -```shell -dnf install dnf-plugins-core -dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -dnf config-manager --set-enabled ol9_codeready_builder -``` - -Activez PHP 8.2 avec la commande suivante : - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -#### Installer les dépendances - -Installez les dépendances suivantes : - -```shell -apt update && apt install lsb-release ca-certificates apt-transport-https software-properties-common wget gnupg2 curl -``` - -#### Installer le dépôt Sury APT pour PHP 8.2 - -Pour installer le dépôt Sury, exécutez la commande suivante : - -```shell -echo "deb https://packages.sury.org/php/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/sury-php.list -``` - -Puis importez la clé du dépôt : - -```shell -wget -O- https://packages.sury.org/php/apt.gpg | gpg --dearmor | tee /etc/apt/trusted.gpg.d/php.gpg > /dev/null 2>&1 -``` - - - + #### Dépôt de base de données @@ -332,73 +36,49 @@ wget -O- https://packages.sury.org/php/apt.gpg | gpg --dearmor | tee /etc/apt/tr #### Dépôt Centreon -Pour installer le logiciel Centreon, vous devez d'abord installer le dépôt Centreon. + -Installez le dépôt Centreon à l'aide de la commande suivante : +## Étape 2 : Installer le serveur central et la base de données - - +Vous pouvez installer le serveur central avec une base de données locale au serveur, ou +avec une base de données distante sur un serveur dédié. -```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -dnf clean all --enablerepo=* -dnf update -``` - - - - -```shell -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -dnf clean all --enablerepo=* -dnf update -``` - - - + + + + + + + + -```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` +## Étape 3 : Mettre en place la configuration TLS -Ensuite, importez la clé du dépôt : +### Préparer les certificats -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` + - - +### Pour la base de données -## Étape 2 : Installation + -Cette section décrit comment installer un serveur central Centreon. +### Pour l'interface web -Vous pouvez installer ce serveur avec une base de données locale au serveur, ou -une base de données distante sur un serveur dédié. +Cette section décrit comment mettre en place une connexion TLS entre le serveur central et son interface web. - - - - - - - - + -## Étape 3 : Configuration +## Étape 4 : Configuration -### Nom du serveur +### Modifier le nom du serveur (facultatif) -Si vous le souhaitez, vous pouvez changer le nom d'hôte du serveur en utilisant la commande suivante : +Si vous souhaitez changer le nom d'hôte du serveur, utilisez la commande suivante, en remplaçant **new-server-name** par le nom de votre choix : ```shell hostnamectl set-hostname new-server-name ``` -Remplacez **new-server-name** par le nom que vous souhaitez. Exemple : +Exemple : ```shell hostnamectl set-hostname central @@ -409,10 +89,10 @@ hostnamectl set-hostname central Vous devez définir le fuseau horaire de PHP. > Remplacez **Europe/Paris** par votre fuseau horaire. Vous pouvez trouver la liste des -> fuseaux horaires supportés [ici] (http://php.net/manual/en/timezones.php). +> fuseaux horaires pris en charge [ici](http://php.net/manual/en/timezones.php). - - + + Exécutez la commande suivante en tant que `root` : @@ -427,7 +107,7 @@ systemctl restart php-fpm ``` - + Exécutez la commande suivante en tant que `root` : @@ -442,19 +122,18 @@ systemctl restart php-fpm ``` - + ```shell -echo "date.timezone = Europe/Paris" >> /etc/php/8.2/mods-available/centreon.ini +echo "date.timezone = Europe/Paris" >> /etc/php/8.4/mods-available/centreon.ini ``` -> Celui-ci a été défini durant le processus d'installation en récupérant le fuseau horaire configuré sur le -> système d'exploitation. +> Le fuseau horaire de PHP a été défini pendant l'installation à partir du fuseau horaire configuré sur le système d'exploitation. -Après avoir enregistré le fichier, redémarrez le service PHP-FPM : +Après avoir enregistré le fichier, redémarrez le service PHP8.4-FPM : ```shell -systemctl restart php8.2-fpm +systemctl restart php8.4-fpm ``` @@ -465,8 +144,8 @@ systemctl restart php8.2-fpm Pour que les services démarrent automatiquement au démarrage du système, exécutez les commandes suivantes sur le serveur central : - - + + ```shell systemctl enable php-fpm httpd centreon cbd centengine gorgoned snmptrapd centreontrapd snmpd @@ -475,19 +154,20 @@ systemctl start crond ``` - + ```shell systemctl enable php-fpm httpd centreon cbd centengine gorgoned snmptrapd centreontrapd snmpd -systemctl enable crond +systemctl enable --now crond systemctl start crond ``` - + ```shell -systemctl enable php8.2-fpm apache2 centreon cbd centengine gorgoned centreontrapd snmpd snmptrapd +systemctl enable apache2 php8.4-fpm centreon cbd centengine gorgoned snmptrapd centreontrapd snmpd +systemctl enable --now cron ``` @@ -497,62 +177,27 @@ Exécutez ensuite la commande suivante (sur le serveur central si vous utilisez -### Sécuriser la base de données - -Il est obligatoire de sécuriser l'accès root de la base de données avant d'installer Centreon. -Si vous utilisez une base de données locale, exécutez la commande suivante sur le serveur central : - - - - -```shell -mariadb-secure-installation -``` - - - - -Récupérez le mot de passe temporaire créé par MySQL : - -```shell -grep 'temporary password' /var/log/mysqld.log -``` - -Puis modifiez-le lorsque la commande suivante vous y invite : - -```shell -mysql_secure_installation -``` - - - - -* Répondez **oui** à toutes les questions, sauf à "Disallow root login remotely ?". -* Il est obligatoire de définir un mot de passe pour l'utilisateur **root** de la base de données. Ce mot de passe vous sera demandé pendant l'[installation web](../web-and-post-installation.md). - -> Pour plus d'informations, veuillez consulter la [documentation officielle de MariaDB](https://mariadb.com/kb/en/mysql_secure_installation/). - -## Étape 4 : Installation web +## Étape 5 : Installation web 1. Démarrez le serveur Apache avec la commande suivante : - - + + ```shell systemctl start httpd ``` - + ```shell systemctl start httpd ``` - + ```shell systemctl start apache2 diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/unattended.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/unattended.md index 64860b2b495a..7cfb13d7abe4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/unattended.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/unattended.md @@ -1,82 +1,81 @@ --- id: unattended-install-poller title: Installation silencieuse d'un collecteur -description: "Installer rapidement un collecteur à l'aide d'un script" +description: "Installer rapidement un collecteur à l'aide d'un script d'installation silencieuse" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Pour installer un collecteur plus rapidement, vous pouvez utiliser un script. Le script exécutera les étapes d'installation proprement dites. Vous devrez ensuite enregistrer le collecteur et le rattacher au serveur central ou au serveur distant. +Pour installer un collecteur rapidement, vous pouvez utiliser un script. -## Procédure d'installation +C'est utile lorsque vous devez installer plusieurs collecteurs avec des paramètres identiques, lorsque vous installez depuis un outil de déploiement ou une chaîne d'intégration continue, ou lorsque vous n'avez pas d'accès interactif à la machine cible. -1. Mettez votre système à jour : +Le script exécutera toutes les étapes de l'installation. Vous devrez ensuite [rattacher le collecteur au serveur central ou à un serveur distant](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). - - +## Prérequis -```shell -dnf update -subscription-manager register --username my_username --password my_password --auto-attach --force -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` +1. Mettez votre système à jour : -> Remplacez **my_username** et **my_password** par les identifiants de votre compte RedHat. + + - + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms + ``` - + Remplacez **my_username** et **my_password** par les identifiants de votre compte Red Hat. -```shell -dnf update -``` + + - - + ```shell + dnf update + ``` -```shell -dnf update -subscription-manager register --username my_username --password my_password --auto-attach --force -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms -``` + + - - + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms + ``` -```shell -dnf update -``` + Remplacez **my_username** et **my_password** par les identifiants de votre compte Red Hat. - - + + -```shell -apt update && apt upgrade -``` + ```shell + dnf update + ``` - - + + -2. Téléchargez le script à l'aide de la commande suivante : + ```shell + apt update && apt upgrade + ``` -```shell -curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh -``` + + -3. Exécutez la commande suivante en **root** : +2. Téléchargez le script : -```shell -bash /tmp/unattended.sh install -t poller -v 26.10 -r stable -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log -``` + ```shell + curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh + ``` - Vous obtiendrez un fichier de log complet avec toutes les erreurs dans votre répertoire **tmp**, fichier nommé **unattended(date).log**. +## Procédure d'installation -4. Une fois le script exécuté, suivez les [étapes 3 à 5 de la procédure d'installation d'un collecteur](using-packages.md#étape-3--enregistrer-le-serveur). +1. Exécutez la commande suivante en tant que **root** : -## Aide + ```shell + bash /tmp/unattended.sh install -t poller -v 26.10 -r stable -l DEBUG 2>&1 + ``` -Pour obtenir de l'aide sur le script, utilisez la commande suivante : + Le script écrit un journal complet, comprenant les éventuelles erreurs, dans `/var/log/centreon-unattended-.log`. -```shell -bash unattended.sh -h -``` +2. Une fois le script exécuté, [rattachez le collecteur au serveur central ou à un serveur distant](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-packages.md index 22885ca3eecf..b9574bfd65ae 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-packages.md @@ -1,270 +1,103 @@ --- id: using-packages -title: À partir des paquets +title: À partir des paquets (collecteur) description: "Installer et enregistrer un collecteur à partir des paquets RPM ou DEB" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import InstallCommon from '../_install-common.mdx'; -Centreon fournit des paquets RPM et DEB pour ses produits au travers de la solution -Centreon Open Sources disponible gratuitement sur notre dépôt. +Vous devez exécuter la procédure d'installation en tant qu'utilisateur privilégié. -Les paquets peuvent être installés sur Alma/RHEL/Oracle Linux 8 et 9 ou Debian 12. +> Lorsque vous exécutez une commande, vérifiez ce qu'elle affiche. En cas de message d'erreur, arrêtez la procédure et corrigez le problème. -L'ensemble de la procédure d'installation doit être faite en tant qu'utilisateur privilégié. + -> Lorsque vous lancez une commande, vérifiez les messagez obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. - -## Prérequis - -Après avoir installé votre serveur, réalisez la mise à jour de votre système -d'exploitation via la commande : - - - - -```shell -dnf update -``` - -### Configuration spécifique - -Pour utiliser Centreon en français, espagnol, portugais ou allemand, installez les paquets correspondants : - -```shell -dnf install glibc-langpack-fr -dnf install glibc-langpack-es -dnf install glibc-langpack-pt -dnf install glibc-langpack-de -``` - -Utilisez la commande suivante pour vérifier quelles langues sont installées sur votre système : - -```shell -locale -a -``` - - - - -```shell -dnf update -``` - -### Configuration spécifique - -Pour utiliser Centreon en français, espagnol, portugais ou allemand, installez les paquets correspondants : - -```shell -dnf install glibc-langpack-fr -dnf install glibc-langpack-es -dnf install glibc-langpack-pt -dnf install glibc-langpack-de -``` - -Utilisez la commande suivante pour vérifier quelles langues sont installées sur votre système : - -```shell -locale -a -``` - - - - -```shell -apt update && apt upgrade -``` - - - - -> Acceptez toutes les clés GPG proposées et redémarrez votre serveur -> si une mise à jour du noyau est proposée. - -## Étape 1 : Pré-installation - -### Désactiver SELinux - - - - -Pendant l'installation, SELinux doit être désactivé. Éditez le fichier -**/etc/selinux/config** et remplacez **enforcing** par **disabled**, ou bien -exécutez la commande suivante : - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Redémarrez votre système d'exploitation pour prendre en compte le changement. - -```shell -reboot -``` - -Après le redémarrage, une vérification rapide permet de confirmer le statut de -SELinux : - -```shell -$ getenforce -Disabled -``` - -> **Notez que cette désactivation doit être temporaire.** SELinux doit être [réactivé après l'installation](../../administration/secure-platform.md#activer-selinux-1) pour des raisons de sécurité. - - - - -Pendant l'installation, SELinux doit être désactivé. Éditez le fichier -**/etc/selinux/config** et remplacez **enforcing** par **disabled**, ou bien -exécutez la commande suivante : - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Redémarrez votre système d'exploitation pour prendre en compte le changement. - -```shell -reboot -``` - -Après le redémarrage, une vérification rapide permet de confirmer le statut de -SELinux : - -```shell -$ getenforce -Disabled -``` - -> **Notez que cette désactivation doit être temporaire.** SELinux doit être [réactivé après l'installation](../../administration/secure-platform.md#activer-selinux-1) pour des raisons de sécurité. - - - - -SELinux n'est pas installé sur Debian 12, continuez. - - - - -### Configurer ou désactiver le pare-feu - -Paramétrez le pare-feu système ou désactivez ce dernier. Pour désactiver ce -dernier exécutez les commandes suivantes : + ### Installer les dépôts - - +#### Dépendances -#### Dépôt Redhat CodeReady Builder + + -Pour installer Centreon, vous devez installer le dépôt **CodeReady Builder**. ```shell -dnf -y install dnf-plugins-core https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms +dnf install dnf-plugins-core +dnf install epel-release +dnf config-manager --set-enabled crb ``` -S'il s'agit d'une instance Cloud RHEL, vous devrez exécuter la commande suivante : + + ```shell -dnf config-manager --set-enabled codeready-builder-for-rhel-8-rhui-rpms +dnf install -y dnf-plugins-core +dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms ``` - - - -#### Dépôt PowerTools de Red Hat - -Afin d'installer les logiciels Centreon, le dépôt PowerTools de Red Hat doit être -activé. - -Exécutez les commandes suivantes : +Si votre serveur est une instance RHEL dans le cloud, vous devez exécuter la commande suivante : ```shell -dnf -y install dnf-plugins-core epel-release -dnf config-manager --set-enabled powertools +dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms ``` - - -#### Dépôt CodeReady Builder de Oracle - -Afin d'installer les logiciels Centreon, le dépôt CodeReady Builder de Oracle -doit être activé. - -Exécutez les commandes suivantes : + ```shell -dnf -y install dnf-plugins-core oracle-epel-release-el8 -dnf config-manager --set-enabled ol8_codeready_builder +dnf install -y dnf-plugins-core +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +dnf config-manager --set-enabled ol9_codeready_builder ``` - - -Exécutez les commandes suivantes : + ```shell -dnf install dnf-plugins-core -dnf install epel-release +dnf install dnf-plugins-core -y dnf config-manager --set-enabled crb +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm ``` - - -Exécutez les commandes suivantes : + ```shell -dnf install -y dnf-plugins-core -dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms +dnf install dnf-plugins-core -y +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms ``` -S'il s'agit d'une instance Cloud RHEL, vous devrez exécuter la commande suivante : +Si votre serveur est une instance RHEL dans le cloud, vous devez exécuter la commande suivante : ```shell dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms ``` - - -Exécutez les commandes suivantes : + ```shell -dnf install dnf-plugins-core -dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -dnf config-manager --set-enabled ol9_codeready_builder +dnf install dnf-plugins-core -y +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm +dnf config-manager --set-enabled ol10_codeready_builder ``` - - -Installez les dépendances suivantes : + ```shell apt update && apt install lsb-release ca-certificates apt-transport-https software-properties-common wget gnupg2 curl @@ -275,43 +108,35 @@ apt update && apt install lsb-release ca-certificates apt-transport-https softwa #### Dépôt Centreon -Afin d’installer les logiciels Centreon à partir des dépôts, vous devez au -préalable installer le fichier lié au dépôt. - -Exécutez la commande suivante à partir d’un utilisateur possédant les droits -suffisants : - - + ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` - + ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` - - -Pour installer le dépôt Centreon, exécutez la commande suivante : + ```shell echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` -Puis importez la clé du dépôt : +Importez ensuite la clé du dépôt : ```shell wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 @@ -321,26 +146,26 @@ apt update -## Étape 2 : Installation +## Étape 2 : Installer le serveur -Pour installer le moteur de supervision, exécutez la commande : +Pour installer le moteur de supervision, exécutez la commande suivante : - + ```shell dnf install -y centreon-poller ``` - + ```shell dnf install -y centreon-poller ``` - + ```shell apt install -y --no-install-recommends centreon-poller @@ -349,10 +174,10 @@ apt install -y --no-install-recommends centreon-poller -Pour activer le démarrage automatique des services de supervision au démarrage -du serveur, exécuter la commande suivante : +Pour que les services démarrent automatiquement au démarrage du système, exécutez la +commande suivante : -```shell +``` shell systemctl enable centreon centengine centreontrapd snmptrapd gorgoned ``` @@ -368,52 +193,49 @@ Redémarrez Centreon Engine : systemctl restart centengine ``` -## Étape 3 : Enregistrer le serveur + -## Étape 4 : Ajouter le Poller à la configuration +## Étape 3 : Rattacher le collecteur à un serveur central ou distant -Rendez-vous au chapitre [Ajouter un Poller à la configuration](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). +Rendez-vous au chapitre [Rattacher un collecteur à un serveur central ou distant](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md). -## Étape 5 : Sécuriser votre plateforme +## Étape 4 : Sécuriser votre plateforme N'oubliez pas de sécuriser votre plateforme Centreon en suivant nos -[recommandations](../../administration/secure-platform.md) +[recommandations](../../administration/secure-platform.md). diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/unattended.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/unattended.md index dba6892f9fc7..b93a4cac41a9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/unattended.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/unattended.md @@ -1,90 +1,163 @@ --- id: unattended-install-remote title: Installation silencieuse d'un serveur distant -description: "Installer rapidement un serveur distant à l'aide d'un script" +description: "Installer rapidement un serveur distant à l'aide d'un script d'installation silencieuse" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import CodeBlock from '@theme/CodeBlock'; -Pour installer un serveur distant plus rapidement, vous pouvez utiliser un script. Le script exécutera les étapes d'installation proprement dites. Vous devrez ensuite enregistrer le serveur distant et le rattacher au serveur central. +Pour installer un serveur distant plus rapidement, vous pouvez utiliser un script. Celui-ci exécutera toutes les étapes de l'installation. Vous devrez ensuite enregistrer le serveur distant et le rattacher au serveur central. -## Procédure d'installation +## Prérequis 1. Mettez votre système à jour : - - + + -```shell -dnf update -subscription-manager register --username my_username --password my_password --auto-attach --force -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms + ``` -> Remplacez **my_username** et **my_password** par les identifiants de votre compte RedHat. + Remplacez **my_username** et **my_password** par les identifiants de votre compte Red Hat. - + + - + ```shell + dnf update + ``` -```shell -dnf update -``` + + - - + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms + ``` -```shell -dnf update -subscription-manager register --username my_username --password my_password --auto-attach --force -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms -``` + Remplacez **my_username** et **my_password** par les identifiants de votre compte Red Hat. - - + + -```shell -dnf update -``` + ```shell + dnf update + ``` - - + + -```shell -apt update && apt upgrade -``` + ```shell + apt update && apt upgrade + ``` - - + + -2. Téléchargez le script à l'aide de la commande suivante : +2. Téléchargez le script : -```shell -curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh -``` + ```shell + curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh + ``` -3. Exécutez la commande suivante en **root** : +## Installation -* Pour spécifier le mot de passe du compte **admin** par défaut : +1. En tant que **root**, exécutez le script avec les options souhaitées. Le script écrit un journal complet, comprenant les éventuelles erreurs, dans `/var/log/centreon-unattended-.log`. -```shell -bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -p -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log -``` + Voici la commande de base (elle installe MariaDB sans TLS) : -* Pour obtenir un mot de passe autogénéré pour le compte **admin** par défaut (le script vous indiquera où le mot de passe est stocké) : + ```shell + bash /tmp/unattended.sh install -t central -v 26.10 + ``` -```shell -bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -l DEBUG 2>&1 |tee -a /tmp/unattended-$(date +"%m-%d-%Y-%H%M%S").log -``` + Et voici les options que vous pouvez passer (voir les [exemples](#exemples) ci-dessous) : -Dans les deux cas, vous obtiendrez un fichier de log complet avec toutes les erreurs dans votre répertoire **tmp**, fichier nommé **unattended(date).log**. + | Option | Description | + |--------|-------------| + | `-d ` | Base de données à installer. Par défaut, le script installe MariaDB : utilisez `-d mysql` pour installer MySQL à la place. | + | `--tls enabled` | Installe le serveur central en mode TLS : les connexions à l'interface web et à la base de données sont chiffrées. Sans cette option, le serveur central est installé sans TLS. Notez que sur certains systèmes d'exploitation, les politiques cryptographiques peuvent empêcher le script de s'exécuter correctement. | + | `-p ` | Mot de passe du compte **admin** par défaut de la base de données. Si vous omettez cette option, le script génère un mot de passe et vous indique où il est stocké. | + | `-s` | Installation silencieuse : le script ne vous demande rien. | + | `-l ` | Niveau de détail du fichier de journal : `DEBUG`, `INFO`, `WARN` ou `ERROR`. | -4. Une fois le script exécuté, suivez les [étapes 5 à 8 de la procédure d'installation standard d'un serveur distant](using-packages.md#étape-5--enregistrer-le-remote-server). + Pour afficher la liste complète des options, exécutez : -## Aide + ```shell + bash /tmp/unattended.sh -h + ``` -Pour obtenir de l'aide sur le script, utilisez la commande suivante : +2. Rendez-vous sur http(s)://\/centreon (où \ est l'adresse IP de votre serveur) et connectez-vous. Suivez ensuite les étapes d'[initialisation de la supervision](../web-and-post-installation.md#initialisation-de-la-supervision). -```shell -bash unattended.sh -h -``` +3. Une fois le script exécuté, réalisez les [étapes 5 à 8 de la procédure d'installation standard d'un serveur distant](./using-packages.md#étape-5--installation-web). + +4. Commencez à utiliser Centreon : suivez notre [guide de démarrage](../../getting-started/welcome.md) pour commencer à superviser vos ressources. + +## Exemples + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParamètresCommande
Avec MariaDB, sans TLSbash /tmp/unattended.sh install -t central -v 26.10
Avec MySQL, sans TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql
Avec MariaDB et TLSbash /tmp/unattended.sh install -t central -v 26.10 -s --tls enabled
Avec MySQL et TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql --tls enabled
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ParamètresCommande (remplacez XXXXX par le mot de passe de votre choix)
Avec MariaDB, sans TLSbash /tmp/unattended.sh install -t central -v 26.10 -p XXXXX
Avec MySQL, sans TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql -p XXXXX
Avec MariaDB et TLSbash /tmp/unattended.sh install -t central -v 26.10 -s --tls enabled -p XXXXX
Avec MySQL et TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql --tls enabled -p XXXXX
+ + + diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md index c207672699f6..1c182cdbfe02 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md @@ -1,6 +1,6 @@ --- id: using-packages -title: À partir des paquets +title: À partir des paquets (serveur distant) description: "Installer et enregistrer un serveur distant à partir des paquets RPM ou DEB" --- import Tabs from '@theme/Tabs'; @@ -9,411 +9,89 @@ import DatabaseRepository from '../_database-repository.mdx'; import DatabaseLocalInstall from '../_database-local-install.mdx'; import DatabaseRemoteInstall from '../_database-remote-install.mdx'; import DatabaseEnableRestart from '../_database-enable-restart.mdx'; +import DatabaseTlsConf from '../_database-tls-conf.mdx'; +import InstallCommon from '../_install-common.mdx'; +import TlsCertificates from '../_tls-certificates.mdx'; +import InterfaceTlsConf from '../_interface-tls-conf.mdx'; +import CentreonRepository from '../_centreon-repository.mdx'; +import DependenciesRepository from '../_dependencies-repository.mdx'; -Centreon fournit des paquets RPM et DEB pour ses produits au travers de la solution -Centreon Open Source disponible gratuitement sur notre dépôt. +Vous devez exécuter la procédure d'installation en tant qu'utilisateur privilégié. -Les paquets peuvent être installés sur Alma/RHEL/Oracle Linux 8 et 9, et Debian 12. +> Lorsque vous exécutez une commande, vérifiez ce qu'elle affiche. En cas de message d'erreur, arrêtez la procédure et corrigez le problème. -L'ensemble de la procédure d'installation doit être faite en tant qu'utilisateur privilégié. +Nous vous recommandons de chiffrer les communications du serveur web comme celles de la base de données, même si ces étapes ne sont pas nécessaires au fonctionnement de Centreon. La procédure ci-dessous met en place ce chiffrement. Dans certains cas (par exemple pour réaliser des tests rapides), vous pouvez préférer une installation non sécurisée : il vous suffit alors d'ignorer l'[étape 3 : Mettre en place la configuration TLS](#étape-3--mettre-en-place-la-configuration-tls). -> Lorsque vous lancez une commande, vérifiez les messagez obtenus. En cas de message d'erreur, arrêtez la procédure et dépannez les problèmes. + -## Prérequis +#### Dépendances -Après avoir installé votre serveur, réalisez la mise à jour de votre système -d'exploitation via la commande : + - - - -```shell -dnf update -``` - -### Configuration spécifique - -Pour utiliser Centreon en français, espagnol, portugais ou allemand, installez les paquets correspondants : - -```shell -dnf install glibc-langpack-fr -dnf install glibc-langpack-es -dnf install glibc-langpack-pt -dnf install glibc-langpack-de -``` - -Utilisez la commande suivante pour vérifier quelles langues sont installées sur votre système : - -```shell -locale -a -``` - - - - -```shell -dnf update -``` - -### Configuration spécifique - -Pour utiliser Centreon en français, espagnol, portugais ou allemand, installez les paquets correspondants : - -```shell -dnf install glibc-langpack-fr -dnf install glibc-langpack-es -dnf install glibc-langpack-pt -dnf install glibc-langpack-de -``` - -Utilisez la commande suivante pour vérifier quelles langues sont installées sur votre système : - -```shell -locale -a -``` - - - - -``` shell -apt update && apt upgrade -``` - - - - -> Acceptez toutes les clés GPG proposées et redémarrez votre serveur -> si une mise à jour du noyau est proposée. - -## Étape 1 : Pré-installation - -### Désactiver SELinux - - - - -Pendant l'installation, SELinux doit être désactivé. Éditez le fichier -**/etc/selinux/config** et remplacez **enforcing** par **disabled**, ou bien -exécutez la commande suivante : - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Redémarrez votre système d'exploitation pour prendre en compte le changement. - -```shell -reboot -``` - -Après le redémarrage, une vérification rapide permet de confirmer le statut de -SELinux : - -```shell -$ getenforce -Disabled -``` - -> **Notez que cette désactivation doit être temporaire.** SELinux doit être [réactivé après l'installation](../../administration/secure-platform.md#activer-selinux-1) pour des raisons de sécurité. - - - - -Pendant l'installation, SELinux doit être désactivé. Éditez le fichier -**/etc/selinux/config** et remplacez **enforcing** par **disabled**, ou bien -exécutez la commande suivante : - -```shell -sed -i s/^SELINUX=.*$/SELINUX=disabled/ /etc/selinux/config -``` - -Redémarrez votre système d'exploitation pour prendre en compte le changement. - -```shell -reboot -``` - -Après le redémarrage, une vérification rapide permet de confirmer le statut de -SELinux : - -```shell -$ getenforce -Disabled -``` - -> **Notez que cette désactivation doit être temporaire.** SELinux doit être [réactivé après l'installation](../../administration/secure-platform.md#activer-selinux-1) pour des raisons de sécurité. - - - - -SELinux n'est pas installé sur Debian 12, continuez. - - - - -### Configurer ou désactiver le pare-feu - -Si votre pare-feu système est actif, [paramétrez-le](../../administration/secure-platform.md#activer-firewalld). -Vous pouvez également le désactiver le temps de l'installation : - -```shell -systemctl stop firewalld -systemctl disable firewalld -``` - -> Vous pouvez trouver des instructions [ici](../../administration/secure-platform.md#activer-firewalld) -> pour configurer le pare-feu. - -### Installer les dépôts - - - - -Exécutez les commandes suivantes : - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -dnf config-manager --set-enabled 'powertools' -``` - -Activez PHP 8.2 en utilisant les commandes suivantes : - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -#### Dépôt CodeReady Builder - -Afin d'installer les logiciels Centreon, le dépôt **CodeReady Builder** doit être installé. - -Exécutez les commandes suivantes : - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms -``` - -S'il s'agit d'une instance Cloud RHEL, vous devrez exécuter la commande suivante : - -```shell -dnf config-manager --set-enabled codeready-builder-for-rhel-8-rhui-rpms -``` - -Activez PHP 8.2 en utilisant les commandes suivantes : - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - - -#### Dépôt CodeReady Builder - -Afin d'installer les logiciels Centreon, le dépôt **CodeReady Builder** doit être installé. - -Exécutez les commandes suivantes : - -```shell -dnf install -y dnf-plugins-core -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm -dnf config-manager --set-enabled ol8_codeready_builder -``` - -Activez PHP 8.2 en utilisant les commandes suivantes : - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -Exécutez les commandes suivantes : - -```shell -dnf install dnf-plugins-core -dnf install epel-release -dnf config-manager --set-enabled crb -``` - -Activez PHP 8.2 avec la commande suivante : - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -Exécutez les commandes suivantes : - -```shell -dnf install -y dnf-plugins-core -dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms -``` - -S'il s'agit d'une instance Cloud RHEL, vous devrez exécuter la commande suivante : - -```shell -dnf config-manager --set-enabled codeready-builder-for-rhel-9-rhui-rpms -``` - -Activez PHP 8.2 avec la commande suivante : - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -Exécutez les commandes suivantes : - -```shell -dnf install dnf-plugins-core -dnf install -y http://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -dnf config-manager --set-enabled ol9_codeready_builder -``` - -Activez PHP 8.2 avec la commande suivante : - -```shell -dnf module reset php -dnf module install php:8.2 -``` - - - - -#### Installer les dépendances - -Installez les dépendances suivantes : - -```shell -apt update && apt install lsb-release ca-certificates apt-transport-https software-properties-common wget gnupg2 curl -``` - -#### Installer le dépôt Sury APT pour PHP 8.2 - -Pour installer le dépôt Sury, exécutez la commande suivante : - -```shell -echo "deb https://packages.sury.org/php/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/sury-php.list -``` - -Puis importez la clé du dépôt : - -```shell -wget -O- https://packages.sury.org/php/apt.gpg | gpg --dearmor | tee /etc/apt/trusted.gpg.d/php.gpg > /dev/null 2>&1 -``` - - - - -#### Dépôt de base données +#### Dépôt de base de données #### Dépôt Centreon -Afin d'installer les logiciels Centreon à partir des dépôts, vous devez au -préalable installer le fichier lié au dépôt. + -Exécutez la commande suivante : - - - +## Étape 2 : Installer le serveur -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo -dnf clean all --enablerepo=* -dnf update -``` +Cette section décrit comment installer un serveur distant Centreon. - - +Vous pouvez installer ce serveur avec une base de données locale au serveur, ou +avec une base de données distante sur un serveur dédié. -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -dnf clean all --enablerepo=* -dnf update -``` + + + - - +Vous pouvez maintenant passer à l'[étape suivante](#étape-3--mettre-en-place-la-configuration-tls). -```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list -``` + + + + + -Ensuite, importez la clé du dépôt : +## Étape 3 : Mettre en place la configuration TLS -```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 -apt update -``` +### Générer les certificats - - + -## Étape 2 : Installation +### Pour la base de données -Ce chapitre décrit l'installation d'un serveur Centreon Remote Server. + -Il est possible d'installer ce serveur avec une base de données locale au -serveur, ou déportée sur un serveur dédié. +### Pour l'interface web - - - +Cette section décrit comment mettre en place une connexion TLS entre le serveur distant et son interface web. -Passez maintenant à [l'étape suivante](#étape-3--configuration). + - - - - - - -## Étape 3 : Configuration +## Étape 4 : Configuration ### Nom du serveur -Si vous le souhaitez, vous pouvez changer le nom du serveur à l'aide de la commande suivante: - +Si vous souhaitez changer le nom du serveur, utilisez la commande suivante : ```shell hostnamectl set-hostname new-server-name ``` Remplacez **new-server-name** par le nom de votre choix. Exemple : - ```shell hostnamectl set-hostname remote1 ``` -### Gérer le lancement des services au démarrage +### Démarrage des services au démarrage du système -Pour activer le lancement automatique des services au démarrage, exécutez la -commande suivante sur le serveur Central : +Pour que les services démarrent automatiquement au démarrage du système, exécutez les commandes suivantes +sur le serveur distant : - + ```shell systemctl enable php-fpm httpd centreon cbd centengine gorgoned snmptrapd centreontrapd snmpd @@ -422,7 +100,7 @@ systemctl start crond ``` - + ```shell systemctl enable php-fpm httpd centreon cbd centengine gorgoned snmptrapd centreontrapd snmpd @@ -431,66 +109,40 @@ systemctl start crond ``` - + ```shell -systemctl enable php8.2-fpm apache2 centreon cbd centengine gorgoned centreontrapd snmpd snmptrapd +systemctl enable php8.4-fpm apache2 centreon cbd centengine gorgoned centreontrapd snmpd snmptrapd ``` -Puis exécutez la commande suivante (sur le serveur distant si vous utilisez une base de données locale, sinon sur le serveur de base de données déporté): +Exécutez ensuite la commande suivante (sur le serveur distant si vous utilisez une base de données locale, ou sur votre serveur de base de données dédié) : -### Sécuriser la base de données - -Il est obligatoire de sécuriser l'accès en root à la base avant d'installer Centreon. Si vous utilisez une base de données locale, exécutez la commande suivante sur le serveur central : - - - - -```shell -mariadb-secure-installation -``` - - - - -```shell -mysql_secure_installation -``` - - - - -* Répondez oui à toute question sauf à "Disallow root login remotely?". -* Définissez obligatoirement un mot de passe pour l'utilisateur **root** de la base de données. -Ce mot de passe vous sera demandé lors de l'[installation web](../web-and-post-installation.md). - -> Pour plus d'informations, consultez la [documentation officielle MariaDB](https://mariadb.com/kb/en/mysql_secure_installation/). +## Étape 5 : Installation web -## Étape 4 : Installation web - -Avant de démarrer l'installation web, démarrez le serveur Apache avec la commande suivante : +1. Démarrez le serveur Apache avec la +commande suivante : - + ```shell systemctl start httpd ``` - + ```shell systemctl start httpd ``` - + ```shell systemctl start apache2 @@ -499,23 +151,20 @@ systemctl start apache2 +2. Pour terminer l'installation, suivez la +procédure d'[installation web](../web-and-post-installation.md#installation-web). -Terminez l'installation en réalisant les -[étapes de l'installation web](../web-and-post-installation.md#installation-web). - -> Pendant l'installation web, il n'est pas nécessaire d'installer le module -> Autodiscovery. +> Pendant l'installation web, il n'est pas nécessaire d'installer le module Autodiscovery. -> A l'étape d'**Initialisation de la supervision**, seules les actions 6 à 8 -> doivent être faites. +> À l'étape **Initialisation de la supervision**, seules les actions 6 à 8 sont nécessaires. -## Étape 5 : Enregistrer le Remote Server + ## Étape 6 : Étendre les droits du SGBD local -Enfin, il est nécessaire d'ajouter des droits à l'utilisateur de base de données **centreon** pour qu'il puisse -utiliser la commande **LOAD DATA INFILE** : +Enfin, ajoutez à l'utilisateur de base de données **centreon** les droits nécessaires pour utiliser la commande +**LOAD DATA INFILE** : ```sql mysql -u root -p @@ -647,12 +295,12 @@ SET GLOBAL local_infile=1; exit ``` -## Étape 7 : Ajouter le Remote Server à la configuration +## Étape 7 : Rattacher le serveur distant au serveur central Rendez-vous au chapitre -[Ajouter un Remote Server à la configuration](../../monitoring/monitoring-servers/add-a-remote-server-to-configuration.md). +[Rattacher un serveur distant à un serveur central](../../monitoring/monitoring-servers/add-a-remote-server-to-configuration.md). ## Étape 8 : Sécuriser votre plateforme -Sécurisez votre plateforme Centreon en suivant nos +N'oubliez pas de sécuriser votre plateforme Centreon en suivant nos [recommandations](../../administration/secure-platform.md). diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx new file mode 100644 index 000000000000..793de3c29192 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx @@ -0,0 +1,67 @@ +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +Ce chapitre décrit comment monter votre plateforme Centreon de la version {props.oldCentreonVersion} à la version 26.10. + +La montée de version n'est possible que si votre OS actuel est RHEL/Oracle/AlmaLinux 9. [Les autres OS ne sont plus supportés](upgrade-matrix.mdx) : suivez une [procédure de migration](../migrate/introduction.md) pour passer à un OS supporté. Si votre plateforme Centreon utilise la HA, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. + +* Lorsque vous montez de version votre serveur central, veillez à monter également de version tous vos serveurs distants et tous vos collecteurs. +* Tous les serveurs de votre architecture doivent utiliser la même version de Centreon. +* De plus, tous les serveurs doivent utiliser la même [version du protocole BBDO](../developer/developer-broker-bbdo-switch-versions.md). + +{props.showMapLegacyWarning && ( +<> + +
Utilisateurs de la Business edition : MAP Legacy n'est plus disponible dans Centreon 26.10. Si vous utilisez toujours MAP Legacy, vous devez migrer vers MAP. Consultez la page [Fin de vie de MAP Legacy](https://docs.centreon.com/docs/24.10/graph-views/map-legacy-eol/).
+ + +)} + +{props.showVmwareWarning && ( +<> +
+

Attention : si vous utilisiez les connecteurs de supervision suivants, à partir de la version 24.10 vous devez déclarer toutes leurs configurations depuis la page Configuration > Configurations de connecteurs additionnels avant de déployer la configuration du collecteur correspondant :

+ +
+ +)} + +## Composants autres que Centreon à monter de version + +| Composant | Version dans {props.oldCentreonVersion} | Version dans 26.10 | +| --- | --- | --- | +| PHP | {props.oldPhpVersion} | 8.4 | +| Base de données |
  • {props.oldMariadbVersion}
  • {props.oldMysqlVersion}
|
  • MariaDB 11.8
  • MySQL 8.4
| + +## Prérequis + +### Réaliser une sauvegarde + +Assurez-vous d'avoir réalisé une sauvegarde complète de votre environnement pour les +serveurs suivants : + +- Serveur central +- Serveur de base de données + +### Vérifier les dépôts + +Avant de monter de version votre plateforme Centreon, assurez-vous que les dépôts de paquets suivants sont activés : + + + + +* EPEL +* BaseOS +* AppStream +* centreon +* centreon-modules, si vous utilisez Centreon Business Edition. + + + diff --git a/versioned_docs/version-26.10/installation/_database-configuration.mdx b/versioned_docs/version-26.10/installation/_database-configuration.mdx index 4929b38d9af2..faade4131d43 100644 --- a/versioned_docs/version-26.10/installation/_database-configuration.mdx +++ b/versioned_docs/version-26.10/installation/_database-configuration.mdx @@ -77,7 +77,7 @@ Please note that the following configuration is only an example for an 8 GB of R We recommend you consult your database administrator for a configuration that fits your needs. - + > ```shell > $ cat /etc/my.cnf.d/centreon.cnf @@ -87,7 +87,7 @@ We recommend you consult your database administrator for a configuration that fi > ``` - + > ```shell > $ cat /etc/my.cnf.d/centreon.cnf @@ -97,7 +97,7 @@ We recommend you consult your database administrator for a configuration that fi > ``` - + > ```shell > $ cat /etc/mysql/mariadb.conf.d/80-centreon.cnf @@ -142,7 +142,7 @@ Please note that the following configuration is only an example for an 8 GB of R We recommend you consult your database administrator for a configuration that fits your needs. - + > ```shell > $ cat /etc/my.cnf.d/centreon.cnf @@ -152,7 +152,7 @@ We recommend you consult your database administrator for a configuration that fi > ``` - + > ```shell > $ cat /etc/my.cnf.d/centreon.cnf @@ -162,7 +162,7 @@ We recommend you consult your database administrator for a configuration that fi > ``` - + > ```shell > $ cat /etc/mysql/mysql.conf.d/80-centreon.cnf diff --git a/versioned_docs/version-26.10/installation/_database-tls-conf.mdx b/versioned_docs/version-26.10/installation/_database-tls-conf.mdx index e83a60c2bc06..532283594f99 100644 --- a/versioned_docs/version-26.10/installation/_database-tls-conf.mdx +++ b/versioned_docs/version-26.10/installation/_database-tls-conf.mdx @@ -48,7 +48,7 @@ systemctl enable --now mariadb systemctl restart mariadb ``` -5. Secure the installation: +5. Secure the installation by defining a password for the database root account: ```shell mariadb-secure-installation @@ -120,7 +120,7 @@ systemctl enable --now mariadb systemctl restart mariadb ``` -5. Secure the installation: +5. Secure the installation by defining a password for the database root account: ```shell mariadb-secure-installation @@ -238,7 +238,7 @@ done -1. ... +1. Create the configuration file for the database to start in TLS. ```shell cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' @@ -346,7 +346,7 @@ SSL: Cipher in use is TLS_AES_128_GCM_SHA256 ``` -8. Set the environment variables that will be used by PHP to communicate with the database in TLS mode. +9. Set the environment variables that will be used by PHP to communicate with the database in TLS mode. ```shell for f in /etc/centreon/.env /usr/share/centreon/.env; do @@ -363,7 +363,7 @@ done -1. ... +1. Create the configuration file for the database to start in TLS. ```shell cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' @@ -471,7 +471,7 @@ SSL: Cipher in use is TLS_AES_128_GCM_SHA256 ``` -8. Set the environment variables that will be used by PHP to communicate with the database in TLS mode. +9. Set the environment variables that will be used by PHP to communicate with the database in TLS mode. ```shell for f in /etc/centreon/.env /usr/share/centreon/.env; do diff --git a/versioned_docs/version-26.10/installation/_tls-certificates.mdx b/versioned_docs/version-26.10/installation/_tls-certificates.mdx index 418517e11bd4..ff9404ecdcfb 100644 --- a/versioned_docs/version-26.10/installation/_tls-certificates.mdx +++ b/versioned_docs/version-26.10/installation/_tls-certificates.mdx @@ -9,10 +9,10 @@ Use a certificate issued by a trusted authority. Self-signed certificates may be Let's say you have the following files in **/etc/pki/centreon-tls/**: - * rootCA.pem (public) - * server.pem (server certificate) - * server-key.pem (server private key) - * CA/rootCA.\{key,pem\} (set the following permissions: root:root, mode 0400) +* rootCA.pem (public) +* server.pem (server certificate) +* server-key.pem (server private key) +{/* * CA/rootCA.\{key,pem\} (set the following permissions: root:root, mode 0400) */} 1. Install the root CA into the OS trust store of the central server's host machine: @@ -42,4 +42,4 @@ Let's say you have the following files in **/etc/pki/centreon-tls/**: -2. If you are using a remote database, also execute this procedure on the machine that will host the remote database, then copy the root CA certificate of the database machine to the central server's trust store. \ No newline at end of file +2. If you are using a remote database, also execute this procedure on the machine that will host the remote database, then copy the root CA certificate of the database machine to the central server host machine's trust store. \ No newline at end of file diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md index 5c171b219970..6c979ce9dc17 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md @@ -94,7 +94,7 @@ To install a remote server quicker, you can use a script. This will perform all 2. Go to http(s)://\/centreon (where \ is your server's IP address) and log in. Then follow the [initialization of the monitoring](../web-and-post-installation.md#initialization-of-the-monitoring) steps. - 3. Once the script has run, carry out [steps 5 to 8 of the standard installation procedure for a remote server](./using-packages.md#step-5-web-installation). +3. Once the script has run, carry out [steps 5 to 8 of the standard installation procedure for a remote server](./using-packages.md#step-5-web-installation). 4. Start using Centreon: follow our [Getting started](../../getting-started/welcome.md) guide to start monitoring your resources. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md index b4ccc984ee64..f172111203cb 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md @@ -67,7 +67,7 @@ You can now move on to the [next step](#step-3-set-up-the-tls-configuration). ### For the web interface -This section describes how to set up a TLS connection between the remote server and its web interface. +This section describes how to set up a TLS connection between the remote server and its web interface. @@ -88,7 +88,7 @@ hostnamectl set-hostname remote1 ### Service startup during system bootup To make services start automatically during system bootup, run these commands -on the central server: +on the remote server: @@ -112,7 +112,7 @@ systemctl start crond ```shell -systemctl enable php8.2-fpm apache2 centreon cbd centengine gorgoned centreontrapd snmpd snmptrapd +systemctl enable php8.4-fpm apache2 centreon cbd centengine gorgoned centreontrapd snmpd snmptrapd ``` From 1ab77a495bb2e61bddcd4990f6afb2aa25030fe0 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 22 Sep 2026 18:03:16 +0200 Subject: [PATCH 070/179] Refresh self-signed certificate procedure --- .../administration/self-signed-certificate.md | 253 +++++++++++++++++- 1 file changed, 250 insertions(+), 3 deletions(-) diff --git a/versioned_docs/version-26.10/administration/self-signed-certificate.md b/versioned_docs/version-26.10/administration/self-signed-certificate.md index bcd82483db8e..86957aa3fda7 100644 --- a/versioned_docs/version-26.10/administration/self-signed-certificate.md +++ b/versioned_docs/version-26.10/administration/self-signed-certificate.md @@ -1,13 +1,234 @@ --- id: self-signed-certificate title: Create a self-signed certificate -description: "Create a self-signed certificate with OpenSSL to enable HTTPS on your Centreon server" +description: "Create a self-signed certificate with OpenSSL" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; > Self-signed certificates are for test purposes only. You MUST NOT use them in production. +## Files you need to set up TLS connections using self-signed certificates + +This procedure allows you to create the following files: + +| File | Where to store it | Role | +|--------------|-----------------------------------|-------------------------------------------------------------------------| +| server.key | On the server you want to make secure (central/remote, database...) | Stays secret on the secure server. Used to decrypt the client's data. | +| server-key.pem | On the server you want to make secure (central/remote, database...) | The signed certificate that will be sent automatically to any client that tries to connect to the secure server. | +| rootCA.pem | On the client (browser, OS...) | Root CA self-signed certificate. This is a public file, used to validate the **server.pem** certificate the client has received. **rootCA.pem** will have to be copied to all machines that will interact with the secure machine (that has sent server-key.pem). only applies for self-signed certificates? | +| rootCA.key | Only on the machine that generates the CA, stays in a temporary folder | This file plays no role in production. It is used only to sign **rootCA.pem** when creating it. | + +## What this procedure does + +The procedure creates the files you need to set up a TLS connection, in a temporary folder. When you set up HTTPS on a server, you will need to deploy the necessary files to the correct location. Example: **/etc/pki/centreon-tls** is the default location for certificates on EL. Debian's default path is **/etc/ssl/certs**. + + + +## Step 1: Create output directories + +Set up folders to keep everything organized: one for the CA's own files, one for files meant for the web or database service. + + + + +```shell +sudo mkdir -p /out/CA +sudo mkdir -p /out/web +``` + + + + +```shell +sudo mkdir -p /out/CA +sudo mkdir -p /out/db +``` + + + + +## Step 2: Generate the root CA private key (4096-bit RSA) + +This is the secret key for your Certificate Authority. **chmod 400** restricts the file so that only its owner can read it (not even write), minimizing exposure. + +```shell +sudo openssl genrsa -out /out/CA/rootCA.key 4096 +sudo chmod 400 /out/CA/rootCA.key +``` + +## Step 3: Generate Root CA self-signed certificate (10 years) + +Now we create the CA's actual certificate — the public document that identifies your CA (name, organization, etc.) and that will later be distributed to any client/server that needs to trust certificates it signs. + +It's "self-signed" because there's no higher authority above it — the CA vouches for itself. This is normal and expected for a root CA. + +* `-x509` tells OpenSSL to output a certificate directly (rather than a signing request). +* `-days 3650` sets it to expire in ~10 years, which is standard for a root CA since it's not meant to be renewed often. +* `-subj` sets the identity fields directly on the command line: CN (Common Name) is "Test Dev CA", O (Organization) is "YourOrganization", OU (Organizational Unit) is "R&D". Replace these to fit your organization. + +```shell +sudo openssl req -x509 -new -nodes -key /out/CA/rootCA.key \ + -sha256 -days 3650 \ + -subj "/CN=Test Dev CA/O=YourOrganization /OU=R&D" \ + -out /out/CA/rootCA.pem +``` + +## Step 4: Generate leaf server private key (2048-bit RSA) + +This is the private key for the actual server (the central/remote server or the database). It's separate from the CA key — the server should never share a key with the CA. + + + + +```shell +sudo openssl genrsa -out /out/web/server-key.pem 2048 +``` + + + + +```shell +sudo openssl genrsa -out /out/db/server-key.pem 2048 +``` + + + + +## Step 5: Create OpenSSL extension config for SANs + +Modern browsers and clients require a certificate to list all the hostnames/IPs it's valid for — this is called the Subject Alternative Name (SAN) list. A single CN is no longer trusted alone. This step writes a small config file describing: + +* `basicConstraints = CA:FALSE`: this certificate is not allowed to sign other certificates (only the root CA can). +* `keyUsage / extendedKeyUsage`: restricts the certificate to its intended purpose, which is authenticating a TLS server. +* `subjectAltName`: the actual list of names/IPs the certificate should be valid for. Here: web, localhost, db, and IP 127.0.0.1. Edit this list to match the actual hostnames your server will be reached by. + +```shell +sudo tee /out/cert.ext > /dev/null < + + +```shell +openssl req -new -key /out/web/server-key.pem -out /out/web/server.csr \ + -subj "/CN=web/O=Centreon" +``` + + + + +```shell +openssl req -new -key /out/db/server-key.pem -out /out/db/server.csr \ + -subj "/CN=web/O=Centreon" +``` + + + + +## Step 7: Sign leaf cert with Root CA (397 days validity) + +This is the step that actually produces the usable server certificate: the CA (its cert + private key from Steps 2–3) signs the CSR from Step 6, applying the extensions/SANs defined in Step 5. + +* `-days 397`: 397 days is the current maximum lifetime accepted by major browsers (Apple/Google/Mozilla) for TLS server certificates. Going longer risks clients rejecting the certificate. +* `-CAcreateserial`: creates a serial number tracking file (rootCA.srl) the first time it runs, and increments it on future signings, so every certificate issued by this CA gets a unique serial number. + + + + + + +```shell +sudo openssl x509 -req -in /out/server.csr \ + -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ + -CAserial /out/CA/rootCA.srl -CAcreateserial \ + -out /out/web/server.pem -days 397 -sha256 \ + -extfile /out/web/cert.ext -extensions v3_req +``` + + + + +```shell +sudo openssl x509 -req -in /out/server.csr \ + -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ + -CAserial /out/CA/rootCA.srl -CAcreateserial \ + -out /out/db/server.pem -days 397 -sha256 \ + -extfile /out/db/cert.ext -extensions v3_req +``` + + + + +## Step 8: Copy Root CA and set permissions -> quel est l'intérêt? + +Make a convenient copy of the root CA certificate alongside the server files (this is the file you'd distribute to clients so they trust your CA — note it's the public certificate, rootCA.pem, never the .key file). + +Permissions here follow the principle of least privilege: + +* `0644` (readable by everyone, writable only by owner) for public certificates — they contain no secrets. +* `0640` (readable by owner and group, not others) for the server's private key, since it's sensitive but likely needs to be read by a service running under a specific group. + +```shell +sudo cp /out/CA/rootCA.pem /out/rootCA.pem +sudo chmod 0644 /out/rootCA.pem /out/server.pem +sudo chmod 0640 /out/server-key.pem +``` + +## Step 9: Create MariaDB-specific copies -> pas logique? + + + +If the database runs as a separate service/container (e.g., MariaDB), it typically needs its own copy of the certificate and key, owned by the user/group it runs as (here 1001:1001 — adjust to match your actual DB container/user UID/GID). + +Note the key permission here is tighter (0600, owner-only) than the general server key in Step 8, and ownership is explicitly changed with chown so the database process can read it. + +```shell +sudo cp /out/server.pem /out/db/server.pem +sudo cp /out/server-key.pem /out/db/server-key.pem +sudo chmod 0644 /out/db/server.pem +sudo chmod 0600 /out/db/server-key.pem +sudo chown 1001:1001 /out/db/server.pem /out/db/server-key.pem +``` + +## Step 10: Generate environment manifest + +Finally, write a small .env-style file listing where each certificate/key lives, so other tooling (deployment scripts, docker-compose, systemd units, etc.) can source this file instead of hardcoding paths everywhere. + +```shell +sudo tee /out/certs.env > /dev/null < - + < + > Open the file **/etc/pki/tls/openssl.cnf**. The goal here is to edit this file in order to inform the various IPs and FQDNs for the server. @@ -140,3 +361,29 @@ Let's assume that you have a Centreon server with a **centreon7.localdomain** FQ 7. You must then retrieve the x509 certificate file (**ca_demo.crt**) and import it into your browser's certificate manager. Now that you have your self-signed certificate, you can perform the following procedure to activate HTTPS mode on your Apache server. + --> + + +## Détails des chemins + +| Machine (Service) | Fichier | Chemin standard - RHEL (AlmaLinux) | Chemin standard - Debian (Ubuntu) | +|:---|:---|:---|:---| +| central / remote (Apache / Nginx) | rootCA | /etc/pki/ca-trust/source/anchors/rootCA.pem | /usr/local/share/ca-certificates/rootCA.crt * | +| | server | /etc/pki/tls/certs/centreon-server.pem | /etc/ssl/certs/centreon-server.pem | +| | key | /etc/pki/tls/private/centreon-server.key | /etc/ssl/private/centreon-server.key | +| central / remote (gorgone - Perl) | rootCA | /etc/pki/centreon-tls/rootCA.pem | /etc/pki/centreon-tls/rootCA.pem | +| | server | /etc/pki/centreon-tls/server.pem | /etc/pki/centreon-tls/server.pem | +| | key | /etc/pki/centreon-tls/server-key.pem | /etc/pki/centreon-tls/server-key.pem | +| poller (Centreon Broker) | rootCA | /etc/centreon-broker/ssl/rootCA.pem (ou /etc/pki/tls/certs/ca-bundle.crt) | /etc/centreon-broker/ssl/rootCA.pem (ou /etc/ssl/certs/ca-certificates.crt) | +| central-db / map-db / mbi-db (MariaDB/MySQL) | rootCA | /etc/my.cnf.d/ssl/rootCA.pem | /etc/mysql/ssl/rootCA.pem | +| | server | /etc/my.cnf.d/ssl/server.pem | /etc/mysql/ssl/server.pem | +| | key | /etc/my.cnf.d/ssl/server.key | /etc/mysql/ssl/server.key | +| map / mbi (Services Java) | rootCA | Intégré dans : /etc/pki/java/cacerts | Intégré dans : /etc/ssl/certs/java/cacerts | +| | Keystore | /etc/centreon-map/keystore.p12 (Format PKCS12) | /var/lib/centreon-map/keystore.p12 (ou /etc/) | \ No newline at end of file From 655b0c1696cec155ef96320bca3fa75a3b14d1ca Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 23 Sep 2026 10:34:40 +0200 Subject: [PATCH 071/179] Fix syntax error --- versioned_docs/version-26.10/upgrade/upgrade-mysql.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/versioned_docs/version-26.10/upgrade/upgrade-mysql.md b/versioned_docs/version-26.10/upgrade/upgrade-mysql.md index 334f66b3c464..83469830c3c1 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-mysql.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-mysql.md @@ -20,8 +20,8 @@ Do not upgrade your version of Centreon and your version of MySQL at the same ti | Centreon | MySQL | |----------|---------| | 26.10 | 8.4 | -| 25.10 | 8.4 (recommended)
8.0 until its end of support (April 2026) | -| 24.10 | 8.4 (recommended)
8.0 until its end of support (April 2026) | +| 25.10 | 8.4 (recommended)
8.0 until its end of support (April 2026) | +| 24.10 | 8.4 (recommended)
8.0 until its end of support (April 2026) | | 24.04 | 8.0 | | 23.10 | not supported | | 23.04 | not supported | From 8617d588349c2f252bda247a0a2ce85b67e5f8a0 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 23 Sep 2026 10:44:39 +0200 Subject: [PATCH 072/179] Fix syntax and anchors --- .../version-26.10/upgrade/upgrade-mysql.md | 6 +++--- versioned_docs/version-26.10/upgrade/upgrade-mysql.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mysql.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mysql.md index f886ebb28c2e..b8c316cf73f6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mysql.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mysql.md @@ -6,7 +6,7 @@ description: "Mettre à jour MySQL vers une version compatible avec Centreon 25. import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Si vous utilisiez Centreon 24.04 ou 24.10 avec MySQL, sachez que le support de MySQL 8.0 prendra fin en avril 2026. Assurez-vous que votre Centreon utilise toujours [une version supportée de MySQL](#versions-de-mysql-compatibles-avec-centreon-2610). +Si vous utilisiez Centreon 24.04 ou 24.10 avec MySQL, sachez que le support de MySQL 8.0 prendra fin en avril 2026. Assurez-vous que votre Centreon utilise toujours [une version supportée de MySQL](#version-de-mysql-pour-chaque-version-de-centreon). Vous pouvez potentiellement avoir plusieurs bases MySQL dans votre architecture. Le serveur central a une base, chaque serveur distant a une base, et les modules MBI et MAP ont chacun une base dédiée. Dans une architecture, toutes les bases doivent avoir la même version de MySQL. @@ -19,8 +19,8 @@ Ne mettez pas à jour votre version de Centreon et votre version de MySQL en mê | Centreon | MySQL | |----------|---------| | 26.10 | 8.4 | -| 25.10 | 8.4 (recommandé)
8.0 jusqu'à sa fin de support (avril 2026) | -| 24.10 | 8.4 (recommandé)
8.0 jusqu'à sa fin de support (avril 2026) | +| 25.10 | 8.4 (recommandé)
8.0 jusqu'à sa fin de support (avril 2026) | +| 24.10 | 8.4 (recommandé)
8.0 jusqu'à sa fin de support (avril 2026) | | 24.04 | 8.0 | | 23.10 | non supporté | | 23.04 | non supporté | diff --git a/versioned_docs/version-26.10/upgrade/upgrade-mysql.md b/versioned_docs/version-26.10/upgrade/upgrade-mysql.md index 83469830c3c1..533fc5af48df 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-mysql.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-mysql.md @@ -6,7 +6,7 @@ description: "Upgrade MySQL to a version supported by Centreon 25.10" import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -If you were using Centreon 24.04 or 24.10 with MySQL, be aware that support for MySQL 8.0 ended at the end of April 2026. Make sure your Centreon always uses [a supported version of MySQL](#versions-of-mysql-compatible-with-centreon-2610). +If you were using Centreon 24.04 or 24.10 with MySQL, be aware that support for MySQL 8.0 ended at the end of April 2026. Make sure your Centreon always uses [a supported version of MySQL](#version-of-mysql-for-each-version-of-centreon). You may have several MySQL databases in your architecture. The central server has a database, each remote server has a database, and the MBI and MAP modules each have a dedicated database. Within your architecture, all databases must have the same version of MySQL. From e8632d535c8b3805308caf929d0aa7c7f9bd7999 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 23 Sep 2026 10:59:07 +0200 Subject: [PATCH 073/179] Add FR self-signed certificates file --- .../administration/self-signed-certificate.md | 145 ++++++++++++++++++ 1 file changed, 145 insertions(+) create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md new file mode 100644 index 000000000000..1e0f339ee13d --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md @@ -0,0 +1,145 @@ +--- +id: self-signed-certificate +title: Créer un certificat autosigné +description: "Créer un certificat autosigné avec OpenSSL, à des fins de test" +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +> Self-signed certificates are for test purposes only. You MUST NOT use them in production. + + + \ No newline at end of file From 3687b0b2a283388a424cdc51a56589a873360131 Mon Sep 17 00:00:00 2001 From: smau Date: Wed, 23 Sep 2026 11:46:57 +0200 Subject: [PATCH 074/179] Revert "update" This reverts commit 85df8ac3593b4eb2360848d961911b8665df9653. --- .../graph-views/map-web-install.md | 27 ++++++++++++++++--- 1 file changed, 23 insertions(+), 4 deletions(-) diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index 93859a499edb..1f7d176fa622 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -8,7 +8,7 @@ import TabItem from '@theme/TabItem'; This topic describes how to install Centreon MAP. We recommend that you install MAP on a dedicated server. However, if you do not have large volumes of data, you can install it on the central server. -> If you plan to use MAP in HTTPS, please note that securing the HTTPS protocol requires configuration on both the Centreon platform and the MAP server. It is therefore easier to plan for this before beginning the installation. See the [Secure MAP in HTTPS](#secure-map-in-https) page for the full procedure. +> If you plan to use MAP in HTTPS, please note that securing the HTTPS protocol requires configuration on both the Centreon platform and the MAP server. It is therefore easier to plan for this before beginning the installation. See the [Secure MAP in HTTPS](#secure-map-in-https) section for the full procedure. ## License @@ -33,7 +33,7 @@ See the [software requirements](../installation/prerequisites.md#characteristics #### Hardware - + | Element | Value | @@ -131,7 +131,26 @@ This is how your MAP server should be partitioned: | vg_data | | Free space (unallocated) | 2 GB | - + + +| Element | Value | +| ----------------------------| --------- | +| CPU | 8 vCPU | +| RAM | 18 GB | + +This is how your MAP server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +|-| ----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 2 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 8 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/mysql | database | 5 GB | +| vg_data | | Free space (unallocated) | 2 GB | + + + For very large amounts of data, contact your sales representative. @@ -439,7 +458,7 @@ apt update && apt install mariadb-server -Then enable and restart mariadb. +Then enable and restart mariadb ```shell systemctl enable mariadb From 876c636ed106b200e61499138caf656cb2b9697c Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 23 Sep 2026 11:49:15 +0200 Subject: [PATCH 075/179] Fix tabs --- .../version-26.10/installation/_database-configuration.mdx | 4 ++-- .../installation-of-a-central-server/using-packages.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx index 85125bbfd35d..18a4988fd171 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx @@ -86,7 +86,7 @@ Nous vous invitons à vous rapprocher de votre administrateur de base de donnée > ``` - + > ```shell > $ cat /etc/my.cnf.d/centreon.cnf @@ -150,7 +150,7 @@ Nous vous invitons à vous rapprocher de votre administrateur de base de donnée > ``` - + > ```shell > $ cat /etc/my.cnf.d/centreon.cnf diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index e8afb68eacc0..5280b2443532 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -18,7 +18,7 @@ import DependenciesRepository from '../_dependencies-repository.mdx'; Vous devez exécuter la procédure d'installation en tant qu'utilisateur privilégié. -> Lorsque vous exécutez une commande, vérifiez les messages obtenus. En cas de message d'erreur, arrêtez la procédure et corrigez le problème. +> Lorsque vous exécutez une commande, vérifiez ce qu'elle affiche. En cas de message d'erreur, arrêtez la procédure et corrigez le problème. Nous vous recommandons de chiffrer les communications du serveur web comme celles de la base de données, même si ces étapes ne sont pas nécessaires au fonctionnement de Centreon. La procédure ci-dessous met en place ce chiffrement. Dans certains cas (par exemple pour réaliser des tests rapides), vous pouvez préférer une installation non sécurisée : il vous suffit alors d'ignorer l'[étape 3 : Mettre en place la configuration TLS](#étape-3--mettre-en-place-la-configuration-tls). From 4f13439c783a5c8c7d7d296a55f3679a72948e0b Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 23 Sep 2026 13:13:02 +0200 Subject: [PATCH 076/179] Fix anchors --- .../version-26.10/installation/web-and-post-installation.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md index 22ef48126121..fa61e7df95fe 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md @@ -55,8 +55,8 @@ Fournissez les informations de connexion à l'instance de base de données. - **Database Host Address** : si vous utilisez une base de données locale, laissez ce champ vide (la valeur par défaut étant **localhost**). Sinon, renseignez l'adresse IP de votre base de données déportée. - **Root user/password** : ce compte sera utilisé pour installer les bases de données. - - S'il s'agit du compte par défaut (**root**), le mot de passe root de la base de données est [celui que vous avez défini](installation-of-a-central-server/using-packages.md#sécuriser-la-base-de-données) lorsque vous avez exécuté `mysql_secure_installation`. - - Si vous avez défini un utilisateur dédié avec des privilèges root sur toutes les bases, (par exemple pendant [l'installation d'une base de donnée déportée](../installation/installation-of-a-central-server/using-packages.md#étape-2--installation)), utilisez celui-ci. Cet utilisateur pourra être supprimé une fois l'installation web terminée. + - S'il s'agit du compte par défaut (**root**), le mot de passe root de la base de données est [celui que vous avez défini](./installation-of-a-central-server/using-packages.md#étape-2--installer-le-serveur-central-et-la-base-de-données) lorsque vous avez exécuté `mysql_secure_installation`/`mariadb_secure_installation`. + - Si vous avez défini un utilisateur dédié avec des privilèges root sur toutes les bases, (par exemple pendant [l'installation d'une base de donnée déportée](../installation/installation-of-a-central-server/using-packages.md#étape-2--installer-le-serveur-central-et-la-base-de-données)), utilisez celui-ci. Cet utilisateur pourra être supprimé une fois l'installation web terminée. - **Database user name/password**: les identifiants du compte qui sera utilisé pour interagir avec les bases de données Centreon. Le compte sera créé pendant l'installation de la base. From b4065a7a267e8c9186e328f85eaf202b571f87f2 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 23 Sep 2026 14:52:45 +0200 Subject: [PATCH 077/179] MON-210153 Remove obsolete migration topics --- ...developer-gorgone-migrate-from-centcore.md | 102 ------- .../version-26.10/migrate/migrate-from-3-4.md | 260 ------------------ .../migrate/nagios-to-centreon.md | 118 -------- .../poller-display-to-remote-server.md | 191 ------------- ...developer-gorgone-migrate-from-centcore.md | 100 ------- .../version-26.10/migrate/migrate-from-3-4.md | 252 ----------------- .../migrate/nagios-to-centreon.md | 117 -------- .../poller-display-to-remote-server.md | 184 ------------- .../version-26.10-sidebars.json | 16 -- 9 files changed, 1340 deletions(-) delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-gorgone-migrate-from-centcore.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-3-4.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/nagios-to-centreon.md delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/poller-display-to-remote-server.md delete mode 100644 versioned_docs/version-26.10/developer/developer-gorgone-migrate-from-centcore.md delete mode 100644 versioned_docs/version-26.10/migrate/migrate-from-3-4.md delete mode 100644 versioned_docs/version-26.10/migrate/nagios-to-centreon.md delete mode 100644 versioned_docs/version-26.10/migrate/poller-display-to-remote-server.md diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-gorgone-migrate-from-centcore.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-gorgone-migrate-from-centcore.md deleted file mode 100644 index a9b4330d5c76..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-gorgone-migrate-from-centcore.md +++ /dev/null @@ -1,102 +0,0 @@ ---- -id: developer-gorgone-migrate-from-centcore -title : Migrer depuis Centreon Centcore -description: "Procédure de migration de Centreon Centcore vers Centreon Gorgone" ---- - -Cette procédure décrit comment migrer de Centreon Centcore vers Centreon Gorgone. - -> Gorgone remplace Centcore depuis la version Centreon 20.04. - -Vous devez créer un fichier de configuration basé sur **/etc/centreon/conf.pm**. - -- Si vous utilisez des paquets, exécutez la commande suivante : - -```shell -$ perl /usr/bin/gorgone_config_init.pl -2019-09-30 11:00:00 - INFO - file '/etc/centreon-gorgone/config.yaml' created success -``` - -- Si vous utilisez des sources, exécutez la commande suivante : - -```shell -$ perl ./contrib/gorgone_config_init.pl -2019-09-30 11:00:00 - INFO - file '/etc/centreon-gorgone/config.yaml' created success -``` -> Vous devez adapter les sections en fonction de votre propre base de données initiale, de votre configuration et de votre réseau. - -Le fichier de configuration suivant sera créé : **/etc/centreon-gorgone/config.yaml** - -```shell -name: config.yaml -description: Configuration init by gorgone_config_init -configuration: - centreon: - database: - db_configuration: - dsn: "mysql:host=localhost;port=3306;dbname=centreon" - username: "centreon" - password: "centreon" - db_realtime: - dsn: "mysql:host=localhost;port=3306;dbname=centreon_storage" - username: "centreon" - password: "centreon" - gorgone: - gorgonecore: - privkey: "/var/lib/centreon-gorgone/.keys/rsakey.priv.pem" - pubkey: "/var/lib/centreon-gorgone/.keys/rsakey.pub.pem" - modules: - - name: httpserver - package: gorgone::modules::core::httpserver::hooks - enable: false - address: 0.0.0.0 - port: 8085 - ssl: false - auth: - enabled: false - allowed_hosts: - enabled: true - subnets: - - 127.0.0.1/32 - - - name: action - package: gorgone::modules::core::action::hooks - enable: true - - - name: cron - package: gorgone::modules::core::cron::hooks - enable: false - cron: !include cron.d/*.yaml - - - name: proxy - package: gorgone::modules::core::proxy::hooks - enable: true - - - name: legacycmd - package: gorgone::modules::centreon::legacycmd::hooks - enable: true - cmd_file: "/var/lib/centreon/centcore.cmd" - cache_dir: "/var/cache/centreon/" - cache_dir_trap: "/etc/snmp/centreon_traps/" - remote_dir: "/var/lib/centreon/remote-data/" - - - name: engine - package: "gorgone::modules::centreon::engine::hooks" - enable: true - command_file: "/var/lib/centreon-engine/rw/centengine.cmd" - - - name: pollers - package: gorgone::modules::centreon::pollers::hooks - enable: true - - - name: broker - package: "gorgone::modules::centreon::broker::hooks" - enable: true - cache_dir: "/var/cache/centreon//broker-stats/" - cron: - - id: broker_stats - timespec: "*/2 * * * *" - action: BROKERSTATS - parameters: - timeout: 10 -``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-3-4.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-3-4.md deleted file mode 100644 index 03a6be73d380..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-3-4.md +++ /dev/null @@ -1,260 +0,0 @@ ---- -id: migrate-from-3-4 -title: Migration depuis une plateforme Centreon 3.4 -description: "Migrer les données et la configuration depuis une plateforme Centreon 3.4" ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -## Prérequis - -Cette procédure ne s'applique que pour une plate-forme **Centreon 3.4**, -installée sur une distribution GNU/Linux 64 bits -et disposant des prérequis suivants : - -| Composants | Version | -| --------------- | ------- | -| Centreon Web | 2.8.x | -| Centreon Broker | 3.0.x | -| Centreon Engine | 1.8.x | - -Avant toute chose, effectuez une sauvegarde de l’ensemble des serveurs de votre plateforme : - -- Serveur Centreon central, -- Serveur de gestion de base de données. - -Si vous utilisez un fournisseur Open Ticket avec des configurations personnalisées, [sauvegardez-les avant de mettre à jour Centreon](../alerts-notifications/ticketing-install.md#sauvegarder-votre-configuration-personnalisée-de-fournisseur-openticket). - -## Migration - -Tous les serveurs de votre architecture (serveur central, serveurs distants et collecteurs) doivent avoir la même version majeure de Centreon. Il est également recommandé d'avoir la même version mineure. - -> En cas de migration d'une plate-forme disposant du système de redondance -> Centreon, il est nécessaire de contacter votre -> [support Centreon](https://support.centreon.com). - -> En cas de migration d'une plate-forme disposant du module **Centreon Poller -> Display 1.6.x**, référez-vous à la -> [procédure de migration](poller-display-to-remote-server.md). - -### Installation du nouveau serveur central - -Réalisez les actions suivantes : - -1. Installez un nouveau serveur Centreon à partir des [paquets](../installation/installation-of-a-central-server/using-packages.md) -jusqu'à terminer le processus d'installation en vous connectant à l'interface -web. - -2. Réalisez les mises à jour logicielle et système : - - - - -```shell -dnf update -``` - - - - -```shell -dnf update -``` - - - - -```shell -apt update -``` - - - - -> Il est préférable de saisir le même mot de passe pour l'utilisateur 'centreon' -> lors du processus d'installation web. - -### Synchronisation des données - -Connectez-vous à votre ancien serveur Centreon et synchronisez les répertoires -suivants : - -```shell -rsync -avz /etc/centreon root@\:/etc -rsync -avz /etc/centreon-broker root@\:/etc -rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine -rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib -rsync -avz /var/spool/centreon/.ssh root@\:/var/spool/centreon -rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img -``` - -> Remplacez **\** par l'adresse IP de votre nouveau serveur -Centreon. - -### Récupération des bases de données - -1. Faire un dump des bases de données sources : - - ```shell - mysqldump -u root -p centreon > /tmp/centreon.sql - mysqldump -u root -p centreon_storage > /tmp/centreon_storage.sql - ``` - -2. Arreter le serveur MariaDB source : - - ```shell - service mysqld stop - ``` - -3. Transférer les exports vers le nouveau serveur de base de données Centreon -26.10 : - - ```shell - rsync -avz /tmp/centreon.sql root@\:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ - ``` - -4. Sur le serveur de base de données Centreon 26.10, supprimer les bases de -données vierges et les recréer : - - ```shell - mysql -u root -p - ``` - - ```SQL - DROP DATABASE centreon; - DROP DATABASE centreon_storage; - CREATE DATABASE centreon; - CREATE DATABASE centreon_storage; - ``` - -5. Importer les dumps : - - ```shell - mysql -u root centreon -p -p - ``` - - Exemple : si votre utilisateur_admin_bdd est `root`, entrez: - - ``` - mysql_upgrade -u root -p - ``` - -7. Démarrer le processus mariadb sur le nouveau serveur : - - ```shell - systemctl start mariadb - ``` - -> Remplacez **\** par l'adresse IP de votre nouveau serveur -Centreon. - -### Synchronisation des plugins - -La synchronisation des sondes de supervision (plugins) est plus délicate et -dépend de votre installation. Les principaux répertoires à synchroniser sont : - -1. /usr/lib/nagios/plugins/ -2. /usr/lib/centreon/plugins/ - -> Il est important d'installer les dépendances nécessaires au fonctionnement des -> sondes de supervision. - -> Si vous avez des Pollers en Centreon Engine 1.8.1 que vous comptez migrer plus -> tard en 26.10, attention au dossier des plugins Nagios. La macro de -> ressource $USER1$ de Centreon 26.10 pointe sur /usr/lib64/nagios/plugins -> -> A exécuter sur vos collecteurs en Centreon Engine 1.8.1 : -> -> ```shell -> mv /usr/lib64/nagios/plugins/* /usr/lib/nagios/plugins/ -> rmdir /usr/lib64/nagios/plugins/ -> ln -s -t /usr/lib64/nagios/ /usr/lib/nagios/plugins/ -> ``` -> -> De cette façon un lien symbolique est créé : -> -> ```shell -> $ ls -alt /usr/lib64/nagios/ -> lrwxrwxrwx 1 root root 24 1 nov. 17:59 plugins -> /usr/lib/nagios/plugins/ -> -rwxr-xr-x 1 root root 1711288 6 avril 2018 cbmod.so -> ``` - -Vous pouvez générer les configurations depuis Centreon 26.10 -indifféremment vers un collecteur en 26.10 ou 1.8.1. - -### Montée de version de la solution Centreon - -Forcez la montée de version du nouveau serveur en déplacant le contenu du répertoire -**/var/lib/centreon/installs/install-26.10.0-YYYYMMDD\_HHMMSS** dans le -répertoire **/usr/share/centreon/www/install** : - -```shell -cd /var/lib/centreon/installs/ -mv install-26.10.0-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ -``` - -> Si vous utilisez la même adresse IP ou le même nom DNS entre l'ancien serveur -> web Centreon et le nouveau, videz complètement le cache de votre navigateur pour -> éviter des problemes de scripts JS. - -Se connecter à l'URL `http:///centreon` et suivre les étapes -de mise à jour. - -> Si vous avez modifié le mot de passe de l'utilisateur 'centreon' lors de -> l'installation de votre nouveau serveur Centreon pour accéder aux bases de -> données, il sera nécessaire de réaliser les actions suivantes sur le nouveau -> serveur Centreon : -> -> 1. Modifiez le fichier /etc/centreon/centreon.conf.php, -> 2. Modifiez le fichier /etc/centreon/conf.pm, -> 3. Éditer la configuration du Centreon Broker central, via l'interface web -> Centreon et modifier le mot de passe pour les deux output broker **Perfdata -> generator** et **Broker SQL database**, -> 4. Modifiez le fichier /etc/centreon/config.d/10-database.yaml. - -Si l'adresse IP de votre serveur Centreon a changé, éditez la configuration de -l'ensemble des modules broker de vos collecteurs et modifiez l'adresse IP de -connexion au serveur Centreon central (output IPv4). Consultez le chapitre -[Configuration -avancée](../monitoring/monitoring-servers/advanced-configuration.md#tcp-outputs) -pour plus d'information. - -Les informations de connexion de l'utilisateur **centreon-gorgone** nouvellement créé doivent être les mêmes que celles de l'utilisateur **centreon-gorgone** sur l'ancien serveur. Éditez le fichier `etc/centreon-gorgone/config.d/31-centreon-api.yaml` et entrez les information de connexion de l'ancien utilisateur. Exemple : - - ```shell - gorgone: - tpapi: - - name: centreonv2 - base_url: "http://127.0.0.1/centreon/api/latest/" - username: "@GORGONE_USER@" - password: "@GORGONE_PASSWORD@" - - name: clapi - username: "@GORGONE_USER@" - password: "@GORGONE_PASSWORD@" - ``` - -Puis [générez](../monitoring/monitoring-servers/deploying-a-configuration.md) -la configuration de l'ensemble de la plateforme et exportez là. - -### Mise à jour des modules - -Référez-vous à la documentation des modules installés afin de connaître leur -compatibilité avec Centreon 26.10, et pour mettre à jour ces derniers. - -### Migrer vos autres serveurs - -Assurez-vous que tous les serveurs de votre architecture (serveur central, serveurs distants et collecteurs) ont la même version majeure de Centreon. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/nagios-to-centreon.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/nagios-to-centreon.md deleted file mode 100644 index 814db3dc6ee3..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/nagios-to-centreon.md +++ /dev/null @@ -1,118 +0,0 @@ ---- -id: nagios-to-centreon -title: Nagios Reader vers Centreon CLAPI -description: "Convertir des fichiers de configuration Nagios en commandes CLAPI Centreon" ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - - -**Nagios Reader to Centreon CLAPI** est un projet libre et open source qui -permet d'analyser une configuration Nagios contenue dans les fichiers CFG et de -transformer celle-ci en commandes compatibles Centreon CALPI afin de pouvoir -importer les objets dans l'interface Centreon web. - -## Prérequis - -Avant toute chose vous devez avoir une plate-forme Centreon installée et prête à -l'emploi. Se référer à la documentation -[d'installation de Centreon](../installation/installation-of-a-central-server/using-packages.md). - -Avant toute chose, effectuez une sauvegarde de l’ensemble des serveurs de votre plateforme : - -- Serveur Centreon central, -- Serveur de gestion de base de données. - -Si vous utilisez un fournisseur Open Ticket avec des configurations personnalisées, [sauvegardez-les avant de mettre à jour Centreon](../alerts-notifications/ticketing-install.md#sauvegarder-votre-configuration-personnalisée-de-fournisseur-openticket). - -## Installation - -Le script nécessite le module Perl-Nagios-Object pour lire les fichiers CFG. -Pour installer ce dernier, exécutez les commandes suivantes sur votre serveur -Nagios(R) : - - - - -```shell -dnf install perl-Module-Build -``` - - - - -```shell -dnf install perl-Module-Build -``` - - - - -```shell -apt-get install libmodule-build-perl -``` - - - - -```shell -cd /tmp -wget http://search.cpan.org/CPAN/authors/id/D/DU/DUNCS/Nagios-Object-0.21.20.tar.gz -tar xzf Nagios-Object-0.21.20.tar.gz -cd Nagios-Object-0.21.20 -perl Build.PL -./Build -./Build test -./Build install -``` - -Puis télécharger le script depuis GitHub sur votre serveur Nagios(R) : - -```shell -cd /tmp -git clone https://github.com/centreon/nagiosToCentreon.git -cd nagiosToCentreon -``` - -## Utilisation - -Sur une nouvelle installation de Centreon, le collecteur par défaut est appelé -"Central". Si le nom de ce dernier est différent, vous devez modifier le script -pour modifier le nom par défaut à la ligne 65 : - -```perl -my $default_poller = "Central"; -``` - -Pour afficher l'aide, exécutez la commande : - -```shell -$ perl nagios_reader_to_centreon_clapi.pl --help -###################################################### -# Copyright (c) 2005-2015 Centreon # -# Bugs to http://github.com/nagiosToCentreon # -###################################################### - -Usage: nagios_reader_to_centreon_clapi.pl - -V (--version) Show script version - -h (--help) Usage help - -C (--config) Path to nagios.cfg file -``` - -Pour exécuter le script lancer la commande : - -```shell -perl nagios_reader_to_centreon_clapi.pl --config /usr/local/nagios/etc/ > /tmp/centreon_clapi_import_commands.txt -``` - -Exportez le fichier **/tmp/centreon\_clapi\_import\_commands.txt** sur votre -serveur Centreon. - -Enfin exécutez la commande suivante pour importer les objets dans Centreon web : - -```shell -/usr/share/centreon/bin/centreon -u admin -p -i /tmp/centreon_clapi_import_commands.txt -``` - -> Remplacez **``** par le mot de passe de l'utilisateur **admin** de -> Centreon web. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/poller-display-to-remote-server.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/poller-display-to-remote-server.md deleted file mode 100644 index 9bfbb92da103..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/poller-display-to-remote-server.md +++ /dev/null @@ -1,191 +0,0 @@ ---- -id: poller-display-to-remote-server -title: Migration d'une plate-forme avec Poller Display -description: "Migrer une plateforme utilisant le module obsolète Poller Display" ---- - -## Migrer le serveur Centreon Central - -Si le module **centreon-poller-display-central-1.6.x** est installé : - -1. Rendez-vous dans le menu **Administration > Extensions > Modules** et -désinstallez le module **centreon-poller-display-central** - -2. Supprimez le paquet associé : - - ```shell - yum remove centreon-poller-display-central - ``` - -Puis suivez la [procédure de migration](../migrate/migrate-from-3-4.md) d'un serveur Centreon -Central vers 26.10. - -> Si vous possédez des modules Centreon EMS, il est nécessaire de mettre à jour -> ces dépôts. Contactez votre support Centreon pour obtenir ces derniers. Demandez -> également les nouvelles licences associées. - -## Migrer un Poller avec Poller Display vers Remote Server - -1. Rendez-vous dans le menu **Administration > Extensions > Modules** et -supprimez le module **Centreon Poller Display**. - -2. Si vous avez installé le module à partir du paquet RPM, supprimez le paquet -en exécutant la commande suivante : - - ```shell - yum remove centreon-poller-display - ``` - -Référez vous à [la procédure de migration](../migrate/migrate-from-3-4.md). - - > Si vous possédez des modules Centreon EMS, il est nécessaire de mettre à jour - > ces dépôts. Contactez votre support Centreon pour obtenir ces derniers. - -4. Rendez-vous dans le menu **Administration > Extensions > Modules** et -installez le module **centreon-license-manager**. - -5. Enregistrer le Remote Server - -Pour l'enregistrer sur le serveur Centreon Central, exécutez la commande suivante : - -``` shell -/usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n -``` - -Exemple: - -``` shell -/usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 -``` - -> Remplacer **\** par l'adresse IP du serveur Centreon Central vue par votre collecteur. - -> Le compte **\** doit avoir accès à l'API de configuration. Vous pouvez utiliser le compte **admin**. - -> Vous pouvez changer le port et la méthode HTTP, le format de l'option **-h** est le suivant : -> HTTPS://\:PORT - -Suivre ensuite les instructions - -1. Saisir le mot de passe : - - ``` shell - 192.168.0.1: please enter your password - ``` - -2. Sélectionner l'adresse IP si plusieurs interfaces réseau existent: - - ```shell - Which IP do you want to use as CURRENT NODE IP ? - 1) 192.168.0.2 - 2) 192.168.0.3 - 1 - ``` - -3. Valider les informations: - - ``` shell - Summary of the informations that will be send: - - Api Connection: - username: admin - password: ****** - target server: 192.168.0.1 - - Pending Registration Server: - name: remote-1 - type: remote - address: 192.168.0.2 - - Do you want to register this server with those informations ? (y/n)y - ``` - -4. Ajouter les informations nécessaires pour permettre de futures communications entre votre Remote Server et son Central - - ```shell - : Please enter your username: - admin - : Please enter your password: - - : Protocol [http]: - : Port [80]: - : centreon root folder [centreon]: - ``` - -5. Définir les accès au proxy du serveur Centreon du Central : - - ```shell - Are you using a proxy ? (y/n) - y - enter your proxy Host: - myproxy.example.com - enter your proxy Port [3128]: - Are you using a username/password ? (y/n) - y - enter your username: - my_proxy_username - enter your password: - - ``` - -Vous recevrez la validation du serveur Centreon Central : - -``` shell -2020-10-16T17:19:37+02:00 [INFO]: The CURRENT NODE 'remote: 'remote-1@192.168.0.2' has been converted and registered successfully. -``` - -### Principaux messages d'erreur - -``` shell -2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials -``` - -> Vos informations d'identification sont incorrectes pour le compte **\**. - -``` shell -2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. -``` - -> L'utilisateur **\** n'a pas accès à l'API de configuration. - -``` shell -Failed connect to 192.168.0.1:444; Connection refused -``` - -> Impossible d'accéder à l'API. Contrôler les valeurs **\**, méthode et port. - -``` shell -2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login -``` - -> L'URL d'accès n'est pas complète ou invalide. Utilisez l'option **-root** pour définir le chemin de l'URL de l'API. -> Par exemple : **--root monitoring**. - -``` shell -2020-10-20T10:42:23+02:00 [ERROR]: No route found for “POST /centreon/api/latest/platform/topology” -``` - -> La version Centreon du serveur distant est invalide. Elle doit être supérieure ou égale à 26.10. - -6. Ajout des droits pour l'utilsateur de base de données centreon d'utiliser la -commande **LOAD DATA INFILE**: - - ``` SQL - GRANT FILE on *.* to 'centreon'@'localhost'; - ``` - -7. Depuis l'interface web du serveur **Centreon Central**, éditez -tous les collecteurs rattachés au **Remote Server** et liez ceux-ci au -nouveau Remote Server via la liste de sélection. - -> N'oubliez pas de [générer la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) de votre -> **Remote Server**. - -> Un serveur Centreon Remote Server est un serveur dont l’administration est -> autonome. -> -> Ainsi, la configuration de l’annuaire LDAP, celle des utilisateurs -> ainsi que celle des ACL sont propres à ce serveur et doivent être configurées -> via les menus **Configuration** (pour les utilisateurs) et **Administration** -> (pour l'annuaire LDAP et les ACL). diff --git a/versioned_docs/version-26.10/developer/developer-gorgone-migrate-from-centcore.md b/versioned_docs/version-26.10/developer/developer-gorgone-migrate-from-centcore.md deleted file mode 100644 index 17cfd7610baf..000000000000 --- a/versioned_docs/version-26.10/developer/developer-gorgone-migrate-from-centcore.md +++ /dev/null @@ -1,100 +0,0 @@ ---- -id: developer-gorgone-migrate-from-centcore -title : Migrating from Centreon Centcore -description: "Procedure to migrate from Centreon Centcore to Centreon Gorgone" ---- - -Follow this procedure to migrate from Centreon Centcore to Centreon Gorgone. - -You need to build a configuration file based on **/etc/centreon/conf.pm**. - -- If using packages, execute the following command: - -```shell -$ perl /usr/bin/gorgone_config_init.pl -2019-09-30 11:00:00 - INFO - file '/etc/centreon-gorgone/config.yaml' created success -``` - -- If using sources, execute the following command: - -```shell -$ perl ./contrib/gorgone_config_init.pl -2019-09-30 11:00:00 - INFO - file '/etc/centreon-gorgone/config.yaml' created success -``` -> You need to adapt the sections according to your own initial database, configuration and network setup. - -The following configuration file will be created at **/etc/centreon-gorgone/config.yaml**: - -```shell -name: config.yaml -description: Configuration init by gorgone_config_init -configuration: - centreon: - database: - db_configuration: - dsn: "mysql:host=localhost;port=3306;dbname=centreon" - username: "centreon" - password: "centreon" - db_realtime: - dsn: "mysql:host=localhost;port=3306;dbname=centreon_storage" - username: "centreon" - password: "centreon" - gorgone: - gorgonecore: - privkey: "/var/lib/centreon-gorgone/.keys/rsakey.priv.pem" - pubkey: "/var/lib/centreon-gorgone/.keys/rsakey.pub.pem" - modules: - - name: httpserver - package: gorgone::modules::core::httpserver::hooks - enable: false - address: 0.0.0.0 - port: 8085 - ssl: false - auth: - enabled: false - allowed_hosts: - enabled: true - subnets: - - 127.0.0.1/32 - - - name: action - package: gorgone::modules::core::action::hooks - enable: true - - - name: cron - package: gorgone::modules::core::cron::hooks - enable: false - cron: !include cron.d/*.yaml - - - name: proxy - package: gorgone::modules::core::proxy::hooks - enable: true - - - name: legacycmd - package: gorgone::modules::centreon::legacycmd::hooks - enable: true - cmd_file: "/var/lib/centreon/centcore.cmd" - cache_dir: "/var/cache/centreon/" - cache_dir_trap: "/etc/snmp/centreon_traps/" - remote_dir: "/var/lib/centreon/remote-data/" - - - name: engine - package: "gorgone::modules::centreon::engine::hooks" - enable: true - command_file: "/var/lib/centreon-engine/rw/centengine.cmd" - - - name: pollers - package: gorgone::modules::centreon::pollers::hooks - enable: true - - - name: broker - package: "gorgone::modules::centreon::broker::hooks" - enable: true - cache_dir: "/var/cache/centreon//broker-stats/" - cron: - - id: broker_stats - timespec: "*/2 * * * *" - action: BROKERSTATS - parameters: - timeout: 10 -``` diff --git a/versioned_docs/version-26.10/migrate/migrate-from-3-4.md b/versioned_docs/version-26.10/migrate/migrate-from-3-4.md deleted file mode 100644 index d18d9d59c2bc..000000000000 --- a/versioned_docs/version-26.10/migrate/migrate-from-3-4.md +++ /dev/null @@ -1,252 +0,0 @@ ---- -id: migrate-from-3-4 -title: Migrate from a Centreon 3.4 platform -description: "Migrate data and configuration from a Centreon 3.4 platform" ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -## Prerequisites - -The following procedure only applies to migration from a Centreon 3.4 platform -installed on a 64-bit GNU/Linux distribution other than Oracle Linux / RHEL 8. -Here are the system requirements: - -| Components | Version | -| --------------- | ------- | -| Centreon Web | 2.8.x | -| Centreon Broker | 3.0.x | -| Centreon Engine | 1.8.x | - -Be sure that you have fully backed up your environment for the following -servers: - -- Central server -- Database server - -If you use Open Ticket providers with custom configurations, [make a backup of these before updating Centreon](../alerts-notifications/ticketing-install.md#creating-a-backup-of-your-custom-open-ticket-provider-configurations). - -## Migrate - -All servers (central, remote and pollers) in your architecture must have the same major version of Centreon. It is also recommended that they have the same minor version. - -> If your Centreon platform includes a Centreon redundancy system, please -> contact [Centreon support](https://support.centreon.com). - -> If you try to migrate a platform using the **Centreon Poller Display 1.6.x**, -> please refer to the following [migration -> procedure](poller-display-to-remote-server.md). - -### Install the new central server - -Perform the following actions: - -1. You will need to install a new Centreon Central server from -[packages](../installation/installation-of-a-central-server/using-packages.md), until you -complete the installation process by connecting to the Centreon Web -interface. - -2. Perform software and system updates: - - - - -```shell -dnf update -``` - - - - -```shell -dnf update -``` - - - - -```shell -apt update -``` - - - - -> It is advisable to set the same password for the *centreon* user during the web -> installation process. - -### Synchronize the data - -Connect to your old Centreon server and synchronize the following directories: - -```shell -rsync -avz /etc/centreon root@:/etc -rsync -avz /etc/centreon-broker root@:/etc -rsync -avz /var/log/centreon-engine/archives/ root@:/var/log/centreon-engine -rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@:/var/lib -rsync -avz /var/spool/centreon/.ssh root@:/var/spool/centreon -rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img -``` - -> Replace **\** with the IP of the new Centreon server. - -### Retrieve databases - -1. Dump source databases: - - ```shell - mysqldump -u root -p centreon > /tmp/centreon.sql - mysqldump -u root -p centreon_storage > /tmp/centreon_storage.sql - ``` - -2. Stop source MariaDB servers: - - ```shell - service mysqld stop - ``` - -3. Export the dumps to the new Centreon 26.10 database server (make sure you -have enough space for large databases dumps): - - ```shell - rsync -avz /tmp/centreon.sql root@:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@:/tmp/ - ``` - -4. On the Centreon 26.10 database server, drop the original databases and -create them again: - - ```shell - mysql -u root -p - ``` - - ```SQL - DROP DATABASE centreon; - DROP DATABASE centreon_storage; - CREATE DATABASE centreon; - CREATE DATABASE centreon_storage; - ``` - -5. Import the previously transferred dumps: - - ```shell - mysql -u root centreon -p -p - ``` - - Example: if your database_admin_user is `root`, enter: - - ``` - mysql_upgrade -u root -p - ``` - -7. Start the MariaDB process on the new server: - - ```shell - systemctl start mariadb - ``` - -> Replace **\** with the IP of the new Centreon server. - -### Synchronize the plugins - -Synchronizing the monitoring plugins is more complex and depends on your -installation. The main directories to synchronize are: - -1. /usr/lib/nagios/plugins/ -2. /usr/lib/centreon/plugins/ - -> To run the plugins, you must first install the required dependencies. - -> If you still have remote Centreon Engine 1.8.1 Pollers whose -> upgrade to 26.10 you want to postpone, be aware that Centreon Web 26.10 resource -> $USER1$ now points to /usr/lib64/nagios/plugins -> -> This is how to mitigate the issue on the 1.8.1 Pollers: -> -> ```shell -> mv /usr/lib64/nagios/plugins/* /usr/lib/nagios/plugins/ -> rmdir /usr/lib64/nagios/plugins/ -> ln -s -t /usr/lib64/nagios/ /usr/lib/nagios/plugins/ -> ``` -> -> You now have a symbolic link like this: -> -> ```shell -> $ ls -alt /usr/lib64/nagios/ -> lrwxrwxrwx 1 root root 24 1 nov. 17:59 plugins -> /usr/lib/nagios/plugins/ -> -rwxr-xr-x 1 root root 1711288 6 avril 2018 cbmod.so -> ``` - -The credentials of the newly created **centreon-gorgone** user need to be updated to match those of the **centreon-gorgone** user on the old server. Edit `etc/centreon-gorgone/config.d/31-centreon-api.yaml` and enter the credentials of the old user. Example: - - ```shell - gorgone: - tpapi: - - name: centreonv2 - base_url: "http://127.0.0.1/centreon/api/latest/" - username: "@GORGONE_USER@" - password: "@GORGONE_PASSWORD@" - - name: clapi - username: "@GORGONE_USER@" - password: "@GORGONE_PASSWORD@" - ``` - -You can now push the poller's configuration from Centreon 25.10 whether the remote -Poller is Centreon Engine 26.10 or 1.8.1. - -### Upgrade Centreon - -On the new server, force the update by moving the contents of the -**/var/lib/centreon/installs/install-26.10.0-YYYYMMDD\_HHMMSS** directory to -the **/usr/share/centreon/www/install** directory: - -```shell -cd /var/lib/centreon/installs/ -mv install-26.10.0-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ -``` - -> If you use the same IP address or same DNS name for the old Centreon webserver -> and the new one, do a full cache cleanup of your browser to avoid JS issues - -Go to `http:///centreon` URL and perform the upgrade. - -> If you changed the *centreon* password during the installation process, you must -> follow these steps: -> -> 1. Edit the /etc/centreon/centreon.conf.php file, -> 2. Edit the /etc/centreon/conf.pm file, -> 3. Edit the Centreon Broker central configuration using Centreon web interface -> and change the password for the **Perfdata generator** and **Broker SQL -> database** output, -> 4. Edit the file /etc/centreon/config.d/10-database.yaml. - -If the IP of your Centreon server has changed, edit the configuration for all -the Centreon Broker modules of your Pollers and change the IP to connect to -the Centreon Central server (output IPv4). See the [Advanced -configuration](../monitoring/monitoring-servers/advanced-configuration.md#tcp-outputs) -chapter for more information. - -Then [generate](../monitoring/monitoring-servers/deploying-a-configuration.md) the -configuration of all your pollers and export it. - -### Upgrade the modules - -Please refer to the documentation of each module to verify compatibility with -Centreon 26.10 and perform the upgrade. - -### Migrate your other servers - -Make sure all servers (central, remote and pollers) in your architecture have the same major version of Centreon. diff --git a/versioned_docs/version-26.10/migrate/nagios-to-centreon.md b/versioned_docs/version-26.10/migrate/nagios-to-centreon.md deleted file mode 100644 index 33f46c073c2d..000000000000 --- a/versioned_docs/version-26.10/migrate/nagios-to-centreon.md +++ /dev/null @@ -1,117 +0,0 @@ ---- -id: nagios-to-centreon -title: Nagios Reader to Centreon CLAPI -description: "Convert Nagios configuration files into Centreon CLAPI import commands" ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - - -**Nagios Reader to Centreon CLAPI** is a free and open source project to analyze -Nagios CFG configuration files and to transform a monitoring configuration to -a Centreon CLAPI command in order to import a configuration into the Centreon web -interface. - -## Prerequisites - -First of all, you need a Centreon server installed and ready to use. Please see -the documentation [to install a Centreon server](../installation/installation-of-a-central-server/using-packages.md). - -Be sure that you have fully backed up your environment for the following -servers: - -- Central server -- Database server - -If you use Open Ticket providers with custom configurations, [make a backup of these before updating Centreon](../alerts-notifications/ticketing-install.md#creating-a-backup-of-your-custom-open-ticket-provider-configurations). - -## Installation - -This script uses the Perl-Nagios-Object library to read CFG files. To install it, -please follow these steps on your Nagios(R) server: - - - - -```shell -dnf install perl-Module-Build -``` - - - - -```shell -dnf install perl-Module-Build -``` - - - - -```shell -apt-get install libmodule-build-perl -``` - - - - -```shell -cd /tmp -wget http://search.cpan.org/CPAN/authors/id/D/DU/DUNCS/Nagios-Object-0.21.20.tar.gz -tar xzf Nagios-Object-0.21.20.tar.gz -cd Nagios-Object-0.21.20 -perl Build.PL -./Build -./Build test -./Build install -``` - -Download script from GitHub on your Nagios(R) server: - -```shell -cd /tmp -git clone https://github.com/centreon/nagiosToCentreon.git -cd nagiosToCentreon -``` - -## Usage - -On a fresh Centreon server,the default poller is named "Central". If you rename -it or if you want to link this Nagios configuration to a predefined poller, you -must change the poller name on line 65: - -```perl -my $default_poller = "Central"; -``` - -To display help use the following command: - -```shell -$ perl nagios_reader_to_centreon_clapi.pl --help -###################################################### -# Copyright (c) 2005-2015 Centreon # -# Bugs to http://github.com/nagiosToCentreon # -###################################################### - -Usage: nagios_reader_to_centreon_clapi.pl - -V (--version) Show script version - -h (--help) Usage help - -C (--config) Path to nagios.cfg file -``` - -To run the script, please use the following command: - -```shell -perl nagios_reader_to_centreon_clapi.pl --config /usr/local/nagios/etc/ > /tmp/centreon_clapi_import_commands.txt -``` - -Export the file /tmp/centreon\_clapi\_import\_commands.txt on your Centreon -server. - -Run the following command to import the configuration into Centreon on your Centreon -server: - -```shell -/usr/share/centreon/bin/centreon -u admin -p -i /tmp/centreon_clapi_import_commands.txt -``` - -Replace **\** with the password of the **admin** Centreon web user. diff --git a/versioned_docs/version-26.10/migrate/poller-display-to-remote-server.md b/versioned_docs/version-26.10/migrate/poller-display-to-remote-server.md deleted file mode 100644 index 9584e9ad5ac0..000000000000 --- a/versioned_docs/version-26.10/migrate/poller-display-to-remote-server.md +++ /dev/null @@ -1,184 +0,0 @@ ---- -id: poller-display-to-remote-server -title: Migrate a platform with Poller Display module -description: "Migrate a platform using the deprecated Poller Display module" ---- - -## Migrate your Centreon Central server - -If the module **centreon-poller-display-central-1.6.x** is installed: - -1. Go to **Administration > Extensions > Modules** and uninstall -**centreon-poller-display-central**. - -2. Remove the associated package: - - ```shell - yum remove centreon-poller-display-central - ``` - -Refer to the [migration procedure](../migrate/migrate-from-3-4.md). - -> If you use the Centreon EMS modules, you must update these repositories. Be sure -> to contact Centreon support and request new licenses. - -## Migrate a Poller from Poller Display module to Remote Server - -1. Go to **Administration > Extensions > Modules** and uninstall the -**Centreon Poller Display** module. - -2. If you installed the module using an RPM package, remove it with the -following command: - - ```shell - yum remove centreon-poller-display - ``` - -Refer to the [migration procedure](../migrate/migrate-from-3-4.md). - - > If you use Centreon EMS modules, you must update the repositories. Be sure to - > contact your Centreon support team and request new licenses. - -4. Go to **Administration > Extensions > Modules** and install the -**centreon-license-manager** module. - -5. ## Register the server - -To transform the server into a Remote Server and register it to the Centreon Central server, execute the following command: - -``` shell -/usr/share/centreon/bin/registerServerTopology.sh -u \ --t remote -h -n -``` - -Example: - -``` shell -/usr/share/centreon/bin/registerServerTopology.sh -u admin -t remote -h 192.168.0.1 -n remote-1 -``` - -> Replace **\** with the IP of the Centreon server seen by the Remote Server. - -> The **\** must have access to the configuration API. You can use the default **admin** account. - -> If you need to change the HTTP method or the port, you can use the following format for the **-h** option: -> HTTPS:/\:PORT - -Then follow instructions by -1. Entering your password: - - ``` shell - 192.168.0.1: please enter your password: - ``` - -2. Select the IP address if multiple network interfaces exist: - - ```shell - Which IP do you want to use as CURRENT NODE IP? - 1) 192.168.0.2 - 2) 192.168.0.3 - 1 - ``` - -3. Then validate the information: - - ``` shell - Summary of the informations that will be send: - - Api connection: - username: admin - password: ****** - target server: 192.168.0.1 - - Pending Registration Server: - name: remote-1 - type: remote - address: 192.168.0.2 - - Do you want to register this server with those informations? (y/n)y - ``` - -4. Add additional information to enable future communication between your Remote Server and its Central. -Provide the required information to convert your platform to a remote server: - - ```shell - : Please enter your username: - admin - : Please enter your password: - - : Protocol [http]: - : Port [80]: - : centreon root folder [centreon]: - ``` - -5. If you use a proxy, please define credentials: - - ```shell - Are you using a proxy? (y/n) - y - enter your proxy Host: - myproxy.example.com - enter your proxy Port [3128]: - Are you using a username/password? (y/n) - y - enter your username: - my_proxy_username - enter your password: - - ``` - -You will receive the validation of the Centreon central server: - -``` shell -2020-10-16T17:19:37+02:00 [INFO]: The CURRENT NODE 'remote: 'remote-1@192.168.0.2' has been converted and registered successfully. -``` - -### Main error messages - -``` shell -2020-10-20T10:23:15+02:00 [ERROR]: Invalid credentials -``` - -> Your credentials are incorrect for the **\**. - -``` shell -2020-10-20T10:24:59+02:00 [ERROR]: Access Denied. -``` - -> The **\** doesn't have access to configuration API. - -``` shell -Failed to connect to 192.168.0.1:444; Connection refused -``` - -> Unable to access the API. Please check **\**, scheme and port. - -``` shell -2020-10-20T10:39:30+02:00 [ERROR]: Can’t connect to the API using: https://192.168.0.1:443/centreon/api/latest/login -``` - -> The access url is not complete or is invalid. Use the **--root** option to define the API URL Path. For example: **--root monitoring**. - -``` shell -2020-10-20T10:42:23+02:00 [ERROR]: No route found for “POST /centreon/api/latest/platform/topology” -``` - -> Your Centreon target version is invalid. It should be greater than or equal to 21.04. - -6. Add rights for the centreon database user to use the **LOAD DATA INFILE** command: - - ``` SQL - GRANT FILE on *.* to 'centreon'@'localhost'; - ``` - -7. **On the Centreon Central server**, edit all pollers and attach them to the -**Remote Server** using the selection list. - -> Remember to [generate the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) for your -> **Remote Server**. - -> A Centreon Remote Server is self-administered. -> -> Thus, the configuration of the -> LDAP directory, users and ACLs are specific to this server and must be -> configured through the **Administration** menu. diff --git a/versioned_sidebars/version-26.10-sidebars.json b/versioned_sidebars/version-26.10-sidebars.json index 6099a925b605..82761c22ba45 100644 --- a/versioned_sidebars/version-26.10-sidebars.json +++ b/versioned_sidebars/version-26.10-sidebars.json @@ -1254,22 +1254,6 @@ { "type": "doc", "id": "migrate/migrate-from-debian-to-debian" - }, - { - "type": "doc", - "id": "migrate/migrate-from-3-4" - }, - { - "type": "doc", - "id": "migrate/nagios-to-centreon" - }, - { - "type": "doc", - "id": "migrate/poller-display-to-remote-server" - }, - { - "type": "doc", - "id": "developer/developer-gorgone-migrate-from-centcore" } ] } From e42dc4b86e2af58f52b427956a81803d7c170988 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 23 Sep 2026 14:53:55 +0200 Subject: [PATCH 078/179] FR migration topics --- .../migrate/migrate-from-debian-to-debian.md | 38 ++++++++++++++++--- .../migrate/migrate-from-el-to-debian.md | 32 ++++++++++++++-- .../migrate/migrate-from-el-to-el.md | 2 +- .../migrate/migrate-from-el-to-el.md | 4 +- 4 files changed, 64 insertions(+), 12 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md index 2cc77943b532..54d8e09445a8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md @@ -1,14 +1,14 @@ --- id: migrate-from-debian-to-debian -title: Migrer depuis Debian 11 vers Debian 12 -description: "Migrer une plateforme Centreon de Debian 11 vers Debian 12" +title: Migrer vers une version plus récente de Debian +description: "Migrer une plateforme Centreon vers une version plus récente de Debian" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; ## Prérequis -Cette procédure ne s'applique que si vous souhaitez migrer de Debian 11 vers Debian 12, sur des serveurs différents. +Cette procédure ne s'applique que si vous souhaitez migrer de Debian vers une version plus récente de Debian, sur des serveurs différents. Tous les serveurs de votre architecture (serveur central, serveurs distants et collecteurs) doivent avoir la même version majeure de Centreon. Il est également recommandé d'avoir la même version mineure. @@ -25,7 +25,7 @@ Si vous utilisez un fournisseur Open Ticket avec des configurations personnalis ### Étape 1 : Installer le nouveau serveur central -1. Installez votre nouvel OS Debian 12. +1. Installez votre nouvel OS Debian. 2. Installez un nouveau serveur central Centreon à partir des [paquets](../installation/installation-of-a-central-server/using-packages.md) jusqu'à terminer le processus d'installation en vous connectant à l'interface web. @@ -91,12 +91,25 @@ apt update && apt upgrade mysqldump -u root -p centreon_storage > /tmp/centreon_storage.sql ``` -2. Sur l'ancien serveur, arrêtez MariaDB : +2. Sur l'ancien serveur, arrêtez la base de données : + + + ```shell systemctl stop mariadb ``` + + + + ```shell + systemctl stop mysql + ``` + + + + 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell @@ -143,12 +156,25 @@ apt update && apt upgrade mysql_upgrade -u root -p ``` -7. Démarrez le processus **mariadb** sur le nouveau serveur : +7. Démarrez le processus de base de données sur le nouveau serveur : + + + ```shell systemctl start mariadb ``` + + + + ```shell + systemctl start mysql + ``` + + + + > Remplacez **\** par l'adresse IP de votre nouveau serveur > Centreon. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md index 8fa2de8ac771..33b44f93b188 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md @@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem'; Cette procédure ne s'applique que dans les conditions suivantes : -- Vous souhaitez migrer d'un OS de type EL 64-bits vers Debian. Par exemple, vous souhaitez migrer d'un CentOS 7 à Debian 12. +- Vous souhaitez migrer d'un OS de type EL 64-bits vers Debian. Par exemple, vous souhaitez migrer d'un CentOS 7 à Debian 13. - Votre version de Centreon est 18.10 ou plus récente, et vous souhaitez passer à la dernière version de Centreon. Si vous souhaitez migrer depuis une plus ancienne version, [contactez l'équipe support Centreon](https://support.centreon.com). Tous les serveurs de votre architecture (serveur central, serveurs distants et collecteurs) doivent avoir la même version majeure de Centreon. Il est également recommandé d'avoir la même version mineure. @@ -95,12 +95,25 @@ apt update && apt upgrade mysqldump -u root -p centreon_storage > /tmp/centreon_storage.sql ``` -2. Sur l'ancien serveur, arrêtez MariaDB : +2. Sur l'ancien serveur, arrêtez la base de données : + + + ```shell systemctl stop mariadb ``` + + + + ```shell + systemctl stop mysql + ``` + + + + 3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell @@ -147,12 +160,25 @@ apt update && apt upgrade mysql_upgrade -u root -p ``` -7. Démarrez le processus **mariadb** sur le nouveau serveur : +7. Démarrez le processus de base de données sur le nouveau serveur : + + + ```shell systemctl start mariadb ``` + + + + ```shell + systemctl start mysql + ``` + + + + > Remplacez **\** par l'adresse IP de votre nouveau serveur > Centreon. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md index 5d153dc9f306..9d765fdd16bb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md @@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem'; Cette procédure ne s'applique que dans les conditions suivantes : -- Vous souhaitez migrer d'un OS de type EL 64-bits vers un autre OS de type EL 64-bits supporté. Par exemple, vous souhaitez migrer d'un CentOS 7 à un Alma 8 ou 9. +- Vous souhaitez migrer d'un OS de type EL 64-bits vers un autre OS de type EL 64-bits supporté. Par exemple, vous souhaitez migrer d'un CentOS 7 à un Alma 9. - Votre version de Centreon est 18.10 ou plus récente. Tous les serveurs de votre architecture (serveur central, serveurs distants et collecteurs) doivent avoir la même version majeure de Centreon. Il est également recommandé d'avoir la même version mineure. diff --git a/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md b/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md index b4fa14a8dd4c..afe25331d4bb 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md @@ -40,14 +40,14 @@ complete the installation process by connecting to the Centreon web interface. 3. Perform software and system updates: - + ```shell dnf update ``` - + ```shell dnf update From a32bfabd397456524b2a907cc37d559fa9c690d7 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 23 Sep 2026 15:28:20 +0200 Subject: [PATCH 079/179] Fix links --- .../version-26.10/migrate/introduction.md | 2 ++ .../version-26.10/migrate/migrate-from-el-to-debian.md | 4 ++-- .../version-26.10/migrate/migrate-from-el-to-el.md | 4 ++-- .../version-26.10/upgrade/introduction.md | 3 +-- versioned_docs/version-26.10/migrate/introduction.md | 2 ++ .../version-26.10/migrate/migrate-from-el-to-debian.md | 4 ++-- versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md | 4 ++-- versioned_docs/version-26.10/upgrade/introduction.md | 3 +-- 8 files changed, 14 insertions(+), 12 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/introduction.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/introduction.md index 61e1a22e7bfb..7d86fa05ef26 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/introduction.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/introduction.md @@ -9,3 +9,5 @@ Les procédures de migration s'appliquent dans le cas où vous souhaitez install Dans les cas où vous souhaitez simplement changer de version de Centreon alors que celui-ci est installé sur un OS supporté, utilisez les [procédures d'upgrade](../upgrade/introduction.md). Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. + +Si vous souhaitez migrer depuis une version très ancienne de Centreon (par exemple, Centreon 3.4), [contactez le support](https://support.centreon.com/). diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md index 33b44f93b188..dfe6a716c413 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md @@ -266,9 +266,9 @@ Si vous utilisez vos propres plugins personnalisés, synchronisez les répertoir 10. Allez à la page **Configuration > Connecteurs > Connecteurs de supervision**, puis [mettez à jour tous les connecteurs de supervision](../monitoring/pluginpacks.md#mettre-à-jour-un-ou-plusieurs-packs). -### Étape 6 (anciennes versions uniquement): Migrer vers Gorgone + ### Étape 7: Mettre à jour les modules diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md index 9d765fdd16bb..ab3293ec8806 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md @@ -260,9 +260,9 @@ rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/c 10. Allez à la page **Configuration > Connecteurs > Connecteurs de supervision**, puis [mettez à jour tous les connecteurs de supervision](../monitoring/pluginpacks.md#mettre-à-jour-un-ou-plusieurs-packs). -### Étape 6 (anciennes versions uniquement): Migrer vers Gorgone + ### Étape 7: Mettre à jour les modules diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/introduction.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/introduction.md index 1ee70e3568df..5ef1a305c6b1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/introduction.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/introduction.md @@ -16,5 +16,4 @@ Avant de monter Centreon de version, pensez à réaliser une sauvegarde de votre > leur nouveau dépôt afin d'éviter les problèmes de dépendances. > Consultez [cette page](../reporting/upgrade.md#étape-1--montée-de-version-du-paquet). -> Si vous souhaitez changer l'OS du serveur hôte, suivez la [procédure de migration](../migrate/introduction.md). (Si vous souhaitez migrer une plateforme qui utilise **Centreon Poller Display 1.6.x**, consultez la -> [procédure de migration](../migrate/poller-display-to-remote-server.md) correspondante.) +> Si vous souhaitez changer l'OS du serveur hôte, suivez la [procédure de migration](../migrate/introduction.md). diff --git a/versioned_docs/version-26.10/migrate/introduction.md b/versioned_docs/version-26.10/migrate/introduction.md index 15d40611467d..266fb6daa807 100644 --- a/versioned_docs/version-26.10/migrate/introduction.md +++ b/versioned_docs/version-26.10/migrate/introduction.md @@ -9,3 +9,5 @@ Migration procedures apply when you wish to install your Centreon on a different If you just want to switch to a newer version of Centreon and your current platform is already installed on a supported OS, use the [upgrade procedures](../upgrade/introduction.md) instead. If you have HA on your platform, contact your Centreon sales representative to discuss any migration scenario. + +If you want to migrate from a very old Centreon version (e.g., Centreon 3.4), [please contact our support team](https://support.centreon.com/). \ No newline at end of file diff --git a/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md b/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md index 14effc3486a4..12ebcbb01ef5 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md @@ -261,9 +261,9 @@ chapter for more information. 10. Go to **Configuration > Connectors > Monitoring Connectors**, then [update all the Monitoring Connectors](../monitoring/pluginpacks.md#updating-one-packall-packs). -### Step 6 (older versions only): Migrate to Gorgone + ### Step 7: Upgrade the modules diff --git a/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md b/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md index afe25331d4bb..934fdb1c1204 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md @@ -274,9 +274,9 @@ chapter for more information. 10. Go to **Configuration > Connectors > Monitoring Connectors**, then [update all the Monitoring Connectors](../monitoring/pluginpacks.md#updating-one-packall-packs). -### Step 6 (older versions only): Migrate to Gorgone + ### Step 7: Upgrade the modules diff --git a/versioned_docs/version-26.10/upgrade/introduction.md b/versioned_docs/version-26.10/upgrade/introduction.md index 189a716ac834..f26023fb1133 100644 --- a/versioned_docs/version-26.10/upgrade/introduction.md +++ b/versioned_docs/version-26.10/upgrade/introduction.md @@ -16,5 +16,4 @@ Before you upgrade Centreon, make sure you back up your platform. > their new repository to avoid dependency problems. > Refer to [this page](../reporting/upgrade.md#step-1-update-the-repository). -> If you want to change the OS of the host server, follow the [migration procedure](../migrate/introduction.md). (If you want to migrate a platform that uses **Centreon Poller Display 1.6.x**, refer -> to the corresponding [migration procedure](../migrate/poller-display-to-remote-server.md).) +> If you want to change the OS of the host server, follow the [migration procedure](../migrate/introduction.md). From 1c1f87c812702410f0d0175d71ed46b902ac632c Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 23 Sep 2026 17:33:18 +0200 Subject: [PATCH 080/179] Creating self-signed certificates --- .../administration/self-signed-certificate.md | 268 +++++++++++++++++- .../administration/self-signed-certificate.md | 108 +++---- 2 files changed, 321 insertions(+), 55 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md index 1e0f339ee13d..40f9f93cee29 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md @@ -1,15 +1,229 @@ --- id: self-signed-certificate -title: Créer un certificat autosigné -description: "Créer un certificat autosigné avec OpenSSL, à des fins de test" +title: Créer un certificat auto-signé +description: "Créer un certificat auto-signé avec OpenSSL" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -> Self-signed certificates are for test purposes only. You MUST NOT use them in production. +> Les certificats auto-signés sont réservés aux tests. Vous NE DEVEZ PAS les utiliser en production. +## Fichiers nécessaires pour établir des connexions TLS avec des certificats auto-signés - + +## Étape 1 : Créer les répertoires de sortie + +Créez des dossiers pour organiser les fichiers : un pour les fichiers propres à l'autorité de certification, un pour les fichiers destinés au service web ou au service de base de données. + +Pour l'autorité de certification : + +```shell +sudo mkdir -p /out/CA +``` + +Pour le serveur central/distant, ou pour la base de données : + + + + +```shell +sudo mkdir -p /out/web +``` + + + + +```shell +sudo mkdir -p /out/db +``` + + + + +## Étape 2 : Générer la clé privée de l'autorité de certification racine (RSA 4096 bits) + +Il s'agit de la clé secrète de votre autorité de certification. La commande **chmod 400** limite l'accès au fichier : seul son propriétaire peut le lire (et personne ne peut y écrire). L'exposition de la clé est ainsi réduite au minimum. + +```shell +sudo openssl genrsa -out /out/CA/rootCA.key 4096 +sudo chmod 400 /out/CA/rootCA.key +``` + +## Étape 3 : Générer le certificat auto-signé de l'autorité de certification racine (10 ans) + +Créez maintenant le certificat de l'autorité de certification. Ce document public identifie votre autorité de certification (nom, organisation, etc.). Vous le distribuerez ensuite à tous les clients et serveurs qui doivent faire confiance aux certificats qu'elle signe. + +Ce certificat est "auto-signé", car aucune autorité ne se trouve au-dessus de lui : l'autorité de certification se porte garante d'elle-même. C'est un fonctionnement normal pour une autorité de certification racine. + +* `-x509` indique à OpenSSL de produire directement un certificat (et non une demande de signature). +* `-days 3650` fixe l'expiration à environ 10 ans. Cette durée est habituelle pour une autorité de certification racine, qui n'a pas vocation à être renouvelée souvent. +* `-subj` définit les champs d'identité directement dans la ligne de commande : CN (Common Name) vaut « Test Dev CA », O (Organization) vaut « YourOrganization » et OU (Organizational Unit) vaut « R&D ». Remplacez ces valeurs par celles de votre organisation. + +```shell +sudo openssl req -x509 -new -nodes -key /out/CA/rootCA.key \ + -sha256 -days 3650 \ + -subj "/CN=Test Dev CA/O=YourOrganization/OU=R&D" \ + -out /out/CA/rootCA.pem +``` + +## Étape 4 : Générer la clé privée du serveur final (RSA 2048 bits) + +Il s'agit de la clé privée du serveur lui-même (du serveur central/distant ou de la base de données). Elle est distincte de la clé de l'autorité de certification : le serveur ne doit jamais partager une clé avec l'autorité de certification. + + + + +```shell +sudo openssl genrsa -out /out/web/server-key.pem 2048 +``` + + + + +```shell +sudo openssl genrsa -out /out/db/server-key.pem 2048 +``` + + + + +## Étape 5 : Créer le fichier de configuration des extensions OpenSSL pour les SAN + +Les navigateurs et clients récents exigent qu'un certificat liste tous les noms d'hôte et adresses IP pour lesquels il est valide : c'est la liste SAN (Subject Alternative Name). Un CN seul ne suffit plus pour être considéré comme fiable. Cette étape crée un petit fichier de configuration qui définit : + +* `basicConstraints = CA:FALSE` : ce certificat n'est pas autorisé à signer d'autres certificats (seule l'autorité de certification racine le peut). +* `keyUsage / extendedKeyUsage` : limite le certificat à son usage prévu, c'est-à-dire l'authentification d'un serveur TLS. +* `subjectAltName` : la liste des noms et adresses IP pour lesquels le certificat doit être valide. Ici : web, localhost, db et l'adresse IP 127.0.0.1. Modifiez cette liste pour qu'elle corresponde aux noms d'hôte réels par lesquels votre serveur sera joint. + +```shell +sudo tee /out/cert.ext > /dev/null < + + +```shell +sudo openssl req -new -key /out/web/server-key.pem -out /out/web/server.csr \ + -subj "/CN=web/O=Centreon" +``` + + + + +```shell +sudo openssl req -new -key /out/db/server-key.pem -out /out/db/server.csr \ + -subj "/CN=db/O=Centreon" +``` + + + + +## Étape 7 : Signer le certificat final avec l'autorité de certification racine (validité de 397 jours) + +C'est cette étape qui produit le certificat serveur utilisable : l'autorité de certification (son certificat et sa clé privée, créés aux étapes 2 et 3) signe la CSR de l'étape 6, en appliquant les extensions et les SAN définis à l'étape 5. + +* `-days 397` : 397 jours est la durée de vie maximale actuellement acceptée par les principaux navigateurs (Apple, Google, Mozilla) pour les certificats de serveur TLS. Au-delà, les clients risquent de rejeter le certificat. +* `-CAcreateserial` : crée, lors de la première exécution, un fichier de suivi des numéros de série (rootCA.srl), puis l'incrémente à chaque nouvelle signature. Chaque certificat émis par cette autorité de certification reçoit ainsi un numéro de série unique. + + + + +```shell +sudo openssl x509 -req -in /out/web/server.csr \ + -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ + -CAserial /out/CA/rootCA.srl -CAcreateserial \ + -out /out/web/server.pem -days 397 -sha256 \ + -extfile /out/cert.ext -extensions v3_req +``` + + + + +```shell +sudo openssl x509 -req -in /out/db/server.csr \ + -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ + -CAserial /out/CA/rootCA.srl -CAcreateserial \ + -out /out/db/server.pem -days 397 -sha256 \ + -extfile /out/cert.ext -extensions v3_req +``` + + + + +## Étape 8 : Définir les permissions + +Les permissions suivent ici le principe du moindre privilège : + +* `0644` (lecture pour tous, écriture pour le propriétaire uniquement) pour les certificats publics : ils ne contiennent aucun secret. +* `0640` (lecture pour le propriétaire et le groupe, aucun accès pour les autres) pour la clé privée du serveur. Cette clé est sensible, mais un service exécuté sous un groupe spécifique aura probablement besoin de la lire. + +Pour l'autorité de certification racine : + +```shell +sudo chmod 0644 /out/CA/rootCA.pem +``` + +Pour le serveur central/distant : + +```shell +sudo chmod 0644 /out/web/server.pem +sudo chmod 0640 /out/web/server-key.pem +``` + +Pour la base de données : + +```shell +sudo chmod 0644 /out/db/server.pem +sudo chmod 0640 /out/db/server-key.pem +``` + +Les 3 fichiers nécessaires se trouvent maintenant dans votre dossier **/out**. Vous pouvez les copier aux emplacements appropriés sur vos serveurs (et les renommer si besoin). + + \ No newline at end of file + --> + + + diff --git a/versioned_docs/version-26.10/administration/self-signed-certificate.md b/versioned_docs/version-26.10/administration/self-signed-certificate.md index 86957aa3fda7..c166f5d38968 100644 --- a/versioned_docs/version-26.10/administration/self-signed-certificate.md +++ b/versioned_docs/version-26.10/administration/self-signed-certificate.md @@ -14,14 +14,23 @@ This procedure allows you to create the following files: | File | Where to store it | Role | |--------------|-----------------------------------|-------------------------------------------------------------------------| -| server.key | On the server you want to make secure (central/remote, database...) | Stays secret on the secure server. Used to decrypt the client's data. | -| server-key.pem | On the server you want to make secure (central/remote, database...) | The signed certificate that will be sent automatically to any client that tries to connect to the secure server. | -| rootCA.pem | On the client (browser, OS...) | Root CA self-signed certificate. This is a public file, used to validate the **server.pem** certificate the client has received. **rootCA.pem** will have to be copied to all machines that will interact with the secure machine (that has sent server-key.pem). only applies for self-signed certificates? | +| server-key.pem | On the server you want to make secure (central/remote, database...) | Private key for **server.pem**: stays secret on the secure server. Used to prove the server's identity. | +| server.pem | On the server you want to make secure (central/remote, database...) | The signed certificate that will be sent automatically to any client that tries to connect to the secure server. | +| rootCA.pem | On the client (browser, OS...) | Root CA self-signed certificate. This is a public file, used to validate the **server.pem** certificate the client has received. **rootCA.pem** will have to be copied to all machines that will interact with the secure machine (that has sent **server.pem**). | | rootCA.key | Only on the machine that generates the CA, stays in a temporary folder | This file plays no role in production. It is used only to sign **rootCA.pem** when creating it. | ## What this procedure does -The procedure creates the files you need to set up a TLS connection, in a temporary folder. When you set up HTTPS on a server, you will need to deploy the necessary files to the correct location. Example: **/etc/pki/centreon-tls** is the default location for certificates on EL. Debian's default path is **/etc/ssl/certs**. +The procedure creates the files you need to set up a TLS connection, in temporary folders. When you set up HTTPS on a server, you will need to deploy the necessary files to the correct location. Example: **/etc/pki/centreon-tls** is the default location for certificates on EL. Debian's default path is **/etc/ssl/certs**. + +The procedure can be run on a Centreon platform that has a local database, or a remote one. + +* If you have a local database, run the commands in both tabs on your Centreon server. +* If you have a remote database, run the procedure twice: + * On your Centreon server, create a CA (steps 1 to 3), then run the commands in the **On the central/remote server** tabs. + * On the database server, create another CA, then run the commands in the **On the database server** tabs. + + You then have two different **rootCA.pem** files. Copy the **rootCA.pem** from the database server to the machines that connect to the database (for example, your Centreon server). Copy the **rootCA.pem** from your Centreon server to the machines that connect to it. - -If the database runs as a separate service/container (e.g., MariaDB), it typically needs its own copy of the certificate and key, owned by the user/group it runs as (here 1001:1001 — adjust to match your actual DB container/user UID/GID). - -Note the key permission here is tighter (0600, owner-only) than the general server key in Step 8, and ownership is explicitly changed with chown so the database process can read it. +For the central/remote server: ```shell -sudo cp /out/server.pem /out/db/server.pem -sudo cp /out/server-key.pem /out/db/server-key.pem -sudo chmod 0644 /out/db/server.pem -sudo chmod 0600 /out/db/server-key.pem -sudo chown 1001:1001 /out/db/server.pem /out/db/server-key.pem +sudo chmod 0644 /out/web/server.pem +sudo chmod 0640 /out/web/server-key.pem ``` -## Step 10: Generate environment manifest - -Finally, write a small .env-style file listing where each certificate/key lives, so other tooling (deployment scripts, docker-compose, systemd units, etc.) can source this file instead of hardcoding paths everywhere. +For the database: ```shell -sudo tee /out/certs.env > /dev/null < + + \ No newline at end of file From 086272ed7c93fb479a1082f09ce14cded068bfa4 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 23 Sep 2026 18:00:25 +0200 Subject: [PATCH 081/179] Fix "which install" topic, EN+FR --- .../version-26.10/getting-started/which-install.md | 8 +++++--- .../version-26.10/getting-started/which-install.md | 2 +- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/which-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/which-install.md index 842273aaa319..2b6be1093990 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/which-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/which-install.md @@ -12,9 +12,11 @@ Centreon propose plusieurs modes d'installation. Lequel choisir ? ## Pour installer Centreon en production -- À partir des [paquets RPM ou DEB](../installation/installation-of-a-central-server/using-packages.md) : si vous avez déjà - l'OS et vous souhaitez juste installer Centreon. Voir la [liste des OS supportés par Centreon](../installation/compatibility.md#système-dexploitation). +Si vous avez déjà l'OS et vous souhaitez juste installer Centreon, utilisez l'une de ces solutions : + +* [Installation silencieuse](../installation/installation-of-a-central-server/unattended.md), réalisée par un script. +* À partir des [paquets RPM ou DEB](../installation/installation-of-a-central-server/using-packages.md) : . Voir la [liste des OS supportés par Centreon](../installation/compatibility.md#système-dexploitation). ## Voir aussi -Voir aussi les [prérequis d'installation](../installation/prerequisites.md). \ No newline at end of file +Voir aussi les [prérequis d'installation](../installation/prerequisites.md). diff --git a/versioned_docs/version-26.10/getting-started/which-install.md b/versioned_docs/version-26.10/getting-started/which-install.md index c7d260ec64df..47733b06c67b 100644 --- a/versioned_docs/version-26.10/getting-started/which-install.md +++ b/versioned_docs/version-26.10/getting-started/which-install.md @@ -14,7 +14,7 @@ There are several ways to install Centreon. Which one suits your needs best? If you already have the OS and you only want to install Centreon, use either of these: -* [Unattended installation](../installation/installation-of-a-central-server/unattended.md), donc by running a script. +* [Unattended installation](../installation/installation-of-a-central-server/unattended.md), done by running a script. * [RPM or DEB packages](../installation/installation-of-a-central-server/using-packages.md). See the list of [supported operating systems](../installation/compatibility.md#operating-systems). From 9db2140ec9689e5ef3d159c8af3540f39214fd26 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 24 Sep 2026 09:36:07 +0200 Subject: [PATCH 082/179] Update OSs in update files --- .../update/update-centreon-ha.md | 12 ++++---- .../update/update-centreon-platform.md | 28 +++++++++---------- .../update/update-centreon-ha.md | 12 ++++---- .../update/update-centreon-platform.md | 28 +++++++++---------- 4 files changed, 40 insertions(+), 40 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-ha.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-ha.md index 932a8ff9f538..c1dce49613cd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-ha.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-ha.md @@ -59,7 +59,7 @@ dnf update centreon\* ``` - + Videz le cache : @@ -74,7 +74,7 @@ dnf update centreon\* ``` - + Videz le cache : @@ -104,14 +104,14 @@ mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`da sudo -u apache /usr/share/centreon/bin/console cache:clear ``` - + ```bash mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y%m%d` sudo -u apache /usr/share/centreon/bin/console cache:clear ``` - + ```bash mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y%m%d` @@ -135,7 +135,7 @@ systemctl restart crond ``` - + ```bash rm -f /etc/cron.d/centreon @@ -144,7 +144,7 @@ rm -f /etc/cron.d/centreon-auto-disco systemctl restart crond ``` - + ```bash rm -f /etc/cron.d/centreon diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md index fa757b380ec4..351537c75d55 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md @@ -28,21 +28,21 @@ Si vous utilisez un fournisseur Open Ticket avec des configurations personnalis Eliminez les paquets debuginfo avant de poursuivre à moins d'en avoir un besoin spécifique. - + ```shell dnf remove $(rpm -qa --qf "%{NAME}\n" | grep '^centreon.*debuginfo') ``` - + ```shell dnf remove $(rpm -qa --qf "%{NAME}\n" | grep '^centreon.*debuginfo') ``` - + ```shell apt remove $(dpkg -l | awk '/^ii/ && $2 ~ /^centreon.*debuginfo/ { print $2 }') @@ -65,9 +65,9 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v * centreon-modules, if you are using Centreon Business Edition. - + -* bookworm, bookworm-updates, bookworm-backports and bookworm security +* trixie, trixie-updates, trixie-backports and trixie security * centreon * centreon-modules, if you are using Centreon Business Edition. @@ -81,7 +81,7 @@ Avant de réaliser la montée de version de votre plateforme Centreon, assurez-v Assurez-vous que tous les utilisateurs sont déconnectés avant de commencer la procédure de mise à jour. - + Videz le cache : @@ -96,7 +96,7 @@ Mettez à jour l'ensemble des composants : ``` - + Videz le cache : @@ -111,7 +111,7 @@ Mettez à jour l'ensemble des composants : ``` - + Videz le cache : @@ -241,7 +241,7 @@ Cette procédure est identique à la mise à jour d'un serveur Centreon Central. ## Mise à jour des collecteurs - + 1. Videz le cache : @@ -256,7 +256,7 @@ Cette procédure est identique à la mise à jour d'un serveur Centreon Central. ``` - + 1. Videz le cache : @@ -271,7 +271,7 @@ Cette procédure est identique à la mise à jour d'un serveur Centreon Central. ``` - + 1. Videz le cache : @@ -304,17 +304,17 @@ en choisissant la méthode **Redémarrer** pour le processus Engine. 5. Exécutez la commande suivante : - + Rien à faire pour cet OS. - + Rien à faire pour cet OS. - + ```shell apt-mark unhold centreon-plugin* diff --git a/versioned_docs/version-26.10/update/update-centreon-ha.md b/versioned_docs/version-26.10/update/update-centreon-ha.md index 72df8fe91a66..d400616326de 100644 --- a/versioned_docs/version-26.10/update/update-centreon-ha.md +++ b/versioned_docs/version-26.10/update/update-centreon-ha.md @@ -59,7 +59,7 @@ dnf update centreon\* ``` - + Clean the cache : @@ -74,7 +74,7 @@ dnf update centreon\* ``` - + Clean the cache : @@ -104,14 +104,14 @@ mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`da sudo -u apache /usr/share/centreon/bin/console cache:clear ``` - + ```bash mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y%m%d` sudo -u apache /usr/share/centreon/bin/console cache:clear ``` - + ```bash mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y%m%d` @@ -135,7 +135,7 @@ systemctl restart crond ``` - + ```bash rm -f /etc/cron.d/centreon @@ -144,7 +144,7 @@ rm -f /etc/cron.d/centreon-auto-disco systemctl restart crond ``` - + ```bash rm -f /etc/cron.d/centreon diff --git a/versioned_docs/version-26.10/update/update-centreon-platform.md b/versioned_docs/version-26.10/update/update-centreon-platform.md index 9c7729f3105c..96047ca03b5b 100644 --- a/versioned_docs/version-26.10/update/update-centreon-platform.md +++ b/versioned_docs/version-26.10/update/update-centreon-platform.md @@ -27,21 +27,21 @@ If you use Open Ticket providers with custom configurations, [make a backup of t Remove the debuginfo packages before the procedure unless you have a particular use for them. - + ```shell dnf remove $(rpm -qa --qf "%{NAME}\n" | grep '^centreon.*debuginfo') ``` - + ```shell dnf remove $(rpm -qa --qf "%{NAME}\n" | grep '^centreon.*debuginfo') ``` - + ```shell apt remove $(dpkg -l | awk '/^ii/ && $2 ~ /^centreon.*debuginfo/ { print $2 }') @@ -64,9 +64,9 @@ Before upgrading your Centreon platform, make sure the following package reposit * centreon-modules, if you are using Centreon Business Edition. - + -* bookworm, bookworm-updates, bookworm-backports and bookworm security +* trixie, trixie-updates, trixie-backports and trixie security * centreon * centreon-modules, if you are using Centreon Business Edition. @@ -80,7 +80,7 @@ Before upgrading your Centreon platform, make sure the following package reposit Make sure all users are logged out from the Centreon web interface before starting the update procedure. - + Clean the cache: @@ -95,7 +95,7 @@ Then upgrade all the components with the following command: ``` - + Clean the cache: @@ -110,7 +110,7 @@ Then upgrade all the components with the following command: ``` - + Clean the cache: @@ -236,7 +236,7 @@ This procedure is the same as to update a Centreon central server. ## Update the Pollers - + 1. Clean the cache: @@ -251,7 +251,7 @@ This procedure is the same as to update a Centreon central server. ``` - + 1. Clean the cache: @@ -266,7 +266,7 @@ This procedure is the same as to update a Centreon central server. ``` - + 1. Clean the cache: @@ -299,17 +299,17 @@ and choose the **Restart** method for the Engine process. 5. Run the following command: - + Nothing to do for this OS. - + Nothing to do for this OS. - + ```shell apt-mark unhold centreon-plugin* From 85d0ceff49bf711ef5ab894954c4f8c488e28143 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 24 Sep 2026 10:20:50 +0200 Subject: [PATCH 083/179] MON-201334 HA upgrade --- .../upgrade/centreon-ha/upgrade-from-23.04.md | 16 +- .../upgrade/centreon-ha/upgrade-from-23.10.md | 142 +---------------- .../upgrade/centreon-ha/upgrade-from-24-04.md | 142 +---------------- .../upgrade/centreon-ha/upgrade-from-24-10.md | 142 +---------------- .../upgrade/centreon-ha/upgrade-from-25-10.md | 142 +---------------- .../upgrade/centreon-ha/upgrade-from-23.04.md | 20 ++- .../upgrade/centreon-ha/upgrade-from-23.10.md | 144 +---------------- .../upgrade/centreon-ha/upgrade-from-24-04.md | 146 +----------------- .../upgrade/centreon-ha/upgrade-from-24-10.md | 144 +---------------- .../upgrade/centreon-ha/upgrade-from-25-10.md | 142 +---------------- 10 files changed, 32 insertions(+), 1148 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md index 9300abad9dec..15ec54e5e600 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md @@ -1,14 +1,12 @@ --- id: upgrade-centreon-ha-from-23-04 title: Montée de version de Centreon HA depuis Centreon 23.04 -description: "Mettre à niveau un cluster Centreon HA depuis la version 23.04 vers la 25.10" +description: "Mettre à niveau un cluster Centreon HA depuis la version 23.04 vers la 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Ce chapitre décrit comment mettre à niveau votre plate-forme Centreon HA de la version 23.04 vers la version 25.10. - -> Si vous utilisiez Debian 11, vous ne pouvez pas directement monter à la version 25.10. Vous devez [migrer votre platforme vers Debian 12](migrate/migrate-from-debian-to-debian.md) d'abord, puis réinstaller la HA. Contactez votre représentant commercial Centreon pour discuter de toute migration avec la HA. +Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 23.04 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. ## Prérequis @@ -63,7 +61,7 @@ Maintenant, pour effectuer la montée de version: > Pour le **nœud central passif** et **le nœud base de données passif s'il existe**, [suivez la documentation officielle](../../upgrade/upgrade-from-23-04.md) **jusqu'à l'étape "Mettre à jour une configuration Apache personnalisée" incluse. Ensuite, sautez à l'étape "Mettre à jour MariaDB"**. Ne procédez pas aux étapes "Finalisation de la mise à jour" et "Actions post montée de version". - + Uniquement sur les serveurs deux nœuds centraux, restaurer le fichier `/etc/centreon-ha/centreon_central_sync.pm`. @@ -94,7 +92,7 @@ rm -f /etc/cron.d/centreon-ha-mysql puis redémarrer le service cron: - + ```bash systemctl restart crond @@ -176,7 +174,7 @@ rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* - + Commencez par extraire tous les identifiants des contraintes: @@ -227,7 +225,7 @@ pcs constraint colocation add master "centreon" with "ms_mysql-clone" - + Extraire d'abord tous les identifiants de contraintes: @@ -290,7 +288,7 @@ pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" Recréez ensuite la contrainte qui empêche les processus Centreon de s'exécuter sur les nœuds de la base de données et vice-et-versa.: - + ```bash pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md index 79ae2528fe11..5ed8169464d6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md @@ -1,14 +1,12 @@ --- id: upgrade-centreon-ha-from-23-10 title: Montée de version de Centreon HA depuis Centreon 23.10 -description: "Mettre à niveau un cluster Centreon HA depuis la version 23.10 vers la 25.10" +description: "Mettre à niveau un cluster Centreon HA depuis la version 23.10 vers la 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Ce chapitre décrit comment mettre à niveau votre plate-forme Centreon HA de la version 23.10 vers la version 25.10. - -> Si vous utilisiez Debian 11, vous ne pouvez pas directement monter à la version 25.10. Vous devez [migrer votre platforme vers Debian 12](migrate/migrate-from-debian-to-debian.md) d'abord, puis réinstaller la HA. Contactez votre représentant commercial Centreon pour discuter de toute migration avec la HA. +Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 23.04 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. ## Prérequis @@ -63,22 +61,6 @@ Maintenant, pour effectuer la montée de version: > Pour le **nœud central passif** et **le nœud base de données passif s'il existe**, [suivez la documentation officielle](../../upgrade/upgrade-from-23-10.md) **jusqu'à l'étape "Mettre à jour une configuration Apache personnalisée" incluse. Ensuite, sautez à l'étape "Mettre à jour MariaDB"**. Ne procédez pas aux étapes "Finalisation de la mise à jour" et "Actions post montée de version". - - -Uniquement sur les serveurs deux nœuds centraux, restaurer le fichier `/etc/centreon-ha/centreon_central_sync.pm`. - -```bash -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -Sur le **nœud central passif**, déplacez le répertoire **install** pour éviter d'obtenir l'écran "upgrade" dans l'interface en cas de nouvel échange de rôles et rechargez le cache Apache. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - - Uniquement sur les serveurs deux nœuds centraux, restaurer le fichier `/etc/centreon-ha/centreon_central_sync.pm`. @@ -110,13 +92,6 @@ rm -f /etc/cron.d/centreon-ha-mysql puis redémarrer le service cron: - - -```bash -systemctl restart crond -``` - - ```bash @@ -199,51 +174,6 @@ rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* - - -Commencez par extraire tous les identifiants des contraintes: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -Vous devriez obtenir un résultat similaire: - -```text -colocation-ms_mysql-clone-centreon-INFINITY -colocation-centreon-ms_mysql-clone-INFINITY -``` - -et supprimer **toutes** les contraintes, **adapter les ID avec les vôtres** - -```bash -pcs constraint delete colocation-ms_mysql-clone-centreon-INFINITY -pcs constraint delete colocation-centreon-ms_mysql-clone-INFINITY -``` - -Vérifier que toutes les contraintes ont bien été supprimées: - -```bash -pcs constraint -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -Si c'est le cas, recréez uniquement les contraintes nécessaires. - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - Commencez par extraire tous les identifiants des contraintes: @@ -296,64 +226,6 @@ pcs constraint colocation add master "centreon" with "ms_mysql-clone" - - -Extraire d'abord tous les identifiants de contraintes: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -Vous devriez obtenir un résultat similaire en fonction de vos noms d'hôtes : - -```text -location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -location-centreon-cc-ha-bdd2-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web1-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web2-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd2-2210-alma8--INFINITY -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-vip_mysql-INFINITY -colocation-centreon-vip-INFINITY -``` - -et supprimer **toutes** les contraintes, **adapter les ids avec les vôtres** - -```bash -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -pcs constraint delete location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -... -``` - -Vérifier que toutes les contraintes sont bien supprimées: - -```bash -pcs constraint -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -Si c'est le cas, recréez uniquement les contraintes nécessaires. - -Afin de coller le rôle de base de données primaire avec l'IP virtuelle, définissez une contrainte mutuelle: - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - Extraire d'abord tous les identifiants de contraintes: @@ -417,16 +289,6 @@ pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" Recréez ensuite la contrainte qui empêche les processus Centreon de s'exécuter sur les nœuds de la base de données et vice-et-versa.: - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - ```bash diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md index a983ec98e15e..697ccfc8883a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md @@ -1,14 +1,12 @@ --- id: upgrade-centreon-ha-from-24-04 title: Montée de version de Centreon HA depuis Centreon 24.04 -description: "Mettre à niveau un cluster Centreon HA depuis la version 24.04 vers la 25.10" +description: "Mettre à niveau un cluster Centreon HA depuis la version 24.04 vers la 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Ce chapitre décrit comment mettre à niveau votre plate-forme Centreon HA de la version 24.04 vers la version 25.10. - -> Si vous utilisiez Debian 11, vous ne pouvez pas directement monter à la version 25.10. Vous devez [migrer votre platforme vers Debian 12](migrate/migrate-from-debian-to-debian.md) d'abord, puis réinstaller la HA. Contactez votre représentant commercial Centreon pour discuter de toute migration avec la HA. +Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 23.04 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. ## Prérequis @@ -63,22 +61,6 @@ Maintenant, pour effectuer la montée de version: > Pour le **nœud central passif** et **le nœud base de données passif s'il existe**, [suivez la documentation officielle](../../upgrade/upgrade-from-24-04.md) **jusqu'à l'étape "Mettre à jour une configuration Apache personnalisée" incluse. Ensuite, sautez à l'étape "Mettre à jour MariaDB"**. Ne procédez pas aux étapes "Finalisation de la mise à jour" et "Actions post montée de version". - - -Uniquement sur les serveurs deux nœuds centraux, restaurer le fichier `/etc/centreon-ha/centreon_central_sync.pm`. - -```bash -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -Sur le **nœud central passif**, déplacez le répertoire **install** pour éviter d'obtenir l'écran "upgrade" dans l'interface en cas de nouvel échange de rôles et rechargez le cache Apache. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - - Uniquement sur les serveurs deux nœuds centraux, restaurer le fichier `/etc/centreon-ha/centreon_central_sync.pm`. @@ -110,13 +92,6 @@ rm -f /etc/cron.d/centreon-ha-mysql puis redémarrer le service cron: - - -```bash -systemctl restart crond -``` - - ```bash @@ -199,51 +174,6 @@ rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* - - -Commencez par extraire tous les identifiants des contraintes: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -Vous devriez obtenir un résultat similaire: - -```text -colocation-ms_mysql-clone-centreon-INFINITY -colocation-centreon-ms_mysql-clone-INFINITY -``` - -et supprimer **toutes** les contraintes, **adapter les ID avec les vôtres** - -```bash -pcs constraint delete colocation-ms_mysql-clone-centreon-INFINITY -pcs constraint delete colocation-centreon-ms_mysql-clone-INFINITY -``` - -Vérifier que toutes les contraintes ont bien été supprimées: - -```bash -pcs constraint -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -Si c'est le cas, recréez uniquement les contraintes nécessaires. - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - Commencez par extraire tous les identifiants des contraintes: @@ -296,64 +226,6 @@ pcs constraint colocation add master "centreon" with "ms_mysql-clone" - - -Extraire d'abord tous les identifiants de contraintes: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -Vous devriez obtenir un résultat similaire en fonction de vos noms d'hôtes : - -```text -location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -location-centreon-cc-ha-bdd2-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web1-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web2-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd2-2210-alma8--INFINITY -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-vip_mysql-INFINITY -colocation-centreon-vip-INFINITY -``` - -et supprimer **toutes** les contraintes, **adapter les ids avec les vôtres** - -```bash -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -pcs constraint delete location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -... -``` - -Vérifier que toutes les contraintes sont bien supprimées: - -```bash -pcs constraint -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -Si c'est le cas, recréez uniquement les contraintes nécessaires. - -Afin de coller le rôle de base de données primaire avec l'IP virtuelle, définissez une contrainte mutuelle: - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - Extraire d'abord tous les identifiants de contraintes: @@ -417,16 +289,6 @@ pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" Recréez ensuite la contrainte qui empêche les processus Centreon de s'exécuter sur les nœuds de la base de données et vice-et-versa.: - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - ```bash diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md index eba0244a3ca2..c9b22c9cd28e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md @@ -1,14 +1,12 @@ --- id: upgrade-centreon-ha-from-24-10 title: Montée de version de Centreon HA depuis Centreon 24.10 -description: "Mettre à niveau un cluster Centreon HA depuis la version 24.10 vers la 25.10" +description: "Mettre à niveau un cluster Centreon HA depuis la version 24.10 vers la 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Ce chapitre décrit comment mettre à niveau votre plate-forme Centreon HA de la version 24.04 vers la version 25.10. - -> Si vous envisagez également de migrer votre plateforme vers un autre système d’exploitation, contactez votre représentant commercial Centreon pour en discuter. +Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 23.04 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. ## Prérequis @@ -63,22 +61,6 @@ Maintenant, pour effectuer la montée de version: > Pour le **nœud central passif** et **le nœud base de données passif s'il existe**, [suivez la documentation officielle](../../upgrade/upgrade-from-24-10.md) **jusqu'à l'étape "Mettre à jour une configuration Apache personnalisée" incluse. Ensuite, sautez à l'étape "Mettre à jour MariaDB"**. Ne procédez pas aux étapes "Finalisation de la mise à jour" et "Actions post montée de version". - - -Uniquement sur les serveurs deux nœuds centraux, restaurer le fichier `/etc/centreon-ha/centreon_central_sync.pm`. - -```bash -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -Sur le **nœud central passif**, déplacez le répertoire **install** pour éviter d'obtenir l'écran "upgrade" dans l'interface en cas de nouvel échange de rôles et rechargez le cache Apache. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - - Uniquement sur les serveurs deux nœuds centraux, restaurer le fichier `/etc/centreon-ha/centreon_central_sync.pm`. @@ -110,13 +92,6 @@ rm -f /etc/cron.d/centreon-ha-mysql puis redémarrer le service cron: - - -```bash -systemctl restart crond -``` - - ```bash @@ -199,51 +174,6 @@ rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* - - -Commencez par extraire tous les identifiants des contraintes: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -Vous devriez obtenir un résultat similaire: - -```text -colocation-ms_mysql-clone-centreon-INFINITY -colocation-centreon-ms_mysql-clone-INFINITY -``` - -et supprimer **toutes** les contraintes, **adapter les ID avec les vôtres** - -```bash -pcs constraint delete colocation-ms_mysql-clone-centreon-INFINITY -pcs constraint delete colocation-centreon-ms_mysql-clone-INFINITY -``` - -Vérifier que toutes les contraintes ont bien été supprimées: - -```bash -pcs constraint -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -Si c'est le cas, recréez uniquement les contraintes nécessaires. - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - Commencez par extraire tous les identifiants des contraintes: @@ -296,64 +226,6 @@ pcs constraint colocation add master "centreon" with "ms_mysql-clone" - - -Extraire d'abord tous les identifiants de contraintes: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -Vous devriez obtenir un résultat similaire en fonction de vos noms d'hôtes : - -```text -location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -location-centreon-cc-ha-bdd2-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web1-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web2-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd2-2210-alma8--INFINITY -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-vip_mysql-INFINITY -colocation-centreon-vip-INFINITY -``` - -et supprimer **toutes** les contraintes, **adapter les ids avec les vôtres** - -```bash -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -pcs constraint delete location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -... -``` - -Vérifier que toutes les contraintes sont bien supprimées: - -```bash -pcs constraint -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -Si c'est le cas, recréez uniquement les contraintes nécessaires. - -Afin de coller le rôle de base de données primaire avec l'IP virtuelle, définissez une contrainte mutuelle: - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - Extraire d'abord tous les identifiants de contraintes: @@ -417,16 +289,6 @@ pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" Recréez ensuite la contrainte qui empêche les processus Centreon de s'exécuter sur les nœuds de la base de données et vice-et-versa.: - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - ```bash diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md index aae4f6a0db30..4f3664d6a18b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md @@ -1,13 +1,11 @@ --- id: upgrade-centreon-ha-from-25-10 -title: Montée de version de Centreon HA depuis Centreon 25.10 +title: Montée de version de Centreon HA depuis Centreon 26.10 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Ce chapitre décrit comment mettre à niveau votre plate-forme Centreon HA de la version 25.10 vers la version 26.10. - -> Si vous envisagez également de migrer votre plateforme vers un autre système d’exploitation, contactez votre représentant commercial Centreon pour en discuter. +Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 23.04 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. ## Prérequis @@ -62,22 +60,6 @@ Maintenant, pour effectuer la montée de version: > Pour le **nœud central passif** et **le nœud base de données passif s'il existe**, [suivez la documentation officielle](../../upgrade/upgrade-from-24-10.md) **jusqu'à l'étape "Mettre à jour une configuration Apache personnalisée" incluse. Ensuite, sautez à l'étape "Mettre à jour MariaDB"**. Ne procédez pas aux étapes "Finalisation de la mise à jour" et "Actions post montée de version". - - -Uniquement sur les serveurs deux nœuds centraux, restaurer le fichier `/etc/centreon-ha/centreon_central_sync.pm`. - -```bash -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -Sur le **nœud central passif**, déplacez le répertoire **install** pour éviter d'obtenir l'écran "upgrade" dans l'interface en cas de nouvel échange de rôles et rechargez le cache Apache. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - - Uniquement sur les serveurs deux nœuds centraux, restaurer le fichier `/etc/centreon-ha/centreon_central_sync.pm`. @@ -109,13 +91,6 @@ rm -f /etc/cron.d/centreon-ha-mysql puis redémarrer le service cron: - - -```bash -systemctl restart crond -``` - - ```bash @@ -198,51 +173,6 @@ rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* - - -Commencez par extraire tous les identifiants des contraintes: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -Vous devriez obtenir un résultat similaire: - -```text -colocation-ms_mysql-clone-centreon-INFINITY -colocation-centreon-ms_mysql-clone-INFINITY -``` - -et supprimer **toutes** les contraintes, **adapter les ID avec les vôtres** - -```bash -pcs constraint delete colocation-ms_mysql-clone-centreon-INFINITY -pcs constraint delete colocation-centreon-ms_mysql-clone-INFINITY -``` - -Vérifier que toutes les contraintes ont bien été supprimées: - -```bash -pcs constraint -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -Si c'est le cas, recréez uniquement les contraintes nécessaires. - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - Commencez par extraire tous les identifiants des contraintes: @@ -295,64 +225,6 @@ pcs constraint colocation add master "centreon" with "ms_mysql-clone" - - -Extraire d'abord tous les identifiants de contraintes: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -Vous devriez obtenir un résultat similaire en fonction de vos noms d'hôtes : - -```text -location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -location-centreon-cc-ha-bdd2-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web1-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web2-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd2-2210-alma8--INFINITY -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-vip_mysql-INFINITY -colocation-centreon-vip-INFINITY -``` - -et supprimer **toutes** les contraintes, **adapter les ids avec les vôtres** - -```bash -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -pcs constraint delete location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -... -``` - -Vérifier que toutes les contraintes sont bien supprimées: - -```bash -pcs constraint -``` - -Vous devriez obtenir un résultat comme celui-ci: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -Si c'est le cas, recréez uniquement les contraintes nécessaires. - -Afin de coller le rôle de base de données primaire avec l'IP virtuelle, définissez une contrainte mutuelle: - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - Extraire d'abord tous les identifiants de contraintes: @@ -416,16 +288,6 @@ pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" Recréez ensuite la contrainte qui empêche les processus Centreon de s'exécuter sur les nœuds de la base de données et vice-et-versa.: - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - ```bash diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md index d19714c8795c..6f447a8a2b34 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md @@ -1,14 +1,12 @@ --- id: upgrade-centreon-ha-from-23-04 title: Upgrade Centreon HA from Centreon 23.04 -description: "Upgrade a Centreon HA cluster from version 23.04 to 25.10" +description: "Upgrade a Centreon HA cluster from version 23.04 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This chapter describes how to upgrade your Centreon HA platform from version 23.04 to version 25.10. - -> If you were using Debian 11, you cannot upgrade your platform directly to version 25.10. You need to [migrate your platform to Debian 12](migrate/migrate-from-debian-to-debian.md) first, then reinstall HA. Contact your Centreon sales representative to discuss any migration with HA. +This chapter describes how to upgrade your Centreon HA platform from version 23.04 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. ## Prerequisites @@ -63,7 +61,7 @@ Now, to perform the upgrade: > For the **passive central node** and **passive database node if needed**, please [follow the official documentation](../../upgrade/upgrade-from-23-04.md) **until the "Update your customized Apache configuration" step included**. Then, skip to the "Upgrade MariaDB" step and follow its instructions. **Do not follow "Finalizing the upgrade" and "Post-upgrade actions"**. - + Then on the **two central nodes**, restore the file `/etc/centreon-ha/centreon_central_sync.pm`: @@ -94,7 +92,7 @@ rm -f /etc/cron.d/centreon-ha-mysql and restart the cron daemon: - + ```bash systemctl restart crond @@ -176,9 +174,9 @@ rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* - + -First extract all contraint IDs: +First extract all constraint IDs: ```bash pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' @@ -227,9 +225,9 @@ pcs constraint colocation add master "centreon" with "ms_mysql-clone" - + -First extract all contraint IDs: +First extract all constraint IDs: ```bash pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' @@ -290,7 +288,7 @@ pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" Then recreate the Constraint that prevent Centreon Processes to run on Database nodes and vice-et-versa: - + ```bash pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md index 8144a2c24007..7b9762e98dd9 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md @@ -1,14 +1,12 @@ --- id: upgrade-centreon-ha-from-23-10 title: Upgrade Centreon HA from Centreon 23.10 -description: "Upgrade a Centreon HA cluster from version 23.10 to 25.10" +description: "Upgrade a Centreon HA cluster from version 23.10 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This chapter describes how to upgrade your Centreon HA platform from version 23.10 to version 25.10. - -> If you were using Debian 11, you cannot upgrade your platform directly to version 25.10. You need to [migrate your platform to Debian 12](migrate/migrate-from-debian-to-debian.md) first, then reinstall HA. Contact your Centreon sales representative to discuss any migration with HA. +This chapter describes how to upgrade your Centreon HA platform from version 23.04 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. ## Prerequisites @@ -63,22 +61,6 @@ Now, to perform the upgrade: > For the **passive central node** and **passive database node if needed**, please [follow the official documentation](../../upgrade/upgrade-from-23-10.md) **until the "Update your customized Apache configuration" step included**. Then, skip to the "Upgrade MariaDB" step and follow its instructions. **Do not follow "Finalizing the upgrade" and "Post-upgrade actions"**. - - -Then on the **two central nodes**, restore the file `/etc/centreon-ha/centreon_central_sync.pm`: - -```shell -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -On the **passive central node**, move the "install" directory to avoid getting the "upgrade" screen in the interface in the event of a further exchange of roles. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - - Then on the **two central nodes**, restore the file `/etc/centreon-ha/centreon_central_sync.pm`: @@ -110,13 +92,6 @@ rm -f /etc/cron.d/centreon-ha-mysql and restart the cron daemon: - - -```bash -systemctl restart crond -``` - - ```bash @@ -199,53 +174,6 @@ rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* - - -First extract all contraint IDs: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -You should have a similar result: - -```text -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-centreon-INFINITY -colocation-centreon-ms_mysql-clone-INFINITY -``` - -and delete **all** constraints, **adapt IDs with your own** - -```bash -pcs constraint delete order-centreon-ms_mysql-clone-mandatory -pcs constraint delete colocation-ms_mysql-clone-centreon-INFINITY -pcs constraint delete colocation-centreon-ms_mysql-clone-INFINITY -``` - -Verify if all constraint are well deleted: - -```bash -pcs constraint -``` - -You should have a result like this: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -If it's OK, then recreate only needed constraints - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - First extract all contraint IDs: @@ -298,64 +226,6 @@ pcs constraint colocation add master "centreon" with "ms_mysql-clone" - - -First extract all contraint IDs: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -You should have a similar result depending of your host names: - -```text -location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -location-centreon-cc-ha-bdd2-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web1-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web2-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd2-2210-alma8--INFINITY -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-vip_mysql-INFINITY -colocation-centreon-vip-INFINITY -``` - -and delete **all** constraints, **adapt IDs with your own** - -```bash -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -pcs constraint delete location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -... -``` - -Verify if all constraint are well deleted: - -```bash -pcs constraint -``` - -You should have a result like this: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -If it's OK, then recreate only needed constraints. - -In order to glue the Primary Database role with the Virtual IP, define a mutual Constraint: - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - First extract all contraint IDs: @@ -419,16 +289,6 @@ pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" Then recreate the Constraint that prevent Centreon Processes to run on Database nodes and vice-et-versa: - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - ```bash diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md index a11a2b14b6bf..ee70fd296013 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md @@ -1,14 +1,12 @@ --- id: upgrade-centreon-ha-from-24-04 title: Upgrade Centreon HA from Centreon 24.04 -description: "Upgrade a Centreon HA cluster from version 24.04 to 25.10" +description: "Upgrade a Centreon HA cluster from version 24.04 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This chapter describes how to upgrade your Centreon HA platform from version 24.04 to version 25.10. - -> If you were using Debian 11, you cannot upgrade your platform directly to version 25.10. You need to [migrate your platform to Debian 12](migrate/migrate-from-debian-to-debian.md) first, then reinstall HA. Contact your Centreon sales representative to discuss any migration with HA. +This chapter describes how to upgrade your Centreon HA platform from version 24.04 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. ## Prerequisites @@ -63,22 +61,6 @@ Now, to perform the upgrade: > For the **passive central node** and **passive database node if needed**, please [follow the official documentation](../../upgrade/upgrade-from-24-04.md) **until the "Update your customized Apache configuration" step included**. Then, skip to the "Upgrade MariaDB" step and follow its instructions. **Do not follow "Finalizing the upgrade" and "Post-upgrade actions"**. - - -Then on the **two central nodes**, restore the file `/etc/centreon-ha/centreon_central_sync.pm`: - -```shell -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -On the **passive central node**, move the "install" directory to avoid getting the "upgrade" screen in the interface in the event of a further exchange of roles. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - - Then on the **two central nodes**, restore the file `/etc/centreon-ha/centreon_central_sync.pm`: @@ -99,7 +81,7 @@ sudo -u apache /usr/share/centreon/bin/console cache:clear ### Removing cron jobs -The RPM upgrade puts cron jobs back in place on the central and databases servers. Remove them to avoid concurrent executions on central and database nodes: +The RPM upgrade puts cron jobs back in place on the central and databases servers. Remove them to avoid concurrent executions on central and database nodes: ```bash rm -f /etc/cron.d/centreon @@ -110,13 +92,6 @@ rm -f /etc/cron.d/centreon-ha-mysql and restart the cron daemon: - - -```bash -systemctl restart crond -``` - - ```bash @@ -199,53 +174,6 @@ rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* - - -First extract all contraint IDs: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -You should have a similar result: - -```text -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-centreon-INFINITY -colocation-centreon-ms_mysql-clone-INFINITY -``` - -and delete **all** constraints, **adapt IDs with your own** - -```bash -pcs constraint delete order-centreon-ms_mysql-clone-mandatory -pcs constraint delete colocation-ms_mysql-clone-centreon-INFINITY -pcs constraint delete colocation-centreon-ms_mysql-clone-INFINITY -``` - -Verify if all constraint are well deleted: - -```bash -pcs constraint -``` - -You should have a result like this: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -If it's OK, then recreate only needed constraints - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - First extract all contraint IDs: @@ -298,64 +226,6 @@ pcs constraint colocation add master "centreon" with "ms_mysql-clone" - - -First extract all contraint IDs: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -You should have a similar result depending of your host names: - -```text -location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -location-centreon-cc-ha-bdd2-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web1-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web2-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd2-2210-alma8--INFINITY -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-vip_mysql-INFINITY -colocation-centreon-vip-INFINITY -``` - -and delete **all** constraints, **adapt IDs with your own** - -```bash -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -pcs constraint delete location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -... -``` - -Verify if all constraint are well deleted: - -```bash -pcs constraint -``` - -You should have a result like this: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -If it's OK, then recreate only needed constraints. - -In order to glue the Primary Database role with the Virtual IP, define a mutual Constraint: - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - First extract all contraint IDs: @@ -419,16 +289,6 @@ pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" Then recreate the Constraint that prevent Centreon Processes to run on Database nodes and vice-et-versa: - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - ```bash diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md index 924e1bdd1d30..96125e022b0e 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md @@ -1,14 +1,12 @@ --- id: upgrade-centreon-ha-from-24-10 title: Upgrade Centreon HA from Centreon 24.10 -description: "Upgrade a Centreon HA cluster from version 24.10 to 25.10" +description: "Upgrade a Centreon HA cluster from version 24.10 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This chapter describes how to upgrade your Centreon HA platform from version 24.10 to version 25.10. - -> If you were considering migrating your platform to another OS too, contact your Centreon sales representative to discuss this. +This chapter describes how to upgrade your Centreon HA platform from version 24.04 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. ## Prerequisites @@ -63,22 +61,6 @@ Now, to perform the upgrade: > For the **passive central node** and **passive database node if needed**, please [follow the official documentation](../../upgrade/upgrade-from-24-10.md) **until the "Update your customized Apache configuration" step included**. Then, skip to the "Upgrade MariaDB" step and follow its instructions. **Do not follow "Finalizing the upgrade" and "Post-upgrade actions"**. - - -Then on the **two central nodes**, restore the file `/etc/centreon-ha/centreon_central_sync.pm`: - -```shell -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -On the **passive central node**, move the "install" directory to avoid getting the "upgrade" screen in the interface in the event of a further exchange of roles. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - - Then on the **two central nodes**, restore the file `/etc/centreon-ha/centreon_central_sync.pm`: @@ -110,13 +92,6 @@ rm -f /etc/cron.d/centreon-ha-mysql and restart the cron daemon: - - -```bash -systemctl restart crond -``` - - ```bash @@ -199,53 +174,6 @@ rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* - - -First extract all contraint IDs: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -You should have a similar result: - -```text -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-centreon-INFINITY -colocation-centreon-ms_mysql-clone-INFINITY -``` - -and delete **all** constraints, **adapt IDs with your own** - -```bash -pcs constraint delete order-centreon-ms_mysql-clone-mandatory -pcs constraint delete colocation-ms_mysql-clone-centreon-INFINITY -pcs constraint delete colocation-centreon-ms_mysql-clone-INFINITY -``` - -Verify if all constraint are well deleted: - -```bash -pcs constraint -``` - -You should have a result like this: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -If it's OK, then recreate only needed constraints - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - First extract all contraint IDs: @@ -298,64 +226,6 @@ pcs constraint colocation add master "centreon" with "ms_mysql-clone" - - -First extract all contraint IDs: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -You should have a similar result depending of your host names: - -```text -location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -location-centreon-cc-ha-bdd2-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web1-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web2-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd2-2210-alma8--INFINITY -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-vip_mysql-INFINITY -colocation-centreon-vip-INFINITY -``` - -and delete **all** constraints, **adapt IDs with your own** - -```bash -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -pcs constraint delete location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -... -``` - -Verify if all constraint are well deleted: - -```bash -pcs constraint -``` - -You should have a result like this: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -If it's OK, then recreate only needed constraints. - -In order to glue the Primary Database role with the Virtual IP, define a mutual Constraint: - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - First extract all contraint IDs: @@ -419,16 +289,6 @@ pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" Then recreate the Constraint that prevent Centreon Processes to run on Database nodes and vice-et-versa: - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - ```bash diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md index b2b5c81f49e5..f08f0ef326d0 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md @@ -6,9 +6,7 @@ description: "Upgrade a Centreon HA cluster from version 25.10 to 26.10" import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This chapter describes how to upgrade your Centreon HA platform from version 25.10 to version 26.10. - -> If you were considering migrating your platform to another OS too, contact your Centreon sales representative to discuss this. +This chapter describes how to upgrade your Centreon HA platform from version 24.04 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. ## Prerequisites @@ -63,22 +61,6 @@ Now, to perform the upgrade: > For the **passive central node** and **passive database node if needed**, please [follow the official documentation](https://docs.centreon.com/docs/upgrade/upgrade-from-25-10.md) **until the "Update your customized Apache configuration" step included**. Then, skip to the "Upgrade MariaDB" step and follow its instructions. **Do not follow "Finalizing the upgrade" and "Post-upgrade actions"**. - - -Then on the **two central nodes**, restore the file `/etc/centreon-ha/centreon_central_sync.pm`: - -```shell -mv /etc/centreon-ha/centreon_central_sync.pm.rpmsave /etc/centreon-ha/centreon_central_sync.pm -``` - -On the **passive central node**, move the "install" directory to avoid getting the "upgrade" screen in the interface in the event of a further exchange of roles. - -```bash -mv /usr/share/centreon/www/install /var/lib/centreon/installs/install-update-`date +%Y-%m-%d` -sudo -u apache /usr/share/centreon/bin/console cache:clear -``` - - Then on the **two central nodes**, restore the file `/etc/centreon-ha/centreon_central_sync.pm`: @@ -110,13 +92,6 @@ rm -f /etc/cron.d/centreon-ha-mysql and restart the cron daemon: - - -```bash -systemctl restart crond -``` - - ```bash @@ -199,53 +174,6 @@ rm -f /var/lib/centreon-broker/central-broker-master.unprocessed* - - -First extract all contraint IDs: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -You should have a similar result: - -```text -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-centreon-INFINITY -colocation-centreon-ms_mysql-clone-INFINITY -``` - -and delete **all** constraints, **adapt IDs with your own** - -```bash -pcs constraint delete order-centreon-ms_mysql-clone-mandatory -pcs constraint delete colocation-ms_mysql-clone-centreon-INFINITY -pcs constraint delete colocation-centreon-ms_mysql-clone-INFINITY -``` - -Verify if all constraint are well deleted: - -```bash -pcs constraint -``` - -You should have a result like this: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -If it's OK, then recreate only needed constraints - -```bash -pcs constraint colocation add master "ms_mysql-clone" with "centreon" -pcs constraint colocation add master "centreon" with "ms_mysql-clone" -``` - - First extract all contraint IDs: @@ -298,64 +226,6 @@ pcs constraint colocation add master "centreon" with "ms_mysql-clone" - - -First extract all contraint IDs: - -```bash -pcs constraint config --full | grep "id:" | awk -F "id:" '{print $2}' | sed 's/.$//' -``` - -You should have a similar result depending of your host names: - -```text -location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -location-centreon-cc-ha-bdd2-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web1-2210-alma8--INFINITY -location-ms_mysql-clone-cc-ha-web2-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd1-2210-alma8--INFINITY -location-php-clone-cc-ha-bdd2-2210-alma8--INFINITY -order-centreon-ms_mysql-clone-mandatory -colocation-ms_mysql-clone-vip_mysql-INFINITY -colocation-centreon-vip-INFINITY -``` - -and delete **all** constraints, **adapt IDs with your own** - -```bash -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd1-2210-alma8--INFINITY -pcs constraint delete location-cbd_rrd-clone-cc-ha-bdd2-2210-alma8--INFINITY -pcs constraint delete location-centreon-cc-ha-bdd1-2210-alma8--INFINITY -... -``` - -Verify if all constraint are well deleted: - -```bash -pcs constraint -``` - -You should have a result like this: - -```text -Location Constraints: -Ordering Constraints: -Colocation Constraints: -Ticket Constraints: -``` - -If it's OK, then recreate only needed constraints. - -In order to glue the Primary Database role with the Virtual IP, define a mutual Constraint: - -```bash -pcs constraint colocation add "vip_mysql" with master "ms_mysql-clone" -pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" -``` - - First extract all contraint IDs: @@ -419,16 +289,6 @@ pcs constraint colocation add master "ms_mysql-clone" with "vip_mysql" Then recreate the Constraint that prevent Centreon Processes to run on Database nodes and vice-et-versa: - - -```bash -pcs constraint location centreon avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location ms_mysql-clone avoids @CENTRAL_MASTER_NAME@=INFINITY @CENTRAL_SLAVE_NAME@=INFINITY -pcs constraint location cbd_rrd-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -pcs constraint location php-clone avoids @DATABASE_MASTER_NAME@=INFINITY @DATABASE_SLAVE_NAME@=INFINITY -``` - - ```bash From 99a940c5b25e11a7ff26324f21c267011061fef3 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 24 Sep 2026 14:29:21 +0200 Subject: [PATCH 084/179] Update tabs with supported OSs --- .../version-26.10/administration/custom-login.md | 6 +++--- .../alerts-notifications/notif-config-for-teams.md | 6 +++--- .../alerts-notifications/ticketing-install.md | 6 +++--- .../developer/developer-gorgone-rebound-mode.md | 12 ++++++------ .../version-26.10/installation/technical.md | 6 +++--- .../version-26.10/administration/custom-login.md | 6 +++--- .../alerts-notifications/notif-config-for-teams.md | 6 +++--- .../alerts-notifications/ticketing-install.md | 6 +++--- .../developer/developer-gorgone-rebound-mode.md | 12 ++++++------ .../version-26.10/installation/technical.md | 7 ++++--- 10 files changed, 37 insertions(+), 36 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/custom-login.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/custom-login.md index 52af7e8b0d55..62af537f945a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/custom-login.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/custom-login.md @@ -33,21 +33,21 @@ La personnalisation de votre plateforme Centreon utilise l'extension **Centreon Exécutez la commande suivante pour mettre à jour l'extension : - + ``` shell dnf update centreon-it-edition-extensions ``` - + ``` shell dnf update centreon-it-edition-extensions ``` - + ```shell apt update && apt install --only-upgrade centreon-it-edition-extensions diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/alerts-notifications/notif-config-for-teams.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/alerts-notifications/notif-config-for-teams.md index 7fe09e6ad7b1..ade6e16d14c2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/alerts-notifications/notif-config-for-teams.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/alerts-notifications/notif-config-for-teams.md @@ -42,21 +42,21 @@ Vous devez installer le plugin de notification Teams avec le gestionnaire de paq - Entrez la commande suivante : - + ``` shell dnf install centreon-plugin-Notification-Teams ``` - + ``` shell dnf install centreon-plugin-Notification-Teams ``` - + ``` shell apt install centreon-plugin-notification-teams diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/alerts-notifications/ticketing-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/alerts-notifications/ticketing-install.md index 5f5a1bae80c8..5ed41d9508ec 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/alerts-notifications/ticketing-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/alerts-notifications/ticketing-install.md @@ -25,21 +25,21 @@ création de ceux-ci. Exécutez la commande suivante : - + ``` shell dnf install centreon-open-tickets ``` - + ``` shell dnf install centreon-open-tickets ``` - + ``` shell apt install centreon-open-tickets diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-gorgone-rebound-mode.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-gorgone-rebound-mode.md index c923f691718f..45a2f8ed3237 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-gorgone-rebound-mode.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/developer/developer-gorgone-rebound-mode.md @@ -72,30 +72,30 @@ Assurez-vous d'avoir un [OS supporté](../installation/compatibility.md#système Installez le démon Gorgone en utilisant les commandes suivantes : - - + ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update dnf install centreon-gorgone ``` - + ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo dnf clean all --enablerepo=* dnf update dnf install centreon-gorgone ``` - + + Pour installer le dépôt Centreon, exécutez la commande suivante : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/technical.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/technical.md index 9f6719ac3a65..c2e7f646645c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/technical.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/technical.md @@ -91,7 +91,7 @@ import TabItem from '@theme/TabItem'; Description des logiciels et utilisateurs liés : - + | Logiciel | Service | Utilisateur | Commentaire | | ----------------- | ---------------- | ---------------- | --------------- | @@ -105,7 +105,7 @@ Description des logiciels et utilisateurs liés : | Centreon Gorgone | gorgoned | centreon-gorgone | automatic start | - + | Logiciel | Service | Utilisateur | Commentaire | | ----------------- | ---------------- | ---------------- | --------------- | @@ -119,7 +119,7 @@ Description des logiciels et utilisateurs liés : | Centreon Gorgone | gorgoned | centreon-gorgone | automatic start | - + | Software | Service | User | Comment | | ----------------- | ---------------- | ---------------- | --------------- | diff --git a/versioned_docs/version-26.10/administration/custom-login.md b/versioned_docs/version-26.10/administration/custom-login.md index 513eae5b5600..a4e4f070542e 100644 --- a/versioned_docs/version-26.10/administration/custom-login.md +++ b/versioned_docs/version-26.10/administration/custom-login.md @@ -33,21 +33,21 @@ Customizing your Centreon platform required the **Centreon IT Edition Extensions Execute the following command to update the extension: - + ``` shell dnf update centreon-it-edition-extensions ``` - + ``` shell dnf update centreon-it-edition-extensions ``` - + ```shell apt update && apt install --only-upgrade centreon-it-edition-extensions diff --git a/versioned_docs/version-26.10/alerts-notifications/notif-config-for-teams.md b/versioned_docs/version-26.10/alerts-notifications/notif-config-for-teams.md index 02e076a0cd9b..4cc28d6a84dd 100644 --- a/versioned_docs/version-26.10/alerts-notifications/notif-config-for-teams.md +++ b/versioned_docs/version-26.10/alerts-notifications/notif-config-for-teams.md @@ -42,21 +42,21 @@ You need to Install the Teams notification plugin with the package manager on ea - Enter the following command: - + ``` shell dnf install centreon-plugin-Notification-Teams ``` - + ``` shell dnf install centreon-plugin-Notification-Teams ``` - + ``` shell apt install centreon-plugin-notification-teams diff --git a/versioned_docs/version-26.10/alerts-notifications/ticketing-install.md b/versioned_docs/version-26.10/alerts-notifications/ticketing-install.md index 42ff3097191d..2aa40666f0f6 100644 --- a/versioned_docs/version-26.10/alerts-notifications/ticketing-install.md +++ b/versioned_docs/version-26.10/alerts-notifications/ticketing-install.md @@ -24,21 +24,21 @@ tickets by giving the ID and creation date of the tickets. Execute the following command: - + ``` shell dnf install centreon-open-tickets ``` - + ``` shell dnf install centreon-open-tickets ``` - + ``` shell apt install centreon-open-tickets diff --git a/versioned_docs/version-26.10/developer/developer-gorgone-rebound-mode.md b/versioned_docs/version-26.10/developer/developer-gorgone-rebound-mode.md index 81db813acf3e..3ba20db20583 100644 --- a/versioned_docs/version-26.10/developer/developer-gorgone-rebound-mode.md +++ b/versioned_docs/version-26.10/developer/developer-gorgone-rebound-mode.md @@ -70,30 +70,30 @@ Ensure you have installed a server with a [supported OS](../installation/compati Then install the Gorgone daemon using the following commands: - - + ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el8/centreon-26.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update dnf install centreon-gorgone ``` - + + ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo dnf clean all --enablerepo=* dnf update dnf install centreon-gorgone ``` - + To install the Centreon repository, execute the following command: diff --git a/versioned_docs/version-26.10/installation/technical.md b/versioned_docs/version-26.10/installation/technical.md index e4f44a526a6c..e9e182085e94 100644 --- a/versioned_docs/version-26.10/installation/technical.md +++ b/versioned_docs/version-26.10/installation/technical.md @@ -91,7 +91,7 @@ import TabItem from '@theme/TabItem'; Description of software and linked users: - + | Software | Service | User | Comment | | ----------------- | ---------------- | ---------------- | --------------- | @@ -105,7 +105,7 @@ Description of software and linked users: | Centreon Gorgone | gorgoned | centreon-gorgone | automatic start | - + | Software | Service | User | Comment | | ----------------- | ---------------- | ---------------- | --------------- | @@ -119,7 +119,7 @@ Description of software and linked users: | Centreon Gorgone | gorgoned | centreon-gorgone | automatic start | - + | Software | Service | User | Comment | | ----------------- | ---------------- | ---------------- | --------------- | @@ -131,6 +131,7 @@ Description of software and linked users: | Centreon Broker | cbd | centreon-broker | automatic start | | Centreon Engine | centengine | centreon-engine | automatic start | | Centreon Gorgone | gorgoned | centreon-gorgone | automatic start | + From 932d178070e0c962432796a5c3ab61827d62b6fe Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 24 Sep 2026 14:39:05 +0200 Subject: [PATCH 085/179] Update supported OSs in tabs --- .../version-26.10/getting-started/autodisco-aws.md | 8 ++++---- .../getting-started/monitor-cisco-router-with-snmp.md | 6 +++--- .../getting-started/monitor-linux-server-with-snmp.md | 6 +++--- .../getting-started/monitor-windows-server-with-snmp.md | 7 +++---- .../version-26.10/getting-started/mysql_tuto.md | 7 +++---- .../version-26.10/getting-started/autodisco-aws.md | 6 +++--- .../getting-started/monitor-cisco-router-with-snmp.md | 6 +++--- .../getting-started/monitor-linux-server-with-snmp.md | 6 +++--- .../getting-started/monitor-windows-server-with-snmp.md | 6 +++--- .../version-26.10/getting-started/mysql_tuto.md | 6 +++--- 10 files changed, 31 insertions(+), 33 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/autodisco-aws.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/autodisco-aws.md index 2c4c45f5a4cc..ce7e9c09bb60 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/autodisco-aws.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/autodisco-aws.md @@ -26,23 +26,23 @@ Vous devez disposer : - Si vous avez une licence en ligne, les connecteurs de supervision sont déjà disponibles dans l'interface. - Si vous avez une licence hors ligne, dans le terminal de votre serveur central, entrez : - + - + ``` shell dnf install centreon-pack-* ``` - + ``` shell dnf install centreon-pack-* ``` - + ```shell apt install centreon-pack-* diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/monitor-cisco-router-with-snmp.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/monitor-cisco-router-with-snmp.md index 70d64087a5f0..b43f1bf4c58d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/monitor-cisco-router-with-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/monitor-cisco-router-with-snmp.md @@ -29,21 +29,21 @@ L'équipement doit être accessible depuis le collecteur Centreon sur le port SN Connectez-vous à votre collecteur en SSH et installez le plugin standard Cisco (voir la [procédure de surveillance pour le connecteur de supervision **Cisco standard**](/pp/integrations/plugin-packs/procedures/network-cisco-standard-snmp) pour plus d'informations) : - + ``` shell dnf install centreon-plugin-Network-Cisco-Standard-Snmp ``` - + ``` shell dnf install centreon-plugin-Network-Cisco-Standard-Snmp ``` - + ```shell apt install centreon-plugin-network-cisco-standard-snmp diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/monitor-linux-server-with-snmp.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/monitor-linux-server-with-snmp.md index 3522f4e7b8f7..a54276fa1199 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/monitor-linux-server-with-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/monitor-linux-server-with-snmp.md @@ -63,21 +63,21 @@ systemctl enable snmpd Connectez-vous à votre collecteur en SSH et installez le plugin SNMP Linux (voir la [procédure de surveillance pour le connecteur de supervision **Linux SNMP**](/pp/integrations/plugin-packs/procedures/operatingsystems-linux-snmp) pour plus d'informations) : - + ``` shell dnf install centreon-plugin-Operatingsystems-Linux-Snmp ``` - + ``` shell dnf install centreon-plugin-Operatingsystems-Linux-Snmp ``` - + ```shell apt install centreon-plugin-operatingsystems-linux-snmp diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/monitor-windows-server-with-snmp.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/monitor-windows-server-with-snmp.md index b547fcfd6d69..ab23506f7655 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/monitor-windows-server-with-snmp.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/monitor-windows-server-with-snmp.md @@ -96,28 +96,27 @@ Sélectionnez ensuite **Accepter les paquets SNMP de ces hôtes** et ajoutez l'a Connectez-vous à votre collecteur en SSH et installez le plugin Windows SNMP (voir la [procédure de supervision du connecteur de supervision **Windows SNMP**](/pp/integrations/plugin-packs/procedures/operatingsystems-windows-snmp) pour plus d'informations): - + ``` shell dnf install centreon-plugin-Operatingsystems-Windows-Snmp ``` - + ``` shell dnf install centreon-plugin-Operatingsystems-Windows-Snmp ``` - + ```shell apt install centreon-plugin-operatingsystems-windows-snmp ``` - ### Sur le serveur central diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/mysql_tuto.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/mysql_tuto.md index 3093ad41cd2d..86f6f4f4e66e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/mysql_tuto.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/getting-started/mysql_tuto.md @@ -32,28 +32,27 @@ GRANT SELECT ON *.* TO 'username'@'IP_POLLER'; Installez le plugin suivant sur le collecteur qui supervisera votre base de données : - + ``` shell dnf install centreon-plugin-Applications-Databases-Mysql ``` - + ``` shell dnf install centreon-plugin-Applications-Databases-Mysql ``` - + ```shell apt install centreon-plugin-applications-databases-mysql ``` - ### Sur le serveur central diff --git a/versioned_docs/version-26.10/getting-started/autodisco-aws.md b/versioned_docs/version-26.10/getting-started/autodisco-aws.md index 7d806c2348fc..8cebf32b115e 100644 --- a/versioned_docs/version-26.10/getting-started/autodisco-aws.md +++ b/versioned_docs/version-26.10/getting-started/autodisco-aws.md @@ -28,21 +28,21 @@ You must have: - If you have an offline license in your central server's terminal, enter: - + ``` shell dnf install centreon-pack-* ``` - + ``` shell dnf install centreon-pack-* ``` - + ```shell apt install centreon-pack-* diff --git a/versioned_docs/version-26.10/getting-started/monitor-cisco-router-with-snmp.md b/versioned_docs/version-26.10/getting-started/monitor-cisco-router-with-snmp.md index 4609f0be53ff..bfab758c7049 100644 --- a/versioned_docs/version-26.10/getting-started/monitor-cisco-router-with-snmp.md +++ b/versioned_docs/version-26.10/getting-started/monitor-cisco-router-with-snmp.md @@ -33,21 +33,21 @@ The target device must be reachable from the Centreon Poller on the UDP/161 SNMP Connect to your poller using SSH and install the Cisco standard plugin (see the [monitoring procedure for the **Cisco standard** Monitoring Connector](/pp/integrations/plugin-packs/procedures/network-cisco-standard-snmp) for more information): - + ``` shell dnf install centreon-plugin-Network-Cisco-Standard-Snmp ``` - + ``` shell dnf install centreon-plugin-Network-Cisco-Standard-Snmp ``` - + ```shell apt install centreon-plugin-network-cisco-standard-snmp diff --git a/versioned_docs/version-26.10/getting-started/monitor-linux-server-with-snmp.md b/versioned_docs/version-26.10/getting-started/monitor-linux-server-with-snmp.md index cb9a70174991..87b8489b617c 100644 --- a/versioned_docs/version-26.10/getting-started/monitor-linux-server-with-snmp.md +++ b/versioned_docs/version-26.10/getting-started/monitor-linux-server-with-snmp.md @@ -71,21 +71,21 @@ systemctl enable snmpd Connect to your poller using SSH and install the Linux SNMP plugin (see the [monitoring procedure for the **Linux SNMP** Monitoring Connector](/pp/integrations/plugin-packs/procedures/operatingsystems-linux-snmp) for more information): - + ``` shell dnf install centreon-plugin-Operatingsystems-Linux-Snmp ``` - + ``` shell dnf install centreon-plugin-Operatingsystems-Linux-Snmp ``` - + ```shell apt install centreon-plugin-operatingsystems-linux-snmp diff --git a/versioned_docs/version-26.10/getting-started/monitor-windows-server-with-snmp.md b/versioned_docs/version-26.10/getting-started/monitor-windows-server-with-snmp.md index 2c2ffaa78bba..73e5e94c01c8 100644 --- a/versioned_docs/version-26.10/getting-started/monitor-windows-server-with-snmp.md +++ b/versioned_docs/version-26.10/getting-started/monitor-windows-server-with-snmp.md @@ -95,21 +95,21 @@ Then select **Accept SNMP packets from these hosts** and add the IP address of t Connect to your poller using SSH and install the Windows SNMP plugin (see the [monitoring procedure for the **Windows SNMP** Monitoring Connector](/pp/integrations/plugin-packs/procedures/operatingsystems-windows-snmp) for more information): - + ``` shell dnf install centreon-plugin-Operatingsystems-Windows-Snmp ``` - + ``` shell dnf install centreon-plugin-Operatingsystems-Windows-Snmp ``` - + ```shell apt install centreon-plugin-operatingsystems-windows-snmp diff --git a/versioned_docs/version-26.10/getting-started/mysql_tuto.md b/versioned_docs/version-26.10/getting-started/mysql_tuto.md index ca56e051b5be..172eb4438e67 100644 --- a/versioned_docs/version-26.10/getting-started/mysql_tuto.md +++ b/versioned_docs/version-26.10/getting-started/mysql_tuto.md @@ -32,21 +32,21 @@ GRANT SELECT ON *.* TO 'username'@'IP_POLLER'; Install the following plugin on the poller that will monitor your database: - + ``` shell dnf install centreon-plugin-Applications-Databases-Mysql ``` - + ``` shell dnf install centreon-plugin-Applications-Databases-Mysql ``` - + ```shell apt install centreon-plugin-applications-databases-mysql From 074666fd3762bd19844a5afae82fcd0bc0d6420e Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 24 Sep 2026 14:59:36 +0200 Subject: [PATCH 086/179] Update supported OSs in tabs --- .../monitoring/anomaly-detection.md | 6 ++-- .../monitoring/basic-objects/commands.md | 8 ++--- .../monitoring/discovery/administration.md | 6 ++-- .../monitoring/discovery/installation.md | 6 ++-- .../monitoring/passive-monitoring/dsm.md | 8 ++--- .../version-26.10/monitoring/pluginpacks.md | 30 +++++++++---------- .../monitoring/web-import-export.md | 6 ++-- .../monitoring/anomaly-detection.md | 6 ++-- .../monitoring/basic-objects/commands.md | 12 ++++---- .../monitoring/discovery/administration.md | 6 ++-- .../monitoring/discovery/installation.md | 6 ++-- .../monitoring/passive-monitoring/dsm.md | 8 ++--- .../version-26.10/monitoring/pluginpacks.md | 30 +++++++++---------- .../monitoring/web-import-export.md | 6 ++-- 14 files changed, 72 insertions(+), 72 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/anomaly-detection.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/anomaly-detection.md index c2ac6690e00f..66c692eff5df 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/anomaly-detection.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/anomaly-detection.md @@ -56,21 +56,21 @@ Pour utiliser **Anomaly Detection**, vous aurez besoin des éléments suivants : Exécutez la commande suivante : - + ```shell dnf install centreon-anomaly-detection ``` - + ```shell dnf install centreon-anomaly-detection ``` - + ``` shell apt update && apt install centreon-anomaly-detection diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/basic-objects/commands.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/basic-objects/commands.md index a834265a9599..fcf517f1135a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/basic-objects/commands.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/basic-objects/commands.md @@ -177,21 +177,21 @@ Utilisé avec Centreon Engine, il accélère l'exécution des contrôles faits v Exécutez la commande suivante en tant qu'utilisateur privilégié : - + ``` shell dnf install centreon-connector-ssh ``` - + ``` shell dnf install centreon-connector-ssh ``` - + ``` shell apt install centreon-connector-ssh @@ -224,7 +224,7 @@ dnf install centreon-connector-perl ``` - + ``` shell apt install centreon-connector-perl diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/administration.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/administration.md index 537e9760b99e..a767ae5c86d8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/administration.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/administration.md @@ -11,21 +11,21 @@ import TabItem from '@theme/TabItem'; 1. Pour mettre à jour le module, exécutez la commande suivante : - + ``` shell dnf update -y centreon-auto-discovery-server ``` - + ``` shell dnf update -y centreon-auto-discovery-server ``` - + ``` shell apt install --only-upgrade centreon-auto-discovery-server diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/installation.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/installation.md index f52097255cd5..9f08c15e12c5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/installation.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/installation.md @@ -11,21 +11,21 @@ import TabItem from '@theme/TabItem'; 1. Pour installer le paquet, exécutez la commande suivante sur le serveur Central : - + ``` shell dnf install -y centreon-auto-discovery-server ``` - + ``` shell dnf install -y centreon-auto-discovery-server ``` - + ``` shell apt update && apt install centreon-auto-discovery-server diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/passive-monitoring/dsm.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/passive-monitoring/dsm.md index 154f51ea2b51..720ce7775b45 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/passive-monitoring/dsm.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/passive-monitoring/dsm.md @@ -29,21 +29,21 @@ installés sur le serveur principal. Exécutez la commande : - + ``` shell dnf install centreon-dsm-server centreon-dsm-client ``` - + ``` shell dnf install centreon-dsm-server centreon-dsm-client ``` - + ``` shell apt install centreon-dsm-server centreon-dsm-client @@ -84,7 +84,7 @@ dnf install centreon-dsm-client ``` - + ``` shell apt install centreon-dsm-client diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/pluginpacks.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/pluginpacks.md index 042c61fa55ba..e63f80122778 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/pluginpacks.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/pluginpacks.md @@ -36,21 +36,21 @@ recommandé de rester à jour sur ce composant. Pour mettre à jour le module, lancez la commande : - + ```shell dnf update centreon-pp-manager ``` - + ```shell dnf update centreon-pp-manager ``` - + ```shell apt install --only-upgrade centreon-pp-manager @@ -94,21 +94,21 @@ Un connecteur de supervision s'installe en 4 étapes : depuis votre serveur central : - + ```shell dnf install centreon-pack-* ``` - + ```shell dnf install centreon-pack-* ``` - + ```shell apt install centreon-pack-* @@ -172,21 +172,21 @@ La procédure de supervision comprend une section **Installation** qui vous indi La commande d'installation suit le modèle suivant : - + ```shell dnf install centreon-plugin-$PLUGIN-PACK$ ``` - + ```shell dnf install centreon-plugin-$PLUGIN-PACK$ ``` - + ```shell apt install centreon-plugin-$PLUGIN-PACK$ @@ -198,21 +198,21 @@ apt install centreon-plugin-$PLUGIN-PACK$ dans laquelle ``$PLUGIN-PACK$`` correspond au nom du pack. Exemple : - + ```shell dnf install centreon-plugin-Cloud-Aws-Ec2-Api ``` - + ```shell dnf install centreon-plugin-Cloud-Aws-Ec2-Api ``` - + ```shell apt install centreon-plugin-cloud-aws-ec2-api @@ -275,21 +275,21 @@ Si **Installation automatique des plugins** est à **OFF**, utilisez la commande 1. Exécutez la commande suivante sur **tous les collecteurs**: - + ```shell dnf update centreon-plugin\* ``` - + ```shell dnf update centreon-plugin\* ``` - + ```shell apt-get --only-upgrade install centreon-plugin\* diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/web-import-export.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/web-import-export.md index 1d5aaa286d35..6e7a0892be60 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/web-import-export.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/web-import-export.md @@ -22,21 +22,21 @@ Il est nécessaire d'avoir un compte administrateur pour pouvoir utiliser AWIE. Exécutez les commandes suivantes en tant qu'utilisateur privilégié : - + ``` shell dnf install centreon-awie ``` - + ``` shell dnf install centreon-awie ``` - + ``` shell apt install centreon-awie diff --git a/versioned_docs/version-26.10/monitoring/anomaly-detection.md b/versioned_docs/version-26.10/monitoring/anomaly-detection.md index 709e5e63a6df..da3f2e1faf1b 100644 --- a/versioned_docs/version-26.10/monitoring/anomaly-detection.md +++ b/versioned_docs/version-26.10/monitoring/anomaly-detection.md @@ -56,21 +56,21 @@ To use Anomaly Detection, you will need: Run the following command: - + ```shell dnf install centreon-anomaly-detection ``` - + ```shell dnf install centreon-anomaly-detection ``` - + ``` shell apt update && apt install centreon-anomaly-detection diff --git a/versioned_docs/version-26.10/monitoring/basic-objects/commands.md b/versioned_docs/version-26.10/monitoring/basic-objects/commands.md index 4339aff49f9e..81afa07c8053 100644 --- a/versioned_docs/version-26.10/monitoring/basic-objects/commands.md +++ b/versioned_docs/version-26.10/monitoring/basic-objects/commands.md @@ -174,21 +174,21 @@ Centreon recommends using its official packages. Most of Centreon’s endorsed s Run the following commands as a privileged user: - + ``` shell dnf install centreon-connector-ssh ``` - + ``` shell dnf install centreon-connector-ssh ``` - + ``` shell apt install centreon-connector-ssh @@ -209,21 +209,21 @@ Centreon recommends using its official packages. Most of Centreon’ endorsed so Run the following commands as a privileged user: - + ``` shell dnf install centreon-connector-perl ``` - + ``` shell dnf install centreon-connector-perl ``` - + ``` shell apt install centreon-connector-perl diff --git a/versioned_docs/version-26.10/monitoring/discovery/administration.md b/versioned_docs/version-26.10/monitoring/discovery/administration.md index c053f405c264..7443798fcfc2 100644 --- a/versioned_docs/version-26.10/monitoring/discovery/administration.md +++ b/versioned_docs/version-26.10/monitoring/discovery/administration.md @@ -11,21 +11,21 @@ import TabItem from '@theme/TabItem'; 1. To update the module, run the following command: - + ``` shell dnf update -y centreon-auto-discovery-server ``` - + ``` shell dnf update -y centreon-auto-discovery-server ``` - + ``` shell apt install --only-upgrade centreon-auto-discovery-server diff --git a/versioned_docs/version-26.10/monitoring/discovery/installation.md b/versioned_docs/version-26.10/monitoring/discovery/installation.md index a7ba5e73723c..4624135cfb8c 100644 --- a/versioned_docs/version-26.10/monitoring/discovery/installation.md +++ b/versioned_docs/version-26.10/monitoring/discovery/installation.md @@ -11,21 +11,21 @@ import TabItem from '@theme/TabItem'; 1. To install packages, execute the following command on the Central server: - + ``` shell dnf install -y centreon-auto-discovery-server ``` - + ``` shell dnf install -y centreon-auto-discovery-server ``` - + ``` shell apt update && apt install centreon-auto-discovery-server diff --git a/versioned_docs/version-26.10/monitoring/passive-monitoring/dsm.md b/versioned_docs/version-26.10/monitoring/passive-monitoring/dsm.md index c442e1bcfef4..662fe35539cc 100644 --- a/versioned_docs/version-26.10/monitoring/passive-monitoring/dsm.md +++ b/versioned_docs/version-26.10/monitoring/passive-monitoring/dsm.md @@ -27,21 +27,21 @@ main server. Run the command: - + ``` shell dnf install centreon-dsm-server centreon-dsm-client ``` - + ``` shell dnf install centreon-dsm-server centreon-dsm-client ``` - + ``` shell apt install centreon-dsm-server centreon-dsm-client @@ -82,7 +82,7 @@ dnf install centreon-dsm-client ``` - + ``` shell apt install centreon-dsm-client diff --git a/versioned_docs/version-26.10/monitoring/pluginpacks.md b/versioned_docs/version-26.10/monitoring/pluginpacks.md index 4949b3466795..8647e7495989 100644 --- a/versioned_docs/version-26.10/monitoring/pluginpacks.md +++ b/versioned_docs/version-26.10/monitoring/pluginpacks.md @@ -38,21 +38,21 @@ Packs. It is installed by default. We recommend that you keep this module regula To update this module, run the following command: - + ```shell dnf update centreon-pp-manager ``` - + ```shell dnf update centreon-pp-manager ``` - + ```shell apt install --only-upgrade centreon-pp-manager @@ -96,21 +96,21 @@ Installing a Monitoring Connector is a 4-step process: - install or update the Monitoring Connectors catalog from your Centreon Central server: - + ```shell dnf install centreon-pack-* ``` - + ```shell dnf install centreon-pack-* ``` - + ```shell apt install centreon-pack-* @@ -175,21 +175,21 @@ The monitoring procedure contains an **Installation** section that explains how The installation command looks like this: - + ```shell dnf install centreon-plugin-$PLUGIN-PACK$ ``` - + ```shell dnf install centreon-plugin-$PLUGIN-PACK$ ``` - + ```shell apt install centreon-plugin-$PLUGIN-PACK$ @@ -202,21 +202,21 @@ Where ``$PLUGIN-PACK$`` is the name of the pack. Example: - + ```shell dnf install centreon-plugin-Cloud-Aws-Ec2-Api ``` - + ```shell dnf install centreon-plugin-Cloud-Aws-Ec2-Api ``` - + ```shell apt install centreon-plugin-cloud-aws-ec2-api @@ -277,21 +277,21 @@ If **Automatic installation of plugins** is set to **OFF**, use the following co 1. Execute the following command on all pollers: - + ```shell dnf update centreon-plugin\* ``` - + ```shell dnf update centreon-plugin\* ``` - + ```shell apt-get --only-upgrade install centreon-plugin\* diff --git a/versioned_docs/version-26.10/monitoring/web-import-export.md b/versioned_docs/version-26.10/monitoring/web-import-export.md index 21e5c2fb8533..a4bcda5af59e 100644 --- a/versioned_docs/version-26.10/monitoring/web-import-export.md +++ b/versioned_docs/version-26.10/monitoring/web-import-export.md @@ -27,21 +27,21 @@ To be able to use AWIE, you need to be an administrator. Run the following commands as a privileged user: - + ``` shell dnf install centreon-awie ``` - + ``` shell dnf install centreon-awie ``` - + ``` shell apt install centreon-awie From 8a28d2fc439272b3c5894461d1df6489616c8dfa Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 24 Sep 2026 15:07:18 +0200 Subject: [PATCH 087/179] Update supported OSs in tabs --- .../version-26.10/administration/postfix.md | 20 +++++++++---------- .../version-26.10/administration/postfix.md | 16 +++++++-------- 2 files changed, 18 insertions(+), 18 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/postfix.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/postfix.md index 0c6abfb959d5..e5ef8b9d9015 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/postfix.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/postfix.md @@ -22,35 +22,35 @@ Nous vous recommandons d'utiliser un compte mail dédié à l'envoi des notifica 1. Dans le terminal de votre serveur, entrez la commande suivante : - + ``` shell dnf install postfix mailx cyrus-sasl-plain ``` - + ``` shell -dnf install postfix mailx cyrus-sasl-plain +dnf install s-nail cyrus-sasl-plain ``` - + ``` shell -dnf install mailx cyrus-sasl-plain +dnf install postfix mailx cyrus-sasl-plain ``` - + ``` shell dnf install s-nail cyrus-sasl-plain ``` - + ``` shell apt install postfix bsd-mailx libsasl2-modules @@ -176,19 +176,19 @@ apt install postfix bsd-mailx libsasl2-modules - Si le destinataire n'a pas reçu l'email, vérifiez le fichier de log suivant (s'il existe) : - + ```shell tail -f /var/log/maillog ``` - + ```shell tail -f /var/log/maillog ``` - + ```shell tail -f /var/log/mail.log diff --git a/versioned_docs/version-26.10/administration/postfix.md b/versioned_docs/version-26.10/administration/postfix.md index 5b48a0f08b10..3dc4359ac2d3 100644 --- a/versioned_docs/version-26.10/administration/postfix.md +++ b/versioned_docs/version-26.10/administration/postfix.md @@ -22,35 +22,35 @@ We recommend that you use a dedicated email account to send notifications. 1. In your server's terminal, enter the following command: - + ``` shell dnf install postfix mailx cyrus-sasl-plain ``` - + ``` shell -dnf install postfix mailx cyrus-sasl-plain +dnf install s-nail cyrus-sasl-plain ``` - + ``` shell -dnf install mailx cyrus-sasl-plain +dnf install postfix mailx cyrus-sasl-plain ``` - + ``` shell dnf install s-nail cyrus-sasl-plain ``` - + ``` shell apt install postfix bsd-mailx libsasl2-modules @@ -194,7 +194,7 @@ apt install postfix bsd-mailx libsasl2-modules tail -f /var/log/maillog ``` - + ```shell tail -f /var/log/mail.log From 2a922cd34d9cbf83056f1368d065c62de576223c Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 24 Sep 2026 15:09:24 +0200 Subject: [PATCH 088/179] Fix typo --- .../version-26.10/cma/cma-setup-manual.md | 4 ++-- versioned_docs/version-26.10/cma/cma-setup-manual.md | 4 ++-- versioned_docs/version-26.10/upgrade/_upgrade-central.mdx | 6 ++++-- 3 files changed, 8 insertions(+), 6 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/cma/cma-setup-manual.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/cma/cma-setup-manual.md index 179a988bac1a..d1b6627e80df 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/cma/cma-setup-manual.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/cma/cma-setup-manual.md @@ -265,7 +265,7 @@ dnf install -y centreon-monitoring-agent ``` - + 1. Exécutez les commandes suivantes : @@ -1002,7 +1002,7 @@ dnf update centreon-monitoring-agent ``` - + ```shell apt-get update && apt-get upgrade centreon-monitoring-agent diff --git a/versioned_docs/version-26.10/cma/cma-setup-manual.md b/versioned_docs/version-26.10/cma/cma-setup-manual.md index cbb028c92582..765092f954db 100644 --- a/versioned_docs/version-26.10/cma/cma-setup-manual.md +++ b/versioned_docs/version-26.10/cma/cma-setup-manual.md @@ -264,7 +264,7 @@ dnf install compat-openssl11 centreon-monitoring-agent ``` - + 1. Execute the following commands: @@ -1006,7 +1006,7 @@ dnf update centreon-monitoring-agent ``` - + ```shell apt-get update && apt-get upgrade centreon-monitoring-agent diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index cc399a0b7cf7..e2cfcafd815c 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -75,7 +75,8 @@ You need to install the Remi repo and the switch the PHP stream from version {pr ```shell dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm rpm -e --nodeps php-sourceguardian-loader -dnf module switch-to php:remi-8.4/common -y +nf module reset php -y +dnf module enable php:remi-8.4 -y ``` @@ -105,7 +106,8 @@ dnf clean all --enablerepo=* ```shell -dnf update centreon\* php-pecl-gnupg +rpm -e --nodeps php-pecl-gnupg +dnf update -y "centreon*" --exclude=php-pecl-gnupg ``` From 78a094faa64e661cb255e073afc683d8433a9704 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 24 Sep 2026 19:09:29 +0200 Subject: [PATCH 089/179] Update "secure your platform" --- .../administration/secure-platform.md | 416 ++++++++---------- .../administration/secure-platform.md | 307 ++++++++----- 2 files changed, 379 insertions(+), 344 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md index 93ec42ae62be..3445dcf6885c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md @@ -28,17 +28,57 @@ passwd De plus, il est important de vérifier que le compte Apache ne dispose pas de droits de connexion au terminal. Exécutez la commande suivante : + + + +```shell +cat /etc/passwd | grep apache +``` + + + + ```shell cat /etc/passwd | grep apache ``` + + + +```shell +cat /etc/passwd | grep www-data +``` + + + + Vous devez avoir **/sbin/nologin** tel que : + + + +```shell +apache:x:48:48:Apache:/usr/share/httpd:/sbin/nologin +``` + + + + ```shell apache:x:48:48:Apache:/usr/share/httpd:/sbin/nologin ``` -> Pour rappel, la liste des utilisateurs et des groupes se trouve [ici](../installation/technical.md#utilisateurs-et-groupes) + + + +```shell +www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin +``` + + + + +> Pour rappel, la [liste des utilisateurs et des groupes se trouve ici](../installation/technical.md#utilisateurs-et-groupes). ## Activer SELinux @@ -92,7 +132,7 @@ shutdown -r now Suivant le type de serveur, installer les paquets avec la commande suivante : - + @@ -128,14 +168,15 @@ Suivant le type de serveur, installer les paquets avec la commande suivante : ```shell - dnf install centreon-mbi-selinux + dnf install centreon-mbi-selinux \ + centreon-gorgoned-selinux ``` - + @@ -179,7 +220,7 @@ Suivant le type de serveur, installer les paquets avec la commande suivante : - + SELinux ne concerne que les environnements EL. @@ -252,7 +293,7 @@ chmod 660 /etc/centreon/centreon.conf.php ## Sécuriser l'accès root au SGBD -Vous devez obligatoirement définir un mot de passe pour l'utilisateur **root** de la base de données. Si vous ne l'avez pas déjà fait, exécutez la commande suivante et suivez les instructions : +Si vous ne l'avez pas déjà fait, définissez un mot de passe **root** pour la base de données (obligatoire) : @@ -261,6 +302,8 @@ Vous devez obligatoirement définir un mot de passe pour l'utilisateur **root** mariadb-secure-installation ``` +Plus d'informations sur la [documentation officielle MariaDB](https://mariadb.com/kb/en/mysql_secure_installation/). + @@ -274,7 +317,7 @@ mysql_secure_installation ## Activer firewalld - + Installez firewalld: @@ -284,7 +327,7 @@ dnf install firewalld - + Installez firewalld: @@ -294,7 +337,7 @@ dnf install firewalld - + Installez firewalld: @@ -389,21 +432,21 @@ Fail2ban est un framework de prévention contre les intrusions, écrit en Python Installez le module inotify: - + ```shell dnf install python3-inotify ``` - + ```shell dnf install python3-inotify ``` - + ```shell apt install python3-inotify @@ -415,7 +458,7 @@ apt install python3-inotify Installez fail2ban : - + ```shell dnf install epel-release @@ -429,7 +472,7 @@ dnf update -y selinux-policy* ``` - + ```shell dnf install epel-release @@ -443,7 +486,7 @@ dnf update -y selinux-policy* ``` - + ```shell apt install fail2ban @@ -517,169 +560,41 @@ Status for the jail: centreon ## Sécuriser le serveur web en HTTPS -Par défaut, Centreon installe un serveur web en mode HTTP. Il est fortement recommandé de passer en mode HTTPS en ajoutant votre certificat. Il est également recommandé d'utiliser un certificat validé par une autorité plutôt qu'un certificat auto-signé. - -- Si vous avez déjà un certificat validé par une autorité, vous pouvez passer directement à cette [étape](#activer-le-mode-https-sur-le-serveur-web) pour activer le mode HTTPS sur votre serveur Apache. +La [procédure d'installation standard à partir des paquets](../installation/installation-of-a-central-server/using-packages.md) vous permet d'installer votre serveur central en mode HTTPS. Si, pour une raison quelconque, vous avez choisi de l'installer en mode HTTP, ou si vous avez mis à niveau un serveur central HTTP et souhaitez maintenant passer en HTTPS, suivez cette procédure. -- Si vous ne disposez pas d'un certificat validé par une autorité, vous pouvez en générer un sur des plateformes telles que [Let's Encrypt](https://letsencrypt.org/fr/). +Il est fortement recommandé de passer en mode HTTPS. Utilisez un certificat émis par une autorité de confiance. Les certificats auto-signés ne doivent pas être utilisés en production. -- Si vous souhaitez créer un certificat selon la méthode auto-signée, suivez cette [étape](#créer-un-certificat-auto-signé) avant d'activer le mode HTTPS sur votre serveur. +- Si vous disposez déjà d'un certificat validé par une autorité, vous pouvez [activer dès maintenant le mode HTTPS sur votre serveur Apache](#activer-le-mode-https-sur-le-serveur-web). -### Créer un certificat auto-signé +- Si vous ne disposez pas d'un certificat validé par une autorité, vous pouvez en générer un sur des plateformes telles que [Let's Encrypt](https://letsencrypt.org/). -> Cette procédure permet de créer : -- Une clé privée pour le serveur : **centreon7.key** dans notre cas. Elle sera utilisée par le service Apache. -- Un fichier CSR (Certificate Signing Request) : **centreon7.csr** dans notre cas. -- Une clé privée pour le certificat de l'autorité de certification : **ca_demo.key** dans notre cas. -- Un certificat x509 pour signer votre certificat pour le serveur : **ca-demo.crt** dans notre cas. -- Un certificat pour le serveur : **centreon7.crt** dans notre cas. +- Si, à des fins de test, vous souhaitez utiliser un certificat auto-signé, [vous pouvez suivre cett procédure pour en créer un](./self-signed-certificate.md) avant d'activer le mode HTTPS sur votre serveur. Si vous utilisez un certificat qui n'est pas fourni par une autorité de confiance, vous devrez importer le certificat de l'autorité de certification (CA) dans votre navigateur. -Soit un serveur Centreon avec le FQDN suivant : **centreon7.localdomain**. - -1. Préparez la configuration OpenSSL : - - En raison d'un changement de politique chez Google, les certificats auto-signés peuvent être rejetés par le navigateur Google Chrome (sans qu'il soit possible d'ajouter une exception). Pour continuer à utiliser ce navigateur, vous devez modifier la configuration OpenSSL. - - - - - Ouvrez le fichier **/etc/pki/tls/openssl.cnf**. L'objectif est de modifier ce fichier pour renseigner les différents IPs et FQDNs relatifs au serveur. - - - - - Ouvrez le fichier **/etc/pki/tls/openssl.cnf**. L'objectif est de modifier ce fichier pour renseigner les différents IPs et FQDNs relatifs au serveur. - - - - - Ouvrez le fichier **/etc/ssl/openssl.cnf**. L'objectif est de modifier ce fichier pour renseigner les différents IPs et FQDNs relatifs au serveur. - - - - - Recherchez la section ```[v3_ca]``` afin d'ajouter le nouveau tag ```alt_names``` : - - ```text - # Add the alt_names tag that allows you to inform our various IPs and FQDNs for the server - [ alt_names ] - IP.1 = xxx.xxx.xxx.xxx - DNS.1 = centreon7.localdomain - # If you have several IP (HA: vip + ip) - # IP.2 = xxx.xxx.xxx.xxx - [ v3_ca ] - subjectAltName = @alt_names - ``` - - Voici un exemple de ce à quoi le fichier peut ressembler : - ```text - [ alt_names ] - IP.1 = 10.25.11.73 - DNS.1 = centreon7.localdomain - - [ v3_ca ] - subjectAltName = @alt_names - ``` - -2. Créez une clé privée pour le serveur : - -Créez une clé privée nommée **centreon7.key** sans mot de passe afin qu'elle puisse être utilisée par le service Apache. -```text -openssl genrsa -out centreon7.key 2048 -``` - -Protégez le fichier en modifiant ses droits : -```text -chmod 400 centreon7.key -``` - -3. Créez un fichier CSR : - -Avec la clé que vous venez de créer, créez un fichier CSR (Certificate Signing Request). Remplissez les champs avec les informations propres à votre entreprise. Le champ **Common Name** doit être identique au hostname de votre serveur Apache (dans notre cas, **centreon7.localdomain**). -```text -openssl req -new -key centreon7.key -out centreon7.csr -``` - -4. Créez une clé privée pour le certificat de l'autorité de certification : - -Créez une clé privée pour cette autorité : **ca_demo.key** dans notre cas. Ajoutez l'option **-aes256** pour chiffrer la clé produite et y appliquer un mot de passe. Ce mot de passe sera demandé chaque fois que la clé sera utilisée. -```text -openssl genrsa -aes256 2048 > ca_demo.key -``` - -5. Créez un certificat x509 à partir de la clé privée du certificat de l'autorité de certification : - -Créez un certificat x509 qui sera valide pendant un an : **ca_demo.crt** dans notre cas. - -> Notez qu'il est nécessaire de simuler un tiers de confiance : le **Common Name** doit être différent de celui du certificat du serveur. -```text -openssl req -new -x509 -days 365 -key ca_demo.key -out ca_demo.crt -``` - -Ce certificat étant créé, vous pourrez l'utiliser pour signer le certificat du serveur. - -6. Créez un certificat pour le serveur : - -Créez votre certificat pour le serveur en utilisant le certificat x509 (**ca_demo.crt**) pour le signer. +### Activer le mode HTTPS sur le serveur web - - -```text -openssl x509 -req -in centreon7.csr -out centreon7.crt -CA ca_demo.crt -CAkey ca_demo.key -CAcreateserial -CAserial ca_demo.srl -extfile /etc/pki/tls/openssl.cnf -extensions v3_ca -``` - - -```text -openssl x509 -req -in centreon7.csr -out centreon7.crt -CA ca_demo.crt -CAkey ca_demo.key -CAcreateserial -CAserial ca_demo.srl -extfile /etc/pki/tls/openssl.cnf -extensions v3_ca -``` - - - - -```text -openssl x509 -req -in centreon7.csr -out centreon7.crt -CA ca_demo.crt -CAkey ca_demo.key -CAcreateserial -CAserial ca_demo.srl -extfile /etc/ssl/openssl.cnf -extensions v3_ca -``` - - - - -Le mot de passe créé à l'étape **Créer une clé privée pour le certificat de l'autorité de certification** doit être renseigné. Vous obtenez un certificat pour le serveur nommé **centreon7.crt**. - -Vous pouvez voir le contenu du fichier : -```text -less centreon7.crt -``` - -7. Vous devez ensuite récupérer le fichier du certificat x509 (**ca_demo.crt**) et l'importer dans le magasin de certificats de votre navigateur. - -Maintenant que vous avez votre certificat auto-signé, vous pouvez suivre la procédure suivante pour activer le mode HTTPS sur votre serveur Apache. - -### Activer le mode HTTPS sur le serveur web - 1. Installez le module SSL pour Apache : - - - ```shell dnf install mod_ssl openssl ``` 2. Installez les certificats : -Installez vos certificats (**centreon7.key** et **centreon7.crt** dans notre cas, et le certificat CA) en les copiant dans la configuration Apache : +Installez vos certificats (**server.pem** et **server-key.pem** dans l'exemple suivant, et le certificat CA) en les copiant dans la configuration Apache : ```shell -cp centreon7.key /etc/pki/tls/private/ -cp centreon7.crt /etc/pki/tls/certs/ -cp ca_demo.crt /etc/pki/tls/certs/ +cp server-key.pem /etc/pki/tls/private/ +cp server.pem /etc/pki/tls/certs/ +cp rootCA.pem /etc/pki/tls/certs/ ``` - + + +1. Installez le module SSL pour Apache : ```shell dnf install mod_ssl openssl @@ -687,16 +602,16 @@ dnf install mod_ssl openssl 2. Installez les certificats : -Installez vos certificats (**centreon7.key** et **centreon7.crt** dans notre cas, et le certificat CA) en les copiant dans la configuration Apache : +Installez vos certificats (**server.pem** et **server-key.pem** dans l'exemple suivant, et le certificat CA) en les copiant dans la configuration Apache : ```shell -cp centreon7.key /etc/pki/tls/private/ -cp centreon7.crt /etc/pki/tls/certs/ -cp ca_demo.crt /etc/pki/tls/certs/ +cp server-key.pem /etc/pki/tls/private/ +cp server.pem /etc/pki/tls/certs/ +cp rootCA.pem /etc/pki/tls/certs/ ``` - + ```shell curl -sSL https://packages.sury.org/apache2/README.txt | sudo bash -x @@ -708,12 +623,12 @@ systemctl restart apache2 2. Installez les certificats : -Installez vos certificats (**centreon7.key** et **centreon7.crt** dans notre cas, et le certificat CA) en les copiant dans la configuration Apache : +Installez vos certificats (**server.pem** et **server-key.pem** dans l'exemple suivant, et le certificat CA) en les copiant dans la configuration Apache : ```shell -cp centreon7.key /etc/ssl/private/ -cp centreon7.crt /etc/ssl/certs/ -cp ca_demo.crt /etc/ssl/certs/ +cp server-key.pem /etc/ssl/private/ +cp server.pem /etc/ssl/certs/ +cp rootCA.pem /etc/ssl/certs/ ``` @@ -722,21 +637,21 @@ cp ca_demo.crt /etc/ssl/certs/ 3. Sauvegardez la configuration actuelle du serveur Apache pour Centreon : - + ```shell cp /etc/httpd/conf.d/10-centreon.conf{,.origin} ``` - + ```shell cp /etc/httpd/conf.d/10-centreon.conf{,.origin} ``` - + ```shell cp /etc/apache2/sites-available/centreon.conf{,.origin} @@ -751,19 +666,20 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} > **/usr/share/centreon/examples/centreon.apache.https.conf** - + Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. - + Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. - + Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section **\**. + @@ -783,7 +699,7 @@ ServerTokens Prod Voici un exemple de ce à quoi le fichier peut ressembler : - + ```apacheconf Define base_uri "/centreon" @@ -806,8 +722,8 @@ ServerTokens Prod SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA SSLHonorCipherOrder On SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/ca.crt - SSLCertificateKeyFile /etc/pki/tls/private/ca.key + SSLCertificateFile /etc/pki/tls/certs/server.pem + SSLCertificateKeyFile /etc/pki/tls/private/server-key.pem Header set X-Frame-Options: "sameorigin" Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict @@ -859,10 +775,10 @@ ServerTokens Prod ``` -> N'oubliez pas de changer les directives **SSLCertificateFile** et **SSLCertificateKeyFile** avec les chemins d'accès vers votre clé et votre certificat. Dans notre cas : **SSLCertificateFile /etc/pki/tls/certs/centreon7.crt** et **SSLCertificateKeyFile /etc/pki/tls/private/centreon7.key**. +> N'oubliez pas de changer les directives **SSLCertificateFile** et **SSLCertificateKeyFile** avec les chemins d'accès vers votre propre clé et son certificat. - + ```apacheconf Define base_uri "/centreon" @@ -885,8 +801,8 @@ ServerTokens Prod SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA SSLHonorCipherOrder On SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/ca.crt - SSLCertificateKeyFile /etc/pki/tls/private/ca.key + SSLCertificateFile /etc/pki/tls/certs/server.pem + SSLCertificateKeyFile /etc/pki/tls/private/server-key.pem Header set X-Frame-Options: "sameorigin" Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict @@ -938,10 +854,10 @@ ServerTokens Prod ``` -> N'oubliez pas de changer les directives **SSLCertificateFile** et **SSLCertificateKeyFile** avec les chemins d'accès vers votre clé et votre certificat. Dans notre cas : **SSLCertificateFile /etc/pki/tls/certs/centreon7.crt** et **SSLCertificateKeyFile /etc/pki/tls/private/centreon7.key**. +> N'oubliez pas de changer les directives **SSLCertificateFile** et **SSLCertificateKeyFile** avec les chemins d'accès vers votre propre clé et son certificat. - + ```apacheconf Define base_uri "/centreon" @@ -964,8 +880,8 @@ ServerTokens Prod SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA SSLHonorCipherOrder On SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/ca.crt - SSLCertificateKeyFile /etc/pki/tls/private/ca.key + SSLCertificateFile /etc/ssl/certs/server.pem + SSLCertificateKeyFile /etc/ssl/private/server-key.pem Header set X-Frame-Options: "sameorigin" Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict @@ -1017,7 +933,7 @@ ServerTokens Prod ``` -> N'oubliez pas de changer les directives **SSLCertificateFile** et **SSLCertificateKeyFile** avec les chemins d'accès vers votre clé et votre certificat. Dans notre cas : **SSLCertificateFile /etc/ssl/certs/centreon7.crt** et **SSLCertificateKeyFile /etc/ssl/private/centreon7.key**. +> N'oubliez pas de changer les directives **SSLCertificateFile** et **SSLCertificateKeyFile** avec les chemins d'accès vers votre propre clé et son certificat. @@ -1025,7 +941,7 @@ ServerTokens Prod 5. Activez les flags HttpOnly / Secure et cacher la signature du serveur Apache : - + Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant les lignes suivantes avant la balise `` : @@ -1047,12 +963,12 @@ ServerTokens Prod * Ajoutez le chemin d'accès au certificat CA qui a été utilisé pour signer le certificat du serveur : ```text - openssl.cafile=/etc/pki/tls/certs/ca_demo.crt - curl.cainfo=/etc/pki/tls/certs/ca_demo.crt + openssl.cafile=/etc/pki/tls/certs/rootCA.pem + curl.cainfo=/etc/pki/tls/certs/rootCA.pem ``` - + Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant les lignes suivantes avant la balise `` : @@ -1074,12 +990,12 @@ ServerTokens Prod * Ajoutez le chemin d'accès au certificat CA qui a été utilisé pour signer le certificat du serveur : ```text - openssl.cafile=/etc/pki/tls/certs/ca_demo.crt - curl.cainfo=/etc/pki/tls/certs/ca_demo.crt + openssl.cafile=/etc/pki/tls/certs/rootCA.pem + curl.cainfo=/etc/pki/tls/certs/rootCA.pem ``` - + Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant les lignes suivantes avant la balise `` : @@ -1092,11 +1008,11 @@ ServerTokens Prod TraceEnable Off ``` -Éditez le fichier **/etc/php/8.2/mods-available/centreon.ini** et ajoutez les lignes suivantes : +Éditez le fichier **/etc/php/8.4/mods-available/centreon.ini** et ajoutez les lignes suivantes : ```text -openssl.cafile=/etc/ssl/certs/ca_demo.crt -curl.cainfo=/etc/ssl/certs/ca_demo.crt +openssl.cafile=/etc/ssl/certs/rootCA.pem +curl.cainfo=/etc/ssl/certs/rootCA.pem ``` @@ -1105,7 +1021,7 @@ curl.cainfo=/etc/ssl/certs/ca_demo.crt 6. Cachez le répertoire par défaut **/icons** : - + Éditez le fichier **/etc/httpd/conf.d/autoindex.conf** en commentant la ligne suivante : @@ -1114,7 +1030,7 @@ curl.cainfo=/etc/ssl/certs/ca_demo.crt ``` - + Éditez le fichier **/etc/httpd/conf.d/autoindex.conf** en commentant la ligne suivante : @@ -1123,9 +1039,7 @@ curl.cainfo=/etc/ssl/certs/ca_demo.crt ``` - - -Éditez le fichier **/etc/apache2/mods-available/autoindex.conf** en commentant la ligne suivante : + > Le répertoire est caché par défaut. @@ -1135,7 +1049,7 @@ curl.cainfo=/etc/ssl/certs/ca_demo.crt 7. Vous pouvez effectuer ce test vérifiant qu'Apache est bien configuré, en exécutant la commande suivante : - + ```apacheconf apachectl configtest @@ -1148,7 +1062,7 @@ Syntax OK ``` - + ```apacheconf apachectl configtest @@ -1161,7 +1075,7 @@ Syntax OK ``` - + ```apacheconf apache2ctl configtest @@ -1179,7 +1093,7 @@ Syntax OK 8. Redémarrez le serveur web Apache et PHP pour prendre la configuration en compte : - + ```shell systemctl restart php-fpm httpd @@ -1215,7 +1129,7 @@ Si tout est correct, vous devriez avoir quelque chose comme : ``` - + ```shell systemctl restart php-fpm httpd @@ -1251,10 +1165,10 @@ Si tout est correct, vous devriez avoir quelque chose comme : ``` - + ```shell -systemctl restart php8.2-fpm apache2 +systemctl restart php8.4-fpm apache2 ``` Puis vérifiez le statut : @@ -1304,7 +1218,7 @@ par le FQDN de votre serveur central : gorgone: tpapi: - name: centreonv2 - base_url: "http://centreon7.localdomain/centreon/api/latest/" + base_url: "https://centreon7.localdomain/centreon/api/latest/" username: "centreon-gorgone" password: "bpltc4aY" - name: clapi @@ -1373,21 +1287,21 @@ Pour personnaliser l'URI de Centreon : 1. Éditez le fichier de configuration Apache pour Centreon : - + ```shell vi /etc/httpd/conf.d/10-centreon.conf ``` - + ```shell vi /etc/httpd/conf.d/10-centreon.conf ``` - + ```shell vi /etc/apache2/sites-available/centreon.conf @@ -1405,21 +1319,21 @@ Define base_uri "/centreon" 3. Redémarrez Apache : - + ```shell systemctl restart httpd ``` - + ```shell systemctl restart httpd ``` - + ```shell systemctl restart apache2 @@ -1435,7 +1349,7 @@ Il est possible d'activer le protocole http2 pour améliorer les performances r Pour utiliser http2, vous devez suivre les étapes suivantes: - + 1. [Configurer le https pour Centreon](#sécuriser-le-serveur-web-en-https). @@ -1477,7 +1391,7 @@ systemctl restart httpd ``` - + 1. [Configurer le https pour Centreon](#sécuriser-le-serveur-web-en-https). @@ -1519,7 +1433,7 @@ systemctl restart httpd ``` - + 1. [Configurer le https pour Centreon](#sécuriser-le-serveur-web-en-https). @@ -1543,7 +1457,7 @@ apt install nghttp2 4. Exécutez les commandes suivantes : ```shell -a2dismod php8.2 +a2dismod php8.4 a2dismod mpm_prefork a2enmod mpm_event a2enmod http2 @@ -1565,21 +1479,21 @@ systemctl restart apache2 1. Installez **mod_security** : - + ```shell dnf install mod_security ``` - + ```shell dnf install mod_security ``` - + ```shell apt install libapache2-mod-security2 @@ -1591,24 +1505,24 @@ apt install libapache2-mod-security2 2. Éditez le fichier suivant et adaptez les paramètres selon votre choix : - + ```shell /etc/httpd/conf.d/mod_security.conf ``` - + ```shell /etc/httpd/conf.d/mod_security.conf ``` - + ```shell -/etc/modsecurity/mod_security.conf +/etc/modsecurity/modsecurity.conf ``` @@ -1616,6 +1530,27 @@ apt install libapache2-mod-security2 Nous recommandons la configuration suivante : + + + +```text + SecResponseBodyAccess Off + SecDebugLog /var/log/httpd/modsec_debug.log + SecDebugLogLevel 0 + SecAuditEngine RelevantOnly + SecAuditLogRelevantStatus "^(?:5|4(?!01|4))" + SecAuditLogParts ABJDEFHZ + SecAuditLogType Serial + SecAuditLog /var/log/httpd/modsec_audit.log + SecArgumentSeparator & + SecCookieFormat 0 + SecTmpDir /var/lib/mod_security + SecDataDir /var/lib/mod_security +``` + + + + ```text SecResponseBodyAccess Off SecDebugLog /var/log/httpd/modsec_debug.log @@ -1631,24 +1566,45 @@ Nous recommandons la configuration suivante : SecDataDir /var/lib/mod_security ``` + + + +```text + SecResponseBodyAccess Off + SecDebugLog /var/log/apache2/modsec_debug.log + SecDebugLogLevel 0 + SecAuditEngine RelevantOnly + SecAuditLogRelevantStatus "^(?:5|4(?!01|4))" + SecAuditLogParts ABJDEFHZ + SecAuditLogType Serial + SecAuditLog /var/log/apache2/modsec_audit.log + SecArgumentSeparator & + SecCookieFormat 0 + SecTmpDir /var/lib/mod_security + SecDataDir /var/lib/mod_security +``` + + + + 3. Redémarrez Apache : - + ```shell systemctl restart httpd ``` - + ```shell systemctl restart httpd ``` - + ```shell systemctl restart apache2 @@ -1657,10 +1613,6 @@ systemctl restart apache2 -## Ajoutez votre certificat à votre navigateur - -Si vous utilisez un certificat qui n'est pas fourni par une autorité de confiance, vous devez importer le certificat CA dans votre navigateur. - ## Authentification des utilisateurs Centreon propose plusieurs méthodes pour authentifier les utilisateurs : @@ -1750,8 +1702,8 @@ Voici une liste des services et répertoires qui doivent être exclus de l'analy * cbd * centreontrapd * gorgoned -* php-fpm -* httpd +* php-fpm (php8.4-fpm sous Debian) +* httpd (apache2 sous Debian) Si vous utilisez l'un de ces connecteurs, excluez les services suivants : diff --git a/versioned_docs/version-26.10/administration/secure-platform.md b/versioned_docs/version-26.10/administration/secure-platform.md index e76adb02f9f5..146f6f67ceb7 100644 --- a/versioned_docs/version-26.10/administration/secure-platform.md +++ b/versioned_docs/version-26.10/administration/secure-platform.md @@ -28,17 +28,57 @@ passwd In addition, it is important to verify that the Apache account does not have connection rights to the terminal. Execute the following command: + + + +```shell +cat /etc/passwd | grep apache +``` + + + + ```shell cat /etc/passwd | grep apache ``` + + + +```shell +cat /etc/passwd | grep www-data +``` + + + + You must have **/sbin/nologin** like: + + + +```shell +apache:x:48:48:Apache:/usr/share/httpd:/sbin/nologin +``` + + + + ```shell apache:x:48:48:Apache:/usr/share/httpd:/sbin/nologin ``` -> As a reminder, the list of users and groups can be found [here](../installation/technical.md#users-and-groups) + + + +```shell +www-data:x:33:33:www-data:/var/www:/usr/sbin/nologin +``` + + + + +> As a reminder, the [list of users and groups can be found here](../installation/technical.md#users-and-groups). ## Enable SELinux @@ -91,7 +131,8 @@ shutdown -r now Depending on the type of server, install the packages with the following command: - + + @@ -127,14 +168,15 @@ Depending on the type of server, install the packages with the following command ```shell - dnf install centreon-mbi-selinux + dnf install centreon-mbi-selinux \ + centreon-gorgoned-selinux ``` - + @@ -178,14 +220,13 @@ Depending on the type of server, install the packages with the following command - + SELinux only concerns EL environments. - To check the installation, execute the following command: ```shell @@ -251,18 +292,19 @@ chmod 660 /etc/centreon/centreon.conf.php ## Securing root access to the DBMS -[MariaDB](https://mariadb.com/kb/en/mysql_secure_installation/) proposes a default procedure to secure the DBMS -installation. It is mandatory to set a password for the **root** user of the database. If you haven't already done so, please execute the following command and follow the instructions: +If you haven't already done so, set a password for the **root** user of the database (this is mandatory): - + ```shell mariadb-secure-installation ``` +More info in [MariaDB's official documentation](https://mariadb.com/kb/en/mysql_secure_installation/). + - + ```shell mysql_secure_installation @@ -274,7 +316,7 @@ mysql_secure_installation ## Enable firewalld - + Install firewalld: @@ -283,7 +325,7 @@ dnf install firewalld ``` - + Install firewalld: @@ -292,7 +334,7 @@ dnf install firewalld ``` - + Install firewalld: @@ -388,21 +430,21 @@ Fail2Ban is an intrusion prevention software framework that protects computer se Install the inotify module: - + ```shell dnf install python3-inotify ``` - + ```shell dnf install python3-inotify ``` - + ```shell apt install python3-inotify @@ -414,35 +456,35 @@ apt install python3-inotify Install fail2ban: - + ```shell -yum install epel-release -yum install fail2ban fail2ban-systemd +dnf install epel-release +dnf install fail2ban fail2ban-systemd ``` If you have SELinux installed, then update the SELinux policies: ```shell -yum update -y selinux-policy* +dnf update -y selinux-policy* ``` - + ```shell -yum install epel-release -yum install fail2ban fail2ban-systemd +dnf install epel-release +dnf install fail2ban fail2ban-systemd ``` If you have SELinux installed, then update the SELinux policies: ```shell -yum update -y selinux-policy* +dnf update -y selinux-policy* ``` - + ```shell apt install fail2ban @@ -527,14 +569,14 @@ It is strongly recommended that you switch to HTTPS mode. Use a certificate issu - If you do not have a certificate validated by an authority, you can generate one on platforms such as [Let's Encrypt](https://letsencrypt.org/). -- If, for test purposes, you want to use a self-signed certificate, follow [this procedure](./self-signed-certificate.md) before activating HTTPS mode on your server. +- If, for test purposes, you want to use a self-signed certificate, follow [this procedure](./self-signed-certificate.md) before activating HTTPS mode on your server. If you use a certificate that is not provided by a trusted authority, you will have to import the CA certificate into your browser. ### Activating HTTPS mode on your web server -1. Install the SSL module for Apache: - - + + +1. Install the SSL module for Apache: ```shell dnf install mod_ssl openssl @@ -542,16 +584,18 @@ dnf install mod_ssl openssl 2. Install your certificates: -Install your certificates (**centreon7.key** and **centreon7.crt** in our example, and the CA certificate) by copying them to the Apache configuration: +Install your certificates (**server.pem** and **server-key.pem** in this example, and the CA certificate) by copying them to the Apache configuration: ```shell -cp centreon7.key /etc/pki/tls/private/ -cp centreon7.crt /etc/pki/tls/certs/ -cp ca_demo.crt /etc/pki/tls/certs/ +cp server-key.pem /etc/pki/tls/private/ +cp server.pem /etc/pki/tls/certs/ +cp rootCA.pem /etc/pki/tls/certs/ ``` - + + +1. Install the SSL module for Apache: ```shell dnf install mod_ssl openssl @@ -559,16 +603,18 @@ dnf install mod_ssl openssl 2. Install your certificates: -Install your certificates (**centreon7.key** and **centreon7.crt** in our example, and the CA certificate) by copying them to the Apache configuration: +Install your certificates (**server.pem** and **server-key.pem** in this example, and the CA certificate) by copying them to the Apache configuration: ```shell -cp centreon7.key /etc/pki/tls/private/ -cp centreon7.crt /etc/pki/tls/certs/ -cp ca_demo.crt /etc/pki/tls/certs/ +cp server-key.pem /etc/pki/tls/private/ +cp server.pem /etc/pki/tls/certs/ +cp rootCA.pem /etc/pki/tls/certs/ ``` - + + +1. Install the SSL module for Apache: ```shell curl -sSL https://packages.sury.org/apache2/README.txt | sudo bash -x @@ -580,12 +626,12 @@ systemctl restart apache2 2. Install your certificates: -Install your certificates (**centreon7.key** and **centreon7.crt** in our example, and the CA certificate) by copying them to the Apache configuration: +Install your certificates (**server.pem** and **server-key.pem** in this example, and the CA certificate) by copying them to the Apache configuration: ```shell -cp centreon7.key /etc/ssl/private/ -cp centreon7.crt /etc/ssl/certs/ -cp ca_demo.crt /etc/ssl/certs/ +cp server-key.pem /etc/ssl/private/ +cp server.pem /etc/ssl/certs/ +cp rootCA.pem /etc/ssl/certs/ ``` @@ -594,21 +640,21 @@ cp ca_demo.crt /etc/ssl/certs/ 3. Back up the previous Apache configuration for Centreon: - + ```shell cp /etc/httpd/conf.d/10-centreon.conf{,.origin} ``` - + ```shell cp /etc/httpd/conf.d/10-centreon.conf{,.origin} ``` - + ```shell cp /etc/apache2/sites-available/centreon.conf{,.origin} @@ -623,19 +669,20 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} > **/usr/share/centreon/examples/centreon.apache.https.conf** - + Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. - + Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. - + Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **\** section. + @@ -655,7 +702,7 @@ ServerTokens Prod This is how the file should look: - + ```apacheconf Define base_uri "/centreon" @@ -678,8 +725,8 @@ ServerTokens Prod SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA SSLHonorCipherOrder On SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/ca.crt - SSLCertificateKeyFile /etc/pki/tls/private/ca.key + SSLCertificateFile /etc/pki/tls/certs/server.pem + SSLCertificateKeyFile /etc/pki/tls/private/server-key.pem Header set X-Frame-Options: "sameorigin" Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict @@ -732,10 +779,10 @@ ServerTokens Prod ``` > Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your -> certificate and key. In our case: **SSLCertificateFile /etc/pki/tls/certs/centreon7.crt** and **SSLCertificateKeyFile /etc/pki/tls/private/centreon7.key**. +> own certificate and key. - + ```apacheconf Define base_uri "/centreon" @@ -758,8 +805,8 @@ ServerTokens Prod SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA SSLHonorCipherOrder On SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/ca.crt - SSLCertificateKeyFile /etc/pki/tls/private/ca.key + SSLCertificateFile /etc/pki/tls/certs/server.pem + SSLCertificateKeyFile /etc/pki/tls/private/server-key.pem Header set X-Frame-Options: "sameorigin" Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict @@ -812,10 +859,10 @@ ServerTokens Prod ``` > Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your -> certificate and key. In our case: **SSLCertificateFile /etc/pki/tls/certs/centreon7.crt** and **SSLCertificateKeyFile /etc/pki/tls/private/centreon7.key**. +> own certificate and key. - + ```apacheconf Define base_uri "/centreon" @@ -838,8 +885,8 @@ ServerTokens Prod SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA SSLHonorCipherOrder On SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/ca.crt - SSLCertificateKeyFile /etc/pki/tls/private/ca.key + SSLCertificateFile /etc/ssl/certs/server.pem + SSLCertificateKeyFile /etc/ssl/private/server-key.pem Header set X-Frame-Options: "sameorigin" Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict @@ -891,8 +938,8 @@ ServerTokens Prod ``` -> Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your -> certificate and key. In our case: **SSLCertificateFile /etc/ssl/certs/centreon7.crt** and **SSLCertificateKeyFile /etc/ssl/private/centreon7.key**. +> Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your own +> certificate and key. @@ -900,7 +947,7 @@ ServerTokens Prod 5. Enable HttpOnly / Secure flags and hide the Apache server signature: - + Edit the **/etc/httpd/conf.d/10-centreon.conf** file and add the following lines before the `` tag: @@ -922,12 +969,12 @@ expose_php = Off * Add the path to the CA certificate that was used to sign the server's certificate: ```text - openssl.cafile=/etc/pki/tls/certs/ca_demo.crt - curl.cainfo=/etc/pki/tls/certs/ca_demo.crt + openssl.cafile=/etc/pki/tls/certs/rootCA.pem + curl.cainfo=/etc/pki/tls/certs/rootCA.pem ``` - + Edit the **/etc/httpd/conf.d/10-centreon.conf** file and add the following lines before the `` tag: @@ -949,12 +996,12 @@ expose_php = Off * Add the path to the CA certificate that was used to sign the server's certificate: ```text - openssl.cafile=/etc/pki/tls/certs/ca_demo.crt - curl.cainfo=/etc/pki/tls/certs/ca_demo.crt + openssl.cafile=/etc/pki/tls/certs/rootCA.pem + curl.cainfo=/etc/pki/tls/certs/rootCA.pem ``` - + Edit the **/etc/apache2/sites-available/centreon.conf** file and add the following lines before the `` tag: @@ -967,11 +1014,11 @@ ServerTokens Prod TraceEnable Off ``` -Edit the **/etc/php/8.2/mods-available/centreon.ini** file and add the following lines: +Edit the **/etc/php/8.4/mods-available/centreon.ini** file and add the following lines: ```text -openssl.cafile=/etc/ssl/certs/ca_demo.crt -curl.cainfo=/etc/ssl/certs/ca_demo.crt +openssl.cafile=/etc/ssl/certs/rootCA.pem +curl.cainfo=/etc/ssl/certs/rootCA.pem ``` @@ -980,7 +1027,7 @@ curl.cainfo=/etc/ssl/certs/ca_demo.crt 6. Hide the default **/icons** directory: - + Edit the **/etc/httpd/conf.d/autoindex.conf** file and comment the following line: @@ -989,7 +1036,7 @@ Edit the **/etc/httpd/conf.d/autoindex.conf** file and comment the following lin ``` - + Edit the **/etc/httpd/conf.d/autoindex.conf** file and comment the following line: @@ -998,9 +1045,7 @@ Edit the **/etc/httpd/conf.d/autoindex.conf** file and comment the following lin ``` - - -Edit the **/etc/apache2/mods-available/autoindex.conf** file and comment the following line: + > The default icons directory is already hidden. @@ -1010,7 +1055,7 @@ Edit the **/etc/apache2/mods-available/autoindex.conf** file and comment the fol 7. You can perform this test to check that Apache is properly configured, by running the following command: - + ```apacheconf apachectl configtest @@ -1023,7 +1068,7 @@ Syntax OK ``` - + ```apacheconf apachectl configtest @@ -1036,7 +1081,7 @@ Syntax OK ``` - + ```apacheconf apache2ctl configtest @@ -1054,7 +1099,7 @@ Syntax OK 8. Restart the Apache and PHP processes to take the new configuration into account: - + ```shell systemctl restart php-fpm httpd @@ -1090,7 +1135,7 @@ If everything is ok, you should have: ``` - + ```shell systemctl restart php-fpm httpd @@ -1126,10 +1171,10 @@ If everything is ok, you should have: ``` - + ```shell -systemctl restart php8.2-fpm apache2 +systemctl restart php8.4-fpm apache2 ``` Then check its status: @@ -1178,7 +1223,7 @@ Replace **127.0.0.1** with the FQDN of your central server in the **/etc/centreo gorgone: tpapi: - name: centreonv2 - base_url: "http://centreon7.localdomain/centreon/api/latest/" + base_url: "https://centreon7.localdomain/centreon/api/latest/" username: "centreon-gorgone" password: "bpltc4aY" - name: clapi @@ -1247,21 +1292,21 @@ To customize the Centreon URI: 1. Edit the Apache configuration file for Centreon Web: - + ```shell vi /etc/httpd/conf.d/10-centreon.conf ``` - + ```shell vi /etc/httpd/conf.d/10-centreon.conf ``` - + ```shell vi /etc/apache2/sites-available/centreon.conf @@ -1279,21 +1324,21 @@ Define base_uri "/centreon" 3. Restart Apache: - + ```shell systemctl restart httpd ``` - + ```shell systemctl restart httpd ``` - + ```shell systemctl restart apache2 @@ -1309,9 +1354,9 @@ It is possible to enable the http2 protocol to improve Centreon's network perfor To use http2, you need to follow these steps: - + -1. [Configure https on Centreon](../installation/installation-of-a-central-server/using-packages.md#step-3-set-up-the-tls-configuration) +1. [Configure https on Centreon](#secure-the-web-server-with-https) 2. Install the nghttp2 module: @@ -1351,7 +1396,7 @@ systemctl restart httpd ``` - + 1. [Configure https on Centreon](#secure-the-web-server-with-https) @@ -1393,7 +1438,7 @@ systemctl restart httpd ``` - + 1. [Configure HTTPS on your Centreon server](#secure-the-web-server-with-https). @@ -1417,7 +1462,7 @@ apt install nghttp2 4. Execute the following commands: ```shell -a2dismod php8.2 +a2dismod php8.4 a2dismod mpm_prefork a2enmod mpm_event a2enmod http2 @@ -1439,21 +1484,21 @@ systemctl restart apache2 1. Install **mod_security** : - + ```shell dnf install mod_security ``` - + ```shell dnf install mod_security ``` - + ```shell apt install libapache2-mod-security2 @@ -1465,24 +1510,24 @@ apt install libapache2-mod-security2 2. Edit the following file and adjust the settings as you want: - + ```shell /etc/httpd/conf.d/mod_security.conf ``` - + ```shell /etc/httpd/conf.d/mod_security.conf ``` - + ```shell -/etc/modsecurity/mod_security.conf +/etc/modsecurity/modsecurity.conf ``` @@ -1490,6 +1535,9 @@ apt install libapache2-mod-security2 We recommend the following configuration: + + + ```text SecResponseBodyAccess Off SecDebugLog /var/log/httpd/modsec_debug.log @@ -1505,24 +1553,63 @@ We recommend the following configuration: SecDataDir /var/lib/mod_security ``` + + + +```text + SecResponseBodyAccess Off + SecDebugLog /var/log/httpd/modsec_debug.log + SecDebugLogLevel 0 + SecAuditEngine RelevantOnly + SecAuditLogRelevantStatus "^(?:5|4(?!01|4))" + SecAuditLogParts ABJDEFHZ + SecAuditLogType Serial + SecAuditLog /var/log/httpd/modsec_audit.log + SecArgumentSeparator & + SecCookieFormat 0 + SecTmpDir /var/lib/mod_security + SecDataDir /var/lib/mod_security +``` + + + + +```text + SecResponseBodyAccess Off + SecDebugLog /var/log/apache2/modsec_debug.log + SecDebugLogLevel 0 + SecAuditEngine RelevantOnly + SecAuditLogRelevantStatus "^(?:5|4(?!01|4))" + SecAuditLogParts ABJDEFHZ + SecAuditLogType Serial + SecAuditLog /var/log/apache2/modsec_audit.log + SecArgumentSeparator & + SecCookieFormat 0 + SecTmpDir /var/lib/mod_security + SecDataDir /var/lib/mod_security +``` + + + + 3. Restart Apache : - + ```shell systemctl restart httpd ``` - + ```shell systemctl restart httpd ``` - + ```shell systemctl restart apache2 @@ -1531,10 +1618,6 @@ systemctl restart apache2 -## Add your certificate to your browser - -If you use a certificate that is not provided by a trusted authority, you must import the CA certificate into your browser. - ## User authentication Centreon offers several methods to authenticate users: @@ -1623,8 +1706,8 @@ Here is a list of services and directories that should be excluded from antiviru * cbd * centreontrapd * gorgoned -* php-fpm -* httpd +* php-fpm (php8.4-fpm on Debian) +* httpd (apache2 on Debian) If you are using one of these connectors, exclude the following services: From a1aa53e152a15a1e8d0609b58d0ff13c857036dc Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 24 Sep 2026 19:12:05 +0200 Subject: [PATCH 090/179] FR corrections (EN in a previous commit) --- .../version-26.10/upgrade/_upgrade-central.mdx | 6 ++++-- versioned_docs/version-26.10/upgrade/_upgrade-central.mdx | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx index 36da84403296..6a242dad4919 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx @@ -75,7 +75,8 @@ Vous devez installer le dépôt Remi, puis basculer le flux PHP de la version {p ```shell dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm rpm -e --nodeps php-sourceguardian-loader -dnf module switch-to php:remi-8.4/common -y +dnf module reset php -y +dnf module enable php:remi-8.4 -y ``` @@ -105,7 +106,8 @@ dnf clean all --enablerepo=* ```shell -dnf update centreon\* php-pecl-gnupg +rpm -e --nodeps php-pecl-gnupg +dnf update -y "centreon*" --exclude=php-pecl-gnupg ``` diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index e2cfcafd815c..9846a67388bd 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -75,7 +75,7 @@ You need to install the Remi repo and the switch the PHP stream from version {pr ```shell dnf install -y https://rpms.remirepo.net/enterprise/remi-release-9.rpm rpm -e --nodeps php-sourceguardian-loader -nf module reset php -y +dnf module reset php -y dnf module enable php:remi-8.4 -y ``` From 36804d3923168ecd3dbd2f6ead12524ac94a20c5 Mon Sep 17 00:00:00 2001 From: smau Date: Fri, 25 Sep 2026 18:29:48 +0200 Subject: [PATCH 091/179] Update MAP installation 26.10 --- .../graph-views/map-web-install.md | 163 ++++++++++-------- 1 file changed, 95 insertions(+), 68 deletions(-) diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index 1f7d176fa622..974f210920de 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -182,7 +182,7 @@ Note that the MAP web interface has the same requirements as the Centreon web in ### Disable SELinux - + During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace **enforcing** by **disabled**. You can also run the following command: @@ -214,7 +214,7 @@ Disabled > - ``SELINUX=permissive`` to make SELinux print warnings instead of enforce security policy. - + During installation, SELinux should be disabled. To do this, edit the file **/etc/selinux/config** and replace **enforcing** by **disabled**. You can also run the following command: @@ -246,9 +246,9 @@ Disabled > - ``SELINUX=permissive`` to make SELinux print warnings instead of enforce security policy. - + -SELinux is not installed on Debian 12, continue. +SELinux is not installed on Debian 13, continue. @@ -302,19 +302,19 @@ in order to create new Centreon Broker output. It will be revoked later ([at thi You need to install the Centreon repository: - + First you need to install an EPEL repository: ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` The command should return results as follows: ```shell Installed: - epel-release-8-17.el8.noarch + epel-release-9-2.el9.noarch Complete! ``` @@ -323,23 +323,25 @@ Then install the Centreon repository: ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` - + First you need to install an EPEL repository: ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm ``` The command should return results as follows: + + ```shell Installed: - epel-release-9-2.el9.noarch + epel-release-10-.el10.noarch Complete! ``` @@ -348,14 +350,16 @@ Then install the Centreon repository: ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo ``` - + Install the following dependencies: + + ```shell apt update && apt install lsb-release ca-certificates apt-transport-https software-properties-common wget gnupg2 curl ``` @@ -363,7 +367,7 @@ apt update && apt install lsb-release ca-certificates apt-transport-https softwa To install the Centreon repository, execute the following command: ```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -397,24 +401,28 @@ Select the tab corresponding to the database you want to use. First you need to add the MariaDB repository: - + ```shell dnf module enable -y mariadb:10.11 ``` - + + + ```shell dnf module enable -y mariadb:10.11 ``` - + + + ```shell -curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=12 --mariadb-server-version="mariadb-10.11" +curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=13 --mariadb-server-version="mariadb-10.11" ``` @@ -423,21 +431,21 @@ curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- - Then install your MariaDB database: - + ```shell dnf install mariadb-server ``` - + ```shell dnf install mariadb-server ``` - + ```shell apt update && apt install mariadb-server @@ -482,21 +490,25 @@ mariadb-secure-installation Depending on your operating system, you may need to add the MySQL repository: - + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el8-1.noarch.rpm -y +dnf install https://dev.mysql.com/get/mysql84-community-release-el9-1.noarch.rpm -y ``` - + + + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el9-1.noarch.rpm -y +dnf install https://dev.mysql.com/get/mysql84-community-release-el10-1.noarch.rpm -y ``` - + + + ```shell wget https://dev.mysql.com/get/mysql-apt-config_0.8.32-1_all.deb @@ -514,18 +526,25 @@ apt update - + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el8-1.noarch.rpm -dnf config-manager --enable mysql-8.4-lts-community -dnf module disable mysql -dnf install mysql-community-server -systemctl start mysqld +dnf install -y mysql-server mysql +dnf install -y centreon-mysql +systemctl enable --now mysqld +echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf +systemctl daemon-reload +systemctl restart mysqld +systemctl list-units --type=service | grep -i mysql +sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld +sudo systemctl start mysqld +sudo systemctl status mysqld ``` - + + + ```shell dnf install -y mysql-server mysql @@ -541,7 +560,7 @@ sudo systemctl status mysqld ``` - + ```shell apt update @@ -576,21 +595,21 @@ mysql_secure_installation Then install the centreon-map-engine package: - + ```shell dnf install centreon-map-engine ``` - + ```shell dnf install centreon-map-engine ``` - + ```shell apt update && apt-get -o Dpkg::Options::="--force-overwrite" install centreon-map-engine @@ -625,21 +644,21 @@ This procedure is to ensure that the configuration file can be used for both MAP 1. Make a backup of the **map.cnf** file: - + ```shell cp /etc/my.cnf.d/map.cnf /etc/my.cnf.d/map.cnf.bk ``` - + ```shell cp /etc/my.cnf.d/map.cnf /etc/my.cnf.d/map.cnf.bk ``` - + ```shell cp /etc/mysql/map.cnf /etc/mysql/map.cnf.bk @@ -651,21 +670,21 @@ This procedure is to ensure that the configuration file can be used for both MAP 2. Install the centreon-map-engine package - + ```shell dnf install centreon-map-engine ``` - + ```shell dnf install centreon-map-engine ``` - + ```shell apt update && apt-get -o Dpkg::Options::="--force-overwrite" install centreon-map-engine @@ -677,21 +696,21 @@ This procedure is to ensure that the configuration file can be used for both MAP 3. Retrieve the configuration file backup: - + ```shell cp /etc/my.cnf.d/map.cnf.bk /etc/my.cnf.d/map.cnf ``` - + ```shell cp /etc/my.cnf.d/map.cnf.bk /etc/my.cnf.d/map.cnf ``` - + ```shell cp /etc/mysql/map.cnf.bk /etc/mysql/map.cnf @@ -707,12 +726,14 @@ This procedure is to ensure that the configuration file can be used for both MAP ``` When installing Centreon MAP Engine server, it will automatically install java -(OpenJDK 17) if needed. +(OpenJDK 25) if needed. + + > Go to this troubleshooting procedure if OpenJDK 17 causes an issue [preventing centreon-map-engine from being installed](./map-web-troubleshooting.md#centreon-map-engine-and-all-its-dependencies-cannot-get-installed-on-alma-linux-8). #### Java requirement - > Ensure a version of Java 17 (or 18) is installed before you start the procedure. + > Ensure a version of Java 25 is installed before you start the procedure. - If you need to check the Java version, enter the following command: @@ -720,14 +741,16 @@ When installing Centreon MAP Engine server, it will automatically install java java -version ``` - - If you need to upgrade the Java installation to Java 17 (or 18), go to the [Oracle official download](https://www.oracle.com/java/technologies/downloads/#java17) page. + - - If several Java versions are installed, you need to activate the right version. Display the installed versions using the following command and select the Java 17 (or 18) version: + - If you need to upgrade the Java installation to Java 25, go to the [Oracle official download](https://www.oracle.com/java/technologies/downloads/#java25) page. + + - If several Java versions are installed, you need to activate the right version. Display the installed versions using the following command and select the Java 25 version: ```shell sudo update-alternatives --config java ``` - - If you need to use your platform in HTTPS, you will have to generate a keystore file for the Java 17 (or 18) version ([see the procedure](./secure-your-map-platform.md#httpstls-configuration-with-a-recognized-key)). + - If you need to use your platform in HTTPS, you will have to generate a keystore file for the Java 25 version ([see the procedure](./secure-your-map-platform.md#httpstls-configuration-with-a-recognized-key)). @@ -741,21 +764,21 @@ This procedure is to ensure that the configuration file can be used for both MAP 1. Make a backup of the **map.cnf** file: - + ```shell cp /etc/my.cnf.d/map.cnf /etc/my.cnf.d/map.cnf.bk ``` - + ```shell cp /etc/my.cnf.d/map.cnf /etc/my.cnf.d/map.cnf.bk ``` - + ```shell cp /etc/mysql/map.cnf /etc/mysql/map.cnf.bk @@ -767,21 +790,21 @@ This procedure is to ensure that the configuration file can be used for both MAP 2. Install the centreon-map-engine package - + ```shell dnf install centreon-map-engine ``` - + ```shell dnf install centreon-map-engine ``` - + ```shell apt update && apt-get -o Dpkg::Options::="--force-overwrite" install centreon-map-engine @@ -793,21 +816,21 @@ This procedure is to ensure that the configuration file can be used for both MAP 3. Retrieve the configuration file backup: - + ```shell cp /etc/my.cnf.d/map.cnf.bk /etc/my.cnf.d/map.cnf ``` - + ```shell cp /etc/my.cnf.d/map.cnf.bk /etc/my.cnf.d/map.cnf ``` - + ```shell cp /etc/mysql/map.cnf.bk /etc/mysql/map.cnf @@ -823,12 +846,14 @@ This procedure is to ensure that the configuration file can be used for both MAP ``` When installing Centreon MAP Engine server, it will automatically install java -(OpenJDK 17) if needed. +(OpenJDK 25) if needed. + + > Go to this troubleshooting procedure if OpenJDK 17 causes an issue [preventing centreon-map-engine from being installed](./map-web-troubleshooting.md#centreon-map-engine-and-all-its-dependencies-cannot-get-installed-on-alma-linux-8). #### Java requirement - > Ensure a version of Java 17 (or 18) is installed before you start the procedure. + > Ensure a version of Java 25 is installed before you start the procedure. - If you need to check the Java version, enter the following command: @@ -836,14 +861,16 @@ When installing Centreon MAP Engine server, it will automatically install java java -version ``` - - If you need to upgrade the Java installation to Java 17 (or 18), go to the [Oracle official download](https://www.oracle.com/java/technologies/downloads/#java17) page. + - - If several Java versions are installed, you need to activate the right version. Display the installed versions using the following command and select the Java 17 (or 18) version: + - If you need to upgrade the Java installation to Java 25, go to the [Oracle official download](https://www.oracle.com/java/technologies/downloads/#java25) page. + + - If several Java versions are installed, you need to activate the right version. Display the installed versions using the following command and select the Java 25 version: ```shell sudo update-alternatives --config java ``` - - If you need to use your platform in HTTPS, you will have to generate a keystore file for the Java 17 (or 18) version ([see the procedure](./secure-your-map-platform.md#httpstls-configuration-with-a-recognized-key)). + - If you need to use your platform in HTTPS, you will have to generate a keystore file for the Java 25 version ([see the procedure](./secure-your-map-platform.md#httpstls-configuration-with-a-recognized-key)). @@ -1031,21 +1058,21 @@ Install the Centreon Business repository. You can find this on the 1. From your terminal, run the following command on the central server: - + ```shell sudo dnf install centreon-map-web-client ``` - + ```shell sudo dnf install centreon-map-web-client ``` - + ```shell sudo apt install centreon-map-web-client From 706c443375fb64ab42696327cc39364f2e880f41 Mon Sep 17 00:00:00 2001 From: smau Date: Mon, 28 Sep 2026 17:02:01 +0200 Subject: [PATCH 092/179] MAP update & upgrade topics to review (EN only) --- .../graph-views/map-web-update.md | 54 +++----------- .../graph-views/map-web-upgrade.md | 70 ++++++------------- 2 files changed, 33 insertions(+), 91 deletions(-) diff --git a/versioned_docs/version-26.10/graph-views/map-web-update.md b/versioned_docs/version-26.10/graph-views/map-web-update.md index 94e6aea39294..938afa0c65ce 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-update.md +++ b/versioned_docs/version-26.10/graph-views/map-web-update.md @@ -14,10 +14,10 @@ Use the following procedure to update your MAP version: sudo systemctl stop centreon-map-engine ``` -2. Update the packages by running this command on the machine(s) hosting the central service and the Centreon MAP service: +2. Update the packages by running these commands on the machines hosting the central service and the Centreon MAP service: - + - On the central server: @@ -32,7 +32,7 @@ Use the following procedure to update your MAP version: ``` - + - On the central server: @@ -47,55 +47,19 @@ Use the following procedure to update your MAP version: ``` - + - - If MAP only is installed: - - On the central server: + - On the central server: ``` shell - sudo apt install centreon-map-web-client + sudo apt install --only-upgrade centreon-map-web-client ``` - On the MAP server: + - On the MAP server: ``` shell - sudo apt install centreon-map-engine + sudo apt install --only-upgrade centreon-map-engine ``` - - - If MAP and MAP Legacy are installed on the same server: - - - Make a backup of the **map.cnf** file: - - ```shell - cp /etc/my.cnf.d/map.cnf /etc/my.cnf.d/map.cnf.bk - ``` - - - Update the centreon-map-engine package - - On the central server: - - ``` shell - sudo apt install -o Dpkg::Options::="--force-overwrite" centreon-map-web-client - ``` - - On the MAP server: - - ``` shell - sudo apt install -o Dpkg::Options::="--force-overwrite" centreon-map-engine - ``` - - - Retrieve the configuration file backup: - - ```shell - cp /etc/my.cnf.d/map.cnf.bk /etc/my.cnf.d/map.cnf - ``` - - - Answer **Y** when prompted. Then restart MySQL: - - ```shell - systemctl restart mariadb - ``` @@ -104,6 +68,8 @@ Use the following procedure to update your MAP version: 4. Finalize the update of the module and the widget in the Centreon interface **Administration > Extensions > Manager**. + > An update button is displayed when an update is available. Click it to update the module, then do the same for the widget. + 5. Restart the **centreon-map-engine** service using the following command: ```shell diff --git a/versioned_docs/version-26.10/graph-views/map-web-upgrade.md b/versioned_docs/version-26.10/graph-views/map-web-upgrade.md index 1c1a92725162..6a43a2353139 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-upgrade.md +++ b/versioned_docs/version-26.10/graph-views/map-web-upgrade.md @@ -14,9 +14,22 @@ import TabItem from '@theme/TabItem'; ## Prerequisites +### Check your operating system + +Make sure that the central server and the MAP server run an [operating system supported by this version](../installation/compatibility.md#operating-systems). + +If one of your servers runs an operating system that is no longer supported, you cannot upgrade it directly. First migrate your platform to a supported operating system: + +- For the central server, see [Migrating a platform](../migrate/introduction.md). +- For the MAP server, see [Migrating the extension](map-web-migrate.md). + +### Check your database version + +Make sure that your database uses a [DBMS version supported by this version](../installation/compatibility.md#dbms). If it does not, upgrade it before you upgrade MAP. See [Upgrading MariaDB](../upgrade/upgrade-mariadb.md) or [Upgrading MySQL](../upgrade/upgrade-mysql.md). + ### 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](../security/key-rotation.md#existing-installation), to remove the old key and install the new one. +For security reasons, the keys used to sign Centreon RPMs are rotated regularly. If your platform still uses a previous key, go through the [key rotation procedure](../security/key-rotation.md#existing-installation) to remove the old key and install the new one. ## Update the package @@ -26,11 +39,10 @@ For security reasons, the keys used to sign Centreon RPMs are rotated regularly. sudo systemctl stop centreon-map-engine ``` -2. In order to update the Centreon MAP module, execute the -following commands: +2. To update the Centreon MAP module, run the following commands: - + - On the central server: @@ -39,12 +51,13 @@ following commands: ``` - On the MAP server: + ``` shell sudo dnf update centreon-map-engine ``` - + - On the central server: @@ -53,60 +66,25 @@ following commands: ``` - On the MAP server: + ``` shell sudo dnf update centreon-map-engine ``` - + - - If MAP only is installed: - - On the central server: + - On the central server: ``` shell sudo apt install --only-upgrade centreon-map-web-client ``` - On the MAP server: + - On the MAP server: ``` shell sudo apt install --only-upgrade centreon-map-engine ``` - - - If MAP and MAP Legacy are installed on the same server: - - - Make a backup of the **map.cnf** file: - - ```shell - cp /etc/my.cnf.d/map.cnf /etc/my.cnf.d/map.cnf.bk - ``` - - - Update the centreon-map-engine package - - On the central server: - - ``` shell - sudo apt install -o Dpkg::Options::="--force-overwrite" centreon-map-web-client - ``` - - On the MAP server: - - ``` shell - sudo apt install -o Dpkg::Options::="--force-overwrite" centreon-map-engine - ``` - - - Retrieve the configuration file backup: - - ```shell - cp /etc/my.cnf.d/map.cnf.bk /etc/my.cnf.d/map.cnf - ``` - - - Answer **Y** when prompted. Then restart MySQL: - - ```shell - systemctl restart mariadb - ``` @@ -115,12 +93,10 @@ following commands: 4. Finalize the update of the module and the widget in the Centreon interface **Administration > Extensions > Manager**. - > An orange update button is visible, indicating that an update is available. Click on it to update the module, and do the same for the widget. + > An update button is displayed when an update is available. Click it to update the module, then do the same for the widget. 5. Restart the **centreon-map-engine** service using the following command: ```shell sudo systemctl start centreon-map-engine ``` - -6. When upgrading to version 24.04 and above, you have to upgrade MariaDB to version 10.11. See [Upgrading MariaDB](../upgrade/upgrade-mariadb.md). From 69ed28beb3970874d82c07b380f51e7cd9372519 Mon Sep 17 00:00:00 2001 From: smau Date: Mon, 28 Sep 2026 18:34:40 +0200 Subject: [PATCH 093/179] Update BAM install/update/upgrade in 26.10 (EN only) --- .../version-26.10/service-mapping/install.md | 24 ++++++++--------- .../version-26.10/service-mapping/update.md | 14 +++++----- .../version-26.10/service-mapping/upgrade.md | 26 +++++++------------ 3 files changed, 27 insertions(+), 37 deletions(-) diff --git a/versioned_docs/version-26.10/service-mapping/install.md b/versioned_docs/version-26.10/service-mapping/install.md index 23f01a8b69ee..dbbf7ea85348 100644 --- a/versioned_docs/version-26.10/service-mapping/install.md +++ b/versioned_docs/version-26.10/service-mapping/install.md @@ -16,34 +16,34 @@ import TabItem from '@theme/TabItem'; See the [software requirements](../installation/prerequisites.md#characteristics-of-the-servers). Install BAM on the central server. -The central server and Centreon BAM must be installed in the same major versions (i.e. both in 26.10.x). +The central server and Centreon BAM must be installed in the same major version (e.g. both in 26.10.x). If you want to be able to view the Business activities monitored by a remote server, install BAM on the remote server too. When BAM is installed on a remote server, the Business activities will only include the resources monitored by the remote server. ## Installation ### Install the package -Add the Centreon Business repository; you can find it on the +Add the Centreon Business repository. You can find it on the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). -And install the package using the following command: +Then install the package using the following command: - + ``` shell dnf install centreon-bam-server ``` - + ``` shell dnf install centreon-bam-server ``` - + ```shell apt update && apt install centreon-bam-server @@ -61,27 +61,27 @@ using the interface. ### Install the interface -Go to the **Administration > Extension > Manager** menu and click the install +Go to the **Administration > Extensions > Manager** menu and click the install button for the following modules: - License Manager (if not yet installed) - Business Activity Monitoring -Once installed and the license added, the module will have a green banner that indicates +Once the module is installed and the license added, the module card displays the license expiry date: ![image](../assets/service-mapping/installation/install-web-step-2.png) -> If you are using MariaDB replication for your monitoring databases, +> If you are using replication for your monitoring databases, > installing Centreon BAM generates a view. You need to exclude it from -> replication by adding the following line on the my.cnf file of the -> slave server: +> replication by adding the following line to the my.cnf file of the +> replica server: > > ``` text > replicate-ignore-table=centreon.mod_bam_view_kpi > ``` > -> Create the view manually on the slave server [using this file](view_creation.sql), by executing the +> Create the view manually on the replica server [using this file](view_creation.sql), by executing the > following command: > > ``` shell diff --git a/versioned_docs/version-26.10/service-mapping/update.md b/versioned_docs/version-26.10/service-mapping/update.md index 0a91f4c812eb..0d8b46800f9e 100644 --- a/versioned_docs/version-26.10/service-mapping/update.md +++ b/versioned_docs/version-26.10/service-mapping/update.md @@ -8,25 +8,24 @@ import TabItem from '@theme/TabItem'; ## Update the package -In order to update the Centreon BAM module, execute the -following command: +To update the Centreon BAM module, run the following command: - + ```shell dnf update centreon-bam-server ``` - + ```shell dnf update centreon-bam-server ``` - + ```shell apt update && apt install --only-upgrade centreon-bam-server @@ -37,7 +36,6 @@ apt update && apt install --only-upgrade centreon-bam-server ## Update through the interface -Log on to the Centreon web interface and go to `Administration > Extension > -Manager`. +Log on to the Centreon web interface and go to **Administration > Extensions > Manager**. -Click the orange button to update the module, and do the same for the widget. +An update button is displayed when an update is available. Click it to update the module, then do the same for the widget. diff --git a/versioned_docs/version-26.10/service-mapping/upgrade.md b/versioned_docs/version-26.10/service-mapping/upgrade.md index b38e5b4154f1..322b4265bc67 100644 --- a/versioned_docs/version-26.10/service-mapping/upgrade.md +++ b/versioned_docs/version-26.10/service-mapping/upgrade.md @@ -8,11 +8,6 @@ import TabItem from '@theme/TabItem'; ## Prerequisites -### License - -When upgrading from a version below 18.10 to one above 18.10, you must obtain -a new license from Centreon support. - ### Upgrade Centreon web on your central server See the [corresponding chapter](../upgrade/introduction.md). @@ -20,37 +15,35 @@ See the [corresponding chapter](../upgrade/introduction.md). ### Install the Business repository If you are upgrading to a new major or minor version (i.e.: A.B.x with A or B that -changes), you need to contact our Support service to retrieve the new -repository. +changes), you need to install the new Business repository. You can find its address on the [support portal](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). ### 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](../security/key-rotation.md#existing-installation) to remove the old key and install the new one. +For security reasons, the keys used to sign Centreon RPMs are rotated regularly. If your platform still uses a previous key, go through the [key rotation procedure](../security/key-rotation.md#existing-installation) to remove the old key and install the new one. ## Update the package -In order to update the Centreon BAM module using an RPM package, execute the -following command: +To update the Centreon BAM module, run the following command: - + ```shell dnf update centreon-bam-server ``` - + ```shell dnf update centreon-bam-server ``` - + ```shell -apt install --only-upgrade centreon-bam-server +apt update && apt install --only-upgrade centreon-bam-server ``` @@ -58,7 +51,6 @@ apt install --only-upgrade centreon-bam-server ## Update through the interface -Log on to the Centreon web interface and go to `Administration > Extension > -Manager`. +Log on to the Centreon web interface and go to **Administration > Extensions > Manager**. -Click the orange button to update the module, and do the same for the widget. +An update button is displayed when an update is available. Click it to update the module, then do the same for the widget. From e22eec50596a537190abaacbf601bbaf26894d86 Mon Sep 17 00:00:00 2001 From: smau Date: Tue, 29 Sep 2026 16:09:56 +0200 Subject: [PATCH 094/179] Add FR version (MAP&BAM install/update/upgrade) --- .../graph-views/map-web-install.md | 251 +++++++++--------- .../graph-views/map-web-update.md | 54 +--- .../graph-views/map-web-upgrade.md | 79 ++---- .../version-26.10/service-mapping/install.md | 38 +-- .../version-26.10/service-mapping/update.md | 18 +- .../version-26.10/service-mapping/upgrade.md | 35 +-- .../graph-views/map-web-install.md | 19 +- 7 files changed, 202 insertions(+), 292 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index 59aead7fdce1..3f5daea9192f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -8,7 +8,7 @@ import TabItem from '@theme/TabItem'; Cette page décrit comment installer Centreon MAP. Il est recommandé d'installer MAP sur un serveur dédié. Toutefois, si vous ne disposez pas de gros volumes de données, vous pouvez l'installer sur le serveur central. -> Si vous prévoyez d'utiliser MAP en HTTPS, veuillez noter que la sécurisation du protocole HTTPS nécessite une configuration tant sur la plateforme Centreon que sur le serveur MAP. Il est donc préférable d'en tenir compte avant de commencer l'installation. Reportez-vous à la section [Sécurisation de MAP en HTTPS](#sécuriser-map-en-https) pour connaître la procédure complète. +> Si vous prévoyez d'utiliser MAP en HTTPS, veuillez noter que la sécurisation du protocole HTTPS nécessite une configuration tant sur la plateforme Centreon que sur le serveur MAP. Il est donc préférable d'en tenir compte avant de commencer l'installation. Reportez-vous à la section [Sécuriser MAP en HTTPS](#sécuriser-map-en-https) pour connaître la procédure complète. ## Licence @@ -135,7 +135,7 @@ Votre serveur MAP doit être partitionné de la manière suivante : | CPU | 8 vCPU | | RAM | 18 Go | -Voici comment votre serveur MAP doit être partitionné : +Votre serveur MAP doit être partitionné de la manière suivante : | Groupe de volumes (LVM) | Partition | Description | Taille | | ----------------------- | ------------------- | ----------------------------------- | ------ | @@ -144,7 +144,7 @@ Voici comment votre serveur MAP doit être partitionné : | vg_root | swap | swap | 8 Go | | vg_root | /var/log | contient tous les fichiers de log | 10 Go | | vg_data | /var/lib/mysql | base de données | 5 Go | -| vg_data | | espace libre (non alloué) | 2 Go | +| vg_data | | Espace libre (non alloué) | 2 Go | @@ -166,18 +166,18 @@ Pour de grosses volumétries de données, contactez votre commercial Centreon. #### Licence -Le serveur nécessite que la licence soit disponible et valide sur le serveur central de Centreon. Pour ce faire, vous devez contacter le [support Centreon](https://support.centreon.com/) pour obtenir et installer votre clé de licence. +L'interface web nécessite que la licence soit disponible et valide sur le serveur central de Centreon. Pour ce faire, vous devez contacter le [support Centreon](https://support.centreon.com/) pour obtenir et installer votre clé de licence. #### Compatibilité -Notez que l'interface web de MAP a les mêmes prérequis que l'interface web Centreon. Voir les prérequis pour la compatibilité des navigateurs web [ici](../installation/compatibility.md#interface-web-de-centreon). +Notez que l'interface web de MAP a les mêmes prérequis que l'interface web Centreon. Voir les prérequis pour la compatibilité des navigateurs web [ici](../installation/prerequisites.md). ## Pré-installation ### Désactiver SELinux - - + + Pendant l'installation, SELinux doit être désactivé. Éditez le fichier **/etc/selinux/config** et remplacez **enforcing** par **disabled**, ou bien @@ -193,11 +193,10 @@ Redémarrez votre système d'exploitation pour prendre en compte le changement. reboot ``` -Après le redémarrage, une vérification rapide permet de confirmer le statut de -SELinux : +Après le démarrage du système, effectuez une vérification rapide de l'état de SELinux : ```shell -$ getenforce +getenforce ``` Vous devriez obtenir ce résultat : @@ -211,7 +210,7 @@ Disabled > - ``SELINUX=permissive`` pour que les erreurs d’accès soient enregistrées dans les logs, mais l’accès ne sera pas bloqué. - + Pendant l'installation, SELinux doit être désactivé. Éditez le fichier **/etc/selinux/config** et remplacez **enforcing** par **disabled**, ou bien @@ -244,9 +243,9 @@ Disabled > - ``SELINUX=permissive`` pour que les erreurs d’accès soient enregistrées dans les logs, mais l’accès ne sera pas bloqué. - + -SELinux n'est pas installé sur Debian 12, continuez. +SELinux n'est pas installé sur Debian 13, continuez. @@ -277,7 +276,7 @@ Excluez l'utilisateur de la politique d'expiration du mot de passe sur la page * ### Étape 2 : créer un utilisateur MySQL -Créez un utilisateur dans l'instance mysql hébergeant les bases de données **centreon** et **centreon_storage** : +Depuis le terminal du serveur central, créez un utilisateur dans l'instance MySQL hébergeant les bases de données **centreon** et **centreon_storage** : > Nous vous recommandons vivement de définir un mot de passe plus sécurisé. @@ -293,22 +292,22 @@ Le privilège INSERT ne sera utilisé que pendant le processus d'installation af #### Installation des paquets -Si vous installez votre serveur Centreon MAP à partir d'une "installation fraîche", vous devez installer le dépôt Centreon : +Vous devez installer le dépôt Centreon : - + Vous devez d'abord installer le dépôt EPEL : ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` La commande doit retourner des résultats comme suit : ```shell Installed: - epel-release-8-17.el8.noarch + epel-release-9-2.el9.noarch Complete! ``` @@ -317,23 +316,25 @@ Ensuite installez le dépôt Centreon : ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo ``` - + Vous devez d'abord installer le dépôt EPEL : ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm ``` La commande doit retourner des résultats comme suit : + + ```shell Installed: - epel-release-9-2.el9.noarch + epel-release-10-.el10.noarch Complete! ``` @@ -342,14 +343,16 @@ Ensuite installez le dépôt Centreon : ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo ``` - + Installez les dépendances suivantes : + + ```shell apt update && apt install lsb-release ca-certificates apt-transport-https software-properties-common wget gnupg2 curl ``` @@ -357,7 +360,7 @@ apt update && apt install lsb-release ca-certificates apt-transport-https softwa Pour installer le dépôt Centreon, exécutez la commande suivante : ```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-26.10-stable.list echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list ``` @@ -376,11 +379,9 @@ wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg Installez le dépôt Centreon Business, vous pouvez le trouver sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). -#### Installation du serveur MAP Engine - > Vous avez deux possibilités pour l'installation : - [sur un nouveau serveur](#étape-3---option-1--installation-de-map-engine-sur-un-nouveau-serveur) (sans paquets Centreon MAP existants), - - [sur un serveur Centreon MAP Legacy](#étape-3---option-2--installation-de-map-engine-sur-un-serveur-map-legacy-existant). + - [sur un serveur Centreon MAP Legacy existant](#étape-3---option-2--installation-de-map-engine-sur-un-serveur-map-legacy-existant). ### Étape 3 - Option 1 : installation de MAP Engine sur un nouveau serveur @@ -389,27 +390,27 @@ Sélectionnez l'onglet correspondant au type de base de données à utiliser. -Vous devez d'abord installer le dépôt MariaDB : +Vous devez d'abord ajouter le dépôt MariaDB : - + ```shell dnf module enable -y mariadb:10.11 ``` - + ```shell dnf module enable -y mariadb:10.11 ``` - + ```shell -curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=12 --mariadb-server-version="mariadb-10.11" +curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=13 --mariadb-server-version="mariadb-10.11" ``` @@ -418,21 +419,21 @@ curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- - Ensuite installez le serveur MariaDB : - + ```shell dnf install mariadb-server ``` - + ```shell dnf install mariadb-server ``` - + ```shell apt update && apt install mariadb-server @@ -444,7 +445,7 @@ apt update && apt install mariadb-server > /etc/mysql/mariadb.conf.d/50-server.cnf > ``` > -> Définir le paramètre **bind-address** à **0.0.0.0.** et redémarrez MariaDB. +> Définissez le paramètre **bind-address** à **0.0.0.0** et redémarrez MariaDB. > > ```shell > systemctl restart mariadb @@ -467,31 +468,33 @@ mariadb-secure-installation ``` * Répondez **oui** à toutes les questions, sauf à "Disallow root login remotely?". -* Il est obligatoire de définir un mot de passe pour l'utilisateur root de la base de données. Vous aurez besoin de ce mot de passe pendant l'[installation web](../installation/web-and-post-installation.md). +* Il est obligatoire de définir un mot de passe pour l'utilisateur **root** de la base de données. Vous aurez besoin de ce mot de passe pendant l'[installation web](../installation/web-and-post-installation.md). -> Pour plus d'informations, veuillez consulter la [documentation officielle](https://mariadb.com/kb/en/mysql_secure_installation/). +> Pour plus d'informations, veuillez consulter la [documentation officielle de MariaDB](https://mariadb.com/kb/en/mysql_secure_installation/). -Vous devez d'abord installer le dépôt MySQL : +Selon votre système d'exploitation, vous devrez peut-être ajouter le dépôt MySQL : - + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el8-1.noarch.rpm -y +dnf install https://dev.mysql.com/get/mysql84-community-release-el9-1.noarch.rpm -y ``` - + + + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el9-1.noarch.rpm -y +dnf install https://dev.mysql.com/get/mysql84-community-release-el10-1.noarch.rpm -y ``` - + ```shell wget https://dev.mysql.com/get/mysql-apt-config_0.8.32-1_all.deb @@ -509,18 +512,23 @@ apt update - + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el8-1.noarch.rpm -dnf config-manager --enable mysql-8.4-lts-community -dnf module disable mysql -dnf install mysql-community-server -systemctl start mysqld +dnf install -y mysql-server mysql +dnf install -y centreon-mysql +systemctl enable --now mysqld +echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf +systemctl daemon-reload +systemctl restart mysqld +systemctl list-units --type=service | grep -i mysql +sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld +sudo systemctl start mysqld +sudo systemctl status mysqld ``` - + ```shell dnf install -y mysql-server mysql @@ -536,7 +544,7 @@ sudo systemctl status mysqld ``` - + ```shell apt update @@ -562,30 +570,30 @@ Il est obligatoire de sécuriser l'accès root de la base de données avant d'in mysql_secure_installation ``` -* Répondez oui à toutes les questions, sauf à "Disallow root login remotely?". -* Il est obligatoire de définir un mot de passe pour l'utilisateur root de la base de données. Vous aurez besoin de ce mot de passe pendant l'[installation web](../installation/web-and-post-installation.md). +* Répondez **oui** à toutes les questions, sauf à "Disallow root login remotely?". +* Il est obligatoire de définir un mot de passe pour l'utilisateur **root** de la base de données. Vous aurez besoin de ce mot de passe pendant l'[installation web](../installation/web-and-post-installation.md). -Installez les paquets de **centreon-map-engine** : +Ensuite, installez le paquet **centreon-map-engine** : - + ```shell dnf install centreon-map-engine ``` - + ```shell dnf install centreon-map-engine ``` - + ```shell apt update && apt-get -o Dpkg::Options::="--force-overwrite" install centreon-map-engine @@ -597,7 +605,7 @@ Installez les paquets de **centreon-map-engine** : > /etc/mysql/mysql.conf.d/mysqld.cnf > ``` > -> Définir le paramètre **bind-address** à **0.0.0.0.** et redémarrez MySQL. +> Définissez le paramètre **bind-address** à **0.0.0.0** et redémarrez MySQL : > > ```shell > sudo service mysql restart @@ -611,7 +619,7 @@ Installez les paquets de **centreon-map-engine** : -> Si vous avez déjà MAP Legacy et que vous installez MAP Engine sur le même serveur, vous devez suivre la procédure suivante. Si non, passez à l'[étape 3 - Option 1 : installation du serveur MAP Engine sur un nouveau serveur](#étape-3---option-1--installation-de-map-engine-sur-un-nouveau-serveur). +> Si vous avez déjà MAP Legacy et que vous installez MAP Engine sur le même serveur, vous devez suivre la procédure suivante. Si non, passez à l'[étape 3 - Option 1 : installation de MAP Engine sur un nouveau serveur](#étape-3---option-1--installation-de-map-engine-sur-un-nouveau-serveur). > Vous pouvez utiliser la base de données MariaDB existante de Centreon MAP Legacy pour le nouveau serveur MAP Engine. Il n'est donc pas nécessaire d'installer une nouvelle base de données. @@ -620,21 +628,21 @@ Cette procédure permet de s'assurer que le fichier de configuration peut être 1. Faites une sauvegarde du fichier **map.cnf** : - + ```shell cp /etc/my.cnf.d/map.cnf /etc/my.cnf.d/map.cnf.bk ``` - + ```shell cp /etc/my.cnf.d/map.cnf /etc/my.cnf.d/map.cnf.bk ``` - + ```shell cp /etc/mysql/map.cnf /etc/mysql/map.cnf.bk @@ -643,24 +651,24 @@ Cette procédure permet de s'assurer que le fichier de configuration peut être -2. Installez les paquets de **centreon-map-engine** : +2. Installez le paquet **centreon-map-engine** : - + ```shell dnf install centreon-map-engine ``` - + ```shell dnf install centreon-map-engine ``` - + ```shell apt update && apt-get -o Dpkg::Options::="--force-overwrite" install centreon-map-engine @@ -672,21 +680,21 @@ Cette procédure permet de s'assurer que le fichier de configuration peut être 3. Récupérez la sauvegarde du fichier de configuration : - + ```shell cp /etc/my.cnf.d/map.cnf.bk /etc/my.cnf.d/map.cnf ``` - + ```shell cp /etc/my.cnf.d/map.cnf.bk /etc/my.cnf.d/map.cnf ``` - + ```shell cp /etc/mysql/map.cnf.bk /etc/mysql/map.cnf @@ -695,18 +703,16 @@ Cette procédure permet de s'assurer que le fichier de configuration peut être -4. Répondez **Y**. Ensuite redémarrez MariaDB : +4. Répondez **Y** lorsque le système vous le demande. Ensuite redémarrez MariaDB : ```shell systemctl restart mariadb ``` -Lors de l'installation du serveur Centreon MAP Engine, java (OpenJDK 17) sera automatiquement installé, si nécessaire. - -> Suivez cette procédure de dépannage si OpenJDK 17 cause un incident [empêchant l'installation de centreon-map-engine](./map-web-troubleshooting.md#centreon-map-engine-et-toutes-ses-dépendances-ne-peuvent-pas-être-installés-sur-alma-linux-8). +Lors de l'installation du serveur Centreon MAP Engine, java (OpenJDK 25) sera automatiquement installé, si nécessaire. #### Prérequis Java - > Assurez-vous qu'une version de Java 17 (ou 18) est installée avant de commencer la procédure. + > Assurez-vous qu'une version de Java 25 est installée avant de commencer la procédure. - Pour vérifier quelle version de Java est installée, entrez la commande suivante : @@ -714,42 +720,42 @@ Lors de l'installation du serveur Centreon MAP Engine, java (OpenJDK 17) sera au java -version ``` - - Pour une mise à jour de Java en version 17 (ou 18), allez sur la [page officielle de téléchargement d'Oracle](https://www.oracle.com/java/technologies/downloads/#java17). + - Pour une mise à jour de Java en version 25, allez sur la [page officielle de téléchargement d'Oracle](https://www.oracle.com/java/technologies/downloads/#java25). - - Si plusieurs versions de Java sont installées, vous devez activer la bonne version. Affichez les versions installées avec la commande suivante puis sélectionnez la version 17 (ou 18) : + - Si plusieurs versions de Java sont installées, vous devez activer la bonne version. Affichez les versions installées avec la commande suivante puis sélectionnez la version 25 : ```shell sudo update-alternatives --config java ``` - - Si vous souhaitez configurer votre plateforme en HTTPS, vous aurez besoin de générer un fichier keystore pour la version 17 de Java (ou 18) ([voir procédure](./secure-your-map-platform.md#configuration-httpstls-avec-une-clé-auto-signée)). + - Si vous souhaitez configurer votre plateforme en HTTPS, vous aurez besoin de générer un fichier keystore pour la version 25 de Java ([voir procédure](./secure-your-map-platform.md#configuration-httpstls-avec-une-clé-reconnue)). -> Si vous avez déjà MAP Legacy et que vous installez MAP Engine sur le même serveur, vous devez suivre la procédure suivante. Si non, passez à l'[étape 3 - Option 1 : installation du serveur MAP Engine sur un nouveau serveur](#étape-3---option-1--installation-de-map-engine-sur-un-nouveau-serveur). +> Si vous avez déjà MAP Legacy et que vous installez MAP Engine sur le même serveur, vous devez suivre la procédure suivante. Si non, passez à l'[étape 3 - Option 1 : installation de MAP Engine sur un nouveau serveur](#étape-3---option-1--installation-de-map-engine-sur-un-nouveau-serveur). -> Vous pouvez utiliser la base de données MariaDB existante de Centreon MAP Legacy pour le nouveau serveur MAP Engine. Il n'est donc pas nécessaire d'installer une nouvelle base de données. +> Vous pouvez utiliser la base de données MySQL existante de Centreon MAP Legacy pour le nouveau serveur MAP Engine. Il n'est donc pas nécessaire d'installer une nouvelle base de données. Cette procédure permet de s'assurer que le fichier de configuration peut être utilisé à la fois pour MAP Engine et MAP Legacy. 1. Faites une sauvegarde du fichier **map.cnf** : - + ```shell cp /etc/my.cnf.d/map.cnf /etc/my.cnf.d/map.cnf.bk ``` - + ```shell cp /etc/my.cnf.d/map.cnf /etc/my.cnf.d/map.cnf.bk ``` - + ```shell cp /etc/mysql/map.cnf /etc/mysql/map.cnf.bk @@ -758,24 +764,24 @@ Cette procédure permet de s'assurer que le fichier de configuration peut être -2. Installez les paquets de centreon-map-engine : +2. Installez le paquet **centreon-map-engine** : - + ```shell dnf install centreon-map-engine ``` - + ```shell dnf install centreon-map-engine ``` - + ```shell apt update && apt-get -o Dpkg::Options::="--force-overwrite" install centreon-map-engine @@ -787,21 +793,21 @@ Cette procédure permet de s'assurer que le fichier de configuration peut être 3. Récupérez la sauvegarde du fichier de configuration : - + ```shell cp /etc/my.cnf.d/map.cnf.bk /etc/my.cnf.d/map.cnf ``` - + ```shell cp /etc/my.cnf.d/map.cnf.bk /etc/my.cnf.d/map.cnf ``` - + ```shell cp /etc/mysql/map.cnf.bk /etc/mysql/map.cnf @@ -810,18 +816,16 @@ Cette procédure permet de s'assurer que le fichier de configuration peut être -4. Répondez **Y**. Ensuite redémarrez MySQL : +4. Répondez **Y** lorsque le système vous le demande. Ensuite redémarrez MySQL : ```shell systemctl restart mysql ``` -Lors de l'installation du serveur Centreon MAP Engine, java (OpenJDK 17) sera automatiquement installé, si nécessaire. - -> Suivez cette procédure de dépannage si OpenJDK 17 cause un incident [empêchant l'installation de centreon-map-engine](./map-web-troubleshooting.md#centreon-map-engine-et-toutes-ses-dépendances-ne-peuvent-pas-être-installés-sur-alma-linux-8). +Lors de l'installation du serveur Centreon MAP Engine, java (OpenJDK 25) sera automatiquement installé, si nécessaire. #### Prérequis Java - > Assurez-vous qu'une version de Java 17 (ou 18) est installée avant de commencer la procédure. + > Assurez-vous qu'une version de Java 25 est installée avant de commencer la procédure. - Pour vérifier quelle version de Java est installée, entrez la commande suivante : @@ -829,14 +833,14 @@ Lors de l'installation du serveur Centreon MAP Engine, java (OpenJDK 17) sera au java -version ``` - - Pour une mise à jour de Java en version 17 (ou 18), allez sur la [page officielle de téléchargement d'Oracle](https://www.oracle.com/java/technologies/downloads/#java17). + - Pour une mise à jour de Java en version 25, allez sur la [page officielle de téléchargement d'Oracle](https://www.oracle.com/java/technologies/downloads/#java25). - - Si plusieurs versions de Java sont installées, vous devez activer la bonne version. Affichez les versions installées avec la commande suivante puis sélectionnez la version 17 (ou 18) : + - Si plusieurs versions de Java sont installées, vous devez activer la bonne version. Affichez les versions installées avec la commande suivante puis sélectionnez la version 25 : ```shell sudo update-alternatives --config java ``` - - Si vous souhaitez configurer votre plateforme en HTTPS, vous aurez besoin de générer un fichier keystore pour la version 17 de Java (ou 18) ([voir procédure](./secure-your-map-platform.md#configuration-httpstls-avec-une-clé-auto-signée)). + - Si vous souhaitez configurer votre plateforme en HTTPS, vous aurez besoin de générer un fichier keystore pour la version 25 de Java ([voir procédure](./secure-your-map-platform.md#configuration-httpstls-avec-une-clé-reconnue)). @@ -865,10 +869,10 @@ Il est obligatoire de sécuriser l'accès root de la base de données avant d'in mariadb-secure-installation ``` -* Répondez **oui** à toutes les questions, sauf à "Disallow root login remotely? +* Répondez **oui** à toutes les questions, sauf à "Disallow root login remotely?". * Il est obligatoire de définir un mot de passe pour l'utilisateur **root** de la base de données. Vous aurez besoin de ce mot de passe pendant l'[installation web](../installation/web-and-post-installation.md). -> Pour plus d'informations, veuillez consulter la [documentation officielle de MariaDB](https://mariadb.com/kb/en/mariadb-secure-installation/). +> Pour plus d'informations, veuillez consulter la [documentation officielle de MariaDB](https://mariadb.com/kb/en/mysql_secure_installation/). @@ -885,7 +889,7 @@ Il est obligatoire de sécuriser l'accès root de la base de données avant d'in mysql_secure_installation ``` -* Répondez **oui** à toutes les questions, sauf à "Disallow root login remotely? +* Répondez **oui** à toutes les questions, sauf à "Disallow root login remotely?". * Il est obligatoire de définir un mot de passe pour l'utilisateur **root** de la base de données. Vous aurez besoin de ce mot de passe pendant l'[installation web](../installation/web-and-post-installation.md). @@ -893,12 +897,12 @@ mysql_secure_installation ### Étape 5 : exécuter le script configure.sh -Exécutez le script de configuration du serveur MAP de Centreon. +Exécutez le script de configuration du serveur Centreon MAP Engine. Deux modes sont disponibles : interactif ou automatique. - Interactif *(aucune option/mode par défaut)* : plusieurs questions seront posées pour remplir de manière interactive les variables d'installation. -- Automatique *(--automatic ou -a)* : l'installation se fera automatiquement à partir des valeurs définies dans le fichier `/etc/centreon-map/vars.sh`. +- Automatique *(--automatic ou -a)* : l'installation se fera automatiquement à partir des valeurs définies dans le fichier **/etc/centreon-map/vars.sh**. Si c'est votre première installation, nous vous conseillons d'utiliser le mode standard (interactif) et de choisir **Non** lorsqu'on vous demande le mode d'installation avancé : @@ -930,20 +934,19 @@ centreon.path=/your-custom-uri Pour implémenter correctement la mémoire dédiée : -Modifiez le paramètre **JAVA_OPTS** dans le fichier de configuration Centreon MAP -`/etc/centreon-map/centreon-map.conf`: +Modifiez le paramètre **JAVA_OPTS** dans le fichier de configuration Centreon MAP `/etc/centreon-map/centreon-map.conf` en ajoutant les paramètres -Xms et -Xmx : - ```text - JAVA_OPTS="-Xms512m -Xmx4G" - ``` +```text +JAVA_OPTS="-Xms512m -Xmx4G..." +``` - > La valeur Xmx dépend de la quantité de mémoire indiquée dans les tableaux dans la section [Matériel](#matériel). +> La valeur Xmx dépend de la quantité de mémoire indiquée dans les tableaux dans la section [Matériel](#matériel). -Redémarrez le service : +Ensuite, redémarrez le service **centreon-map-engine** : - ```shell - systemctl restart centreon-map-engine - ``` +```shell +systemctl restart centreon-map-engine +``` ### Étape 6 : appliquer la configuration Broker et redémarrer MAP Engine @@ -955,17 +958,17 @@ Redémarrez Centreon Broker sur le serveur central : systemctl restart cbd ``` -Supprimer le privilège INSERT de l'utilisateur **centreon_map** : +Supprimez le privilège INSERT de l'utilisateur **centreon_map** : ```sql REVOKE INSERT ON centreon.* FROM 'centreon_map'@''; ``` -Ensuite redémarrer le service **centreon-map-engine** : +Ensuite, redémarrez le service **centreon-map-engine** : - ```shell - systemctl start centreon-map-engine - ``` +```shell +systemctl restart centreon-map-engine +``` Exécutez la commande suivante pour vérifier que le service **centreon-map-engine** est correctement démarré : @@ -997,7 +1000,7 @@ Vérifiez la configuration du serveur MAP Engine avec cette commande : > En cas d'erreur, consultez la section **Lancement de l'outil de diagnostic** à la page [Dépanner MAP](map-web-troubleshooting.md#exécuter-notre-outil-de-diagnostic). -Si la configuration est correcte, le service **centreon-map-engine** peut être lancé à partir du serveur Centreon MAP (Legacy) : +Si la configuration est correcte, le service **centreon-map-engine** peut être lancé à partir du serveur Centreon MAP : ```shell systemctl restart centreon-map-engine @@ -1009,7 +1012,7 @@ Permettez au service de démarrer automatiquement au démarrage du serveur : systemctl enable centreon-map-engine ``` -Le serveur Centreon MAP est maintenant démarré et activé : installons la partie interface de l'extension. +Le serveur Centreon MAP Engine est maintenant démarré et activé : installons la partie interface de l'extension. ## Installation du client web MAP @@ -1022,21 +1025,21 @@ Installez le dépôt de Centreon Business : vous pouvez le trouver sur le [porta 1. Depuis votre terminal, entrez la commande suivante sur le serveur central : - + ```shell sudo dnf install centreon-map-web-client ``` - + ```shell sudo dnf install centreon-map-web-client ``` - + ```shell sudo apt install centreon-map-web-client diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-update.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-update.md index ab368e1b8d04..09296fa4cef5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-update.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-update.md @@ -14,10 +14,10 @@ Suivez cette procédure pour mettre à jour la version de MAP : sudo systemctl stop centreon-map-engine ``` -2. Mettez à jour les paquets en exécutant la commande suivante sur la ou les machines hébergeant le service du central et le service Centreon MAP : +2. Mettez à jour les paquets en exécutant les commandes suivantes sur les machines hébergeant le service du central et le service Centreon MAP : - + - Sur le serveur central : @@ -32,7 +32,7 @@ Suivez cette procédure pour mettre à jour la version de MAP : ``` - + - Sur le serveur central : @@ -47,55 +47,19 @@ Suivez cette procédure pour mettre à jour la version de MAP : ``` - + - - Si MAP seul est installé : - - Sur le serveur central : + - Sur le serveur central : ``` shell - sudo apt install centreon-map-web-client + sudo apt install --only-upgrade centreon-map-web-client ``` - Sur le serveur MAP : + - Sur le serveur MAP : ``` shell - sudo apt install centreon-map-engine + sudo apt install --only-upgrade centreon-map-engine ``` - - - Si MAP et MAP Legacy sont installés sur le même serveur : - - - Faites une sauvegarde du fichier **map.cnf** : - - ```shell - cp /etc/my.cnf.d/map.cnf /etc/my.cnf.d/map.cnf.bk - ``` - - - Mettez les paquets de **centreon-map-engine** à jour : - - Sur le serveur central : - - ``` shell - sudo apt install -o Dpkg::Options::="--force-overwrite" centreon-map-web-client - ``` - - Sur le serveur MAP : - - ``` shell - sudo apt install -o Dpkg::Options::="--force-overwrite" centreon-map-engine - ``` - - - Récupérez la sauvegarde du fichier de configuration : - - ```shell - cp /etc/my.cnf.d/map.cnf.bk /etc/my.cnf.d/map.cnf - ``` - - - Répondez **Y**. Ensuite redémarrez MySQL : - - ```shell - systemctl restart mariadb - ``` @@ -104,6 +68,8 @@ Suivez cette procédure pour mettre à jour la version de MAP : 4. Finalisez la mise à jour du module et du widget dans l'interface Centreon **Administration > Extensions > Gestionnaire**. + > Un bouton de mise à jour s'affiche lorsqu'une mise à jour est disponible. Cliquez dessus pour mettre à jour le module, puis faites de même pour le widget. + 5. Redémarrez le service **centreon-map-engine** en exécutant la commande suivante : ```shell diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md index b9a42782bd64..ad0b57377ca5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md @@ -6,28 +6,41 @@ description: "Monter de version Centreon MAP vers une nouvelle version majeure" import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -> **À partir de Centreon 24.10, MAP Legacy n'est plus disponible.** Suivez ce [lien](https://archives-docs.centreon.com/24.04/fr/docs/graph-views/introduction/) pour consulter la dernière version disponible de la documentation pour MAP Legacy (version archivée). +> Lorsque vous montez vers une nouvelle version majeure (c'est-à-dire version A.B.x avec A ou B qui évolue), vous devez installer le nouveau dépôt Business. Vous pouvez trouver l'adresse du dépôt sur le [portail support Centreon](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). -> Lorsque vous mettez à jour une nouvelle version majeure (c'est à dire version A.B.x avec A ou B qui évolue), vous devez installer le nouveau dépôt Business. Vous pouvez trouver l'adresse du dépôt sur le [portail support Centreon](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). +> **À partir de Centreon 24.10, MAP Legacy n'est plus disponible.** Suivez ce [lien](https://archives-docs.centreon.com/24.04/fr/docs/graph-views/introduction/) pour consulter la dernière version disponible de la documentation pour MAP Legacy (version archivée). ## Prérequis +### Vérifier votre système d'exploitation + +Assurez-vous que le serveur central et le serveur MAP fonctionnent sous un [système d'exploitation pris en charge par cette version](../installation/compatibility.md#systèmes-dexploitation). + +Si l'un de vos serveurs fonctionne sous un système d'exploitation qui n'est plus pris en charge, vous ne pouvez pas le monter de version directement. Migrez d'abord votre plateforme vers un système d'exploitation pris en charge : + +- Pour le serveur central, voir [Migrer une plateforme](../migrate/introduction.md). +- Pour le serveur MAP, voir [Migrer l'extension](map-web-migrate.md). + +### Vérifier la version de votre base de données + +Assurez-vous que votre base de données utilise une [version de SGBD prise en charge par cette version](../installation/compatibility.md#sgbd). Si ce n'est pas le cas, mettez-la à jour avant de monter de version MAP. Voir [Mettre à jour MariaDB](../upgrade/upgrade-mariadb.md) ou [Mettre à jour MySQL](../upgrade/upgrade-mysql.md). + ### Mettre à jour la clé de signature RPM -Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. +Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Si votre plateforme utilise encore une ancienne clé, suivez la [procédure de changement de clé](../security/key-rotation.md#installation-existante) afin de supprimer l'ancienne clé et d'installer la nouvelle. ## Mise à jour du paquet -1. Arrêtez le service **centreon-map-engine** en entrant cette commande sur la machine où se trouve le serveur MAP : +1. Arrêtez le service **centreon-map-engine** en exécutant cette commande sur la machine hébergeant le service Centreon MAP : - ```shell - sudo systemctl stop centreon-map-engine - ``` + ```shell + sudo systemctl stop centreon-map-engine + ``` 2. Pour mettre à jour le module Centreon MAP, exécutez les commandes suivantes : - + - Sur le serveur central : @@ -42,7 +55,7 @@ Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centre ``` - + - Sur le serveur central : @@ -57,56 +70,20 @@ Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centre ``` - + - - Si MAP seul est installé : - - Sur le serveur central : + - Sur le serveur central : ``` shell sudo apt install --only-upgrade centreon-map-web-client ``` - Sur le serveur MAP : + - Sur le serveur MAP : ``` shell sudo apt install --only-upgrade centreon-map-engine ``` - - Si MAP et MAP Legacy sont installés sur le même serveur : - - - Faites une sauvegarde du fichier **map.cnf** : - - ```shell - cp /etc/my.cnf.d/map.cnf /etc/my.cnf.d/map.cnf.bk - ``` - - - Mettez les paquets de **centreon-map-engine** à jour : - - Sur le serveur central : - - ``` shell - sudo apt install -o Dpkg::Options::="--force-overwrite" centreon-map-web-client - ``` - - Sur le serveur MAP : - - ``` shell - sudo apt install -o Dpkg::Options::="--force-overwrite" centreon-map-engine - ``` - - - Récupérez la sauvegarde du fichier de configuration : - - ```shell - cp /etc/my.cnf.d/map.cnf.bk /etc/my.cnf.d/map.cnf - ``` - - - Répondez **Y**. Ensuite redémarrez MySQL : - - ```shell - systemctl restart mariadb - ``` - @@ -114,14 +91,10 @@ Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centre 4. Finalisez la mise à jour du module et du widget dans l'interface Centreon **Administration > Extensions > Gestionnaire**. - > Un bouton orange de mise à jour est visible et signale qu'une mise à -jour est disponible, cliquez dessus pour mettre à jour le module, faire -de même pour le widget. + > Un bouton de mise à jour s'affiche lorsqu'une mise à jour est disponible. Cliquez dessus pour mettre à jour le module, puis faites de même pour le widget. 5. Redémarrez le service **centreon-map-engine** en exécutant la commande suivante : ```shell sudo systemctl start centreon-map-engine ``` - -6. Si vous faites une mise à jour vers la version 24.04 et plus, vous devez mettre à jour MariaDB en version 10.11. Voir [Mettre à jour MariaDB](../upgrade/upgrade-mariadb.md). diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/install.md index 9f544d609dd7..25e989717ded 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/install.md @@ -1,49 +1,49 @@ --- id: install title: Installer l'extension Centreon BAM -description: "Installer et activer la licence de l'extension Centreon BAM" +description: "Installer et activer la licence de l'extension Centreon BAM sur votre plateforme" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -> Centreon BAM est une **extension** Centreon qui requiert une license +> Centreon BAM est une **extension** Centreon qui requiert une clé de licence > valide. Pour plus d'information, contactez > [Centreon](mailto:sales@centreon.com). -## Prerequisites +## Prérequis Voir les [prérequis logiciels](../installation/prerequisites.md#caractéristiques-des-serveurs). Installez BAM sur le serveur central. -Le serveur central et Centreon BAM doivent être dans la même version majeure (c'est-à-dire tous les deux en 26.10.x). +Le serveur central et Centreon BAM doivent être dans la même version majeure (par exemple tous les deux en 26.10.x). Si vous voulez pouvoir voir les Activités métier supervisées par un serveur distant, installez BAM également sur le serveur distant. Lorsque BAM est installé sur un serveur distant, les Activités métier n'incluent que les ressources supervisées par le serveur distant. ## Installation -### Installation du paquet +### Installer le paquet -Ajouter le dépôt Centreon Business, vous pouvez le trouver sur le +Ajoutez le dépôt Centreon Business. Vous pouvez le trouver sur le [portail support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). -Et installer le paquet en exécutant la commande ci-dessous : +Ensuite, installez le paquet en exécutant la commande suivante : - + ``` shell dnf install centreon-bam-server ``` - + ``` shell dnf install centreon-bam-server ``` - + ```shell apt update && apt install centreon-bam-server @@ -55,20 +55,20 @@ apt update && apt install centreon-bam-server ### Charger la licence -Le fichier de licence "bam.license" est fourni par Centreon, pour -l'installer, rendez vous dans **Administration > Extensions > Gestionnaire** puis -télécharger la via l'interface. +Un fichier de licence *bam.license* est fourni par Centreon. Allez dans le menu +**Administration > Extensions > Gestionnaire** et chargez la licence +via l'interface. -### Installation sur l'interface +### Installer l'interface -Se rendre dans le menu **Administration > Extensions > Gestionnaire** et cliquez -sur le bouton d'installation des modules suivantes : +Allez dans le menu **Administration > Extensions > Gestionnaire** et cliquez +sur le bouton d'installation des modules suivants : -- License Manager (si celui-ci n'est pas déjà installé) +- License Manager (s'il n'est pas déjà installé) - Business Activity Monitoring -Une fois installé et la licence ajoutée, le module aura un bandeau vert -indiquant la date de fin de validité de la licence : +Une fois le module installé et la licence ajoutée, la carte du module affiche +la date d'expiration de la licence : ![image](../assets/service-mapping/installation/install-web-step-2.png) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/update.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/update.md index 1df136ad4857..b0b95ede1f24 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/update.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/update.md @@ -8,25 +8,24 @@ import TabItem from '@theme/TabItem'; ## Mise à jour du paquet -Afin de mettre à jour le module **Centreon BAM**, lancer la commande -ci-dessous : +Pour mettre à jour le module Centreon BAM, exécutez la commande suivante : - + ```shell dnf update centreon-bam-server ``` - + ```shell dnf update centreon-bam-server ``` - + ```shell apt update && apt install --only-upgrade centreon-bam-server @@ -35,11 +34,8 @@ apt update && apt install --only-upgrade centreon-bam-server -## Mise à jour de l'interface +## Mise à jour via l'interface -Se connecter à l'interface web de Centreon et se rendre dans le menu -`Administration > Extensions > Gestionnaire`. +Connectez-vous à l'interface web de Centreon et allez dans **Administration > Extensions > Gestionnaire**. -Un bouton orange de mise à jour est visible et signale qu'une mise à -jour est disponible, cliquez dessus pour mettre à jour le module, faire -de même pour le widget. +Un bouton de mise à jour s'affiche lorsqu'une mise à jour est disponible. Cliquez dessus pour mettre à jour le module, puis faites de même pour le widget. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/upgrade.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/upgrade.md index d8282b7eb210..a4626cbbd789 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/upgrade.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/service-mapping/upgrade.md @@ -8,60 +8,49 @@ import TabItem from '@theme/TabItem'; ## Prérequis -### Licence - -Si vous mettez à jour d'une version inférieure à 18.10 vers une version -supérieure à 18.10, une nouvelle licence doit être récupérée auprès du -support Centreon. - -### Mettre à jour Centreon web sur votre serveur central +### Monter de version Centreon web sur votre serveur central Voir le [chapitre correspondant](../upgrade/introduction.md). ### Installer le dépôt Business -Lorsque vous mettez à jour vers une nouvelle version majeure ou -mineure (c'est à dire version A.B.x avec A ou B qui évolue), contactez -le support pour récupérer l'adresse du nouveau dépôt. +Lorsque vous montez vers une nouvelle version majeure ou mineure (c'est-à-dire version A.B.x avec A ou B qui +évolue), vous devez installer le nouveau dépôt Business. Vous pouvez trouver son adresse sur le [portail support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). ### Mettre à jour la clé de signature RPM -Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. +Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Si votre plateforme utilise encore une ancienne clé, suivez la [procédure de changement de clé](../security/key-rotation.md#installation-existante) afin de supprimer l'ancienne clé et d'installer la nouvelle. ## Mise à jour du paquet -Afin de mettre à jour le module **Centreon BAM**, lancer la commande -ci-dessous : +Pour mettre à jour le module Centreon BAM, exécutez la commande suivante : - + ```shell dnf update centreon-bam-server ``` - + ```shell dnf update centreon-bam-server ``` - + ```shell -apt install --only-upgrade centreon-bam-server +apt update && apt install --only-upgrade centreon-bam-server ``` -## Mise à jour de l'interface +## Mise à jour via l'interface -Se connecter à l'interface web de Centreon et se rendre dans le menu -`Administration > Extensions > Gestionnaire`. +Connectez-vous à l'interface web de Centreon et allez dans **Administration > Extensions > Gestionnaire**. -Un bouton orange de mise à jour est visible et signale qu'une mise à -jour est disponible, cliquez dessus pour mettre à jour le module, faire -de même pour le widget. +Un bouton de mise à jour s'affiche lorsqu'une mise à jour est disponible. Cliquez dessus pour mettre à jour le module, puis faites de même pour le widget. diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index 974f210920de..60ab068c8b18 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -410,8 +410,6 @@ dnf module enable -y mariadb:10.11 - - ```shell dnf module enable -y mariadb:10.11 ``` @@ -419,8 +417,6 @@ dnf module enable -y mariadb:10.11 - - ```shell curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=13 --mariadb-server-version="mariadb-10.11" ``` @@ -508,8 +504,6 @@ dnf install https://dev.mysql.com/get/mysql84-community-release-el10-1.noarch.rp - - ```shell wget https://dev.mysql.com/get/mysql-apt-config_0.8.32-1_all.deb dpkg -i mysql-apt-config_0.8.32-1_all.deb @@ -544,8 +538,6 @@ sudo systemctl status mysqld - - ```shell dnf install -y mysql-server mysql dnf install -y centreon-mysql @@ -728,10 +720,6 @@ This procedure is to ensure that the configuration file can be used for both MAP When installing Centreon MAP Engine server, it will automatically install java (OpenJDK 25) if needed. - - -> Go to this troubleshooting procedure if OpenJDK 17 causes an issue [preventing centreon-map-engine from being installed](./map-web-troubleshooting.md#centreon-map-engine-and-all-its-dependencies-cannot-get-installed-on-alma-linux-8). - #### Java requirement > Ensure a version of Java 25 is installed before you start the procedure. @@ -741,7 +729,6 @@ When installing Centreon MAP Engine server, it will automatically install java java -version ``` - - If you need to upgrade the Java installation to Java 25, go to the [Oracle official download](https://www.oracle.com/java/technologies/downloads/#java25) page. @@ -848,9 +835,6 @@ This procedure is to ensure that the configuration file can be used for both MAP When installing Centreon MAP Engine server, it will automatically install java (OpenJDK 25) if needed. - - -> Go to this troubleshooting procedure if OpenJDK 17 causes an issue [preventing centreon-map-engine from being installed](./map-web-troubleshooting.md#centreon-map-engine-and-all-its-dependencies-cannot-get-installed-on-alma-linux-8). #### Java requirement > Ensure a version of Java 25 is installed before you start the procedure. @@ -860,8 +844,7 @@ When installing Centreon MAP Engine server, it will automatically install java ```shell java -version ``` - - + - If you need to upgrade the Java installation to Java 25, go to the [Oracle official download](https://www.oracle.com/java/technologies/downloads/#java25) page. From d0bf0218f415d0b61cae1aaf6de16e5ad732d8d2 Mon Sep 17 00:00:00 2001 From: smau Date: Tue, 29 Sep 2026 17:17:43 +0200 Subject: [PATCH 095/179] Fix broken links --- .../version-26.10/graph-views/map-web-install.md | 4 ++-- .../version-26.10/graph-views/map-web-upgrade.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index 3f5daea9192f..6bc213197969 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -727,7 +727,7 @@ Lors de l'installation du serveur Centreon MAP Engine, java (OpenJDK 25) sera au sudo update-alternatives --config java ``` - - Si vous souhaitez configurer votre plateforme en HTTPS, vous aurez besoin de générer un fichier keystore pour la version 25 de Java ([voir procédure](./secure-your-map-platform.md#configuration-httpstls-avec-une-clé-reconnue)). + - Si vous souhaitez configurer votre plateforme en HTTPS, vous aurez besoin de générer un fichier keystore pour la version 25 de Java ([voir procédure](./secure-your-map-platform.md#configuration-httpstls-avec-une-clé-auto-signée)). @@ -840,7 +840,7 @@ Lors de l'installation du serveur Centreon MAP Engine, java (OpenJDK 25) sera au sudo update-alternatives --config java ``` - - Si vous souhaitez configurer votre plateforme en HTTPS, vous aurez besoin de générer un fichier keystore pour la version 25 de Java ([voir procédure](./secure-your-map-platform.md#configuration-httpstls-avec-une-clé-reconnue)). + - Si vous souhaitez configurer votre plateforme en HTTPS, vous aurez besoin de générer un fichier keystore pour la version 25 de Java ([voir procédure](./secure-your-map-platform.md#configuration-httpstls-avec-une-clé-auto-signée)). diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md index ad0b57377ca5..85e2d27c0b4d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md @@ -14,7 +14,7 @@ import TabItem from '@theme/TabItem'; ### Vérifier votre système d'exploitation -Assurez-vous que le serveur central et le serveur MAP fonctionnent sous un [système d'exploitation pris en charge par cette version](../installation/compatibility.md#systèmes-dexploitation). +Assurez-vous que le serveur central et le serveur MAP fonctionnent sous un [système d'exploitation pris en charge par cette version](../installation/compatibility.md#système-dexploitation). Si l'un de vos serveurs fonctionne sous un système d'exploitation qui n'est plus pris en charge, vous ne pouvez pas le monter de version directement. Migrez d'abord votre plateforme vers un système d'exploitation pris en charge : From 5f4c67454f82bd3d090aa8036b7d7f418167de31 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 29 Sep 2026 17:39:15 +0200 Subject: [PATCH 096/179] Corrections to "secure your platform" --- .../administration/secure-platform.md | 37 ++---------------- .../administration/secure-platform.md | 39 +++---------------- 2 files changed, 9 insertions(+), 67 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md index 3445dcf6885c..3931aefd8e39 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md @@ -614,10 +614,7 @@ cp rootCA.pem /etc/pki/tls/certs/ ```shell -curl -sSL https://packages.sury.org/apache2/README.txt | sudo bash -x -apt update a2enmod ssl -a2enmod security2 systemctl restart apache2 ``` @@ -683,6 +680,8 @@ cp /etc/apache2/sites-available/centreon.conf{,.origin} +Voici un exemple de ce à quoi le fichier peut ressembler avant d'insérer le bloc : + ```apacheconf Define base_uri "/centreon" Define install_dir "/usr/share/centreon" @@ -696,7 +695,7 @@ ServerTokens Prod ``` -Voici un exemple de ce à quoi le fichier peut ressembler : +Voici un exemple de ce à quoi le fichier peut ressembler une fois le bloc inséré : @@ -943,15 +942,6 @@ ServerTokens Prod -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant les lignes suivantes avant la balise `` : - -```apacheconf -Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict -Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" -ServerSignature Off -ServerTokens Prod -``` - Éditez le fichier **/etc/php.d/50-centreon.ini** : * Assurez-vous que le paramètre `expose_php` est désactivé : @@ -970,15 +960,6 @@ ServerTokens Prod -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant les lignes suivantes avant la balise `` : - -```apacheconf -Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict -Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" -ServerSignature Off -ServerTokens Prod -``` - Éditez le fichier **/etc/php.d/50-centreon.ini** : * Assurez-vous que le paramètre `expose_php` est désactivé : @@ -997,17 +978,6 @@ ServerTokens Prod -Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant les lignes suivantes avant la balise `` : - -```apacheconf -Header set X-Frame-Options: "sameorigin" -Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict -Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" -ServerSignature Off -ServerTokens Prod -TraceEnable Off -``` - Éditez le fichier **/etc/php/8.4/mods-available/centreon.ini** et ajoutez les lignes suivantes : ```text @@ -1497,6 +1467,7 @@ dnf install mod_security ```shell apt install libapache2-mod-security2 +a2enmod security2 ``` diff --git a/versioned_docs/version-26.10/administration/secure-platform.md b/versioned_docs/version-26.10/administration/secure-platform.md index 146f6f67ceb7..bab8786de7a7 100644 --- a/versioned_docs/version-26.10/administration/secure-platform.md +++ b/versioned_docs/version-26.10/administration/secure-platform.md @@ -412,7 +412,7 @@ public (active) icmp-block-inversion: no interfaces: eth0 sources: - services: http snmp snmptrap ssh + services: http https snmp snmptrap ssh ports: 5556/tcp 5669/tcp protocols: forward: no @@ -617,10 +617,7 @@ cp rootCA.pem /etc/pki/tls/certs/ 1. Install the SSL module for Apache: ```shell -curl -sSL https://packages.sury.org/apache2/README.txt | sudo bash -x -apt update a2enmod ssl -a2enmod security2 systemctl restart apache2 ``` @@ -686,6 +683,8 @@ Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **\ +This is how the file looks before adding the lines: + ```apacheconf Define base_uri "/centreon" Define install_dir "/usr/share/centreon" @@ -699,7 +698,7 @@ ServerTokens Prod ``` -This is how the file should look: +This is how the file should look after adding them: @@ -949,15 +948,6 @@ ServerTokens Prod -Edit the **/etc/httpd/conf.d/10-centreon.conf** file and add the following lines before the `` tag: - -```apacheconf -Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict -Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" -ServerSignature Off -ServerTokens Prod -``` - Edit the **/etc/php.d/50-centreon.ini** file: * Make sure that the `expose_php` parameter is disabled: @@ -976,15 +966,6 @@ expose_php = Off -Edit the **/etc/httpd/conf.d/10-centreon.conf** file and add the following lines before the `` tag: - -```apacheconf -Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict -Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" -ServerSignature Off -ServerTokens Prod -``` - Edit the **/etc/php.d/50-centreon.ini** file: * Make sure that the `expose_php` parameter is disabled: @@ -1003,17 +984,6 @@ expose_php = Off -Edit the **/etc/apache2/sites-available/centreon.conf** file and add the following lines before the `` tag: - -```apacheconf -Header set X-Frame-Options: "sameorigin" -Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure;SameSite=Strict -Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" -ServerSignature Off -ServerTokens Prod -TraceEnable Off -``` - Edit the **/etc/php/8.4/mods-available/centreon.ini** file and add the following lines: ```text @@ -1502,6 +1472,7 @@ dnf install mod_security ```shell apt install libapache2-mod-security2 +a2enmod security2 ``` From 699b0c810ab41c9dc511937e064418e8e9b2e614 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 30 Sep 2026 12:33:26 +0200 Subject: [PATCH 097/179] Update --- .../installation/web-and-post-installation.md | 33 ++++++++++- .../upgrade/_upgrade-central.mdx | 21 +++---- .../version-26.10/upgrade/upgrade-mariadb.md | 57 ++++++------------- .../installation/web-and-post-installation.md | 29 ++++++++++ .../upgrade/_upgrade-central.mdx | 20 +++---- .../version-26.10/upgrade/upgrade-mariadb.md | 30 +++++----- 6 files changed, 113 insertions(+), 77 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md index fa61e7df95fe..9ddd8667423c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md @@ -3,10 +3,12 @@ id: web-and-post-installation title: Installation Web description: "Terminer l'assistant d'installation web et initialiser la supervision" --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; ## Installation web -Connectez-vous à l'interface web via `http:///centreon`. +Connectez-vous à l'interface web via `http(s):///centreon`. ### Étape 1 : Welcome to Centreon setup @@ -99,6 +101,35 @@ Vous pouvez maintenant vous connecter en utilisant le compte **admin**, et [init ## Initialisation de la supervision +Appliquez les permissions suivantes : + + + + +```shell +usermod -a -G centreon-broker apache +usermod -a -G apache centreon-broker +``` + + + + +```shell +usermod -a -G centreon-broker apache +usermod -a -G apache centreon-broker +``` + + + + +```shell +usermod -a -G centreon-broker www-data +usermod -a -G www-data centreon-broker +``` + + + + Pour démarrer les processus de supervision : 1. Depuis l'interface web, rendez-vous dans le menu **Configuration > diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx index 6a242dad4919..6ab2abdd85bc 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx @@ -198,7 +198,16 @@ Ajoutez le code suivant à votre fichier de configuration Apache, dans les élé AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json ``` -### Étape 6 : Finaliser la montée de version +### Étape 6 : Monter la base de données de version + +
    +
  • Si vous utilisiez MariaDB {props.oldMariadbVersion}, [montez-la de version](upgrade-mariadb.md) vers la version 11.8.
    • + {props.showSecondPoint &&
  • Si vous utilisiez MySQL 8.0, [montez-la de version vers la 8.4](upgrade-mysql.md).
    • } + {props.showThirdPoint &&
  • Si vous utilisiez déjà MySQL 8.4, vous n'avez rien à faire.
    • } +
+ + +### Étape 7 : Finaliser la montée de version 1. Avant de démarrer la montée de version via l'interface web, montez de version le [module Centreon BAM](../service-mapping/upgrade.md), puis rechargez le serveur Apache à l'aide de la commande suivante : @@ -289,7 +298,7 @@ de connexion : 8. Consultez les procédures dédiées à [Centreon MBI](../reporting/update.md) et à [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. -### Étape 7 : Actions post montée de version +### Étape 8 : Actions post montée de version 1. Montez de version les extensions. Depuis le menu **Administration > Extensions > Gestionnaire**, mettez à jour toutes les extensions, en commençant par les suivantes : @@ -318,11 +327,3 @@ par les suivantes : ``` shell systemctl restart cbd centengine centreontrapd gorgoned ``` - -### Étape 8 : Monter la base de données de version - -
    -
  • Si vous utilisiez MariaDB {props.oldMariadbVersion}, [montez-la de version](upgrade-mariadb.md) vers la version 11.8.
    • - {props.showSecondPoint &&
  • Si vous utilisiez MySQL 8.0, [montez-la de version vers la 8.4](upgrade-mysql.md).
    • } - {props.showThirdPoint &&
  • Si vous utilisiez déjà MySQL 8.4, vous n'avez rien à faire.
    • } -
diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md index 57f1d4004a9b..db3656152fc2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md @@ -63,56 +63,19 @@ Il est nécessaire de désinstaller puis réinstaller MariaDB pour changer de ve systemctl stop mariadb ``` -2. Désinstallez la version actuelle : - - - - -```shell -rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-compat MariaDB-common -``` - - - +2. Exécutez la commande suivante : ```shell -rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-common +dnf module reset mariadb -y ``` - - - -> Pendant cette étape de désinstallation, vous pouvez rencontrer une erreur parce qu'un ou plusieurs paquets MariaDB sont manquants. Dans ce cas, vous devez exécuter la commande de désinstallation sans inclure le paquet manquant. -> ->Par exemple, vous obtenez le message d'erreur suivant : -> -> `package MariaDB-compat is not installed` -> -> Comme le paquet **MariaDB-compat** est manquant, vous devez exécuter la même commande sans citer **MariaDB-compat** : -> -> `rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-common` - -> Assurez-vous d'avoir [installé le dépôt officiel de MariaDB](https://mariadb.com/kb/en/mariadb-package-repository-setup-and-usage/) avant de poursuivre la procédure. - 3. Installez la version 10.11 : - - - ```shell -dnf install mariadb-server-10.11\* mariadb-10.11\* +dnf module enable -y mariadb:11.8 +dnf install mariadb-server-11.8\* mariadb-11.8\* ``` - - - -```shell -dnf install mariadb-server-10.11\* mariadb-10.11\* -``` - - - - 4. Démarrer le service mariadb : ```shell @@ -146,6 +109,18 @@ dnf install mariadb-server-10.11\* mariadb-10.11\* systemctl enable mariadb ``` +7. Avant de finir la montée de version de votre plateforme Centreon, exécutez la commande suivante sur le serveur central : + + ```shell + systemctl restart php-fpm httpd + ``` + +8. Vérifiez que MariaDB tourne à l'aide de la commande `systemctl status mariadb`. Si ce n'est pas le cas, démarrez le service : + + ```shell + systemctl start mariadb + ``` + ### Montée de version de 10.1 à une version plus récente Le paramètre `innodb_additional_mem_pool_size` a été supprimé depuis MariaDB diff --git a/versioned_docs/version-26.10/installation/web-and-post-installation.md b/versioned_docs/version-26.10/installation/web-and-post-installation.md index 84ca20a69196..be003808835c 100644 --- a/versioned_docs/version-26.10/installation/web-and-post-installation.md +++ b/versioned_docs/version-26.10/installation/web-and-post-installation.md @@ -95,6 +95,35 @@ You can now log in using the **admin** account and [initialize the monitoring](# ## Initialization of the monitoring +Apply the following permissions: + + + + +```shell +usermod -a -G centreon-broker apache +usermod -a -G apache centreon-broker +``` + + + + +```shell +usermod -a -G centreon-broker apache +usermod -a -G apache centreon-broker +``` + + + + +```shell +usermod -a -G centreon-broker www-data +usermod -a -G www-data centreon-broker +``` + + + + To start the monitoring processes: 1. From your web interface, go to **Configuration > Pollers**. diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index 9846a67388bd..84f45d44d872 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -198,7 +198,15 @@ Add the following code to your Apache configuration file, in both the ` +
  • If you were using MariaDB {props.oldMariadbVersion}, [upgrade it](upgrade-mariadb.md) to version 11.8.
    • + {props.showSecondPoint &&
  • If you were using MySQL 8.0, [upgrade it to version 8.4](upgrade-mysql.md).
    • } + {props.showThirdPoint &&
  • If you were already using MySQL 8.4, you don't need to do anything.
    • } + + +### Step 7: Finalize the upgrade 1. Before starting the web upgrade process, upgrade the [Centreon BAM module](../service-mapping/upgrade.md) and reload the Apache server with the following command: @@ -289,7 +297,7 @@ page: 8. Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. -### Step 7: Post-upgrade actions +### Step 8: Post-upgrade actions 1. Upgrade extensions. From **Administration > Extensions > Manager**, upgrade all extensions, starting with the following: @@ -318,11 +326,3 @@ with the following: ``` shell systemctl restart cbd centengine centreontrapd gorgoned ``` - -### Step 8: Upgrade the database - -
      -
    • If you were using MariaDB {props.oldMariadbVersion}, [upgrade it](upgrade-mariadb.md) to version 11.8.
      • - {props.showSecondPoint &&
    • If you were using MySQL 8.0, [upgrade it to version 8.4](upgrade-mysql.md).
      • } - {props.showThirdPoint &&
    • If you were already using MySQL 8.4, you don't need to do anything.
      • } -
    \ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md b/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md index 3ac2c5cc316f..02097debf73b 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md @@ -64,37 +64,25 @@ You must uninstall then reinstall MariaDB to upgrade between major versions. In systemctl stop mariadb ``` -2. Uninstall the current version: +2. Execute the following command: ```shell -rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-compat MariaDB-common +dnf module reset mariadb -y ``` ```shell -rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-common +dnf module reset mariadb -y ``` -> During this uninstallation step, you may encounter an error because one or several MariaDB packages are missing. In that case, you should execute the uninstallation command without including the missing package. -> -> For instance, you get the following error message: -> -> `package MariaDB-compat is not installed` -> -> As **MariaDB-compat** is the missing package, please execute the same command without quoting **MariaDB-compat**: -> -> `rpm --erase --nodeps --verbose MariaDB-server MariaDB-client MariaDB-shared MariaDB-common` - -> Make sure you have [installed the official MariaDB repository](https://mariadb.com/kb/en/mariadb-package-repository-setup-and-usage/) before you continue the procedure. - 3. Install version 11.8: @@ -149,6 +137,18 @@ dnf install mariadb-server-11.8\* mariadb-11.8\* systemctl enable mariadb ``` +7. Before you finish upgrading your Centreon platform, execute the following command on the central server: + + ```shell + systemctl restart php-fpm httpd + ``` + +8. Make sure MariaDB is running using `systemctl status mariadb`. If not, start it: + + ```shell + systemctl start mariadb + ``` + ### Upgrading from 10.1 to a more recent version The `innodb_additional_mem_pool_size` parameter has been removed since MariaDB 10.2, From 4dc68872a02a59cbb5fd9a99270299182a471f8b Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 1 Oct 2026 09:43:02 +0200 Subject: [PATCH 098/179] Fix import --- .../version-26.10/installation/web-and-post-installation.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/versioned_docs/version-26.10/installation/web-and-post-installation.md b/versioned_docs/version-26.10/installation/web-and-post-installation.md index be003808835c..ad17a80aec79 100644 --- a/versioned_docs/version-26.10/installation/web-and-post-installation.md +++ b/versioned_docs/version-26.10/installation/web-and-post-installation.md @@ -3,6 +3,8 @@ id: web-and-post-installation title: Web And Post Installation description: "Complete the web setup wizard and initialize your monitoring" --- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; ## Web installation From 3c11441eacf54aca6dcd31045de227685f9ac373 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 1 Oct 2026 13:35:05 +0200 Subject: [PATCH 099/179] Fix FR compatibility topic + add "from 10.2" --- .../version-26.10/installation/compatibility.md | 15 +++++++-------- .../version-26.10/installation/compatibility.md | 2 +- 2 files changed, 8 insertions(+), 9 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/compatibility.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/compatibility.md index 05ec35de6f8b..21c19277be18 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/compatibility.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/compatibility.md @@ -25,12 +25,11 @@ Votre résolution doit être au minimum à 1280 x 768. Les OS supportés par Centreon sont les suivants : -| Version | Mode d'installation | -|--------------------------------|-------------------------------------------------------| -| Alma Linux 8 | paquets RPM, sources, machine virtuelle | -| RHEL/Oracle Linux 8 | paquets RPM, sources | -| RHEL/Oracle Linux/Alma Linux 9 | paquets RPM, sources | -| Debian 12 (bookworm) | paquets DEB | +| Version | Mode d'installation | +|---------------------------------|-------------------------------------------------------| +| RHEL/Oracle Linux/Alma Linux 9 | paquets RPM, sources | +| RHEL/Oracle Linux/Alma Linux 10 (à partir de la version 10.2) | paquets RPM, sources | +| Debian 13 (trixie) | paquets DEB | Voir notre article de base de connaissances [How to install Linux to host Centreon software](https://thewatch.centreon.com/product-how-to-21/how-to-install-linux-to-host-centreon-software-3759). @@ -44,8 +43,8 @@ Attention, les modules de l'IT Edition et de la Business Edition ne fonctionnent | Logiciel | Version | |----------|------------------| -| MariaDB | 10.11 | -| MySQL |
    • 8.4 (recommandé)
    • 8.0 jusqu'à sa fin de support (avril 2026)
    | +| MariaDB | 11.8 | +| MySQL | 8.4 | > Vous pouvez utiliser un autre SGBD basé sur MySQL, mais celui-ci sera uniquement supporté par la communauté. diff --git a/versioned_docs/version-26.10/installation/compatibility.md b/versioned_docs/version-26.10/installation/compatibility.md index f0d69b669dfc..e198a6e235a0 100644 --- a/versioned_docs/version-26.10/installation/compatibility.md +++ b/versioned_docs/version-26.10/installation/compatibility.md @@ -28,7 +28,7 @@ Centreon supports the following operating systems: | Version | Installation mode | |---------------------------------|--------------------------------------------------------| | RHEL/Oracle Linux/Alma Linux 9 | RPM packages, sources | -| RHEL/Oracle Linux/Alma Linux 10 | RPM packages, sources | +| RHEL/Oracle Linux/Alma Linux 10 (from version 10.2) | RPM packages, sources | | Debian 13 (trixie) | DEB packages | See our knowledge base article [How to install Linux to host Centreon software](https://thewatch.centreon.com/product-how-to-21/how-to-install-linux-to-host-centreon-software-3759). From c456d92ecf2340f28659d7b383a8e441b58f1051 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 1 Oct 2026 13:48:12 +0200 Subject: [PATCH 100/179] At least EL 10.2 --- .../version-26.10/installation/_install-common.mdx | 2 ++ .../installation-of-a-central-server/unattended.md | 4 ++++ versioned_docs/version-26.10/installation/_install-common.mdx | 3 +++ .../installation-of-a-central-server/unattended.md | 4 ++++ 4 files changed, 13 insertions(+) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx index 23d0ceaa1d13..cb8b2f69f82b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx @@ -33,6 +33,8 @@ locale -a     +> Pour récupérer la version de PHP requise par Centreon 26.10 lors de l'installation, votre version d'Alma/RHEL/Oracle Linux doit être au minimum 10.2. + ```shell dnf update ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/unattended.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/unattended.md index 5b50ffde40cd..e8ee86c1c7c4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/unattended.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/unattended.md @@ -38,6 +38,8 @@ C'est utile lorsque vous devez installer plusieurs serveurs centraux avec des pa + > Pour récupérer la version de PHP requise par Centreon 26.10 lors de l'installation, votre version de RHEL doit être au minimum 10.2. + ```shell dnf update subscription-manager register --username my_username --password my_password --auto-attach --force @@ -49,6 +51,8 @@ C'est utile lorsque vous devez installer plusieurs serveurs centraux avec des pa + > Pour récupérer la version de PHP requise par Centreon 26.10 lors de l'installation, votre version d'Alma/Oracle Linux doit être au minimum 10.2. + ```shell dnf update ``` diff --git a/versioned_docs/version-26.10/installation/_install-common.mdx b/versioned_docs/version-26.10/installation/_install-common.mdx index 981e778033db..a1d4761b9eb3 100644 --- a/versioned_docs/version-26.10/installation/_install-common.mdx +++ b/versioned_docs/version-26.10/installation/_install-common.mdx @@ -33,11 +33,14 @@ locale -a +> To get the PHP version required by Centreon 26.10 during installation, your Alma/RHEL/Oracle Linux version must be at least 10.2. + ```shell dnf update ``` ### Additional configuration for EL 10 + If you intend to use Centreon in French, Spanish, Portuguese or German, install the corresponding packages: ```shell diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md index 2e105f2babc6..d6532468dbd5 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md @@ -38,6 +38,8 @@ This is useful when you need to install several central servers with identical s + > To get the PHP version required by Centreon 26.10 during installation, your RHEL version must be at least 10.2. + ```shell dnf update subscription-manager register --username my_username --password my_password --auto-attach --force @@ -49,6 +51,8 @@ This is useful when you need to install several central servers with identical s + > To get the PHP version required by Centreon 26.10 during installation, your Alma/Oracle Linux version must be at least 10.2. + ```shell dnf update ``` From 016037252d2d0eb9e4cd4af3f66bc248dffca734 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 2 Oct 2026 18:04:08 +0200 Subject: [PATCH 101/179] Add sentence about in-place migration doc --- .../version-26.10/migrate/migrate-from-debian-to-debian.md | 2 +- .../version-26.10/migrate/migrate-from-debian-to-debian.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md index 54d8e09445a8..a4bc37948531 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md @@ -8,7 +8,7 @@ import TabItem from '@theme/TabItem'; ## Prérequis -Cette procédure ne s'applique que si vous souhaitez migrer de Debian vers une version plus récente de Debian, sur des serveurs différents. +Cette procédure ne s'applique que si vous souhaitez migrer de Debian vers une version plus récente de Debian, sur des serveurs différents. La procédure de migration de Debian 12 vers Debian 13 sur le même serveur (migration in-place) sera bientôt disponible sur notre plateforme communautaire The Watch. Tous les serveurs de votre architecture (serveur central, serveurs distants et collecteurs) doivent avoir la même version majeure de Centreon. Il est également recommandé d'avoir la même version mineure. diff --git a/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md b/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md index aa4a91acc232..2c7ad23b75a8 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md @@ -8,7 +8,7 @@ import TabItem from '@theme/TabItem'; ## Prerequisites -This procedure only applies if you wish to migrate from Debian to a newer version of Debian, on another server. +This procedure only applies if you wish to migrate from Debian to a newer version of Debian, on another server. The procedure to migrate from Debian 12 to Debian 13 on the same server (in-place migration) will be available soon on our community platform The Watch. All servers (central, remote and pollers) in your architecture must have the same major version of Centreon. It is also recommended that they have the same minor version. From 1ca66533bc18e6b0a653fa09ecc34216d9cb3d19 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 2 Oct 2026 18:04:43 +0200 Subject: [PATCH 102/179] Clean up lifecycle topic --- .../version-26.10/releases/lifecycle.md | 66 ++---------------- .../version-26.10/releases/lifecycle.md | 67 +------------------ 2 files changed, 7 insertions(+), 126 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/releases/lifecycle.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/releases/lifecycle.md index 21f9d4125889..2a0e83548ad6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/releases/lifecycle.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/releases/lifecycle.md @@ -11,9 +11,6 @@ de Centreon sur une cadence régulière depuis Centreon 18.10, permettant à la entreprises et aux développeurs de planifier leurs feuilles de route avec la certitude d’avoir de la visibilité en amont sur les nouvelles capacités offertes par l'open source. - - - ## Numéros de version Les versions de Centreon sont nommées par l'année et la période de livraison. Par @@ -37,11 +34,11 @@ version. Le cycle de vie d'une version est divisé en 3 phases : -1. Première phase : bogues de toute criticité (minor, major, critical, blocking) et correction de sécurité seront traités par priorité. Des améliorations fonctionnelles seront ajoutées. -2. Seconde phase : bogues et correction de sécurité de criticité major, critical et blocking seront traités par priorité. -3. Troisième phase : bogues et correction de sécurité de criticité blocking seront traités par priorité. +1. Première phase : bugs de toute criticité (minor, major, critical, blocking) et correction de sécurité seront traités par priorité. Des améliorations fonctionnelles seront ajoutées. +2. Seconde phase : bugs et correction de sécurité de criticité major, critical et blocking seront traités par priorité. +3. Troisième phase : bugs bloquants et correction de sécurité seront traités par priorité. Une vulnérabilité dont le délai de remédiation dépasse la date de fin de support de la version n'est pas corrigée sur cette version: passez à une version supportée pour bénéficier du correctif. -> La priorisation des bogues est faite par l'équipe produit Centreon. +> Les vulnérabilités sont traitées selon un [plan de remédiation CVSS v3](../security/security.md#notation-des-vulnérabilités). Les bugs sont priorisés par l'équipe Produit Centreon. La première phase du cycle de vie commence le jour de la sortie de la version. @@ -55,61 +52,6 @@ Le schéma suivant présente le cycle de vie des produits Centreon à partir de ![image](../assets/releases/lifecycle-24.10.png) - - - -## Numéros de version - -Les versions de Centreon sont nommées par l'année et la période de livraison : XX.04 pour la version de printemps, -et XX.10 pour la version d'automne. Par -exemple, Centreon 21.04 a été livrée au printemps 2021. Tous les modules et -composants de la collection de logiciels Centreon possèdent le même numéro de -version. - -## Cadence de publication - -Jusqu'à la version 21.04 incluse, les versions étaient supportées pendant 18 mois. Le cycle de vie d'une version est divisé en 3 phases : - -1. Première phase : bogues de toute criticité (minor, major, critical, - blocking) et correction de sécurité seront traités par priorité -2. Seconde phase : bogues et correction de sécurité de criticité major, - critical et blocking seront traités par priorité. -3. Troisième phase : bogues et correction de sécurité de criticité blocking seront traités par priorité. - -> La priorisation des bogues est faite par l'équipe produit -> Centreon. - -La première phase du cycle de vie commence le jour de la sortie de la version. - -La deuxième phase d'une version commence lorsque la prochaine version majeure -est disponible. Par exemple, la publication de Centreon 21.04 lance la deuxième -phase de Centreon 20.10. - -La troisième phase d'une version commence lorsque la deuxième version majeure -suivante est disponible. Par exemple, la sortie de Centreon 21.04 lance la -troisième phase de Centreon 20.04 et la deuxième phase de Centreon 20.10. - -### À partir de la version 21.10 - -À partir de la version 21.10, les versions sont supportées pendant 2 ans. Le cycle de vie d'une version est divisé en 2 phases de douze mois chacune. - -1. Première phase : bogues de toute criticité (minor, major, critical, - blocking) et correction de sécurité seront traités par priorité -2. Seconde phase : bogues et correction de sécurité de criticité major, - critical et blocking seront traités par priorité. - -> La priorisation des bogues est faite par l'équipe produit -> Centreon. - -### Schéma - -Le schéma suivant présente le cycle de vie des produits Centreon jusqu'à la version 24.04 : - -![image](../assets/releases/lifecycle.png) - - - - ## Tableau de maintenance des versions > Tous les autres produits non décrits dans les tableaux suivants ne sont plus diff --git a/versioned_docs/version-26.10/releases/lifecycle.md b/versioned_docs/version-26.10/releases/lifecycle.md index f37010220e78..347cac7f1f6e 100644 --- a/versioned_docs/version-26.10/releases/lifecycle.md +++ b/versioned_docs/version-26.10/releases/lifecycle.md @@ -11,9 +11,6 @@ Centreon solution at regular intervals since version 18.10, enabling the communi developers to plan their roadmaps with the guarantee of upstream visibility on the latest open source capabilities. - - - ## Version numbers Releases of Centreon are named according to the year and period of delivery. @@ -38,11 +35,11 @@ The lifecycle of a version is divided into three phases: 1. First phase: Bugs of all severity levels (minor, major, critical, blocker) and security issues are fixed according to their priority. Functional enhancements are added. -2. Second phase: Major, critical bugs and blockers, or security issues are +2. Second phase: Major, critical bugs and blockers, and security issues are fixed according to their priority. -3. Third phase: Blockers or security issues are fixed according to their priority. +3. Third phase: Blockers and security issues are fixed according to their priority. A vulnerability whose remediation deadline falls after the version's end of support is not fixed on that version: upgrade to a supported version to get the fix. -> The prioritization is determined by Centreon’s Product team. +> Vulnerabilities follow a [CVSS v3 remediation plan](../security/security.md#vulnerability-scoring). Bugs are prioritized by Centreon's product team. The first phase of the lifecycle begins on the day of a version release. @@ -56,64 +53,6 @@ This diagram outlines the Centreon version lifecycle policy from version 24.10: ![image](../assets/releases/lifecycle-from-24.10.png) - - - -## Version numbers - -Releases of Centreon are named according to the year and period of delivery: -XX.04 for the spring release, and XX.10 for the fall release. -For example, Centreon 21.04 was released in spring 2021. All modules and -components of the Centreon software suite use the same version numbers. - -## Release frequency - -Centreon delivers two releases per year. The first will occur in the spring and will be major (including new products or features as well as larger architecture changes), while the second will be in the fall and will be minor (including primarily enhancements and fixes to existing features). Between these two, Centreon will regularly deliver minor updates (versioned YY.MM.NN), including security/vulnerability fixes, bug fixes and enhancements to the software. - -## Maintenance and security updates - -### Until version 21.04 - -Version 21.04 and prior versions were supported for 18 months. The lifecycle of a version is divided into three phases: - -1. First phase: Bugs of all severity levels (minor, major, critical, blocker) - and security issues are fixed according to their priority. -2. Second phase: Major, critical bugs and blockers, or security issues are - fixed according to their priority. -3. Third phase: Blockers or security issues are fixed according to their priority. - -> The prioritization is determined by Centreon’s Product team. - -The first phase of the lifecycle begins on the day of a version release. - -The second phase of a version begins when the next major version is available. -For example, the release of Centreon 21.04 triggers the second phase of Centreon -20.10. - -The third phase of a version begins when the second next major version is -available. For example, the release of Centreon 21.04 triggers the third phase of -Centreon 20.04 and the second phase of Centreon 20.10. - -### From version 21.10 - -Since version 21.10, versions are supported for two years. The lifecycle of a version is divided into two phases of 12 months each. - -1. First phase: Bugs of all severity levels (minor, major, critical, blocker) - and security issues are fixed according to their priority. -2. Second phase: Major, critical bugs and blockers, or security issues are - fixed according to their priority. - -> The prioritization is determined by Centreon’s Product team. - -### Version lifecycle diagram - -This diagram outlines the Centreon version lifecycle policy until version 24.04: - -![image](../assets/releases/lifecycle.png) - - - - ## Maintenance table for Centreon versions > Any other products not described in the following tables are no longer supported From ba5cd510b7c5d48f4e6d87a834c435246272aac7 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 5 Oct 2026 13:31:49 +0200 Subject: [PATCH 103/179] Fix incorrect version numbers in HA upgrade topics --- .../version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md index 5ed8169464d6..75236b65ebd2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md @@ -6,7 +6,7 @@ description: "Mettre à niveau un cluster Centreon HA depuis la version 23.10 ve import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 23.04 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. +Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 23.10 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. ## Prérequis diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md index 697ccfc8883a..6524981ac766 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md @@ -6,7 +6,7 @@ description: "Mettre à niveau un cluster Centreon HA depuis la version 24.04 ve import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 23.04 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. +Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 24.04 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. ## Prérequis diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md index c9b22c9cd28e..a5bc5639a107 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md @@ -6,7 +6,7 @@ description: "Mettre à niveau un cluster Centreon HA depuis la version 24.10 ve import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 23.04 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. +Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 24.10 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. ## Prérequis diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md index 4f3664d6a18b..f1d10cb7736f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md @@ -5,7 +5,7 @@ title: Montée de version de Centreon HA depuis Centreon 26.10 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 23.04 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. +Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 25.10 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. ## Prérequis diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md index 7b9762e98dd9..990de5bee51b 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md @@ -6,7 +6,7 @@ description: "Upgrade a Centreon HA cluster from version 23.10 to 26.10" import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This chapter describes how to upgrade your Centreon HA platform from version 23.04 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. +This chapter describes how to upgrade your Centreon HA platform from version 23.10 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. ## Prerequisites diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md index 96125e022b0e..c24767aee7ae 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md @@ -6,7 +6,7 @@ description: "Upgrade a Centreon HA cluster from version 24.10 to 26.10" import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This chapter describes how to upgrade your Centreon HA platform from version 24.04 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. +This chapter describes how to upgrade your Centreon HA platform from version 24.10 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. ## Prerequisites diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md index f08f0ef326d0..a1e88b41f8fc 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md @@ -6,7 +6,7 @@ description: "Upgrade a Centreon HA cluster from version 25.10 to 26.10" import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This chapter describes how to upgrade your Centreon HA platform from version 24.04 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. +This chapter describes how to upgrade your Centreon HA platform from version 25.10 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. ## Prerequisites From 894df5b838af95453714a62ea188d538b9baf69b Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 5 Oct 2026 13:51:43 +0200 Subject: [PATCH 104/179] Fix method --- .../version-26.10/upgrade/_intro.mdx | 7 ++ .../upgrade/_upgrade-central.mdx | 74 +++++++++--------- .../version-26.10/upgrade/_intro.mdx | 9 ++- .../upgrade/_upgrade-central.mdx | 77 +++++++++---------- 4 files changed, 86 insertions(+), 81 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx index 793de3c29192..b7ab13e81b41 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx @@ -65,3 +65,10 @@ Avant de monter de version votre plateforme Centreon, assurez-vous que les dép     + +### Créer un jeton d'authentification + +Si vous souhaitez finaliser la mise à jour via l'API, vous aurez besoin d'un jeton d'authentification. Créez-en un avant de commencer la procédure de mise à jour. + +1. Allez dans **Administration > Jetons d'authentification**, puis cliquez sur **Ajouter**. +2. Copiez le jeton et conservez-le précieusement, car il ne sera affiché qu'une seule fois. Vous en aurez besoin à l'[étape 7](./_upgrade-central.mdx#étape-7--finaliser-la-montée-de-version). \ No newline at end of file diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx index 6ab2abdd85bc..db6cc02f439a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx @@ -224,66 +224,62 @@ commande suivante : 2. Finalisez le processus de montée de version : - - - -1. Connectez-vous à l'interface web de Centreon pour poursuivre le processus de mise à jour. Cliquez sur **Next** : - - ![image](../assets/upgrade/web_update_1.png) + + -2. Cliquez sur **Next** : + 1. Connectez-vous à l'interface web de Centreon pour poursuivre le processus de mise à jour. Cliquez sur **Next** : - ![image](../assets/upgrade/web_update_2.png) + ![image](../assets/upgrade/web_update_1.png) -3. Les notes de version décrivent les principaux changements. Cliquez sur **Next** : + 2. Cliquez sur **Next** : - ![image](../assets/upgrade/web_update_3.png) + ![image](../assets/upgrade/web_update_2.png) -4. Ce processus réalise les différentes mises à jour. Cliquez sur **Next** : + 3. Les notes de version décrivent les principaux changements. Cliquez sur **Next** : - ![image](../assets/upgrade/web_update_4.png) + ![image](../assets/upgrade/web_update_3.png) -5. Votre serveur Centreon est maintenant à jour. Cliquez sur **Finish** pour accéder à la page -de connexion : + 4. Ce processus réalise les différentes mises à jour. Cliquez sur **Next** : - ![image](../assets/upgrade/web_update_5.png) + ![image](../assets/upgrade/web_update_4.png) -6. [Déployez la configuration du serveur central depuis l'interface web de Centreon](../monitoring/monitoring-servers/deploying-a-configuration.md). + 5. Votre serveur Centreon est maintenant à jour. Cliquez sur **Finish** pour accéder à la page + de connexion : - - + ![image](../assets/upgrade/web_update_5.png) -1. Rendez-vous à la page **Administration > Jetons d'authentification**, puis cliquez sur **Ajouter**. + 6. [Déployez la configuration du serveur central depuis l'interface web de Centreon](../monitoring/monitoring-servers/deploying-a-configuration.md). -3. Copiez le jeton afin de l'utiliser dans la requête suivante. Conservez-le précieusement : il ne sera pas affiché une seconde fois. + + -4. Dans votre terminal, saisissez cette requête en utilisant l'adresse IP de votre plateforme et en remplaçant **mytoken** par votre jeton : + 1. Dans votre terminal, saisissez cette requête en utilisant l'adresse IP de votre plateforme et en remplaçant **mytoken** par votre jeton (comme précisé dans les prérequis) : - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: mytoken' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` + ```shell + curl --location --request POST 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ + --header 'X-AUTH-TOKEN: mytoken' \ + --header 'Content-Type: application/json' \ + --data '{ + "components": [ + { + "name": "centreon-web" + } + ] + }' + ``` -5. Cette requête ne renvoie aucun résultat. Pour vérifier que la mise à jour a bien été appliquée, consultez le numéro de version affiché sur la page de connexion de l'interface web de Centreon. + 2. Cette requête ne renvoie aucun résultat. Pour vérifier que la mise à jour a bien été appliquée, consultez le numéro de version affiché sur la page de connexion de l'interface web de Centreon. - - + + -6. Enfin, redémarrez Broker, Engine et Gorgone sur le serveur central à l'aide de cette commande : +3. Enfin, redémarrez Broker, Engine et Gorgone sur le serveur central à l'aide de cette commande : ```shell systemctl restart cbd centengine gorgoned ``` -7. Mettez à jour les permissions sur les fichiers de configuration de centreon-broker. +4. Mettez à jour les permissions sur les fichiers de configuration de centreon-broker. @@ -296,7 +292,7 @@ de connexion : -8. Consultez les procédures dédiées à [Centreon MBI](../reporting/update.md) et à [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. +5. Consultez les procédures dédiées à [Centreon MBI](../reporting/update.md) et à [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. ### Étape 8 : Actions post montée de version diff --git a/versioned_docs/version-26.10/upgrade/_intro.mdx b/versioned_docs/version-26.10/upgrade/_intro.mdx index 7b09b0b13dfd..a21f08995b86 100644 --- a/versioned_docs/version-26.10/upgrade/_intro.mdx +++ b/versioned_docs/version-26.10/upgrade/_intro.mdx @@ -64,4 +64,11 @@ Before upgrading your Centreon platform, make sure the following package reposit * centreon-modules, if you are using Centreon Business Edition.     -     \ No newline at end of file +     + +### Create an authentication token + +If you want to finalize the upgrade via the API, you will need an authentication token. Create one before starting the upgrade process. + +1. Go to **Administration > Authentication tokens**, then click **Add**. +2. Copy the token and store it carefully, as it will not be displayed twice. You will need it at [Step 7](./_upgrade-central.mdx#step-7-finalize-the-upgrade). \ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index 84f45d44d872..1cca04c32aa8 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -208,8 +208,7 @@ AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javasc ### Step 7: Finalize the upgrade -1. Before starting the web upgrade process, upgrade the [Centreon BAM module](../service-mapping/upgrade.md) and reload the Apache server with the -following command: +1. Before starting the web upgrade process, upgrade the [Centreon BAM module](../service-mapping/upgrade.md) and reload the Apache server with the following command: @@ -223,66 +222,62 @@ following command: 2. Finalize the upgrade process: - - - -1. Log on to the Centreon web interface to continue the update process. Click **Next**: - - ![image](../assets/upgrade/web_update_1.png) + + -2. Click **Next**: + 1. Log on to the Centreon web interface to continue the update process. Click **Next**: - ![image](../assets/upgrade/web_update_2.png) + ![image](../assets/upgrade/web_update_1.png) -3. The release notes describe the main changes. Click **Next**: + 2. Click **Next**: - ![image](../assets/upgrade/web_update_3.png) + ![image](../assets/upgrade/web_update_2.png) -4. This process performs the various upgrades. Click **Next**: + 3. The release notes describe the main changes. Click **Next**: - ![image](../assets/upgrade/web_update_4.png) + ![image](../assets/upgrade/web_update_3.png) -5. Your Centreon server is now up to date. Click **Finish** to access the login -page: + 4. This process performs the various upgrades. Click **Next**: - ![image](../assets/upgrade/web_update_5.png) + ![image](../assets/upgrade/web_update_4.png) -6. [Deploy the central's configuration from the Centreon web UI](../monitoring/monitoring-servers/deploying-a-configuration.md). + 5. Your Centreon server is now up to date. Click **Finish** to access the login + page: - - + ![image](../assets/upgrade/web_update_5.png) -1. Go to **Administration > Authentication tokens**, then click **Add**. + 6. [Deploy the central's configuration from the Centreon web UI](../monitoring/monitoring-servers/deploying-a-configuration.md). -3. Copy the token to use it in the next request. Store it carefully, as it will not be displayed twice. + + -4. In your terminal, enter this request, using the correct IP address for your platform, and replacing **mytoken** with your actual token: + 1. In your terminal, enter this request, using the correct IP address for your platform, and replacing **mytoken** with your actual token (as described in the prerequisites): - ```shell - curl --location --request PATCH 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ - --header 'X-AUTH-TOKEN: mytoken' \ - --header 'Content-Type: application/json' \ - --data '{ - "components": [ - { - "name": "centreon-web" - } - ] - }' - ``` + ```shell + curl --location --request POST 'http://10.25.XX.XX:80/centreon/api/latest/platform/updates' \ + --header 'X-AUTH-TOKEN: mytoken' \ + --header 'Content-Type: application/json' \ + --data '{ + "components": [ + { + "name": "centreon-web" + } + ] + }' + ``` -5. This request does not return any result. To check if the update has been successfully applied, read the version number displayed on the Centreon web interface login page. + 2. This request does not return any result. To check if the update has been successfully applied, read the version number displayed on the Centreon web interface login page. - - + + -6. Finally, restart Broker, Engine and Gorgone on the central server by running this command: +3. Finally, restart Broker, Engine and Gorgone on the central server by running this command: ```shell systemctl restart cbd centengine gorgoned ``` -7. Update the permissions on the centreon-broker configuration files. +4. Update the permissions on the centreon-broker configuration files. @@ -295,7 +290,7 @@ page: -8. Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. +5. Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. ### Step 8: Post-upgrade actions From 45d3b6fa9727617c8356ecd2a783c947c6881823 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 5 Oct 2026 14:07:44 +0200 Subject: [PATCH 105/179] Fix link --- .../version-26.10/upgrade/_intro.mdx | 2 +- versioned_docs/version-26.10/upgrade/_intro.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx index b7ab13e81b41..6a1ea6eec21e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx @@ -71,4 +71,4 @@ Avant de monter de version votre plateforme Centreon, assurez-vous que les dép Si vous souhaitez finaliser la mise à jour via l'API, vous aurez besoin d'un jeton d'authentification. Créez-en un avant de commencer la procédure de mise à jour. 1. Allez dans **Administration > Jetons d'authentification**, puis cliquez sur **Ajouter**. -2. Copiez le jeton et conservez-le précieusement, car il ne sera affiché qu'une seule fois. Vous en aurez besoin à l'[étape 7](./_upgrade-central.mdx#étape-7--finaliser-la-montée-de-version). \ No newline at end of file +2. Copiez le jeton et conservez-le précieusement, car il ne sera affiché qu'une seule fois. Vous en aurez besoin à l'étape 7 de la procédure d'upgrade. \ No newline at end of file diff --git a/versioned_docs/version-26.10/upgrade/_intro.mdx b/versioned_docs/version-26.10/upgrade/_intro.mdx index a21f08995b86..1048f3557115 100644 --- a/versioned_docs/version-26.10/upgrade/_intro.mdx +++ b/versioned_docs/version-26.10/upgrade/_intro.mdx @@ -71,4 +71,4 @@ Before upgrading your Centreon platform, make sure the following package reposit If you want to finalize the upgrade via the API, you will need an authentication token. Create one before starting the upgrade process. 1. Go to **Administration > Authentication tokens**, then click **Add**. -2. Copy the token and store it carefully, as it will not be displayed twice. You will need it at [Step 7](./_upgrade-central.mdx#step-7-finalize-the-upgrade). \ No newline at end of file +2. Copy the token and store it carefully, as it will not be displayed twice. You will need it at step 7 of the upgrade procedure. \ No newline at end of file From 316697fae179de25d2b5455b21e9a7fde9adcefc Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 6 Oct 2026 09:50:41 +0200 Subject: [PATCH 106/179] Key rotation in HA topics --- .../version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md | 2 +- .../version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md | 2 +- 10 files changed, 10 insertions(+), 10 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md index 15ec54e5e600..194296abd350 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md @@ -27,7 +27,7 @@ Avant toute chose, il est préférable de s’assurer de l’état et de la cons ### Mettre à jour la clé de signature RPM -Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. +Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 2 décembre 2025. Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. ### Modifier le script centreon_central_sync script (MBI uniquement) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md index 75236b65ebd2..1ebef4b448ab 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md @@ -27,7 +27,7 @@ Avant toute chose, il est préférable de s’assurer de l’état et de la cons ### Mettre à jour la clé de signature RPM -Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. +Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 2 décembre 2025. Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. ### Modifier le script centreon_central_sync script (MBI uniquement) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md index 6524981ac766..6c7cad3e6a76 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md @@ -27,7 +27,7 @@ Avant toute chose, il est préférable de s’assurer de l’état et de la cons ### Mettre à jour la clé de signature RPM -Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. +Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 2 décembre 2025. Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. ### Modifier le script centreon_central_sync script (MBI uniquement) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md index a5bc5639a107..48188adba7fb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md @@ -27,7 +27,7 @@ Avant toute chose, il est préférable de s’assurer de l’état et de la cons ### Mettre à jour la clé de signature RPM -Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. +Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 2 décembre 2025. Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. ### Modifier le script centreon_central_sync script (MBI uniquement) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md index f1d10cb7736f..cf9f39931264 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md @@ -26,7 +26,7 @@ Avant toute chose, il est préférable de s’assurer de l’état et de la cons ### Mettre à jour la clé de signature RPM -Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. +Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 2 décembre 2025. Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. ### Modifier le script centreon_central_sync script (MBI uniquement) diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md index 6f447a8a2b34..1ec01f0aa0d0 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md @@ -27,7 +27,7 @@ Be sure that you have fully backed up your environment for the following servers ### 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. +For security reasons, the keys used to sign Centreon RPMs are rotated regularly. The last change occurred on December 2, 2025. When upgrading from an older version, you need to go through the [key rotation procedure](../../security/key-rotation.md#existing-installation), to remove the old key and install the new one. ### Update the centreon_central_sync script (MBI only) diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md index 990de5bee51b..96001126c49a 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md @@ -27,7 +27,7 @@ Be sure that you have fully backed up your environment for the following servers ### 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. +For security reasons, the keys used to sign Centreon RPMs are rotated regularly. The last change occurred on December 2, 2025. When upgrading from an older version, you need to go through the [key rotation procedure](../../security/key-rotation.md#existing-installation), to remove the old key and install the new one. ### Update the centreon_central_sync script (MBI only) diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md index ee70fd296013..cf9d1c16be69 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md @@ -27,7 +27,7 @@ Be sure that you have fully backed up your environment for the following servers ### 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. +For security reasons, the keys used to sign Centreon RPMs are rotated regularly. The last change occurred on December 2, 2025. When upgrading from an older version, you need to go through the [key rotation procedure](../../security/key-rotation.md#existing-installation), to remove the old key and install the new one. ### Update the centreon_central_sync script (MBI only) diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md index c24767aee7ae..de9e34557e9f 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md @@ -27,7 +27,7 @@ Be sure that you have fully backed up your environment for the following servers ### 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. +For security reasons, the keys used to sign Centreon RPMs are rotated regularly. The last change occurred on December 2, 2025. When upgrading from an older version, you need to go through the [key rotation procedure](../../security/key-rotation.md#existing-installation), to remove the old key and install the new one. ### Update the centreon_central_sync script (MBI only) diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md index a1e88b41f8fc..adacb9c04a87 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md @@ -27,7 +27,7 @@ Be sure that you have fully backed up your environment for the following servers ### 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. +For security reasons, the keys used to sign Centreon RPMs are rotated regularly. The last change occurred on December 2, 2025. When upgrading from an older version, you need to go through the [key rotation procedure](https://docs.centreon.com/docs/security/key-rotation/#existing-installation), to remove the old key and install the new one. ### Update the centreon_central_sync script (MBI only) From 411ffd4a005a15908c599c6db182e9372285d6ae Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 6 Oct 2026 09:51:31 +0200 Subject: [PATCH 107/179] Fix link --- .../version-26.10/upgrade/_upgrade-central.mdx | 2 +- versioned_docs/version-26.10/upgrade/_upgrade-central.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx index db6cc02f439a..4d4caf2dfd02 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx @@ -202,7 +202,7 @@ AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javasc
    • Si vous utilisiez MariaDB {props.oldMariadbVersion}, [montez-la de version](upgrade-mariadb.md) vers la version 11.8.
      • - {props.showSecondPoint &&
    • Si vous utilisiez MySQL 8.0, [montez-la de version vers la 8.4](upgrade-mysql.md).
      • } + {props.showSecondPoint &&
    • Si vous utilisiez MySQL 8.0, montez-la de version vers la 8.4.
      • } {props.showThirdPoint &&
    • Si vous utilisiez déjà MySQL 8.4, vous n'avez rien à faire.
      • }
    diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index 1cca04c32aa8..7cfe443f3d4a 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -202,7 +202,7 @@ AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javasc
    • If you were using MariaDB {props.oldMariadbVersion}, [upgrade it](upgrade-mariadb.md) to version 11.8.
      • - {props.showSecondPoint &&
    • If you were using MySQL 8.0, [upgrade it to version 8.4](upgrade-mysql.md).
      • } + {props.showSecondPoint &&
    • If you were using MySQL 8.0, upgrade it to version 8.4.
      • } {props.showThirdPoint &&
    • If you were already using MySQL 8.4, you don't need to do anything.
      • }
    From bb4ca82917dd533da90e30e5a269893d4fb225f0 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 6 Oct 2026 15:45:56 +0200 Subject: [PATCH 108/179] Import Link --- _review/unattended.restructured.md | 130 ++ _review/unattended.review-2.html | 288 ++++ _review/unattended.review.html | 441 +++++ _review/upgrade-debian-in-place.review.html | 183 ++ .../administration/self-signed-certificate.md | 419 +++++ centreon-os-support-vs-26-10.md | 62 + .../migrate/migrate-from-el-to-el.md.bak | 285 ++++ .../reporting/installation.md.bak | 1473 +++++++++++++++++ .../upgrade/centreon-ha/upgrade-from-23.04.md | 1 + .../upgrade/centreon-ha/upgrade-from-23.10.md | 1 + .../upgrade/centreon-ha/upgrade-from-24-04.md | 1 + .../upgrade/centreon-ha/upgrade-from-24-10.md | 1 + .../upgrade/centreon-ha/upgrade-from-25-10.md | 1 + secure_db.txt | 34 + src/components/UpgradeMatrixTable.jsx | 72 + .../unattended.md.bak | 164 ++ .../installation/prerequisites.md.bak | 336 ++++ .../migrate/upgrade-debian-in-place.md | 632 +++++++ .../upgrade/centreon-ha/upgrade-from-23.04.md | 1 + .../upgrade/centreon-ha/upgrade-from-23.10.md | 1 + .../upgrade/centreon-ha/upgrade-from-24-04.md | 1 + .../upgrade/centreon-ha/upgrade-from-24-10.md | 1 + .../upgrade/centreon-ha/upgrade-from-25-10.md | 1 + 23 files changed, 4529 insertions(+) create mode 100644 _review/unattended.restructured.md create mode 100644 _review/unattended.review-2.html create mode 100644 _review/unattended.review.html create mode 100644 _review/upgrade-debian-in-place.review.html create mode 100644 _translation/version-26.10/administration/self-signed-certificate.md create mode 100644 centreon-os-support-vs-26-10.md create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md.bak create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/installation.md.bak create mode 100644 secure_db.txt create mode 100644 src/components/UpgradeMatrixTable.jsx create mode 100644 versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md.bak create mode 100644 versioned_docs/version-26.10/installation/prerequisites.md.bak create mode 100644 versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md diff --git a/_review/unattended.restructured.md b/_review/unattended.restructured.md new file mode 100644 index 000000000000..adc6f5aec9a4 --- /dev/null +++ b/_review/unattended.restructured.md @@ -0,0 +1,130 @@ +--- +id: unattended-install-central-restructured +title: Unattended installation of a central server +description: "Install a central server quickly using an unattended script" +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +An unattended installation lets you install a central server by passing all the required settings as options to the installation script. The script then runs the whole procedure, including the web installation, without further input. + +This is useful when you need to install several central servers with identical settings, when you install from a deployment tool or a CI pipeline, or when you have no interactive access to the target machine. + +> An unattended installation always sets up the central server with a local database. To use a remote database, [install the central server from packages](using-packages.md). + +## Prerequisites + +1. Update your system: + + + + + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms + ``` + + Replace **my_username** and **my_password** with the credentials of your RedHat account. + + + + + ```shell + dnf update + ``` + + + + + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms + ``` + + Replace **my_username** and **my_password** with the credentials of your RedHat account. + + + + + ```shell + dnf update + ``` + + + + + ```shell + apt update && apt upgrade + ``` + + + + +2. Download the script: + + ```shell + curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh + ``` + +## Installation + +1. As **root**, run the script with the options you want. A full log, including any errors, will be written to `/var/log/centreon-unattended-.log`. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    SettingsCommand with autogenerated admin DB passwordWith custom admin DB password
    Using MariaDB and no TLSbash /tmp/unattended.sh install -t central -v 26.10 -r stable -sbash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -p XXXXX
    Using MySQL and no TLSbash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -d mysqlbash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -d mysql -p XXXXX
    Using MariaDB and TLSbash /tmp/unattended.sh install -t central -v 26.10 -r stable -s --tls=enabledbash /tmp/unattended.sh install -t central -v 26.10 -r stable -s --tls=enabled -p XXXXX
    Using MySQL and TLSbash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -d mysql --tls=enabledbash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -d mysql --tls=enabled -p XXXXX
    + +4. Configure Centreon: go to `http:///centreon`, where `` is your server's IP address, and log in. Then follow the + [initialization of the monitoring](../web-and-post-installation.md#initialization-of-the-monitoring) steps. + +5. Start using Centreon: follow our [Getting started](../../getting-started/welcome.md) guide to start monitoring your resources. + +## Options + +To display the full list of options, run: + +```shell +bash /tmp/unattended.sh -h +``` + +The main options are the following: + +| Option | Description | +|--------|-------------| +| `-t ` | Type of server to install. Use `central` to install a central server. | +| `-d ` | Database to install. By default, the script installs MariaDB: use `-d MySQL` to install MySQL instead. | +| `--tls enabled` | Installs the central server in TLS mode: the connections to the web interface and to the database are encrypted. Without this option, the central server is installed without TLS. | +| `-p ` | Password of the default **admin** account. If you omit this option, the script generates a password and tells you where it is stored. | +| `-s` | Silent installation: the script does not prompt you for anything. | +| `-l ` | Level of detail of the log file: `DEBUG`, `INFO`, `WARN` or `ERROR`. | diff --git a/_review/unattended.review-2.html b/_review/unattended.review-2.html new file mode 100644 index 000000000000..75c7586abdc2 --- /dev/null +++ b/_review/unattended.review-2.html @@ -0,0 +1,288 @@ + + + + + +Editorial review + + + +
    +

    Editorial review

    +

    Source: versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md — reviewed 2026-08-27. Language: English (US). Product glossary: infra-monitoring.csv + common.csv.

    + + + +
    +

    1 · Plain language

    + +
    The script uses those values to complete the installation on its own, so the process is quick and requires little effort. (l. 10)
    +
    + Plain language + Suggested rewrite: "The script then completes the installation without any further input from you." + Why: "the process is quick and requires little effort" is unmeasurable filler — the reader already knows why they chose an unattended install. Saying what the script does (no further input needed) is the actual useful fact. +
    + +
    This is useful when you need to install several central servers with identical settings, when you install from a deployment tool or CI pipeline, or when you have no interactive access to the target machine. (l. 12 — 35 words)
    +
    + Plain language + Suggested rewrite: convert to a bulleted list — "Use an unattended installation when:" followed by three bullets ("you install several central servers with identical settings", "you install from a deployment tool or a CI/CD pipeline", "you have no interactive access to the target machine"). + Why: a 35-word sentence with three parallel "when" clauses is a list in disguise. Bullets make the three cases scannable, which is how readers use an intro block. +
    + +
    …when you install from a deployment tool or CI pipeline… (l. 12)
    +
    + Plain language + Suggested rewrite: "from a deployment tool or a CI/CD pipeline". + Why: "CI" is an unexpanded abbreviation. It appears nowhere else on the page, so a reader who does not already know it gets no help. "CI/CD pipeline" is the form used across the rest of the documentation and is self-explanatory enough in context. +
    + +
    A full log, including any errors, will be written to /var/log/centreon-unattended-<date>.log. (l. 74)
    +
    + Plain language + Suggested rewrite: "The script writes a full log, including any errors, to /var/log/centreon-unattended-<date>.log." + Why: actor-obscuring passive plus future tense. The active present tense names the agent (the script) and matches the tense used in the Options table ("the script installs MariaDB", "the script generates a password"). +
    + +
    Installs the central server in TLS mode: the connections to the web interface and to the database are encrypted. Without this option, the central server is installed without TLS. (l. 127)
    +
    + Plain language + Suggested rewrite: "Installs the central server in TLS mode: the script encrypts the connections to the web interface and to the database. Omit this option to install without TLS." + Why: two passives in two sentences ("are encrypted", "is installed"). Naming the script as the actor in the first clause and using the imperative "Omit this option" in the second removes both and shortens the cell. +
    +
    + +
    +

    2 · Idiomaticity

    + +
    The main options are the following: (l. 121)
    +
    + Idiomaticity + Suggested rewrite: "The main options are:" or "Here are the main options:". + Why: "are the following" is a literal rendering of « sont les suivantes ». It is grammatical but reads translated; native technical English drops the placeholder noun before a table. +
    + +
    Replace my_username and my_password with the credentials of your RedHat account. (l. 29, l. 47)
    +
    + Idiomaticity + Suggested rewrite: "Replace my_username and my_password with your Red Hat account credentials." + Why: "the credentials of your X account" is an of-genitive calque of « les identifiants de votre compte X ». English prefers the attributive form. (See also the Spelling section for "RedHat".) +
    + +
    Level of detail of the log file: DEBUG, INFO, WARN or ERROR. (l. 130)
    +
    + Idiomaticity + Suggested rewrite: "Verbosity level of the log file: …" or "Log level: …". + Why: the stacked "Level of detail of the log file" reads awkwardly, and "log level" / "verbosity level" is the established collocation in this domain — it is also what the reader will see in the script's own -h output. +
    + +
    Go to http://<SERVER_IP>/centreon, where <SERVER_IP> is your server's IP address, and log in. (l. 108)
    +
    + Idiomaticity + Suggested rewrite: "Go to http://<SERVER_IP>/centreon (where <SERVER_IP> is your server's IP address) and log in." + Why: the comma-delimited relative clause strands "and log in" so far from "Go to" that the sentence has to be re-parsed. Parentheses keep the two imperatives adjacent. +
    + +
    Start using Centreon: follow our Getting started guide to start monitoring your resources. (l. 111)
    +
    + Idiomaticity + Suggested rewrite: "Start using Centreon: follow our Getting started guide to begin monitoring your resources." + Why: "Start … start" in one short sentence is an unintentional echo. Swapping the second verb for "begin" (or cutting it: "…guide to monitor your resources") removes it. +
    +
    + +
    +

    3 · Spelling

    + +
    …with the credentials of your RedHat account. (l. 29 and l. 47)
    +
    + Spelling + Correction: Red Hat (two words, both capitalized) — the vendor's own trademark spelling. + Why: "RedHat" is a misspelling of a proper noun. Note for the wider fix: the repository currently contains 12 occurrences of "RedHat" against 1 of "Red Hat", so the error is inherited from the older pages rather than introduced here — worth a repo-wide correction rather than a fix limited to this file. +
    + +

    US/UK spelling: no issues found. The script's center/centre hit is a false positive — the only match is the string centreon inside the download URL (l. 69). No other misspellings or typos found ("autogenerated", "unattended", "MariaDB", "MySQL" are all correct).

    +
    + +
    +

    4 · Style & terminology

    + +
    Commands: --tls=enabled (l. 97, 98, 102, 103) — Options table: --tls enabled (l. 127)
    +
    + Style & terminology + Correction: use one form in both places — --tls=enabled, matching the copy-pasteable commands. + Why: the same option is documented two ways on one page. This is not only a consistency nit: a reader who copies the syntax from the Options table may run a command the script does not accept. Confirm with the script which separator is valid, then align both. +
    + +
    Commands: -d mysql (l. 92, 93, 102, 103) — Options table: "use -d MySQL to install MySQL instead" (l. 126)
    +
    + Style & terminology + Correction: use lowercase -d mysql in the Options table to match the commands. + Why: same problem as above — the value's casing differs between the two tables. Keep the product name capitalized in prose ("to install MySQL instead") but the literal option value lowercase. +
    + +
    "Command with autogenerated admin DB password" / "Command with custom admin DB password" (l. 80–81) vs. "Password of the default admin database account" (l. 128)
    +
    + Style & terminology + Correction: (a) spell out "database" rather than "DB" in the column headers, and (b) verify what -p actually sets. + Why: "DB" is an abbreviation used nowhere else on the page — "admin database password" is only a few characters longer in a header that already runs long. More importantly, the 25.10 version of this page documented the same option as "the password for the default admin account", i.e. the Centreon web interface account, not a database account. One of the two pages is wrong about a credential, and the reader cannot tell which. This needs a technical check before publication. +
    + +
    Installation section step numbering: 1. (l. 74) → 4. (l. 108) → 5. (l. 111)
    +
    + Style & terminology + Correction: renumber to 1., 2., 3.. + Why: leftover numbering from the reorganization that moved the "update your system" and "download the script" steps into Prerequisites. Docusaurus renumbers ordered lists on render, so the published page looks fine — but the source misleads the next editor, and the 2/3 gap invites the reader of the raw file to think two steps were lost. While renumbering, also align the indentation of the raw <table> block (l. 76–106, 4 spaces) with the 3-space continuation indent used in the Prerequisites steps. +
    + +
    Row "Using MariaDB and no TLS": bash /tmp/unattended.sh install -t central -v 26.10 (l. 87–88)
    +
    + Style & terminology + Correction: add -s, as in the other three rows. + Why: this is the only one of the four rows without -s, and -s is defined on the same page as "the script does not prompt you for anything". On a page whose subject is unattended installation, the default MariaDB command is the one that still prompts — almost certainly an omission rather than an intentional difference, and it is the row most readers will copy. +
    + +
    Options table descriptions: "Type of server to install." / "Database to install." / "Password of the default admin database account." / "Silent installation:" / "Level of detail of the log file:" — vs. "Installs the central server in TLS mode:" (l. 125–130)
    +
    + Style & terminology + Correction: recast the --tls description as a noun phrase, e.g. "TLS mode: the script encrypts the connections to the web interface and to the database. Omit this option to install without TLS." + Why: five of the six rows open with a noun phrase; only --tls opens with a finite verb. Parallel grammatical form across a reference table lets the reader scan the column instead of reading it. +
    + +
    DEBUG, INFO, WARN or ERROR. (l. 130)
    +
    + Style & terminology + Correction: "DEBUG, INFO, WARN, or ERROR." + Why: missing serial (Oxford) comma, which US-English technical style — the register this documentation uses — applies before the final item in a list. +
    + +
    Table column header: "Settings" (l. 79)
    +
    + Style & terminology + Correction: "Configuration" or "Database and TLS options". + Why: the column holds four database/TLS combinations, not settings the reader enters. "Settings" also collides with the intro's use of the word for the option values passed to the script (l. 10, l. 12), so one term names two different things on the same page. +
    + +

    Glossary conformity (common.csv + infra-monitoring.csv): no deviations. "central server", "database", "TLS", "web interface" and "Centreon" are used consistently and match the approved source terms. Voice is consistently second person ("you"), and blockquote notes (>) match the convention of the surrounding installation pages — no :::note admonitions are used anywhere in version-26.10/installation/, so the > on l. 14 is correct here.

    +
    + + + +
    +

    Summary

    +
    + + + + + + + + + + +
    CriterionIssuesTakeaway
    Plain language5Two passives hiding the script as actor, one 35-word sentence that should be a bulleted list, one unexpanded "CI", and one filler clause
    Idiomaticity5Reads slightly translated in places: "are the following", "the credentials of your … account", "Level of detail of the log file"
    Spelling1"RedHat" → "Red Hat" (×2); US/UK spelling clean, the centre hit is a false positive
    Style & terminology8Command syntax contradicts the Options table (--tls, -d); missing -s in the first command; "admin DB password" may name the wrong account; step numbering jumps 1 → 4 → 5
    Links & anchors0No issues found — all three relative links and the one anchor resolve
    Total19Three items need a technical decision, not just an edit: the --tls separator, the missing -s, and what -p actually sets
    +
    +
    +
    + + diff --git a/_review/unattended.review.html b/_review/unattended.review.html new file mode 100644 index 000000000000..b53d14dd20c2 --- /dev/null +++ b/_review/unattended.review.html @@ -0,0 +1,441 @@ + + + + + +Editorial review + + + +
    +

    Editorial review

    +

    + Source: versioned_docs/version-26.10/installation/installation-of-a-central-server/unattended.md + — reviewed 2026-08-27 — language: English (US) — product glossary: infra-monitoring + common +

    + + + +
    +

    0 · Blockers (outside the five criteria)

    +

    These are not editorial issues but the page cannot ship as it stands. They are + listed separately and are not counted in the summary table.

    + +
    To use MySQL:
    + ```shell
    +
    + ```
    +
    + To install the central server in TLS mode (…):
    + ```shell
    +
    + ```
    +
    + Blocker + Lines 93–103 — the entire “Options” section is empty. Both code + blocks contain no command, so the section as published tells the reader that + options exist and then shows nothing. Either fill in the two commands or remove + the section until the option flags are confirmed. +
    + +
    bash /tmp/unattended.sh install -t central -v 26.10 -r stable -s -p <admin_password> -l DEBUG …
    +
    + Blocker + Line 70/76 — the -s flag contradicts the “Options” intro. + The intro says the default install is “without TLS, and with MariaDB”, but the + basic command already passes -s, which is never explained. Document + what -s, -t, -v, -r, -p + and -l do (a short option table would serve better than the current + prose), so the reader can tell the default from the override. +
    + +
    <!-- This is useful when you need to install several central servers with identical settings, when you install from a deployment tool or CI pipeline, or when you have no interactive access to the target machine. -->
    +
    + Blocker + Line 11 — useful “when to use this” content is hidden in an HTML comment. + This is the one sentence that tells the reader whether the page applies to them. + Decide: publish it (recommended, reworded per criterion 1) or delete it. Leaving + commented-out prose in a shipped page invites it to rot. +
    + +
    subscription-manager register --username my_username --password my_password --auto-attach --force
    +
    + Blocker + Lines 22 and 38 — the note explaining the placeholders was dropped. + The previous revision carried “Replace my_username and + my_password with the credentials of your RedHat account.”, and the + sibling pages installation-of-a-poller/unattended.md:24 and + installation-of-a-remote-server/unattended.md:24 still do. Restore it + in both RHEL tabs. +
    +
    + +
    +

    1 · Plain language

    + +
    An unattended installation lets you install a central server by passing all the required settings as options when you run the installation script. The script uses those values to complete the installation on its own, so the process is quick and requires little effort.
    +
    + Plain language + Suggested rewrite: “An unattended installation lets you install a central server + by passing all the required settings as options to the installation script. The + script then runs the whole procedure, including the web installation, without + further input.”
    + Why: “so the process is quick and requires little effort” is a + value claim, not information — the reader cannot act on it. The rewrite replaces + it with the fact that actually sells the page, and restores “including the web + installation”, which the previous revision stated and this one lost. Also + “lets you install … when you run the installation script” repeats “install” + three times in one sentence. +
    + +
    Run the script as root. Here is the basic command that installs the central with the default settings :
    +
    + Plain language + Suggested rewrite: “As root, run one of the following commands to + install a central server with the default settings:”
    + Why: “Here is the basic command that…” is a filler frame around + the instruction, and “command” is singular while two commands follow. Fold the + frame into the imperative. (The stray space before the colon and “the central” + are handled under criterion 4.) +
    + +
    In both cases, you will get a full log file with all errors in your tmp folder, named unattended(date).log.
    +
    + Plain language + Suggested rewrite: “Both commands write a full log, including any errors, to + /tmp/unattended-<date>.log.”
    + Why: “a full log file with all errors” reads as if the file + contained only errors. Naming the path once, as a path, removes the need for + “in your … folder, named …”. (The tmp vs /tmp and the + filename pattern are flagged under criterion 4.) +
    + +
    If you don't specify any options when running the script, it will install the central server without TLS, and with MariaDB.
    To change this, pass the corresponding options:
    +
    + Plain language + Suggested rewrite: “By default, the script installs the central server with + MariaDB and without TLS. To change this, use the following options:”
    + Why: “If you don't specify any options … it will” is a + four-clause way of saying “by default”. Leading with the default also puts the + information the reader is scanning for first. +
    + +
    Configure Centreon: log in to the Centreon web interface via the URL http://[SERVER_IP]/centreon where [SERVER_IP] is the real IP address of your server.
    +
    + Plain language + Suggested rewrite: “Configure Centreon: go to + http://<SERVER_IP>/centreon, where + <SERVER_IP> is your server's IP address, and log in.”
    + Why: “log in to the web interface via the URL X” makes the URL a + subordinate detail when it is the actionable part. Put the address first, the + explanation second. (“the real IP address” is flagged under criterion 2.) +
    +
    + +
    +

    2 · Idiomaticity

    + +
    follow our quick start guide to start your monitoring.
    +
    + Idiomaticity + Suggested rewrite: “follow our quick start guide to start monitoring your + resources.”
    + Why: “start your monitoring” is a calque of « démarrer votre + supervision ». In English, monitoring is not a countable thing you own; + it takes an object. This phrasing also appears in the 25.10 page, so fixing it + here is worth propagating. +
    + +
    where [SERVER_IP] is the real IP address of your server
    +
    + Idiomaticity + Suggested rewrite: “where <SERVER_IP> is your server's IP + address”.
    + Why: “the real IP address” is a literal rendering of « l'adresse + IP réelle ». A native reader hears it as “as opposed to a fake one”. The + placeholder already implies substitution, so “real” adds nothing; if the contrast + must be stated, “actual” is the idiomatic choice. +
    + +
    In both cases, you will get a full log file …
    +
    + Idiomaticity + Suggested rewrite: “Both commands write a full log to …”
    + Why: “you will get” describes what happens to the reader rather + than what the tool does. The repo's house voice for tool behaviour is active and + tool-subject (“the script tells you where the password is stored”, used two lines + above) — this sentence breaks that pattern. +
    + +
    To get help on the script, use the following command: bash unattended.sh -h
    +
    + Idiomaticity + Suggested rewrite: “To display the script's help, run: + bash /tmp/unattended.sh -h”
    + Why: “get help on X” collocates with people and topics, not with + programs; a program's help is displayed. Note also that the path is + missing here while every other invocation on the page uses + /tmp/unattended.sh — copy-pasted as written, this command fails. +
    +
    + +
    +

    3 · Spelling

    + +
    To install the central server in TLS mode (the conneection to the web interface and to the database will be secure):
    +
    + Spelling + “conneection” → connection. +
    + +

    US/UK check: the script flagged the center/centre pair, but + every occurrence is inside the product name “Centreon”. No genuine UK spelling is + present; US spelling is respected throughout. No other typos found.

    +
    + +
    +

    4 · Style & terminology

    + +
    Here is the basic command that installs the central with the default settings :
    +
    + Style & terminology + Two issues in one line.
    + (a) Terminology: “the central” → the central server. + The glossary entry is Central Server / Serveur central; “the central” + is internal shorthand. The page uses the full term correctly in the title, the + intro and the Options section, so this is an inconsistency within the page.
    + (b) Punctuation: remove the space before the colon + (“settings :” → “settings:”). This is French typographic spacing left in English + text; no other colon on the page is spaced this way. +
    + +
    … in your tmp folder, named unattended(date).log.
    +
    + Style & terminology + Two inconsistencies with the commands directly above.
    + (a) tmp → /tmp. Every command on the + page writes to /tmp/…; bolded tmp without the slash + reads as a relative folder.
    + (b) unattended(date).log does not match what the + command produces. The tee pattern generates + unattended-MM-DD-YYYY-HHMMSS.log. Write it as + unattended-<date>.log and drop the parentheses, which look like + literal characters in a filename. +
    + +
    <TabItem value="RHEL 9" label="RHEL 9"> … <TabItem value="Alma / Oracle Linux 9" label="Alma / Oracle Linux 9">
    +
    + Style & terminology + The OS tabs use groupId="os" — correct — but the tab + values do not match those used elsewhere in the same group. + using-packages.md uses + "Alma / RHEL / Oracle Linux 9", "Alma / RHEL / Oracle Linux 10" + and "Debian 13". Because Docusaurus syncs tabs by + value within a groupId, a reader who picks + “Alma / RHEL / Oracle Linux 9” on the packages page lands on this page with an + unmatched selection and gets the first tab instead. Align the values with + using-packages.md (RHEL is split out here only because of the + subscription-manager commands — if the split is intentional, use a + distinct groupId rather than the shared os one). +
    + +
    Once you are logged in, follow the steps described here.
    +
    + Style & terminology + Replace the bare “here” with descriptive link text: “follow the + initialization of the monitoring steps.” Every other cross-link in + this folder names its target (“web installation”, + “quick start guide”); “here” is unusable for screen readers and for + readers scanning link text. +
    + +
    4. Configure Centreon: log in … / 5. Start using Centreon: follow our quick start guide …
    +
    + Style & terminology + Steps 4 and 5 carry a “Label: instruction” prefix; steps 2 and 3 are plain + imperatives. Either give all five steps a label or none. (Step 1, “Update your + system:”, is a lead-in to a code block, which is a different pattern and can + stay.) +
    + +
    -p <admin_password> … http://[SERVER_IP]/centreon where [SERVER_IP] …
    +
    + Style & terminology + Placeholder syntax is mixed on one page: angle brackets in the commands + (<admin_password>) and square brackets in the URL + ([SERVER_IP]). Pick one — angle brackets are the more common + convention in this folder — and note that square brackets in prose read as + Markdown link syntax. +
    + +

    Glossary conformity (common.csv + + infra-monitoring.csv): all other terms conform — “central server”, + “monitoring”, “web interface”, “database” are used consistently, and + product names (Centreon, MariaDB, MySQL, TLS) are capitalized correctly throughout.

    +
    + + + +
    +

    Summary

    +
    + + + + + + + + + + + + + + + + + + + + + + + + + +
    CriterionIssuesTakeaway
    Plain language5The new intro trades a fact (“including the web installation”) for a + value claim; several instructions are wrapped in filler frames + (“Here is the basic command that…”, “If you don't specify any options…”).
    Idiomaticity4Two French calques (“start your monitoring”, “the real IP address”), + plus “get help on the script” and a reader-subject “you will get” where + the house voice is tool-subject.
    Spelling1“conneection” → “connection”. The script's center/centre flag is + a false positive on “Centreon”; US spelling is otherwise respected.
    Style & terminology6“the central” instead of “central server”, a French space before a colon, + a log filename that doesn't match the command, tab + values that break groupId="os" sync with + using-packages.md, a bare “here” link, and mixed + <>/[] placeholders.
    Links & anchors2One link relies on unvalidated URL-relative resolution instead of the + .md form; the unattended.sh download URL + returns 404 and needs confirming with the delivery team.
    Total18Sum of all issues flagged across the five criteria
    +

    Plus 4 blockers listed in section 0 and not counted above: the + empty “Options” section, the undocumented -s flag that contradicts the + stated defaults, the “when to use this” sentence hidden in an HTML comment, and the + dropped RedHat-credentials note.

    +
    +
    +
    + + diff --git a/_review/upgrade-debian-in-place.review.html b/_review/upgrade-debian-in-place.review.html new file mode 100644 index 000000000000..6569ad2cc0df --- /dev/null +++ b/_review/upgrade-debian-in-place.review.html @@ -0,0 +1,183 @@ + + + + + +Editorial review + + + +
    +

    Editorial review

    +

    versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md · 2026-10-06

    + + + +
    +

    1 · Plain language

    +
    Snapshots let you quickly roll back a whole server, but they are not a substitute for backups: they usually share the same storage as the VM, capture databases in a crash-consistent state only, and cannot restore a single database or file. (L49)
    +
    Plain language41 words. Suggested: "Snapshots let you roll back a whole server quickly, but they do not replace backups. They usually share the VM's storage, capture databases only in a crash-consistent state, and cannot restore a single database or file."
    + +
    apt-get update # no error (a broken repository blocks the major) … cat /etc/debian_version # 12.latest (L70, L134)
    +
    Plain languageJargon/shorthand: "the major", "12.latest". Suggested: "# no error (a broken repository blocks the upgrade to Debian 13)" and "# latest 12.x version".
    + +
    The commands edit the existing files (deb822 /etc/apt/sources.list.d/*.sources, written by recent Debian 12 installs, or one-line *.list); never add a new file next to an old one (25.10 and 26.10 would mix). (L206–207)
    +
    Plain languageDense parentheticals. Suggested: "The commands edit your existing repository files (either deb822 *.sources files or one-line *.list files). Do not add a new file next to an old one: the 25.10 and 26.10 repositories would mix."
    + +
    This is because the 26.10 packages restart the services (and cron if it was upgraded) while the schema is still 25.10 until the wizard; Gorgone then logs … every 15 s. (L323–325)
    +
    Plain languageLong, elliptical ("until the wizard"). Suggested: "The 26.10 packages restart the services (and cron, if it was upgraded), but the database schema stays at 25.10 until you run the update wizard in step 8. Until then, Gorgone logs … every 15 seconds."
    + +
    On the central with a local engine, on a remote database, on MAP or MBI. (L255)
    +
    Plain languageVerbless fragment; "local engine" is unclear. Suggested: "Run this on every server that hosts a database: the central server (if the database is local), the remote database server, and the MAP or MBI server."
    + +
    Known issues table: "1.4: install/enable cron", "dpkg --configure -a, all ii", "Pollers on latest 25.10 first; upgrade them soon" (L586–606)
    +
    Plain languageNote-style shorthand throughout the table. Write full imperative sentences, e.g. "Install and enable cron (see step 1).", "Run dpkg --configure -a, then check that all packages show ii."
    +
    + +
    +

    2 · Idiomaticity

    +
    It is the only fast rollback. (L47)
    +
    IdiomaticitySuggested: "It is the only way to roll back quickly."
    + +
    You can do the servers in any order, central or database server first. (L143)
    +
    IdiomaticitySuggested: "You can update the servers in any order (central server or database server first)."
    + +
    On the reporting server, work outside an ETL run. (L529)
    +
    IdiomaticitySuggested: "On the reporting server, make sure no ETL run is in progress: check with …"
    +
    + +
    +

    3 · Spelling

    +
    I your database is on a separate server… (L364)
    +
    Spelling"I" → "If".
    + +
    ## Step 8: Finalize the upgrade on he central server (L380)
    +
    Spelling"he" → "the".
    + +
    centreontrapd is inactive, wth exit 0/SUCCESS (L473)
    +
    Spelling"wth" → "with".
    +

    US/UK: the script's "centre" hit is a false positive (substring of "Centreon"); US spelling is used throughout.

    +
    + +
    +

    4 · Style & terminology

    +
    "steps 5.1, 5.2 and 5.3", "step 5.4", "7.1 to 7.4", "4b", "7.5", "section 11", "step 1.2", "**5.2 Centreon**" (L163–164, 229, 334, 487, 494, 586–605)
    +
    StyleSub-step numbers are referenced everywhere, but the headings are not numbered (Step 5 has "On your Debian OS / On Centreon / On the database server / Check and simulate"). "4b" and "7.5" don't exist at all, and "**5.2 Centreon**" is a leftover label. Either number the H3 headings (5.1–5.4, 7.1–7.5) or replace every reference with a heading name + link.
    + +
    [MAP], [MySQL], [local DB] tags in code comments and tables (L56, L141, L285, L329, L439…)
    +
    StyleThese tags are only defined in the commented-out "Find your case" section, so readers never see the legend. Add a short legend near the top, or use tabs/admonitions instead.
    + +
    "as it did on the database servers we tested" (L378), "On both test platforms" (L390), "seen 0.8.36 → 0.8.40" (L141), Known issues rows "MBI doc | Java 17 required…" and "Official doc | No Debian 12 → 13 path… | This document" (L596–597)
    +
    StyleInternal test notes and meta-comments about other docs. Remove them from published content (and fix the MBI doc itself instead).
    + +
    "Apache merge (step 2)" (L357), "Steps 2, 7 (custom Apache) … Apache merge" (L599), "Steps 2, 8 (wizard)" (L591)
    +
    StyleThe Apache merge procedure and the step 2 wizard notes are inside an HTML comment (L92–125), so these references point to invisible content. Restore the procedure or drop the references.
    + +
    "Restart all" (L421) vs "Restart" (L497); "**Update all**" (L390) vs "_Update all_" (L590); "(See step 1.4.)" (L474)
    +
    StyleUse the exact UI label consistently, always in bold; lowercase "see" mid-sentence.
    + +
    Indentation of L81–83 (paragraph at 3/2 spaces under list item 4) and the code block after "2. After the reboot…" (L453, not indented); mix of "*" and "-" list markers.
    +
    StyleMis-indented continuation content breaks the numbered lists when rendered. Indent continuation blocks by 4 spaces and pick one bullet marker.
    + +
    "the central" / "central server" / "central"; "remote database" / "remote DB" / "database server"; "Centreon Monitoring Agent" / "Monitoring Agent"
    +
    TerminologyPick one term for each and use it everywhere ("central server", "database server", "Centreon Monitoring Agent" per the infra-monitoring glossary).
    +
    + + + +
    +

    Summary

    +
    + + + + + + + + + + +
    CriterionIssuesTakeaway
    Plain language6Long sentences, shorthand and jargon ("the major", "until the wizard"), terse known-issues table
    Idiomaticity3A few literal phrasings ("the only fast rollback", "do the servers")
    Spelling3Typos "I your", "he central", "wth"; US spelling OK
    Style & terminology7Phantom sub-step numbers, undefined tags, internal test notes, references to commented-out content
    Links & anchors2One broken anchor, 24.10 link points to 25.10 docs
    Total21Sum of all issues flagged
    +
    +
    +
    + + diff --git a/_translation/version-26.10/administration/self-signed-certificate.md b/_translation/version-26.10/administration/self-signed-certificate.md new file mode 100644 index 000000000000..926a861cdb8d --- /dev/null +++ b/_translation/version-26.10/administration/self-signed-certificate.md @@ -0,0 +1,419 @@ +--- +id: self-signed-certificate +title: Créer un certificat auto-signé +description: "Créer un certificat auto-signé avec OpenSSL" +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +> Les certificats auto-signés sont réservés aux tests. Vous NE DEVEZ PAS les utiliser en production. + +## Fichiers nécessaires pour établir des connexions TLS avec des certificats auto-signés + +Cette procédure vous permet de créer les fichiers suivants : + +| Fichier | Où le stocker | Rôle | +|--------------|-----------------------------------|-------------------------------------------------------------------------| +| server-key.pem | Sur le serveur à sécuriser (central/distant, base de données...) | Clé privée de **server.pem** : reste secrète sur le serveur sécurisé. Sert à prouver l'identité du serveur. | +| server.pem | Sur le serveur à sécuriser (central/distant, base de données...) | Certificat signé, envoyé automatiquement à tout client qui tente de se connecter au serveur sécurisé. | +| rootCA.pem | Sur le client (navigateur, système d'exploitation...) | Certificat auto-signé de l'autorité de certification racine. Ce fichier public sert à valider le certificat **server.pem** reçu par le client. Vous devrez copier **rootCA.pem** sur toutes les machines qui communiqueront avec la machine sécurisée (celle qui a envoyé **server.pem**). | +| rootCA.key | Uniquement sur la machine qui génère l'autorité de certification, dans un dossier temporaire | Ce fichier ne joue aucun rôle en production. Il sert uniquement à signer **rootCA.pem** lors de sa création. | + +## Ce que fait cette procédure + +La procédure crée, dans des dossiers temporaires, les fichiers nécessaires pour établir une connexion TLS. Lorsque vous configurerez HTTPS sur un serveur, vous devrez déployer ces fichiers au bon emplacement. Par exemple, **/etc/pki/centreon-tls** est l'emplacement par défaut des certificats sous EL. Sous Debian, le chemin par défaut est **/etc/ssl/certs**. + +Vous pouvez suivre cette procédure sur une plateforme Centreon dont la base de données est locale ou distante. + +* Si votre base de données est locale, exécutez les commandes des deux onglets sur votre serveur Centreon. +* Si votre base de données est distante, suivez la procédure deux fois : + * Sur votre serveur Centreon, créez une autorité de certification (étapes 1 à 3), puis exécutez les commandes des onglets **Sur le serveur central/distant**. + * Sur le serveur de base de données, créez une autre autorité de certification, puis exécutez les commandes des onglets **Sur le serveur de base de données**. + + Vous obtenez alors deux fichiers **rootCA.pem** différents. Copiez le fichier **rootCA.pem** du serveur de base de données sur les machines qui se connectent à la base de données (par exemple, votre serveur Centreon). Copiez le fichier **rootCA.pem** de votre serveur Centreon sur les machines qui se connectent à celui-ci. + + + +## Étape 1 : Créer les répertoires de sortie + +Créez des dossiers pour organiser les fichiers : un pour les fichiers propres à l'autorité de certification, un pour les fichiers destinés au service web ou au service de base de données. + +Pour l'autorité de certification : + +```shell +sudo mkdir -p /out/CA +``` + +Pour le serveur central/distant, ou pour la base de données : + + + + +```shell +sudo mkdir -p /out/web +``` + + + + +```shell +sudo mkdir -p /out/db +``` + + + + +## Étape 2 : Générer la clé privée de l'autorité de certification racine (RSA 4096 bits) + +Il s'agit de la clé secrète de votre autorité de certification. La commande **chmod 400** limite l'accès au fichier : seul son propriétaire peut le lire (et personne ne peut y écrire). L'exposition de la clé est ainsi réduite au minimum. + +```shell +sudo openssl genrsa -out /out/CA/rootCA.key 4096 +sudo chmod 400 /out/CA/rootCA.key +``` + +## Étape 3 : Générer le certificat auto-signé de l'autorité de certification racine (10 ans) + +Créez maintenant le certificat de l'autorité de certification. Ce document public identifie votre autorité de certification (nom, organisation, etc.). Vous le distribuerez ensuite à tous les clients et serveurs qui doivent faire confiance aux certificats qu'elle signe. + +Ce certificat est « auto-signé », car aucune autorité ne se trouve au-dessus de lui : l'autorité de certification se porte garante d'elle-même. C'est un fonctionnement normal pour une autorité de certification racine. + +* `-x509` indique à OpenSSL de produire directement un certificat (et non une demande de signature). +* `-days 3650` fixe l'expiration à environ 10 ans. Cette durée est habituelle pour une autorité de certification racine, qui n'a pas vocation à être renouvelée souvent. +* `-subj` définit les champs d'identité directement dans la ligne de commande : CN (Common Name) vaut « Test Dev CA », O (Organization) vaut « YourOrganization » et OU (Organizational Unit) vaut « R&D ». Remplacez ces valeurs par celles de votre organisation. + +```shell +sudo openssl req -x509 -new -nodes -key /out/CA/rootCA.key \ + -sha256 -days 3650 \ + -subj "/CN=Test Dev CA/O=YourOrganization/OU=R&D" \ + -out /out/CA/rootCA.pem +``` + +## Étape 4 : Générer la clé privée du serveur final (RSA 2048 bits) + +Il s'agit de la clé privée du serveur lui-même (le serveur central/distant ou la base de données). Elle est distincte de la clé de l'autorité de certification : le serveur ne doit jamais partager une clé avec l'autorité de certification. + + + + +```shell +sudo openssl genrsa -out /out/web/server-key.pem 2048 +``` + + + + +```shell +sudo openssl genrsa -out /out/db/server-key.pem 2048 +``` + + + + +## Étape 5 : Créer le fichier de configuration des extensions OpenSSL pour les SAN + +Les navigateurs et clients récents exigent qu'un certificat liste tous les noms d'hôte et adresses IP pour lesquels il est valide : c'est la liste SAN (Subject Alternative Name). Un CN seul ne suffit plus pour être considéré comme fiable. Cette étape crée un petit fichier de configuration qui définit : + +* `basicConstraints = CA:FALSE` : ce certificat n'est pas autorisé à signer d'autres certificats (seule l'autorité de certification racine le peut). +* `keyUsage / extendedKeyUsage` : limite le certificat à son usage prévu, c'est-à-dire l'authentification d'un serveur TLS. +* `subjectAltName` : la liste des noms et adresses IP pour lesquels le certificat doit être valide. Ici : web, localhost, db et l'adresse IP 127.0.0.1. Modifiez cette liste pour qu'elle corresponde aux noms d'hôte réels par lesquels votre serveur sera joint. + +```shell +sudo tee /out/cert.ext > /dev/null < + + +```shell +sudo openssl req -new -key /out/web/server-key.pem -out /out/web/server.csr \ + -subj "/CN=web/O=Centreon" +``` + + + + +```shell +sudo openssl req -new -key /out/db/server-key.pem -out /out/db/server.csr \ + -subj "/CN=db/O=Centreon" +``` + + +     + +## Étape 7 : Signer le certificat final avec l'autorité de certification racine (validité de 397 jours) + +C'est cette étape qui produit le certificat serveur utilisable : l'autorité de certification (son certificat et sa clé privée, créés aux étapes 2 et 3) signe la CSR de l'étape 6, en appliquant les extensions et les SAN définis à l'étape 5. + +* `-days 397` : 397 jours est la durée de vie maximale actuellement acceptée par les principaux navigateurs (Apple, Google, Mozilla) pour les certificats de serveur TLS. Au-delà, les clients risquent de rejeter le certificat. +* `-CAcreateserial` : crée, lors de la première exécution, un fichier de suivi des numéros de série (rootCA.srl), puis l'incrémente à chaque nouvelle signature. Chaque certificat émis par cette autorité de certification reçoit ainsi un numéro de série unique. + + + + + + +```shell +sudo openssl x509 -req -in /out/web/server.csr \ + -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ + -CAserial /out/CA/rootCA.srl -CAcreateserial \ + -out /out/web/server.pem -days 397 -sha256 \ + -extfile /out/cert.ext -extensions v3_req +``` + + + + +```shell +sudo openssl x509 -req -in /out/db/server.csr \ + -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ + -CAserial /out/CA/rootCA.srl -CAcreateserial \ + -out /out/db/server.pem -days 397 -sha256 \ + -extfile /out/cert.ext -extensions v3_req +``` + + + + +## Étape 8 : Définir les permissions + +Les permissions suivent ici le principe du moindre privilège : + +* `0644` (lecture pour tous, écriture pour le propriétaire uniquement) pour les certificats publics : ils ne contiennent aucun secret. +* `0640` (lecture pour le propriétaire et le groupe, aucun accès pour les autres) pour la clé privée du serveur. Cette clé est sensible, mais un service exécuté sous un groupe spécifique aura probablement besoin de la lire. + +Pour l'autorité de certification racine : + +```shell +sudo chmod 0644 /out/CA/rootCA.pem +``` + +Pour le serveur central/distant : + +```shell +sudo chmod 0644 /out/web/server.pem +sudo chmod 0640 /out/web/server-key.pem +``` + +Pour la base de données : + +```shell +sudo chmod 0644 /out/db/server.pem +sudo chmod 0640 /out/db/server-key.pem +``` + +Les 3 fichiers nécessaires se trouvent maintenant dans votre dossier **/out**. Vous pouvez les copier aux emplacements appropriés sur vos serveurs (et les renommer si besoin). + + + + + + diff --git a/centreon-os-support-vs-26-10.md b/centreon-os-support-vs-26-10.md new file mode 100644 index 000000000000..363ecd08fd57 --- /dev/null +++ b/centreon-os-support-vs-26-10.md @@ -0,0 +1,62 @@ +# Centreon — Versions et systèmes d'exploitation supportés + +> Document généré à partir de la documentation officielle Centreon (dépôt `centreon-documentation` +> pour les versions 24.10 à 26.10, et des sites d'archives pour les versions antérieures). +> Date de génération : 2026-07-03. + +## Cycle de vie des versions + +Source : `versioned_docs/version-26.10/releases/lifecycle.md` + +| Version Centreon | Sortie | Fin de support | État | +|-------------------|---------|-----------------|----------------------| +| 26.10 | 10/2026 | 04/2029 | Supportée | +| 25.10 | 10/2025 | 04/2027 | Supportée | +| 24.10 | 10/2024 | 10/2027 | Supportée | +| 24.04 | 04/2024 | 04/2026 | Plus supportée | +| 23.10 | 10/2023 | 10/2025 | Plus supportée | +| 23.04 | 04/2023 | 04/2025 | Plus supportée | +| 22.10 | 10/2022 | 10/2024 | Plus supportée | +| 22.04 | 05/2022 | 05/2024 | Plus supportée | +| 21.10 | 11/2021 | 11/2023 | Plus supportée | +| 21.04 | 04/2021 | 10/2022 | Plus supportée | +| 20.10 | 10/2020 | 05/2022 | Plus supportée | +| 20.04 | 04/2020 | 10/2021 | Plus supportée | +| 19.10 | 10/2019 | 04/2021 | Plus supportée | +| 19.04 | 04/2019 | 10/2020 | Plus supportée | +| 18.10 | 10/2018 | 04/2020 | Plus supportée | + +## Systèmes d'exploitation supportés par version + +Rappel — OS supportés par la version actuelle **Centreon 26.10** : RHEL/Oracle Linux/Alma Linux 9, RHEL/Oracle Linux/Alma Linux 10, Debian 13 (trixie). + +| Version Centreon | OS supportés à l'époque | Parmi eux, toujours supportés en 26.10 | +|-------------------|--------------------------|------------------------------------------| +| **26.10** | RHEL/Oracle Linux/Alma Linux 9 & 10 (RPM, sources) • Debian 13 "trixie" (DEB) | RHEL/Oracle/Alma Linux 9, RHEL/Oracle/Alma Linux 10, Debian 13 (version actuelle) | +| **25.10** | RHEL/Oracle Linux 8 (RPM, sources) • Alma Linux 8 (RPM, VM, sources) • RHEL/Oracle/Alma Linux 9 (RPM, sources) • Debian 12 "bookworm" (DEB) | RHEL/Oracle/Alma Linux 9 | +| **24.10** | RHEL/Oracle Linux 8 (RPM, sources) • Alma Linux 8 (RPM, VM, sources) • RHEL/Oracle/Alma Linux 9 (RPM, sources) • Debian 12 "bookworm" (DEB) | RHEL/Oracle/Alma Linux 9 | +| **24.04** | RHEL/Oracle Linux 8 (RPM, sources) • Alma Linux 8 (RPM, VM, sources) • RHEL/Oracle/Alma Linux 9 (RPM, sources) • Debian 11 "bullseye" (DEB) • Debian 12 "bookworm" (DEB) | RHEL/Oracle/Alma Linux 9 | +| **23.10** | RHEL/Oracle Linux 8 (RPM, sources) • AlmaLinux 8 (RPM, VM, sources) • RHEL/Oracle/AlmaLinux 9 (RPM, sources) • Debian 11 (DEB) | RHEL/Oracle/AlmaLinux 9 | +| **23.04** | RHEL/Oracle Linux 8 (RPM, sources) • AlmaLinux 8 (RPM, VM, sources) • RHEL/Oracle/AlmaLinux 9 (RPM, sources) • Debian 11 (DEB) | RHEL/Oracle/AlmaLinux 9 | +| **22.10** | CentOS 7 (RPM, VM, sources) • RHEL/Oracle Linux 7 (RPM, sources) • RHEL/Oracle Linux 8 (RPM, sources) • AlmaLinux 8 (RPM, VM, sources) • Debian 11 (DEB) — *CentOS/RHEL 7 déconseillés* | Aucun | +| **22.04** | Non trouvé (page d'archive inaccessible, erreur HTTP 403) | N/A | +| **21.10** | CentOS 7 (ISO, RPM, VM, sources) • RHEL/Oracle Linux 7 (RPM, sources) • RHEL/Oracle Linux 8 (RPM, sources) | Aucun | +| **21.04** | CentOS 7 (ISO, RPM, VM, sources) • RHEL/Oracle Linux 7 ou 8 (RPM, sources) | Aucun | +| **20.10** | CentOS 7 (RPM) • RHEL 7/8 (RPM) • Oracle Linux 7/8 (RPM) | Aucun | +| **20.04** | CentOS 7 (ISO) • RHEL 7 (RPM) | Aucun | +| **19.10** | Non trouvé | N/A | +| **19.04** | Non trouvé | N/A | +| **18.10** | Non trouvé | N/A | + +### Notes + +- Sur toutes les versions où l'information est disponible : seules les architectures **64 bits (x86_64)** sont supportées. +- Les utilisateurs Open Source sans contrat de support peuvent utiliser une autre distribution GNU/Linux en installant depuis les sources, mais les modules IT Edition / Business Edition ne fonctionnent pas sur les distributions non supportées. +- Pour **22.04**, la page d'archive (`archives-docs.centreon.com/22.04/`) a renvoyé une erreur 403 lors de la consultation — non vérifiable. +- Pour **18.10 / 19.04 / 19.10**, la plateforme d'archives (`docs-older.centreon.com`) est dépréciée et ne fournit pas de page dédiée par version pour ces informations — volontairement laissées vides plutôt que devinées. +- À partir de la version 22.10 incluse et en amont, plus aucun OS de l'époque n'est encore supporté en 26.10 (CentOS 7 et RHEL/Oracle/Alma Linux 7-8 sont tous en fin de vie côté Centreon). Seule la lignée « Enterprise Linux 9 » (RHEL/Oracle Linux/AlmaLinux 9), apparue à partir de 22.10, perdure jusqu'en 26.10. + +### Sources + +- Dépôt local (versions 24.10 à 26.10) : `versioned_docs/version-{24.10,25.10,26.10}/installation/compatibility.md` et `versioned_docs/version-26.10/releases/lifecycle.md` +- Archives (versions 20.04 à 24.04) : `https://archives-docs.centreon.com/{version}/docs/installation/compatibility` (ou `.../installation/prerequisites` pour 20.x et 21.x) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md.bak b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md.bak new file mode 100644 index 000000000000..fccd85b2e43c --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md.bak @@ -0,0 +1,285 @@ +--- +id: migrate-from-el-to-el +title: Migrer depuis un OS de type EL vers un autre OS de type EL (depuis un Centreon 18.10 ou plus récent) +description: "Migrer une plateforme Centreon entre deux OS de type EL" +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +## Prérequis + +Cette procédure ne s'applique que dans les conditions suivantes : + +- Vous souhaitez migrer d'un OS de type EL 64-bits vers un autre OS de type EL 64-bits supporté. Par exemple, vous souhaitez migrer d'un CentOS 7 à un Alma 9. +- Votre version de Centreon est 18.10 ou plus récente. + +Tous les serveurs de votre architecture (serveur central, serveurs distants et collecteurs) doivent avoir la même version majeure de Centreon. Il est également recommandé d'avoir la même version mineure. + +> Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. + +Avant toute chose, effectuez une sauvegarde de l’ensemble des serveurs de votre plateforme : + +- Serveur Centreon central, +- Serveur de gestion de base de données. + +Si vous utilisez un fournisseur Open Ticket avec des configurations personnalisées, [sauvegardez-les avant de mettre à jour Centreon](../alerts-notifications/ticketing-install.md#sauvegarder-votre-configuration-personnalisée-de-fournisseur-openticket). + +## Migrer une plateforme + +### Étape 1 : Installer le nouveau serveur central + +1. Installez votre nouvel OS: voir la liste des [OS supportés](../installation/compatibility.md#système-dexploitation). + +2. Installez un nouveau serveur central Centreon à partir des [paquets](../installation/installation-of-a-central-server/using-packages.md) + jusqu'à terminer le processus d'installation en vous connectant à l'interface web. + + > Pendant le processus d'installation web, utilisez le même mot de passe pour l'utilisateur **centreon** que sur l'ancienne plateforme. + +3. Réalisez les mises à jour logicielle et système : + + + + +```shell +dnf update +``` + + + + +### Étape 2 : Synchroniser les données + +1. Connectez-vous à votre ancien serveur Centreon. + +2. Générez une paire de clés ssh pour **root** : + + ```shell + ssh-keygen -t rsa + ``` + + Par défaut, la paire de clés générée sera **/root/.ssh/id_rsa.pub** et **/root/.ssh/id_rsa**. + +3. Copiez la clé publique de **root** (**/root/.ssh/id_rsa.pub**) dans le fichier **/root/.ssh/authorized_keys** du nouveau serveur. Si vous n'utilisez pas le compte **root** pour la synchronisation, assurez-vous que votre utilisateur dispose de droits d'écriture sur le dossier cible. + +4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : + + ```shell + rsync -avz /etc/centreon root@\:/etc + rsync -avz /etc/centreon-broker root@\:/etc + rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine + rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib + rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img + ``` + + Si vous avez personnalisé le nom de votre fichier de clé privée, utilisez le format suivant (remplacez **id_rsa_custom** par le nom de votre fichier, et `` par les commandes ci-dessus): + + ```shell + rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" + ``` + + > Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. + +### Étape 3 : Récupérer les bases de données + +>Si vous utilisez une base de données distante, ignorez cette étape et passez directement à l'[étape 4](#étape-4--synchroniser-les-plugins). + +1. Sur l'ancien serveur, faitez un dump des bases de données : + + ```shell + mysqldump -u root -p centreon > /tmp/centreon.sql + mysqldump -u root -p centreon_storage > /tmp/centreon_storage.sql + ``` + +2. Sur l'ancien serveur, arrêtez MariaDB : + + ```shell + systemctl stop mariadb + ``` + +3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): + + ```shell + rsync -avz /tmp/centreon.sql root@\:/tmp/ + rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ + ``` + +4. Sur le nouveau serveur de base de données, supprimez les bases de + données vierges et recréez-les : + + ```shell + mysql -u root -p + ``` + + ```SQL + DROP DATABASE centreon; + DROP DATABASE centreon_storage; + CREATE DATABASE centreon; + CREATE DATABASE centreon_storage; + ``` + +5. Sur le nouveau serveur de bases de données, importez dans la base les dumps précédemment transférés : + + ```shell + mysql -u root centreon -p -p + ``` + + Exemple : si votre utilisateur_admin_bdd est `root`, entrez: + + ```shell + mysql_upgrade -u root -p + ``` + +7. Démarrez le processus **mariadb** sur le nouveau serveur : + + ```shell + systemctl start mariadb + ``` + +> Remplacez **\** par l'adresse IP de votre nouveau serveur +> Centreon. + +### Étape 4 : Synchroniser les plugins + +Si vous n'utilisez que des plugins Centreon, réinstallez-les sur le nouveau serveur: + + + + +```shell +dnf install centreon-plugin-\* +``` + + + + +```shell +dnf install centreon-plugin-\* +``` + + + + +```shell +apt install centreon-plugin-\* +``` + + + + +Si vous utilisez vos propres plugins personnalisés, synchronisez les répertoires qui contiennent ceux-ci, ainsi que toutes éventuelles dépendances. + +Utilisez la commande suivante pour synchroniser les images et autres médias entre votre ancien serveur et le nouveau. + +```shell +rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img/ +``` + +### Étape 5 : Montée de version de la solution Centreon + +1. Sur le nouveau serveur, forcez la montée de version en déplacant le contenu du répertoire + **/var/lib/centreon/installs/install-26.10.x-YYYYMMDD_HHMMSS** dans le + répertoire **/usr/share/centreon/www/install** (**x** est le numéro de version cible pour votre machine migrée): + + ```shell + cd /var/lib/centreon/installs/ + mv install-26.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ + ``` + +2. Si vous utilisez la meme adresse IP ou le même nom DNS entre l'ancien serveur + web Centreon et le nouveau, videz complètement le cache de votre navigateur pour + éviter des problemes de scripts JS. + +3. Connectez-vous à l'URL `http:///centreon` et suivez les étapes + de la mise à jour. + +4. Si vous avez modifié le mot de passe de l'utilisateur **centreon** lors de + l'installation de votre nouveau serveur Centreon pour accéder aux bases de + données, il sera nécessaire de réaliser les actions suivantes sur le nouveau + serveur Centreon : + + 1. Modifiez le fichier **/etc/centreon/centreon.conf.php**, + 2. Modifiez le fichier **/etc/centreon/conf.pm**, + 3. Éditez la configuration du Centreon Broker central, via l'interface web + Centreon et modifiez le mot de passe pour l'output **unfied-sql**, + 4. Modifiez le fichier **/etc/centreon/config.d/10-database.yaml**. + +5. Si l'adresse IP de votre serveur Centreon a changé : + - Éditez la configuration de l'ensemble des modules Broker de vos collecteurs et modifiez l'adresse IP de + connexion au serveur Centreon central (output IPv4). Consultez le chapitre + [Configuration + avancée](../monitoring/monitoring-servers/advanced-configuration.md#tcp-outputs) + pour plus d'information. + - L'empreinte de votre plateforme a également changé : [contactez Centreon](mailto:support@centreon.com) pour obtenir une nouvelle licence. + +6. Les informations de connexion de l'utilisateur **centreon-gorgone** nouvellement créé doivent être les mêmes que celles de l'utilisateur **centreon-gorgone** sur l'ancien serveur. Éditez le fichier `etc/centreon-gorgone/config.d/31-centreon-api.yaml` et entrez les information de connexion de l'ancien utilisateur. Exemple : + + ```shell + gorgone: + tpapi: + - name: centreonv2 + base_url: "http://127.0.0.1/centreon/api/latest/" + username: "@GORGONE_USER@" + password: "@GORGONE_PASSWORD@" + - name: clapi + username: "@GORGONE_USER@" + password: "@GORGONE_PASSWORD@" + ``` + +7. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) de tous vos serveurs de supervision (y compris celle du central). + +8. Redémarrez les processus suivants : + + ```shell + systemctl restart cbd centengine + systemctl restart gorgoned + systemctl start snmptrapd centreontrapd + systemctl start snmpd + ``` + +9. Si vous supervisiez votre ancienne machine Centreon, et que vous avez changé le nom d'utilisateur/mot de passe de la base pendant la migration, mettez à jour la configuration des ressources concernées (hôte, services dépendant de cet hôte). + +10. Allez à la page **Configuration > Connecteurs > Connecteurs de supervision**, puis [mettez à jour tous les connecteurs de supervision](../monitoring/pluginpacks.md#mettre-à-jour-un-ou-plusieurs-packs). + +### Étape 6 (anciennes versions uniquement): Migrer vers Gorgone + +Si vous migrez depuis un Centreon 18.10, 19.04 ou 19.10, vous devez également [migrer de Centcore à Gorgone](../developer/developer-gorgone-migrate-from-centcore.md). + +### Étape 7: Mettre à jour les modules + +Pour mettre à jour les modules, allez à la page **Administration > Extensions > Gestionnaire** et cliquez sur **Update all**. +Si vous avez un serveur MAP ou MBI, suivez les procédures de migration correspondantes : + +- Procédure de migration pour [MAP](../graph-views/map-web-migrate.md), +- Procédure de migration pour [MBI](../reporting/migrate.md). + +### Étape 8: Migrer vos autres serveurs (architecture distribuée) + +#### Migrer un serveur distant + +Pour migrer un serveur distant : + +1. Suivez la même procédure que pour un serveur central. +2. [Rattachez le nouveau serveur distant](../monitoring/monitoring-servers/add-a-remote-server-to-configuration.md) à votre serveur central. + +#### Migrer un collecteur + +Pour migrer un collecteur : + +1. [Installez un nouveau collecteur](../installation/installation-of-a-poller/using-packages.md). +2. Synchronisez les plugins, comme décrit à [l'étape 4 de la procédure de migration pour un serveur central](#étape-4--synchroniser-les-plugins). +3. Sur le serveur central, allez à la page **Configuration > Collecteurs**. Sélectionnez le collecteur migré et mettez à jour son adresse IP (si celle-ci a changé). +4. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). +5. Si votre collecteur rencontre des problèmes suite à la migration (impossible de déployer la configuration, d'effectuer des actions de supervision...), mettez à jour l'empreinte du collecteur comme décrit dans [cet article de base de connaissances](https://thewatch.centreon.com/troubleshooting-41/poller-does-not-work-after-migration-or-reinstallation-fingerprint-changed-for-target-1177). diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/installation.md.bak b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/installation.md.bak new file mode 100644 index 000000000000..27d617130fe2 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/installation.md.bak @@ -0,0 +1,1473 @@ +--- +id: installation +title: Installer MBI +description: "Installer et configurer le serveur de reporting et l'interface de Centreon MBI" +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; +import DatabaseRepository from '../installation/_database-repository.mdx'; + +> Cette page s'adresse aux administrateurs qui vont installer et configurer Centreon MBI. + +Cette page présente l'architecture logicielle de l'extension **Centreon MBI** et explique comment l'installer. Quatre grandes étapes sont nécessaires : + +1. [Vérifiez les prérequis système](#étape-1--vérifiez-les-prérequis-système). +2. [Installez l'interface Centreon MBI dans l'application Centreon](#étape-2--installez-linterface-centreon-mbi-dans-lapplication-centreon). +3. [Installez le serveur de reporting (Centreon MBI Reporting Server)](#étape-3--installez-le-serveur-de-reporting). +4. [Configurez l'ETL dans l'interface de Centreon](#étape-4--configurez-letl-dans-linterface-de-centreon). +5. [Construisez la base de données MBI](#étape-5--construire-la-base-de-données-mbi). + +Une fois l'installation effectuée, vous pouvez [superviser votre serveur MBI avec Centreon](#supervisez-votre-serveur-mbi-avec-centreon). + +## Architecture + +### Un serveur de reporting dédié + +L'architecture et ces prérequis s'appliquent aux environnements de : + +- test +- pré-production +- production. + +Le schéma ci-dessous met en avant les principaux composants de Centreon MBI : + +![image](../assets/reporting/installation/architecture.png) + +*La base de monitoring n'est pas nécessairement sur le même serveur que le serveur Centreon* + +- **ETL** : Processus qui extrait, transforme et charge les données dans la + base de données de reporting. +- **CBIS** : Ordonnanceur qui gère l'exécution et la publication des rapports. +- **Base de données de reporting** : Base de données MariaDB/MySQL qui contient les données de reporting + et certaines données brutes extraites de la base de données de supervision. + +### Tableaux des flux réseau + +Le tableau ci-dessous présente les différents types de flux, par défaut, +entre le serveur BI dédié, le serveur Centreon et les bases de données : + +| **Application** | **Source** | **Destination** | **Port** | **Protocol** | +|-----------------|--------------------------|--------------------------------------|----------|--------------| +| ETL/CBIS | Serveur de reporting | Serveur de bases de données Centreon | 3306 | TCP | +| ETL | Localhost | Localhost | 8085 | TCP | +| SSH | Serveur de reporting | Serveur Centreon | 22 | TCP | +| CBIS | Serveur de reporting | Serveur Centreon | 80 | HTTP* | +| CBIS | Centreon | Serveur de reporting | 1234 | TCP | +| Widgets | Serveur central Centreon | Serveur de reporting | 3306 | TCP | + +\**Uniquement requis pour les rapports Host-Graph-v2 et Hostgroup-Graph-v2 qui utilisent l'API Centreon pour générer des graphiques.* + +### Informations sur les paquets + +L'installation de Centreon MBI est basée sur deux paquets RPM : + +- **Centreon-bi-server :** Installe l'interface MBI intégrée à l'interface de Centreon. Le paquet est installé sur le serveur central Centreon. +- **Centreon-bi-reporting-server** : Contient tous les composants nécessaires à l'exécution + du serveur de reporting (planificateur de rapports, ETL, rapports standard). Il doit être + installé sur un serveur dédié aux processus de reporting. + +L'installation de la base de données doit être faite en même temps. Nous recommandons +fortement d'installer la base MariaDB/MySQL sur le serveur de reporting pour des raisons de +performances & d'isolation. + +## Étape 1 : Vérifiez les prérequis système + +### Serveur central + +#### Prérequis logiciels + +Voir les [prérequis logiciels](../installation/prerequisites.md#caractéristiques-des-serveurs). + + + + +- Centreon Web 25.10 +- Vérifiez que `date.timezone` est correctement configurée dans le fichier + `/etc/php.d/50-centreon.ini` ou `/etc/php.d/20-timezone.ini` (même que celui retourné par la commande + `timedatectl status`) +- Evitez l'utilisation des variables ci-dessous dans le fichier de + configuration MariaDB `/etc/my.cnf`. Elles interrompent l'exécution de longues requêtes et peuvent arrêter les jobs d'ETL ou de génération de rapports : + - wait_timeout + - interactive_timeout + +| Utilisateur | Groupe | +|----------------------|----------------------------| +| centreonBI (nouveau) | apache,centreon,centreonBI | +| apache (existant) | centreonBI | + + + + +- Centreon Web 25.10 +- Vérifiez que `date.timezone` est correctement configurée dans le fichier + `/etc/php.d/50-centreon.ini` ou `/etc/php.d/20-timezone.ini` (même que celui retourné par la commande + `timedatectl status`) +- Evitez l'utilisation des variables ci-dessous dans le fichier de + configuration MariaDB `/etc/my.cnf`. Elles interrompent l'exécution de longues requêtes et peuvent arrêter les jobs d'ETL ou de génération de rapports : + - wait_timeout + - interactive_timeout + +| Utilisateur | Groupe | +|----------------------|----------------------------| +| centreonBI (nouveau) | apache,centreon,centreonBI | +| apache (existant) | centreonBI | + + + + +- Centreon Web 25.10 +- Vérifiez que `date.timezone` est correctement configurée dans le fichier + `/etc/php/8.2/mods-available/centreon.ini` ou `/etc/php/8.2/mods-available/timezone.ini` (même que celui retourné par la commande + `timedatectl status`) +- Evitez l'utilisation des variables ci dessous dans le fichier de + configuration MariaDB `/etc/mysql/mariadb.cnf`. Elles interrompent l'exécution de longues requêtes et peuvent arrêter les jobs d'ETL ou de génération de rapports : + - wait_timeout + - interactive_timeout +- Lors de la création de l'utilisateur CentreonBI, éxecutez la commande suivante : `adduser centreonBI --force-badname` + +#### Utilisateurs et groupes + +| Utilisateur | Groupe | +|----------------------|------------------------------| +| centreonBI (nouveau) | www-data,centreon,centreonBI | +| apache (existant) | centreonBI | + + + + +#### Description des utilisateurs, umask et répertoire personnel + +| Utilisateur | umask | home | +|-------------|-------|------------------| +| centreonBI | 0002 | /home/centreonBI | + +### Serveur de reporting dédié + +#### Couche Matériel + + + + +| Élément | Valeur | +| ----------------------------| --------- | +| CPU | 4 vCPU | +| RAM | 16 Go | + +Votre serveur MBI doit être partitionné de la manière suivante : + +| Groupe de volumes (LVM) | Partition | Description | Taille | +|-| ----------------------------|-------------|----------------------------------------------------------| +| | /boot | images de boot | 1 Go | +| vg_root | / | racine du système | 20 Go | +| vg_root | swap | swap | 4 Go | +| vg_root | /var/log | contient tous les fichiers de log | 10 Go | +| vg_data | /var/lib/mysql | base de données | 233 Go | +| vg_data | /var/backup | répertoire de sauvegarde | 10 Go | +| vg_data | | Espace libre (non alloué) | 5 Go | + + + + +| Élément | Valeur | +| ----------------------------| --------- | +| CPU | 4 vCPU | +| RAM | 16 Go | + +Votre serveur MBI doit être partitionné de la manière suivante : + +| Groupe de volumes (LVM) | Partition | Description | Taille | +|-| ----------------------------|-------------|----------------------------------------------------------| +| | /boot | images de boot | 1 Go | +| vg_root | / | racine du système | 20 Go | +| vg_root | swap | swap | 4 Go | +| vg_root | /var/log | contient tous les fichiers de log | 10 Go | +| vg_data | /var/lib/mysql | base de données | 465 Go | +| vg_data | /var/backup | répertoire de sauvegarde | 10 Go | +| vg_data | | Espace libre (non alloué) | 5 Go | + + + + +| Element | Value | +| ----------------------------| --------- | +| CPU | 4 vCPU | +| RAM | 24 Go | + +Votre serveur MBI doit être partitionné de la manière suivante : + +| Groupe de volumes (LVM) | Partition | Description | Taille | +|-| ----------------------------|-------------|----------------------------------------------------------| +| | /boot | images de boot | 1 Go | +| vg_root | / | racine du système | 20 Go | +| vg_root | swap | swap | 4 Go | +| vg_root | /var/log | contient tous les fichiers de log | 10 Go | +| vg_data | /var/lib/mysql | base de données | 1163 Go | +| vg_data | /var/backup | répertoire de sauvegarde | 10 Go | +| vg_data | | Espace libre (non alloué) | 5 Go | + + + + +| Element | Value | +| ----------------------------| --------- | +| CPU | 8 vCPU | +| RAM | 24 Go | + +Votre serveur MBI doit être partitionné de la manière suivante : + +| Groupe de volumes (LVM) | Partition | Description | Taille | +|-| ----------------------------|-------------|----------------------------------------------------------| +| | /boot | images de boot | 1 Go | +| vg_root | / | racine du système | 20 Go | +| vg_root | swap | swap | 4 Go | +| vg_root | /var/log | contient tous les fichiers de log | 10 Go | +| vg_data | /var/lib/mysql | base de données | 2326 Go | +| vg_data | /var/backup | répertoire de sauvegarde | 10 Go | +| vg_data | | Espace libre (non alloué) | 5 Go | + + + + +| Element | Value | +| ----------------------------| --------- | +| CPU | 12 vCPU | +| RAM | 32 Go | + +Votre serveur MBI doit être partitionné de la manière suivante : + +| Groupe de volumes (LVM) | Partition | Description | Taille | +|-| ----------------------------|-------------|----------------------------------------------------------| +| | /boot | images de boot | 1 Go | +| vg_root | / | racine du système | 20 Go | +| vg_root | swap | swap | 4 Go | +| vg_root | /var/log | contient tous les fichiers de log | 10 Go | +| vg_data | /var/lib/mysql | base de données | 4651 Go | +| vg_data | /var/backup | répertoire de sauvegarde | 10 Go | +| vg_data | | Espace libre (non alloué) | 5 Go | + + + + +| Élément | Valeur | +| ------- | ------- | +| CPU | 16 vCPU | +| RAM | 64 Go | + +Voici comment votre serveur MBI doit être partitionné : + +| Groupe de volumes (LVM) | Partition | Description | Taille | +| ----------------------- | ------------------- | ----------------------------------- | -------- | +| | /boot | images de boot | 2 Go | +| vg_root | / | racine du système | 20 Go | +| vg_root | swap | swap | 8 Go | +| vg_root | /var/log | contient tous les fichiers de log | 10 Go | +| vg_data | /var/lib/mysql | base de données | 8 462 Go | +| vg_data | /var/backup | répertoire de sauvegarde | 10 Go | +| vg_data | | espace libre (non alloué) | 5 Go | + + + + +Pour de grosses volumétries de données, contactez votre commercial Centreon. + + + + +Pour contrôler l'espace libre, utilisez la commande suivante en remplaçant +**vg_data** par le nom du groupe de volumes : + +```shell +vgdisplay vg_data | grep -i free* +``` + +#### Couche interlogiciel et logiciel + +- OS : voir la compatibilité [ici](../installation/compatibility.md#système-dexploitation) +- SGBD : voir la compatibilité [ici](../installation/compatibility.md#sgbd) +- Firewalld : Désactivé ([voir ici](../installation/installation-of-a-central-server/using-packages.md#configurer-ou-désactiver-le-pare-feu)) +- SELinux : Désactivé ([voir ici](../installation/installation-of-a-central-server/using-packages.md#désactiver-selinux)) + +> Assurez-vous que le fuseau horaire du serveur de reporting est le même que celui du serveur central, sinon les publications de rapports échoueront (lien vers le téléchargement manquant). +> Le même fuseau horaire doit être affiché avec la commande `timedatectl`. +> Vous pouvez changer le fuseau horaire avec cette commande : +> +>```shell +>timedatectl set-timezone Europe/Paris +>``` + +Veillez à optimiser MariaDB/MySQL sur votre serveur de reporting. Vous aurez besoin +d'au moins 12GB de mémoire vive afin d'utiliser le +[fichier suivant](../assets/reporting/installation/centreon.cnf). + +> Si vous souhaitez utiliser un répertoire autre que `/var/lib/mysql/`, éditez les variables **datadir** et **tmpdir** du fichier centreon.cnf. + +Assurez-vous que le dossier **tmp** soit créé dans la même partition que **/var/lib/mysql**. + +> Ne définissez pas ces optimisations MariaDB/MySQL sur votre serveur de supervision. + +Si vous utilisez MySQL : + +1. Effectuez l'action suivante : + + + + +Dans le fichier `/etc/my.cnf.d/mysql-server.cnf`, ajoutez : + +```shell +log_bin_trust_function_creators=1 +``` + + + + +Dans le fichier `/etc/my.cnf.d/mysql-server.cnf`, ajoutez : + +```shell +log_bin_trust_function_creators=1 +``` + + + + +Dans le fichier `/etc/mysql/mysql.cnf`, ajoutez: + +```shell +[mysqld] +log_bin_trust_function_creators=1 +``` + + + + +2. Redémarrez MySQL. + +3. Vérifiez que la base de données que la variable suivante est appliquée : + +```shell +show global variables like 'log_bin_trust_function_creators'; ++---------------------------------+-------+ +| Variable_name | Value | ++---------------------------------+-------+ +| log_bin_trust_function_creators | ON | +``` + +Si la variable n'est pas appliquée, activez-la manuellement : + +```shell +mysql> SET GLOBAL log_bin_trust_function_creators = 1; +``` + +Utilisateurs et groupes : + +| Utilisateur | Groupe | +|-------------|------------| +| centreonBI | centreonBI | + +Description des utilisateurs, umask et répertoire utilisateur : + +| Utilisateur | umask | home | +|-------------|-------|------------------| +| centreonBI | 0002 | /home/centreonBI | + +## Étape 2 : Installez l'interface Centreon MBI dans l'application Centreon + +Les actions listées à cette étape doivent être exécutées **sur le serveur central Centreon**. + +1. Installez le dépôt Business : vous pouvez le trouver sur le [portail support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). + +2. Puis lancez la commande suivante : + + + + +```shell +dnf install centreon-bi-server +``` + + + + +```shell +dnf install centreon-bi-server +``` + + + + +Installez **gpg** : + +```shell +apt install gpg +``` + +Importez la clé du dépôt : + +```shell +wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 +``` + +Puis installez Centreon MBI : + +```shell +apt install centreon-bi-server +``` + + + + +### Donner des droits à l'utilisateur centreon + +Dans la base de données du central, donnez des droits trigger à l'utilisateur **centreon** : + +```shell +GRANT TRIGGER ON centreon.* TO `centreon`@'%'; +GRANT TRIGGER ON centreon_storage.* TO `centreon`@'%'; +``` + +### Activer l'extension + +Le menu **Administration > Extension > Gestionnaire** vous permet +d'installer les différentes extensions détectées par Centreon. Cliquez sur la tuile **Centreon MBI** pour l'installer. + +Par la suite, téléchargez la licence envoyée par l'équipe Centreon pour pouvoir commencer à configurer les options générales. + +### Configurer l'extension + +Renseignez les valeurs suivantes dans les options générales de Centreon +MBI, menu **Rapports > Monitoring Business Intelligence > Paramètres globaux** : + +| Onglet | Option | Value | +|----------------------------------------------------------------------------------------|----------------------------|--------------------------------------------------------------------------------------| +| Options de l'ordonnanceur | Hôte de CBIS | Adresse IP du serveur de reporting | +| Options de l'ETL | Une base de données MySQL dédiée au reporting a été mise en place | Oui | | +| Widgets de reporting* | Reporting MySQL database | Adresse IP de la base de reporting (par défaut = adresse IP du serveur de reporting) | + +\* *Le test de connexion ne fonctionnera pas encore à ce moment de l'installation* + +### Accès à la base de données centrale + +Téléchargez la licence envoyée par l'équipe Centreon pour pouvoir commencer à configurer les options générales. + + + + + + + +La base de données de supervision MariaDB est hébergée sur le serveur de supervision central. + +Lancez la commande ci-dessous pour autoriser le serveur de reporting à se connecter aux bases de données du serveur de supervision. Utilisez l'option suivante : + +```shell +perl /usr/share/centreon/www/modules/centreon-bi-server/tools/centreonMysqlRights.pl --root-password=@ROOTPWD@ +``` + +**@ROOTPWD@**: Mot de passe root de la base MariaDB de supervision. S'il n'y a pas de mot de passe pour l'utilisateur "root", ne spécifiez pas l'option **root-password**. + + + + +La base de données de supervision MySQL est hébergée sur le serveur de supervision central. + +Lancez la commande ci-dessous pour autoriser le serveur de reporting à se connecter aux bases de données du serveur de supervision. Utilisez l'option suivante : + +```shell +perl /usr/share/centreon/www/modules/centreon-bi-server/tools/centreonMysqlRights.pl --root-password=@ROOTPWD@ +``` + +**@ROOTPWD@**: Mot de passe root de la base MySQL de supervision. S'il n'y a pas de mot de passe pour l'utilisateur "root", ne spécifiez pas l'option **root-password**. + + + + + + + + + + +La base de données de supervision MariaDB est hébergée sur un serveur dédié. + +Connectez-vous par SSH au serveur de la base de données, et exécutez les commandes suivantes : + +```SQL +CREATE USER 'centreonbi'@'$BI_ENGINE_IP$' IDENTIFIED BY 'centreonbi'; +GRANT ALL PRIVILEGES ON centreon.* TO 'centreonbi'@'$BI_ENGINE_IP$'; +GRANT ALL PRIVILEGES ON centreon_storage.* TO 'centreonbi'@'$BI_ENGINE_IP$'; +``` + +**$BI_ENGINE_IP$**: IP address of the reporting server. + + + + +La base de données de supervision MySQL est hébergée sur un serveur dédié. + +Connectez-vous par SSH au serveur de la base de données, et exécutez les commandes suivantes : + +```SQL +CREATE USER 'centreonbi'@'$BI_ENGINE_IP$' IDENTIFIED BY 'centreonbi'; +GRANT ALL PRIVILEGES ON centreon.* TO 'centreonbi'@'$BI_ENGINE_IP$'; +GRANT ALL PRIVILEGES ON centreon_storage.* TO 'centreonbi'@'$BI_ENGINE_IP$'; +``` + +**$BI_ENGINE_IP$**: IP address of the reporting server. + + + + + + + + + + +Si vous utilisez la réplication MariaDB pour vos **bases de données de supervision**, certaines vues sont créées lors de l'installation de Centreon MBI. Vous devez les exclure de la réplication en ajoutant la ligne suivante dans le fichier **my.cnf** du serveur esclave ou mariadb.cnf sur Debian 12. + +```shell +replicate-wild-ignore-table=centreon.mod_bi_%v01,centreon.mod_bi_%V01 +``` +Ensuite, créez les vues manuellement sur le serveur esclave : + +1. Téléchargez [le fichier suivant](../assets/reporting/installation/view_creation.sql) dans un répertoire temporaire (ici, **/tmp**), par exemple en utilisant **wget**. + +2. Exécutez la commande suivante (changez le nom de votre répertoire temporaire si besoin) : + +```bash +mysql centreon < /tmp/view_creation.sql +``` + +#### Configuration spécifique à Debian 12 + +MariaDB doit écouter sur toutes les interfaces au lieu d'écouter sur localhost/127.0.0.1 (valeur par défaut). Éditez le fichier suivant : + +```shell +/etc/mysql/mariadb.conf.d/50-server.cnf +``` + +Donnez au paramètre **bind-address** la valeur **0.0.0.0** et redémarrez **mariadb**. + +```shell +systemctl restart mariadb +``` + + + + +Si vous utilisez la réplication MySQL pour vos bases de données de supervision, certaines vues sont créées lors de l'installation de Centreon MBI. Vous devez les exclure de la réplication en ajoutant la ligne suivante dans le fichier my.cnf du serveur esclave ou mysql.cnf sur Debian 12. + +```shell +replicate-wild-ignore-table=centreon.mod_bi_%v01,centreon.mod_bi_%V01 +``` + +Ensuite, créez les vues manuellement sur le serveur esclave : + +1. Téléchargez [le fichier suivant](../assets/reporting/installation/view_creation.sql) dans un répertoire temporaire (ici, **/tmp**), par exemple en utilisant **wget**. + +2. Exécutez la commande suivante (changez le nom de votre répertoire temporaire si besoin) : + +```bash +mysql centreon < /tmp/view_creation.sql +``` + +#### Configuration spécifique à Debian 12 + +MySQL doit écouter sur toutes les interfaces au lieu d'écouter sur localhost/127.0.0.1 (valeur par défaut). Éditez le fichier suivant :: + +```shell +/etc/mysql/mysql.conf.d/mysqld.cnf +``` + +Donnez au paramètre **bind-address** la valeur **0.0.0.0** et redémarrez **mysql**. + +```shell +systemctl restart mysql +``` + + + + +### Donner des droits à l'utilisateur cbis + +Lorsque vous installez Centreon MBI, un [utilisateur](../monitoring/basic-objects/contacts.md) nommé **cbis** est créé automatiquement. Il permet au moteur de génération de rapports d'extraire les données de Centreon (en utilisant les APIs) afin de les insérer dans le rapport. Cet utilisateur doit [avoir accès à toutes les ressources supervisées par Centreon](../administration/access-control-lists.md) afin de pouvoir extraire les graphes de performance pour les rapports suivants : + +- Host-Graph-v2 +- Hostgroup-Graph-v2. + +Pour tester la connexion entre le serveur de reporting MBI et l'API Centreon, utilisez la commande suivante pour télécharger un graphique. Remplacez les paramètres du graphique et les timestamps, et remplacez XXXXXXXXX par le jeton d'autologin de l'utilisateur **cbis** : + +```bash +curl -XGET 'https://IP_CENTRAL/centreon/include/views/graphs/generateGraphs/generateImage.php?akey=XXXXXXXXX&username=CBIS&hostname=&service=&start=&end=' --output /tmp/image.png + +``` + +Exemple : + +```bash +curl -XGET 'https://10.1.1.1/centreon/include/views/graphs/generateGraphs/generateImage.php?akey=otmw3n1hu03bvt9e0caphuf50ph8sdthcsk8ofdk&username=CBIS&hostname=my-poller&service=Cpu&start=1623016800&end=1623621600' --output /tmp/image.png +``` + +Le résultat devrait ressembler au code ci-dessous, et l'image du graphe désiré doit avoir été téléchargée dans le répertoire `/tmp` : + +```text + % Total % Received % Xferd Average Speed Time Time Time Current + Dload Upload Total Spent Left Speed +100 18311 100 18311 0 0 30569 0 --:--:-- --:--:-- --:--:-- 30569 +``` + +## Étape 3 : Installez le serveur de reporting + +### Installer les paquets + +Cette étape s'effectue **sur la machine qui deviendra votre serveur MBI**. + +#### Prérequis + +Vous devez disposer des informations suivantes avant de procéder à l'installation : + +- IP/DNS de la base de données centrale +- IP/DNS de l'interface web Centreon +- IP/DNS de la base de données de reporting (**localhost** fortement recommandé) + +Définissez et récupérez le mot de passe SSH de l'utilisateur **centreonBI**, sur le serveur central (pour la mise à disposition des rapports générés sur l'interface). + +Pendant l'installation de la base de données, notez le mot de passe du compte **root** de la base. + +#### Installer les dépôts Centreon + +1. Installez le dépôt standard : + + + + +```shell +dnf install -y dnf-plugins-core +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf clean all --enablerepo=* +dnf update +``` + + + + +```shell +dnf install -y dnf-plugins-core +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf clean all --enablerepo=* +dnf update +``` + + + + +Installez les paquets prérequis : + +```shell +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list +``` + +Ensuite, importez la clé du dépôt : + +```shell +wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 +apt update +``` + + + + +2. Installez le dépôt Business. Vous pouvez trouver son adresse sur le [portail du support](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). + +#### Installer le dépôt de base de données + + + +#### Installer les dépendances + + + + +Installez le dépôt **epel** : + +```shell +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +``` + +Activer les dépôts **codeready-builder** : + +```shell +subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms +``` + + + + +Installez le dépôt **epel** : + +```shell +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +``` + +Activer les dépôts **codeready-builder** : + +```shell +dnf config-manager --set-enabled ol8_codeready_builder +``` + + + + +Installez le dépôt **epel** : + +```shell +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +``` + +Activez les dépôts powertools : + +```shell +dnf config-manager --set-enabled 'powertools' +``` + + + +Installez le dépôt **epel** : + +```shell +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +``` + +Activer les dépôts **codeready-builder** : + +```shell +subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms +``` + + + + +Installez le dépôt **epel** : + +```shell +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +``` + +Activez les dépôts **codeready-builder** : + +```shell +dnf config-manager --set-enabled ol9_codeready_builder +``` + + + +Installez le dépôt **epel** : + +```shell +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +``` + +Exécutez la commande suivante : + +```shell +dnf config-manager --set-enabled 'crb' +``` + + + + +Pas de dépendances requises. + + + + +#### Installer la base de données du serveur MBI + + + + + + +```shell +dnf install MariaDB-server MariaDB-client +``` + + + + +```shell +dnf install MariaDB-server MariaDB-client +``` + + + + +```shell +apt update +apt install mariadb-server mariadb-client +``` + + + + + + + + + + +```shell +dnf install https://dev.mysql.com/get/mysql84-community-release-el8-1.noarch.rpm +dnf config-manager --enable mysql-8.4-lts-community +dnf module disable mysql +dnf install mysql-community-server +systemctl start mysqld +``` + + + + +```shell +dnf install -y mysql-server mysql +dnf install -y centreon-mysql +systemctl enable --now mysqld +echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf +systemctl daemon-reload +systemctl restart mysqld +systemctl list-units --type=service | grep -i mysql +sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld +sudo systemctl start mysqld +sudo systemctl status mysqld +``` + + + + +```shell +apt update +apt install -y centreon-mysql +# Sélectionner "Use Legacy Authentication Method" +systemctl daemon-reload +systemctl restart mysql +``` + + + + + + + +#### Installer le module MBI sur le serveur MBI + + + + +```shell +dnf install centreon-bi-reporting-server +``` + + + + +```shell +dnf install centreon-bi-reporting-server +``` + + + + +```shell +apt update +apt install centreon-bi-reporting-server +``` + + + + +Assurez-vous qu'une version de Java 17 (ou 18) est installée. + + - Pour vérifier quelle version de Java est installée, entrez la commande suivante : + + ```shell + java -version + ``` + + - Pour une mise à jour de Java en version 17 (ou 18), allez sur la [page officielle de téléchargement d'Oracle](https://www.oracle.com/java/technologies/downloads/#java17). + + - Si plusieurs versions de Java sont installées, vous devez activer la bonne version. Affichez les versions installées avec la commande suivante puis sélectionnez la version 17 (ou 18) : + + ```shell + sudo update-alternatives --config java + ``` + +#### Activer les services + +Activez le service **cbis** : + +```shell +systemctl enable cbis +``` + +Démarrez et activez **gorgoned** : + +```shell +systemctl start gorgoned && systemctl enable gorgoned +``` + +### Optimiser la base de données + + + + + + +Assurez vous que [le fichier](../assets/reporting/installation/centreon.cnf) de configuration optimisé fourni dans les pré-requis est bien présent dans `/etc/my.cnf.d/`, puis redémarrez le service MariaDB : + +```shell +systemctl restart mariadb +``` + +Il est nécessaire de modifier la limitation **LimitNOFILE**. Changer cette option dans `/etc/my.cnf` NE fonctionnera PAS. + +```shell +mkdir -p /etc/systemd/system/mariadb.service.d/ +echo -ne "[Service]\nLimitNOFILE=32000\n" | tee /etc/systemd/system/mariadb.service.d/limits.conf +systemctl daemon-reload +systemctl restart mariadb +``` + +Si le service MariaDB échoue lors du démarrage, supprimer les fichiers *ib_logfile* (MariaDB doit absolument être stoppé) puis redémarrer à nouveau MariaDB : + +```shell +rm -f /var/lib/mysql/ib_logfile* +systemctl start mariadb +``` + +Si vous utilisez un fichier de socket spécifique pour MariaDB, modifiez le fichier `/etc/my.cnf` et dans la section [client], ajoutez : + +```shell +socket=$PATH_TO_SOCKET$ +``` + + + + +Assurez vous que [le fichier](../assets/reporting/installation/centreon.cnf) de configuration optimisé fourni dans les pré-requis est bien présent dans `/etc/my.cnf.d/`, puis redémarrez le service MariaDB : + +```shell +systemctl restart mariadb +``` + +Il est nécessaire de modifier la limitation **LimitNOFILE**. Changer cette option dans `/etc/my.cnf` NE fonctionnera PAS. + +```shell +echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list +``` + +Si le service MariaDB échoue lors du démarrage, supprimer les fichiers *ib_logfile* (MariaDB doit absolument être stoppé) puis redémarrer à nouveau MariaDB : +```shell +rm -f /var/lib/mysql/ib_logfile* +systemctl start mariadb +``` + +Si vous utilisez un fichier de socket spécifique pour MariaDB, modifiez le fichier `/etc/my.cnf` et dans la section [client], ajoutez : + +```shell +socket=$PATH_TO_SOCKET$ +``` + + + + +Assurez vous que [le fichier](../assets/reporting/installation/centreon.cnf) de configuration optimisé fourni dans les pré-requis est bien présent dans `/etc/my.cnf.d/`, puis redémarrez le service MariaDB : + +Renommez le fichier en `80-centreon.cnf`: + +```shell +mv centreon.cnf 80-centreon.cnf +``` + +MariaDB doit écouter toutes les interfaces au lieu de localhost/127.0.0.1, qui est la valeur par défaut. Éditez le fichier suivant : + +```shell +/etc/mysql/mariadb.conf.d/50-server.cnf +``` + +Définissez le paramètre **bind-address** à **0.0.0.0** et redémarrez mariadb. + +```shell +systemctl restart mariadb +``` + +Il est nécessaire de modifier la limitation **LimitNOFILE**. Changer cette option dans `/etc/mysql/mariadb.cnf` NE fonctionnera PAS. + +```shell +mkdir -p /etc/systemd/system/mariadb.service.d/ +echo -ne "[Service]\nLimitNOFILE=32000\n" | tee /etc/systemd/system/mariadb.service.d/limits.conf +systemctl daemon-reload +systemctl restart mariadb +``` + +Si le service MariaDB échoue lors du démarrage, supprimez les fichiers *ib_logfile* (MariaDB doit absolument être stoppé) puis redémarrez à nouveau MariaDB : + +```shell +rm -f /var/lib/mysql/ib_logfile* +systemctl start mariadb +``` + +Si vous utilisez un fichier de socket spécifique pour MariaDB, modifiez le fichier `/etc/mysql/mariadb.cnf` et dans la section [client], ajoutez : + +```shell +socket=$PATH_TO_SOCKET$ +``` + + + + + + + + +Assurez vous que [le fichier](../assets/reporting/installation/centreon.cnf) de configuration optimisé fourni dans les pré-requis est bien présent dans `/etc/my.cnf.d/`, puis redémarrez le service MySQL : + +```shell +systemctl restart mysql +``` + +Il est nécessaire de modifier la limitation **LimitNOFILE**. Changer cette option dans `/etc/my.cnf` NE fonctionnera PAS. + +```shell +mkdir -p /etc/systemd/system/mysql.service.d/ +echo -ne "[Service]\nLimitNOFILE=32000\n" | tee /etc/systemd/system/mysql.service.d/limits.conf +systemctl daemon-reload +systemctl restart mysql +``` + +Si le service MySQL échoue lors du démarrage, supprimez les fichiers *ib_logfile* (MySQL doit absolument être stoppé) puis redémarrez à nouveau MySQL : + +```shell +rm -f /var/lib/mysql/ib_logfile* +systemctl start mysql +``` + +Si vous utilisez un fichier de socket spécifique pour MySQL, modifiez le fichier `/etc/my.cnf` et dans la section [client], ajoutez : + +```shell +socket=$PATH_TO_SOCKET$ +``` + + + + +Assurez vous que [le fichier](../assets/reporting/installation/centreon.cnf) de configuration optimisé fourni dans les pré-requis est bien présent dans `/etc/my.cnf.d/`, puis redémarrez le service MySQL : + +```shell +systemctl restart mysql +``` + +Il est nécessaire de modifier la limitation **LimitNOFILE**. Changer cette option dans `/etc/my.cnf` NE fonctionnera PAS. + +```shell +mkdir -p /etc/systemd/system/mysql.service.d/ +echo -ne "[Service]\nLimitNOFILE=32000\n" | tee /etc/systemd/system/mysql.service.d/limits.conf +systemctl daemon-reload +systemctl restart mysql +``` + +Si le service MySQL échoue lors du démarrage, supprimez les fichiers *ib_logfile* (MySQL doit absolument être stoppé) puis redémarrez à nouveau MySQL : + +```shell +rm -f /var/lib/mysql/ib_logfile* +systemctl start mysql +``` + +Si vous utilisez un fichier de socket spécifique pour MySQL, modifiez le fichier `/etc/my.cnf` et dans la section [client], ajoutez : + +```shell +socket=$PATH_TO_SOCKET$ +``` + + + + +Assurez vous que [le fichier](../assets/reporting/installation/centreon.cnf) +de configuration optimisé fourni dans les pré-requis est bien présent dans `/etc/mysql/mysql.conf.d/`. + +Renommez le fichier en `80-centreon.cnf`: + +```shell +mv centreon.cnf 80-centreon.cnf +``` + +MySQL doit écouter toutes les interfaces au lieu de localhost/127.0.0.1, qui est la valeur par défaut. Éditez le fichier suivant : + +```shell +/etc/mysql/mysql.conf.d/mysqld.cnf +``` + +Définissez le paramètre **bind-address** à **0.0.0.0** et redémarrez mysql. + +```shell +systemctl restart mysql +``` + +Il est nécessaire de modifier la limitation **LimitNOFILE**. Changer cette option dans `/etc/mysql/mysql.cnf` NE fonctionnera PAS. + +```shell +mkdir -p /etc/systemd/system/mysql.service.d/ +echo -ne "[Service]\nLimitNOFILE=32000\n" | tee /etc/systemd/system/mysql.service.d/limits.conf +systemctl daemon-reload +systemctl restart mysql +``` + +Si le service MySQL échoue lors du démarrage, supprimez les fichiers *ib_logfile* (MySQL doit absolument être stoppé) puis redémarrez à nouveau MySQL : + +```shell +rm -f /var/lib/mysql/ib_logfile* +systemctl start mysql +``` + +Si vous utilisez un fichier de socket spécifique pour MySQL, modifiez le fichier `/etc/mysql/mysql.cnf` et dans la section [client], ajoutez : + +```shell +socket=$PATH_TO_SOCKET$ +``` + + + + + + + +### Sécuriser la base de données + +Il est obligatoire de sécuriser l'accès root de la base de données avant d'installer Centreon. +Si vous utilisez une base de données locale, exécutez la commande suivante sur le serveur central, sinon sur le serveur de base de données : + + + + +```shell +mariadb-secure-installation +``` + + + + +```shell +mysql_secure_installation +``` + + + + +- Répondez **oui** à toutes les questions, sauf à "Disallow root login remotely?" +- Il est obligatoire de définir un mot de passe pour l'utilisateur **root** de la base de données. Vous aurez besoin de ce mot de passe pendant l'[installation web](../installation/web-and-post-installation.md). + +> Voir les procédures avancées pour [Sécuriser votre plateforme MBI](../reporting/secure-your-mbi-platform.md). + +#### Commencer à configurer + +Vérifiez que la base de reporting est bien démarrée puis lancez les +commandes ci dessous et répondez aux questions: + +```shell +/usr/share/centreon-bi/config/install.sh +``` + +Le script gère l'échange de clés SSH entre le serveur de supervision et le serveur de reporting, et configure la règle de publication SFTP par défaut +afin de publier les rapports sur l'interface web Centreon. Enfin, il active la sauvegarde et démarre le service CBIS. + +Une fois l'installation terminée, poursuivez au chapitre suivant pour configurer l'ETL. + +#### Problème avec l'échange de la clé SSH + +Dans quelques cas, l'échange de clés SSH échoue. +Afin de résoudre le problème, procédez manuellement comme suit : + +Connectez-vous avec l'utilisateur `centreonBI` : + +```bash +su - centreonBI +``` + +Ensuite, générez une clé SSH : + +```bash +ssh-keygen -t ed25519 -a 100 -f ~/.ssh/id_ed25519 -P "" -q +``` + +Et affichez la clé publique générée (afin de l'autoriser ensuite sur Centreon) : + +```bash +cat /home/centreonBI/.ssh/id_ed25519.pub +``` + +Maintenant, **sur le serveur de supervision** : + +Créez un dossier `.ssh` dont `centreonBI` sera propriétaire, restreingez les droits sur ce fichier et collez dans le fichier `authorized_keys` le contenu de sa clé publique sur le serveur de reporting (affichée précédemment) : + +```bash +mkdir -p /home/centreonBI/.ssh/ && chown centreonBI: /home/centreonBI/.ssh/ && chmod 700 /home/centreonBI/.ssh/ && echo "@contenu de la clé publique@" > /home/centreonBI/.ssh/authorized_keys +``` + +L'échange de clés doit enfin être validé par une première connexion qui acceptera la signature du serveur SSH. +En tant que l'utilisateur `centreonBI` **depuis le serveur de reporting** : + +```bash +ssh centreonBI@@MONITORING_SERVER@ +``` + +Vous pouvez maintenant quitter la session `centreonBI` avec `exit` ou `Ctrl-D`. + +Pour continuer, relancez le script d'installation (`/usr/share/centreon-bi/config/install.sh`) comme ci-dessus et répondez **Oui** lorsqu'on vous demande de procéder à l'échange de clés SSH. +Vous aurez une erreur lors de la création de l'USER car il existe déjà. Ce n'est pas une étape bloquante. + +## Étape 4 : Configurez l'ETL dans l'interface de Centreon + +Centreon MBI intègre un ETL qui permet de : + +- Synchroniser les données brutes de la supervision vers le serveur de + reporting +- Alimenter les bases de données du serveur de reporting avec les + données statistiques +- Contrôler la rétention des données sur le serveur de reporting + + + +Dans le menu `Rapports > Monitoring Business Intelligence > Options générales > Options de l'ETL`, spécifiez les options +suivantes : + +| Option | Valeurs | +|------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| **Options générales** | | +| Une base de données MariaDB dédiée au reporting a été mise en place. | Oui. Vous devez avoir un serveur de reporting dédié. | +| Espace de stockage des fichiers temporaires sur le serveur de reporting * | Dossier sur le serveur de reporting dans lequel les dumps de données seront positionnés | +| Type de statistiques à traiter | Sélectionnez « Disponibilité uniquement » si vous utilisez uniquement les rapports de disponibilité. Sélectionnez « Performance et capacité uniquement» si vous souhaitez utiliser uniquement les rapports de capacité et de performance. Sélectionnez «Tous» afin de calculer les statistiques pour les deux types de rapports. | +| Activer le stockage des tables temporaires en mémoire (uniquement si la mémoire physique allouée au serveur de reporting est suffisante) | Crée des tables temporaires en utilisant de la RAM plutôt que de les créer sur disque. Non recommandé si vous disposez de bases de données avec moins de 64Go de RAM. | +| **Sélection du périmètre du reporting** | | +| Groupes d'hôtes | Sélectionnez les groupes d’hôtes pour lesquels vous souhaitez conserver les statistiques. | +| Catégories d'hôtes | Sélectionnez les catégories d’hôtes pour lesquels vous souhaitez conserver les statistiques. | +| Catégories de services | Sélectionnez les catégories de services pour lesquels vous souhaitez conserver les statistiques. | +| **Calcul des données de disponibilité** | | +| Sélectionner les plages de services pour le calcul des statistiques de disponibilité | Plages horaires (time periods) pour lesquelles les calculs de disponibilité des hôtes et des services sont réalisées | +| **Calcul des données de performance et de capacité** | | +| Granularité des données statistiques à calculer | Sélectionnez le ou les niveaux de granularité pour le calcul des données de performance (1) | +| Sélectionner les plages de services pour le calcul des statistiques de performance | Plages horaires sur les jours de la semaine pris en compte dans le calcul des données de capacité et de performance | +| **Capacity statistic aggregated by month** | | +| Sélectionne la plage de service 24h/24, 7j/7 pour le calcul des statistiques mensuelles de capacité | Sélectionnez la plage horaire 24x7. | +| Sélectionner les catégories de services liées aux indicateurs de capacité | Sélectionnez les catégories de services ayant été rattachés à des services de type capacité | +| Exclure les métriques qui ne renvoient pas une indication d'utilisation des espaces de stockage | Concerne uniquement les métriques liées aux services qui renvoient une information de capacité. Sélectionnez uniquement les métriques qui donnent une valeur maximale ou une valeur totale de capacité et non une valeur d’utilisation. (Par exemple, la métrique “ size ” returnée par le plugin check_centreon_snmp_remote_storage ») | +| **Paramètres pour le calcul des centiles** | | +| Calculating centile aggregation by | Sélectionnez la granularité des calculs. Le rapport de trafic fourni en standard avec BI 2.1 utilise les données au Mois. | +| Sélectionner les catégories de services sur lesquelles aggréger les données | Sélectionnez uniquement les catégories de services pertinentes (Ex: Traffic) | +| Premier jour de la semaine | Sélectionnez le premier jour à considérer pour les statistiques à la semaine | +| Créer les combinaisons centile-plage horaire qui couvrent vos besoins (Format du centile : 00.0000) | Créez des combinaisons centile/plage horaire sur lesquels les statistiques seront effectuées | + +### Définir les données qui seront utilisées par MBI + +Dans la page **Reporting > Monitoring Business Intelligence > Paramètres Globaux**, vous pouvez utiliser les options de l'onglet **Options de l'ETL** pour déterminer les données qui seront importées dans la base de données MBI depuis le serveur central. Assurez-vous de n'importer que les données que vous souhaitez voir dans les rapports : toutes les données innécessaires prennent de l'espace de stockage et augmentent le temps de calcul. + +| **Options** | **Valeurs** | +|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| **Options générales** | +| Type de statistiques à traiter |
    • Selectionnez **Disponibilité uniquement** si vous n'utilisez que les [rapports de disponibilité](../alerts-notifications/availability.md).
    • Select **Performance et capacité uniquement** si vous ne souhaitez avoir que des rapports de capacité et performance (c'est-à-dire les rapports de [performance](available-reports/performance-reports.md), [stockage](available-reports/storage-reports.md), [réseau](available-reports/network-reports.md), [virtualisation](available-reports/virtualization-reports.md), [consommation électrique](available-reports/electric-consumption-reports.md)).
    • Select **Toutes** pour calculer les statistiques de ces deux types de rapports. Cette option permet également d'obtenir des rapports de type [profiling](available-reports/profiling-reports.md) et [diagnostics de la base de données](available-reports/database-diagnostics-reports.md).
    | +| **Sélection du périmètre du reporting*** | | +| Groupes d'hôtes | Ne sélectionnez que les groupes d'hôtes pour lesquels vous souhaitez créer des rapports. | +| Catégories d'hôtes | Ne sélectionnez que les catégories d'hôtes pour lesquelles vous souhaitez créer des rapports. | +| Catégories de services | Ne sélectionnez que les catégories de services pour lesquelles vous souhaitez créer des rapports. | +| **Calcul des données de disponibilité** | | +| Plages de services pour le calcul des statistiques de disponibilité | Vos [rapports de disponibilité](available-reports/availability-events-reports.md) contiendront uniquement des données de ces [périodes temporelles](../monitoring/basic-objects/timeperiods.md). | +| **Calcul des données de performance et de capacité** | | +| Granularité des données statistiques à calculer | Sélectionnez le niveau de granularité nécessaire pour générer les rapports de performance souhaités (1). | +| Plages de services pour le calcul des statistiques de performance. | +| **Données de capacité aggrégées par mois** (rapports de [stockage](available-reports/storage-reports.md)). Les données sont uniquement agrégées par mois. | | +| Plage de services pour le calcul des statistiques de capacité | Sélectionnez **24x7**, il s'agit de la seule période temporelle pour laquelle il est pertinent de calculer l'espace de stockage. | +| Catégories de services liées aux indicateurs de capacité | Sélectionnez les [catégories de service](../monitoring/categories.md) qui ont été associées à des services de capacité. | +| Exclure les métriques qui ne renvoient pas une indication d'utilisation des espaces de stockage | Concerne les métriques liées aux services qui renvoient des données de stockage. Sélectionnez les métriques qui ne renvoient pas des informations d'utilisation de stockage mais une valeur maximale ou totale (par exemple la métrique "taille"). | + +**(1)** Les rapports nécessitant une granularité des données à l'heure sont listés ci-dessous. +Si vous ne souhaitez pas utiliser ces rapports,désactivez le calcul des statistiques à l'heure: + +- Hostgroup-Host-details-1 + +- Host-detail-v2 +- Hostgroup-traffic-Average-Usage-By-Interface +- Hostgroup-traffic-by-Interface-And-Bandwith-Ranges + +### ETL: Rétention de données + +Le serveur de reporting contient des tables de statistiques spécifiques à Centreon MBI dans la base de données "centreon_storage". +L'espace de stockage utilisé par ces tables augmente chaque jour. Il est possible de contrôler la taille de ces tables en définissant +des règles de rétention des données. + +Sous **Rapports > Monitoring Business Intelligence > Options Générales > Options de rétention des données**, +la rétention des données peut être gérée par : + +- Type de données (disponibilité, performance). +- Granularité des données (données brutes, valeurs horaires, quotidiennes ou mensuelles). + +> Avant d'activer les options de rétention de données, vérifiez que le moteur de reporting +> utilise un serveur MariaDB dédié, et que l'option correspondante est réglée sur +> **Oui** dans le menu **Reporting > Business Intelligence > Options générales Options ETL**. + +Activez la gestion de la rétention des données en sélectionnant **Oui**, puis définissez les options de la configuration (exemple ci-dessous). + +![image](../assets/reporting/installation/bi_retention.png) + +Pour activer la purge automatique des anciennes données, modifiez le fichier cron +**/etc/cron.d/centreon-bi-purge** sur le serveur de reporting, puis décommentez la ligne suivante : + +```shell +#0 20 * * * root @CENTREON_BI_HOME@/*etl*/dataRetentionManager.pl >> @CENTREON_BI_LOG@/dataRetentionManager.log 2>&1 +``` + +Évitez les périodes prévues pour les calculs statistiques avec Centreon MBI ETL et les générations de rapports. + +Vous pouvez exécuter ce cron quotidiennement ou hebdomadairement, en fonction du temps d'exécution du batch et de la charge générée sur le serveur. + + + + +Redémarrez le service cron : + +```shell +systemctl restart crond +``` + + + + +Redémarrez le service cron : + +```shell +systemctl restart cron +``` + + + + +**BONNES PRATIQUES** : Sélectionnez différentes périodes de rétention en fonction de la granularité des données statistiques: + +- Les valeurs agrégées par heure sont utilisées pour analyser une métrique sur une courte période, elles prennent + beaucoup d'espace sur le disque. Vous n'aurez peut-être pas besoin de conserver ces statistiques plus de deux ou trois mois. +- Au-delà de cinq ou six mois, vous n'aurez peut-être besoin que de visualiser la tendance pour lesstatistiques de disponibilité ou de performance. + Vous pourriez alors conserver lesdonnées agrégées quotidiennes pendant un maximum de six mois, par exemple, etconfigurer la conservation des données + agrégées mensuelles pour une période de plusieurs dizaines de mois. + +Veuillez passer à la section suivante pour continuer l'installation. + +## Étape 5 : Construire la base de données MBI + +### Prérequis + +* Avant de continuer, assurez-vous que vous avez installé le fichier de configuration MariaDB comme indiqué ci-dessus dans les prérequis. +* Configurez et activez la rétention des données afin que seules les données requises soient importées et calculées. +* Assurez-vous que [les données soient prêtes sur le serveur central](how-mbi-works.md#phase-1--les-données-sont-préparées-par-le-serveur-central). +* Assurez-vous que le processus **gorgoned** finctionne correctement : `systemctl status gorgoned`. Si besoin, redémarrez-le: `systemctl restart gorgoned`. +* Attention, si vous créez la base de données MBI pour la première fois, vous devez importer toutes les données en une seule fois. Si vous disposez d'une grande quantité de données et/ou si vous démarrez le processus tard dans la journée, il est important de savoir que la phase de création de la base de données peut prendre un temps considérable, pouvant même se prolonger jusqu'au lendemain. Dans ce cas, vous devez désactiver [temporairement](#réactiver-lexécution-quotidienne-du-script) l'exécution quotidienne de l'ETL, jusqu'à ce que le provisionnement initial soit terminé, afin d'éviter les doublons ou d'autres problèmes. + + 1. Éditez le fichier cron **/etc/cron.d/centreon-bi-engine** et commentez la ligne suivante : + + ```shell + #30 4 * * * root /usr/share/centreon-bi/bin/centreonBIETL -d >> /var/log/centreon-bi/centreonBIETL.log 2>&1 + ``` + + 2. Redémarrez **crond**. + + + + +```shell +systemctl restart crond +``` + + + + +```shell +systemctl restart cron +``` + + + + +### Construction des statistiques à partir des données historiques + +Exécutez la commande suivante sur le serveur de reporting. Celle-ci va : + +- Supprimer toutes les données existantes du serveur de reporting. +- Importer les données de supervision brutes du serveur de supervision vers le serveur de reporting (en fonction des paramètres de rétention). +- Remplir les tables contenant les statistiques de disponibilité des hôtes et des services. +- Remplir les tables contenant les statistiques de performance et de capacité des hôtes et des services. + +```shell +/usr/share/centreon-bi/bin/centreonBIETL -r +``` + +Vous pouvez l'exécuter en arrière-plan et rediriger la sortie du script vers un journal : + +```shell +nohup /usr/share/centreon-bi//bin/centreonBIETL -r >> /var/log/centreon-bi/centreonBIETL.log 2>&1 & +``` + +Regardez le fichier de log **/var/log/centreon-bi/centreonBIETL.log** : vous devriez voir des lignes avec les 4 parties suivantes : + +```shell +2025-08-01 13:34:16 - INFO - [SCHEDULER] >>>>>>> start +2025-08-01 13:34:16 - INFO - [SCHEDULER][IMPORT] >>>>>>> start +... +2025-08-01 13:35:18 - INFO- [SCHEDULER][IMPORT] <<<<<<< end +2025-08-01 13:35:18 - INFO - [SCHEDULER][DIMENSIONS] >>>>>>> start +... +2025-08-01 13:35:52 - INFO - [SCHEDULER][DIMENSIONS] <<<<<<< end +2025-08-01 13:35:52 - INFO - [SCHEDULER][EVENT] >>>>>>> start +... +2025-08-01 13:38:37 - INFO - [SCHEDULER][EVENT] <<<<<<< end +2025-08-01 13:38:37 - INFO - [SCHEDULER][PERFDATA] >>>>>>> start +... +2025-08-01 13:48:17 - INFO - [SCHEDULER][PERFDATA] <<<<<<< end +2025-08-01 13:58:17 - INFO - [SCHEDULER] <<<<<<< end +``` + +### Réactiver l'exécution quotidienne du script + +Une fois le processus de reconstruction des données terminé, vous pouvez activer le calcul des +statistiques. +Sur le serveur de reporting, éditez le fichier **/etc/cron.d/centreon-bi-engine** et décommentez la ligne suivante : + +```shell +#30 4 * * * root /usr/share/centreon-bi/bin/centreonBIETL -d >> /var/log/centreon-bi/centreonBIETL.log 2>&1 +``` + + + + +Redémarrez le service cron sur le serveur de reporting : + +```shell +systemctl restart crond +``` + + + + +Redémarrez le service cron sur le serveur de reporting : + +```shell +systemctl restart cron +``` + + + + +> Assurez-vous que le batch **centreonBIETL** ne démarre qu'une fois que le batch **eventReportBuilder** est terminé sur +> le serveur de supervision (consultez le fichier cron **/etc/cron.d/centreon** sur le serveur de supervision). + +L'installation de Centreon MBI est maintenant terminée. Vous pouvez créer des [tâches](concepts.md#tâches) afin de générer des rapports. Consultez [le tutoriel](../getting-started/analyze-resources-availability.md). + +## Supervisez votre serveur MBI avec Centreon + +Il est fortement recommandé de superviser votre serveur MBI à l'aide du [connecteur Centreon MBI](/pp/integrations/plugin-packs/procedures/applications-monitoring-centreon-mbi). diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md index 194296abd350..eaa27cb65466 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md @@ -5,6 +5,7 @@ description: "Mettre à niveau un cluster Centreon HA depuis la version 23.04 ve --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Link from '@docusaurus/Link'; Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 23.04 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md index 1ebef4b448ab..11235f79164f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md @@ -5,6 +5,7 @@ description: "Mettre à niveau un cluster Centreon HA depuis la version 23.10 ve --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Link from '@docusaurus/Link'; Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 23.10 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md index 6c7cad3e6a76..03b326ab4e6d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md @@ -5,6 +5,7 @@ description: "Mettre à niveau un cluster Centreon HA depuis la version 24.04 ve --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Link from '@docusaurus/Link'; Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 24.04 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md index 48188adba7fb..4cbb0ca74841 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md @@ -5,6 +5,7 @@ description: "Mettre à niveau un cluster Centreon HA depuis la version 24.10 ve --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Link from '@docusaurus/Link'; Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 24.10 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md index cf9f39931264..c4ab7ea923ee 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md @@ -4,6 +4,7 @@ title: Montée de version de Centreon HA depuis Centreon 26.10 --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Link from '@docusaurus/Link'; Ce chapitre décrit comment mettre à niveau votre plateforme Centreon HA de la version 25.10 vers la version 26.10. Veuillez consulter la [matrice des montées de version](../upgrade-matrix.mdx) pour savoir si votre OS est encore pris en charge. Si ce n'est pas le cas, vous devrez migrer votre plateforme : contactez votre représentant commercial Centreon pour discuter de toute migration avec HA. diff --git a/secure_db.txt b/secure_db.txt new file mode 100644 index 000000000000..22db1799dc10 --- /dev/null +++ b/secure_db.txt @@ -0,0 +1,34 @@ +### Secure the database + +It is mandatory to secure the database's root access before installing Centreon. +If you are using a local database, run the following command on the central server: + + + + +```shell +mariadb-secure-installation +``` + + + + +Retrieve the temporary password created by MySQL: + +```shell +grep 'temporary password' /var/log/mysqld.log +``` + +Then change it when prompted by the following command: + +```shell +mysql_secure_installation +``` + + + + +* Answer **yes** to all the questions except "Disallow root login remotely?". +* It is mandatory to set a password for the **root** user of the database. You will need this password during the [web installation](../web-and-post-installation.md). + +> For more information, please see the [official MariaDB documentation](https://mariadb.com/kb/en/mysql_secure_installation/). \ No newline at end of file diff --git a/src/components/UpgradeMatrixTable.jsx b/src/components/UpgradeMatrixTable.jsx new file mode 100644 index 000000000000..d846ef896a24 --- /dev/null +++ b/src/components/UpgradeMatrixTable.jsx @@ -0,0 +1,72 @@ +import React from 'react'; + +function UpgradeMatrixTable({ rows }) { + const [versionFilter, setVersionFilter] = React.useState('all'); + const [supportedFilter, setSupportedFilter] = React.useState('all'); + + const versions = Array.from(new Set(rows.map((row) => row.version))); + + const filteredRows = rows.filter((row) => { + if (versionFilter !== 'all' && row.version !== versionFilter) { + return false; + } + if (supportedFilter !== 'all' && (row.supported ? 'OUI' : 'NON') !== supportedFilter) { + return false; + } + return true; + }); + + return ( +
    +
    + + +
    + + + + + + + + + + + {filteredRows.length === 0 ? ( + + + + ) : ( + filteredRows.map((row, index) => ( + + + + + + + )) + )} + +
    Version de départOS supporté à l'époqueOS toujours supporté ?Procédure à suivre
    Aucun résultat pour ces filtres.
    {row.version}{row.os} + {row.supported ? 'OUI' : 'NON'} + {row.procedureLabel}
    +
    + ); +} + +export default UpgradeMatrixTable; diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md.bak b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md.bak new file mode 100644 index 000000000000..08326fe524a9 --- /dev/null +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/unattended.md.bak @@ -0,0 +1,164 @@ +--- +id: unattended-install-remote +title: Unattended installation of a remote server +description: "Install a remote server quickly using an unattended script" +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +To install a remote server quicker, you can use a script. This will perform all installation steps. You must then register the remote server and attach it to the central server. + +## Prerequisites + +1. Update your system: + + + + + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms + ``` + + Replace **my_username** and **my_password** with your Red Hat account credentials. + + + + + ```shell + dnf update + ``` + + + + + ```shell + dnf update + subscription-manager register --username my_username --password my_password --auto-attach --force + subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms + ``` + + Replace **my_username** and **my_password** with your Red Hat account credentials. + + + + + ```shell + dnf update + ``` + + + + + ```shell + apt update && apt upgrade + ``` + + + + +2. Download the script: + + ```shell + curl -L https://download.centreon.com/26.10/unattended.sh --output /tmp/unattended.sh + ``` + +## Installation + +1. As **root**, run the script with the options you want. The script writes a full log, including any errors, to `/var/log/centreon-unattended-.log`. + + Here is the basic command (installs MariaDB with no TLS): + + ```shell + bash /tmp/unattended.sh install -t central -v 26.10 + ``` + + And here are the options you can pass (see the [examples](#examples) below): + + | Option | Description | + |--------|-------------| + | `-d ` | Database to install. By default, the script installs MariaDB: use `-d mysql` to install MySQL instead. | + | `--tls enabled` | Installs the central server in TLS mode: the connections to the web interface and to the database are encrypted. Without this option, the central server is installed without TLS. Note that on some OSs, cryptographic policies may prevent the script from running correctly. | + | `-p ` | Password of the default **admin** database account. If you omit this option, the script generates a password and tells you where it is stored. | + | `-s` | Silent installation: the script does not prompt you for anything. | + | `-l ` | Level of detail of the log file: `DEBUG`, `INFO`, `WARN` or `ERROR`. | + + To display the full list of options, run: + + ```shell + bash /tmp/unattended.sh -h + ``` + +2. Go to http(s)://\/centreon (where \ is your server's IP address) and log in. Then follow the + [initialization of the monitoring](../web-and-post-installation.md#initialization-of-the-monitoring) steps. + + 4. Once the script has run, carry out [steps 4 to 8 of the standard installation procedure for a remote server](./using-packages.md#step-5-register-the-server). + + +3. Start using Centreon: follow our [Getting started](../../getting-started/welcome.md) guide to start monitoring your resources. + +## Examples + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    SettingsCommand
    Using MariaDB and no TLSbash /tmp/unattended.sh install -t central -v 26.10
    Using MySQL and no TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql
    Using MariaDB and TLSbash /tmp/unattended.sh install -t central -v 26.10 -s --tls enabled
    Using MySQL and TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql --tls enabled
    + +     + + + + + + + + + + + + + + + + + + + + + + + + + + + +
    SettingsCommand (replace XXXXX with the password of your choice)
    Using MariaDB and no TLSbash /tmp/unattended.sh install -t central -v 26.10 -p XXXXX
    Using MySQL and no TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql -p XXXXX
    Using MariaDB and TLSbash /tmp/unattended.sh install -t central -v 26.10 -s --tls enabled -p XXXXX
    Using MySQL and TLSbash /tmp/unattended.sh install -t central -v 26.10 -s -d mysql --tls enabled -p XXXXX
    + +     +     diff --git a/versioned_docs/version-26.10/installation/prerequisites.md.bak b/versioned_docs/version-26.10/installation/prerequisites.md.bak new file mode 100644 index 000000000000..55cd1bb2e6f2 --- /dev/null +++ b/versioned_docs/version-26.10/installation/prerequisites.md.bak @@ -0,0 +1,336 @@ +--- +id: prerequisites +title: Prerequisites +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +This topic gives you broad guidelines to determine the size of your platform. See also the prerequisites sections for [MAP](../graph-views/map-web-install.md#prerequisites) and [MBI](../reporting/installation.md#hardware-layer). + +## Architecture + +First, use the guidelines described on the [Architectures](./architectures.md#what-kind-of-architecture-do-you-need) page to determine the type of architecture you need. + +## Characteristics of the servers + +* The more services you monitor, the more CPU you need. +* The space used to store collected performance data depends on several criteria: + + * Frequency of checks + * Number of checks + * Retention time + * Average number of metrics per service + +* The number of users simultaneously connected to the interface of the central/remote server has an impact on performance. If a large number of users will have to log in to the Centreon interface at the same time, you will need more CPU. + +The following data is meant for: + +* An average of 10 services per host. +* Data is collected every 5 minutes. +* The retention period is 12 months. +* Each service has on average 8 metrics. + +You need to adapt the following figures to your actual values. Bear in mind that you may need to adjust the size of your platform as you add more hosts over time. + +## Architecture and central/database sizing + + + + +Standalone central server: + +| Element | Value | +| ----------------------------| --------- | +| CPU | 4 vCPU | +| RAM | 4 GB | + +> If you prefer, you can also monitor your 500 hosts using a [poller](#poller-sizing) attached to a central. + +This is how your central server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +| - |----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 1 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 4 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/centreon | contains mostly RRD files | 34 GB | +| vg_data | /var/lib/centreon-broker | contains broker retention files | 5 GB | +| vg_data | /var/lib/centreon-engine | contains engine retention files | 5 GB | +| vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 106 GB | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
    If you perform backups, use the following characteristics:
    • size of the /var/lib/mysql partition * 0.6
    • this size is meant for 1 full backup and 6 partial ones
    • this is only an estimate, size should be checked manually
    | +| vg_data | | Free space (unallocated) | 5 GB | + +> Your system must use LVM to manage the file system. + +In some cases, you may want to set up a distributed architecture, even for fewer than 500 hosts. The poller will have the same characteristics as for up to 1,000 hosts. + +     + + +Distributed architecture: + +* 1 central server +* 1 [poller](#poller-sizing) for every 500 hosts + +### Central server + +| Element | Value | +| ----------------------------| --------- | +| CPU | 4 vCPU | +| RAM | 8 GB | + +This is how your central server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +| - |----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 1 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 4 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/centreon | contains mostly RRD files | 68 GB | +| vg_data | /var/lib/centreon-broker | contains Broker retention files | 10 GB | +| vg_data | /var/lib/centreon-engine | | 5 GB | +| vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 213 GB | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
    If you perform backups, use the following characteristics:
    • size of the /var/lib/mysql partition * 0.6
    • this size is meant for 1 full backup and 6 partial ones
    • this is only an estimate, size should be checked manually
    | +| vg_data | | Free space (unallocated) | 5 GB | + +> Your system must use LVM to manage the file system. + +> At least 1 GB of non-allocated free space must be available for the **volume group** containing **/var/lib/mysql**, +> if you wish to use **snapshot LVM** as a backup method. + +     + + +Distributed architecture: + +* 1 central server +* 1 [poller](#poller-sizing) for every 500 hosts + +### Central server + +| Element | Value | +| ----------------------------| --------- | +| CPU | 4 vCPU | +| RAM | 8 GB | + +This is how your central server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +| - |----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 1 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 4 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/centreon | contains mostly RRD files | 169 GB | +| vg_data | /var/lib/centreon-broker | contains Broker retention files | 25 GB | +| vg_data | /var/lib/centreon-engine | | 5 GB | +| vg_data | /var/lib/mysql (only if the DBMS is on the central server) | database | 538 GB | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
    If you perform backups, use the following characteristics:
    • size of the /var/lib/mysql partition * 0.6
    • this size is meant for 1 full backup and 6 partial ones
    • this is only an estimate, size should be checked manually
    | +| vg_data | | Free space (unallocated) | 5 GB | + +> Your system must use LVM to manage the file system. + +> At least 1 GB of non-allocated free space must be available for the **volume group** containing **/var/lib/mysql**, +> if you wish to use **snapshot LVM** as a backup method. + +     + + +Distributed architecture: + +* 1 central server without a database +* 1 database server +* 1 [poller](#poller-sizing) for every 500 hosts + +### Central server + +| Element | Value | +| ----------------------------| --------- | +| CPU | 4 vCPU | +| RAM | 8 GB | + +This is how your central server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +| - |----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 1 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 4 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/centreon | contains mostly RRD files | 339 GB | +| vg_data | /var/lib/centreon-broker | contains Broker retention files | 50 GB | +| vg_data | /var/lib/centreon-engine | | 5 GB | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
    If you perform backups, use the following characteristics:
    • size of the /var/lib/mysql partition * 0.6
    • this size is meant for 1 full backup and 6 partial ones
    • this is only an estimate, size should be checked manually
    | + +### Database server + +| Element | Value | +| ----------------------------| --------- | +| CPU | 4 vCPU | +| RAM | 8 GB | + +This is how the database server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +| - |----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 1 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 4 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/mysql | database | 1094 GB | +| vg_data | | Free space (unallocated) | 5 GB | + +> Your system must use LVM to manage the file system. + +> At least 1 GB of non-allocated free space must be available for the **volume group** containing **/var/lib/mysql**, +> if you wish to use **snapshot LVM** as a backup method. + +     +Distributed architecture: + +* 1 central server without a database +* 1 database server +* 1 [poller](#poller-sizing) for every 500 hosts + +### Central server + +| Element | Value | +| ----------------------------| --------- | +| CPU | 8 vCPU | +| RAM | 8 GB | + +This is how your central server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +| - |----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 1 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 4 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/centreon | contains mostly RRD files | 677 GB | +| vg_data | /var/lib/centreon-broker | contains broker retention files | 50 GB | +| vg_data | /var/lib/centreon-engine | | 5 GB | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
    If you perform backups, use the following characteristics:
    • size of the /var/lib/mysql partition * 0.6
    • this size is meant for 1 full backup and 6 partial ones
    • this is only an estimate, size should be checked manually
    | + +### Database server + +| Element | Value | +| ----------------------------| --------- | +| CPU | 8 vCPU | +| RAM | 8 GB | + +This is how the database server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +| - |----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 1 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 4 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/mysql | database | 2257 GB | +| vg_data | | Free space (unallocated) | 5 GB | + +> Your system must use LVM to manage the file system. + +> At least 1 GB of non-allocated free space must be available for the **volume group** containing **/var/lib/mysql**, +> if you wish to use **snapshot LVM** as a backup method. + +     + + +Distributed architecture: + +* 1 central server without a database +* 1 database server +* 1 [poller](#poller-sizing) for every 500 hosts + +### Central server + +| Element | Value | +| ----------------------------| --------- | +| CPU | 8 vCPU | +| RAM | 16 GB | + +This is how your central server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +| - |----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 2 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 8 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/centreon | contains mostly RRD files | 1355 GB | +| vg_data | /var/lib/centreon-broker | contains broker retention files | 50 GB | +| vg_data | /var/lib/centreon-engine | | 5 GB | +| vg_data | /var/cache/centreon/backup | backup directory | 10 GB
    If you perform backups, use the following characteristics:
    • size of the /var/lib/mysql partition * 0.6
    • this size is meant for 1 full backup and 6 partial ones
    • this is only an estimate, size should be checked manually
    | + +### Database server + +| Element | Value | +| ----------------------------| --------- | +| CPU | 8 vCPU | +| RAM | 16 GB | + +This is how the database server should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +| - |----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 2 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 8 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/mysql | database | 4500 GB | +| vg_data | | Free space (unallocated) | 5 GB | + +> Your system must use LVM to manage the file system. + +> At least 1 GB of non-allocated free space must be available for the **volume group** containing **/var/lib/mysql**, +> if you wish to use **snapshot LVM** as a backup method. + +     + + +For very large amounts of data, contact your sales representative. + + +     + +## Poller sizing + +* To handle testing or small environments (up to 2000 services with checks every 5 minutes, or up to 500 services with checks every minute): + +| Element | Value | +| ----------------------------| --------- | +| CPU (logical core at 3 GHz) | 2 vCPU | +| RAM | 2 GB | +| HDD | 40 GB | + +* To handle production environments (up to 7000 services with checks every 5 minutes): + +| Element | Value | +| ----------------------------| --------- | +| CPU (logical core at 3 GHz) | 4 vCPU | +| RAM | 4 GB | +| HDD | 40 GB | + +This is how the pollers should be partitioned: + +| Volume group (LVM) | File system | Description | Size | +|-| ----------------------------|-------------|----------------------------------------------------------| +| | /boot | boot images | 1 GB | +| vg_root | / | system root | 20 GB | +| vg_root | swap | swap | 4 GB | +| vg_root | /var/log | contains all log files | 10 GB | +| vg_data | /var/lib/centreon-engine | | 5 GB | + +> Your system must use LVM to manage the file system. + +> The number of +> vCPU depends on the complexity of the checks. If you use connectors or perform a large number of system/third-party +> binary calls, you should add more vCPU. + +## Network flows + +If you have firewalls or security resources in place, check the [table of network flows](./technical.md#tables-of-network-flows). diff --git a/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md b/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md new file mode 100644 index 000000000000..5dfc15fd18fd --- /dev/null +++ b/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md @@ -0,0 +1,632 @@ +--- +id: upgrade-debian-in-place +title: Upgrading Centreon and Debian (12 to 13) on the same server +description: "In-place migration procedure for Debian - Debian 12 to 13" +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +Use this procedure if you are running Centreon 24.04, 24.10 or 25.10 on Debian 12 and you wish to upgrade to Centreon 26.10 (only Debian 13 is supported for this version). + +> Run every command as `root`. + + +## Step 1: Before you start + +### 1.1 Take a snapshot of each server + +Snapshot every server (central server, database server, MAP server, MBI server). If you have a remote database, take both snapshots at the same time, with Centreon stopped if possible. It is the only way to roll back quickly. + +### 1.2 Create dumps + +Snapshots let you roll back a whole server quickly, but they do not replace backups. They usually share the VM's storage, capture databases only in a crash-consistent state, and cannot restore a single database or file. Once your snapshots are done, also make the backups below. + + ```bash + B=/root/upgrade-2610-backup; mkdir -p $B + # On the server that hosts the database + mysqldump --single-transaction --routines --triggers --events centreon | gzip > $B/centreon.sql.gz + mysqldump --single-transaction --routines --triggers --events centreon_storage | gzip > $B/centreon_storage.sql.gz + mysqldump --single-transaction --routines --triggers --events centreon_map | gzip > $B/centreon_map.sql.gz # [MAP], where it lives + zcat $B/centreon_storage.sql.gz | tail -n 1 # "-- Dump completed on …" + # On every server + tar czf $B/etc-$(hostname).tar.gz -C / etc + dpkg -l > $B/dpkg-l.txt + systemctl list-unit-files --state=enabled > $B/enabled-units.txt # compared in step 9 + ``` + +### 1.3 Check the state of the server + +Before starting the upgrade, check that the server is in the expected state: Debian 12, Centreon 25.10, enough free disk space, and working package repositories. If any result differs from the expected one, fix it before going further. + + ```bash + cat /etc/debian_version # 12.x + dpkg -l centreon-web | awk '/^ii/{print $3}' # 25.10.x + df -h / /var /var/lib/mysql # several GB free (~1,300 packages) + apt-get update # no error (a broken repository blocks the upgrade to Debian 13) + ``` + +### 1.4 Check that cron and logrotate are installed (on every Centreon server) + +Centreon needs **cron** to run its scheduled jobs and **logrotate** to rotate its logs. Minimal Debian images often include neither, and nothing warns you when they are missing. + +```bash +ls /etc/cron.d/ | grep -iE "centreon|centstorage" # Centreon jobs here? +dpkg -l cron | grep -q "^ii" || apt-get install -y cron # install if missing +systemctl enable --now cron && systemctl is-active cron # active +dpkg -l logrotate | grep -q "^ii" || apt-get install -y logrotate +chmod 644 /etc/logrotate.d/cbd /etc/logrotate.d/centengine 2>/dev/null +logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" # nothing +``` + +- **Without cron**, the Centreon jobs never run and no error is shown. This affects the MBI jobs (ETL, purge, backup) in particular. +- **Without logrotate**, Centreon logs are never rotated. +- **The `chmod 644` line** is a workaround. The Broker and Engine logrotate files are shipped with permissions `0664`, so logrotate ignores them. A package upgrade can restore `0664`, so check again in step 9. + +## Step 2: Update your Centreon version to the latest minor + +Follow the update procedures for your version ([24.04](https://archives-docs.centreon.com/24.04/docs/update/update-centreon-platform/), [24.10](../../version-24.10/update/update-centreon-platform.md) or [25.10](../update/update-centreon-platform.md)). Update your central server, your pollers and your remote servers. + + + +## Step 3: Update Debian 12 to the latest version + +The following commands bring the server to the latest Debian 12 minor version before the major migration to Debian 13. + +```bash +apt-get update +DEBIAN_FRONTEND=noninteractive apt-get -y -o Dpkg::Options::=--force-confold full-upgrade +cat /etc/debian_version # latest 12.x version +systemctl reboot +``` + +| If… | Do | +| ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | +| `apt-get update` fails on the **MaxScale** line (`NO_PUBKEY`) in `mariadb.list` | Comment **only that line** (the file also holds the MariaDB Server repository) | +| [MySQL] `mysql-apt-config` is upgraded (seen 0.8.36 → 0.8.40) | Nothing: `mysql.list` is kept | + +After the reboot, check that the web interface works and that the pollers are connected. You can update the servers in any order (central server or database server first). + +## Step 4: Upgrade a remote database server (if applicable) + +Do this only if your database runs on its own server, separate from the central. Before you start, make sure Centreon is already stopped on the central server. + +### 4.1 Back up the configuration and stop the database + +Run these commands on the **database server**: + +```bash +B=/root/upgrade-2610-backup; mkdir -p $B/apt-bookworm +cp -a /etc/apt/sources.list /etc/apt/sources.list.d /etc/mysql $B/apt-bookworm/ +systemctl stop mariadb # MySQL: systemctl stop mysql +``` + +This saves your current APT repositories and MySQL/MariaDB configuration, then stops the database. + +### 4.2 Upgrade the server + +1. **Update the repositories:** steps 5.1, 5.2 and 5.3. Here you only need the standard repository and the plugins repository. The `centreon-mariadb` and `centreon-mysql` packages come from the standard repository. +2. **Run the simulation (step 5.4).** You should see: + - `mariadb-server` 11.8, or `mysql-community-server` 8.4.x-1debian13 + - `centreon-mariadb` or `centreon-mysql` at 26.10 + - no `centreon-web`, because it is not installed on this server +3. **Run the upgrade (step 6).** + +### 4.3 Check the result + +```bash +dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' # nothing +cat /etc/debian_version # 13.x +systemctl is-active mariadb # active (MySQL: mysql) +mariadb -e "SELECT @@version, @@read_only" # 11.8.x, 0 (MySQL: 8.4.x, 0) +mariadb-upgrade --check-if-upgrade-is-needed && echo "run: mariadb-upgrade" || echo "done" # MySQL: skip this line +mariadb -e "SHOW DATABASES" | grep -E "^centreon(_storage)?$" # both databases listed +tail -n 5 /var/log/mysql/error.log # MySQL only: "ready for connections. Version: '8.4.x'" +find /etc/mysql -name "*.dpkg-dist" # keep your own file +systemctl enable mariadb && systemctl reboot # MySQL: mysql +``` + +For MySQL, use `mysql` instead of `mariadb` in the commands above. + +### 4.4 Check the connection from the central + +After the reboot, run this on the **central server**, replacing `` with the address of your database server: + +```bash +timeout 3 bash -c '/3306' && echo OK +``` + +It should print `OK`. (This command is used because `nc` is not installed by default.) + +### 4.5 Troubleshooting + +| If you see | What to do | +| --- | --- | +| A file named `50-server.cnf.dpkg-dist` | **Keep your own file** and ignore the new one. The new file sets `bind-address = 127.0.0.1`, which only allows local connections, so the central could no longer reach the database. Your file should have `bind-address = 0.0.0.0` (or the server's IP address) and `utf8mb4`. | +| MariaDB does not start | Run `systemctl start mariadb`, then read the details with `journalctl -u mariadb`. The usual cause is an option in your tuning file that was removed or renamed in the new MariaDB version. | +| `read_only` is 1 | Run `mariadb -e "SET GLOBAL read_only=OFF"`, then delete the `read_only` line from your configuration. That setting is meant for replica servers. | + +## Step 5: Switch the repositories (on every server you upgrade) + +The commands edit your existing repository files (either deb822 *.sources files or one-line *.list files). Do not add a new file next to an old one: the 25.10 and 26.10 repositories would mix. + +```bash +B=/root/upgrade-2610-backup; mkdir -p $B/apt-bookworm +cp -a /etc/apt/sources.list /etc/apt/sources.list.d $B/apt-bookworm/ # rollback +cp -a /etc/apache2/sites-available/centreon.conf $B/apache-centreon.conf.2510 2>/dev/null +ls /etc/apt/sources.list.d/ +``` + +### 5.1 On your Debian OS + +Point APT at the Debian 13 repositories instead of Debian 12. It only edits configuration files, nothing is downloaded or upgraded yet. + +```bash +[ -f /etc/apt/sources.list.d/debian.sources ] && sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/debian.sources +sed -i 's/bookworm/trixie/g' /etc/apt/sources.list +grep -rqs "trixie-backports" /etc/apt/sources.list /etc/apt/sources.list.d/ || \ + echo "deb http://deb.debian.org/debian/ trixie-backports main non-free-firmware" >> /etc/apt/sources.list +``` + +### 5.2 On Centreon + +**5.2 Centreon** (any file name: `centreon-25.10-stable.list`, `centreon-stable.list`, …) + +Point the Centreon repositories at the 26.10 packages for Debian 13. It only edits APT configuration files, nothing is upgraded yet. + +```bash +for f in $(grep -lE "packages.centreon.com|centreon.jfrog.io" /etc/apt/sources.list.d/*.list); do + sed -i -E -e 's/bookworm-25\.10-[a-z-]+/trixie-26.10-stable/g' -e 's/ (bookworm|bullseye) / trixie /g' "$f" + echo "== $f"; cat "$f" +done +grep -qs "apt-plugins-stable/\? trixie" /etc/apt/sources.list.d/*.list || \ + echo "deb https://packages.centreon.com/apt-plugins-stable/ trixie main" > /etc/apt/sources.list.d/centreon-plugins-stable.list +mv centreon-25.10-stable.list centreon-26.10-stable.list +``` + +| Repository line | Required? | +| ---------------------------------------------------------------------------------- | --------------------------------------------------------------------- | +| `apt-standard/ …` | **Yes** | +| `apt-plugins-stable/ trixie` | **Yes**: trixie builds of the Perl libs (Net::Curl, Libssh::Session…) | +| `apt-business/ …` | Only with Business modules (**required on the MBI server**) | +| `apt-plugins-testing/ bookworm` (or `apt-plugins-testing trixie` after the switch) | Optional | +| `centreon.jfrog.io/…/apt-connectors-stable/` | Optional | + +File names keep `25.10`: cosmetic (`mv centreon-25.10-stable.list centreon-26.10-stable.list` if you want). + +### 5.3 On the database server + +Run this on every server that hosts a database: the central server (if the database is local), the remote database server, and the MAP or MBI server. + +Update the database repositories for Debian 13. For MariaDB it also changes the version, from 10.11 to 11.8. It only edits APT configuration files and upgrades nothing yet. + + + + +```bash +for f in /etc/apt/sources.list.d/mariadb.sources /etc/apt/sources.list.d/mariadb.list; do + [ -f "$f" ] || continue + sed -i -e 's|mariadb-server/10.11/|mariadb-server/11.8/|' -e 's/bookworm/trixie/g' "$f" + echo "== $f"; grep -vE "^\s*#|^\s*$" "$f" +done +``` + + + + +```bash +[ -f /etc/apt/sources.list.d/mysql.list ] && sed -i 's/ bookworm / trixie /g' /etc/apt/sources.list.d/mysql.list +echo "mysql-apt-config mysql-apt-config/repo-codename select trixie" | debconf-set-selections +echo "== /etc/apt/sources.list.d/mysql.list"; grep -vE "^\s*#|^\s*$" /etc/apt/sources.list.d/mysql.list +``` + + + + +| If… | Do / know | +| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| No `mariadb.*` file | MariaDB comes from Debian: Debian 13 ships 11.8, nothing to do | +| [MySQL] `mysql.list` points to `mysql-8.0` | **Stop**: `repo.mysql.com` trixie has no 8.0. Upgrade to 8.4 LTS on Debian 12 first (trixie has `mysql-8.4-lts`, `mysql-9.7-lts`, `mysql-innovation`, plus `mysql-apt-config`, `mysql-tools`) | +| [MySQL] debconf line skipped | A later `mysql-apt-config` reconfiguration (`dpkg-reconfigure`, new package version) may write `bookworm` back. With it: kept (checked; prints a harmless `gpg: cannot open '/dev/tty'`) | +| `*.disabled`, `*.old_*` files | Ignored by apt | +| MaxScale line commented in step 3 | Stays commented | + +### 5.4 Check and simulate + +This step is a dry-run check before the real upgrade. It verifies that the repository changes are correct and simulates the upgrade, so you can spot problems while nothing has been modified yet. The comment at the end of each line is the expected result. + +```bash +grep -rn bookworm /etc/apt/sources.list /etc/apt/sources.list.d/ | grep -v ":\s*#" # nothing +apt clean && apt-get update # no W:/E: +apt-get -s full-upgrade > $B/sim.txt +tail -n 3 $B/sim.txt # N upgraded / new / removed +grep -iE "broken|unmet" $B/sim.txt # nothing +grep -E "^Inst (centreon-web|php8.4-fpm|mariadb-server|mysql-community-server) " $B/sim.txt +grep -E "^Remv centreon" $B/sim.txt # nothing +``` + +* If the simulation shows broken packages, stop and restore the sources: `cp -a $B/apt-bookworm/* /etc/apt/`. +* If everything matches the expected results, you can proceed to the real upgrade. If not, fix the repositories first. Nothing has changed on the system at this point, so the check is safe to repeat. + +## Step 6: Upgrade (every server you upgrade) + +This is the real upgrade to Debian 13. It runs the upgrade in the background, in two stages, and then lets you watch its progress. + +```bash +systemd-run --unit=upg2610 /bin/sh -c 'export DEBIAN_FRONTEND=noninteractive; O="-o Dpkg::Options::=--force-confold -o Dpkg::Options::=--force-confdef"; apt-get -y $O upgrade --without-new-pkgs > /root/upgrade-2610-backup/upg-step1.log 2>&1 && apt-get -y $O full-upgrade > /root/upgrade-2610-backup/upg-step2.log 2>&1' +watch -n 10 'pgrep -x apt-get; pgrep -x dpkg; tail -n 2 /root/upgrade-2610-backup/upg-step2.log' # done when both pgrep print nothing +``` + +- Don't interrupt it and don't reboot until it's finished, even if it seems slow (about 1,300 packages). +- Duration: central ~10–15 min, database/MBI server ~6 min, poller ~6 min. +- `systemd-run`: the upgrade survives an SSH disconnection (`openssh-server` is upgraded). +- Wait on the **processes**, not on the unit state (unreliable while systemd itself is upgraded). +- Expected in the logs: `chmod: cannot access '/var/cache/centreon/config/broker/*'` and `…/engine/*`. +- **Do not reboot yet.** + +Then stop Centreon again on the central server. The 26.10 packages restart the services (and cron, if it was upgraded), but the database schema stays at 25.10 until you run the update wizard in step 8. Until then, Gorgone logs `Unknown column 'uid' in 'field list'` / `[legacycmd] Cannot get configuration for pollers` every 15 s. + +```bash +systemctl stop centengine cbd gorgoned centreontrapd cron +systemctl stop centreon-map-engine 2>/dev/null # [MAP] +``` + +## Step 7: Checks after the packages + +### 7.1 Run checks + +This step is the post-upgrade verification (7.1 to 7.4), followed by switching the web stack to PHP 8.4. It checks that the upgrade to Debian 13 went cleanly and that nothing was left half-done. The comment on each line is the expected result. + +```bash +# 7.1 dpkg +dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' # nothing ("rc" = removed, OK) +grep -hE "^(W|E):|dpkg: (error|erreur)" /root/upgrade-2610-backup/upg-step*.log # nothing +cat /etc/debian_version # 13.x +dpkg -l centreon-web centreon-engine centreon-broker centreon-gorgone php8.4-fpm | awk '/^ii/{print $2, $3}' +# 7.2 Perl / libraries left on Debian 12 +dpkg -l | awk '/^ii/ && $3 ~ /deb12/ {print $2, $3}' # only obsolete Debian libs (libperl5.36, perl-modules-5.36…) +perl -MCrypt::OpenSSL::AES -MNet::Curl -MLibssh::Session -e 'print "OK\n"' # OK +# 7.3 Config files kept by --force-confold +find /etc -name "*.dpkg-dist" -o -name "*.ucf-dist" | grep -E "apache2|centreon|php|mysql" +# 7.4 PHP 8.4 +systemctl enable --now php8.4-fpm; systemctl disable --now php8.2-fpm 2>/dev/null +systemctl restart apache2 +curl -s -o /dev/null -w "%{http_code}\n" http://localhost/centreon/ # 200 +``` + +| If… (7.2 / 7.3) | Do | +| ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | +| A Centreon or `lib*-perl` package still `deb12`, or Perl not OK | `apt-get install --reinstall `; check `apt-plugins-stable trixie` (5.2) | +| [MAP] `openjdk-17-jre-headless` still `deb12` | Normal: MAP 26.10 uses Java 25 (`openjdk-25-jre-headless`, now default). After validation: `apt purge openjdk-17-jre-headless` | +| `apache2/…/centreon.conf.dpkg-dist` | **Apache merge** (step 2): 26.10 adds the Gorgone websocket `ProxyPass` block | +| `/etc/centreon-engine/centengine.cfg.dpkg-dist`, `/etc/centreon-broker/central-module.json.dpkg-dist` | Keep yours (generated by the export) | +| `/etc/mysql/mariadb.conf.d/50-server.cnf.dpkg-dist` | Keep yours (package sets `bind-address = 127.0.0.1`) | +| [MAP] `/etc/centreon-map/map-config.properties.dpkg-dist` | Keep yours: it is a template (`%CENTREON_BROKER_ADDRESS%`, `%CENTREON_PWD%`…) | + +### 7.2 Check the database + +If you have a local database, run this on the central server. If your database is on a separate server, run this on that server, not on the central. + +This step is the database health check after the upgrade. It confirms that the new MariaDB 11.8 is running, writable, upgraded internally, and that the Centreon databases are still there. The comments give the expected result, with the MySQL variant after the dash. + +```bash +systemctl is-active mariadb # active — [MySQL] mysql +mariadb -e "SELECT @@version, @@read_only" # 11.8.x, 0 — [MySQL] 8.4.x, 0 +mariadb-upgrade --check-if-upgrade-is-needed && echo "run: mariadb-upgrade" || echo "done" # [MySQL] skip +mariadb -e "SHOW DATABASES" | grep -E "^centreon(_storage|_map)?$" +journalctl -u mariadb --since "-1h" | grep -iE "error|warning" | tail -n 20 # [MySQL] tail /var/log/mysql/error.log +``` + +* If MariaDB isn't active, or the version query shows read_only = 1 (the database refuses writes), use [the troubleshooting table from step 4](#troubleshooting). +* If the check prints "run: mariadb-upgrade", run mariadb-upgrade. It takes its login details from /root/.my.cnf. When it works, it finishes with return code 0 after 8 phases, and running the check again reports that no upgrade is needed. + Why this happens: the MariaDB package normally updates the database's internal system tables during the upgrade. It can't do this if the MariaDB root account has a password, and it won't warn you. MariaDB 11.8 then runs on system tables still in the 10.11 format. If root logs in through unix_socket (no password), the package does it by itself, as it did on the database servers we tested. + +## Step 8: Finalize the upgrade on the central server + +### 8.1 On the web interface + +First, clear your browser cache so you don't see old pages from 25.10. (If you use MAP, its documentation has the same step.) + +1. Run the update wizard to 26.10. Click Finish only once. + The wizard log may show `Undefined array key "is_reverse"` in `Update-25.11.0.php`. If you use the Centreon Monitoring Agent, check the connection mode of each agent configuration. It should be set to "agent initiated", which is the default. +2. Update the modules in **Administration > Extensions > Manager**. Update them one at a time, and wait for each to finish before starting the next. + * If you use MAP, update both the MAP module and the MAP widget. They have separate buttons. + * Avoid **Update all**. On both test platforms, it left auto-discovery not updated until a second request. If you use it anyway, check that auto-discovery shows version 26.10. +3. Apply the updates in the Monitoring Connector Manager. + +### 8.2 On the central server + +To restart Centreon on the new version, run these commands on the central server: + +```bash +cd /usr/share/centreon && sudo -u www-data php bin/console cache:clear +usermod -a -G centreon-broker www-data +usermod -a -G www-data centreon-broker +sudo -u www-data php /usr/share/centreon/bin/console w:m:c --dry-run # "No invalid commands found." +systemctl restart cbd centengine gorgoned centreontrapd +systemctl start centreon-map-engine # [MAP] +``` + +What these commands do: + +* Clear the web application cache. +* Let the web server and Broker access each other's files. +* Check for invalid Engine and Broker commands. If the check lists any, run it again without **--dry-run** to remove them. (`w:m:c` is short for `web:monitoring-server:clean-engine-broker-command`.) +* Restart the monitoring services, and start the MAP engine if you use MAP. + +If you use MAP, check that it works: + +* `systemctl is-active centreon-map-engine` should print `active`. +* Run `for p in $(pgrep -x java); do readlink -f /proc/$p/exe; done`. The result should contain `java-25-openjdk`. +* Run `grep -E "ERROR|Connection with Broker established" /var/log/centreon-map/centreon-map-engine.log | tail -n 5`. You should see that the connection with Broker is established. A few `Error while connecting to Broker` messages are normal while Broker restarts. + +### 8.3 Export the configuration from the web interface + +1. Export the central server's configuration with **Generate**, **Move export files** and **Restart all** checked. If you skip **Move export files**, the new files stay in `/var/cache/centreon/config` and Engine 26.10 keeps using the old configuration. + +2. Restart the services one last time + + ```bash + systemctl restart cbd centengine centreontrapd gorgoned + systemctl start cron + ``` + + This makes the services load the new configuration and turns scheduled jobs (cron) back on. + +## Step 9: Make sure everything starts at boot, then reboot + +1. Run these commands on the central server: + + ```bash + systemctl enable centengine cbd gorgoned centreontrapd snmptrapd.socket php8.4-fpm apache2 cron + systemctl enable centreon-map-engine 2>/dev/null # [MAP] + systemctl enable mariadb # [local DB] or local MAP DB — [MySQL] mysql + diff <(awk '{print $1}' /root/upgrade-2610-backup/enabled-units.txt | sort) \ + <(systemctl list-unit-files --state=enabled | awk '{print $1}' | sort) # php8.2 → php8.4 expected + systemctl reboot + ``` + + What these commands do: + + * Make sure all Centreon services, the web server, PHP 8.4, cron and the database start automatically at boot. + * Compare the list of services enabled before the upgrade (saved in step 1.2) with the current list. The only expected difference is php8.2-fpm replaced by php8.4-fpm. Anything else deserves a look. + * Reboot the server. + +2. After the reboot, check that everything works: + +```bash +uname -r # 6.12.x +systemctl --failed # 0 units +for u in centengine cbd gorgoned centreontrapd php8.4-fpm apache2 mariadb centreon-map-engine cron; do printf "%s=%s " $u $(systemctl is-active $u); done; echo +ls /etc/cron.d/ # centreon, centstorage +ss -ulnp | grep ":162 " # SNMP traps: UDP 162 held by systemd +logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" # nothing (else table below) +systemctl is-active centreontrapd # active (see the table below) +``` + +What you should see: + +* The kernel version starts with 6.12. +* No failed services. +* Each service reports active. +* The Centreon cron files (centreon, centstorage) are in /etc/cron.d/. +* Port UDP 162, used for SNMP traps, is held by systemd. + +| What you see | What it means and what to do | +| -------------------------------------------- | ------------------------------------------------------------------------------------ | +| `snmptrapd` is inactive | Normal on Debian 13. It starts on demand when the first trap arrives. | +| `centreontrapd` is inactive, with exit **0/SUCCESS** | The trap database is empty. See step 10, centreontrapd. | +| `cron` is inactive | Run `systemctl enable --now cron` (See step 1.4.) | +| `logrotate.service` failed (`Ignoring cbd` / `centengine`) | `chmod 644 /etc/logrotate.d/cbd /etc/logrotate.d/centengine`; `systemctl start logrotate` | + +Finally, check the web interface: + +* **Configuration > Pollers**: all pollers are running and were updated recently. There should be no duplicate **Central** entry. (The 26.10 Broker registers the central under a new instance ID, so a duplicate can appear.) +* **Resources Status**: force a check, acknowledge a problem and set a downtime, to confirm they work. +* Graphs are drawn. +* Gorgone is connected. + +## Step 10: Upgrade the pollers (after the central) + +Allow about 6 minutes per poller. Do each poller one at a time. + +1. Back up and update Debian 12. Do the system part of step 1.2, then step 3 (Debian 12 point release and reboot). +2. Stop the monitoring services: + + ```bash + systemctl stop centengine gorgoned centreontrapd + ``` + +3. Upgrade to Debian 13 and Centreon 26.10. Do steps 5.1 and 5.2 (APT repositories, standard and plugins), then step 5.4 and step 6. + After step 5.4, you should see `centreon-poller`, `centreon-engine`, `centreon-broker` and `centreon-gorgone` at 26.10.0, plugins built for `deb13`, and no package removed. +4. Check the result. Do steps 7.1 and 7.2. If `centengine.cfg.dpkg-dist` exists, keep your own file. +5. Reboot, then export the poller's configuration from the central server, with **Generate**, **Move export files** and **Restart** all checked. +6. Check that everything works: + + ```bash + systemctl --failed # 0 units + systemctl is-active centengine gorgoned centreontrapd # all active + grep -E "Centreon Engine 26.10|Configuration loaded" /var/log/centreon-engine/centengine.log | tail -n 2 + ss -tn | grep -E ":5669|:5556" # Broker (5669) and Gorgone (5556) connected to the central + ls -l /etc/snmp/centreon_traps/centreontrapd.sdb # file is not empty + logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" # nothing (else 1.4) + ``` + +### If `centreontrapd` stops by itself + +If the trap database `centreontrapd.sdb` is empty, `centreontrapd` stops one second after it starts. In `/var/log/centreon/centreontrapd.log`, you will see `MySQL error: no such table: cfg_nagios`. systemd reports `inactive (dead)` with status **0/SUCCESS**, so there is no alert, and **no SNMP trap is processed**. + +To fix it: + +1. In the web interface, go to **Configuration > SNMP Traps > Generate**. +2. Select the poller. +3. Check **Generate traps database**, **Apply configurations** and **Restart centreontrapd**. + +The upgrade does not cause this problem. It was also seen on 25.10 after a simple reboot. + +### What to expect + +- Acknowledgements and downtimes survive the poller upgrade, thanks to retention. +- The `downtimes` history gets a new row when Engine restarts. This is normal. + +## Step 11: Upgrade your MBI server (if applicable) + +The central server needs nothing extra. `centreon-bi-server` is upgraded in step 6, and the MBI module and widgets are updated in step 8. + +On the reporting server, make sure no ETL run is in progress: check with `ps -ef | grep -i etl` that none is in progress. + +### 11.1 Before the upgrade + +1. **Back up the server:** + + ```bash + B=/root/upgrade-2610-backup; mkdir -p $B + tar czf $B/etc-$(hostname).tar.gz -C / etc; dpkg -l > $B/dpkg-l.txt + systemctl list-unit-files --state=enabled > $B/enabled-units.txt + ``` + + Also back up the reporting database, as described on the MBI page [Backing up and restoring MBI](../reporting/backup-restore.md). + +2. **Make sure cron is installed** (see step 1.4). + + ```bash + dpkg -l cron | grep -q "^ii" || apt-get install -y cron + ``` + +3. **Stop the services:** + + ```bash + systemctl stop cbis gorgoned cron + ``` + +### 11.2 Upgrade + +1. Do step 3 (Debian 12 point release and reboot), if not already done. +2. Do steps 5.1 and 5.2 (standard, **business** and plugins repositories), then step 5.3 (MariaDB or MySQL repository). +3. Do step 5.4, then step 6. In the simulation, you should see `centreon-bi-reporting-server`, `centreon-bi-engine`, `centreon-bi-etl` and `centreon-bi-report` at 26.10.0, plus `openjdk-25-jdk`. No package should be removed. + +### 11.3 Check and restart + +```bash +dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' # nothing +dpkg -l "centreon-bi*" | awk '/^ii/{print $2, $3}' # 26.10.0 +java -version 2>&1 | head -n 1 # openjdk 25 +grep ExecStart /lib/systemd/system/cbis.service | grep -o "java-[0-9]*-openjdk" # java-25-openjdk +find /etc -name "*.dpkg-dist" | grep -E "centreon|mysql" # keep yours (bind-address) +systemctl is-active mariadb # local reporting DB (MySQL: mysql) +systemctl start cbis; systemctl enable --now gorgoned cron +systemctl is-active cbis gorgoned cron # all active +ls /etc/cron.d/ | grep centreon-bi # engine, purge, backup-reporting-server +tail -n 20 /var/log/centreon-bi/cbis.$(date +%F).log # no "Connection test … failed" +``` + +Then reboot and check again that `cbis`, `gorgoned` and `cron` are active. After 07:30 on the next weekday, `/var/log/centreon-bi/centreonBIETL.log` should show the ETL run. + +### Good to know + +- **Java 25, not 17.** MBI 26.10 uses Java 25. `centreon-bi-engine` pulls in `openjdk-25-jdk`, and `cbis.service` runs `/usr/lib/jvm/java-25-openjdk-amd64/bin/java` directly. The Java 17 left over from Debian 12 is unused. After validation, remove it with `apt purge openjdk-17-*`. + +## Known issues + +Here is the table without the Ticket column: + +| When | You see | Do | +| --- | --- | --- | +| MBI server | Nothing: ETL, purge, backup never run (`cron` absent) | 1.4: install/enable `cron`; check `centreonBIETL.log` next weekday | +| Reboot (central, poller) | `centreontrapd` inactive, exit 0, `no such table: cfg_nagios` | Generate the SNMP traps database, restart centreontrapd | +| Any server, after the upgrade | `logrotate.service` failed, `Ignoring cbd … writable by group or others`; or no logrotate at all (25.10) | 1.4: install logrotate, `chmod 644` cbd/centengine | +| Step 2 | dpkg error, `chmod … .ssh/id_rsa` | `dpkg --configure -a`, all `ii` | +| Steps 2, 8 (extensions) | `cache:clear` error, `Cannot rename` / `Failed to read file …/symfon_` | One module at a time; `cache:clear` alone; check versions | +| Step 8 (_Update all_) | auto-discovery still on 25.10 after the batch | Update it again, check 26.10 | +| Steps 2, 8 (wizard) | Last step sent twice, HTTP 500 | Click Finish once; update done anyway | +| Step 8 (wizard log) | `Undefined array key "is_reverse"` in `Update-25.11.0.php` | Check Monitoring Agent connection modes | +| Export | `auto_reschedule_checks is no longer available` | Warning only | +| Steps 2, 6 (package logs) | `chmod: cannot access '/var/cache/centreon/config/broker/*'` | Harmless | +| 25.10 pollers | Ack closed in history when the service enters a downtime | Pollers on latest 25.10 first; upgrade them soon | +| MBI doc | Java 17 required, no Debian 13 tab, no cron | Follow section 11 | +| Official doc | No Debian 12 → 13 path for 25.10 → 26.10 | This document | +| Step 6 → 8 | Gorgone `Unknown column 'uid'` every 15 s | Stop Centreon again after step 6 | +| Steps 2, 7 (custom Apache) | `centreon.conf.dpkg-dist`, new vhost not applied | Apache merge | +| 4b, 7.3, 11 | `50-server.cnf.dpkg-dist` with `bind-address = 127.0.0.1` | Keep yours | +| Step 7.2 | Plugins / Gorgone cannot load a Perl module | Reinstall from trixie; `apt-plugins-stable trixie` | +| Step 8 export | Engine still on the old config | Export again with **Move** checked | +| Step 9 | `snmptrapd` inactive | Normal (socket-activated) | +| MariaDB 11.8 tools | `mysql: Deprecated program name …` | Cosmetic; use `mariadb` | +| 4b, 7.5 (MariaDB root with a password) | `mariadb-upgrade --check-if-upgrade-is-needed` → needed after the upgrade, nothing logged | Run `mariadb-upgrade` yourself | +| Step 3 | `NO_PUBKEY` on the MaxScale line | Comment only that line | + +## MariaDB/MySQL equivalents + +| Item | MariaDB | MySQL (Oracle `repo.mysql.com`) | +| ---------------- | ----------------------------------------------------- | ---------------------------------- | +| Service, client | `mariadb` | `mysql` | +| Dump | `mysqldump` / `mariadb-dump` | `mysqldump` | +| Centreon package | `centreon-mariadb` | `centreon-mysql` | +| Repository file | `mariadb.sources` or `mariadb.list` | `mysql.list` + `mysql-apt-config` | +| Version | 10.11 → **11.8** (major) | **8.4 → 8.4** LTS, Debian 13 build | +| Data upgrade | `mariadb-upgrade`, run by the package | automatic at server start | +| Root access | `sudo mariadb` if `unix_socket`, else `/root/.my.cnf` | `/root/.my.cnf` | +| Config dir | `/etc/mysql/mariadb.conf.d/` | `/etc/mysql/mysql.conf.d/` | diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md index 1ec01f0aa0d0..263402b8a358 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.04.md @@ -5,6 +5,7 @@ description: "Upgrade a Centreon HA cluster from version 23.04 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Link from '@docusaurus/Link'; This chapter describes how to upgrade your Centreon HA platform from version 23.04 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md index 96001126c49a..cafe67e31557 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-23.10.md @@ -5,6 +5,7 @@ description: "Upgrade a Centreon HA cluster from version 23.10 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Link from '@docusaurus/Link'; This chapter describes how to upgrade your Centreon HA platform from version 23.10 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md index cf9d1c16be69..3b840b35f547 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-04.md @@ -5,6 +5,7 @@ description: "Upgrade a Centreon HA cluster from version 24.04 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Link from '@docusaurus/Link'; This chapter describes how to upgrade your Centreon HA platform from version 24.04 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md index de9e34557e9f..cc63b5694b84 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-24-10.md @@ -5,6 +5,7 @@ description: "Upgrade a Centreon HA cluster from version 24.10 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Link from '@docusaurus/Link'; This chapter describes how to upgrade your Centreon HA platform from version 24.10 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. diff --git a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md index adacb9c04a87..5bae64fa35bd 100644 --- a/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md +++ b/versioned_docs/version-26.10/upgrade/centreon-ha/upgrade-from-25-10.md @@ -5,6 +5,7 @@ description: "Upgrade a Centreon HA cluster from version 25.10 to 26.10" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import Link from '@docusaurus/Link'; This chapter describes how to upgrade your Centreon HA platform from version 25.10 to version 26.10. Please refer to the [upgrade matrix](../upgrade-matrix.mdx) to know whether your OS is still supported. If not, you will need to migrate your platform: contact your Centreon sales representative to discuss any migration with HA. From 7ec27539a063d4ab69e5720d79a26286de5887e1 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 6 Oct 2026 15:48:05 +0200 Subject: [PATCH 109/179] Add in-place migration topic to sidebar --- versioned_sidebars/version-26.10-sidebars.json | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/versioned_sidebars/version-26.10-sidebars.json b/versioned_sidebars/version-26.10-sidebars.json index 82761c22ba45..dc092337dcc0 100644 --- a/versioned_sidebars/version-26.10-sidebars.json +++ b/versioned_sidebars/version-26.10-sidebars.json @@ -1254,6 +1254,10 @@ { "type": "doc", "id": "migrate/migrate-from-debian-to-debian" + }, + { + "type": "doc", + "id": "migrate/upgrade-debian-in-place" } ] } From a5a9fe150536d9dd048dc0765965f256c837bb24 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 6 Oct 2026 15:57:32 +0200 Subject: [PATCH 110/179] Fix link --- versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md b/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md index 5dfc15fd18fd..a9e3011d727a 100644 --- a/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md +++ b/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md @@ -95,7 +95,7 @@ logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" # nothing ## Step 2: Update your Centreon version to the latest minor -Follow the update procedures for your version ([24.04](https://archives-docs.centreon.com/24.04/docs/update/update-centreon-platform/), [24.10](../../version-24.10/update/update-centreon-platform.md) or [25.10](../update/update-centreon-platform.md)). Update your central server, your pollers and your remote servers. +Follow the update procedures for your version ([24.04](https://archives-docs.centreon.com/24.04/docs/update/update-centreon-platform/), [24.10](https://docs.centreon.com/docs/24.10/update/update-centreon-platform/) or [25.10](../update/update-centreon-platform.md)). Update your central server, your pollers and your remote servers. - -## Étape 1 : Créer les répertoires de sortie - -Créez des dossiers pour organiser les fichiers : un pour les fichiers propres à l'autorité de certification, un pour les fichiers destinés au service web ou au service de base de données. - -Pour l'autorité de certification : - -```shell -sudo mkdir -p /out/CA -``` - -Pour le serveur central/distant, ou pour la base de données : - - - - -```shell -sudo mkdir -p /out/web -``` - - - - -```shell -sudo mkdir -p /out/db -``` - - - - -## Étape 2 : Générer la clé privée de l'autorité de certification racine (RSA 4096 bits) - -Il s'agit de la clé secrète de votre autorité de certification. La commande **chmod 400** limite l'accès au fichier : seul son propriétaire peut le lire (et personne ne peut y écrire). L'exposition de la clé est ainsi réduite au minimum. - -```shell -sudo openssl genrsa -out /out/CA/rootCA.key 4096 -sudo chmod 400 /out/CA/rootCA.key -``` - -## Étape 3 : Générer le certificat auto-signé de l'autorité de certification racine (10 ans) - -Créez maintenant le certificat de l'autorité de certification. Ce document public identifie votre autorité de certification (nom, organisation, etc.). Vous le distribuerez ensuite à tous les clients et serveurs qui doivent faire confiance aux certificats qu'elle signe. - -Ce certificat est « auto-signé », car aucune autorité ne se trouve au-dessus de lui : l'autorité de certification se porte garante d'elle-même. C'est un fonctionnement normal pour une autorité de certification racine. - -* `-x509` indique à OpenSSL de produire directement un certificat (et non une demande de signature). -* `-days 3650` fixe l'expiration à environ 10 ans. Cette durée est habituelle pour une autorité de certification racine, qui n'a pas vocation à être renouvelée souvent. -* `-subj` définit les champs d'identité directement dans la ligne de commande : CN (Common Name) vaut « Test Dev CA », O (Organization) vaut « YourOrganization » et OU (Organizational Unit) vaut « R&D ». Remplacez ces valeurs par celles de votre organisation. - -```shell -sudo openssl req -x509 -new -nodes -key /out/CA/rootCA.key \ - -sha256 -days 3650 \ - -subj "/CN=Test Dev CA/O=YourOrganization/OU=R&D" \ - -out /out/CA/rootCA.pem -``` - -## Étape 4 : Générer la clé privée du serveur final (RSA 2048 bits) - -Il s'agit de la clé privée du serveur lui-même (le serveur central/distant ou la base de données). Elle est distincte de la clé de l'autorité de certification : le serveur ne doit jamais partager une clé avec l'autorité de certification. - - - - -```shell -sudo openssl genrsa -out /out/web/server-key.pem 2048 -``` - - - - -```shell -sudo openssl genrsa -out /out/db/server-key.pem 2048 -``` - - - - -## Étape 5 : Créer le fichier de configuration des extensions OpenSSL pour les SAN - -Les navigateurs et clients récents exigent qu'un certificat liste tous les noms d'hôte et adresses IP pour lesquels il est valide : c'est la liste SAN (Subject Alternative Name). Un CN seul ne suffit plus pour être considéré comme fiable. Cette étape crée un petit fichier de configuration qui définit : - -* `basicConstraints = CA:FALSE` : ce certificat n'est pas autorisé à signer d'autres certificats (seule l'autorité de certification racine le peut). -* `keyUsage / extendedKeyUsage` : limite le certificat à son usage prévu, c'est-à-dire l'authentification d'un serveur TLS. -* `subjectAltName` : la liste des noms et adresses IP pour lesquels le certificat doit être valide. Ici : web, localhost, db et l'adresse IP 127.0.0.1. Modifiez cette liste pour qu'elle corresponde aux noms d'hôte réels par lesquels votre serveur sera joint. - -```shell -sudo tee /out/cert.ext > /dev/null < - - -```shell -sudo openssl req -new -key /out/web/server-key.pem -out /out/web/server.csr \ - -subj "/CN=web/O=Centreon" -``` - - - - -```shell -sudo openssl req -new -key /out/db/server-key.pem -out /out/db/server.csr \ - -subj "/CN=db/O=Centreon" -``` - - -     - -## Étape 7 : Signer le certificat final avec l'autorité de certification racine (validité de 397 jours) - -C'est cette étape qui produit le certificat serveur utilisable : l'autorité de certification (son certificat et sa clé privée, créés aux étapes 2 et 3) signe la CSR de l'étape 6, en appliquant les extensions et les SAN définis à l'étape 5. - -* `-days 397` : 397 jours est la durée de vie maximale actuellement acceptée par les principaux navigateurs (Apple, Google, Mozilla) pour les certificats de serveur TLS. Au-delà, les clients risquent de rejeter le certificat. -* `-CAcreateserial` : crée, lors de la première exécution, un fichier de suivi des numéros de série (rootCA.srl), puis l'incrémente à chaque nouvelle signature. Chaque certificat émis par cette autorité de certification reçoit ainsi un numéro de série unique. - - - - - - -```shell -sudo openssl x509 -req -in /out/web/server.csr \ - -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ - -CAserial /out/CA/rootCA.srl -CAcreateserial \ - -out /out/web/server.pem -days 397 -sha256 \ - -extfile /out/cert.ext -extensions v3_req -``` - - - - -```shell -sudo openssl x509 -req -in /out/db/server.csr \ - -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ - -CAserial /out/CA/rootCA.srl -CAcreateserial \ - -out /out/db/server.pem -days 397 -sha256 \ - -extfile /out/cert.ext -extensions v3_req -``` - - - - -## Étape 8 : Définir les permissions - -Les permissions suivent ici le principe du moindre privilège : - -* `0644` (lecture pour tous, écriture pour le propriétaire uniquement) pour les certificats publics : ils ne contiennent aucun secret. -* `0640` (lecture pour le propriétaire et le groupe, aucun accès pour les autres) pour la clé privée du serveur. Cette clé est sensible, mais un service exécuté sous un groupe spécifique aura probablement besoin de la lire. - -Pour l'autorité de certification racine : - -```shell -sudo chmod 0644 /out/CA/rootCA.pem -``` - -Pour le serveur central/distant : - -```shell -sudo chmod 0644 /out/web/server.pem -sudo chmod 0640 /out/web/server-key.pem -``` - -Pour la base de données : - -```shell -sudo chmod 0644 /out/db/server.pem -sudo chmod 0640 /out/db/server-key.pem -``` - -Les 3 fichiers nécessaires se trouvent maintenant dans votre dossier **/out**. Vous pouvez les copier aux emplacements appropriés sur vos serveurs (et les renommer si besoin). - - - - - - diff --git a/centreon-os-support-vs-26-10.md b/centreon-os-support-vs-26-10.md deleted file mode 100644 index 363ecd08fd57..000000000000 --- a/centreon-os-support-vs-26-10.md +++ /dev/null @@ -1,62 +0,0 @@ -# Centreon — Versions et systèmes d'exploitation supportés - -> Document généré à partir de la documentation officielle Centreon (dépôt `centreon-documentation` -> pour les versions 24.10 à 26.10, et des sites d'archives pour les versions antérieures). -> Date de génération : 2026-07-03. - -## Cycle de vie des versions - -Source : `versioned_docs/version-26.10/releases/lifecycle.md` - -| Version Centreon | Sortie | Fin de support | État | -|-------------------|---------|-----------------|----------------------| -| 26.10 | 10/2026 | 04/2029 | Supportée | -| 25.10 | 10/2025 | 04/2027 | Supportée | -| 24.10 | 10/2024 | 10/2027 | Supportée | -| 24.04 | 04/2024 | 04/2026 | Plus supportée | -| 23.10 | 10/2023 | 10/2025 | Plus supportée | -| 23.04 | 04/2023 | 04/2025 | Plus supportée | -| 22.10 | 10/2022 | 10/2024 | Plus supportée | -| 22.04 | 05/2022 | 05/2024 | Plus supportée | -| 21.10 | 11/2021 | 11/2023 | Plus supportée | -| 21.04 | 04/2021 | 10/2022 | Plus supportée | -| 20.10 | 10/2020 | 05/2022 | Plus supportée | -| 20.04 | 04/2020 | 10/2021 | Plus supportée | -| 19.10 | 10/2019 | 04/2021 | Plus supportée | -| 19.04 | 04/2019 | 10/2020 | Plus supportée | -| 18.10 | 10/2018 | 04/2020 | Plus supportée | - -## Systèmes d'exploitation supportés par version - -Rappel — OS supportés par la version actuelle **Centreon 26.10** : RHEL/Oracle Linux/Alma Linux 9, RHEL/Oracle Linux/Alma Linux 10, Debian 13 (trixie). - -| Version Centreon | OS supportés à l'époque | Parmi eux, toujours supportés en 26.10 | -|-------------------|--------------------------|------------------------------------------| -| **26.10** | RHEL/Oracle Linux/Alma Linux 9 & 10 (RPM, sources) • Debian 13 "trixie" (DEB) | RHEL/Oracle/Alma Linux 9, RHEL/Oracle/Alma Linux 10, Debian 13 (version actuelle) | -| **25.10** | RHEL/Oracle Linux 8 (RPM, sources) • Alma Linux 8 (RPM, VM, sources) • RHEL/Oracle/Alma Linux 9 (RPM, sources) • Debian 12 "bookworm" (DEB) | RHEL/Oracle/Alma Linux 9 | -| **24.10** | RHEL/Oracle Linux 8 (RPM, sources) • Alma Linux 8 (RPM, VM, sources) • RHEL/Oracle/Alma Linux 9 (RPM, sources) • Debian 12 "bookworm" (DEB) | RHEL/Oracle/Alma Linux 9 | -| **24.04** | RHEL/Oracle Linux 8 (RPM, sources) • Alma Linux 8 (RPM, VM, sources) • RHEL/Oracle/Alma Linux 9 (RPM, sources) • Debian 11 "bullseye" (DEB) • Debian 12 "bookworm" (DEB) | RHEL/Oracle/Alma Linux 9 | -| **23.10** | RHEL/Oracle Linux 8 (RPM, sources) • AlmaLinux 8 (RPM, VM, sources) • RHEL/Oracle/AlmaLinux 9 (RPM, sources) • Debian 11 (DEB) | RHEL/Oracle/AlmaLinux 9 | -| **23.04** | RHEL/Oracle Linux 8 (RPM, sources) • AlmaLinux 8 (RPM, VM, sources) • RHEL/Oracle/AlmaLinux 9 (RPM, sources) • Debian 11 (DEB) | RHEL/Oracle/AlmaLinux 9 | -| **22.10** | CentOS 7 (RPM, VM, sources) • RHEL/Oracle Linux 7 (RPM, sources) • RHEL/Oracle Linux 8 (RPM, sources) • AlmaLinux 8 (RPM, VM, sources) • Debian 11 (DEB) — *CentOS/RHEL 7 déconseillés* | Aucun | -| **22.04** | Non trouvé (page d'archive inaccessible, erreur HTTP 403) | N/A | -| **21.10** | CentOS 7 (ISO, RPM, VM, sources) • RHEL/Oracle Linux 7 (RPM, sources) • RHEL/Oracle Linux 8 (RPM, sources) | Aucun | -| **21.04** | CentOS 7 (ISO, RPM, VM, sources) • RHEL/Oracle Linux 7 ou 8 (RPM, sources) | Aucun | -| **20.10** | CentOS 7 (RPM) • RHEL 7/8 (RPM) • Oracle Linux 7/8 (RPM) | Aucun | -| **20.04** | CentOS 7 (ISO) • RHEL 7 (RPM) | Aucun | -| **19.10** | Non trouvé | N/A | -| **19.04** | Non trouvé | N/A | -| **18.10** | Non trouvé | N/A | - -### Notes - -- Sur toutes les versions où l'information est disponible : seules les architectures **64 bits (x86_64)** sont supportées. -- Les utilisateurs Open Source sans contrat de support peuvent utiliser une autre distribution GNU/Linux en installant depuis les sources, mais les modules IT Edition / Business Edition ne fonctionnent pas sur les distributions non supportées. -- Pour **22.04**, la page d'archive (`archives-docs.centreon.com/22.04/`) a renvoyé une erreur 403 lors de la consultation — non vérifiable. -- Pour **18.10 / 19.04 / 19.10**, la plateforme d'archives (`docs-older.centreon.com`) est dépréciée et ne fournit pas de page dédiée par version pour ces informations — volontairement laissées vides plutôt que devinées. -- À partir de la version 22.10 incluse et en amont, plus aucun OS de l'époque n'est encore supporté en 26.10 (CentOS 7 et RHEL/Oracle/Alma Linux 7-8 sont tous en fin de vie côté Centreon). Seule la lignée « Enterprise Linux 9 » (RHEL/Oracle Linux/AlmaLinux 9), apparue à partir de 22.10, perdure jusqu'en 26.10. - -### Sources - -- Dépôt local (versions 24.10 à 26.10) : `versioned_docs/version-{24.10,25.10,26.10}/installation/compatibility.md` et `versioned_docs/version-26.10/releases/lifecycle.md` -- Archives (versions 20.04 à 24.04) : `https://archives-docs.centreon.com/{version}/docs/installation/compatibility` (ou `.../installation/prerequisites` pour 20.x et 21.x) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md.bak b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md.bak deleted file mode 100644 index fccd85b2e43c..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md.bak +++ /dev/null @@ -1,285 +0,0 @@ ---- -id: migrate-from-el-to-el -title: Migrer depuis un OS de type EL vers un autre OS de type EL (depuis un Centreon 18.10 ou plus récent) -description: "Migrer une plateforme Centreon entre deux OS de type EL" ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -## Prérequis - -Cette procédure ne s'applique que dans les conditions suivantes : - -- Vous souhaitez migrer d'un OS de type EL 64-bits vers un autre OS de type EL 64-bits supporté. Par exemple, vous souhaitez migrer d'un CentOS 7 à un Alma 9. -- Votre version de Centreon est 18.10 ou plus récente. - -Tous les serveurs de votre architecture (serveur central, serveurs distants et collecteurs) doivent avoir la même version majeure de Centreon. Il est également recommandé d'avoir la même version mineure. - -> Si vous utilisez la HA sur votre plateforme, contactez votre représentant commercial Centreon pour discuter des scénarios de migration possibles. - -Avant toute chose, effectuez une sauvegarde de l’ensemble des serveurs de votre plateforme : - -- Serveur Centreon central, -- Serveur de gestion de base de données. - -Si vous utilisez un fournisseur Open Ticket avec des configurations personnalisées, [sauvegardez-les avant de mettre à jour Centreon](../alerts-notifications/ticketing-install.md#sauvegarder-votre-configuration-personnalisée-de-fournisseur-openticket). - -## Migrer une plateforme - -### Étape 1 : Installer le nouveau serveur central - -1. Installez votre nouvel OS: voir la liste des [OS supportés](../installation/compatibility.md#système-dexploitation). - -2. Installez un nouveau serveur central Centreon à partir des [paquets](../installation/installation-of-a-central-server/using-packages.md) - jusqu'à terminer le processus d'installation en vous connectant à l'interface web. - - > Pendant le processus d'installation web, utilisez le même mot de passe pour l'utilisateur **centreon** que sur l'ancienne plateforme. - -3. Réalisez les mises à jour logicielle et système : - - - - -```shell -dnf update -``` - - - - -### Étape 2 : Synchroniser les données - -1. Connectez-vous à votre ancien serveur Centreon. - -2. Générez une paire de clés ssh pour **root** : - - ```shell - ssh-keygen -t rsa - ``` - - Par défaut, la paire de clés générée sera **/root/.ssh/id_rsa.pub** et **/root/.ssh/id_rsa**. - -3. Copiez la clé publique de **root** (**/root/.ssh/id_rsa.pub**) dans le fichier **/root/.ssh/authorized_keys** du nouveau serveur. Si vous n'utilisez pas le compte **root** pour la synchronisation, assurez-vous que votre utilisateur dispose de droits d'écriture sur le dossier cible. - -4. Depuis l'ancien serveur, synchronisez les répertoires suivants vers le nouveau serveur : - - ```shell - rsync -avz /etc/centreon root@\:/etc - rsync -avz /etc/centreon-broker root@\:/etc - rsync -avz /var/log/centreon-engine/archives/ root@\:/var/log/centreon-engine - rsync -avz --exclude centcore/ --exclude log/ /var/lib/centreon root@\:/var/lib - rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img - ``` - - Si vous avez personnalisé le nom de votre fichier de clé privée, utilisez le format suivant (remplacez **id_rsa_custom** par le nom de votre fichier, et `` par les commandes ci-dessus): - - ```shell - rsync -avz -e "ssh -i /root/.ssh/id_rsa_custom" - ``` - - > Remplacez **\** par l'adresse IP de votre nouveau serveur Centreon. - -### Étape 3 : Récupérer les bases de données - ->Si vous utilisez une base de données distante, ignorez cette étape et passez directement à l'[étape 4](#étape-4--synchroniser-les-plugins). - -1. Sur l'ancien serveur, faitez un dump des bases de données : - - ```shell - mysqldump -u root -p centreon > /tmp/centreon.sql - mysqldump -u root -p centreon_storage > /tmp/centreon_storage.sql - ``` - -2. Sur l'ancien serveur, arrêtez MariaDB : - - ```shell - systemctl stop mariadb - ``` - -3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): - - ```shell - rsync -avz /tmp/centreon.sql root@\:/tmp/ - rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ - ``` - -4. Sur le nouveau serveur de base de données, supprimez les bases de - données vierges et recréez-les : - - ```shell - mysql -u root -p - ``` - - ```SQL - DROP DATABASE centreon; - DROP DATABASE centreon_storage; - CREATE DATABASE centreon; - CREATE DATABASE centreon_storage; - ``` - -5. Sur le nouveau serveur de bases de données, importez dans la base les dumps précédemment transférés : - - ```shell - mysql -u root centreon -p -p - ``` - - Exemple : si votre utilisateur_admin_bdd est `root`, entrez: - - ```shell - mysql_upgrade -u root -p - ``` - -7. Démarrez le processus **mariadb** sur le nouveau serveur : - - ```shell - systemctl start mariadb - ``` - -> Remplacez **\** par l'adresse IP de votre nouveau serveur -> Centreon. - -### Étape 4 : Synchroniser les plugins - -Si vous n'utilisez que des plugins Centreon, réinstallez-les sur le nouveau serveur: - - - - -```shell -dnf install centreon-plugin-\* -``` - - - - -```shell -dnf install centreon-plugin-\* -``` - - - - -```shell -apt install centreon-plugin-\* -``` - - - - -Si vous utilisez vos propres plugins personnalisés, synchronisez les répertoires qui contiennent ceux-ci, ainsi que toutes éventuelles dépendances. - -Utilisez la commande suivante pour synchroniser les images et autres médias entre votre ancien serveur et le nouveau. - -```shell -rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/centreon/www/img/ -``` - -### Étape 5 : Montée de version de la solution Centreon - -1. Sur le nouveau serveur, forcez la montée de version en déplacant le contenu du répertoire - **/var/lib/centreon/installs/install-26.10.x-YYYYMMDD_HHMMSS** dans le - répertoire **/usr/share/centreon/www/install** (**x** est le numéro de version cible pour votre machine migrée): - - ```shell - cd /var/lib/centreon/installs/ - mv install-26.10.x-YYYYMMDD_HHMMSS/ /usr/share/centreon/www/install/ - ``` - -2. Si vous utilisez la meme adresse IP ou le même nom DNS entre l'ancien serveur - web Centreon et le nouveau, videz complètement le cache de votre navigateur pour - éviter des problemes de scripts JS. - -3. Connectez-vous à l'URL `http:///centreon` et suivez les étapes - de la mise à jour. - -4. Si vous avez modifié le mot de passe de l'utilisateur **centreon** lors de - l'installation de votre nouveau serveur Centreon pour accéder aux bases de - données, il sera nécessaire de réaliser les actions suivantes sur le nouveau - serveur Centreon : - - 1. Modifiez le fichier **/etc/centreon/centreon.conf.php**, - 2. Modifiez le fichier **/etc/centreon/conf.pm**, - 3. Éditez la configuration du Centreon Broker central, via l'interface web - Centreon et modifiez le mot de passe pour l'output **unfied-sql**, - 4. Modifiez le fichier **/etc/centreon/config.d/10-database.yaml**. - -5. Si l'adresse IP de votre serveur Centreon a changé : - - Éditez la configuration de l'ensemble des modules Broker de vos collecteurs et modifiez l'adresse IP de - connexion au serveur Centreon central (output IPv4). Consultez le chapitre - [Configuration - avancée](../monitoring/monitoring-servers/advanced-configuration.md#tcp-outputs) - pour plus d'information. - - L'empreinte de votre plateforme a également changé : [contactez Centreon](mailto:support@centreon.com) pour obtenir une nouvelle licence. - -6. Les informations de connexion de l'utilisateur **centreon-gorgone** nouvellement créé doivent être les mêmes que celles de l'utilisateur **centreon-gorgone** sur l'ancien serveur. Éditez le fichier `etc/centreon-gorgone/config.d/31-centreon-api.yaml` et entrez les information de connexion de l'ancien utilisateur. Exemple : - - ```shell - gorgone: - tpapi: - - name: centreonv2 - base_url: "http://127.0.0.1/centreon/api/latest/" - username: "@GORGONE_USER@" - password: "@GORGONE_PASSWORD@" - - name: clapi - username: "@GORGONE_USER@" - password: "@GORGONE_PASSWORD@" - ``` - -7. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) de tous vos serveurs de supervision (y compris celle du central). - -8. Redémarrez les processus suivants : - - ```shell - systemctl restart cbd centengine - systemctl restart gorgoned - systemctl start snmptrapd centreontrapd - systemctl start snmpd - ``` - -9. Si vous supervisiez votre ancienne machine Centreon, et que vous avez changé le nom d'utilisateur/mot de passe de la base pendant la migration, mettez à jour la configuration des ressources concernées (hôte, services dépendant de cet hôte). - -10. Allez à la page **Configuration > Connecteurs > Connecteurs de supervision**, puis [mettez à jour tous les connecteurs de supervision](../monitoring/pluginpacks.md#mettre-à-jour-un-ou-plusieurs-packs). - -### Étape 6 (anciennes versions uniquement): Migrer vers Gorgone - -Si vous migrez depuis un Centreon 18.10, 19.04 ou 19.10, vous devez également [migrer de Centcore à Gorgone](../developer/developer-gorgone-migrate-from-centcore.md). - -### Étape 7: Mettre à jour les modules - -Pour mettre à jour les modules, allez à la page **Administration > Extensions > Gestionnaire** et cliquez sur **Update all**. -Si vous avez un serveur MAP ou MBI, suivez les procédures de migration correspondantes : - -- Procédure de migration pour [MAP](../graph-views/map-web-migrate.md), -- Procédure de migration pour [MBI](../reporting/migrate.md). - -### Étape 8: Migrer vos autres serveurs (architecture distribuée) - -#### Migrer un serveur distant - -Pour migrer un serveur distant : - -1. Suivez la même procédure que pour un serveur central. -2. [Rattachez le nouveau serveur distant](../monitoring/monitoring-servers/add-a-remote-server-to-configuration.md) à votre serveur central. - -#### Migrer un collecteur - -Pour migrer un collecteur : - -1. [Installez un nouveau collecteur](../installation/installation-of-a-poller/using-packages.md). -2. Synchronisez les plugins, comme décrit à [l'étape 4 de la procédure de migration pour un serveur central](#étape-4--synchroniser-les-plugins). -3. Sur le serveur central, allez à la page **Configuration > Collecteurs**. Sélectionnez le collecteur migré et mettez à jour son adresse IP (si celle-ci a changé). -4. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md). -5. Si votre collecteur rencontre des problèmes suite à la migration (impossible de déployer la configuration, d'effectuer des actions de supervision...), mettez à jour l'empreinte du collecteur comme décrit dans [cet article de base de connaissances](https://thewatch.centreon.com/troubleshooting-41/poller-does-not-work-after-migration-or-reinstallation-fingerprint-changed-for-target-1177). diff --git a/secure_db.txt b/secure_db.txt deleted file mode 100644 index 22db1799dc10..000000000000 --- a/secure_db.txt +++ /dev/null @@ -1,34 +0,0 @@ -### Secure the database - -It is mandatory to secure the database's root access before installing Centreon. -If you are using a local database, run the following command on the central server: - - - - -```shell -mariadb-secure-installation -``` - - - - -Retrieve the temporary password created by MySQL: - -```shell -grep 'temporary password' /var/log/mysqld.log -``` - -Then change it when prompted by the following command: - -```shell -mysql_secure_installation -``` - - - - -* Answer **yes** to all the questions except "Disallow root login remotely?". -* It is mandatory to set a password for the **root** user of the database. You will need this password during the [web installation](../web-and-post-installation.md). - -> For more information, please see the [official MariaDB documentation](https://mariadb.com/kb/en/mysql_secure_installation/). \ No newline at end of file From 6d01f5aa1bbb6a01516a098a2741e3cd22032ef1 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 6 Oct 2026 18:26:19 +0200 Subject: [PATCH 116/179] Add temporary FR file (workaround for zombie links) --- .../migrate/upgrade-debian-in-place.md | 632 ++++++++++++++++++ 1 file changed, 632 insertions(+) create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/upgrade-debian-in-place.md diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/upgrade-debian-in-place.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/upgrade-debian-in-place.md new file mode 100644 index 000000000000..78b19a318665 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/upgrade-debian-in-place.md @@ -0,0 +1,632 @@ +--- +id: upgrade-debian-in-place +title: Upgrading Centreon and Debian (12 to 13) on the same server +description: "In-place migration procedure for Debian - Debian 12 to 13" +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +Use this procedure if you are running Centreon 24.04, 24.10 or 25.10 on Debian 12 and you wish to upgrade to Centreon 26.10 (only Debian 13 is supported for this version). + +> Run every command as `root`. + + +## Step 1: Before you start + +### 1.1 Take a snapshot of each server + +Snapshot every server (central server, database server, MAP server, MBI server). If you have a remote database, take both snapshots at the same time, with Centreon stopped if possible. It is the only way to roll back quickly. + +### 1.2 Create dumps + +Snapshots let you roll back a whole server quickly, but they do not replace backups. They usually share the VM's storage, capture databases only in a crash-consistent state, and cannot restore a single database or file. Once your snapshots are done, also make the backups below. + + ```bash + B=/root/upgrade-2610-backup; mkdir -p $B + # On the server that hosts the database + mysqldump --single-transaction --routines --triggers --events centreon | gzip > $B/centreon.sql.gz + mysqldump --single-transaction --routines --triggers --events centreon_storage | gzip > $B/centreon_storage.sql.gz + mysqldump --single-transaction --routines --triggers --events centreon_map | gzip > $B/centreon_map.sql.gz # [MAP], where it lives + zcat $B/centreon_storage.sql.gz | tail -n 1 # "-- Dump completed on …" + # On every server + tar czf $B/etc-$(hostname).tar.gz -C / etc + dpkg -l > $B/dpkg-l.txt + systemctl list-unit-files --state=enabled > $B/enabled-units.txt # compared in step 9 + ``` + +### 1.3 Check the state of the server + +Before starting the upgrade, check that the server is in the expected state: Debian 12, Centreon 25.10, enough free disk space, and working package repositories. If any result differs from the expected one, fix it before going further. + + ```bash + cat /etc/debian_version # 12.x + dpkg -l centreon-web | awk '/^ii/{print $3}' # 25.10.x + df -h / /var /var/lib/mysql # several GB free (~1,300 packages) + apt-get update # no error (a broken repository blocks the upgrade to Debian 13) + ``` + +### 1.4 Check that cron and logrotate are installed (on every Centreon server) + +Centreon needs **cron** to run its scheduled jobs and **logrotate** to rotate its logs. Minimal Debian images often include neither, and nothing warns you when they are missing. + +```bash +ls /etc/cron.d/ | grep -iE "centreon|centstorage" # Centreon jobs here? +dpkg -l cron | grep -q "^ii" || apt-get install -y cron # install if missing +systemctl enable --now cron && systemctl is-active cron # active +dpkg -l logrotate | grep -q "^ii" || apt-get install -y logrotate +chmod 644 /etc/logrotate.d/cbd /etc/logrotate.d/centengine 2>/dev/null +logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" # nothing +``` + +- **Without cron**, the Centreon jobs never run and no error is shown. This affects the MBI jobs (ETL, purge, backup) in particular. +- **Without logrotate**, Centreon logs are never rotated. +- **The `chmod 644` line** is a workaround. The Broker and Engine logrotate files are shipped with permissions `0664`, so logrotate ignores them. A package upgrade can restore `0664`, so check again in step 9. + +## Step 2: Update your Centreon version to the latest minor + +Follow the update procedures for your version ([24.04](https://archives-docs.centreon.com/24.04/docs/update/update-centreon-platform/), [24.10](https://docs.centreon.com/docs/24.10/update/update-centreon-platform/) or [25.10](https://docs.centreon.com/docs/25.10/update/update-centreon-platform.md)). Update your central server, your pollers and your remote servers. + + + +## Step 3: Update Debian 12 to the latest version + +The following commands bring the server to the latest Debian 12 minor version before the major migration to Debian 13. + +```bash +apt-get update +DEBIAN_FRONTEND=noninteractive apt-get -y -o Dpkg::Options::=--force-confold full-upgrade +cat /etc/debian_version # latest 12.x version +systemctl reboot +``` + +| If… | Do | +| ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | +| `apt-get update` fails on the **MaxScale** line (`NO_PUBKEY`) in `mariadb.list` | Comment **only that line** (the file also holds the MariaDB Server repository) | +| [MySQL] `mysql-apt-config` is upgraded (seen 0.8.36 → 0.8.40) | Nothing: `mysql.list` is kept | + +After the reboot, check that the web interface works and that the pollers are connected. You can update the servers in any order (central server or database server first). + +## Step 4: Upgrade a remote database server (if applicable) + +Do this only if your database runs on its own server, separate from the central. Before you start, make sure Centreon is already stopped on the central server. + +### 4.1 Back up the configuration and stop the database + +Run these commands on the **database server**: + +```bash +B=/root/upgrade-2610-backup; mkdir -p $B/apt-bookworm +cp -a /etc/apt/sources.list /etc/apt/sources.list.d /etc/mysql $B/apt-bookworm/ +systemctl stop mariadb # MySQL: systemctl stop mysql +``` + +This saves your current APT repositories and MySQL/MariaDB configuration, then stops the database. + +### 4.2 Upgrade the server + +1. **Update the repositories:** steps 5.1, 5.2 and 5.3. Here you only need the standard repository and the plugins repository. The `centreon-mariadb` and `centreon-mysql` packages come from the standard repository. +2. **Run the simulation (step 5.4).** You should see: + - `mariadb-server` 11.8, or `mysql-community-server` 8.4.x-1debian13 + - `centreon-mariadb` or `centreon-mysql` at 26.10 + - no `centreon-web`, because it is not installed on this server +3. **Run the upgrade (step 6).** + +### 4.3 Check the result + +```bash +dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' # nothing +cat /etc/debian_version # 13.x +systemctl is-active mariadb # active (MySQL: mysql) +mariadb -e "SELECT @@version, @@read_only" # 11.8.x, 0 (MySQL: 8.4.x, 0) +mariadb-upgrade --check-if-upgrade-is-needed && echo "run: mariadb-upgrade" || echo "done" # MySQL: skip this line +mariadb -e "SHOW DATABASES" | grep -E "^centreon(_storage)?$" # both databases listed +tail -n 5 /var/log/mysql/error.log # MySQL only: "ready for connections. Version: '8.4.x'" +find /etc/mysql -name "*.dpkg-dist" # keep your own file +systemctl enable mariadb && systemctl reboot # MySQL: mysql +``` + +For MySQL, use `mysql` instead of `mariadb` in the commands above. + +### 4.4 Check the connection from the central + +After the reboot, run this on the **central server**, replacing `` with the address of your database server: + +```bash +timeout 3 bash -c '/3306' && echo OK +``` + +It should print `OK`. (This command is used because `nc` is not installed by default.) + +### 4.5 Troubleshooting + +| If you see | What to do | +| --- | --- | +| A file named `50-server.cnf.dpkg-dist` | **Keep your own file** and ignore the new one. The new file sets `bind-address = 127.0.0.1`, which only allows local connections, so the central could no longer reach the database. Your file should have `bind-address = 0.0.0.0` (or the server's IP address) and `utf8mb4`. | +| MariaDB does not start | Run `systemctl start mariadb`, then read the details with `journalctl -u mariadb`. The usual cause is an option in your tuning file that was removed or renamed in the new MariaDB version. | +| `read_only` is 1 | Run `mariadb -e "SET GLOBAL read_only=OFF"`, then delete the `read_only` line from your configuration. That setting is meant for replica servers. | + +## Step 5: Switch the repositories (on every server you upgrade) + +The commands edit your existing repository files (either deb822 *.sources files or one-line *.list files). Do not add a new file next to an old one: the 25.10 and 26.10 repositories would mix. + +```bash +B=/root/upgrade-2610-backup; mkdir -p $B/apt-bookworm +cp -a /etc/apt/sources.list /etc/apt/sources.list.d $B/apt-bookworm/ # rollback +cp -a /etc/apache2/sites-available/centreon.conf $B/apache-centreon.conf.2510 2>/dev/null +ls /etc/apt/sources.list.d/ +``` + +### 5.1 On your Debian OS + +Point APT at the Debian 13 repositories instead of Debian 12. It only edits configuration files, nothing is downloaded or upgraded yet. + +```bash +[ -f /etc/apt/sources.list.d/debian.sources ] && sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/debian.sources +sed -i 's/bookworm/trixie/g' /etc/apt/sources.list +grep -rqs "trixie-backports" /etc/apt/sources.list /etc/apt/sources.list.d/ || \ + echo "deb http://deb.debian.org/debian/ trixie-backports main non-free-firmware" >> /etc/apt/sources.list +``` + +### 5.2 On Centreon + +**5.2 Centreon** (any file name: `centreon-25.10-stable.list`, `centreon-stable.list`, …) + +Point the Centreon repositories at the 26.10 packages for Debian 13. It only edits APT configuration files, nothing is upgraded yet. + +```bash +for f in $(grep -lE "packages.centreon.com|centreon.jfrog.io" /etc/apt/sources.list.d/*.list); do + sed -i -E -e 's/bookworm-25\.10-[a-z-]+/trixie-26.10-stable/g' -e 's/ (bookworm|bullseye) / trixie /g' "$f" + echo "== $f"; cat "$f" +done +grep -qs "apt-plugins-stable/\? trixie" /etc/apt/sources.list.d/*.list || \ + echo "deb https://packages.centreon.com/apt-plugins-stable/ trixie main" > /etc/apt/sources.list.d/centreon-plugins-stable.list +mv centreon-25.10-stable.list centreon-26.10-stable.list +``` + +| Repository line | Required? | +| ---------------------------------------------------------------------------------- | --------------------------------------------------------------------- | +| `apt-standard/ …` | **Yes** | +| `apt-plugins-stable/ trixie` | **Yes**: trixie builds of the Perl libs (Net::Curl, Libssh::Session…) | +| `apt-business/ …` | Only with Business modules (**required on the MBI server**) | +| `apt-plugins-testing/ bookworm` (or `apt-plugins-testing trixie` after the switch) | Optional | +| `centreon.jfrog.io/…/apt-connectors-stable/` | Optional | + +File names keep `25.10`: cosmetic (`mv centreon-25.10-stable.list centreon-26.10-stable.list` if you want). + +### 5.3 On the database server + +Run this on every server that hosts a database: the central server (if the database is local), the remote database server, and the MAP or MBI server. + +Update the database repositories for Debian 13. For MariaDB it also changes the version, from 10.11 to 11.8. It only edits APT configuration files and upgrades nothing yet. + + + + +```bash +for f in /etc/apt/sources.list.d/mariadb.sources /etc/apt/sources.list.d/mariadb.list; do + [ -f "$f" ] || continue + sed -i -e 's|mariadb-server/10.11/|mariadb-server/11.8/|' -e 's/bookworm/trixie/g' "$f" + echo "== $f"; grep -vE "^\s*#|^\s*$" "$f" +done +``` + + + + +```bash +[ -f /etc/apt/sources.list.d/mysql.list ] && sed -i 's/ bookworm / trixie /g' /etc/apt/sources.list.d/mysql.list +echo "mysql-apt-config mysql-apt-config/repo-codename select trixie" | debconf-set-selections +echo "== /etc/apt/sources.list.d/mysql.list"; grep -vE "^\s*#|^\s*$" /etc/apt/sources.list.d/mysql.list +``` + + + + +| If… | Do / know | +| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| No `mariadb.*` file | MariaDB comes from Debian: Debian 13 ships 11.8, nothing to do | +| [MySQL] `mysql.list` points to `mysql-8.0` | **Stop**: `repo.mysql.com` trixie has no 8.0. Upgrade to 8.4 LTS on Debian 12 first (trixie has `mysql-8.4-lts`, `mysql-9.7-lts`, `mysql-innovation`, plus `mysql-apt-config`, `mysql-tools`) | +| [MySQL] debconf line skipped | A later `mysql-apt-config` reconfiguration (`dpkg-reconfigure`, new package version) may write `bookworm` back. With it: kept (checked; prints a harmless `gpg: cannot open '/dev/tty'`) | +| `*.disabled`, `*.old_*` files | Ignored by apt | +| MaxScale line commented in step 3 | Stays commented | + +### 5.4 Check and simulate + +This step is a dry-run check before the real upgrade. It verifies that the repository changes are correct and simulates the upgrade, so you can spot problems while nothing has been modified yet. The comment at the end of each line is the expected result. + +```bash +grep -rn bookworm /etc/apt/sources.list /etc/apt/sources.list.d/ | grep -v ":\s*#" # nothing +apt clean && apt-get update # no W:/E: +apt-get -s full-upgrade > $B/sim.txt +tail -n 3 $B/sim.txt # N upgraded / new / removed +grep -iE "broken|unmet" $B/sim.txt # nothing +grep -E "^Inst (centreon-web|php8.4-fpm|mariadb-server|mysql-community-server) " $B/sim.txt +grep -E "^Remv centreon" $B/sim.txt # nothing +``` + +* If the simulation shows broken packages, stop and restore the sources: `cp -a $B/apt-bookworm/* /etc/apt/`. +* If everything matches the expected results, you can proceed to the real upgrade. If not, fix the repositories first. Nothing has changed on the system at this point, so the check is safe to repeat. + +## Step 6: Upgrade (every server you upgrade) + +This is the real upgrade to Debian 13. It runs the upgrade in the background, in two stages, and then lets you watch its progress. + +```bash +systemd-run --unit=upg2610 /bin/sh -c 'export DEBIAN_FRONTEND=noninteractive; O="-o Dpkg::Options::=--force-confold -o Dpkg::Options::=--force-confdef"; apt-get -y $O upgrade --without-new-pkgs > /root/upgrade-2610-backup/upg-step1.log 2>&1 && apt-get -y $O full-upgrade > /root/upgrade-2610-backup/upg-step2.log 2>&1' +watch -n 10 'pgrep -x apt-get; pgrep -x dpkg; tail -n 2 /root/upgrade-2610-backup/upg-step2.log' # done when both pgrep print nothing +``` + +- Don't interrupt it and don't reboot until it's finished, even if it seems slow (about 1,300 packages). +- Duration: central ~10–15 min, database/MBI server ~6 min, poller ~6 min. +- `systemd-run`: the upgrade survives an SSH disconnection (`openssh-server` is upgraded). +- Wait on the **processes**, not on the unit state (unreliable while systemd itself is upgraded). +- Expected in the logs: `chmod: cannot access '/var/cache/centreon/config/broker/*'` and `…/engine/*`. +- **Do not reboot yet.** + +Then stop Centreon again on the central server. The 26.10 packages restart the services (and cron, if it was upgraded), but the database schema stays at 25.10 until you run the update wizard in step 8. Until then, Gorgone logs `Unknown column 'uid' in 'field list'` / `[legacycmd] Cannot get configuration for pollers` every 15 s. + +```bash +systemctl stop centengine cbd gorgoned centreontrapd cron +systemctl stop centreon-map-engine 2>/dev/null # [MAP] +``` + +## Step 7: Checks after the packages + +### 7.1 Run checks + +This step is the post-upgrade verification (7.1 to 7.4), followed by switching the web stack to PHP 8.4. It checks that the upgrade to Debian 13 went cleanly and that nothing was left half-done. The comment on each line is the expected result. + +```bash +# 7.1 dpkg +dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' # nothing ("rc" = removed, OK) +grep -hE "^(W|E):|dpkg: (error|erreur)" /root/upgrade-2610-backup/upg-step*.log # nothing +cat /etc/debian_version # 13.x +dpkg -l centreon-web centreon-engine centreon-broker centreon-gorgone php8.4-fpm | awk '/^ii/{print $2, $3}' +# 7.2 Perl / libraries left on Debian 12 +dpkg -l | awk '/^ii/ && $3 ~ /deb12/ {print $2, $3}' # only obsolete Debian libs (libperl5.36, perl-modules-5.36…) +perl -MCrypt::OpenSSL::AES -MNet::Curl -MLibssh::Session -e 'print "OK\n"' # OK +# 7.3 Config files kept by --force-confold +find /etc -name "*.dpkg-dist" -o -name "*.ucf-dist" | grep -E "apache2|centreon|php|mysql" +# 7.4 PHP 8.4 +systemctl enable --now php8.4-fpm; systemctl disable --now php8.2-fpm 2>/dev/null +systemctl restart apache2 +curl -s -o /dev/null -w "%{http_code}\n" http://localhost/centreon/ # 200 +``` + +| If… (7.2 / 7.3) | Do | +| ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | +| A Centreon or `lib*-perl` package still `deb12`, or Perl not OK | `apt-get install --reinstall `; check `apt-plugins-stable trixie` (5.2) | +| [MAP] `openjdk-17-jre-headless` still `deb12` | Normal: MAP 26.10 uses Java 25 (`openjdk-25-jre-headless`, now default). After validation: `apt purge openjdk-17-jre-headless` | +| `apache2/…/centreon.conf.dpkg-dist` | **Apache merge** (step 2): 26.10 adds the Gorgone websocket `ProxyPass` block | +| `/etc/centreon-engine/centengine.cfg.dpkg-dist`, `/etc/centreon-broker/central-module.json.dpkg-dist` | Keep yours (generated by the export) | +| `/etc/mysql/mariadb.conf.d/50-server.cnf.dpkg-dist` | Keep yours (package sets `bind-address = 127.0.0.1`) | +| [MAP] `/etc/centreon-map/map-config.properties.dpkg-dist` | Keep yours: it is a template (`%CENTREON_BROKER_ADDRESS%`, `%CENTREON_PWD%`…) | + +### 7.2 Check the database + +If you have a local database, run this on the central server. If your database is on a separate server, run this on that server, not on the central. + +This step is the database health check after the upgrade. It confirms that the new MariaDB 11.8 is running, writable, upgraded internally, and that the Centreon databases are still there. The comments give the expected result, with the MySQL variant after the dash. + +```bash +systemctl is-active mariadb # active — [MySQL] mysql +mariadb -e "SELECT @@version, @@read_only" # 11.8.x, 0 — [MySQL] 8.4.x, 0 +mariadb-upgrade --check-if-upgrade-is-needed && echo "run: mariadb-upgrade" || echo "done" # [MySQL] skip +mariadb -e "SHOW DATABASES" | grep -E "^centreon(_storage|_map)?$" +journalctl -u mariadb --since "-1h" | grep -iE "error|warning" | tail -n 20 # [MySQL] tail /var/log/mysql/error.log +``` + +* If MariaDB isn't active, or the version query shows read_only = 1 (the database refuses writes), use [the troubleshooting table from step 4](#45-troubleshooting). +* If the check prints "run: mariadb-upgrade", run mariadb-upgrade. It takes its login details from /root/.my.cnf. When it works, it finishes with return code 0 after 8 phases, and running the check again reports that no upgrade is needed. + Why this happens: the MariaDB package normally updates the database's internal system tables during the upgrade. It can't do this if the MariaDB root account has a password, and it won't warn you. MariaDB 11.8 then runs on system tables still in the 10.11 format. If root logs in through unix_socket (no password), the package does it by itself, as it did on the database servers we tested. + +## Step 8: Finalize the upgrade on the central server + +### 8.1 On the web interface + +First, clear your browser cache so you don't see old pages from 25.10. (If you use MAP, its documentation has the same step.) + +1. Run the update wizard to 26.10. Click Finish only once. + The wizard log may show `Undefined array key "is_reverse"` in `Update-25.11.0.php`. If you use the Centreon Monitoring Agent, check the connection mode of each agent configuration. It should be set to "agent initiated", which is the default. +2. Update the modules in **Administration > Extensions > Manager**. Update them one at a time, and wait for each to finish before starting the next. + * If you use MAP, update both the MAP module and the MAP widget. They have separate buttons. + * Avoid **Update all**. On both test platforms, it left auto-discovery not updated until a second request. If you use it anyway, check that auto-discovery shows version 26.10. +3. Apply the updates in the Monitoring Connector Manager. + +### 8.2 On the central server + +To restart Centreon on the new version, run these commands on the central server: + +```bash +cd /usr/share/centreon && sudo -u www-data php bin/console cache:clear +usermod -a -G centreon-broker www-data +usermod -a -G www-data centreon-broker +sudo -u www-data php /usr/share/centreon/bin/console w:m:c --dry-run # "No invalid commands found." +systemctl restart cbd centengine gorgoned centreontrapd +systemctl start centreon-map-engine # [MAP] +``` + +What these commands do: + +* Clear the web application cache. +* Let the web server and Broker access each other's files. +* Check for invalid Engine and Broker commands. If the check lists any, run it again without **--dry-run** to remove them. (`w:m:c` is short for `web:monitoring-server:clean-engine-broker-command`.) +* Restart the monitoring services, and start the MAP engine if you use MAP. + +If you use MAP, check that it works: + +* `systemctl is-active centreon-map-engine` should print `active`. +* Run `for p in $(pgrep -x java); do readlink -f /proc/$p/exe; done`. The result should contain `java-25-openjdk`. +* Run `grep -E "ERROR|Connection with Broker established" /var/log/centreon-map/centreon-map-engine.log | tail -n 5`. You should see that the connection with Broker is established. A few `Error while connecting to Broker` messages are normal while Broker restarts. + +### 8.3 Export the configuration from the web interface + +1. Export the central server's configuration with **Generate**, **Move export files** and **Restart all** checked. If you skip **Move export files**, the new files stay in `/var/cache/centreon/config` and Engine 26.10 keeps using the old configuration. + +2. Restart the services one last time + + ```bash + systemctl restart cbd centengine centreontrapd gorgoned + systemctl start cron + ``` + + This makes the services load the new configuration and turns scheduled jobs (cron) back on. + +## Step 9: Make sure everything starts at boot, then reboot + +1. Run these commands on the central server: + + ```bash + systemctl enable centengine cbd gorgoned centreontrapd snmptrapd.socket php8.4-fpm apache2 cron + systemctl enable centreon-map-engine 2>/dev/null # [MAP] + systemctl enable mariadb # [local DB] or local MAP DB — [MySQL] mysql + diff <(awk '{print $1}' /root/upgrade-2610-backup/enabled-units.txt | sort) \ + <(systemctl list-unit-files --state=enabled | awk '{print $1}' | sort) # php8.2 → php8.4 expected + systemctl reboot + ``` + + What these commands do: + + * Make sure all Centreon services, the web server, PHP 8.4, cron and the database start automatically at boot. + * Compare the list of services enabled before the upgrade (saved in step 1.2) with the current list. The only expected difference is php8.2-fpm replaced by php8.4-fpm. Anything else deserves a look. + * Reboot the server. + +2. After the reboot, check that everything works: + +```bash +uname -r # 6.12.x +systemctl --failed # 0 units +for u in centengine cbd gorgoned centreontrapd php8.4-fpm apache2 mariadb centreon-map-engine cron; do printf "%s=%s " $u $(systemctl is-active $u); done; echo +ls /etc/cron.d/ # centreon, centstorage +ss -ulnp | grep ":162 " # SNMP traps: UDP 162 held by systemd +logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" # nothing (else table below) +systemctl is-active centreontrapd # active (see the table below) +``` + +What you should see: + +* The kernel version starts with 6.12. +* No failed services. +* Each service reports active. +* The Centreon cron files (centreon, centstorage) are in /etc/cron.d/. +* Port UDP 162, used for SNMP traps, is held by systemd. + +| What you see | What it means and what to do | +| -------------------------------------------- | ------------------------------------------------------------------------------------ | +| `snmptrapd` is inactive | Normal on Debian 13. It starts on demand when the first trap arrives. | +| `centreontrapd` is inactive, with exit **0/SUCCESS** | The trap database is empty. See step 10, centreontrapd. | +| `cron` is inactive | Run `systemctl enable --now cron` (See step 1.4.) | +| `logrotate.service` failed (`Ignoring cbd` / `centengine`) | `chmod 644 /etc/logrotate.d/cbd /etc/logrotate.d/centengine`; `systemctl start logrotate` | + +Finally, check the web interface: + +* **Configuration > Pollers**: all pollers are running and were updated recently. There should be no duplicate **Central** entry. (The 26.10 Broker registers the central under a new instance ID, so a duplicate can appear.) +* **Resources Status**: force a check, acknowledge a problem and set a downtime, to confirm they work. +* Graphs are drawn. +* Gorgone is connected. + +## Step 10: Upgrade the pollers (after the central) + +Allow about 6 minutes per poller. Do each poller one at a time. + +1. Back up and update Debian 12. Do the system part of step 1.2, then step 3 (Debian 12 point release and reboot). +2. Stop the monitoring services: + + ```bash + systemctl stop centengine gorgoned centreontrapd + ``` + +3. Upgrade to Debian 13 and Centreon 26.10. Do steps 5.1 and 5.2 (APT repositories, standard and plugins), then step 5.4 and step 6. + After step 5.4, you should see `centreon-poller`, `centreon-engine`, `centreon-broker` and `centreon-gorgone` at 26.10.0, plugins built for `deb13`, and no package removed. +4. Check the result. Do steps 7.1 and 7.2. If `centengine.cfg.dpkg-dist` exists, keep your own file. +5. Reboot, then export the poller's configuration from the central server, with **Generate**, **Move export files** and **Restart** all checked. +6. Check that everything works: + + ```bash + systemctl --failed # 0 units + systemctl is-active centengine gorgoned centreontrapd # all active + grep -E "Centreon Engine 26.10|Configuration loaded" /var/log/centreon-engine/centengine.log | tail -n 2 + ss -tn | grep -E ":5669|:5556" # Broker (5669) and Gorgone (5556) connected to the central + ls -l /etc/snmp/centreon_traps/centreontrapd.sdb # file is not empty + logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" # nothing (else 1.4) + ``` + +### If `centreontrapd` stops by itself + +If the trap database `centreontrapd.sdb` is empty, `centreontrapd` stops one second after it starts. In `/var/log/centreon/centreontrapd.log`, you will see `MySQL error: no such table: cfg_nagios`. systemd reports `inactive (dead)` with status **0/SUCCESS**, so there is no alert, and **no SNMP trap is processed**. + +To fix it: + +1. In the web interface, go to **Configuration > SNMP Traps > Generate**. +2. Select the poller. +3. Check **Generate traps database**, **Apply configurations** and **Restart centreontrapd**. + +The upgrade does not cause this problem. It was also seen on 25.10 after a simple reboot. + +### What to expect + +- Acknowledgements and downtimes survive the poller upgrade, thanks to retention. +- The `downtimes` history gets a new row when Engine restarts. This is normal. + +## Step 11: Upgrade your MBI server (if applicable) + +The central server needs nothing extra. `centreon-bi-server` is upgraded in step 6, and the MBI module and widgets are updated in step 8. + +On the reporting server, make sure no ETL run is in progress: check with `ps -ef | grep -i etl` that none is in progress. + +### 11.1 Before the upgrade + +1. **Back up the server:** + + ```bash + B=/root/upgrade-2610-backup; mkdir -p $B + tar czf $B/etc-$(hostname).tar.gz -C / etc; dpkg -l > $B/dpkg-l.txt + systemctl list-unit-files --state=enabled > $B/enabled-units.txt + ``` + + Also back up the reporting database, as described on the MBI page [Backing up and restoring MBI](../reporting/backup-restore.md). + +2. **Make sure cron is installed** (see step 1.4). + + ```bash + dpkg -l cron | grep -q "^ii" || apt-get install -y cron + ``` + +3. **Stop the services:** + + ```bash + systemctl stop cbis gorgoned cron + ``` + +### 11.2 Upgrade + +1. Do step 3 (Debian 12 point release and reboot), if not already done. +2. Do steps 5.1 and 5.2 (standard, **business** and plugins repositories), then step 5.3 (MariaDB or MySQL repository). +3. Do step 5.4, then step 6. In the simulation, you should see `centreon-bi-reporting-server`, `centreon-bi-engine`, `centreon-bi-etl` and `centreon-bi-report` at 26.10.0, plus `openjdk-25-jdk`. No package should be removed. + +### 11.3 Check and restart + +```bash +dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' # nothing +dpkg -l "centreon-bi*" | awk '/^ii/{print $2, $3}' # 26.10.0 +java -version 2>&1 | head -n 1 # openjdk 25 +grep ExecStart /lib/systemd/system/cbis.service | grep -o "java-[0-9]*-openjdk" # java-25-openjdk +find /etc -name "*.dpkg-dist" | grep -E "centreon|mysql" # keep yours (bind-address) +systemctl is-active mariadb # local reporting DB (MySQL: mysql) +systemctl start cbis; systemctl enable --now gorgoned cron +systemctl is-active cbis gorgoned cron # all active +ls /etc/cron.d/ | grep centreon-bi # engine, purge, backup-reporting-server +tail -n 20 /var/log/centreon-bi/cbis.$(date +%F).log # no "Connection test … failed" +``` + +Then reboot and check again that `cbis`, `gorgoned` and `cron` are active. After 07:30 on the next weekday, `/var/log/centreon-bi/centreonBIETL.log` should show the ETL run. + +### Good to know + +- **Java 25, not 17.** MBI 26.10 uses Java 25. `centreon-bi-engine` pulls in `openjdk-25-jdk`, and `cbis.service` runs `/usr/lib/jvm/java-25-openjdk-amd64/bin/java` directly. The Java 17 left over from Debian 12 is unused. After validation, remove it with `apt purge openjdk-17-*`. + +## Known issues + +Here is the table without the Ticket column: + +| When | You see | Do | +| --- | --- | --- | +| MBI server | Nothing: ETL, purge, backup never run (`cron` absent) | 1.4: install/enable `cron`; check `centreonBIETL.log` next weekday | +| Reboot (central, poller) | `centreontrapd` inactive, exit 0, `no such table: cfg_nagios` | Generate the SNMP traps database, restart centreontrapd | +| Any server, after the upgrade | `logrotate.service` failed, `Ignoring cbd … writable by group or others`; or no logrotate at all (25.10) | 1.4: install logrotate, `chmod 644` cbd/centengine | +| Step 2 | dpkg error, `chmod … .ssh/id_rsa` | `dpkg --configure -a`, all `ii` | +| Steps 2, 8 (extensions) | `cache:clear` error, `Cannot rename` / `Failed to read file …/symfon_` | One module at a time; `cache:clear` alone; check versions | +| Step 8 (_Update all_) | auto-discovery still on 25.10 after the batch | Update it again, check 26.10 | +| Steps 2, 8 (wizard) | Last step sent twice, HTTP 500 | Click Finish once; update done anyway | +| Step 8 (wizard log) | `Undefined array key "is_reverse"` in `Update-25.11.0.php` | Check Monitoring Agent connection modes | +| Export | `auto_reschedule_checks is no longer available` | Warning only | +| Steps 2, 6 (package logs) | `chmod: cannot access '/var/cache/centreon/config/broker/*'` | Harmless | +| 25.10 pollers | Ack closed in history when the service enters a downtime | Pollers on latest 25.10 first; upgrade them soon | +| MBI doc | Java 17 required, no Debian 13 tab, no cron | Follow section 11 | +| Official doc | No Debian 12 → 13 path for 25.10 → 26.10 | This document | +| Step 6 → 8 | Gorgone `Unknown column 'uid'` every 15 s | Stop Centreon again after step 6 | +| Steps 2, 7 (custom Apache) | `centreon.conf.dpkg-dist`, new vhost not applied | Apache merge | +| 4b, 7.3, 11 | `50-server.cnf.dpkg-dist` with `bind-address = 127.0.0.1` | Keep yours | +| Step 7.2 | Plugins / Gorgone cannot load a Perl module | Reinstall from trixie; `apt-plugins-stable trixie` | +| Step 8 export | Engine still on the old config | Export again with **Move** checked | +| Step 9 | `snmptrapd` inactive | Normal (socket-activated) | +| MariaDB 11.8 tools | `mysql: Deprecated program name …` | Cosmetic; use `mariadb` | +| 4b, 7.5 (MariaDB root with a password) | `mariadb-upgrade --check-if-upgrade-is-needed` → needed after the upgrade, nothing logged | Run `mariadb-upgrade` yourself | +| Step 3 | `NO_PUBKEY` on the MaxScale line | Comment only that line | + +## MariaDB/MySQL equivalents + +| Item | MariaDB | MySQL (Oracle `repo.mysql.com`) | +| ---------------- | ----------------------------------------------------- | ---------------------------------- | +| Service, client | `mariadb` | `mysql` | +| Dump | `mysqldump` / `mariadb-dump` | `mysqldump` | +| Centreon package | `centreon-mariadb` | `centreon-mysql` | +| Repository file | `mariadb.sources` or `mariadb.list` | `mysql.list` + `mysql-apt-config` | +| Version | 10.11 → **11.8** (major) | **8.4 → 8.4** LTS, Debian 13 build | +| Data upgrade | `mariadb-upgrade`, run by the package | automatic at server start | +| Root access | `sudo mariadb` if `unix_socket`, else `/root/.my.cnf` | `/root/.my.cnf` | +| Config dir | `/etc/mysql/mariadb.conf.d/` | `/etc/mysql/mysql.conf.d/` | From 04b3a947e69d9a98c9dae861b4773e1bdc418ec6 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Wed, 7 Oct 2026 15:20:22 +0200 Subject: [PATCH 117/179] Corrections --- .../administration/self-signed-certificate.md | 177 +----------------- .../installation/_database-local-install.mdx | 2 +- .../upgrade/_upgrade-central.mdx | 2 +- .../version-26.10/upgrade/upgrade-mariadb.md | 15 +- .../administration/self-signed-certificate.md | 177 +----------------- .../installation/_database-local-install.mdx | 2 +- .../upgrade/_upgrade-central.mdx | 4 +- .../version-26.10/upgrade/upgrade-mariadb.md | 15 +- 8 files changed, 21 insertions(+), 373 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md index 40f9f93cee29..c979c4303c11 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md @@ -21,7 +21,7 @@ Cette procédure vous permet de créer les fichiers suivants : ## Ce que fait cette procédure -La procédure crée, dans des dossiers temporaires, les fichiers nécessaires pour établir une connexion TLS. Lorsque vous configurerez HTTPS sur un serveur, vous devrez déployer ces fichiers au bon emplacement. Par exemple, **/etc/pki/centreon-tls** est l'emplacement par défaut des certificats sous EL. Sous Debian, le chemin par défaut est **/etc/ssl/certs**. +La procédure crée, dans des dossiers temporaires, les fichiers nécessaires pour établir une connexion TLS. Lorsque vous configurerez HTTPS sur un serveur, vous devrez déployer ces fichiers au bon emplacement. Par exemple, **/etc/pki** est l'emplacement par défaut des certificats sous EL. Sous Debian, le chemin par défaut est **/etc/ssl/certs**. Vous pouvez suivre cette procédure sur une plateforme Centreon dont la base de données est locale ou distante. @@ -222,178 +222,3 @@ sudo chmod 0640 /out/db/server-key.pem ``` Les 3 fichiers nécessaires se trouvent maintenant dans votre dossier **/out**. Vous pouvez les copier aux emplacements appropriés sur vos serveurs (et les renommer si besoin). - - - - - diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx index d9665f7c2021..904f508ee17f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx @@ -92,7 +92,7 @@ systemctl restart mysql Définissez un mot de passe pour l'utilisateur root de la base de données en exécutant la commande suivante : ```shell -mysql-secure-installation +mysql_secure_installation ```     diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx index 46b09755246a..5d7bbcb1e6ca 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx @@ -36,7 +36,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/e ### Étape 2 : Démarrer la montée de version de la solution Centreon -1. Assurez-vous que tous les utilisateurs sont déconnectés de l'interface web de Centreon avant de démarrer la procédure de montée de version. +1. Assurez-vous que tous les utilisateurs sont déconnectés de l'interface web de Centreon avant de démarrer la procédure de montée de version. Considérez la plateforme comme en maintenance jusqu'à la fin de l'étape 7. 2. Si vous avez installé des extensions Business, supprimez la configuration du dépôt {props.oldCentreonVersion} : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md index db3656152fc2..784bc9b0ffd5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md @@ -10,10 +10,9 @@ Vous pouvez potentiellement avoir plusieurs bases MariaDB dans votre architectur ## Processus de mise à jour -Lorsque vous passez d'une version majeure de Centreon à une autre, vous devez : +Passer d'une version majeure de Centreon à une autre implique une série d'étapes que vous devez effectuer dans le bon ordre. Ces étapes comprennent notamment la mise à jour de MariaDB et celle de Centreon (paquets, installation web, déploiement de la configuration), mais leur ordre exact dépend de votre version actuelle et de la version cible. Suivez toujours la procédure de mise à jour correspondant à votre version. -1. Upgrader Centreon (paquets, installation web, déploiement de la configuration). NOtez que vous ne pouvez upgrader Centreon [qu'à partir d'un OS encore supporté](upgrade-matrix.mdx). -2. Upgrader MariaDB. +Vous ne pouvez mettre à jour Centreon que [depuis un OS supporté](upgrade-matrix.mdx). > Référez vous à la documentation officielle de MariaDB pour en savoir davantage sur le processus de mise à jour : > - https://mariadb.com/kb/en/upgrading-between-major-mariadb-versions/ @@ -55,7 +54,7 @@ MariaDB-compat-10.5.8-1.el9.centos.x86_64 ## Changer de version majeure de MariaDB -Il est nécessaire de désinstaller puis réinstaller MariaDB pour changer de version majeure (par exemple pour passer d'une version 10.5 à une version 10.11). +Dans cet exemple, nous passons de la version 10.11 à la version 11.8. Adaptez la procédure si vous effectuez la mise à jour depuis une autre version. 1. Arrêtez le service mariadb : @@ -73,7 +72,7 @@ dnf module reset mariadb -y ```shell dnf module enable -y mariadb:11.8 -dnf install mariadb-server-11.8\* mariadb-11.8\* +dnf install -y mariadb-server-11.8\* mariadb-11.8\* ``` 4. Démarrer le service mariadb : @@ -85,19 +84,19 @@ dnf install mariadb-server-11.8\* mariadb-11.8\* 5. Lancez le processus de mise à jour MariaDB : ```shell - mysql_upgrade + mariadb-upgrade ``` Si votre base de données est protégée par mot de passe, entrez : ```shell - mysql_upgrade -u -p + mariadb-upgrade -u -p ``` Exemple : si votre utilisateur_admin_bdd est `root`, entrez: ``` - mysql_upgrade -u root -p + mariadb-upgrade -u root -p ``` > Référez vous à la [documentation officielle](https://mariadb.com/kb/en/mysql_upgrade/) diff --git a/versioned_docs/version-26.10/administration/self-signed-certificate.md b/versioned_docs/version-26.10/administration/self-signed-certificate.md index c166f5d38968..b1a14d11820c 100644 --- a/versioned_docs/version-26.10/administration/self-signed-certificate.md +++ b/versioned_docs/version-26.10/administration/self-signed-certificate.md @@ -21,7 +21,7 @@ This procedure allows you to create the following files: ## What this procedure does -The procedure creates the files you need to set up a TLS connection, in temporary folders. When you set up HTTPS on a server, you will need to deploy the necessary files to the correct location. Example: **/etc/pki/centreon-tls** is the default location for certificates on EL. Debian's default path is **/etc/ssl/certs**. +The procedure creates the files you need to set up a TLS connection, in temporary folders. When you set up HTTPS on a server, you will need to deploy the necessary files to the correct location. Example: **/etc/pki** is the default location for certificates on EL. Debian's default path is **/etc/ssl/certs**. The procedure can be run on a Centreon platform that has a local database, or a remote one. @@ -224,178 +224,3 @@ sudo chmod 0640 /out/db/server-key.pem ``` You now have the files you need in your **/out** folder. You can copy them to the correct locations on your servers (and rename them if you need to). - - - - - \ No newline at end of file diff --git a/versioned_docs/version-26.10/installation/_database-local-install.mdx b/versioned_docs/version-26.10/installation/_database-local-install.mdx index b14122bbaff3..a81bd1c08c99 100644 --- a/versioned_docs/version-26.10/installation/_database-local-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-local-install.mdx @@ -92,7 +92,7 @@ systemctl restart mysql Set a password for the root user of the database by executing the following command: ```shell -mysql-secure-installation +mysql_secure_installation ```     diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index 29be6f3b00f8..a1c9b85f32ef 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -36,7 +36,7 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/e ### Step 2: Start upgrading the Centreon solution -1. Make sure all users are logged out from the Centreon web interface before starting the upgrade procedure. +1. Make sure all users are logged out from the Centreon web interface before starting the upgrade procedure. Consider your platform as in maintenance until the end of step 7. 2. If you have installed Business extensions, delete the configuration of the {props.oldCentreonVersion} repository: @@ -275,7 +275,7 @@ AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javasc 3. Finally, restart Broker, Engine and Gorgone on the central server by running this command: ```shell - systemctl restart cbd centengine gorgoned + systemctl restart cbd centengine gorgoned centreontrapd ``` 4. Update the permissions on the centreon-broker configuration files. diff --git a/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md b/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md index 02097debf73b..578889a055b1 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md @@ -11,10 +11,9 @@ and the MBI and MAP modules each have a dedicated database. Within your architec ## Upgrading process -When you upgrade from one major version of Centreon to another, you must: +Upgrading from one major version of Centreon to another is a series of steps that you must perform in the correct order. These steps include upgrading MariaDB and upgrading Centreon (packages, web installation, configuration deployment), but the exact sequence depends on your current and target versions. Always follow the upgrade procedure for your version. -1. Upgrade Centreon (packages, web installation, deploying the configuration). Note that you can only upgrade Centreon [from a supported OS](upgrade-matrix.mdx). -2. Upgrade MariaDB. +You can only upgrade Centreon [from a supported OS](upgrade-matrix.mdx). > Refer to the official MariaDB documentation for more information about this process: > https://mariadb.com/kb/en/upgrading-between-major-mariadb-versions/ @@ -56,7 +55,7 @@ MariaDB-compat-10.5.8-1.el9.centos.x86_64 ## Upgrading between major MariaDB versions -You must uninstall then reinstall MariaDB to upgrade between major versions. In this example, we will switch from version 10.11 to version 11.8. Adapt the procedure if you are upgrading from another version. +In this example, we will switch from version 10.11 to version 11.8. Adapt the procedure if you are upgrading from another version. 1. Stop the MariaDB service: @@ -90,7 +89,7 @@ dnf module reset mariadb -y ```shell dnf module enable -y mariadb:11.8 -dnf install mariadb-server-11.8\* mariadb-11.8\* +dnf install -y mariadb-server-11.8\* mariadb-11.8\* ```     @@ -113,19 +112,19 @@ dnf install mariadb-server-11.8\* mariadb-11.8\* 5. Launch the MariaDB upgrade process: ```shell - mysql_upgrade + mariadb-upgrade ``` If your database is password-protected, enter: ```shell - mysql_upgrade -u -p + mariadb-upgrade -u -p ``` Example: if your database_admin_user is `root`, enter: ```shell - mysql_upgrade -u root -p + mariadb-upgrade -u root -p ``` > Refer to the [official documentation](https://mariadb.com/kb/en/mysql_upgrade/) From 370c412e252530b455bf8d29f5020674b9d3d541 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 8 Oct 2026 09:54:41 +0200 Subject: [PATCH 118/179] Changes following review --- .../installation/_database-configuration.mdx | 16 ++++- .../installation/_database-local-install.mdx | 16 +++-- .../installation/_database-remote-install.mdx | 10 +-- .../installation/_database-repository.mdx | 6 -- .../installation/_install-common.mdx | 2 + .../using-packages.md | 1 - .../using-packages.md | 2 +- .../installation/web-and-post-installation.md | 2 +- .../migrate/migrate-from-el-to-el.md | 64 ++++++++++++++----- .../version-26.10/upgrade/upgrade-mariadb.md | 4 +- .../installation/_database-configuration.mdx | 18 +++++- .../installation/_database-local-install.mdx | 17 +++-- .../installation/_database-remote-install.mdx | 11 ++-- .../installation/_database-repository.mdx | 6 -- .../installation/_install-common.mdx | 4 +- .../using-packages.md | 1 - .../using-packages.md | 2 +- .../installation/web-and-post-installation.md | 2 +- .../migrate/migrate-from-el-to-el.md | 42 +++++++----- .../version-26.10/upgrade/upgrade-mariadb.md | 4 +- 20 files changed, 151 insertions(+), 79 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx index 18a4988fd171..f9514258a2a4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx @@ -3,7 +3,7 @@ import TabItem from '@theme/TabItem'; > Il est obligatoire de définir un mot de passe pour l'utilisateur root de la base de données. -Définissez un mot de passe pour l'utilisateur root de la base de données en exécutant la commande suivante : +Vous devez obligatoirement définir un mot de passe pour l'utilisateur root de la base de données (vous aurez besoin de ce mot de passe lors de l'[installation web](../web-and-post-installation.md)). @@ -12,13 +12,25 @@ Définissez un mot de passe pour l'utilisateur root de la base de données en ex mariadb-secure-installation ``` +Répondez **yes** à toutes les questions sauf à "Disallow root login remotely?". + +Récupérez le mot de passe temporaire créé par MySQL : + +```shell +grep 'temporary password' /var/log/mysqld.log +``` + +Modifiez-le ensuite lorsque la commande suivante vous y invite (le mot de passe doit comporter au moins 8 caractères, dont des majuscules, des minuscules, un chiffre et un caractère spécial) : + ```shell mysql_secure_installation ``` +Répondez **yes** à toutes les questions sauf à "Disallow root login remotely?". + @@ -34,7 +46,7 @@ FLUSH PRIVILEGES; Exemple : -```shell +```SQL CREATE USER 'dbadmin'@'' IDENTIFIED BY ''; GRANT ALL PRIVILEGES ON *.* TO 'dbadmin'@'' WITH GRANT OPTION; FLUSH PRIVILEGES; diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx index 904f508ee17f..6dad8aae2473 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx @@ -50,6 +50,8 @@ Définissez un mot de passe pour l'utilisateur root de la base de données en ex mariadb-secure-installation ``` +Répondez **yes** à toutes les questions sauf à "Disallow root login remotely?". +     @@ -58,10 +60,9 @@ mariadb-secure-installation ```shell dnf install -y mysql-server mysql -dnf install -y centreon-mysql centreon +dnf install -y centreon-mysql systemctl enable --now mysqld -echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf -sed -Ei 's/LimitNOFILE\s\=\s[0-9]{1,}/LimitNOFILE = 32000/' /usr/lib/systemd/system/$mysql_service_name.service +sed -Ei 's/LimitNOFILE\s\=\s[0-9]{1,}/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service systemctl daemon-reload systemctl restart mysqld ``` @@ -88,12 +89,19 @@ systemctl restart mysql     +Vous devez obligatoirement définir un mot de passe pour l'utilisateur root de la base de données (vous aurez besoin de ce mot de passe lors de l'[installation web](web-and-post-installation.md)). Il doit comporter au moins 8 caractères, dont des majuscules, des minuscules, un chiffre et un caractère spécial. Récupérez le mot de passe temporaire créé par MySQL : -Définissez un mot de passe pour l'utilisateur root de la base de données en exécutant la commande suivante : +```shell +grep 'temporary password' /var/log/mysqld.log +``` + +Modifiez-le ensuite lorsque la commande suivante vous y invite : ```shell mysql_secure_installation ``` +Répondez **yes** à toutes les questions sauf à "Disallow root login remotely?". +     diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx index d89b10209e5e..e2f6cba8a62f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx @@ -3,7 +3,7 @@ import TabItem from '@theme/TabItem'; import DatabaseConfiguration from './_database-configuration.mdx'; > Si vous installez la base de données sur un serveur dédié, ce serveur doit également avoir -> les dépôts requis. +> [les dépôts requis](installation-of-a-central-server/using-packages.md#database-repository). Exécutez la commande suivante sur le serveur central : @@ -76,13 +76,13 @@ systemctl restart mariadb ```shell dnf install -y mysql-server mysql -dnf install -y centreon-mysql centreon +dnf install -y centreon-mysql systemctl enable --now mysqld echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf systemctl daemon-reload systemctl restart mysqld systemctl list-units --type=service | grep -i mysql -sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld +sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service sudo systemctl start mysqld sudo systemctl status mysqld ``` @@ -92,13 +92,13 @@ sudo systemctl status mysqld ```shell dnf install -y mysql-server mysql -dnf install -y centreon-mysql centreon +dnf install -y centreon-mysql systemctl enable --now mysqld echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf systemctl daemon-reload systemctl restart mysqld systemctl list-units --type=service | grep -i mysql -sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld +sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service sudo systemctl start mysqld sudo systemctl status mysqld ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-repository.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-repository.mdx index c62e849147c6..9f55c460d294 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-repository.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-repository.mdx @@ -41,9 +41,6 @@ curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2025 -o /etc/pki/rpm-gpg/RPM old_mysql_key=$(rpm -q gpg-pubkey 2>/dev/null | grep -i a8d3785c || true) if [ -n "$old_mysql_key" ]; then rpm -e $old_mysql_key 2>/dev/null || true; fi rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 -# install_weak_deps=False : ici, la pile mariadb de la distribution n'est qu'une dépendance recommandée ; -# sans cette option, dnf installe mariadb à côté d'Oracle MySQL et les deux entrent en conflit sur /usr/bin/mysql. -dnf install -y --setopt=install_weak_deps=False mysql-server ```     @@ -55,9 +52,6 @@ curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2025 -o /etc/pki/rpm-gpg/RPM old_mysql_key=$(rpm -q gpg-pubkey 2>/dev/null | grep -i a8d3785c || true) if [ -n "$old_mysql_key" ]; then rpm -e $old_mysql_key 2>/dev/null || true; fi rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 -# install_weak_deps=False : ici, la pile mariadb de la distribution n'est qu'une dépendance recommandée ; -# sans cette option, dnf installe mariadb à côté d'Oracle MySQL et les deux entrent en conflit sur /usr/bin/mysql. -dnf install -y --setopt=install_weak_deps=False mysql-server ```     diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx index cb8b2f69f82b..cbed12009814 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx @@ -148,3 +148,5 @@ Vous pouvez également le désactiver le temps de l'installation en exécutant l systemctl stop firewalld systemctl disable firewalld ``` + +> Cette désactivation doit être temporaire. Pour des raisons de sécurité, le pare-feu doit être [réactivé après l'installation](../administration/secure-platform.md#enable-firewalld). diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index 5280b2443532..193886bd57c6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -159,7 +159,6 @@ systemctl start crond ```shell systemctl enable php-fpm httpd centreon cbd centengine gorgoned snmptrapd centreontrapd snmpd systemctl enable --now crond -systemctl start crond ```     diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md index 1c182cdbfe02..db8523993074 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md @@ -289,7 +289,7 @@ Enfin, ajoutez à l'utilisateur de base de données **centreon** les droits néc **LOAD DATA INFILE** : ```sql -mysql -u root -p +mariadb -u root -p GRANT FILE on *.* to 'centreon'@'localhost'; SET GLOBAL local_infile=1; exit diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md index 9ddd8667423c..dfa4c4494700 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/web-and-post-installation.md @@ -57,7 +57,7 @@ Fournissez les informations de connexion à l'instance de base de données. - **Database Host Address** : si vous utilisez une base de données locale, laissez ce champ vide (la valeur par défaut étant **localhost**). Sinon, renseignez l'adresse IP de votre base de données déportée. - **Root user/password** : ce compte sera utilisé pour installer les bases de données. - - S'il s'agit du compte par défaut (**root**), le mot de passe root de la base de données est [celui que vous avez défini](./installation-of-a-central-server/using-packages.md#étape-2--installer-le-serveur-central-et-la-base-de-données) lorsque vous avez exécuté `mysql_secure_installation`/`mariadb_secure_installation`. + - S'il s'agit du compte par défaut (**root**), le mot de passe root de la base de données est [celui que vous avez défini](./installation-of-a-central-server/using-packages.md#étape-2--installer-le-serveur-central-et-la-base-de-données) lorsque vous avez exécuté `mysql_secure_installation`/`mariadb-secure-installation`. - Si vous avez défini un utilisateur dédié avec des privilèges root sur toutes les bases, (par exemple pendant [l'installation d'une base de donnée déportée](../installation/installation-of-a-central-server/using-packages.md#étape-2--installer-le-serveur-central-et-la-base-de-données)), utilisez celui-ci. Cet utilisateur pourra être supprimé une fois l'installation web terminée. - **Database user name/password**: les identifiants du compte qui sera utilisé pour interagir avec les bases de données Centreon. Le compte sera créé pendant l'installation de la base. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md index ab3293ec8806..756b91156e41 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md @@ -90,27 +90,46 @@ dnf update >Si vous utilisez une base de données distante, ignorez cette étape et passez directement à l'[étape 4](#étape-4--synchroniser-les-plugins). -1. Sur l'ancien serveur, faitez un dump des bases de données : +1. Arrêtez les processus Centreon : ```shell - mysqldump -u root -p centreon > /tmp/centreon.sql - mysqldump -u root -p centreon_storage > /tmp/centreon_storage.sql + systemctl stop cbd centengine gorgoned centreontrapd snmpd ``` -2. Sur l'ancien serveur, arrêtez MariaDB : +2. Sur l'ancien serveur, faitez un dump des bases de données : + + ```shell + mysqldump -u root -p --single-transaction centreon > /tmp/centreon.sql + mysqldump -u root -p --single-transaction centreon_storage > /tmp/centreon_storage.sql + ``` + +3. Sur l'ancien serveur, arrêtez la base de données : + + + ```shell systemctl stop mariadb ``` -3. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): + + + + ```shell + systemctl stop mysqld + ``` + + + + +4. Depuis l'ancien serveur, exportez les dumps vers le nouveau serveur de base de données (assurez-vous d'avoir assez d'espace): ```shell rsync -avz /tmp/centreon.sql root@\:/tmp/ rsync -avz /tmp/centreon_storage.sql root@\:/tmp/ ``` -4. Sur le nouveau serveur de base de données, supprimez les bases de +5. Sur le nouveau serveur de base de données, supprimez les bases de données vierges et recréez-les : ```shell @@ -124,17 +143,17 @@ dnf update CREATE DATABASE centreon_storage; ``` -5. Sur le nouveau serveur de bases de données, importez dans la base les dumps précédemment transférés : +6. Sur le nouveau serveur de bases de données, importez dans la base les dumps précédemment transférés : ```shell mysql -u root centreon -p + + + ```shell + systemctl restart mariadb + ``` + + + ```shell - systemctl start mariadb + systemctl restart mysqld ``` + +     + > Remplacez **\** par l'adresse IP de votre nouveau serveur > Centreon. @@ -220,7 +252,7 @@ rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/c 1. Modifiez le fichier **/etc/centreon/centreon.conf.php**, 2. Modifiez le fichier **/etc/centreon/conf.pm**, 3. Éditez la configuration du Centreon Broker central, via l'interface web - Centreon et modifiez le mot de passe pour l'output **unfied-sql**, + Centreon et modifiez le mot de passe pour l'output **unified-sql**, 4. Modifiez le fichier **/etc/centreon/config.d/10-database.yaml**. 5. Si l'adresse IP de votre serveur Centreon a changé : @@ -231,7 +263,7 @@ rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/c pour plus d'information. - L'empreinte de votre plateforme a également changé : [contactez Centreon](mailto:support@centreon.com) pour obtenir une nouvelle licence. -6. Les informations de connexion de l'utilisateur **centreon-gorgone** nouvellement créé doivent être les mêmes que celles de l'utilisateur **centreon-gorgone** sur l'ancien serveur. Éditez le fichier `etc/centreon-gorgone/config.d/31-centreon-api.yaml` et entrez les information de connexion de l'ancien utilisateur. Exemple : +6. Les informations de connexion de l'utilisateur **centreon-gorgone** nouvellement créé doivent être les mêmes que celles de l'utilisateur **centreon-gorgone** sur l'ancien serveur. Éditez le fichier `/etc/centreon-gorgone/config.d/31-centreon-api.yaml` et entrez les information de connexion de l'ancien utilisateur. Exemple : ```shell gorgone: @@ -260,11 +292,13 @@ rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/c 10. Allez à la page **Configuration > Connecteurs > Connecteurs de supervision**, puis [mettez à jour tous les connecteurs de supervision](../monitoring/pluginpacks.md#mettre-à-jour-un-ou-plusieurs-packs). +Une fois que vous avez vérifié que votre plateforme Centreon fonctionne correctement, vous pouvez supprimer les dumps de la base de données que vous avez stockés dans le répertoire **/tmp**. + -### Étape 7: Mettre à jour les modules +### Étape 6: Mettre à jour les modules Pour mettre à jour les modules, allez à la page **Administration > Extensions > Gestionnaire** et cliquez sur **Update all**. Si vous avez un serveur MAP ou MBI, suivez les procédures de migration correspondantes : @@ -272,7 +306,7 @@ Si vous avez un serveur MAP ou MBI, suivez les procédures de migration correspo - Procédure de migration pour [MAP](../graph-views/map-web-migrate.md), - Procédure de migration pour [MBI](../reporting/migrate.md). -### Étape 8: Migrer vos autres serveurs (architecture distribuée) +### Étape 7: Migrer vos autres serveurs (architecture distribuée) #### Migrer un serveur distant diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md index 784bc9b0ffd5..93210cdffa07 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md @@ -36,7 +36,7 @@ Pour connaître la version de MariaDB installée sur une machine, tapez la comma ```shell -rpm -qa |grep MariaDB +rpm -qa |grep -i mariadb ``` Le résultat pourra ressembler à cet exemple : @@ -161,7 +161,7 @@ Suivez ces étapes pour changer de version mineure de MariaDB (par exemple, pour ```shell -dnf update MariaDB-* +dnf update mariadb-* ``` diff --git a/versioned_docs/version-26.10/installation/_database-configuration.mdx b/versioned_docs/version-26.10/installation/_database-configuration.mdx index faade4131d43..3b211e6c99c9 100644 --- a/versioned_docs/version-26.10/installation/_database-configuration.mdx +++ b/versioned_docs/version-26.10/installation/_database-configuration.mdx @@ -3,7 +3,7 @@ import TabItem from '@theme/TabItem'; > It is mandatory to set a password for the root user of the database. -Set a password for the root user of the database by executing the following command: +It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](../web-and-post-installation.md)). @@ -12,17 +12,29 @@ Set a password for the root user of the database by executing the following comm mariadb-secure-installation ``` +Answer **yes** to all the questions except "Disallow root login remotely?". + +Retrieve the temporary password created by MySQL: + +```shell +grep 'temporary password' /var/log/mysqld.log +``` + +Then change it when prompted by the following command (the password must have at least 8 characaters, upper and lower case, a digit and a special character): + ```shell mysql_secure_installation ``` +Answer **yes** to all the questions except "Disallow root login remotely?". + -Then, in the remote dabatase, create a user with **root** privileges. You will have to enter this user during the +Then, in the remote database, create a user with **root** privileges. You will have to enter this user during the web installation process (at [step 6](./web-and-post-installation.md#step-6-database-information), in the **Root user** and **Root password** fields). @@ -34,7 +46,7 @@ FLUSH PRIVILEGES; Example: -```shell +```SQL CREATE USER 'dbadmin'@'' IDENTIFIED BY ''; GRANT ALL PRIVILEGES ON *.* TO 'dbadmin'@'' WITH GRANT OPTION; FLUSH PRIVILEGES; diff --git a/versioned_docs/version-26.10/installation/_database-local-install.mdx b/versioned_docs/version-26.10/installation/_database-local-install.mdx index a81bd1c08c99..7d71d9da6317 100644 --- a/versioned_docs/version-26.10/installation/_database-local-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-local-install.mdx @@ -50,6 +50,8 @@ Set a password for the root user of the database by executing the following comm mariadb-secure-installation ``` +Answer **yes** to all the questions except "Disallow root login remotely?". + @@ -58,10 +60,9 @@ mariadb-secure-installation ```shell dnf install -y mysql-server mysql -dnf install -y centreon-mysql centreon +dnf install -y centreon-mysql systemctl enable --now mysqld -echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf -sed -Ei 's/LimitNOFILE\s\=\s[0-9]{1,}/LimitNOFILE = 32000/' /usr/lib/systemd/system/$mysql_service_name.service +sed -Ei 's/LimitNOFILE\s\=\s[0-9]{1,}/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service systemctl daemon-reload systemctl restart mysqld ``` @@ -89,11 +90,19 @@ systemctl restart mysql     -Set a password for the root user of the database by executing the following command: +It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](web-and-post-installation.md)). It must have at least 8 characaters, upper and lower case, a digit and a special character. Retrieve the temporary password created by MySQL: + +```shell +grep 'temporary password' /var/log/mysqld.log +``` + +Then change it when prompted by the following command: ```shell mysql_secure_installation ``` +Answer **yes** to all the questions except "Disallow root login remotely?". +     diff --git a/versioned_docs/version-26.10/installation/_database-remote-install.mdx b/versioned_docs/version-26.10/installation/_database-remote-install.mdx index f16dbb1ab8c8..a15e11abd528 100644 --- a/versioned_docs/version-26.10/installation/_database-remote-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-remote-install.mdx @@ -3,7 +3,7 @@ import TabItem from '@theme/TabItem'; import DatabaseConfiguration from './_database-configuration.mdx'; > If installing the database on a dedicated server, this server should also have -> the prerequisite repositories. +> the [prerequisite repositories](installation-of-a-central-server/using-packages.md#database-repository). Run the following command on the central server: @@ -76,13 +76,12 @@ systemctl restart mariadb ```shell dnf install -y mysql-server mysql -dnf install -y centreon-mysql centreon +dnf install -y centreon-mysql systemctl enable --now mysqld -echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf systemctl daemon-reload systemctl restart mysqld systemctl list-units --type=service | grep -i mysql -sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld +sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service sudo systemctl start mysqld sudo systemctl status mysqld ``` @@ -92,13 +91,13 @@ sudo systemctl status mysqld ```shell dnf install -y mysql-server mysql -dnf install -y centreon-mysql centreon +dnf install -y centreon-mysql systemctl enable --now mysqld echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf systemctl daemon-reload systemctl restart mysqld systemctl list-units --type=service | grep -i mysql -sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld +sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service sudo systemctl start mysqld sudo systemctl status mysqld ``` diff --git a/versioned_docs/version-26.10/installation/_database-repository.mdx b/versioned_docs/version-26.10/installation/_database-repository.mdx index 3ddc2e1ce6a4..9f55c460d294 100644 --- a/versioned_docs/version-26.10/installation/_database-repository.mdx +++ b/versioned_docs/version-26.10/installation/_database-repository.mdx @@ -41,9 +41,6 @@ curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2025 -o /etc/pki/rpm-gpg/RPM old_mysql_key=$(rpm -q gpg-pubkey 2>/dev/null | grep -i a8d3785c || true) if [ -n "$old_mysql_key" ]; then rpm -e $old_mysql_key 2>/dev/null || true; fi rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 -# install_weak_deps=False: the distro mariadb stack is only a Recommends here; without it dnf -# pulls mariadb alongside Oracle MySQL and they collide on /usr/bin/mysql. -dnf install -y --setopt=install_weak_deps=False mysql-server ```     @@ -55,9 +52,6 @@ curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2025 -o /etc/pki/rpm-gpg/RPM old_mysql_key=$(rpm -q gpg-pubkey 2>/dev/null | grep -i a8d3785c || true) if [ -n "$old_mysql_key" ]; then rpm -e $old_mysql_key 2>/dev/null || true; fi rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 -# install_weak_deps=False: the distro mariadb stack is only a Recommends here; without it dnf -# pulls mariadb alongside Oracle MySQL and they collide on /usr/bin/mysql. -dnf install -y --setopt=install_weak_deps=False mysql-server ```     diff --git a/versioned_docs/version-26.10/installation/_install-common.mdx b/versioned_docs/version-26.10/installation/_install-common.mdx index a1d4761b9eb3..31d6bac0f571 100644 --- a/versioned_docs/version-26.10/installation/_install-common.mdx +++ b/versioned_docs/version-26.10/installation/_install-common.mdx @@ -148,4 +148,6 @@ You can also disable the firewall during installation by running the following c ```shell systemctl stop firewalld systemctl disable firewalld -``` \ No newline at end of file +``` + +> **Note that this deactivation should be temporary.** The firewall should be [reenabled after installation](../administration/secure-platform.md#enable-firewalld) for security reasons. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index 26a10134800b..b8e7ba1f454a 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -159,7 +159,6 @@ systemctl start crond ```shell systemctl enable php-fpm httpd centreon cbd centengine gorgoned snmptrapd centreontrapd snmpd systemctl enable --now crond -systemctl start crond ```     diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md index f172111203cb..310e51cab844 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md @@ -289,7 +289,7 @@ Finally, add rights for the **centreon** database user to use **LOAD DATA INFILE command: ```sql -mysql -u root -p +mariadb -u root -p GRANT FILE on *.* to 'centreon'@'localhost'; SET GLOBAL local_infile=1; exit diff --git a/versioned_docs/version-26.10/installation/web-and-post-installation.md b/versioned_docs/version-26.10/installation/web-and-post-installation.md index ad17a80aec79..9e7d18edb718 100644 --- a/versioned_docs/version-26.10/installation/web-and-post-installation.md +++ b/versioned_docs/version-26.10/installation/web-and-post-installation.md @@ -55,7 +55,7 @@ Provide the information needed to connect to the database instance. - **Database Host Address**: If you are using a local database, leave the field blank (the default value is **localhost**). Otherwise, enter the IP address of your remote database. - **Root user/password**: this is the account that will be used to install the databases. - - if this is the default account (**root**), the root password of the database is the password [you have defined](installation-of-a-central-server/using-packages.md#step-2-install-the-central-server-and-the-database) when executing `mysql_secure_installation` or `mariadb_secure_installation`. + - if this is the default account (**root**), the root password of the database is the password [you have defined](installation-of-a-central-server/using-packages.md#step-2-install-the-central-server-and-the-database) when executing `mysql_secure_installation` or `mariadb-secure-installation`. - if you have defined a custom user with root privileges on all databases (e.g. during the process of installing a [remote database](../installation/installation-of-a-central-server/using-packages.md#step-2-install-the-central-server-and-the-database)), use this one. This user can be deleted once the web installation process is finished. - **Database user name/password**: the credentials of the account that will be used to interact with the Centreon databases. The account will be created when the database is installed. diff --git a/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md b/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md index 934fdb1c1204..17c7cc827394 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md @@ -92,14 +92,20 @@ dnf update >If you are using a remote database, ignore this step and move on to [Step 4](#step-4-synchronize-the-plugins) -1. On the old server, create a dump of the databases: +1. Stop the Centreon processes: ```shell - mysqldump -u root -p centreon > /tmp/centreon.sql - mysqldump -u root -p centreon_storage > /tmp/centreon_storage.sql + systemctl stop cbd centengine gorgoned centreontrapd snmpd ``` -2. On the old server, stop the database: +2. On the old server, create a dump of the databases: + + ```shell + mysqldump -u root -p --single-transaction centreon > /tmp/centreon.sql + mysqldump -u root -p --single-transaction centreon_storage > /tmp/centreon_storage.sql + ``` + +3. On the old server, stop the database: @@ -112,13 +118,13 @@ dnf update ```shell - systemctl stop mysql + systemctl stop mysqld ``` -3. On the old server, export the dumps to the new Centreon database server (make sure you +4. On the old server, export the dumps to the new Centreon database server (make sure you have enough space for large database dumps): ```shell @@ -126,7 +132,7 @@ have enough space for large database dumps): rsync -avz /tmp/centreon_storage.sql root@:/tmp/ ``` -4. On the new database server, drop the original databases and +5. On the new database server, drop the original databases and create them again: ```shell @@ -141,17 +147,17 @@ create them again: exit ``` -5. On the new database server, import the previously transferred dumps into the database: +6. On the new database server, import the previously transferred dumps into the database: ```shell mysql -u root centreon -p ```shell - systemctl start mariadb + systemctl restart mariadb ``` ```shell - systemctl start mysql + systemctl restart mysqld ``` @@ -235,7 +241,7 @@ the **/usr/share/centreon/www/install** directory (**x** is the target version n 1. Edit the **/etc/centreon/centreon.conf.php** file, 2. Edit the **/etc/centreon/conf.pm** file, - 3. Edit the Centreon Broker central configuration using the Centreon web interface and change the password for the **unfied-sql** output, + 3. Edit the Centreon Broker central configuration using the Centreon web interface and change the password for the **unified-sql** output, 4. Edit the **/etc/centreon/config.d/10-database.yaml** file. 5. If the IP address of your Centreon server has changed: @@ -245,7 +251,7 @@ configuration](../monitoring/monitoring-servers/advanced-configuration.md#tcp-ou chapter for more information. - The fingerprint of your platform has changed too: [contact Centreon](mailto:support@centreon.com) to obtain a new license. -6. The credentials of the newly created **centreon-gorgone** user need to be updated to match those of the **centreon-gorgone** user on the old server. Edit `etc/centreon-gorgone/config.d/31-centreon-api.yaml` and enter the credentials of the old user. Example: +6. The credentials of the newly created **centreon-gorgone** user need to be updated to match those of the **centreon-gorgone** user on the old server. Edit `/etc/centreon-gorgone/config.d/31-centreon-api.yaml` and enter the credentials of the old user. Example: ```shell gorgone: @@ -274,11 +280,13 @@ chapter for more information. 10. Go to **Configuration > Connectors > Monitoring Connectors**, then [update all the Monitoring Connectors](../monitoring/pluginpacks.md#updating-one-packall-packs). +Once you are satisfied your Centreon works, you can delete the database dumps you stored in the **/tmp** directory. + -### Step 7: Upgrade the modules +### Step 6: Upgrade the modules To upgrade the modules, go to **Administration > Extensions > Manager** and click **Update all**. If you have a MAP server or an MBI server, follow the corresponding migration procedures: @@ -286,7 +294,7 @@ If you have a MAP server or an MBI server, follow the corresponding migration pr - Migration procedure for [MAP](../graph-views/map-web-migrate.md), - Migration procedure for [MBI](../reporting/migrate.md). -### Step 8: Migrating your other servers (distributed architecture) +### Step 7: Migrating your other servers (distributed architecture) #### Migrating a remote server diff --git a/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md b/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md index 578889a055b1..9e2ae919bc35 100644 --- a/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md +++ b/versioned_docs/version-26.10/upgrade/upgrade-mariadb.md @@ -37,7 +37,7 @@ To find out which version of MariaDB is installed on your machine, enter the fol ```shell -rpm -qa |grep MariaDB +rpm -qa |grep -i mariadb ``` The results may look like this example: @@ -189,7 +189,7 @@ Follow these steps to upgrade between minor versions of MariaDB (for example, to ```shell -dnf update MariaDB-* +dnf update mariadb-* ``` From 79ecb3ed618fdbddf157bdd73e61612d1c11ac81 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 8 Oct 2026 10:28:09 +0200 Subject: [PATCH 119/179] Fix link --- .../version-26.10/installation/_database-configuration.mdx | 2 +- .../version-26.10/installation/_database-configuration.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx index f9514258a2a4..6f81d7e78181 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx @@ -3,7 +3,7 @@ import TabItem from '@theme/TabItem'; > Il est obligatoire de définir un mot de passe pour l'utilisateur root de la base de données. -Vous devez obligatoirement définir un mot de passe pour l'utilisateur root de la base de données (vous aurez besoin de ce mot de passe lors de l'[installation web](../web-and-post-installation.md)). +Vous devez obligatoirement définir un mot de passe pour l'utilisateur root de la base de données (vous aurez besoin de ce mot de passe lors de l'[installation web](web-and-post-installation.md)). diff --git a/versioned_docs/version-26.10/installation/_database-configuration.mdx b/versioned_docs/version-26.10/installation/_database-configuration.mdx index 3b211e6c99c9..f9c226666d0d 100644 --- a/versioned_docs/version-26.10/installation/_database-configuration.mdx +++ b/versioned_docs/version-26.10/installation/_database-configuration.mdx @@ -3,7 +3,7 @@ import TabItem from '@theme/TabItem'; > It is mandatory to set a password for the root user of the database. -It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](../web-and-post-installation.md)). +It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](web-and-post-installation.md)). From 28a3a62ec357eeed2eb2ce53c7afb322c69543dd Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 8 Oct 2026 10:48:19 +0200 Subject: [PATCH 120/179] Fix anchors --- .../version-26.10/installation/_database-remote-install.mdx | 2 +- .../version-26.10/installation/_install-common.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx index e2f6cba8a62f..6e12b8d0ff55 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx @@ -3,7 +3,7 @@ import TabItem from '@theme/TabItem'; import DatabaseConfiguration from './_database-configuration.mdx'; > Si vous installez la base de données sur un serveur dédié, ce serveur doit également avoir -> [les dépôts requis](installation-of-a-central-server/using-packages.md#database-repository). +> [les dépôts requis](installation-of-a-central-server/using-packages.md#dépôt-de-base-de-données). Exécutez la commande suivante sur le serveur central : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx index cbed12009814..a120efafcbb4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx @@ -149,4 +149,4 @@ systemctl stop firewalld systemctl disable firewalld ``` -> Cette désactivation doit être temporaire. Pour des raisons de sécurité, le pare-feu doit être [réactivé après l'installation](../administration/secure-platform.md#enable-firewalld). +> Cette désactivation doit être temporaire. Pour des raisons de sécurité, le pare-feu doit être [réactivé après l'installation](../administration/secure-platform.md#activer-firewalld). From efd6a4a37c2980c8d9e94477f113ba132ead7556 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 8 Oct 2026 15:58:40 +0200 Subject: [PATCH 121/179] Changes following review --- .../administration/secure-platform.md | 63 +++++++++-------- .../installation/_interface-tls-conf.mdx | 70 +++++++++++++++++++ .../administration/secure-platform.md | 63 +++++++++-------- .../installation/_interface-tls-conf.mdx | 69 ++++++++++++++++++ 4 files changed, 203 insertions(+), 62 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md index 3931aefd8e39..4c766c72153a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md @@ -1182,7 +1182,7 @@ Vous pouvez maintenant accéder à votre plateforme via votre navigateur en mode 9. Configuration API de Gorgone Éditez le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** en remplaçant **127.0.0.1** -par le FQDN de votre serveur central : +par le FQDN de votre serveur central, comme dans l'exemple suivant : ```text gorgone: @@ -1190,10 +1190,10 @@ gorgone: - name: centreonv2 base_url: "https://centreon7.localdomain/centreon/api/latest/" username: "centreon-gorgone" - password: "bpltc4aY" + password: "XXXXX" - name: clapi username: "centreon-gorgone" - password: "bpltc4aY" + password: "XXXXX" ``` Redémarrez le daemon Gorgone : @@ -1208,42 +1208,43 @@ Puis vérifiez le statut : systemctl status gorgoned ``` -Si tout est correct, vous devriez avoir quelque chose comme : +Si tout est correct, vous devriez avoir quelque chose comme cet exemple : ```shell ● gorgoned.service - Centreon Gorgone - Loaded: loaded (/etc/systemd/system/gorgoned.service; enabled; vendor preset: disabled) - Active: active (running) since Mon 2023-03-06 15:58:10 CET; 27min ago - Main PID: 1791096 (perl) - Tasks: 124 (limit: 23040) - Memory: 595.3M - CGroup: /system.slice/gorgoned.service - ├─1791096 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=info - ├─1791109 gorgone-statistics - ├─1791112 gorgone-legacycmd - ├─1791117 gorgone-engine - ├─1791118 gorgone-audit - ├─1791125 gorgone-nodes - ├─1791138 gorgone-action - ├─1791151 gorgone-cron - ├─1791158 gorgone-dbcleaner - ├─1791159 gorgone-autodiscovery - ├─1791166 gorgone-httpserver - ├─1791180 gorgone-proxy - ├─1791181 gorgone-proxy - ├─1791182 gorgone-proxy - ├─1791189 gorgone-proxy - └─1791190 gorgone-proxy - -mars 06 15:58:10 ito-central systemd[1]: gorgoned.service: Succeeded. -mars 06 15:58:10 ito-central systemd[1]: Stopped Centreon Gorgone. -mars 06 15:58:10 ito-central systemd[1]: Started Centreon Gorgone. + Loaded: loaded (/usr/lib/systemd/system/gorgoned.service; enabled; preset: enabled) + Active: active (running) since Thu 2026-10-08 09:27:46 UTC; 4h 10min ago + Invocation: 40225788460245609d05c9db103f1ff3 + Main PID: 807 (perl) + Tasks: 51 (limit: 4618) + Memory: 176.2M (peak: 241.4M) + CPU: 9.461s + CGroup: /system.slice/gorgoned.service + ├─ 807 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=error + ├─1073 gorgone-proxy + ├─1075 gorgone-proxy + ├─1076 gorgone-proxy + ├─1077 gorgone-proxy + ├─1080 gorgone-proxy + ├─1086 gorgone-engine + ├─1089 gorgone-audit + ├─1097 gorgone-legacycmd + ├─1098 gorgone-httpserver + ├─1100 gorgone-nodes + ├─1107 gorgone-statistics + ├─1108 gorgone-cron + ├─1113 gorgone-anomalydetection + ├─1125 gorgone-autodiscovery + ├─1133 gorgone-action + └─1137 gorgone-dbcleaner + +Oct 08 09:27:46 doc-central systemd[1]: Started gorgoned.service - Centreon Gorgone. ``` Vous devriez voir la ligne suivante dans les logs de Gorgone **/var/log/centreon-gorgone/gorgoned.log** : ```text -2023-03-06 15:58:12 - INFO - [autodiscovery] -class- host discovery - sync started +2026-10-08 15:58:12 - INFO - [autodiscovery] -class- host discovery - sync started ``` ## URI personnalisée diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx index d9be72accf15..a351748da694 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx @@ -96,3 +96,73 @@ a2ensite 00-centreon-tls + +> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez définir l'adresse `centreon.url=https://` dans le fichier **/etc/centreon-map/map-config.properties** pour utiliser HTTPS au lieu de HTTP. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md#configurer-httpstls-sur-le-serveur-map). + +9. Configuration API de Gorgone + +Éditez le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** en remplaçant **127.0.0.1** +par le FQDN de votre serveur central, comme dans l'exemple suivant : + +```text +gorgone: + tpapi: + - name: centreonv2 + base_url: "https://centreon7.localdomain/centreon/api/latest/" + username: "centreon-gorgone" + password: "XXXXX" + - name: clapi + username: "centreon-gorgone" + password: "XXXXX" +``` + +Redémarrez le daemon Gorgone : + +```shell +systemctl restart gorgoned +``` + +Puis vérifiez le statut : + +```shell +systemctl status gorgoned +``` + +Si tout est correct, vous devriez avoir quelque chose comme cet exemple : + +```shell +● gorgoned.service - Centreon Gorgone + Loaded: loaded (/usr/lib/systemd/system/gorgoned.service; enabled; preset: enabled) + Active: active (running) since Thu 2026-10-08 09:27:46 UTC; 4h 10min ago + Invocation: 40225788460245609d05c9db103f1ff3 + Main PID: 807 (perl) + Tasks: 51 (limit: 4618) + Memory: 176.2M (peak: 241.4M) + CPU: 9.461s + CGroup: /system.slice/gorgoned.service + ├─ 807 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=error + ├─1073 gorgone-proxy + ├─1075 gorgone-proxy + ├─1076 gorgone-proxy + ├─1077 gorgone-proxy + ├─1080 gorgone-proxy + ├─1086 gorgone-engine + ├─1089 gorgone-audit + ├─1097 gorgone-legacycmd + ├─1098 gorgone-httpserver + ├─1100 gorgone-nodes + ├─1107 gorgone-statistics + ├─1108 gorgone-cron + ├─1113 gorgone-anomalydetection + ├─1125 gorgone-autodiscovery + ├─1133 gorgone-action + └─1137 gorgone-dbcleaner + +Oct 08 09:27:46 doc-central systemd[1]: Started gorgoned.service - Centreon Gorgone. +``` + +Vous devriez voir la ligne suivante dans les logs de Gorgone **/var/log/centreon-gorgone/gorgoned.log** : + +```text +2026-10-08 15:58:12 - INFO - [autodiscovery] -class- host discovery - sync started +``` diff --git a/versioned_docs/version-26.10/administration/secure-platform.md b/versioned_docs/version-26.10/administration/secure-platform.md index bab8786de7a7..8371ea8733c0 100644 --- a/versioned_docs/version-26.10/administration/secure-platform.md +++ b/versioned_docs/version-26.10/administration/secure-platform.md @@ -1187,7 +1187,7 @@ Now you can access your platform with your browser in HTTPS mode. 9. Gorgone API configuration -Replace **127.0.0.1** with the FQDN of your central server in the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file: +Replace **127.0.0.1** with the FQDN of your central server in the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file, like in this example: ```text gorgone: @@ -1195,10 +1195,10 @@ gorgone: - name: centreonv2 base_url: "https://centreon7.localdomain/centreon/api/latest/" username: "centreon-gorgone" - password: "bpltc4aY" + password: "XXXXX" - name: clapi username: "centreon-gorgone" - password: "bpltc4aY" + password: "XXXXX" ``` Then restart the Gorgone daemon: @@ -1213,42 +1213,43 @@ Then check its status: systemctl status gorgoned ``` -If everything is ok, you should have: +If everything is ok, you should have something like this (example on Debian): ```shell ● gorgoned.service - Centreon Gorgone - Loaded: loaded (/etc/systemd/system/gorgoned.service; enabled; vendor preset: disabled) - Active: active (running) since Mon 2023-03-06 15:58:10 CET; 27min ago - Main PID: 1791096 (perl) - Tasks: 124 (limit: 23040) - Memory: 595.3M - CGroup: /system.slice/gorgoned.service - ├─1791096 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=info - ├─1791109 gorgone-statistics - ├─1791112 gorgone-legacycmd - ├─1791117 gorgone-engine - ├─1791118 gorgone-audit - ├─1791125 gorgone-nodes - ├─1791138 gorgone-action - ├─1791151 gorgone-cron - ├─1791158 gorgone-dbcleaner - ├─1791159 gorgone-autodiscovery - ├─1791166 gorgone-httpserver - ├─1791180 gorgone-proxy - ├─1791181 gorgone-proxy - ├─1791182 gorgone-proxy - ├─1791189 gorgone-proxy - └─1791190 gorgone-proxy - -mars 06 15:58:10 ito-central systemd[1]: gorgoned.service: Succeeded. -mars 06 15:58:10 ito-central systemd[1]: Stopped Centreon Gorgone. -mars 06 15:58:10 ito-central systemd[1]: Started Centreon Gorgone. + Loaded: loaded (/usr/lib/systemd/system/gorgoned.service; enabled; preset: enabled) + Active: active (running) since Thu 2026-10-08 09:27:46 UTC; 4h 10min ago + Invocation: 40225788460245609d05c9db103f1ff3 + Main PID: 807 (perl) + Tasks: 51 (limit: 4618) + Memory: 176.2M (peak: 241.4M) + CPU: 9.461s + CGroup: /system.slice/gorgoned.service + ├─ 807 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=error + ├─1073 gorgone-proxy + ├─1075 gorgone-proxy + ├─1076 gorgone-proxy + ├─1077 gorgone-proxy + ├─1080 gorgone-proxy + ├─1086 gorgone-engine + ├─1089 gorgone-audit + ├─1097 gorgone-legacycmd + ├─1098 gorgone-httpserver + ├─1100 gorgone-nodes + ├─1107 gorgone-statistics + ├─1108 gorgone-cron + ├─1113 gorgone-anomalydetection + ├─1125 gorgone-autodiscovery + ├─1133 gorgone-action + └─1137 gorgone-dbcleaner + +Oct 08 09:27:46 doc-central systemd[1]: Started gorgoned.service - Centreon Gorgone. ``` You should see the following line in the Gorgone daemon log file **/var/log/centreon-gorgone/gorgoned.log**: ```text -2023-03-06 15:58:12 - INFO - [autodiscovery] -class- host discovery - sync started +2026-10-08 15:58:12 - INFO - [autodiscovery] -class- host discovery - sync started ``` ## Custom URI diff --git a/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx b/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx index f84256a593d9..4c7db0b7e503 100644 --- a/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx +++ b/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx @@ -96,3 +96,72 @@ a2ensite 00-centreon-tls + +> Once your web server is set to HTTPS mode, if you have a MAP server on your platform, you must set the `centreon.url=https://` inside the **/etc/centreon-map/map-config.properties** file to use HTTPS instead of HTTP. Otherwise recent web browsers may block communication between the two servers. The procedure is detailed [here](../graph-views/secure-your-map-platform.md#configure-httpstls-on-the-map-server). + +4. Gorgone API configuration + +Replace **127.0.0.1** with the FQDN of your central server in the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file, like in this example: + +```text +gorgone: + tpapi: + - name: centreonv2 + base_url: "https://centreon7.localdomain/centreon/api/latest/" + username: "centreon-gorgone" + password: "XXXXX" + - name: clapi + username: "centreon-gorgone" + password: "XXXXX" +``` + +Then restart the Gorgone daemon: + +```shell +systemctl restart gorgoned +``` + +Then check its status: + +```shell +systemctl status gorgoned +``` + +If everything is ok, you should have something like this (example on Debian): + +```shell +● gorgoned.service - Centreon Gorgone + Loaded: loaded (/usr/lib/systemd/system/gorgoned.service; enabled; preset: enabled) + Active: active (running) since Thu 2026-10-08 09:27:46 UTC; 4h 10min ago + Invocation: 40225788460245609d05c9db103f1ff3 + Main PID: 807 (perl) + Tasks: 51 (limit: 4618) + Memory: 176.2M (peak: 241.4M) + CPU: 9.461s + CGroup: /system.slice/gorgoned.service + ├─ 807 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=error + ├─1073 gorgone-proxy + ├─1075 gorgone-proxy + ├─1076 gorgone-proxy + ├─1077 gorgone-proxy + ├─1080 gorgone-proxy + ├─1086 gorgone-engine + ├─1089 gorgone-audit + ├─1097 gorgone-legacycmd + ├─1098 gorgone-httpserver + ├─1100 gorgone-nodes + ├─1107 gorgone-statistics + ├─1108 gorgone-cron + ├─1113 gorgone-anomalydetection + ├─1125 gorgone-autodiscovery + ├─1133 gorgone-action + └─1137 gorgone-dbcleaner + +Oct 08 09:27:46 doc-central systemd[1]: Started gorgoned.service - Centreon Gorgone. +``` + +You should see the following line in the Gorgone daemon log file **/var/log/centreon-gorgone/gorgoned.log**: + +```text +2026-10-08 15:58:12 - INFO - [autodiscovery] -class- host discovery - sync started +``` From cb7511b1c6ac2edd6fd649578e0f43f0557180c3 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 8 Oct 2026 18:09:38 +0200 Subject: [PATCH 122/179] 26.10 Pollers in containers (#5629) * 26.10 Pollers in containers * Unbreak build * Unbreak build * Typo * Unbreak build * Workaround for zombie links * Add temporary FR files (workaround for zombie links) * Fix link * Fix link * Fix link * Try to fix build by making a dummy change in monitoring connectors section * Fix anchor * doc: use ghcr.io stable image in custom Dockerfile example Align the FROM instruction with the install-poller docker.sh script, which pulls stable poller images from ghcr.io/centreon/centreon- rather than the Harbor docker.centreon.com/centreon/centreon--trixie path (only used for testing/unstable channels). Co-Authored-By: Claude Sonnet 5 * doc: use ghcr.io stable image in fr Dockerfile example Same fix as 03a5b27f7, applied to the untranslated fr i18n copy of using-containers-advanced-configuration.md. Co-Authored-By: Claude Sonnet 5 * Pollers in containers * Fix links * Replace docker by container * Update * Translate topics into French * Rearrange ToC * FR translation * Update screenshot + delete obsolete ones * HTTPS + minor tweaks * Update * Update * Add links to HTTPS procedure * Remove unnecessary example * Add translation string * MON-209967 Note about poller prerequisites * Update version-26.10.json * Corrections EN * Corrections FR --------- Co-authored-by: Tpo76 Co-authored-by: Claude Sonnet 5 --- .../version-26.10.json | 4 + .../assets/installation/connected-poller.png | Bin 0 -> 23027 bytes .../installation/create-poller-banner.png | Bin 0 -> 10427 bytes .../adapt-legacy-pullwss.md | 98 ++++++++ .../pollers-containers-prerequisites.md | 223 +++++++++++++++++ ...using-containers-advanced-configuration.md | 233 ++++++++++++++++++ .../using-containers.md | 174 +++++++++++++ .../procedures/virtualization-vmware2-esx.md | 2 +- .../assets/installation/connected-poller.png | Bin 0 -> 23027 bytes .../installation/create-poller-banner.png | Bin 0 -> 10427 bytes .../adapt-legacy-pullwss.md | 98 ++++++++ .../pollers-containers-prerequisites.md | 224 +++++++++++++++++ ...using-containers-advanced-configuration.md | 210 ++++++++++++++++ .../using-containers.md | 170 ++++++++++++- .../version-26.10-sidebars.json | 37 ++- 15 files changed, 1462 insertions(+), 11 deletions(-) create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/assets/installation/connected-poller.png create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/assets/installation/create-poller-banner.png create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/adapt-legacy-pullwss.md create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-containers-advanced-configuration.md create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-containers.md create mode 100644 versioned_docs/version-26.10/assets/installation/connected-poller.png create mode 100644 versioned_docs/version-26.10/assets/installation/create-poller-banner.png create mode 100644 versioned_docs/version-26.10/installation/installation-of-a-poller/adapt-legacy-pullwss.md create mode 100644 versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md create mode 100644 versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers-advanced-configuration.md diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10.json b/i18n/fr/docusaurus-plugin-content-docs/version-26.10.json index a9881f3dfeba..abbfe11aa7f4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10.json +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10.json @@ -343,6 +343,10 @@ "message": "Utiliser MBI", "description": "The label for category Using MBI in sidebar docs" }, + "sidebar.docs.category.Pollers in containers": { + "message": "Collecteurs en conteneurs", + "description": "The label for category Pollers in containers in sidebar docs" + }, "sidebar.docs.category.Manual setup (advanced)": { "message": "Installation manuelle", "description": "The label for category Manual setup (advanced) in sidebar docs" diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/assets/installation/connected-poller.png b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/assets/installation/connected-poller.png new file mode 100644 index 0000000000000000000000000000000000000000..057601c0e7afa2d8f2e451e82a80458206ded3dd GIT binary patch literal 23027 zcmdSBbzD^6_cx0A5mW>N0cjNhB}KYTIz+mqo1tSU6$NPl0cq(RkQjy<5G5ps9D3*& zYN(k32AJoV-|sK(bMO7V?(@ezuNR&@=j>Q}?X_3D*FJ_mQgI^ z5;7SQl2bzGP6JPHt94_*?UdVdxkn_Wy^Lt!$3NB&RUVR%lt+^vnVtoHpLdqmb0Z<4 z{PyGTR6D4^0(f}U{i&|I2FS|Y%hc79M9$UH(#g#R8tM4>>Y-iM+c>eOa(-ogyzV^aa962w>np_C)ivAv^ zc;~hHjW3&)_6MeKzOY{o$~t%Z)w=P6k0rMs-ilkfon&GitNgY5c2YN@yLPxq`uLzh zCS!BZx>roVzt=~)s91FH7|oKwl3%|ZpJ%Oo1t9mw^{JwcecrJ7k8ND~O#QF!)`OE;kpZ{q;_Er$hCm%-i@*Q>JCX zisY7L(;M&~%muFZ>WW~4TQ4G}=`O#GKe>RH1L>bzYU4Am*|wG%rx_j>K?Me0_gW={ z3q0c^V8fm;44G)n#76}-28Lfr8*g9cqo}5aq|NmB^3|`Wtko|%ka3j^TerkV;}(@c zX{~#T43XD2&ixwefw__@2x2&JIX^l;vFK`t4K=0`$A70t+IAvJM^PCB{WP3Xw%Ftn zv#)EoI|mkt-JQHn3MkM^gV-yG6_ibyGO|n!FljbR4}fCyPI%O=UC>AE6BGDJnC}CALqWk8_-+Zs$}B) z)yYfJ*i=;BVv1FTfhXABVN6wcaKJ#Ob8pH!+vv7_kH6nyE=;CTPEIu4j) z|4=deDtcpUYpcwB7Sc@ zk|H|`3kw^Ym6_%s;JTloq5zVUlZ$4S;uQHUTOH*$&?-TZDe%Et-_@*ic_WQ?s@>@A%KdL5>0_+nEjY>D$bvUbsA%Ijw%_ePb%egJuGkY+G(Bc{zGLv0v^&7~!wMj* zw{{@6NOIhJRNL9e>-%ytJIhqtzqx0_ek%t81{e24%hU}_c&8gGI{lvIr}IFk;%LXC zrGLz;!z?YO3E3kN`5woJ6U7FdKax{<^`@gG8p8h0FjC}BP9DtFUvB>oms9}O#^=I3 zd&P6DK~&nmh4Ll)tw-Z_`LM&I{cKjaiVp^2Ui^C+eJfAo4X}Gi@50yE%cZsHM)xfL zzUq4-FR}QSvCmZghrImXESqN-dZSGxCF$e30_C;e6eWee_gqCo3{R=>Nx`S~wU?=7 zMn_%09cq*sr0fm?(foNEOEPsxHp#ouVDZ6 z`a#dTFOhpRT5++c0LueX2?pSG{33&e%J0_6SN^n?+Bg*VHhnFX=6MX(qx$vwlhuG{2HNvPRfxL{!~coJ?gOE5tF{sE>&-TZRU@3-)R3uK;aE|yvxRv zgdFr93{3TB6j$YcoN{0V$rlC;w$~va8yrMFu{9i~&}2QpVVmdrW}HALHf#Ez-b%Q7 z%!~N|@I;-!5&gx@NxKat)qgRl;0xCSV2;2LM!ucn$3gv`-Oq-VY`=*aC*4aJX6_xn z;63Y*x&^ij#!W*Kx5;hZeuLyH|Ev8+pCA0s&)O4CZumY-8~oYWjG<|5X3UuIN)OXv z$n#$7EmTuS1$>H!Ts7%GGd_U?aVLflZ@1Hk-`e1lap=$G1}X~g*IR6x@C*{) zB{6?3O1y1zcA?l|zCgzp10gPVf$@L)M*L-QE_Fi&3e4^&HApkUimx zj%OZ5{82?O88!HIUjh=Pp$ASG{I_-dwczrTAKSFSbPVnr^{jVFe1ii-=oqa{aDLDLtl~)IlM{`y<8#qA|;zq`0Nsf}*HBq&X<85E-`~ z)V;34zvvTttV5a9(ae!@SD-etjm@6&NA&{b--E=Uz(B2GaIF9PB>3GtNwo@M=S=~z zE`Z6Nbq>>wMl_B$Dw6KUG1wVaEd6NtvU5Rzqi0!NiwO;BM_to^aEy^9jis1%?%pPp zG2V}>yhuse>EXAru~A`jCI;H0>~v=s2{9leC5_rAB_&;5ORN3U(e34&GF}M|cdQ1} z_Igx)sb@E&Vj@3^a?Sr2nZAc}Onk;}2rfJE z#X4x9{|G78yo=&!suG=IL5zQF<(e=%JL?)W9`wzOV?IQ}GD*3Cf`Vm8MwwRq)%rs4 z)jd4EONbQ%$ER~Mtw>7ph9x*$1;rN%2i%?0{V_)pYQ^sg@Ce}u>*E^Fv0}4E?N6jv zqd0>$vC|FfD3L`&L<-)R#)bB?_e5-K*R*1oT^@|@IB%_$xKgoPp9g_FZZ*R&+c%0# z!QHAvtB6kKOX*XsbDJZU3j7`7z$z9kXsTL{NKY74*IaAEP8O_DYTlKq58*y{Da=;O_NwmZrt8>A%v>OKo1M&KiqFo9GK{Q zt)z$O1{ktFTK>2(>{f+&JEflZ4f}PwdQJU337Gn=O# zXG82EPc3s{dO`hkDxgZ)ZlU!O`%Rz4zS%3jC)23j6sZexUM;%(G^3mv;vCeW5b#AEV(J(Zf^oD_=LAvdD3$Fc>GmK)kq2#zlD9jAu{3>o^@(jyHh{_?Ra@hYQjD^!uYf%MDg2ANdU4 z1&6U-OIpl=IKY9FktgmxsMNc%UYk9XHFOmrQ| zs8!p%5k=!uO{Yr5D;rZHoi29hGfV=L!S4s~d!EB0 zTjhYYU4|2a*W#B!vg{}x$`q-D@?4TGmhmknRUVQ?CHQ8K^o&PZsq{t1b*s_J zUf-?cNH2{l z-T7_OZ#$(ATmvbl2r|_;!>zuVxAaOM+rFo7UZH>l(?I23`({zizwFnq6b0Ppisb>mo&SrrU{27QY1Ehs;LWC04>!irjlEsze?Zq{6X~YkhL7S z&4hxt<7;q^j->6Hzh{o?66w6|J;T+>WEor2jB@{C8ueFn>)bJ@)qcl;9H}nG=j|9R z&+ooq{o?}hTXwu+&%UilX1dJvB!ghiQd|&``U{Sh;9?o%#_B^>IJJaOwL?D4O!-g= zN>i`_yU)WFp=<&!)-ETPV_`H9_U_s^w=?sZM%GRbbm6D%V=Hz7ua#!&ZyIyEqH6Ra z=FVI6{B$DYJ3hn#5r^i{(wmvZ^MFK=xomt5L?=~N9p|-Y6RpK!(FLhhjKU{p%sG3p zCebtJydq&Y3i^ca!d1o<$2e6$*t_#x{|phCna|DLo}X>MConMWVK9;U9i`cE*WA*Q zyCB^GnkA(}{&6C7(17?*-aMt$eK>xTF0yQ3!o~#5XqyiUMoIPR7r?t;SfkMp+Nmhj zm3~Jb1gfqmPoLe6cRsh<^c0*7FrxKuAv|l}r1{|c>>C>CUU+~tV#@^I zP4A@#1nGlyql9c%B_EvdqR-gkqhTsay>!a+b z@n#SyEwl8bKUVC#SmBX|WxutM3E#77FLAlefND_h08S!ZYzyhM){)+l-Ff3KoaaiN zl^@126!O8oZqR^>UE^+S4F6fnxvvM_7>KlGVM$B^SmWA8E6Y(TFZaC7D{qZ)hU-0;iP4I*p{-30fl)YaDpGaR*w zNkw~N6J-RL3j(H;a$%b^NN`^~3>bC8mWESk#sWx1 zNqU*xtITxNYUR@*`@qYH__jqrlnl8ZE8qR;=UGta!vY+&v{F4HbX<57+^{&;w{X%w zu41g)bG|AHG@tytli0DLN&}Nw_;w022AWYvahpZ!?s+tXSaBvzi=EfB=}|K;Yq)BU zU_Q(RmCt@fz(-+FHD2>DDTYYghxM+^r{X?jRBfo(=Za?GgAQB3Y&@ z)?T{NGsy%1R_pUfr|1|+^84Vz{zwd6#xGy>JQxfP4hbPom~W4UL7^Q3mT}SXy`sM~ z90MI)3>R%U5NcK!8h1SY2`Fl^{|+$ZK~lh=VwM+WtzA1A`MadQccX^fRegY@LX%7a zWINw&fKY09KThehKLMAX&YUzwb0IBFE7UNBAMQ`sfO+XxgQj`A7UTcyj)QK6T^~&? zIq+J!NUP@BFVpvNN3!FDE2MkDN>(5bhE+u}{?I1RlKhr(e$1a0jvY-gE5hC;-1rfu z_@w`u)mDd9r?OLlOGolA?{zi18vWNQbxV31w-_gLo$KpzILVv6V z$@i2h00Xdk78uy1yp(JV-2OvMNwO2XNAn;62$rj$P#|ztk#$$Gny3c4aXfS8OvS6t zp)VVH5cZz{`3;@FAj6I5|6x%v2WD<=PIifT9gRl+Nm^)Xsi`3{ABVKHw_Dy{Q&Reo zvLJu^707|Kw7fC=o44q0X=&Noat7+ItP~g~#G;}iBdIT(6{Gz*Q9$w>-#%&%I4!~t zmvUd}`~Ll1>L0A6pc)AK9*0ndCINO-P3;n&^6w@uZSV2(_YV%TTCwNBjEsz2|70sZ z39rllD|ca)&eZV-_$B$$UCFBV2P`D{=;L|&4+05bFNi3MzsZXiOJgzIf6=#YNr~8= zWR%nBXVZ>YwvmJii;h?d2H_R1KU`2u27~Lpx6P7<*mWDc%Nw(7cVnad7Fb#ID)flz z$8YYRg(Qu>+(ddH95s!i4QF8ea?(371F1S>x$wNUV5Rq`;)r2@*{RN(b6RweCIUOKtUGT8S|P&x})^! z@av=T^4-dheojaEB=LKhJ)4)WrF|Z|s(PG;?gm{Gr}A1&QovH#Qyibd*lodBF^Lmf ztG2h;+(|c(3(~|Jy*NUmDuOA-cU*XOM>0Q8MsLR4jKBvq8nZ@Q z!M6w6BE%>m(5iC!H1a2L(pQ}(R|WC%BD74E}7# zDcOPFEQsvb4D4AIZo2K$lX|VbyZ9}LjpVSJen>}SoJ{sV{V#S5sZyh}e3nKvr&vi> z&PF?E&-YAz{zzu=-klPP_<$Q5*OG;BslFelk0Qj{bTwz$R8Iyp1Rg}XXp-Dfx|f_q zRUm8wsVtTbYyBdK;r#lrFw)$d9A`vUB#SCpk?Eoe@icQuw~07$pS+>B$e_{ZfGd=q zL8uYMGU=F1-sj~`(b22iO#aU3vZM>^l?}~jsK1>TBl*mbCF?jc!M)mjT;H{l zx7p06f#R_}Rd{uYCZA1^=+e5aV@%~p)o}+XY<>E}nJ}4JCE0*QDc|~h-6PkN(}w-v zBH3PJm(thIpPUhws}+8^w^IaJB%!!qW8VsYMEqp9$v-cyQPf;mc1!Jwougw4(nn~Y zyP6x()@$yJ8TYyTz-LdO+~<(mT#Y67aLX;;BXFqtMk9B@RiEeYCdNGG`Ut2Psv3lZ z>#;1R^^??sN@=Pw#nJ}a~ESHc?aG#&NmKTX*3N1+Q1DEW1 zbsY3hEweS+AIO8gh1l?U=O{7f5G%#c#M@B#>k=|79U1f|MZv7}CLZ|nU*K8wLO~B{ z%8HR*5fHyHIZgK#Fa(Zpy;Ey#t;@AUUsHOegx0w_&_BHRgS1tIi%nJ3^qxp_3~|9H%H732Wb7N70r}x9jyEqO}pRlb^ zM?0Bu4knjy-b-?fLDi!k!lay+P0prSn|OFq2MukvzEk>Wnf;Ifb9a{OjbewD7SpVx z%L>!gveG&&%+rylx|E@^)EQCp5~pNHhK2Wcl$qDa?guv81(gozhoL?P+}!miX#@9P zI=^9pSV$DU)gHl58Hsd>(yG-fc90yYP3S*bYV_z(qL+20?#YA%xK>-&F!38xH8DnM z%`@Yy>+2Qc-EkTGU$WGfxbowH-GYUzx^zk zAh98?k!&5|yw$1kM$JLP>6ZT0<4>T+Tr=XN+Z{KePv6lHY?w1$lC1B#wXW_b2k z;80=u_3lq53LPS6s4pzF`R5xM44c(A%|*M)3x2LS1>LPeGVgF@@u=Cz&Kn>ZBUh}T zp;HcFl{`JMs~pyPBR=GV-!bPa4br6Yj&De)^>#alDjb(Ca=?d4^BG5rA}WQhj(@Jb zKE3{a`fBrOpD-7M5ScdEJ~&&^gqi7aTB`04tp7;-Y)Pl@+oM2(cUD&VTxI~cU&=@z zlpepYDL=H->5#JOt{xt7jnaa=tpC9|?XR#*I<^rM^Vhk0b0Iimy(gwVp@2tRWP=;M zDWjt`$+q_J`MfQ_t{6ZAHbu^phEE`D6qX%^rFu_swijiyyts8n(UqI?2_%;^1a9e80wtoDntlA7!hlZrCD&MWNWV+5a ze!?tZhkRl@jNZfrKlv6mp=AHh@?8nj(qe`qJ(b~z;FY7y%H%$7M`*74b844Fq3YY# zS-AC5=XB>Pmegss-AO8H1u(=bhPGY{4~S2K3TxP^ z*eRszmXp7=4JYfLZ?Ea{FK+M2(rMl9C=JCPcT^>4A*rHPYI1~IED=IOHrm)b{8rsd zu{=ByJht{O=a={6?OUY^FcLJhb{1AV*o>+?w~PLAgA-?vsT=g@UOtV!wGK9_Lxjf% z{kK)+nq+%nYpL)#1^rVU5!-hSv>9G{1{EVcFFg}G4Jp59G0P}WDv+!Fj9`;~D*~H6 zcF0^(Y1=@x(RG8g@~A@BgcSdf#FCuM<|y7d&8POfiy1%KUgP!g=GU`hiSr!R)csz2KJ@YIRm)utd`X|Rr9asPHkvZf=4p%$VPPp2M!xomqRK&Kjg4F=Y(oZDkHY6KQPzz&rR(Jv zyc{-jWh@Hzj2?dD_R#QF`kHYUoUD19&HkDG$Omzz+g16;MxiUyGL=|}akv+4(=(1t zi$}y(iNUC+{?t^y;?WWPMJ_^#M%ES!jOnJVGFN%SC$uPX_oYP7pV4F~jw-wIK9pa2 z{^o+H2L19Gx7!k==`Nek$iFo^OeH>%%ap;bNRn#xam`6GoS{C~{z3XvNoBDIx~lQI z)p_4k_S7MDDO(Y~^GsK9ud4-50$GQZk9pPB#OGUvKJUqDJ=U)Or$%+GjqU4LMBCE> zy{7Yr=Pn*l&{E!kgg(jE3!Ll_H(^V6D%qvUGx8Bp-1f39O8hv48IQ<^Js9L~>ck;F z8tW4VsXgAEJm%SEkVwA5p#gxg{|LBeKLL{~vuCvQi}82wg?ZrdmA_{|0yUMZ_er(-#41vOck46S*Ax4nq> z?n~cU8~d~(4ODvpcE(T)od%|tV~g=!Z0>PeFZPD3U2;kvMB&3q9KU4}fLbrn&2TUC z6{cj-<+sOyd%Eon%lHj3$QSk zg5^gW&8W=KXb2aOq+*dmW+wCkgJ4IdUzEJiFE=}jc2tO?qMG;hCByhv;JfW5tTLvz zU%B}jGz!e&>M5D;g-)+UTn{`9)?juxU^;s zMzEc^Y*nS*HP11124zNLoXf(OD_`qplL|oT4jm$4r|_`@O8!ZNTg2;e!&~b(Hk?rX zb{?&#p8>MrW}km;W^d!F-v?)DSTDh&qqtQ3ZJP%lOg2faB~!7ty=WFIRg|PLWv6u= z5*p?$rT?wkJ!-TH<6hY4QD#5gUE3u_25mm+6fK^Kkx&s0((9C<+dsQ!+3XZC5T$n~ z+*69PiD`phLkjsx@p^>9RXLC?PG~$eMc2|kql4m_7O1FQH+o&8R4RYg88bzqY2$mG zf+<8SH+(js{wRVeX$?=jzV>mmVOMov!o592E;yZl|2o;Uu|IP#l~L2+ysGt9qipr0 zi_gn%#Z4-sZf<3efg>b%QCu3p7N5eFQwK-Uj?NVQ%cAkTR;lllrozN^bsBGX=(NaQ zMzKDjb}%Xo{DAcouH+PXo2wp5TAO#Dy?AzX#kb4k$c^xN>fK<*rAX#jY?+(8Nx)ud zy^wfjjjG&s!`^NH{2Z^9DbIXddGYG75O&vPa?7Q@z1@JoswVWU9&`gm>$0ebwJect zhddtl8sExWmQok1Oy@;Q3f^#Sdc;G$id=fg>9iu$-YD363+d5~uuI|$A~8@Y zvc;|XC(v}EJ4(riw$)WT(RqrKBR0De3*z_I7|a6;_t+jb(-kjv-)mZrH1PrC`DK{> zbW@SW*&0BeiB80ioY?~tI>tVWs)L7EL@X*nP>i2{Z?ehDe{Ud4CN0o;b|(hu#U4$; z!XhqQ=dt|7C>rZ`7*-l>40i7c?&z=Sp_YJC#7-u3Me54U<~@5uXCncpsUwNX zmpYsceFtnuDpRY+>t$uyydGEwl4iad$a(52Ue8_w7l==Z>RqVdN=Q7Umtuse_;p0b z-7zTf>DqInNZaAiKw*1ih7sPB*nY{xd!R&*Bh7m^yizU6Qq)rK8H(>kcVS1BJu$rE z#G_PuDqpQj^eq*Yp_I3wI&79DD4?$%K zm5fXtXOm~9R3yJjZ!RB}5>&9A?TM33qo*)y(3{Gf7JrjM+wEczprNR~W*6d+p*-iR z&$ze{FR&?o{7nRNdfq5^Q`4mND2hX;f8{LOyUa+(C;8{JM!70`YlSO5t6I6Z8CbIi zCi&P6s9B?)6Hj#gn?rtBdT_E|8a20I@!7`JVsEs}7<0g)g9C)5-)np^S^N5GF08C^ z6+S$tHDF*8YKHSqHA^o&)+i_5Z0s&p%lcSrgjJVW6UljVp;K7(4!hH*r!jlES9aU# zRXcD4_t?A2x2G@@iK|7*A}098t)*}E8Rs_dHKfGf85m|Sd+DV#3whqfxD{{Y)pa;h zJMLj3iN?pcfbHEEhpkoRUK+?vai}#ZEWiJ-tDAmym>*G91g_Ye<+DHGCK@vMX|`rj zm9KF_j7o;2=hE0xSHGp@A3rZ;%066KA#X=A5#ml2 zuO?IWB~TzjpLr=!0mY&CIYjxku~~YyA;)b!Rg8LN&i+E+I~Y&t)hXRk^3&P~fR zoIR3QrBW5^@H^f1-ShY|G7XjN#%RDxFos8M!UYDhCuT!CxJDWdni+^bxHzLj4cMu8 zl=Q)ZMxvo>q4ZQB@k|bkjRHlmXeUF+)HokBzwMHcInwdhK}n<3pDA(3$&v+Z#r4LW z*v*u(FccrG?+HHvGu%<{_K)AWuEVhrM&C0C`mmTge2rQjr4!_=-DgL=rh4k*-n2qB-o#-Vkc_e5HKtOa0leg)coRwt>7Do|-QZ=*&BN+QqNfE2KDSBjvR> zlbn~R)!jCdP|D`iBzZ3O_9Xtss<-1X9!m}!iHA0@j=ejLIh^bPg%M7n+UKkJV!a5T zW7N$8(Njek!6jvillx|c(vOZ1b1B!bsbkRQxo4unW)Dw|=pSD1iykrfsEHDP6jJjX zMX%0(pfadC;To+v)~G-LX+9j0g?i$GhhwpY-M*MA;6&deVeZQ(SvgX@W+lwi0f`wX zaqW(K!#!{>VPI<>k-x>t5LS*Un%Q}Cs?Eggk?dqIlY3`jK_ds}2_E`j`=c|B zBb889&{{U3f$E*8keFI+)NX+PGj#aTFt_A%5s|{kgf*EeP%~fa81LkhfJADBM_vkk zv9T}zoL+~i-ZRtPSfCY|N~qEiTzV7lJoL2s6H-vxcj!jidPdDiOP{Lgd{P2rVCf7rHeTpEV*gQ~GF5b*fcBv;TOw@6B2ZeC}9ojn&Q4!U9%b z{lzYDO+Y?sH=NSSxJ+6p5y3}FSIrm9K_|2#FAD7QKskl#VBg&I9WLr+F*CTy6z-t6~k*3%+N(#-`Q+i&6L!hXIBG|xfb1=OS z5qhXE!Cbt_Oz_^=xRti@u)Xj3w50W5eOt=hx{zBrfBlfiQ*+3gq=lT=$b-tUGk0q* z;8f!jtqZdx*|#f)bNY#G%*S8$Gj7@MCpXu0c-Vz8OhYv}8WoIB!BfqnkWO$AeIqHcEM2F+DX>g6>gGSd=uc9uc8i-X)&yXpmRdP{FdBX?N|M7V z_4hBe_+*Vljnrg4aa#Z^=@IVM)i6b6_Il@jxx-{))H|-I=cI7hFWz=bsbUeKPja-7X3pNKuH5gyFCIvkiZ} zx(HR|>Xk|fLg+JoE{eG)-ZSrU&BocPQWX4{>)8lx&3z19W6%I=1JU_X2Tj0e^`$3# z&em7A7QTj?k8o1m|I&3(mt*QKjLYv@%3yUC7YDttVXMYER{o4dg}<{Re&8 zV@`%Lw2jj3%K58JceBI2`?C6j(p(1Xmu%;IHYq*UUTn%)v&c%OKP_V~EvETL;A&Ul zw#}vK_tL1-J9+9n)DqAO96kL-HjG8(2HDTPNbCavYO=}xR<{4>oe*iWDk~US)$UM^ zYGqcXQND~2qTdat+b^8?#N>Iqe*boxNr$uPBcJ6foouIS$;}y-)C~k8`fa%*akq-6 zu9fgXrWkM}C33)~?$TlT{z=$dc&>ZwegFmW&O0~kerVXs?dzZwf7;TkYj#A0;nLk@ zJWB7PnlfkldRTp#tvLw=Z(2}fez^mLiFYs7;N?(UW?ImEU`5>;1LT;9 z-tK)-DM8krzIA%i$-L|iO}i)lnzWl1o}=l0mFKsGt%78kMwqj6vr!s{(PzBcGX9sd z56})IosDBqr$180#kF_&1!}-m)v5z5U3Y2#)ssyi`Q&i^5<8N9mggDivCEh(frIAL zwN3b1m%juh8NdC9S@KBI zE3*&}y;O|{E8U#egGHt_3<&iiglVSh62LOVZ9Hx>o|UqeaM?pg8nM8umNkg>FIwlb zCp=XsDQM-|+fXORz9Lgi_?81BmV>V`T1}~pp+QD(_p0ASw2}y>pJev>iX3|plBeVc z;VIHS?k#~b;C};^m=1v0=vEyMO*r6hHSNzSZPqTQyCI~?0Q=n|GTq=jo0Y57-6XV@k_m&(@D=4maF8>+zmiNLa{x6fZhNQ$GJe5GSsI37635yWIIlmt#^5{ zs?_6}Zm&%~_zRF3@hwThFiL#*DcJm089w@=T1zyNlo`B|xr-pCo_u}d?s&$01n#*4 z7^>8ox;5Zth#$|aKE+2V8{5%eUS179<8@r)+%^K>O(Ou_M4oRX;N1Q#dm<3yw<_ER zkV2&#O``<=TYS&L)w`yz8groH*cGtTMyu1X$4{tBU$$*k zVj*-em`n~;mpD%E0_TP*oK#-^YX}cO0)gRx>jCqBUv!+Ts@-Hi-rxA2o_qklFa9+G z$(O1tHy!oCT-JYJV7qVs+k+AR5v2W#!qPVbA0e(e4Mb1>TWi77SAv&V{@}PT^B(;9 zkc-3zK&?rVu8~$lH~klAo8a61BYe6ibAiS6XrQzYK&MbkOg4eCiFFP6&tIXS(4+-A z`v8Ec`{C08U5y0*^XD)prWStBkd+Ss1w%seWp4(>P;eHQo;-l2b_S&^kLqlLGngkO z^Whk3y@}w*f5A&|zl5MmFFAp@QXb`lz)ZM#8}^tq`W=i}BQgL)?gKi(z)7e&SIp1B zVU6XmdR_d5nxoNig<$7HfcDUF!bwk~x5&WI3$L4}|H7?n-~aF7)`X=}A&|dazd*hr z44Gb9oA06zk_Duy-t=2An^Jz}(UJj!Y$MbH>2Z?P)cpj7vZCN2&XNTjDmT;;P-z zgeBTrR@vvyS6-2-_Yd{&acV#VeqDkP=$yNWluZj&nb*}wuH4?Qi|IODj>(*<^^vS2 zd@Pns@*YW$P(^Q}pAf9B<8{64O3mpy081mp%=Kh6Y*?+>Y`YARk@0QuM$HuK)&#)cihOZsv4cR*h8P3n3>Uj(L zaEE{b&OrE>HgVnqq4dIm2n)$S1y~oofr(`UiBdSoZ7W;)7!yy#eGPQ)98T`oo{h;| zK7rrEgCwNA1MnQYe5qiq*`eY(;!YP6%b_76zf|;audO4~v^ENnh649*h%F0xf*A}S z?}@4AhWXI4x@e#q?OO9!hwg_CMRnItZ4Kz3;9T<}JR=fR(4Dlf^xF2BysV>*MI*Wm z{jq(A2ko-c1}AeF6SV8HsV9Cmd+&eRqt%Cx)4hX=U3ClhW6h20>@(-wU@i;spi)J< zY3H6SuPF$u)X>L%gMQFO2U+)=;+BiVt@e~2c&Wd@I(I$=L%ZoyHba-P;u5$x%raefLAY4n?eb_c? z!s)N@%(=}@EW0GZCFAre3m)b1uoa3i87@3M3GAvsSfFyeI(mbvtid(k_W01cG9N}H zV%PW#aItA9Hu6r1JO;AhwYyr%#&72aUA*&mIx=RF^fc>v=Rz2eAmK2jz|4#02ce`Hi1e`KgRmn3Vn0x@Ba_FkGzrN>J?&0_V zSg`*>Af->5Jw$h-khi|qBYf47>x|N;iJ7z1X{*IG zje>T@h2}eoq|+Aj1~VDAH0ymVkwRaMh!@LMzx_wNb|YZa<1lX5aM?A|!}--4Xx2RT zQhx>mk}b2rL(s|YjXjZb&MeTpgfCw8gWCriha!!=W@_PgQah`JNX9mj>*SU&PrfO>e;C#Yz_cD}HTuj3=t5o$9J+!7j69IoV*aOQ zdP@987!ag9yVGDfUhf6M?cqMGA)UrN9`N$gz}Cf`J3Z_dC-eAGD2@GYEhdg$j3oMX zqkW@HV{x{q7#(*qBb^kkc*OUlJzgrK(QGfx^9OPOMsF0CfiVr()wr0Yx@M zqCuY#X)|9x4dWZuN^)x4^q=hs@shbRY3eP)rJhr)Vtfjd@YNtUL2QPrely{Re5^Hk z4`5j5_mC@{#fa1>5?FeDS-EOMGg_mmreL?AVeSd}eD3&|*x_XpL<^nn(Ncc(mDGxP z|3dpr&uzDp=T1yM&QH!atxHrdjpj?<#>CCr-O_KyDh$F(;NtQk^PlbM54s7o9zyjd?GKP0fq^!iqXoH&o8GrD?A6+nTWXgJb~|_inA) z?Q#IcMMsTzJc?c1JH@GLw8XK?Wl8b+O}1O9r61eZ;i~%m4?Ei~Vo%9tFMV5?ritq^ zn7)o*8Cq@&8F=!Q^j%7q=xnE&M@hFYNFbFWf6Il2C_8=!KIPN&poH%R1Ucb%htFW>15C)|IhBcHc+;kkbu@q|ns#3ksB ziDP1sB+h(YB%|fU9Br9kjeH2+au0dZ80nbyo7KeC4vSya2RM{0RSr&EMmv7e9 zYAu0&wS}RLZ*J~tdN7l<>c$&83)5BiHN=2Oz7al4uc%@B;f6`-DAlMOGfRqyMu|PB z2a0%OcIeT{l?Q#T#E~TIeSzz+j{Q^ypCf%FI(y+(FqWT`D;=h^gq~w)XFEXc9_{ZUzcw*#cMwwSRAnZ&w#(1syZYDEd+PZ;4s-KJI3c1oAQbU{l|3~mI`>7olU_FB_c6^)2p8pO~=OD(P1YU#A7rNt-_ zWGhXjqNp_lF(pJ25gAJm{v> zuO0Y&aP4|XHM-5G$-sJvhzpyJoQe1;Yjn{uaO9R>ebLtL*~0Z~Zpi^V0;m>$My^(9 zGv3MLF`Xi~Gq4A)bb#DeRC`oZyhZ@K?fRV_l@+gvz!p(iS=r`FGIMEx4S@k8FkYOc zJ^|L~UtzdP&aIjBgMKbS*|}LdP0}=8_WQ-zgDFuy$Wp5YrQdEl_PQ($}~H++=mfjU!@wl!%gH)f&IdJ03_Luq@e` zdm|P_T%`!DZTW7KQD0$f^4Xp#7*epasN<4tHD%+u=a>EIci^$|a8Jth7w1|6T|z60 zoq|N&p*UP@;Ds^JjTFMR!!!`}H-gJT#X9f|WO^){bpZ*j$?1|PVta0zRmTM{>V8b+ z{cq<7x^onFNUSeP!*q7&S3}MHhVUs|ihhIIkEsD;tp-&;z|}!%Q>|7-gbZu|RR})Y zd9vG@doXvyP3SF{sz#{Q<`}f~2r*=^9LLl=HZK{FCG?rFo6JxcpaNzm>FG775y@(r zRk2d>S4V?6ZFw?~g^A;G;Ur+&zFNkxp!88&Zx%SjSk3_}oQ6vTkroRT6R_;Dr6fuD zG#SHtTPZb1yS|EpsQGk?8>8fM4Jf!B?4G^oY(Er4bg0MDAAjMbBD$vL9)2(fs5TZo z_OEcekU=T-;A@p}cDvp09X!@}k5XtjR{!nwy{q~JulKOIatS@}& zqVf83#=3`#1;k?ZIGhp?6P(-ytrb?=X+=DghH&%G4c*U|)3JCfY&sG~>)QNW>^V*g zvYnu)T?S))3|Ns*h_T_cCnr%~GoBS_wAK$2i*y$o6L5Wod;LsKDhWP+#JpL`FG_bY z*Ti=?jd3?qQ+u>f-~L;Wn=pFjwPvI^?WyW9wZb7G_^5b{sd@UB-=o|t&rR1S)?ph^ zU~bY5IsbwNf!C{QI|6l7txz`Q05Xo0`w@^k8~zv@yZ6Rf^Z;NU}c? z>R1z*$$GZZW?V&kU7K|S@xVI>)Zb-Xzj#0C@ z-sXH6d1aec4rK)UHnZrFDK z`Rl9_FPy^5Z*ukBV&wK@`qCWks&(4(!&8{KRg!%<^8`Pj%x-Qr$6$?V`4rE=`B2SW zuZSOv)AAy^M3-C2cA93_M8O}zv%~YsMsC8Z4P8s4YW>AA*UZLtOOX!}9V|2IWrFL? z1^4sg^zq;*5Ss0o199#*xQ#N5bv1XkS6_c=e~R@`s}^SUJZj@;^!Y=}@YX3{5P8+L zKHSU^e2frP+b(9v883J$>d_u1>?rQxOYseL3)`QLV(1);rhutTBXouNf!5THGP^*6 z&|cd)?R(~xYyPK9#_PIoTu6xUQ%a2!k02(z zDe2|z3%iyqzhrZT+qO#$X))i3HJp{YI+q?)zqWSi3zhj4dfOK83G}wX#K}Iw$sWQ% z+^yZ7uq+?~wo`f_!$+5(Q#10jTm*nY--L9En0U@obCTw+s-g34x{4gchMloeo`;QA zBYRT0C$i9MnZL?|6j#~QLBrt%A^o&Vn}UA$0`x56++$xsmOhyY*-Cj@{(xKK`$9_a zBFV)9iJqQnZ<(!=(_muZbRdsq9FKGd_;at1IC=@AiImQ~GD4Va2E&NFnME1m#CatO3DXUW-rYtZtot?uJb72F0t%ybor!xtzbJz70GVa zsCokEIA)eO3)vPht$8TE?7pTJu}KYpK<(%Ke?g@SkVSM(LszL8R3UX);iS0gp8DHb zisL@Q8rqK#4KPAN`RraDF@)KN8}j|K{KQTl5q{ClsnUCc0@(;Cp^UUZRAvD#TG!BU z3OgthF`HA~k_`c1LG6^VG=k02H3Dd}4{Fi~izSDaOZp?rlIT;0J;oQuY>%ROdRqT0 zl3NnS88+V14*RCxvTo6ie-|KL+IH$#S^ z(ZK5&%lSRfHNl#jnN3Yi-2@zTe88#)_)>>I{3b0Uqi7Ha__@rGR4R4j^{C%D@3OPA zfp`%u9WA0Xb46>Lwibvc1Poy+zB2L#9f1E1_dazE$e(%V1snsmZ%Q9{^6h_>(0*hr z|6#C+o`6nwE|V3hw|Ax0TPw*p?`?l3k5;^^@6TM~ffY;bdz8JO_AW-q;BPi_y7?5$ zB^Wx&%{LhAk+*Q+r#ZPdn09`@VyxW%X;Cvk)ZF{Ix~0v^-P;hS-D{uPsX=P;wb3}= z$BnTaAlNs}e0J7;OKfGlk;y~))ir>~^{fwNNh(6d!Q+o(KFHMjEtZdx`ai`neJSjy5B4=}c^ zs}cmp_f?NS&&=ba%Q|vSCj(iEFV*($>-lDWdgSE;Lc%lW*VttLmD0q?dwWzmUBjIG z(4j9^yReyM>=|7#c)mX7IrgSt`&bbiDcKLJCJ972#eLRU-Wc1w^K$a`U3y-g;MtWdjUd>8V_ z_YVLj+(R9xu0arUf)G5J1&g#}LKEXgkEy z)Q5X|@3Gw*Q8Rk(YVP}fTZ4%Q_NXLB6djs>I>K8+n}M=l^|#D4IWRE5Ux8Eu$xVk} zEZq}_F;vBpKRa#WS} z5T{|mKbF%dN@Mm1y4^3f7On)IC3;m_3P^DI6WOzLOdEg3=9lHbu}de^nDL~ojt}z z)0dVQ6X@FmZv#~Yj8DJmw$PPFPV(CF7#Q^__&0V~=sK>anz=Uy1_kTi>w&rf%OU#V z6CY(WA48AVKK^!Z95GbiI6As}JA3$88$U*iaJ*1gk~ey5y;nf&Lq67ifb>0ZF|2Ke z(@@qb8^&fay$LdYcdA=UQ%O!PXv|IZXf;Rg4^Bz3avFZw&rT;Rr6Z_m)%%nRk*6Fq z&+#6eK9y%8Apky;yGxUmQ&TI!A;i53+WF#iCgFWHD3K%Kr1M7S_!@R<{wqf|Xn3%2 zcvsf@x7I^1PtP7>mI^X)adCS|GXPPtI6fF0!TdWMy0#em`LP9{c0yA`M8pUH&a@KTw$Z=kw6jlXBpTxmy0jL;t3mW9eW#O*r{y=?r9Vp;MNXh2^n!}3ElR^wf)~ZDGUa)uOsfG2|bd?-xLM%x2`@Zf@9(k89B`mp}3*qYCHRbq32Lq zg4VCbMWfk;ucjn{sGVzUB-ZV4DI;5O(Wh3{ob`6UYM?|lDv$}?6D1bJ?;Igjx{c?G z(HCXte_!yw5$xJy=?FM-)HcD=YEIm?Y?E*lC&VcA{`ITQ(n&#&%x-UW8s$@}S|va&Xo0ilNxjDK(#-xdFEqVENaRKiUf zO92BqIid8oul{r*$fhb$3o{{_!)x<8WJOvouBKNrZWA#}!u+m0)->gS5tvA3uIaDHFOruhF$MO!^X0 z22CtAMb#3I-UQGQzO|2ONc1gMF?JLw8E**#;;hqh>6KPB&d+x+FPK)>KCew%3d?EAL&E!_Kj5&SNG#N?kp)%hvMt%bZM; z2yzPN-q*y%#f7W=@GW)A*SOyQa&W~Lf6#f~;c<1|aV{;$DRJV1_UqLP3SuSmbBm+K3zq{S5_* zLXBA)yBI6XPkp>Tss%(_AFa{9G*X8>rjX|1b=S-fy}JxoL&SsOp?98%6^_rjWNPPg zbTIk9$kl{yL@54%Z%ibWgRH+~< zuYS8x;J+!ka7m-gOpBDVIf1Y3rx<8w9M+M*cJ;-t+pEZAG%#BJ`G{L1JM6Oz%p{!_r>!Qk0dFH1 z5NftYDgu~kBKz;j2+rk zCYVJd8|v}O5!hddgSMbq@xTg4i4w9VkXN9+k|7{+#zyk5puKJX*ywoKEn27|idcIgpYU7xI^7 zY_V?$HB`sT8_u{(F{j7+Vd7kV}v`8yQw3xniiXKiZZbVaaaB$#FwV>0{vB3XIEZSa?6Ob}H?j>wDEUxq$Y zYn_n$kTu_(a!SVH@o`b4lyTco9%iTt6V6AH3Vj=c5Uj}4G2xs^W`rjXtnGoxyOSZY zL@e3`P7>yJv4uA&6|6;X-^kE&NN?uVYU~Ktb>y-my(_HENOdN`CPP|ta?BN2R6;<1 zT}X=TJZmz$N|@Jyh~pvuCNcgU$NHD&uz&d@pG>Pyeh|&B=_TyZtG?8KIn~_mNG><&IzlC7VKZOOy|2b<4@B0wd)N@qr`|<7m}omzKjwth zIGRsxrrs`d3*S(7`mIe!Tr6RPY?ZEm@8PRz@pGNQ0Ky_Owe4TMFLJ4*7D@{%nn=>2 zWjyk*Ke*hxF9{C^m7#Jbv30)lP8l^ZyT6BFK?FUOlu)|AUe#`uj_9D8DsZdPcX&*0z|4+t%8IEYW<)lwWwdZb$@r49mt z$_A;6P^$~5alQ$U{0fce z@x=OOxH6WQy?N+1eu6sTHmuzIY(F;q{#)>rDr1n!V++#>TaB1F{zWRw^h}2=#4@8X zU`n_*qT^48iI81MU#>`i&ko2z>9hZy%>p_9s={7Ex#05r{%n9|4>95Tkc~YcD^B;X zwDxKpR9TjCO!Q^13!4_|yR)atx1W|s8`zxgQPR-LSI7epBFzD16NYMrPjCO^y3@zmErH#<2H>DEHF(;ZcZdjsA1@xW=}fM=)3yj?RHuS76~ z45duI8YUw@gl%EW>&e8pR?q0YBhTsemfN(epe}R+!kep&>G-*YDaL>d;XI}uT&N8c zxfDKoP5ALnH-za`enzT>1o>S+k<`?}ghx|`UpI?J3ug@1tE=mEWNOh6C63+@4kA7w zYStt=F0#>~(Zr%lF1Nn@m()TyL%K<6p^+0>)b7>F{vWhTpa zo0+KRynGMsCg7penz*GVacs41Fc%pW_%z!g1M4PH2 zaXq@`E6|_6%qV>Z9V+chRNNLDF6O?H=+vEIMzn>gvqf()*TD(MoO)nz0;H)Okecnc z?f)l#%HT3q(f@^ps7i`x?DCvHY*O#{`_k|0@+rH$=u+f0-5@@$Y-;g=4FKN`d z3Ydg&cS5UhdeW=Zr#s4X^)Z%RUn*$~Fm0jm=3*1si^R?RzNqlpmsc86~LeEL~&Wc??= zK@mgXpzGM`sR^>ER~Pzmw)e*o=(^HznA22JDh zW3mQ;7;F|Nz4fcWqt@1vT$Vb;v@M=i%M$K}_or1!*yI+gZ$C={2Ju(s$C&M?Zu0i(^Ww81%i zw#c<%YY0!GGp&gyXJ;lWLtg@}^BbQNR!=LC7ERMexefw-yyd1CF}@06w-U-~z@z1D z5|OE2!PcZDeJ!Dt0Xh^bdOm%%p`7jyR@KPUnQ+`A9h#3$iVl$Ry8VFt?$gh5_^OXa z&OYgmDCGtor<-P;R34b3+4*GV>`#r|9UKnI*D?RGeYe?QRitR)(!L7fD}`RXo50>v zNEezZa<`C%1+heYh=x5Q2H-u1zyQ({orPLLrFwMy$R>&ngmJ^bvy*RvTZAyuyuZq} z11mb7cUAVQ8>^UCkTTA!rBgIkWS19BR!RVPDK!9lN=53L!I*}edpONcb1$TsnHyr5gQ#JHawl&|+ozlh8B_k5L{C?E8Q*=H zQ#9|jkZJfuTcS&w44+@Y67HQWpL5tnjwAa8#izW1vV0Vc4E=Nz3V^BdA&%mRp%##D zq=`&@`1r>Kn!3(5x9*0<0GA>YH=B##X&z#iL5eD_K`3ybaRusLU2E~|s)ZMRpYl^E z!NjC`hNfuJ3p4qtf^Kc#eDiLn{AJgD+95W*=y_HB7;K?y;f*O$+Dx4VbrFBdgi zbRBw{4+scG(u>h)CS;lcqT`7CW<7a$DZcGIM%TO;CEdlr6k$<$d3jM^m(&LM7wxHp z{A|9FgW+#&9#hDK+=v^Sni@JfveL`E%O;`|ms3_&F4Ho)FwP=y=-sd8Tl%|@@+2l= zkn~GLZ)swoH$-F}LT=adJT}pBZr^bbi>&5^WeYAptBJL)_7hwT= zUGgoD*_X-$Ez>D%S3HfsN0-nK3j~vkV^Hos#t+m2MB8=!?Unfdn=o@B`fCjZ307qE z(@ff52oS6={M7;V|48iAEp7s^l7`m)48csy0_A~={j*k6xJC}ahEg)hGXriWOa&2*USJgaFP}v zgoe30yZ%~Or4Mn%9?8!ud!B7KI2pX}^}pfJ|9!aXnD?}shsqWbt-c{%Xu<1OR7?>> z_rui3L3-$ZD4~bhhn3f5(oh>TEA={iA8liP5Rg5Px-97L7}F*;NVVxu$C1r`P{kQ@ z45I%}#5fQ57cuNg!sx}!rfoM7uh%UGclMsH|9QVk&~ItOFC%7ZWT=?;x3dP;Ln5)uMTpj8vj&UG;WJ-2p$< zTUWawq8|FaC2ZFkYJKMe0&I(97im{VO5K&Ujx`Ct`=CnZ{s&3>G}~Iyjt?3KM{ois z-Ey1i0T#M$D_Z^e%z59)fSV`<{Rm(e_IjnYI1Qeu-nK31?tPkhhNxx#+DEM#Clc-5 z^m(Y>IlqlZv<)k=&5jiIbjZ`nY{AbtfEKAh7BcXmwPR10I#Y3n3$^mZ{(f|Y(sk0S zI~i_?tUB?0voTl(d4)Rt>+83K7fDmt62$EgoFHWpk(Ea__g|e|esiHdG<#8M(}Hz4 zkJ@XL|uge5k7%0g}+G}gEdEPj89c}=KO z{=oZelfBZ*8oynFv*3dY=&)$CUoML)HLYsQyAfZtHDG=}%CPbDo%ZaDeuboqNxlX3 zy)VzUu5)us$9h}}dxrsqLcmH7+kTEJLZBkSD%Lu!1|ZlbQF}wzbmY&fPp-*gmgwZ& zj~9Nkn;L+3v{j`ibiobPH69wYHDy?Yt>)A9Z|$=}+tdN~zsmbDdg8=6VwxUFRKmvV zg@*IN9rRQ`ao-r&G~dKJw)GBge~pEJs>^(J2g{yHXz@jWDkSa@|~v$PX1 zAGSlQno>`{z3Fv$o8b5tbJ~(B17`7YTSBWvQew87JF|b*twcKj=ib)k6%Zy^1h&J` zm^A9ve_X7-pnzk_AD=hFdG!7-!0hxg8|}H7%_3%?plad^1*LCUqS>+a|4N&+77#jQ zcf|gKM6syGXMUoIc2`VjG`azhC_(ra8$R0+ASuy)&kPMhXzY6VKOve*%75e37&GFy znvc3San980EEfJ>_+qD-K(3Q7EUDEUkJG*e?6fiw9(7RgnD)?Y)N=%>X{`%=FT)so38A1zn;4CM8U; zqjf&?X2TP5;21Y1y6_z>k-roVukE~h`8NdvQBU6t!(k9`>=H-}YGDGse$9r)@VUrp z#7htZvtil!N3hTe-y9#T-m~*!8NZCO>!E6vd!|WdBMg=Vu&@YTWDnK4vExz9sN|{* zWDrOj0U>CjG8+nIf^&28^03UZ;%r_?lxQU#H?-^{c@b4z%iA|c3kks89%Y{++uK`+ z)@($BQcj7RelL%^4>}c=)D^NirHW}bZjIkh;aC%2T}Y|*)~6coEL!l=H-4Y?KEJX! zXCAAc$}#DM6L5}o8$si0jtWR-l>Oc4#)#pV*r1Z*4cg(GW8?kQlAUro_V9HeJBMqA z#6;6R0){AQja2i$|l{p zb?4=HxEU#Kqzl7mcyNjuG>U*kk(`aFLYI=I&8 zW7Fxk<+3^~sbgh0%ccqD1U)5QK-RhkW@!DHVA4yh3$4)046CjI9Zvafk3}uen z$D|*NMpc{9h)&qk0Z(?FBAkCu_H@LnBr{p6)o^g3(?WFkVJU1?*tder(P(^U>j1)x z)2KeLeLWa3^9;}ka?`vvnP4BMRc&PRuIA``8OSVA5IsC6zczGb;$Qgj__W%&#ViC{ zy0Ie}FmoEP=T!0P)ZiX>51+RHl4ml~rdYAn=qwG7C~Q-o!w#N{=Hfb9n_>cBzsW(F zYE-He+RUe~2K-3fcz(+y7}DG#m$@-SQWR4wTiGbEZn0b29OXg~KpuyJUv^XO5l#As znli!R@+ngfVUEc8GWwYDf-?(o9q5leveO>oI6hF{KJ)Skcny}D$WF6m7y$>-@{EsF z*7Q8Ft}@z~v)1I@K&|L|hszjj%wSxX?w8W`G{Hq(Fuk6vtcENBLDSj?`s$MU*CX`8 zr)AW_#`!n&Mks}stnHrJi>^c0{K&&qDEt%N&iDwef>L8yfxN{1<};VtQs0!{#Y-vs z#ko3-<6<=v0UwSxWVO}Bwu)#IfL!ac=30~C;{^f2OqW1_QDpi(3yii%XW-2D0zh#7 zH3k~H$#@XwlXNn8J)>ZuY|Za_{l{Fn){e2)qx{W6M>#TJoFDV0z^fYXd0;dvNq+u{8;43jM~Py zn|t+$E8wdELoHbB^&ehDKN)H4bZbPs^@jns@?%?(NVR){0E)%WT(BnV>kh*2Cr>zD zT=XDZcFLu4A(tzsYreQWGVORP0Oy?*p`Mo|qB}Ju`K!jO^00Dzw;nhl6Jf~*Q|QH; z(D(D1&V11F(LG^?8NI&2miGQ8pD05heW(|cns(5>Eg>jgZ93Q};x+NBV4H!J9pZu% zXNSuJt4>~tvSH}&NbS|Mu2EYivK;(SOJ16?~GWT-%>C`?R zA_!ruw~hYXEJ-lHrpUP4VEPxk+73trq1rr=z9~`QQZhVx^W_-;5p9h0%Y%zzmuRuq zliZ?JV-6{w&=8?D{qy);lRgqK{^vm?*kl~O!;=T*M~#?8iUIx zn~Q1CdY!!0B5aJ!BZT=p3(q|()wYQ{g-`o3j>ReZf@#)sCy14`L{h$J1JKdzh*N>Q zq0QJ8@EDx3#R9(lTs4Op-SnXe3FTX3ta@^5um{;M{$P4~x2P{%wyORKSBdb;X&CKP zd1mm~hV$LEuTcZTt=)=fG93J4C`IS-0_=cLr#+- zuW(K+Ts1k_G1;9yU4)0l{wAub9E;>MN3Ud&C)*WPt7PJVHQI_YZ&oK-g00lJRa2B{ zH3!6OpI)(oJO?M9f?@cIHq)_cGva}>3@zGWrG4~7swuqxC~BXVkrP?QuA559+_7h) z7tn%`nNzZHFmP<&q;wq^b7uY(NcgFYG_fOKAV$#6H!a>cUjv^`B#rk9zM&IT=^l`l z?J-qu%wht)9rQNgSqWZv>)}`4F)KC-pS73di8Vn|)xo_~JhH~UK(wVw)nF_hQ2xja z6ze7;?9abm96(aLtYTq?4zKi?p8y}+Kc1%ngX3t@G`N@gh8}gHA9wQtbL7kbY%X>1 zk?-WdOJHImISW`z>GUst>fJGy~*9BJ4pp@Zrp?3TX!Oj8pmuBkR!33PJrxP5!)~>OPOEf~Mh-KfH zpN~%_K$8lxOVdpg;SI{vr8WBNH&vSc-@T$-tKf)%SSVKS_loFfZ1gD@lJ=wVFT%@b zeOrB;#MyWSak_e74#NyyH1G~Z=_LT@g- zs;aBeNrV^!!6V#$634g~%2PD1W)$PnixhMbu1>%6KPD$9A3~Ku3E>K|*owC9#;T4}8J1K|_?sh*9_n1zN653Mr%6LBJ`_4I46y=%> zRsMh9L2-jqzD`ht-07C4Enf#4h9MgX>^(lq>6wHwn zj9^-gKQ@(hc3p9KUnby=yEsojp3c9c&`A78rEg-6s;m~15<+#jNA)~L7rkCzj<_f83ZXN()4;PtpDn~tSJqMbq+lEVABHA*8UO$Q literal 0 HcmV?d00001 diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/adapt-legacy-pullwss.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/adapt-legacy-pullwss.md new file mode 100644 index 000000000000..e06ad812350e --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/adapt-legacy-pullwss.md @@ -0,0 +1,98 @@ +--- +id: adapt-legacy-pullwss +title: Adapter les anciennes configurations de collecteurs pullwss +description: "Comment adapter les anciennes connexions pullwss à la nouvelle configuration des collecteurs en conteneur" +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +## Quand utiliser cette procédure + +Cette page décrit la marche à suivre si les conditions suivantes sont réunies : + +* Vous avez mis à jour une plateforme existante en version 26.10. +* Cette plateforme utilisait des collecteurs en mode pullwss. +* Vous souhaitez désormais utiliser des collecteurs en conteneur. (Si vous ne souhaitez pas utiliser de collecteurs en conteneur, vos anciens collecteurs en mode pullwss continueront de fonctionner normalement : vous n'avez rien à faire.) + +Selon votre installation, vous pouvez [configurer vos anciens collecteurs pour qu'ils utilisent le port 443 (recommandé)](#configurer-vos-anciens-collecteurs-pour-quils-utilisent-le-port-443-recommandé) ou [rediriger le trafic vers Gorgone (non recommandé)](#rediriger-le-trafic-vers-gorgone-non-recommandé). + +## Configurer vos anciens collecteurs pour qu'ils utilisent le port 443 (recommandé) + +1. Configurez le serveur central pour qu'il puisse recevoir le trafic pullwss de vos collecteurs en conteneur, comme décrit dans la page [Prérequis pour les collecteurs en conteneur](./pollers-containers-prerequisites.md). +2. Mettez à jour tous vos collecteurs en version 26.10. +3. Sur le collecteur, modifiez la configuration du module **pullwss** dans **/etc/centreon-gorgone/config.d/40-gorgoned.yaml** : définissez le port sur 443 et ajoutez la clé `central_uri`, afin que le poller accède à Gorgone via Apache (adaptez `/centreon` dans `central_uri` si votre serveur central utilise un autre URI de base). + + ```yaml + gorgone: + modules: + - name: pullwss + package: "gorgone::modules::core::pullwss::hooks" + enable: true + ssl: true + port: 443 + token: "secret_token" + address: + central_uri: "/centreon/gorgone/pullwss/websocket" + ``` + +## Rediriger le trafic vers Gorgone (non recommandé) + +N'utilisez cette section que si vous avez de nombreux collecteurs dont la configuration ne peut pas être modifiée facilement comme décrit ci-dessus. Dans ce cas, modifiez la configuration d'Apache sur votre serveur central afin de conserver l'ancien port pullwss 8086 et de rediriger le trafic vers Gorgone. + +### Collecteur avec HTTPS + +1. Configurez le serveur central pour qu'il puisse recevoir le trafic pullwss de vos collecteurs en conteneur, comme décrit dans la page [Prérequis pour les collecteurs en conteneur](./pollers-containers-prerequisites.md). +2. Mettez à jour vos collecteurs en version 26.10. +3. Sur le serveur central, exécutez les commandes suivantes pour rediriger le trafic du port 8086 vers Gorgone sur le serveur central. + + + + + ```shell + cp /usr/share/centreon/examples/centreon-apache-https-gorgone.conf /etc/httpd/conf.d/ + systemctl restart httpd + ``` + + + + + ```shell + cp /usr/share/centreon/examples/centreon-apache-https-gorgone.conf /etc/apache2/sites-available/ + a2ensite centreon-apache-https-gorgone + systemctl restart apache2 + ``` + + + + +### Collecteur sans HTTPS (HTTP simple, non recommandé) + +> Cette configuration n'existe que pour assurer la compatibilité avec d'anciens collecteurs qui ne peuvent pas être configurés pour utiliser TLS. Notez que l'utilisation de pullwss sans TLS est déconseillée en production. Mettez votre configuration à jour dès que possible. + +1. Configurez le serveur central pour qu'il puisse recevoir le trafic pullwss de vos collecteurs en conteneur, comme décrit dans la page [Prérequis pour les collecteurs en conteneur](./pollers-containers-prerequisites.md). +2. Mettez à jour vos collecteurs en version 26.10. +3. Sur le serveur central, exécutez les commandes suivantes pour rediriger le trafic du port 8086 vers Gorgone sur le serveur central. + + + + + ```shell + cp /usr/share/centreon/examples/centreon-apache-gorgone.conf /etc/httpd/conf.d/ + systemctl restart httpd + ``` + + + + + ```shell + cp /usr/share/centreon/examples/centreon-apache-gorgone.conf /etc/apache2/sites-available/ + a2ensite centreon-apache-gorgone + systemctl restart apache2 + ``` + + + + +## Dépanner votre installation + +Voir [Dépanner l'installation](./pollers-containers-prerequisites.md#dépanner-linstallation). diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md new file mode 100644 index 000000000000..b9abdeb9ab02 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md @@ -0,0 +1,223 @@ +--- +id: pollers-containers-prerequisites +title: Prérequis pour les collecteurs en conteneur +description: "Configurer Centreon pour recevoir les connexions des collecteurs en conteneur" +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +Cette page explique comment configurer votre plateforme afin de pouvoir utiliser des collecteurs en conteneur. Cette procédure n'est à réaliser qu'une seule fois pour l'ensemble de la plateforme, avant d'installer votre premier collecteur en conteneur. Elle n'a aucun impact sur les autres modes de déploiement des collecteurs. + +## Quand utiliser cette procédure + +Cette page décrit la marche à suivre si les conditions suivantes sont réunies : + +* Vous venez d'installer une plateforme en version 26.10, ou vous avez mis à jour une plateforme qui ne comportait aucun collecteur en mode pullwss. +* Vous souhaitez utiliser des collecteurs en conteneur pour la première fois. + +> Si votre plateforme comportait des collecteurs en mode pullwss et que vous souhaitez désormais utiliser des collecteurs en conteneur, suivez la procédure [Adapter les anciennes configurations de collecteurs pullwss](./adapt-legacy-pullwss.md). + +### Le mode pullwss + +Par défaut, c'est le serveur central qui initie la connexion vers ses collecteurs. Or un collecteur qui s'exécute dans un conteneur ne peut pas accepter de connexions entrantes : ce mode ne fonctionne donc pas. + +Le mode **pullwss** inverse le sens de la connexion : c'est le collecteur qui ouvre une connexion WebSocket vers le serveur central, puis qui la maintient ouverte. + +La méthode recommandée et sécurisée consiste à utiliser HTTPS. Des certificats sont donc nécessaires pour sécuriser la connexion. Pour simplifier la gestion du cycle de vie de ces certificats, Apache (qui héberge déjà l'interface web Centreon) sert de reverse proxy : il termine la connexion TLS et transmet le trafic vers Gorgone sur le serveur central. + +## Prérequis à l'installation + +* Assurez-vous que votre conteneur soit conforme aux [prérequis d'installation d'un collecteur](../prerequisites.md#dimensionnement-dun-collecteur). + +* Assurez-vous que le serveur central et Gorgone sont déjà installés et à jour dans la dernière version majeure. + +* Si ce n'est pas déjà fait, configurez le HTTPS sur votre serveur central. Cela peut être fait dans le cadre de la [procédure d'installation](../installation-of-a-central-server/using-packages.md#étape-3--mettre-en-place-la-configuration-tls), ou [séparément](../../administration/secure-platform.md#activer-le-mode-https-sur-le-serveur-web). + + Une fois HTTPS activé, mettez également à jour l'URL de l'API Gorgone : dans **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** sur le serveur central, définissez `base_url` sur `https:///centreon/api/latest/`, puis redémarrez Gorgone (`systemctl restart gorgoned`). Sinon, le serveur central rejettera chaque collecteur exécuté dans un conteneur avec une erreur `invalid token`. + +* Le collecteur doit pouvoir joindre le serveur central. + +## Étape 1 : Configurer Gorgone sur le serveur central + +Dans les versions précédentes de Centreon, Gorgone pouvait écouter directement les connexions pullwss sur le réseau, à condition d'être configuré manuellement. À partir de la version 26.10, la méthode recommandée consiste à utiliser Apache comme reverse proxy pour Gorgone. + +1. Sur le serveur central, modifiez le fichier **/etc/centreon-gorgone/config.d/40-gorgoned.yaml** comme suit. Le module `nodes` doit déjà être présent et ne nécessite aucune modification dans une installation par défaut. Le module `proxy` est également présent, mais pas la sous-clé `httpserver`, que vous devez ajouter. + + ```yaml + gorgone: + modules: + + - name: proxy + package: "gorgone::modules::core::proxy::hooks" + enable: true + httpserver: + enable: true + ssl: false + address: "localhost" + port: 8087 + + ``` + + > Attention, il s'agit d'un fichier YAML : l'indentation y est importante. Utilisez 2 espaces par niveau d'indentation. + + Explication de la configuration : + + * `ssl: false` et `address: "localhost"` : Gorgone n'accepte que les connexions provenant de la machine locale, en HTTP simple. C'est Apache qui termine le TLS pour les collecteurs et qui transmet le trafic en local ; Gorgone n'a donc pas besoin de certificat. + * `port: 8087` : port interne utilisé uniquement pour la connexion entre Apache et Gorgone sur le même serveur. Il ne doit pas être exposé sur le réseau. + +2. Redémarrez Gorgone après cette modification : + + ```shell + systemctl restart gorgoned + ``` + +3. Vérifiez que Gorgone écoute bien sur le port 8087 : + + ```shell + sudo ss -tnlp | grep 8087 + ``` + + La commande doit renvoyer une ligne semblable à celle-ci : + + ```text + LISTEN 0 4096 [::1]:8087 [::]:* users:(("gorgone-proxy-h",pid=2305,fd=28)) + ``` + +## Étape 2 : Configurer Apache comme reverse proxy + +Cette étape se réalise également sur le serveur central. + +### Prérequis sur les modules Apache + +Assurez-vous que le module Apache `proxy_wstunnel` est activé : + + + + + +Contrairement aux paquets .deb, le paquet **httpd** d'Alma Linux 9 active déjà le module **proxy_wstunnel** par défaut : il n'y a donc rien à faire. + + + + + +```shell +a2enmod proxy proxy_wstunnel +systemctl restart apache2 +``` + + + + +### Configuration du reverse proxy Apache + +1. Modifiez votre fichier de configuration Apache. Celui-ci se trouve ici : + + + + + ```shell + /etc/httpd/conf.d/10-centreon.conf + ``` + + + + + + ```shell + /etc/apache2/sites-availables/centreon.conf + ``` + + + + +2. Ajoutez le contenu adéquat au VirtualHost Apache : + + * Centreon fournit un exemple de fichier de configuration permettant d'activer HTTPS et d'exposer Gorgone derrière un reverse proxy, disponible ici : `/usr/share/centreon/examples/centreon-apache-https.conf`. Vous pouvez en copier-coller le contenu. + * Cependant, si vous disposez d'une configuration personnalisée et que vous ne pouvez pas copier-coller le fichier d'exemple tel quel, voici la configuration à ajouter dans votre VirtualHost Apache : + + ```apache + + ProxyPass "/${base_uri}/gorgone/pullwss/websocket" "ws://localhost:8087/" + ProxyPassReverse "/${base_uri}/gorgone/pullwss/websocket" "ws://localhost:8087/" + + ``` + +3. Redémarrez Apache + + + + + ```shell + systemctl restart httpd + ``` + + + + + + ```shell + systemctl restart apache2 + ``` + + + + +## Étape 3 : Ajouter le collecteur à la configuration de la plateforme + +Vous pouvez maintenant ajouter un collecteur en conteneur. Pour cela, [récupérez la commande adéquate depuis l'interface web Centreon](./using-containers.md). Le collecteur se connectera automatiquement au serveur central via pullwss. + +## Si vous supprimez tous vos collecteurs en conteneur + +Si vous veniez à supprimer à l'avenir tous vos collecteurs en conteneur, n'oubliez pas d'annuler les étapes ci-dessus. + +## Dépanner l'installation + +Si votre installation ne fonctionne pas, plusieurs points sont à vérifier : + +### Le collecteur peut-il joindre le serveur central ? + +Le collecteur doit pouvoir joindre le serveur central sur le port web (443 pour une adresse `https://`, 80 pour une adresse `http://`, ou le port indiqué dans l'adresse) et sur le port TCP 5669 (utilisé par Centreon Broker). Pour vérifier la connectivité, exécutez ces commandes sur le collecteur : + +```shell +nc -zv 443 +nc -zv 5669 +``` + +### Gorgone écoute-t-il bien sur le port 8087 ? + +```bash +curl --header "Connection: Upgrade" --header "Upgrade: websocket" http://localhost:8087/ +``` + +La sortie attendue est la suivante : + +```text +HTTP/1.1 101 Switching Protocols +Connection: Upgrade +Sec-WebSocket-Accept: Kfh9QIsMVZcl6xEPYxPHzW8SZ8w= +Server: Mojolicious (Perl) +Upgrade: websocket +``` + +### Apache2 redirige-t-il correctement le trafic vers Gorgone ? + +```bash +curl -v --header "Connection: Upgrade" --header "Upgrade: websocket" https://localhost:443/centreon/gorgone/pullwss/websocket +``` + +La sortie attendue est la suivante : + +```text +< HTTP/1.1 101 Switching Protocols +< Connection: Upgrade +< Sec-WebSocket-Accept: Kfh9QIsMVZcl6xEPYxPHzW8SZ8w= +< Server: Mojolicious (Perl) +< Upgrade: websocket +``` + +Si vous obtenez une page HTML indiquant `You need to enable JavaScript to run this app`, le reverse proxy Apache n'est pas configuré correctement : le trafic est redirigé vers l'interface web Centreon au lieu de Gorgone. Vérifiez votre configuration Apache et redémarrez Apache après chaque modification. + +### Le collecteur est-il rejeté avec une erreur `invalid token` ? + +Si les logs Gorgone du collecteur (`docker compose logs gorgone`) affichent `{"code":500,"message":"invalid token"}`, vérifiez que le jeton est bien un jeton de type collecteur valide. Si votre serveur web redirige HTTP vers HTTPS, vérifiez également que `base_url` dans **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** sur le serveur central utilise `https://`, puis redémarrez Gorgone. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-containers-advanced-configuration.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-containers-advanced-configuration.md new file mode 100644 index 000000000000..dfcac519cce0 --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-containers-advanced-configuration.md @@ -0,0 +1,233 @@ +--- +id: using-containers-advanced-configuration +title: Configuration avancée des conteneurs +description: "Configuration optionnelle d'un collecteur en conteneur : supervision VMware, plugins personnalisés, prise en charge de l'agent CMA et notifications par email" +--- + +Cette page décrit la configuration optionnelle d'un collecteur [déployé dans un +conteneur](./using-containers.md), +au-delà des services `centengine` et `gorgone` présents par défaut. + +## Permettre au collecteur d'envoyer des notifications par e-mail + +Cette section s'applique si vous souhaitez que votre collecteur puisse envoyer des notifications. + +Un collecteur en conteneur dispose de deux moyens d'envoyer des notifications par e-mail : +utilisez celui qui convient le mieux à votre infrastructure. + +* Une [commande SMTP native](#option-1--commande-smtp-native), qui utilise la commande `mail` (du paquet `mailutils`) + relayée par `msmtp`. +* Le [connecteur **centreon-plugin-notification-email**](#option-2--connecteur-centreon-plugin-notification-email). + +### Option 1 : Commande SMTP native + +Il s'agit de la manière la plus courante d'[envoyer des notifications](../../alerts-notifications/notif-configuration.md). + +La commande SMTP native a besoin d'un relais SMTP pour envoyer les e-mails. Configurez-le à l'aide de variables d'environnement sur le service `centengine`, dans le fichier docker-compose. + +| Variable | Effet | +|----------|--------| +| `SMTP_HOST` | Adresse du relais SMTP. Obligatoire pour la commande SMTP native : tant que cette variable est vide, les notifications ne sont pas envoyées, et aucune erreur n'est remontée. | +| `SMTP_PORT` | Port du relais SMTP (par défaut : `25`). | +| `SMTP_FROM` | Adresse utilisée dans le champ `From:` des e-mails de notification envoyés. | +| `SMTP_TLS` | Définissez cette variable sur `on` pour utiliser TLS lors de la connexion au relais (par défaut : `off`). | + +Si vous utilisez la commande SMTP native, sachez que le fichier `docker-compose.yaml` généré +par le script d'installation ne renseigne pas ces variables par défaut. Ajoutez-les +directement dans le bloc `environment:` du service `centengine` ou, pour les garder hors du +fichier `.env` que le script d'installation régénère à chaque exécution, placez-les dans un +fichier distinct référencé comme `env_file` supplémentaire : + +Ajoutez les 3 dernières lignes à votre fichier docker-compose. + +```yaml +services: + centengine: + # ... + env_file: + - .env + - .env.smtp +``` + +Stockez ensuite vos variables d'environnement dans un fichier `.env.smtp` situé dans le même répertoire que le fichier docker-compose. + +```shell +# .env.smtp +SMTP_HOST=smtp.example.com +SMTP_PORT=25 +SMTP_FROM=centreon-engine@example.com +SMTP_TLS=off +``` + +Redémarrez le service `centengine` (`docker compose up -d`) après avoir modifié ces variables. + +`mailutils` et `msmtp` sont préinstallés dans l'image. Au démarrage, `centengine` écrit une +configuration `msmtp` à partir des variables `SMTP_*` ci-dessus : `/usr/bin/mail` envoie donc +les messages via votre relais, sans configuration supplémentaire. + +### Option 2 : Connecteur centreon-plugin-notification-email + +Les paramètres du relais SMTP du connecteur sont de simples options en ligne de commande : vous pouvez donc les définir directement dans la commande. + +Le connecteur est préinstallé dans `$CENTREONPLUGINS$` (généralement +`/usr/lib/centreon/plugins/`), sous le nom `centreon_notification_email.pl`. Ses options +`--smtp-address`, `--smtp-port` et `--from-address` suffisent à renseigner votre relais, +sans aucune variable d'environnement. + +Le connecteur choisit entre son modèle de notification d'hôte et son modèle de notification de +service selon que l'option `--service-description` est renseignée ou non : la **même +command_line** peut donc servir à la fois de commande de notification d'hôte et de service. +Remplacez les valeurs SMTP, l'URL Centreon et le jeton de l'exemple ci-dessous par les vôtres, +puis définissez la commande à la page **Configuration > Commandes** : + +```shell +$CENTREONPLUGINS$centreon_notification_email.pl --plugin=notification::email::plugin --mode=alert --to-address='$CONTACTEMAIL$' --host-address='$HOSTADDRESS$' --host-name='$HOSTNAME$' --host-alias='$HOSTALIAS$' --host-state='$HOSTSTATE$' --host-output='$HOSTOUTPUT$' --host-attempts='$HOSTATTEMPT$' --max-host-attempts='$MAXHOSTATTEMPTS$' --host-duration='$HOSTDURATION$' --date='$SHORTDATETIME$' --type='$NOTIFICATIONTYPE$' --service-description='$SERVICEDESC$' --service-displayname='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --service-longoutput='$LONGSERVICEOUTPUT$' --service-attempts='$SERVICEATTEMPT$' --max-service-attempts='$MAXSERVICEATTEMPTS$' --service-duration='$SERVICEDURATION$' --host-id='$HOSTID$' --service-id='$SERVICEID$' --notif-author='$NOTIFICATIONAUTHOR$' --notif-comment='$NOTIFICATIONCOMMENT$' --centreon-url='https://central.example.com' --smtp-address='smtp.example.com' --smtp-port='25' --from-address='centreon-engine@example.com' --centreon-user='admin' --centreon-token='your-autologin-key' --smtp-nossl +``` + +* `--centreon-url`, `--centreon-user` et `--centreon-token` (une clé d'auto-connexion Centreon, + **Administration > Comptes > votre utilisateur > Sécurité**) permettent d'inclure dans + l'e-mail un lien vers la ressource ainsi que son graphique de performance. Omettez ces trois + options si vous n'en avez pas besoin : l'e-mail est envoyé quand même. +* `--insecure` ignore la vérification du certificat TLS lors de la récupération de ce graphique, + ce qui est utile lorsque `--centreon-url` utilise un certificat autosigné. +* Ajoutez `--smtp-user` et `--smtp-password` si votre relais nécessite une authentification, + et supprimez `--smtp-nossl` pour utiliser TLS. + +> Stocker `--centreon-token` dans une définition de commande revient à l'écrire en clair +> dans la configuration de Centreon Engine. Utilisez un jeton associé à un compte dédié +> disposant de droits limités plutôt qu'à un compte administrateur. + +Ces options peuvent également utiliser les macros de ressources du collecteur +`$SMTPADDRESS$`, `$SMTPPORT$` et `$SMTPFROMADDRESS$`. Dans un conteneur, ces +macros sont écrasées à chaque démarrage du conteneur par les valeurs des +variables `SMTP_HOST`, `SMTP_PORT` et `SMTP_FROM` (voir l'option 1) : définissez +ces variables plutôt que de définir les macros dans l'interface de Centreon. + +## Permettre au collecteur d'utiliser des plugins personnalisés pour la supervision + +Cette section s'applique uniquement si vous souhaitez utiliser vos propres plugins personnalisés pour la supervision. Aucune action n'est nécessaire pour utiliser les connecteurs de supervision officiels Centreon. + +Le conteneur `centengine` peut installer des scripts de contrôle personnalisés et des dépendances APT supplémentaires sans qu'il soit nécessaire de reconstruire l'image. + +Dans le fichier `docker-compose.yaml` généré, ajoutez les volumes suivants au service `centengine` : + +```yaml + volumes: + # Scripts de plugins personnalisés (ils doivent être exécutables) + - ./custom-plugins:/usr/lib/nagios/plugins/custom:ro + # Paquets APT supplémentaires, installés au démarrage + - ./custom-deps.json:/etc/centreon-engine/custom-deps.json:ro +``` + +* Créez un répertoire **custom-plugins** et placez-y vos scripts de plugins personnalisés. Le conteneur les copiera dans `/usr/lib/nagios/plugins/custom`. +* Si votre plugin nécessite des dépendances système, vous devez les déclarer dans un fichier `custom-deps.json`. Par exemple : + + ```json + { + "apt": ["snmp", "jq"] + } + ``` + + Ce fichier est lu au démarrage du conteneur, puis surveillé : le modifier depuis l'hôte + déclenche automatiquement l'installation des paquets listés, sans qu'il soit nécessaire de + redémarrer le conteneur. L'installation des paquets s'exécute en arrière-plan : `centengine` + n'est donc pas bloqué pendant ce temps. + +### Intégrer les dépendances dans une image personnalisée + +Si vous avez un grand nombre de dépendances, vous pouvez construire une image personnalisée basée sur l'image officielle, plutôt que d'ajouter les dépendances une à une au fichier `custom-deps.json`. Votre image personnalisée sera déployée via le docker-compose. + + + +```dockerfile +FROM ghcr.io/centreon/centreon-engine:26.10 + +RUN sudo apt-get update && sudo apt-get install -y --no-install-recommends \ + snmp \ + jq \ + && sudo apt-get clean +``` + +Construisez-la, puis référencez-la dans `ENGINE_TAG` (ou remplacez directement la valeur +`image:`) dans votre fichier `docker-compose.yaml`. Le principal avantage de cette approche est +le temps de démarrage : lorsqu'un collecteur a besoin de nombreuses dépendances, les installer +une seule fois lors de la construction est plus rapide que de les installer à chaque démarrage +du conteneur via `custom-deps.json`. + +## Permettre au collecteur de superviser des ressources VMware + +Suivez cette procédure avant de déployer un collecteur en conteneur avec l'option `--with-vmware`. + +La supervision d'une infrastructure VMware nécessite le SDK Perl propriétaire de VMware : +sans lui, le démon ne peut pas démarrer du tout, même avec des identifiants en clair. +Comme ce SDK ne peut pas être redistribué pour des raisons de licence, l'image de conteneur +`centreon-vmware` n'est pas publiée sur un registre. Le fichier `docker-compose.yaml` généré +la référence sous la forme `connector-vmware:${VMWARE_TAG:-local}` avec `pull_policy: never` : +vous devez donc la construire localement, sur l'hôte des conteneurs, avant d'utiliser +`--with-vmware`. + +Téléchargez les archives du SDK depuis le portail développeur de Broadcom (voir les +[prérequis du connecteur de supervision VMware +ESX](/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx#prérequis) +pour la marche à suivre), puis clonez `centreon-plugins`, placez les archives dans son +répertoire `sdks-vmware` et construisez l'image : + +```shell +git clone https://github.com/centreon/centreon-plugins.git +cd centreon-plugins +# Placez les archives du SDK téléchargées dans sdks-vmware/ avant de construire l'image +docker build \ + --file .github/docker/connector/Dockerfile.connector-vmware \ + --tag connector-vmware:local \ + . +``` + +> Cette commande télécharge le dernier paquet depuis le dépôt APT stable de Centreon et +> inclut le SDK par défaut. Ajoutez `--build-arg VERSION=` pour figer une version +> précise, ou `--build-arg PACKAGE_SOURCE=mount` pour construire l'image à partir d'un paquet +> `.deb` placé dans un répertoire `packages-centreon`. Construire avec +> `--build-arg WITH_SDK=false` permet uniquement de vérifier que l'image se construit +> correctement : le démon obtenu ne peut pas démarrer, car le SDK est requis dans tous les cas. + +## Permettre au collecteur de recevoir des données des agents CMA + +Ajoutez `--with-cma` à la commande d'installation du collecteur pour que `centengine` puisse +accepter les connexions de l'agent CMA (Centreon Monitoring Agent) via OpenTelemetry gRPC. +L'option `--with-cma` ajoute les éléments suivants au service `centengine` dans le docker-compose : + +```yaml + volumes: + - ./certs/poller.crt:/etc/pki/poller.crt:ro + - ./certs/poller.key:/etc/pki/poller.key:ro + ports: + - "4317:4317" +``` + +Générez ensuite les certificats TLS correspondants et configurez le côté agent en suivant les pages +[Configurer les certificats](../../cma/cma-certificates.md) et +[Configurer l'environnement de l'agent](../../cma/cma-setup.md). + + diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-containers.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-containers.md new file mode 100644 index 000000000000..e6090f23525d --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-containers.md @@ -0,0 +1,174 @@ +--- +id: using-containers +title: Installer un collecteur dans un conteneur +description: "Installer un collecteur Centreon à l'aide de docker-compose" +--- + +> La méthode de déploiement de collecteurs en conteneur est actuellement en **BÊTA**. + +Une commande d'installation prête à l'emploi et adaptée à votre plateforme est disponible depuis l'interface du serveur central. + +
    +Contenu des conteneurs + +Les collecteurs en conteneur utilisent Debian 13. + +Plutôt qu'un seul conteneur monolithique, chaque composant du collecteur s'exécute dans son +propre conteneur (Centreon Engine, Gorgone et, en option, la gestion des traps SNMP et la +supervision VMware), le tout orchestré par un unique fichier `docker-compose.yaml`. + +Cette méthode de déploiement repose sur une commande d'installation générée, qui télécharge +puis exécute un script d'installation sur l'hôte des conteneurs. Le script génère pour vous les +fichiers `.env` et `docker-compose.yaml`, puis démarre l'ensemble des services. + +> Voir [Utilisateurs et groupes](https://docs.centreon.com/docs/installation/technical/) pour connaître les +> utilisateurs système (`centreon-engine`, `centreon-gorgone`, etc.) utilisés dans ces conteneurs. + +
    + +## Prérequis + +* Sur le serveur central, [le module **pullwss** de Gorgone doit être configuré pour accepter les connexions](./pollers-containers-prerequisites.md). Cette opération n'est à réaliser qu'une seule fois, avant d'installer votre premier collecteur en conteneur. +* Un hôte Linux sur lequel **Docker Engine** et le plugin **Docker Compose v2** sont + installés (la commande `docker compose version` doit aboutir). +* Vous devez avoir créé un jeton d'authentification de type collecteur. +* Un accès réseau sortant depuis cet hôte vers votre serveur central Centreon : port web (443 pour HTTPS, 80 pour HTTP) et port TCP 5669 (Centreon Broker). +* Si vous prévoyez de recevoir des traps SNMP sur ce collecteur, le port UDP 162 doit être + accessible sur cet hôte. +* Si vous prévoyez de superviser une infrastructure VMware depuis ce collecteur, l'image + Docker `centreon-vmware` doit avoir été construite au préalable (voir + [Conteneur centreon-vmware](./using-containers-advanced-configuration.md#permettre-au-collecteur-de-superviser-des-ressources-vmware)). + +## Étape 1 : Générer la commande d'installation + +1. Sur le serveur central, cliquez sur la zone des collecteurs en haut à gauche de l'écran puis, dans la fenêtre qui s'ouvre, cliquez sur **Créer un collecteur**. + + ![image](../../assets/installation/create-poller-banner.png) + +2. Renseignez les informations concernant le collecteur : + + * **Nom du collecteur** : un nom unique pour ce collecteur. Il apparaîtra dans la liste des collecteurs. + * **Adresse du collecteur** : l'adresse de la machine hôte sur laquelle vous allez installer le collecteur. + > L'adresse du collecteur n'a aucune incidence sur la connectivité : Gorgone + > utilise PullWSS, c'est donc toujours le collecteur qui initie la connexion vers le + > serveur central, et non l'inverse. + * **Adresse du serveur central Centreon, telle que vue par ce collecteur** : l'URL que ce collecteur utilise pour joindre le serveur central, par exemple `http(s)://10.10.10.10/centreon`. Si votre serveur central est configuré en HTTPS, la connexion entre le serveur central et le collecteur sera automatiquement configurée en HTTPS aussi. + +3. Sélectionnez **Conteneur** comme environnement du collecteur. + +4. Sélectionnez le [jeton d'authentification](#prérequis) que vous avez créé pour ce collecteur. + +5. Dans la section **Générer la commande d'installation**, cliquez sur le bouton et patientez le temps que la commande soit générée. + +6. Copiez la commande à l'aide du bouton situé en haut à droite du bloc de code. Laissez la fenêtre ouverte : vous en aurez de nouveau besoin par la suite. + +7. Ajoutez à la commande les [options facultatives](#services-optionnels-à-ajouter-à-la-commande-dinstallation) que vous souhaitez (par exemple pour permettre au collecteur de recevoir des données des agents CMA, ou pour superviser des ressources VMware. Dans les deux cas, vous devrez suivre les procédures correspondantes dans [Configuration avancée des conteneurs](./using-containers-advanced-configuration.md)). + +8. Si vous souhaitez pouvoir utiliser les notifications par e-mail ou des plugins personnalisés, suivez les procédures correspondantes dans +[Configuration avancée des conteneurs](./using-containers-advanced-configuration.md). + +## Étape 2 : Exécuter la commande d'installation sur l'hôte des conteneurs + +1. Exécutez la commande copiée en tant qu'utilisateur autorisé à utiliser des conteneurs sur +l'hôte cible. + + > Si votre serveur central utilise HTTPS, l'hôte du conteneur doit faire confiance à son certificat. Si vous utilisez un certificat auto-signé, utilisez l'option `-k` (`--insecure`) de curl pour autoriser les connexions non sécurisées. + +
    + Ce que fait le script + + Le script : + + 1. Vérifie que Docker et le plugin Docker Compose v2 sont disponibles. + 2. Génère un fichier `.env` et un fichier `docker-compose.yaml` dans le répertoire + courant. + 3. Démarre les services avec `docker compose up -d`, sauf si l'option `--no-start` a + été ajoutée à la commande (dans ce cas, démarrez-les vous-même plus tard avec + `docker compose up -d`). + + Par défaut, deux services sont toujours générés : + + * **centengine** : Centreon Engine, le moteur de supervision. + * **gorgone** : Gorgone, chargé de récupérer la configuration du collecteur et de + communiquer avec le serveur central. + + **Référence des fichiers générés** + + Le fichier `docker-compose.yaml` généré par le script d'installation relie les services + entre eux à l'aide de volumes Docker nommés : vous n'avez donc rien à configurer + vous-même. + + | Volume | Partagé entre | Rôle | + |--------|-----------------|---------| + | `poller-engine` | centengine, gorgone | Configuration de Centreon Engine (`/etc/centreon-engine`) | + | `poller-broker` | centengine, gorgone | Configuration de Centreon Broker (`/etc/centreon-broker`) | + | `poller-centcmd` | centengine, gorgone, centreontrapd | Pipe de commandes externes de Centreon Engine (`/var/lib/centreon-engine/rw`) | + | `poller-snmp-spool` | snmptrapd, centreontrapd | Répertoire de spool dans lequel les traps reçus sont écrits, puis traités | + | `poller-snmp-traps` | gorgone, centreontrapd | Définitions des traps SNMP transmis par le serveur central | + + Chaque service dispose également d'un healthcheck Docker : la commande + `docker compose ps` indique donc `healthy` dès qu'un service est complètement démarré. + +
    + +2. Vérifiez l'état de santé du conteneur `gorgone` sur l'hôte des conteneurs : + + ```shell + docker compose ps + ``` + + Dès que `gorgone` indique `healthy`, la connexion au serveur central est établie. + + Si `gorgone` n'atteint pas l'état `healthy` au bout de quelques minutes, consultez ses logs +(`docker compose logs gorgone`), puis reportez-vous aux pages +[Rattacher un collecteur à un serveur central ou distant](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md) +et [Communications entre serveurs](../../monitoring/monitoring-servers/communications.md) +pour en savoir plus sur la façon dont les collecteurs s'enregistrent et communiquent avec le +serveur central. + +## Étape 3 : Exporter la configuration + +Sur le serveur central, revenez à la fenêtre de création du collecteur et cliquez sur +**Exporter la configuration**. + +Le collecteur apparaît alors comme actif à la page **Configuration > Collecteurs** : + +![image](../../assets/installation/connected-poller.png) + +## Étape 4 : Sécuriser votre plateforme + +Si votre serveur central est configuré en HTTPS, la connexion entre le serveur central et le collecteur sera automatiquement configurée en HTTPS aussi. Pensez cependant à effectuer les autres actions de sécurisation de votre plateforme Centreon en suivant nos +[recommandations](../../administration/secure-platform.md). + +## Services optionnels à ajouter à la commande d'installation + +La commande générée de base ressemble à ceci : + +```shell +curl -fsSL /poller/install.sh | bash -s -- \ + --type docker \ + --poller_token : \ + --uid \ + --name '' \ + --central_url \ + --appsecret \ + --salt +``` + +Ajoutez les options suivantes à la commande d'installation pour inclure des fonctionnalités supplémentaires : + +| Option | Effet | +|------|--------| +| `--with-snmptrap` | Ajoute les services `snmptrapd` et `centreontrapd`, pour la supervision passive via les [traps SNMP](../../monitoring/passive-monitoring/enable-snmp-traps.md). | +| `--with-vmware` | [Permet au collecteur de superviser des ressources VMware](using-containers-advanced-configuration.md#permettre-au-collecteur-de-superviser-des-ressources-vmware) (ajoute le service `centreon-vmware` au docker-compose). | +| `--with-cma` | [Permet au collecteur de recevoir des données des agents CMA](./using-containers-advanced-configuration.md#permettre-au-collecteur-de-recevoir-des-données-des-agents-cma). Monte les certificats TLS et expose le port 4317, pour les collecteurs qui acceptent les connexions de l'agent CMA (Centreon Monitoring Agent) via OpenTelemetry gRPC. | +| `--tz ` | Définit le fuseau horaire des conteneurs (par défaut : `UTC`). | +| `--debug true` | Active les logs de débug sur les services. | +| `--gorgone-ssl ` | Remplace le paramètre SSL utilisé pour la connexion de Gorgone au serveur central (par défaut : HTTPS si le serveur central utilise déjà HTTPS). | +| `--no-start` | Génère uniquement les fichiers `.env` et `docker-compose.yaml` ; ne démarre pas les services. | + +Si vous avez déjà exécuté la commande d'installation sans ces options, vous pouvez également +ajouter le ou les services correspondants à la main dans les fichiers `docker-compose.yaml` +et `.env` générés, puis exécuter de nouveau `docker compose up -d`. + +> Exécuter à nouveau la commande d'installation régénère les fichiers `.env` et `docker-compose.yaml` sans avertissement : toute modification manuelle (paramètres SMTP, plugins personnalisés, CMA, etc.) est perdue. Sauvegardez ces fichiers avant de relancer la commande. diff --git a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx.md b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx.md index eb126acb4d65..dff43197288b 100644 --- a/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx.md +++ b/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx.md @@ -12,7 +12,7 @@ The Centreon **VMware VM** Monitoring Connector relies on a dedicated connector > This Monitoring Connector can be used with either version 6 or 7 of the VMware API. -## Pack assets +## Pack assets ### Templates diff --git a/versioned_docs/version-26.10/assets/installation/connected-poller.png b/versioned_docs/version-26.10/assets/installation/connected-poller.png new file mode 100644 index 0000000000000000000000000000000000000000..057601c0e7afa2d8f2e451e82a80458206ded3dd GIT binary patch literal 23027 zcmdSBbzD^6_cx0A5mW>N0cjNhB}KYTIz+mqo1tSU6$NPl0cq(RkQjy<5G5ps9D3*& zYN(k32AJoV-|sK(bMO7V?(@ezuNR&@=j>Q}?X_3D*FJ_mQgI^ z5;7SQl2bzGP6JPHt94_*?UdVdxkn_Wy^Lt!$3NB&RUVR%lt+^vnVtoHpLdqmb0Z<4 z{PyGTR6D4^0(f}U{i&|I2FS|Y%hc79M9$UH(#g#R8tM4>>Y-iM+c>eOa(-ogyzV^aa962w>np_C)ivAv^ zc;~hHjW3&)_6MeKzOY{o$~t%Z)w=P6k0rMs-ilkfon&GitNgY5c2YN@yLPxq`uLzh zCS!BZx>roVzt=~)s91FH7|oKwl3%|ZpJ%Oo1t9mw^{JwcecrJ7k8ND~O#QF!)`OE;kpZ{q;_Er$hCm%-i@*Q>JCX zisY7L(;M&~%muFZ>WW~4TQ4G}=`O#GKe>RH1L>bzYU4Am*|wG%rx_j>K?Me0_gW={ z3q0c^V8fm;44G)n#76}-28Lfr8*g9cqo}5aq|NmB^3|`Wtko|%ka3j^TerkV;}(@c zX{~#T43XD2&ixwefw__@2x2&JIX^l;vFK`t4K=0`$A70t+IAvJM^PCB{WP3Xw%Ftn zv#)EoI|mkt-JQHn3MkM^gV-yG6_ibyGO|n!FljbR4}fCyPI%O=UC>AE6BGDJnC}CALqWk8_-+Zs$}B) z)yYfJ*i=;BVv1FTfhXABVN6wcaKJ#Ob8pH!+vv7_kH6nyE=;CTPEIu4j) z|4=deDtcpUYpcwB7Sc@ zk|H|`3kw^Ym6_%s;JTloq5zVUlZ$4S;uQHUTOH*$&?-TZDe%Et-_@*ic_WQ?s@>@A%KdL5>0_+nEjY>D$bvUbsA%Ijw%_ePb%egJuGkY+G(Bc{zGLv0v^&7~!wMj* zw{{@6NOIhJRNL9e>-%ytJIhqtzqx0_ek%t81{e24%hU}_c&8gGI{lvIr}IFk;%LXC zrGLz;!z?YO3E3kN`5woJ6U7FdKax{<^`@gG8p8h0FjC}BP9DtFUvB>oms9}O#^=I3 zd&P6DK~&nmh4Ll)tw-Z_`LM&I{cKjaiVp^2Ui^C+eJfAo4X}Gi@50yE%cZsHM)xfL zzUq4-FR}QSvCmZghrImXESqN-dZSGxCF$e30_C;e6eWee_gqCo3{R=>Nx`S~wU?=7 zMn_%09cq*sr0fm?(foNEOEPsxHp#ouVDZ6 z`a#dTFOhpRT5++c0LueX2?pSG{33&e%J0_6SN^n?+Bg*VHhnFX=6MX(qx$vwlhuG{2HNvPRfxL{!~coJ?gOE5tF{sE>&-TZRU@3-)R3uK;aE|yvxRv zgdFr93{3TB6j$YcoN{0V$rlC;w$~va8yrMFu{9i~&}2QpVVmdrW}HALHf#Ez-b%Q7 z%!~N|@I;-!5&gx@NxKat)qgRl;0xCSV2;2LM!ucn$3gv`-Oq-VY`=*aC*4aJX6_xn z;63Y*x&^ij#!W*Kx5;hZeuLyH|Ev8+pCA0s&)O4CZumY-8~oYWjG<|5X3UuIN)OXv z$n#$7EmTuS1$>H!Ts7%GGd_U?aVLflZ@1Hk-`e1lap=$G1}X~g*IR6x@C*{) zB{6?3O1y1zcA?l|zCgzp10gPVf$@L)M*L-QE_Fi&3e4^&HApkUimx zj%OZ5{82?O88!HIUjh=Pp$ASG{I_-dwczrTAKSFSbPVnr^{jVFe1ii-=oqa{aDLDLtl~)IlM{`y<8#qA|;zq`0Nsf}*HBq&X<85E-`~ z)V;34zvvTttV5a9(ae!@SD-etjm@6&NA&{b--E=Uz(B2GaIF9PB>3GtNwo@M=S=~z zE`Z6Nbq>>wMl_B$Dw6KUG1wVaEd6NtvU5Rzqi0!NiwO;BM_to^aEy^9jis1%?%pPp zG2V}>yhuse>EXAru~A`jCI;H0>~v=s2{9leC5_rAB_&;5ORN3U(e34&GF}M|cdQ1} z_Igx)sb@E&Vj@3^a?Sr2nZAc}Onk;}2rfJE z#X4x9{|G78yo=&!suG=IL5zQF<(e=%JL?)W9`wzOV?IQ}GD*3Cf`Vm8MwwRq)%rs4 z)jd4EONbQ%$ER~Mtw>7ph9x*$1;rN%2i%?0{V_)pYQ^sg@Ce}u>*E^Fv0}4E?N6jv zqd0>$vC|FfD3L`&L<-)R#)bB?_e5-K*R*1oT^@|@IB%_$xKgoPp9g_FZZ*R&+c%0# z!QHAvtB6kKOX*XsbDJZU3j7`7z$z9kXsTL{NKY74*IaAEP8O_DYTlKq58*y{Da=;O_NwmZrt8>A%v>OKo1M&KiqFo9GK{Q zt)z$O1{ktFTK>2(>{f+&JEflZ4f}PwdQJU337Gn=O# zXG82EPc3s{dO`hkDxgZ)ZlU!O`%Rz4zS%3jC)23j6sZexUM;%(G^3mv;vCeW5b#AEV(J(Zf^oD_=LAvdD3$Fc>GmK)kq2#zlD9jAu{3>o^@(jyHh{_?Ra@hYQjD^!uYf%MDg2ANdU4 z1&6U-OIpl=IKY9FktgmxsMNc%UYk9XHFOmrQ| zs8!p%5k=!uO{Yr5D;rZHoi29hGfV=L!S4s~d!EB0 zTjhYYU4|2a*W#B!vg{}x$`q-D@?4TGmhmknRUVQ?CHQ8K^o&PZsq{t1b*s_J zUf-?cNH2{l z-T7_OZ#$(ATmvbl2r|_;!>zuVxAaOM+rFo7UZH>l(?I23`({zizwFnq6b0Ppisb>mo&SrrU{27QY1Ehs;LWC04>!irjlEsze?Zq{6X~YkhL7S z&4hxt<7;q^j->6Hzh{o?66w6|J;T+>WEor2jB@{C8ueFn>)bJ@)qcl;9H}nG=j|9R z&+ooq{o?}hTXwu+&%UilX1dJvB!ghiQd|&``U{Sh;9?o%#_B^>IJJaOwL?D4O!-g= zN>i`_yU)WFp=<&!)-ETPV_`H9_U_s^w=?sZM%GRbbm6D%V=Hz7ua#!&ZyIyEqH6Ra z=FVI6{B$DYJ3hn#5r^i{(wmvZ^MFK=xomt5L?=~N9p|-Y6RpK!(FLhhjKU{p%sG3p zCebtJydq&Y3i^ca!d1o<$2e6$*t_#x{|phCna|DLo}X>MConMWVK9;U9i`cE*WA*Q zyCB^GnkA(}{&6C7(17?*-aMt$eK>xTF0yQ3!o~#5XqyiUMoIPR7r?t;SfkMp+Nmhj zm3~Jb1gfqmPoLe6cRsh<^c0*7FrxKuAv|l}r1{|c>>C>CUU+~tV#@^I zP4A@#1nGlyql9c%B_EvdqR-gkqhTsay>!a+b z@n#SyEwl8bKUVC#SmBX|WxutM3E#77FLAlefND_h08S!ZYzyhM){)+l-Ff3KoaaiN zl^@126!O8oZqR^>UE^+S4F6fnxvvM_7>KlGVM$B^SmWA8E6Y(TFZaC7D{qZ)hU-0;iP4I*p{-30fl)YaDpGaR*w zNkw~N6J-RL3j(H;a$%b^NN`^~3>bC8mWESk#sWx1 zNqU*xtITxNYUR@*`@qYH__jqrlnl8ZE8qR;=UGta!vY+&v{F4HbX<57+^{&;w{X%w zu41g)bG|AHG@tytli0DLN&}Nw_;w022AWYvahpZ!?s+tXSaBvzi=EfB=}|K;Yq)BU zU_Q(RmCt@fz(-+FHD2>DDTYYghxM+^r{X?jRBfo(=Za?GgAQB3Y&@ z)?T{NGsy%1R_pUfr|1|+^84Vz{zwd6#xGy>JQxfP4hbPom~W4UL7^Q3mT}SXy`sM~ z90MI)3>R%U5NcK!8h1SY2`Fl^{|+$ZK~lh=VwM+WtzA1A`MadQccX^fRegY@LX%7a zWINw&fKY09KThehKLMAX&YUzwb0IBFE7UNBAMQ`sfO+XxgQj`A7UTcyj)QK6T^~&? zIq+J!NUP@BFVpvNN3!FDE2MkDN>(5bhE+u}{?I1RlKhr(e$1a0jvY-gE5hC;-1rfu z_@w`u)mDd9r?OLlOGolA?{zi18vWNQbxV31w-_gLo$KpzILVv6V z$@i2h00Xdk78uy1yp(JV-2OvMNwO2XNAn;62$rj$P#|ztk#$$Gny3c4aXfS8OvS6t zp)VVH5cZz{`3;@FAj6I5|6x%v2WD<=PIifT9gRl+Nm^)Xsi`3{ABVKHw_Dy{Q&Reo zvLJu^707|Kw7fC=o44q0X=&Noat7+ItP~g~#G;}iBdIT(6{Gz*Q9$w>-#%&%I4!~t zmvUd}`~Ll1>L0A6pc)AK9*0ndCINO-P3;n&^6w@uZSV2(_YV%TTCwNBjEsz2|70sZ z39rllD|ca)&eZV-_$B$$UCFBV2P`D{=;L|&4+05bFNi3MzsZXiOJgzIf6=#YNr~8= zWR%nBXVZ>YwvmJii;h?d2H_R1KU`2u27~Lpx6P7<*mWDc%Nw(7cVnad7Fb#ID)flz z$8YYRg(Qu>+(ddH95s!i4QF8ea?(371F1S>x$wNUV5Rq`;)r2@*{RN(b6RweCIUOKtUGT8S|P&x})^! z@av=T^4-dheojaEB=LKhJ)4)WrF|Z|s(PG;?gm{Gr}A1&QovH#Qyibd*lodBF^Lmf ztG2h;+(|c(3(~|Jy*NUmDuOA-cU*XOM>0Q8MsLR4jKBvq8nZ@Q z!M6w6BE%>m(5iC!H1a2L(pQ}(R|WC%BD74E}7# zDcOPFEQsvb4D4AIZo2K$lX|VbyZ9}LjpVSJen>}SoJ{sV{V#S5sZyh}e3nKvr&vi> z&PF?E&-YAz{zzu=-klPP_<$Q5*OG;BslFelk0Qj{bTwz$R8Iyp1Rg}XXp-Dfx|f_q zRUm8wsVtTbYyBdK;r#lrFw)$d9A`vUB#SCpk?Eoe@icQuw~07$pS+>B$e_{ZfGd=q zL8uYMGU=F1-sj~`(b22iO#aU3vZM>^l?}~jsK1>TBl*mbCF?jc!M)mjT;H{l zx7p06f#R_}Rd{uYCZA1^=+e5aV@%~p)o}+XY<>E}nJ}4JCE0*QDc|~h-6PkN(}w-v zBH3PJm(thIpPUhws}+8^w^IaJB%!!qW8VsYMEqp9$v-cyQPf;mc1!Jwougw4(nn~Y zyP6x()@$yJ8TYyTz-LdO+~<(mT#Y67aLX;;BXFqtMk9B@RiEeYCdNGG`Ut2Psv3lZ z>#;1R^^??sN@=Pw#nJ}a~ESHc?aG#&NmKTX*3N1+Q1DEW1 zbsY3hEweS+AIO8gh1l?U=O{7f5G%#c#M@B#>k=|79U1f|MZv7}CLZ|nU*K8wLO~B{ z%8HR*5fHyHIZgK#Fa(Zpy;Ey#t;@AUUsHOegx0w_&_BHRgS1tIi%nJ3^qxp_3~|9H%H732Wb7N70r}x9jyEqO}pRlb^ zM?0Bu4knjy-b-?fLDi!k!lay+P0prSn|OFq2MukvzEk>Wnf;Ifb9a{OjbewD7SpVx z%L>!gveG&&%+rylx|E@^)EQCp5~pNHhK2Wcl$qDa?guv81(gozhoL?P+}!miX#@9P zI=^9pSV$DU)gHl58Hsd>(yG-fc90yYP3S*bYV_z(qL+20?#YA%xK>-&F!38xH8DnM z%`@Yy>+2Qc-EkTGU$WGfxbowH-GYUzx^zk zAh98?k!&5|yw$1kM$JLP>6ZT0<4>T+Tr=XN+Z{KePv6lHY?w1$lC1B#wXW_b2k z;80=u_3lq53LPS6s4pzF`R5xM44c(A%|*M)3x2LS1>LPeGVgF@@u=Cz&Kn>ZBUh}T zp;HcFl{`JMs~pyPBR=GV-!bPa4br6Yj&De)^>#alDjb(Ca=?d4^BG5rA}WQhj(@Jb zKE3{a`fBrOpD-7M5ScdEJ~&&^gqi7aTB`04tp7;-Y)Pl@+oM2(cUD&VTxI~cU&=@z zlpepYDL=H->5#JOt{xt7jnaa=tpC9|?XR#*I<^rM^Vhk0b0Iimy(gwVp@2tRWP=;M zDWjt`$+q_J`MfQ_t{6ZAHbu^phEE`D6qX%^rFu_swijiyyts8n(UqI?2_%;^1a9e80wtoDntlA7!hlZrCD&MWNWV+5a ze!?tZhkRl@jNZfrKlv6mp=AHh@?8nj(qe`qJ(b~z;FY7y%H%$7M`*74b844Fq3YY# zS-AC5=XB>Pmegss-AO8H1u(=bhPGY{4~S2K3TxP^ z*eRszmXp7=4JYfLZ?Ea{FK+M2(rMl9C=JCPcT^>4A*rHPYI1~IED=IOHrm)b{8rsd zu{=ByJht{O=a={6?OUY^FcLJhb{1AV*o>+?w~PLAgA-?vsT=g@UOtV!wGK9_Lxjf% z{kK)+nq+%nYpL)#1^rVU5!-hSv>9G{1{EVcFFg}G4Jp59G0P}WDv+!Fj9`;~D*~H6 zcF0^(Y1=@x(RG8g@~A@BgcSdf#FCuM<|y7d&8POfiy1%KUgP!g=GU`hiSr!R)csz2KJ@YIRm)utd`X|Rr9asPHkvZf=4p%$VPPp2M!xomqRK&Kjg4F=Y(oZDkHY6KQPzz&rR(Jv zyc{-jWh@Hzj2?dD_R#QF`kHYUoUD19&HkDG$Omzz+g16;MxiUyGL=|}akv+4(=(1t zi$}y(iNUC+{?t^y;?WWPMJ_^#M%ES!jOnJVGFN%SC$uPX_oYP7pV4F~jw-wIK9pa2 z{^o+H2L19Gx7!k==`Nek$iFo^OeH>%%ap;bNRn#xam`6GoS{C~{z3XvNoBDIx~lQI z)p_4k_S7MDDO(Y~^GsK9ud4-50$GQZk9pPB#OGUvKJUqDJ=U)Or$%+GjqU4LMBCE> zy{7Yr=Pn*l&{E!kgg(jE3!Ll_H(^V6D%qvUGx8Bp-1f39O8hv48IQ<^Js9L~>ck;F z8tW4VsXgAEJm%SEkVwA5p#gxg{|LBeKLL{~vuCvQi}82wg?ZrdmA_{|0yUMZ_er(-#41vOck46S*Ax4nq> z?n~cU8~d~(4ODvpcE(T)od%|tV~g=!Z0>PeFZPD3U2;kvMB&3q9KU4}fLbrn&2TUC z6{cj-<+sOyd%Eon%lHj3$QSk zg5^gW&8W=KXb2aOq+*dmW+wCkgJ4IdUzEJiFE=}jc2tO?qMG;hCByhv;JfW5tTLvz zU%B}jGz!e&>M5D;g-)+UTn{`9)?juxU^;s zMzEc^Y*nS*HP11124zNLoXf(OD_`qplL|oT4jm$4r|_`@O8!ZNTg2;e!&~b(Hk?rX zb{?&#p8>MrW}km;W^d!F-v?)DSTDh&qqtQ3ZJP%lOg2faB~!7ty=WFIRg|PLWv6u= z5*p?$rT?wkJ!-TH<6hY4QD#5gUE3u_25mm+6fK^Kkx&s0((9C<+dsQ!+3XZC5T$n~ z+*69PiD`phLkjsx@p^>9RXLC?PG~$eMc2|kql4m_7O1FQH+o&8R4RYg88bzqY2$mG zf+<8SH+(js{wRVeX$?=jzV>mmVOMov!o592E;yZl|2o;Uu|IP#l~L2+ysGt9qipr0 zi_gn%#Z4-sZf<3efg>b%QCu3p7N5eFQwK-Uj?NVQ%cAkTR;lllrozN^bsBGX=(NaQ zMzKDjb}%Xo{DAcouH+PXo2wp5TAO#Dy?AzX#kb4k$c^xN>fK<*rAX#jY?+(8Nx)ud zy^wfjjjG&s!`^NH{2Z^9DbIXddGYG75O&vPa?7Q@z1@JoswVWU9&`gm>$0ebwJect zhddtl8sExWmQok1Oy@;Q3f^#Sdc;G$id=fg>9iu$-YD363+d5~uuI|$A~8@Y zvc;|XC(v}EJ4(riw$)WT(RqrKBR0De3*z_I7|a6;_t+jb(-kjv-)mZrH1PrC`DK{> zbW@SW*&0BeiB80ioY?~tI>tVWs)L7EL@X*nP>i2{Z?ehDe{Ud4CN0o;b|(hu#U4$; z!XhqQ=dt|7C>rZ`7*-l>40i7c?&z=Sp_YJC#7-u3Me54U<~@5uXCncpsUwNX zmpYsceFtnuDpRY+>t$uyydGEwl4iad$a(52Ue8_w7l==Z>RqVdN=Q7Umtuse_;p0b z-7zTf>DqInNZaAiKw*1ih7sPB*nY{xd!R&*Bh7m^yizU6Qq)rK8H(>kcVS1BJu$rE z#G_PuDqpQj^eq*Yp_I3wI&79DD4?$%K zm5fXtXOm~9R3yJjZ!RB}5>&9A?TM33qo*)y(3{Gf7JrjM+wEczprNR~W*6d+p*-iR z&$ze{FR&?o{7nRNdfq5^Q`4mND2hX;f8{LOyUa+(C;8{JM!70`YlSO5t6I6Z8CbIi zCi&P6s9B?)6Hj#gn?rtBdT_E|8a20I@!7`JVsEs}7<0g)g9C)5-)np^S^N5GF08C^ z6+S$tHDF*8YKHSqHA^o&)+i_5Z0s&p%lcSrgjJVW6UljVp;K7(4!hH*r!jlES9aU# zRXcD4_t?A2x2G@@iK|7*A}098t)*}E8Rs_dHKfGf85m|Sd+DV#3whqfxD{{Y)pa;h zJMLj3iN?pcfbHEEhpkoRUK+?vai}#ZEWiJ-tDAmym>*G91g_Ye<+DHGCK@vMX|`rj zm9KF_j7o;2=hE0xSHGp@A3rZ;%066KA#X=A5#ml2 zuO?IWB~TzjpLr=!0mY&CIYjxku~~YyA;)b!Rg8LN&i+E+I~Y&t)hXRk^3&P~fR zoIR3QrBW5^@H^f1-ShY|G7XjN#%RDxFos8M!UYDhCuT!CxJDWdni+^bxHzLj4cMu8 zl=Q)ZMxvo>q4ZQB@k|bkjRHlmXeUF+)HokBzwMHcInwdhK}n<3pDA(3$&v+Z#r4LW z*v*u(FccrG?+HHvGu%<{_K)AWuEVhrM&C0C`mmTge2rQjr4!_=-DgL=rh4k*-n2qB-o#-Vkc_e5HKtOa0leg)coRwt>7Do|-QZ=*&BN+QqNfE2KDSBjvR> zlbn~R)!jCdP|D`iBzZ3O_9Xtss<-1X9!m}!iHA0@j=ejLIh^bPg%M7n+UKkJV!a5T zW7N$8(Njek!6jvillx|c(vOZ1b1B!bsbkRQxo4unW)Dw|=pSD1iykrfsEHDP6jJjX zMX%0(pfadC;To+v)~G-LX+9j0g?i$GhhwpY-M*MA;6&deVeZQ(SvgX@W+lwi0f`wX zaqW(K!#!{>VPI<>k-x>t5LS*Un%Q}Cs?Eggk?dqIlY3`jK_ds}2_E`j`=c|B zBb889&{{U3f$E*8keFI+)NX+PGj#aTFt_A%5s|{kgf*EeP%~fa81LkhfJADBM_vkk zv9T}zoL+~i-ZRtPSfCY|N~qEiTzV7lJoL2s6H-vxcj!jidPdDiOP{Lgd{P2rVCf7rHeTpEV*gQ~GF5b*fcBv;TOw@6B2ZeC}9ojn&Q4!U9%b z{lzYDO+Y?sH=NSSxJ+6p5y3}FSIrm9K_|2#FAD7QKskl#VBg&I9WLr+F*CTy6z-t6~k*3%+N(#-`Q+i&6L!hXIBG|xfb1=OS z5qhXE!Cbt_Oz_^=xRti@u)Xj3w50W5eOt=hx{zBrfBlfiQ*+3gq=lT=$b-tUGk0q* z;8f!jtqZdx*|#f)bNY#G%*S8$Gj7@MCpXu0c-Vz8OhYv}8WoIB!BfqnkWO$AeIqHcEM2F+DX>g6>gGSd=uc9uc8i-X)&yXpmRdP{FdBX?N|M7V z_4hBe_+*Vljnrg4aa#Z^=@IVM)i6b6_Il@jxx-{))H|-I=cI7hFWz=bsbUeKPja-7X3pNKuH5gyFCIvkiZ} zx(HR|>Xk|fLg+JoE{eG)-ZSrU&BocPQWX4{>)8lx&3z19W6%I=1JU_X2Tj0e^`$3# z&em7A7QTj?k8o1m|I&3(mt*QKjLYv@%3yUC7YDttVXMYER{o4dg}<{Re&8 zV@`%Lw2jj3%K58JceBI2`?C6j(p(1Xmu%;IHYq*UUTn%)v&c%OKP_V~EvETL;A&Ul zw#}vK_tL1-J9+9n)DqAO96kL-HjG8(2HDTPNbCavYO=}xR<{4>oe*iWDk~US)$UM^ zYGqcXQND~2qTdat+b^8?#N>Iqe*boxNr$uPBcJ6foouIS$;}y-)C~k8`fa%*akq-6 zu9fgXrWkM}C33)~?$TlT{z=$dc&>ZwegFmW&O0~kerVXs?dzZwf7;TkYj#A0;nLk@ zJWB7PnlfkldRTp#tvLw=Z(2}fez^mLiFYs7;N?(UW?ImEU`5>;1LT;9 z-tK)-DM8krzIA%i$-L|iO}i)lnzWl1o}=l0mFKsGt%78kMwqj6vr!s{(PzBcGX9sd z56})IosDBqr$180#kF_&1!}-m)v5z5U3Y2#)ssyi`Q&i^5<8N9mggDivCEh(frIAL zwN3b1m%juh8NdC9S@KBI zE3*&}y;O|{E8U#egGHt_3<&iiglVSh62LOVZ9Hx>o|UqeaM?pg8nM8umNkg>FIwlb zCp=XsDQM-|+fXORz9Lgi_?81BmV>V`T1}~pp+QD(_p0ASw2}y>pJev>iX3|plBeVc z;VIHS?k#~b;C};^m=1v0=vEyMO*r6hHSNzSZPqTQyCI~?0Q=n|GTq=jo0Y57-6XV@k_m&(@D=4maF8>+zmiNLa{x6fZhNQ$GJe5GSsI37635yWIIlmt#^5{ zs?_6}Zm&%~_zRF3@hwThFiL#*DcJm089w@=T1zyNlo`B|xr-pCo_u}d?s&$01n#*4 z7^>8ox;5Zth#$|aKE+2V8{5%eUS179<8@r)+%^K>O(Ou_M4oRX;N1Q#dm<3yw<_ER zkV2&#O``<=TYS&L)w`yz8groH*cGtTMyu1X$4{tBU$$*k zVj*-em`n~;mpD%E0_TP*oK#-^YX}cO0)gRx>jCqBUv!+Ts@-Hi-rxA2o_qklFa9+G z$(O1tHy!oCT-JYJV7qVs+k+AR5v2W#!qPVbA0e(e4Mb1>TWi77SAv&V{@}PT^B(;9 zkc-3zK&?rVu8~$lH~klAo8a61BYe6ibAiS6XrQzYK&MbkOg4eCiFFP6&tIXS(4+-A z`v8Ec`{C08U5y0*^XD)prWStBkd+Ss1w%seWp4(>P;eHQo;-l2b_S&^kLqlLGngkO z^Whk3y@}w*f5A&|zl5MmFFAp@QXb`lz)ZM#8}^tq`W=i}BQgL)?gKi(z)7e&SIp1B zVU6XmdR_d5nxoNig<$7HfcDUF!bwk~x5&WI3$L4}|H7?n-~aF7)`X=}A&|dazd*hr z44Gb9oA06zk_Duy-t=2An^Jz}(UJj!Y$MbH>2Z?P)cpj7vZCN2&XNTjDmT;;P-z zgeBTrR@vvyS6-2-_Yd{&acV#VeqDkP=$yNWluZj&nb*}wuH4?Qi|IODj>(*<^^vS2 zd@Pns@*YW$P(^Q}pAf9B<8{64O3mpy081mp%=Kh6Y*?+>Y`YARk@0QuM$HuK)&#)cihOZsv4cR*h8P3n3>Uj(L zaEE{b&OrE>HgVnqq4dIm2n)$S1y~oofr(`UiBdSoZ7W;)7!yy#eGPQ)98T`oo{h;| zK7rrEgCwNA1MnQYe5qiq*`eY(;!YP6%b_76zf|;audO4~v^ENnh649*h%F0xf*A}S z?}@4AhWXI4x@e#q?OO9!hwg_CMRnItZ4Kz3;9T<}JR=fR(4Dlf^xF2BysV>*MI*Wm z{jq(A2ko-c1}AeF6SV8HsV9Cmd+&eRqt%Cx)4hX=U3ClhW6h20>@(-wU@i;spi)J< zY3H6SuPF$u)X>L%gMQFO2U+)=;+BiVt@e~2c&Wd@I(I$=L%ZoyHba-P;u5$x%raefLAY4n?eb_c? z!s)N@%(=}@EW0GZCFAre3m)b1uoa3i87@3M3GAvsSfFyeI(mbvtid(k_W01cG9N}H zV%PW#aItA9Hu6r1JO;AhwYyr%#&72aUA*&mIx=RF^fc>v=Rz2eAmK2jz|4#02ce`Hi1e`KgRmn3Vn0x@Ba_FkGzrN>J?&0_V zSg`*>Af->5Jw$h-khi|qBYf47>x|N;iJ7z1X{*IG zje>T@h2}eoq|+Aj1~VDAH0ymVkwRaMh!@LMzx_wNb|YZa<1lX5aM?A|!}--4Xx2RT zQhx>mk}b2rL(s|YjXjZb&MeTpgfCw8gWCriha!!=W@_PgQah`JNX9mj>*SU&PrfO>e;C#Yz_cD}HTuj3=t5o$9J+!7j69IoV*aOQ zdP@987!ag9yVGDfUhf6M?cqMGA)UrN9`N$gz}Cf`J3Z_dC-eAGD2@GYEhdg$j3oMX zqkW@HV{x{q7#(*qBb^kkc*OUlJzgrK(QGfx^9OPOMsF0CfiVr()wr0Yx@M zqCuY#X)|9x4dWZuN^)x4^q=hs@shbRY3eP)rJhr)Vtfjd@YNtUL2QPrely{Re5^Hk z4`5j5_mC@{#fa1>5?FeDS-EOMGg_mmreL?AVeSd}eD3&|*x_XpL<^nn(Ncc(mDGxP z|3dpr&uzDp=T1yM&QH!atxHrdjpj?<#>CCr-O_KyDh$F(;NtQk^PlbM54s7o9zyjd?GKP0fq^!iqXoH&o8GrD?A6+nTWXgJb~|_inA) z?Q#IcMMsTzJc?c1JH@GLw8XK?Wl8b+O}1O9r61eZ;i~%m4?Ei~Vo%9tFMV5?ritq^ zn7)o*8Cq@&8F=!Q^j%7q=xnE&M@hFYNFbFWf6Il2C_8=!KIPN&poH%R1Ucb%htFW>15C)|IhBcHc+;kkbu@q|ns#3ksB ziDP1sB+h(YB%|fU9Br9kjeH2+au0dZ80nbyo7KeC4vSya2RM{0RSr&EMmv7e9 zYAu0&wS}RLZ*J~tdN7l<>c$&83)5BiHN=2Oz7al4uc%@B;f6`-DAlMOGfRqyMu|PB z2a0%OcIeT{l?Q#T#E~TIeSzz+j{Q^ypCf%FI(y+(FqWT`D;=h^gq~w)XFEXc9_{ZUzcw*#cMwwSRAnZ&w#(1syZYDEd+PZ;4s-KJI3c1oAQbU{l|3~mI`>7olU_FB_c6^)2p8pO~=OD(P1YU#A7rNt-_ zWGhXjqNp_lF(pJ25gAJm{v> zuO0Y&aP4|XHM-5G$-sJvhzpyJoQe1;Yjn{uaO9R>ebLtL*~0Z~Zpi^V0;m>$My^(9 zGv3MLF`Xi~Gq4A)bb#DeRC`oZyhZ@K?fRV_l@+gvz!p(iS=r`FGIMEx4S@k8FkYOc zJ^|L~UtzdP&aIjBgMKbS*|}LdP0}=8_WQ-zgDFuy$Wp5YrQdEl_PQ($}~H++=mfjU!@wl!%gH)f&IdJ03_Luq@e` zdm|P_T%`!DZTW7KQD0$f^4Xp#7*epasN<4tHD%+u=a>EIci^$|a8Jth7w1|6T|z60 zoq|N&p*UP@;Ds^JjTFMR!!!`}H-gJT#X9f|WO^){bpZ*j$?1|PVta0zRmTM{>V8b+ z{cq<7x^onFNUSeP!*q7&S3}MHhVUs|ihhIIkEsD;tp-&;z|}!%Q>|7-gbZu|RR})Y zd9vG@doXvyP3SF{sz#{Q<`}f~2r*=^9LLl=HZK{FCG?rFo6JxcpaNzm>FG775y@(r zRk2d>S4V?6ZFw?~g^A;G;Ur+&zFNkxp!88&Zx%SjSk3_}oQ6vTkroRT6R_;Dr6fuD zG#SHtTPZb1yS|EpsQGk?8>8fM4Jf!B?4G^oY(Er4bg0MDAAjMbBD$vL9)2(fs5TZo z_OEcekU=T-;A@p}cDvp09X!@}k5XtjR{!nwy{q~JulKOIatS@}& zqVf83#=3`#1;k?ZIGhp?6P(-ytrb?=X+=DghH&%G4c*U|)3JCfY&sG~>)QNW>^V*g zvYnu)T?S))3|Ns*h_T_cCnr%~GoBS_wAK$2i*y$o6L5Wod;LsKDhWP+#JpL`FG_bY z*Ti=?jd3?qQ+u>f-~L;Wn=pFjwPvI^?WyW9wZb7G_^5b{sd@UB-=o|t&rR1S)?ph^ zU~bY5IsbwNf!C{QI|6l7txz`Q05Xo0`w@^k8~zv@yZ6Rf^Z;NU}c? z>R1z*$$GZZW?V&kU7K|S@xVI>)Zb-Xzj#0C@ z-sXH6d1aec4rK)UHnZrFDK z`Rl9_FPy^5Z*ukBV&wK@`qCWks&(4(!&8{KRg!%<^8`Pj%x-Qr$6$?V`4rE=`B2SW zuZSOv)AAy^M3-C2cA93_M8O}zv%~YsMsC8Z4P8s4YW>AA*UZLtOOX!}9V|2IWrFL? z1^4sg^zq;*5Ss0o199#*xQ#N5bv1XkS6_c=e~R@`s}^SUJZj@;^!Y=}@YX3{5P8+L zKHSU^e2frP+b(9v883J$>d_u1>?rQxOYseL3)`QLV(1);rhutTBXouNf!5THGP^*6 z&|cd)?R(~xYyPK9#_PIoTu6xUQ%a2!k02(z zDe2|z3%iyqzhrZT+qO#$X))i3HJp{YI+q?)zqWSi3zhj4dfOK83G}wX#K}Iw$sWQ% z+^yZ7uq+?~wo`f_!$+5(Q#10jTm*nY--L9En0U@obCTw+s-g34x{4gchMloeo`;QA zBYRT0C$i9MnZL?|6j#~QLBrt%A^o&Vn}UA$0`x56++$xsmOhyY*-Cj@{(xKK`$9_a zBFV)9iJqQnZ<(!=(_muZbRdsq9FKGd_;at1IC=@AiImQ~GD4Va2E&NFnME1m#CatO3DXUW-rYtZtot?uJb72F0t%ybor!xtzbJz70GVa zsCokEIA)eO3)vPht$8TE?7pTJu}KYpK<(%Ke?g@SkVSM(LszL8R3UX);iS0gp8DHb zisL@Q8rqK#4KPAN`RraDF@)KN8}j|K{KQTl5q{ClsnUCc0@(;Cp^UUZRAvD#TG!BU z3OgthF`HA~k_`c1LG6^VG=k02H3Dd}4{Fi~izSDaOZp?rlIT;0J;oQuY>%ROdRqT0 zl3NnS88+V14*RCxvTo6ie-|KL+IH$#S^ z(ZK5&%lSRfHNl#jnN3Yi-2@zTe88#)_)>>I{3b0Uqi7Ha__@rGR4R4j^{C%D@3OPA zfp`%u9WA0Xb46>Lwibvc1Poy+zB2L#9f1E1_dazE$e(%V1snsmZ%Q9{^6h_>(0*hr z|6#C+o`6nwE|V3hw|Ax0TPw*p?`?l3k5;^^@6TM~ffY;bdz8JO_AW-q;BPi_y7?5$ zB^Wx&%{LhAk+*Q+r#ZPdn09`@VyxW%X;Cvk)ZF{Ix~0v^-P;hS-D{uPsX=P;wb3}= z$BnTaAlNs}e0J7;OKfGlk;y~))ir>~^{fwNNh(6d!Q+o(KFHMjEtZdx`ai`neJSjy5B4=}c^ zs}cmp_f?NS&&=ba%Q|vSCj(iEFV*($>-lDWdgSE;Lc%lW*VttLmD0q?dwWzmUBjIG z(4j9^yReyM>=|7#c)mX7IrgSt`&bbiDcKLJCJ972#eLRU-Wc1w^K$a`U3y-g;MtWdjUd>8V_ z_YVLj+(R9xu0arUf)G5J1&g#}LKEXgkEy z)Q5X|@3Gw*Q8Rk(YVP}fTZ4%Q_NXLB6djs>I>K8+n}M=l^|#D4IWRE5Ux8Eu$xVk} zEZq}_F;vBpKRa#WS} z5T{|mKbF%dN@Mm1y4^3f7On)IC3;m_3P^DI6WOzLOdEg3=9lHbu}de^nDL~ojt}z z)0dVQ6X@FmZv#~Yj8DJmw$PPFPV(CF7#Q^__&0V~=sK>anz=Uy1_kTi>w&rf%OU#V z6CY(WA48AVKK^!Z95GbiI6As}JA3$88$U*iaJ*1gk~ey5y;nf&Lq67ifb>0ZF|2Ke z(@@qb8^&fay$LdYcdA=UQ%O!PXv|IZXf;Rg4^Bz3avFZw&rT;Rr6Z_m)%%nRk*6Fq z&+#6eK9y%8Apky;yGxUmQ&TI!A;i53+WF#iCgFWHD3K%Kr1M7S_!@R<{wqf|Xn3%2 zcvsf@x7I^1PtP7>mI^X)adCS|GXPPtI6fF0!TdWMy0#em`LP9{c0yA`M8pUH&a@KTw$Z=kw6jlXBpTxmy0jL;t3mW9eW#O*r{y=?r9Vp;MNXh2^n!}3ElR^wf)~ZDGUa)uOsfG2|bd?-xLM%x2`@Zf@9(k89B`mp}3*qYCHRbq32Lq zg4VCbMWfk;ucjn{sGVzUB-ZV4DI;5O(Wh3{ob`6UYM?|lDv$}?6D1bJ?;Igjx{c?G z(HCXte_!yw5$xJy=?FM-)HcD=YEIm?Y?E*lC&VcA{`ITQ(n&#&%x-UW8s$@}S|va&Xo0ilNxjDK(#-xdFEqVENaRKiUf zO92BqIid8oul{r*$fhb$3o{{_!)x<8WJOvouBKNrZWA#}!u+m0)->gS5tvA3uIaDHFOruhF$MO!^X0 z22CtAMb#3I-UQGQzO|2ONc1gMF?JLw8E**#;;hqh>6KPB&d+x+FPK)>KCew%3d?EAL&E!_Kj5&SNG#N?kp)%hvMt%bZM; z2yzPN-q*y%#f7W=@GW)A*SOyQa&W~Lf6#f~;c<1|aV{;$DRJV1_UqLP3SuSmbBm+K3zq{S5_* zLXBA)yBI6XPkp>Tss%(_AFa{9G*X8>rjX|1b=S-fy}JxoL&SsOp?98%6^_rjWNPPg zbTIk9$kl{yL@54%Z%ibWgRH+~< zuYS8x;J+!ka7m-gOpBDVIf1Y3rx<8w9M+M*cJ;-t+pEZAG%#BJ`G{L1JM6Oz%p{!_r>!Qk0dFH1 z5NftYDgu~kBKz;j2+rk zCYVJd8|v}O5!hddgSMbq@xTg4i4w9VkXN9+k|7{+#zyk5puKJX*ywoKEn27|idcIgpYU7xI^7 zY_V?$HB`sT8_u{(F{j7+Vd7kV}v`8yQw3xniiXKiZZbVaaaB$#FwV>0{vB3XIEZSa?6Ob}H?j>wDEUxq$Y zYn_n$kTu_(a!SVH@o`b4lyTco9%iTt6V6AH3Vj=c5Uj}4G2xs^W`rjXtnGoxyOSZY zL@e3`P7>yJv4uA&6|6;X-^kE&NN?uVYU~Ktb>y-my(_HENOdN`CPP|ta?BN2R6;<1 zT}X=TJZmz$N|@Jyh~pvuCNcgU$NHD&uz&d@pG>Pyeh|&B=_TyZtG?8KIn~_mNG><&IzlC7VKZOOy|2b<4@B0wd)N@qr`|<7m}omzKjwth zIGRsxrrs`d3*S(7`mIe!Tr6RPY?ZEm@8PRz@pGNQ0Ky_Owe4TMFLJ4*7D@{%nn=>2 zWjyk*Ke*hxF9{C^m7#Jbv30)lP8l^ZyT6BFK?FUOlu)|AUe#`uj_9D8DsZdPcX&*0z|4+t%8IEYW<)lwWwdZb$@r49mt z$_A;6P^$~5alQ$U{0fce z@x=OOxH6WQy?N+1eu6sTHmuzIY(F;q{#)>rDr1n!V++#>TaB1F{zWRw^h}2=#4@8X zU`n_*qT^48iI81MU#>`i&ko2z>9hZy%>p_9s={7Ex#05r{%n9|4>95Tkc~YcD^B;X zwDxKpR9TjCO!Q^13!4_|yR)atx1W|s8`zxgQPR-LSI7epBFzD16NYMrPjCO^y3@zmErH#<2H>DEHF(;ZcZdjsA1@xW=}fM=)3yj?RHuS76~ z45duI8YUw@gl%EW>&e8pR?q0YBhTsemfN(epe}R+!kep&>G-*YDaL>d;XI}uT&N8c zxfDKoP5ALnH-za`enzT>1o>S+k<`?}ghx|`UpI?J3ug@1tE=mEWNOh6C63+@4kA7w zYStt=F0#>~(Zr%lF1Nn@m()TyL%K<6p^+0>)b7>F{vWhTpa zo0+KRynGMsCg7penz*GVacs41Fc%pW_%z!g1M4PH2 zaXq@`E6|_6%qV>Z9V+chRNNLDF6O?H=+vEIMzn>gvqf()*TD(MoO)nz0;H)Okecnc z?f)l#%HT3q(f@^ps7i`x?DCvHY*O#{`_k|0@+rH$=u+f0-5@@$Y-;g=4FKN`d z3Ydg&cS5UhdeW=Zr#s4X^)Z%RUn*$~Fm0jm=3*1si^R?RzNqlpmsc86~LeEL~&Wc??= zK@mgXpzGM`sR^>ER~Pzmw)e*o=(^HznA22JDh zW3mQ;7;F|Nz4fcWqt@1vT$Vb;v@M=i%M$K}_or1!*yI+gZ$C={2Ju(s$C&M?Zu0i(^Ww81%i zw#c<%YY0!GGp&gyXJ;lWLtg@}^BbQNR!=LC7ERMexefw-yyd1CF}@06w-U-~z@z1D z5|OE2!PcZDeJ!Dt0Xh^bdOm%%p`7jyR@KPUnQ+`A9h#3$iVl$Ry8VFt?$gh5_^OXa z&OYgmDCGtor<-P;R34b3+4*GV>`#r|9UKnI*D?RGeYe?QRitR)(!L7fD}`RXo50>v zNEezZa<`C%1+heYh=x5Q2H-u1zyQ({orPLLrFwMy$R>&ngmJ^bvy*RvTZAyuyuZq} z11mb7cUAVQ8>^UCkTTA!rBgIkWS19BR!RVPDK!9lN=53L!I*}edpONcb1$TsnHyr5gQ#JHawl&|+ozlh8B_k5L{C?E8Q*=H zQ#9|jkZJfuTcS&w44+@Y67HQWpL5tnjwAa8#izW1vV0Vc4E=Nz3V^BdA&%mRp%##D zq=`&@`1r>Kn!3(5x9*0<0GA>YH=B##X&z#iL5eD_K`3ybaRusLU2E~|s)ZMRpYl^E z!NjC`hNfuJ3p4qtf^Kc#eDiLn{AJgD+95W*=y_HB7;K?y;f*O$+Dx4VbrFBdgi zbRBw{4+scG(u>h)CS;lcqT`7CW<7a$DZcGIM%TO;CEdlr6k$<$d3jM^m(&LM7wxHp z{A|9FgW+#&9#hDK+=v^Sni@JfveL`E%O;`|ms3_&F4Ho)FwP=y=-sd8Tl%|@@+2l= zkn~GLZ)swoH$-F}LT=adJT}pBZr^bbi>&5^WeYAptBJL)_7hwT= zUGgoD*_X-$Ez>D%S3HfsN0-nK3j~vkV^Hos#t+m2MB8=!?Unfdn=o@B`fCjZ307qE z(@ff52oS6={M7;V|48iAEp7s^l7`m)48csy0_A~={j*k6xJC}ahEg)hGXriWOa&2*USJgaFP}v zgoe30yZ%~Or4Mn%9?8!ud!B7KI2pX}^}pfJ|9!aXnD?}shsqWbt-c{%Xu<1OR7?>> z_rui3L3-$ZD4~bhhn3f5(oh>TEA={iA8liP5Rg5Px-97L7}F*;NVVxu$C1r`P{kQ@ z45I%}#5fQ57cuNg!sx}!rfoM7uh%UGclMsH|9QVk&~ItOFC%7ZWT=?;x3dP;Ln5)uMTpj8vj&UG;WJ-2p$< zTUWawq8|FaC2ZFkYJKMe0&I(97im{VO5K&Ujx`Ct`=CnZ{s&3>G}~Iyjt?3KM{ois z-Ey1i0T#M$D_Z^e%z59)fSV`<{Rm(e_IjnYI1Qeu-nK31?tPkhhNxx#+DEM#Clc-5 z^m(Y>IlqlZv<)k=&5jiIbjZ`nY{AbtfEKAh7BcXmwPR10I#Y3n3$^mZ{(f|Y(sk0S zI~i_?tUB?0voTl(d4)Rt>+83K7fDmt62$EgoFHWpk(Ea__g|e|esiHdG<#8M(}Hz4 zkJ@XL|uge5k7%0g}+G}gEdEPj89c}=KO z{=oZelfBZ*8oynFv*3dY=&)$CUoML)HLYsQyAfZtHDG=}%CPbDo%ZaDeuboqNxlX3 zy)VzUu5)us$9h}}dxrsqLcmH7+kTEJLZBkSD%Lu!1|ZlbQF}wzbmY&fPp-*gmgwZ& zj~9Nkn;L+3v{j`ibiobPH69wYHDy?Yt>)A9Z|$=}+tdN~zsmbDdg8=6VwxUFRKmvV zg@*IN9rRQ`ao-r&G~dKJw)GBge~pEJs>^(J2g{yHXz@jWDkSa@|~v$PX1 zAGSlQno>`{z3Fv$o8b5tbJ~(B17`7YTSBWvQew87JF|b*twcKj=ib)k6%Zy^1h&J` zm^A9ve_X7-pnzk_AD=hFdG!7-!0hxg8|}H7%_3%?plad^1*LCUqS>+a|4N&+77#jQ zcf|gKM6syGXMUoIc2`VjG`azhC_(ra8$R0+ASuy)&kPMhXzY6VKOve*%75e37&GFy znvc3San980EEfJ>_+qD-K(3Q7EUDEUkJG*e?6fiw9(7RgnD)?Y)N=%>X{`%=FT)so38A1zn;4CM8U; zqjf&?X2TP5;21Y1y6_z>k-roVukE~h`8NdvQBU6t!(k9`>=H-}YGDGse$9r)@VUrp z#7htZvtil!N3hTe-y9#T-m~*!8NZCO>!E6vd!|WdBMg=Vu&@YTWDnK4vExz9sN|{* zWDrOj0U>CjG8+nIf^&28^03UZ;%r_?lxQU#H?-^{c@b4z%iA|c3kks89%Y{++uK`+ z)@($BQcj7RelL%^4>}c=)D^NirHW}bZjIkh;aC%2T}Y|*)~6coEL!l=H-4Y?KEJX! zXCAAc$}#DM6L5}o8$si0jtWR-l>Oc4#)#pV*r1Z*4cg(GW8?kQlAUro_V9HeJBMqA z#6;6R0){AQja2i$|l{p zb?4=HxEU#Kqzl7mcyNjuG>U*kk(`aFLYI=I&8 zW7Fxk<+3^~sbgh0%ccqD1U)5QK-RhkW@!DHVA4yh3$4)046CjI9Zvafk3}uen z$D|*NMpc{9h)&qk0Z(?FBAkCu_H@LnBr{p6)o^g3(?WFkVJU1?*tder(P(^U>j1)x z)2KeLeLWa3^9;}ka?`vvnP4BMRc&PRuIA``8OSVA5IsC6zczGb;$Qgj__W%&#ViC{ zy0Ie}FmoEP=T!0P)ZiX>51+RHl4ml~rdYAn=qwG7C~Q-o!w#N{=Hfb9n_>cBzsW(F zYE-He+RUe~2K-3fcz(+y7}DG#m$@-SQWR4wTiGbEZn0b29OXg~KpuyJUv^XO5l#As znli!R@+ngfVUEc8GWwYDf-?(o9q5leveO>oI6hF{KJ)Skcny}D$WF6m7y$>-@{EsF z*7Q8Ft}@z~v)1I@K&|L|hszjj%wSxX?w8W`G{Hq(Fuk6vtcENBLDSj?`s$MU*CX`8 zr)AW_#`!n&Mks}stnHrJi>^c0{K&&qDEt%N&iDwef>L8yfxN{1<};VtQs0!{#Y-vs z#ko3-<6<=v0UwSxWVO}Bwu)#IfL!ac=30~C;{^f2OqW1_QDpi(3yii%XW-2D0zh#7 zH3k~H$#@XwlXNn8J)>ZuY|Za_{l{Fn){e2)qx{W6M>#TJoFDV0z^fYXd0;dvNq+u{8;43jM~Py zn|t+$E8wdELoHbB^&ehDKN)H4bZbPs^@jns@?%?(NVR){0E)%WT(BnV>kh*2Cr>zD zT=XDZcFLu4A(tzsYreQWGVORP0Oy?*p`Mo|qB}Ju`K!jO^00Dzw;nhl6Jf~*Q|QH; z(D(D1&V11F(LG^?8NI&2miGQ8pD05heW(|cns(5>Eg>jgZ93Q};x+NBV4H!J9pZu% zXNSuJt4>~tvSH}&NbS|Mu2EYivK;(SOJ16?~GWT-%>C`?R zA_!ruw~hYXEJ-lHrpUP4VEPxk+73trq1rr=z9~`QQZhVx^W_-;5p9h0%Y%zzmuRuq zliZ?JV-6{w&=8?D{qy);lRgqK{^vm?*kl~O!;=T*M~#?8iUIx zn~Q1CdY!!0B5aJ!BZT=p3(q|()wYQ{g-`o3j>ReZf@#)sCy14`L{h$J1JKdzh*N>Q zq0QJ8@EDx3#R9(lTs4Op-SnXe3FTX3ta@^5um{;M{$P4~x2P{%wyORKSBdb;X&CKP zd1mm~hV$LEuTcZTt=)=fG93J4C`IS-0_=cLr#+- zuW(K+Ts1k_G1;9yU4)0l{wAub9E;>MN3Ud&C)*WPt7PJVHQI_YZ&oK-g00lJRa2B{ zH3!6OpI)(oJO?M9f?@cIHq)_cGva}>3@zGWrG4~7swuqxC~BXVkrP?QuA559+_7h) z7tn%`nNzZHFmP<&q;wq^b7uY(NcgFYG_fOKAV$#6H!a>cUjv^`B#rk9zM&IT=^l`l z?J-qu%wht)9rQNgSqWZv>)}`4F)KC-pS73di8Vn|)xo_~JhH~UK(wVw)nF_hQ2xja z6ze7;?9abm96(aLtYTq?4zKi?p8y}+Kc1%ngX3t@G`N@gh8}gHA9wQtbL7kbY%X>1 zk?-WdOJHImISW`z>GUst>fJGy~*9BJ4pp@Zrp?3TX!Oj8pmuBkR!33PJrxP5!)~>OPOEf~Mh-KfH zpN~%_K$8lxOVdpg;SI{vr8WBNH&vSc-@T$-tKf)%SSVKS_loFfZ1gD@lJ=wVFT%@b zeOrB;#MyWSak_e74#NyyH1G~Z=_LT@g- zs;aBeNrV^!!6V#$634g~%2PD1W)$PnixhMbu1>%6KPD$9A3~Ku3E>K|*owC9#;T4}8J1K|_?sh*9_n1zN653Mr%6LBJ`_4I46y=%> zRsMh9L2-jqzD`ht-07C4Enf#4h9MgX>^(lq>6wHwn zj9^-gKQ@(hc3p9KUnby=yEsojp3c9c&`A78rEg-6s;m~15<+#jNA)~L7rkCzj<_f83ZXN()4;PtpDn~tSJqMbq+lEVABHA*8UO$Q literal 0 HcmV?d00001 diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/adapt-legacy-pullwss.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/adapt-legacy-pullwss.md new file mode 100644 index 000000000000..70a7d50e6ec8 --- /dev/null +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/adapt-legacy-pullwss.md @@ -0,0 +1,98 @@ +--- +id: adapt-legacy-pullwss +title: Adapting legacy pullwss poller setups +description: How to adapt legacy pullwss connections to the new pollers in containers configuration +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +## When to use this procedure + +This page describes what to do if the following conditions are met: + +* You have upgraded an existing platform to version 26.10. +* This platform used some pollers in pullwss mode. +* You now wish to use pollers in containers. (If you do not wish to use pollers in containers, your old pollers in pullwss mode will work just fine, there is nothing to do.) + +Depending on your setup, you can [configure your old pollers to use port 443 (recommended)](#configure-your-old-pollers-to-use-port-443-recommended), or [redirect traffic to Gorgone (not recommended)](#redirect-traffic-to-gorgone-not-recommended). + +## Configure your old pollers to use port 443 (recommended) + +1. Enable the central server to receive pullwss traffic from your pollers in containers, as described in [Pollers in containers prerequisites](./pollers-containers-prerequisites.md). +2. Update all your pollers to version 26.10. +3. On the poller, edit the **pullwss** module configuration in **/etc/centreon-gorgone/config.d/40-gorgoned.yaml**: set the port to 443 and add the `central_uri` key, so that the poller reaches Gorgone through Apache (adapt `/centreon` in `central_uri` if your central server uses another base URI). + + ```yaml + gorgone: + modules: + - name: pullwss + package: "gorgone::modules::core::pullwss::hooks" + enable: true + ssl: true + port: 443 + token: "secret_token" + address: + central_uri: "/centreon/gorgone/pullwss/websocket" + ``` + +## Redirect traffic to Gorgone (not recommended) + +This section should be used only if you have many pollers whose configuration cannot be reconfigured easily as described above. In that case, edit the Apache configuration on your central server to keep the legacy pullwss port 8086 and redirect the traffic to Gorgone. + +### Poller with HTTPS + +1. Enable the central server to receive pullwss traffic from your pollers in containers, as described in [Pollers in containers prerequisites](./pollers-containers-prerequisites.md). +2. Update your pollers to version 26.10. +3. On the central server, execute the following commands to redirect the traffic from port 8086 to the central server's Gorgone. + + + + + ```shell + cp /usr/share/centreon/examples/centreon-apache-https-gorgone.conf /etc/httpd/conf.d/ + systemctl restart httpd + ``` + + + + + ```shell + cp /usr/share/centreon/examples/centreon-apache-https-gorgone.conf /etc/apache2/sites-available/ + a2ensite centreon-apache-https-gorgone + systemctl restart apache2 + ``` + + + + +### Poller without HTTPS (plain HTTP, not recommended) + +> This configuration is only for compatibility with old pollers that cannot be configured to use TLS. Please note that using pullwss without TLS is not recommended in production. Update your configuration as soon as possible. + +1. Enable the central server to receive pullwss traffic from your pollers in containers, as described in [Pollers in containers prerequisites](./pollers-containers-prerequisites.md). +2. Update your pollers to version 26.10. +3. On the central server, execute the following commands to redirect the traffic from port 8086 to the central server's Gorgone. + + + + + ```shell + cp /usr/share/centreon/examples/centreon-apache-gorgone.conf /etc/httpd/conf.d/ + systemctl restart httpd + ``` + + + + + ```shell + cp /usr/share/centreon/examples/centreon-apache-gorgone.conf /etc/apache2/sites-available/ + a2ensite centreon-apache-gorgone + systemctl restart apache2 + ``` + + + + +## Troubleshooting your setup + +See [Troubleshooting the installation](./pollers-containers-prerequisites.md#troubleshooting-the-installation). diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md new file mode 100644 index 000000000000..e3c637db53ec --- /dev/null +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md @@ -0,0 +1,224 @@ +--- +id: pollers-containers-prerequisites +title: Pollers in containers prerequisites +description: "Configuring Centreon to receive connections from pollers in containers" +--- +import Tabs from '@theme/Tabs'; +import TabItem from '@theme/TabItem'; + +This page explains how to configure your platform to be able to use pollers in containers. You only have to perform this procedure once for the whole platform, before you install your first poller in a container. It has no impact on other poller deployment modes. + +## When to use this procedure + +This page describes what to do if the following conditions are met: + +* You have just installed a platform in version 26.10, or upgraded a platform that did not have any pollers in pullwss mode. +* You want to use pollers in containers for the first time. + +> If your platform had pollers in pullwss mode and you now wish to use pollers in containers, follow [Adapting legacy pullwss poller setups](./adapt-legacy-pullwss.md). + +### Pullwss mode + +By default, the central server initiates the connection to its pollers. However, a poller running in a container cannot accept incoming connections, so this mode does not work. + +**pullwss** mode reverses the direction: the poller opens a WebSocket connection to the central server and keeps it open. + +The recomended and secure way is to use HTTPS. This means that certificates are needed to secure the connection. To simplify certificate lifecycle management, Apache (which already hosts the Centreon web interface) is used as a reverse proxy to terminate the TLS connection and forward the traffic to the central server's Gorgone. + +## Installation requirements + +* Make sure your container meets the [poller installation prerequisites](../prerequisites.md#poller-sizing). + +* Ensure the central server and Gorgone are already installed and up to date with the latest major version. + +* If not already done, configure HTTPS on your central server. This can be done as part of the [installation procedure](../installation-of-a-central-server/using-packages.md#step-3-set-up-the-tls-configuration), or [separately](../../administration/secure-platform.md#activating-https-mode-on-your-web-server). + + Once HTTPS is enabled, also update the Gorgone API URL: in **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** on the central server, set `base_url` to `https:///centreon/api/latest/`, then restart Gorgone (`systemctl restart gorgoned`). Otherwise, the central server rejects every poller in a container with an `invalid token` error. + +* The poller must be able to reach the central server. + +## Step 1: Configure Gorgone on the central server + +In previous versions of Centreon, Gorgone could listen for pullwss connections directly on the network if manually configured to do so. Starting with version 26.10, the recommended method is to use Apache as a reverse proxy for Gorgone. + +1. On the central server, update the file **/etc/centreon-gorgone/config.d/40-gorgoned.yaml** as follows. The `nodes` module should already be present, and does not need modification in a default installation. The `proxy` module is already present too, but not the `httpserver` sub-key, which you should add. + + ```yaml + gorgone: + modules: + + - name: proxy + package: "gorgone::modules::core::proxy::hooks" + enable: true + httpserver: + enable: true + ssl: false + address: "localhost" + port: 8087 + + ``` + + > Please note this is a yaml file, so indentation is important. Use 2 spaces for each indentation level. + + Explanation of the configuration: + + * `ssl: false` and `address: "localhost"`: Gorgone only accepts connections from the local machine, in plain HTTP. Apache is the one terminating TLS for the pollers and forwarding the traffic locally, so Gorgone itself does not need a certificate. + * `port: 8087`: internal port used only for the connection between Apache and Gorgone on the same host. It should not be exposed to the network. + +2. Restart Gorgone after this change: + + ```shell + systemctl restart gorgoned + ``` + +3. Check that Gorgone is listening on port 8087 correctly: + + ```shell + sudo ss -tnlp | grep 8087 + ``` + + The command should return one line similar to this: + + ```text + LISTEN 0 4096 [::1]:8087 [::]:* users:(("gorgone-proxy-h",pid=2305,fd=28)) + ``` + +## Step 2: Configure Apache as a reverse proxy + +This step is also done on the central server. + +### Apache modules prerequisites + +Make sure the `proxy_wstunnel` Apache module is enabled: + + + + + +Unlike .deb packages, the Alma Linux 9 **httpd** package already has the **proxy_wstunnel** module enabled by default, so there is nothing to do. + + + + + +```shell +a2enmod proxy proxy_wstunnel +systemctl restart apache2 +``` + + + + +### Apache reverse proxy configuration + +1. Edit your Apache configuration file. This is located here: + + + + + ```shell + /etc/httpd/conf.d/10-centreon.conf + ``` + + + + + + ```shell + /etc/apache2/sites-availables/centreon.conf + ``` + + + + +2. Add the correct contents to the Apache virtual host: + + * Centreon offers an example configuration file to enable HTTPS and serve Gorgone as a reverse proxy, available at: `/usr/share/centreon/examples/centreon-apache-https.conf`. You can copy and paste the contents. + * However, if you have a custom configuration and cannot just copy and paste the example file, this is the required configuration to add inside your Apache virtual host: + + ```apache + + ProxyPass "/${base_uri}/gorgone/pullwss/websocket" "ws://localhost:8087/" + ProxyPassReverse "/${base_uri}/gorgone/pullwss/websocket" "ws://localhost:8087/" + + ``` + +3. Restart Apache + + + + + ```shell + systemctl restart httpd + ``` + + + + + + ```shell + systemctl restart apache2 + ``` + + + + +## Add the poller to the platform's configuration + +You can now add a poller in a container. To do so, [retrieve the correct command from the Centreon web interface](./using-containers.md). +The poller will automatically connect to the central server using pullwss. + +## If you delete all your pollers in containers + +If in the future you should delete all your pollers in containers, do not forget to undo the steps above. + +## Troubleshooting the installation + +If your installation does not work, there are multiple things you can check: + +### Can the poller reach the central server? + +The poller must reach the central server on the web port (443 for an `https://` address, 80 for an `http://` address, or the port given in the address) and on TCP port 5669 (Centreon Broker). You can check from the poller with the following commands: + +```shell +nc -zv 443 +nc -zv 5669 +``` + +### Is Gorgone correctly listening on port 8087? + +```bash +curl --header "Connection: Upgrade" --header "Upgrade: websocket" http://localhost:8087/ +``` + +The expected output is: + +```text +HTTP/1.1 101 Switching Protocols +Connection: Upgrade +Sec-WebSocket-Accept: Kfh9QIsMVZcl6xEPYxPHzW8SZ8w= +Server: Mojolicious (Perl) +Upgrade: websocket +``` + +### Does Apache2 redirect the traffic to Gorgone correctly? + +```bash +curl -v --header "Connection: Upgrade" --header "Upgrade: websocket" https://localhost:443/centreon/gorgone/pullwss/websocket +``` + +The expected output is: + +```text +< HTTP/1.1 101 Switching Protocols +< Connection: Upgrade +< Sec-WebSocket-Accept: Kfh9QIsMVZcl6xEPYxPHzW8SZ8w= +< Server: Mojolicious (Perl) +< Upgrade: websocket +``` + +If you see an HTML page indicating `You need to enable JavaScript to run this app`, the Apache reverse proxy is not configured correctly, and the traffic is redirected to the Centreon web interface instead of to Gorgone. Check your Apache configuration and restart Apache after any change. + +### Is the poller rejected with an `invalid token` error? + +If the Gorgone logs of the poller (`docker compose logs gorgone`) show `{"code":500,"message":"invalid token"}`, check that the token is a valid poller-type token. If your web server redirects HTTP to HTTPS, also check that `base_url` in **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** on the central server uses `https://`, then restart Gorgone. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers-advanced-configuration.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers-advanced-configuration.md new file mode 100644 index 000000000000..7490dfcf12de --- /dev/null +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers-advanced-configuration.md @@ -0,0 +1,210 @@ +--- +id: using-containers-advanced-configuration +title: Advanced container configuration +description: "Optional configuration for a container-based poller: VMware monitoring, custom plugins, CMA support, and email notifications" +--- + +This page covers optional configuration for a poller [deployed in a +container](./using-containers.md), +beyond the default `centengine` and `gorgone` services. + +## Allow the poller to send email notifications + +This section applies if you want your poller to be able to send notifications. + +A poller in a container has two different ways to send email +notifications, so you can use whichever fits your infrastructure: + +* A [native SMTP command](#option-1-native-smtp-command), using the `mail` command (from `mailutils`) + relayed through `msmtp`. +* The [**centreon-plugin-notification-email** connector](#option-2-centreon-plugin-notification-email-connector). + +### Option 1: Native SMTP command + +This is the most common way of [sending notifications](../../alerts-notifications/notif-configuration.md). + +The native SMTP command needs an SMTP relay to send emails. Configure it with environment variables on the `centengine` service in the docker-compose. + +| Variable | Effect | +|----------|--------| +| `SMTP_HOST` | Address of the SMTP relay. Required for the native SMTP command: notifications are silently not sent while this is empty. | +| `SMTP_PORT` | Port of the SMTP relay (default: `25`). | +| `SMTP_FROM` | `From:` address used in outgoing notification emails. | +| `SMTP_TLS` | Set to `on` to use TLS when connecting to the relay (default: `off`). | + +If you use the native SMTP command, the `docker-compose.yaml` generated by +the install script does not map these variables by default. Add them +directly to the `centengine` service's `environment:` block, or, to keep +them out of the `.env` file the install script regenerates on every run, put +them in a separate file and reference it as an extra `env_file`: + +Add the last 3 lines to your docker-compose file. + +```yaml +services: + centengine: + # ... + env_file: + - .env + - .env.smtp +``` + +Then store your environment variables in a `.env.smtp` file located in the same directory as the docker-compose file. + +```shell +# .env.smtp +SMTP_HOST=smtp.example.com +SMTP_PORT=25 +SMTP_FROM=centreon-engine@example.com +SMTP_TLS=off +``` + +Restart the `centengine` service (`docker compose up -d`) after changing these variables. + +`mailutils` and `msmtp` are pre-installed in the image. At startup, +`centengine` writes an `msmtp` configuration from the `SMTP_*` variables +above, so `/usr/bin/mail` sends through your relay with no further setup. + +### Option 2: centreon-plugin-notification-email connector + +The connector's SMTP relay settings are plain command-line options, so you can set them directly in the command. + +The connector is pre-installed under `$CENTREONPLUGINS$` (usually +`/usr/lib/centreon/plugins/`), as `centreon_notification_email.pl`. Its +`--smtp-address`, `--smtp-port` and `--from-address` options take your relay +directly, no environment variable needed. + +The connector picks between its host and service notification templates +based on whether `--service-description` is set, so the **same command_line** +can be used as both the host and the service notification command. Replace +the SMTP, Centreon URL, and token placeholders below with your own, then +define it on the **Configuration > Commands** page: + +```shell +$CENTREONPLUGINS$centreon_notification_email.pl --plugin=notification::email::plugin --mode=alert --to-address='$CONTACTEMAIL$' --host-address='$HOSTADDRESS$' --host-name='$HOSTNAME$' --host-alias='$HOSTALIAS$' --host-state='$HOSTSTATE$' --host-output='$HOSTOUTPUT$' --host-attempts='$HOSTATTEMPT$' --max-host-attempts='$MAXHOSTATTEMPTS$' --host-duration='$HOSTDURATION$' --date='$SHORTDATETIME$' --type='$NOTIFICATIONTYPE$' --service-description='$SERVICEDESC$' --service-displayname='$SERVICEDISPLAYNAME$' --service-state='$SERVICESTATE$' --service-output='$SERVICEOUTPUT$' --service-longoutput='$LONGSERVICEOUTPUT$' --service-attempts='$SERVICEATTEMPT$' --max-service-attempts='$MAXSERVICEATTEMPTS$' --service-duration='$SERVICEDURATION$' --host-id='$HOSTID$' --service-id='$SERVICEID$' --notif-author='$NOTIFICATIONAUTHOR$' --notif-comment='$NOTIFICATIONCOMMENT$' --centreon-url='https://central.example.com' --smtp-address='smtp.example.com' --smtp-port='25' --from-address='centreon-engine@example.com' --centreon-user='admin' --centreon-token='your-autologin-key' --smtp-nossl +``` + +* `--centreon-url`, `--centreon-user` and `--centreon-token` (a Centreon + autologin key, **Administration > Accounts > your user > Security**) make + the email link back to the resource and embed its performance graph. Omit + all three if you don't need that - the email is still sent. +* `--insecure` skips TLS certificate verification when fetching that graph, + useful when `--centreon-url` uses a self-signed certificate. +* Add `--smtp-user`/`--smtp-password` if your relay requires authentication, + and drop `--smtp-nossl` to use TLS. + +> Storing `--centreon-token` in a command definition puts it in plain text +> in Centreon Engine's configuration. Use a token scoped to a dedicated, +> low-privilege account rather than an administrator's. + +These options can also use the `$SMTPADDRESS$`, `$SMTPPORT$` and `$SMTPFROMADDRESS$` +poller resource macros. In a container, these macros are overwritten at each +container start with the values of the `SMTP_HOST`, `SMTP_PORT` and `SMTP_FROM` +variables (see Option 1): set these variables rather than defining the macros in +the Centreon interface. + +## Allow the poller to use custom plugins for monitoring + +This section only applies if you want to use your own custom plugins for monitoring. No action is needed to use the official Centreon monitoring connectors. + +The `centengine` container can install custom check scripts and extra APT dependencies without rebuilding the image. + +In the generated `docker-compose.yaml`, add the following volumes to the `centengine` service : + +```yaml + volumes: + # Custom plugin scripts (must be executable) + - ./custom-plugins:/usr/lib/nagios/plugins/custom:ro + # Extra APT packages, installed at startup + - ./custom-deps.json:/etc/centreon-engine/custom-deps.json:ro +``` + +* Create a **custom-plugins** directory and store your custom plugin scripts there. The container will copy them to `/usr/lib/nagios/plugins/custom`. +* If your plugin needs system dependencies, you must declare them in a `custom-deps.json` file. For example: + + ```json + { + "apt": ["snmp", "jq"] + } + ``` + + This file is read when the container starts, and watched for changes + afterward: editing it on the host triggers an automatic install of the + listed packages, with no need to restart the container. Package + installation runs in the background, so `centengine` is not blocked while + it happens. + +### Baking dependencies into a custom image + +If you have a large number of dependencies, you can build a custom image on top of the official one instead of adding the dependencies one by one to the `custom-deps.json` file. Your custom image will be deployed using the docker-compose. + + + +```dockerfile +FROM ghcr.io/centreon/centreon-engine:26.10 + +RUN sudo apt-get update && sudo apt-get install -y --no-install-recommends \ + snmp \ + jq \ + && sudo apt-get clean +``` + +Build it, then reference it as `ENGINE_TAG` (or override the `image:` value +directly) in your `docker-compose.yaml`. The main advantage of this approach +is startup time: when a poller needs many dependencies, installing them once +at build time is faster than installing them every time the container starts +via `custom-deps.json`. + +## Allow the poller to monitor VMware resources + +Follow this procedure before you deploy a poller in a container using the `--with-vmware` option. + +Monitoring VMware infrastructure requires the proprietary VMware Perl SDK: +the daemon cannot start at all without it, even with plain-text credentials. +Because the SDK cannot be redistributed for licensing reasons, the +`centreon-vmware` container image is not published on a registry. The +generated `docker-compose.yaml` references it as +`connector-vmware:${VMWARE_TAG:-local}` with `pull_policy: never`, so you must +build it locally, on the container host, before using `--with-vmware`. + +Download the SDK archives from the Broadcom developer portal (see the +[prerequisites of the VMware ESX monitoring +connector](/pp/integrations/plugin-packs/procedures/virtualization-vmware2-esx#prerequisites) +for instructions), then clone `centreon-plugins`, place the archives in its +`sdks-vmware` directory, and build the image: + +```shell +git clone https://github.com/centreon/centreon-plugins.git +cd centreon-plugins +# Place the downloaded SDK archives in sdks-vmware/ before building +docker build \ + --file .github/docker/connector/Dockerfile.connector-vmware \ + --tag connector-vmware:local \ + . +``` + +> This downloads the latest package from Centreon's stable APT repository and +> includes the SDK by default. Add `--build-arg VERSION=` to pin a +> specific release, or `--build-arg PACKAGE_SOURCE=mount` to build from a +> `.deb` package placed in a `packages-centreon` directory instead. Building +> with `--build-arg WITH_SDK=false` only validates that the image builds: the +> resulting daemon cannot start, since the SDK is required in all cases. + +## Allow the poller to receive data from Centreon Monitoring Agents (CMA) + +Add `--with-cma` to the poller install command so that `centengine` can accept +connections from the Centreon Monitoring Agent over OpenTelemetry gRPC. Using `--with-cma` +adds the following to the `centengine` service in the docker-compose: + +```yaml + volumes: + - ./certs/poller.crt:/etc/pki/poller.crt:ro + - ./certs/poller.key:/etc/pki/poller.key:ro + ports: + - "4317:4317" +``` + +Then generate the corresponding TLS certificates and configure the agent side following +[Configuring certificates](../../cma/cma-certificates.md) and +[Setting up the agent's environment](../../cma/cma-setup.md). diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers.md index 01a7e5998f86..4ad8b7953398 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers.md @@ -1,7 +1,173 @@ --- id: using-containers -title: Installing a poller on a container +title: Installing a poller in a container description: "Install a Centreon poller using docker-compose" --- -L'utilitaire docker-compose doit être disponible sur le système de conteneurisation où vous voulez installer le collecteur. \ No newline at end of file +> The container-based poller deployment method is currently in **BETA**. + +A ready-to-use installation command for container-based pollers can be retrieved from the central server's interface, tailored to your platform. + +
    +Container contents + +Container-based pollers use Debian 13. + +Instead of a single monolithic container, each poller component runs in its own dedicated container +(Centreon Engine, Gorgone, and optionally SNMP trap handling and VMware +monitoring), orchestrated by a single `docker-compose.yaml` file. + +This deployment method relies on a generated installation command that downloads +and runs an installer script on the target container host. The script generates the +`.env` and `docker-compose.yaml` files for you and starts the stack. + +> See [Users and groups](https://docs.centreon.com/docs/installation/technical/) for the system users +> (`centreon-engine`, `centreon-gorgone`, etc.) used inside these containers. + +
    + +## Prerequisites + +* On the central server, [Gorgone's **pullwss** module must be configured to accept connections](./pollers-containers-prerequisites.md). This only needs to be done once, before you install your first poller in a container. +* A Linux host with **Docker Engine** and the **Docker Compose v2** plugin + installed (`docker compose version` must succeed). +* You must have created a poller-type authentication token. +* Outbound network access from this host to your Centreon central server: web port (443 for HTTPS, 80 for HTTP) and TCP port 5669 (Centreon Broker). +* If you plan to receive SNMP traps on this poller, UDP port 162 must be + reachable on this host. +* If you plan to monitor VMware infrastructure from this poller, the + `centreon-vmware` Docker image must be built beforehand (see + [Centreon-vmware container](./using-containers-advanced-configuration.md#allow-the-poller-to-monitor-vmware-resources)). + +## Step 1: Generate the install command + +1. On the central server, click the pollers zone at the top left of the screen and in the popup that opens, click **Create new poller**. + + ![image](../../assets/installation/create-poller-banner.png) + +2. Fill in the poller's information: + + * **Poller name**: a unique name for this poller. It will appear in the list of pollers. + * **Poller address**: the address of the host machine where you are going to install the poller. + > The **Poller address** does not affect connectivity: Gorgone uses + > PullWSS, so the poller always initiates the connection to the central + > server, not the other way around. + * **Centreon Central address, as seen by this poller**: the URL this poller uses to reach the central server, e.g. `http(s)://10.10.10.10/centreon`. If your central server is configured in HTTPS, the connection between the central server and the poller will be automatically configured in HTTPS too. + +3. Select **Container** as the poller's environment. + +4. Select the [authentication token](#prerequisites) you have created for this poller. + +5. In the **Generate installation command** section, click the button and wait for the command to be generated. + +6. Copy the command using the button at the top right of the code block. Keep the window open: you will need to use it again later. + +7. Add to the command any [optional flags](#optional-services-to-add-to-the-installation-command) you want (e.g. to allow the poller to receive data from CMA agents, or if you want to monitor VMware resources. In both cases, you will need to follow the corresponding procedures in [Advanced container configuration](./using-containers-advanced-configuration.md)). + +8. If you want to be able to use email notifications or custom plugins, follow the corresponding procedures in +[Advanced container configuration](./using-containers-advanced-configuration.md). + +## Step 2: Run the install command on the container host + +1. Run the copied command as a user who is allowed to use containers on the target +host. + + > If your central server uses HTTPS, the container host must trust its certificate. If you are using a self-signed certificate, use curl's `-k` (`--insecure`) option to allow insecure connections. + +
    + What the script does + + The script: + + 1. Checks that Docker and the Docker Compose v2 plugin are available. + 2. Generates a `.env` file and a `docker-compose.yaml` file in the current + directory. + 3. Starts the stack with `docker compose up -d`, unless `--no-start` was + added to the command (in that case, start it yourself later with + `docker compose up -d`). + + By default, the generated stack always includes two services: + + * **centengine**: Centreon Engine, the monitoring engine. + * **gorgone**: Gorgone, in charge of retrieving the poller's configuration and + communicating with the central server. + + **Generated files reference** + + The `docker-compose.yaml` generated by the install script wires the services + together using named Docker volumes, so you don't need to configure this + yourself: + + | Volume | Shared between | Purpose | + |--------|-----------------|---------| + | `poller-engine` | centengine, gorgone | Centreon Engine configuration (`/etc/centreon-engine`) | + | `poller-broker` | centengine, gorgone | Centreon Broker configuration (`/etc/centreon-broker`) | + | `poller-centcmd` | centengine, gorgone, centreontrapd | Centreon Engine's external command pipe (`/var/lib/centreon-engine/rw`) | + | `poller-snmp-spool` | snmptrapd, centreontrapd | Spool directory where received traps are written and then processed | + | `poller-snmp-traps` | gorgone, centreontrapd | SNMP trap definitions pushed by the central server | + + Each service also has a Docker healthcheck, so `docker compose ps` reports + `healthy` once a service is fully up. + +
    + +2. Check the health status of the `gorgone` container on the container's host: + + ```shell + docker compose ps + ``` + + Once `gorgone` reports `healthy`, the connection to the central server is established. + + If `gorgone` does not become healthy after a few minutes, check its logs +(`docker compose logs gorgone`), then see +[Attach a poller to a central or a remote server](../../monitoring/monitoring-servers/add-a-poller-to-configuration.md) +and [Communications between servers](../../monitoring/monitoring-servers/communications.md) +for more details on how pollers register and communicate with the central +server. + +## Step 3: Export the configuration + +On the central server, go back to the poller creation window and click +**Export configuration**. + +The poller then shows up as running on the **Configuration > Pollers** page: + +![image](../../assets/installation/connected-poller.png) + +## Step 4: Secure your platform + +If your central server is configured in HTTPS, the connection between the central server and the poller will automatically be configured in HTTPS as well. However, remember to carry out the other security measures for your Centreon platform by following our [recommendations](../../administration/secure-platform.md). + +## Optional services to add to the installation command + +The basic generated command looks like this: + +```shell +curl -fsSL /poller/install.sh | bash -s -- \ + --type docker \ + --poller_token : \ + --uid \ + --name '' \ + --central_url \ + --appsecret \ + --salt +``` + +Add the following flags to the install command to include additional features: + +| Flag | Effect | +|------|--------| +| `--with-snmptrap` | Adds the `snmptrapd` and `centreontrapd` services, for passive monitoring via [SNMP traps](../../monitoring/passive-monitoring/enable-snmp-traps.md). | +| `--with-vmware` | [Allow the poller to monitor VMware resources](using-containers-advanced-configuration.md#allow-the-poller-to-monitor-vmware-resources) (adds the `centreon-vmware` service to the docker-compose). | +| `--with-cma` | [Allows the poller to receive data from Centreon Monitoring Agents (CMA)](./using-containers-advanced-configuration.md#allow-the-poller-to-receive-data-from-centreon-monitoring-agents-cma). Mounts TLS certificates and exposes port 4317, for pollers that accept connections from the Centreon Monitoring Agent (CMA) over OpenTelemetry gRPC. | +| `--tz ` | Sets the container timezone (default: `UTC`). | +| `--debug true` | Enables debug logging on the services. | +| `--gorgone-ssl ` | Overrides the SSL setting used for the Gorgone connection to the central server (by default, HTTPS if the central server already uses HTTPS). | +| `--no-start` | Only generates `.env` and `docker-compose.yaml`; does not start the stack. | + +If you already ran the install command without these flags, you can also add +the corresponding service(s) by hand to the generated `docker-compose.yaml` +and `.env` files, then run `docker compose up -d` again. + +> Running the installation command again regenerates `.env` and `docker-compose.yaml` without warning: any manual change (SMTP settings, custom plugins, CMA, etc.) is lost. Back up these files before running the command again. diff --git a/versioned_sidebars/version-26.10-sidebars.json b/versioned_sidebars/version-26.10-sidebars.json index dc092337dcc0..d7970675cce9 100644 --- a/versioned_sidebars/version-26.10-sidebars.json +++ b/versioned_sidebars/version-26.10-sidebars.json @@ -154,12 +154,33 @@ "id": "installation/installation-of-a-poller/unattended-install-poller" }, { - "type": "doc", - "id": "installation/installation-of-a-poller/using-packages" + "type": "category", + "label": "Pollers in containers", + "link": { + "type": "generated-index" + }, + "items": [ + { + "type": "doc", + "id": "installation/installation-of-a-poller/using-containers" + }, + { + "type": "doc", + "id": "installation/installation-of-a-poller/pollers-containers-prerequisites" + }, + { + "type": "doc", + "id": "installation/installation-of-a-poller/using-containers-advanced-configuration" + }, + { + "type": "doc", + "id": "installation/installation-of-a-poller/adapt-legacy-pullwss" + } + ] }, { "type": "doc", - "id": "installation/installation-of-a-poller/using-containers" + "id": "installation/installation-of-a-poller/using-packages" } ] }, @@ -173,7 +194,7 @@ { "type": "doc", "id": "installation/installation-of-a-remote-server/unattended-install-remote" - }, + }, { "type": "doc", "id": "installation/installation-of-a-remote-server/using-packages" @@ -1197,7 +1218,7 @@ { "type": "doc", "id": "upgrade/introduction" - }, + }, { "type": "doc", "id": "upgrade/upgrade-matrix" @@ -1738,10 +1759,10 @@ { "type": "category", "label": "Release notes for Centreon 26.10", - "link": { + "link": { "type": "doc", "id": "releases/introduction" - }, + }, "items": [ { "type": "doc", @@ -1823,4 +1844,4 @@ ] } ] -} +} \ No newline at end of file From 65b8445ad43f2df311424731d98b34cb7e07b88a Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 9 Oct 2026 10:27:17 +0200 Subject: [PATCH 123/179] Changes following review --- .../administration/secure-platform.md | 687 +---------------- .../installation/_database-local-install.mdx | 2 +- .../installation/_database-repository.mdx | 4 +- .../installation/_database-tls-conf.mdx | 3 +- .../installation/_install-common.mdx | 2 +- .../installation/_tls-certificates.mdx | 3 +- .../using-packages.md | 8 +- .../administration/secure-platform.md | 691 +----------------- .../installation/_database-local-install.mdx | 2 +- .../installation/_database-repository.mdx | 4 +- .../installation/_database-tls-conf.mdx | 3 +- .../installation/_install-common.mdx | 2 +- .../installation/_tls-certificates.mdx | 3 +- .../using-packages.md | 8 +- 14 files changed, 26 insertions(+), 1396 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md index 4c766c72153a..34df59968b45 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md @@ -560,692 +560,9 @@ Status for the jail: centreon ## Sécuriser le serveur web en HTTPS -La [procédure d'installation standard à partir des paquets](../installation/installation-of-a-central-server/using-packages.md) vous permet d'installer votre serveur central en mode HTTPS. Si, pour une raison quelconque, vous avez choisi de l'installer en mode HTTP, ou si vous avez mis à niveau un serveur central HTTP et souhaitez maintenant passer en HTTPS, suivez cette procédure. +La [procédure d'installation standard à partir des paquets](../installation/installation-of-a-central-server/using-packages.md) vous permet d'installer votre serveur central en mode HTTPS. Si, pour une raison quelconque, vous avez choisi de l'installer en mode HTTP, ou si vous avez mis à niveau un serveur central HTTP et souhaitez maintenant passer en HTTPS, [suivez cette procédure](../installation/installation-of-a-central-server/using-packages.md#étape-3--mettre-en-place-la-configuration-tls). -Il est fortement recommandé de passer en mode HTTPS. Utilisez un certificat émis par une autorité de confiance. Les certificats auto-signés ne doivent pas être utilisés en production. - -- Si vous disposez déjà d'un certificat validé par une autorité, vous pouvez [activer dès maintenant le mode HTTPS sur votre serveur Apache](#activer-le-mode-https-sur-le-serveur-web). - -- Si vous ne disposez pas d'un certificat validé par une autorité, vous pouvez en générer un sur des plateformes telles que [Let's Encrypt](https://letsencrypt.org/). - -- Si, à des fins de test, vous souhaitez utiliser un certificat auto-signé, [vous pouvez suivre cett procédure pour en créer un](./self-signed-certificate.md) avant d'activer le mode HTTPS sur votre serveur. Si vous utilisez un certificat qui n'est pas fourni par une autorité de confiance, vous devrez importer le certificat de l'autorité de certification (CA) dans votre navigateur. - -### Activer le mode HTTPS sur le serveur web - - - - -1. Installez le module SSL pour Apache : - -```shell -dnf install mod_ssl openssl -``` - -2. Installez les certificats : - -Installez vos certificats (**server.pem** et **server-key.pem** dans l'exemple suivant, et le certificat CA) en les copiant dans la configuration Apache : - -```shell -cp server-key.pem /etc/pki/tls/private/ -cp server.pem /etc/pki/tls/certs/ -cp rootCA.pem /etc/pki/tls/certs/ -``` - - - - -1. Installez le module SSL pour Apache : - -```shell -dnf install mod_ssl openssl -``` - -2. Installez les certificats : - -Installez vos certificats (**server.pem** et **server-key.pem** dans l'exemple suivant, et le certificat CA) en les copiant dans la configuration Apache : - -```shell -cp server-key.pem /etc/pki/tls/private/ -cp server.pem /etc/pki/tls/certs/ -cp rootCA.pem /etc/pki/tls/certs/ -``` - - - - -```shell -a2enmod ssl -systemctl restart apache2 -``` - -2. Installez les certificats : - -Installez vos certificats (**server.pem** et **server-key.pem** dans l'exemple suivant, et le certificat CA) en les copiant dans la configuration Apache : - -```shell -cp server-key.pem /etc/ssl/private/ -cp server.pem /etc/ssl/certs/ -cp rootCA.pem /etc/ssl/certs/ -``` - - - - -3. Sauvegardez la configuration actuelle du serveur Apache pour Centreon : - - - - -```shell -cp /etc/httpd/conf.d/10-centreon.conf{,.origin} -``` - - - - -```shell -cp /etc/httpd/conf.d/10-centreon.conf{,.origin} -``` - - - - -```shell -cp /etc/apache2/sites-available/centreon.conf{,.origin} -``` - - - - -4. Éditer la configuration Apache pour Centreon : - -> Centreon propose un fichier de configuration d'exemple HTTPS disponible dans le répertoire : -> **/usr/share/centreon/examples/centreon.apache.https.conf** - - - - -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. - - - - -Éditez le fichier **/etc/httpd/conf.d/10-centreon.conf** en ajoutant la section **\**. - - - - -Éditez le fichier **/etc/apache2/sites-available/centreon.conf** en ajoutant la section **\**. - - - - -Voici un exemple de ce à quoi le fichier peut ressembler avant d'insérer le bloc : - -```apacheconf -Define base_uri "/centreon" -Define install_dir "/usr/share/centreon" - -ServerTokens Prod - - - RewriteEngine On - RewriteCond %{HTTPS} off - RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - -``` - -Voici un exemple de ce à quoi le fichier peut ressembler une fois le bloc inséré : - - - - -```apacheconf -Define base_uri "/centreon" -Define install_dir "/usr/share/centreon" - -ServerTokens Prod - - - RewriteEngine On - RewriteCond %{HTTPS} off - RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - - - - ##################### - # SSL configuration # - ##################### - SSLEngine On - SSLProtocol All -SSLv3 -SSLv2 -TLSv1 -TLSv1.1 - SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA - SSLHonorCipherOrder On - SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/server.pem - SSLCertificateKeyFile /etc/pki/tls/private/server-key.pem - - Header set X-Frame-Options: "sameorigin" - Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict - Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" - ServerSignature Off - TraceEnable Off - - Alias ${base_uri}/api ${install_dir} - Alias ${base_uri} ${install_dir}/www/ - - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/www/$1" - - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" - - - ProxyTimeout 300 - ErrorDocument 404 ${base_uri}/index.html - Options -Indexes +FollowSymLinks - - - # https://github.com/SpiderLabs/ModSecurity/issues/652 - SecRuleRemoveById 200003 - - - - DirectoryIndex index.php - AllowOverride none - Require all granted - FallbackResource ${base_uri}/index.html - - - - AllowOverride none - Require all granted - - - - RedirectMatch ^/$ ${base_uri} - - -``` - -> N'oubliez pas de changer les directives **SSLCertificateFile** et **SSLCertificateKeyFile** avec les chemins d'accès vers votre propre clé et son certificat. - - - - -```apacheconf -Define base_uri "/centreon" -Define install_dir "/usr/share/centreon" - -ServerTokens Prod - - - RewriteEngine On - RewriteCond %{HTTPS} off - RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - - - - ##################### - # SSL configuration # - ##################### - SSLEngine On - SSLProtocol All -SSLv3 -SSLv2 -TLSv1 -TLSv1.1 - SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA - SSLHonorCipherOrder On - SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/server.pem - SSLCertificateKeyFile /etc/pki/tls/private/server-key.pem - - Header set X-Frame-Options: "sameorigin" - Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict - Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" - ServerSignature Off - TraceEnable Off - - Alias ${base_uri}/api ${install_dir} - Alias ${base_uri} ${install_dir}/www/ - - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/www/$1" - - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" - - - ProxyTimeout 300 - ErrorDocument 404 ${base_uri}/index.html - Options -Indexes +FollowSymLinks - - - # https://github.com/SpiderLabs/ModSecurity/issues/652 - SecRuleRemoveById 200003 - - - - DirectoryIndex index.php - AllowOverride none - Require all granted - FallbackResource ${base_uri}/index.html - - - - AllowOverride none - Require all granted - - - - RedirectMatch ^/$ ${base_uri} - - -``` - -> N'oubliez pas de changer les directives **SSLCertificateFile** et **SSLCertificateKeyFile** avec les chemins d'accès vers votre propre clé et son certificat. - - - - -```apacheconf -Define base_uri "/centreon" -Define install_dir "/usr/share/centreon" - -ServerTokens Prod - - - RewriteEngine On - RewriteCond %{HTTPS} off - RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - - - - ##################### - # SSL configuration # - ##################### - SSLEngine On - SSLProtocol All -SSLv3 -SSLv2 -TLSv1 -TLSv1.1 - SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA - SSLHonorCipherOrder On - SSLCompression Off - SSLCertificateFile /etc/ssl/certs/server.pem - SSLCertificateKeyFile /etc/ssl/private/server-key.pem - - Header set X-Frame-Options: "sameorigin" - Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict - Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" - ServerSignature Off - TraceEnable Off - - Alias ${base_uri}/api ${install_dir} - Alias ${base_uri} ${install_dir}/www/ - - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/www/$1" - - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" - - - ProxyTimeout 300 - ErrorDocument 404 ${base_uri}/index.html - Options -Indexes +FollowSymLinks - - - # https://github.com/SpiderLabs/ModSecurity/issues/652 - SecRuleRemoveById 200003 - - - - DirectoryIndex index.php - AllowOverride none - Require all granted - FallbackResource ${base_uri}/index.html - - - - AllowOverride none - Require all granted - - - - RedirectMatch ^/$ ${base_uri} - - -``` - -> N'oubliez pas de changer les directives **SSLCertificateFile** et **SSLCertificateKeyFile** avec les chemins d'accès vers votre propre clé et son certificat. - - - - -5. Activez les flags HttpOnly / Secure et cacher la signature du serveur Apache : - - - - -Éditez le fichier **/etc/php.d/50-centreon.ini** : - -* Assurez-vous que le paramètre `expose_php` est désactivé : - - ```phpconf - expose_php = Off - ``` - -* Ajoutez le chemin d'accès au certificat CA qui a été utilisé pour signer le certificat du serveur : - - ```text - openssl.cafile=/etc/pki/tls/certs/rootCA.pem - curl.cainfo=/etc/pki/tls/certs/rootCA.pem - ``` - - - - -Éditez le fichier **/etc/php.d/50-centreon.ini** : - -* Assurez-vous que le paramètre `expose_php` est désactivé : - - ```phpconf - expose_php = Off - ``` - -* Ajoutez le chemin d'accès au certificat CA qui a été utilisé pour signer le certificat du serveur : - - ```text - openssl.cafile=/etc/pki/tls/certs/rootCA.pem - curl.cainfo=/etc/pki/tls/certs/rootCA.pem - ``` - - - - -Éditez le fichier **/etc/php/8.4/mods-available/centreon.ini** et ajoutez les lignes suivantes : - -```text -openssl.cafile=/etc/ssl/certs/rootCA.pem -curl.cainfo=/etc/ssl/certs/rootCA.pem -``` - - - - -6. Cachez le répertoire par défaut **/icons** : - - - - -Éditez le fichier **/etc/httpd/conf.d/autoindex.conf** en commentant la ligne suivante : - -```apacheconf -#Alias /icons/ "/usr/share/httpd/icons/" -``` - - - - -Éditez le fichier **/etc/httpd/conf.d/autoindex.conf** en commentant la ligne suivante : - -```apacheconf -#Alias /icons/ "/usr/share/httpd/icons/" -``` - - - - -> Le répertoire est caché par défaut. - - - - -7. Vous pouvez effectuer ce test vérifiant qu'Apache est bien configuré, en exécutant la commande suivante : - - - - -```apacheconf -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```apacheconf -Syntax OK -``` - - - - -```apacheconf -apachectl configtest -``` - -Le résultat attendu est le suivant : - -```apacheconf -Syntax OK -``` - - - - -```apacheconf -apache2ctl configtest -``` - -Le résultat attendu est le suivant : - -```apacheconf -Syntax OK -``` - - - - -8. Redémarrez le serveur web Apache et PHP pour prendre la configuration en compte : - - - - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -```shell -systemctl restart php-fpm httpd -``` - -Puis vérifiez le statut : - -```shell -systemctl status httpd -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● 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 - -``` - - - - -```shell -systemctl restart php8.4-fpm apache2 -``` - -Puis vérifiez le statut : - -```shell -systemctl status apache2 -``` - -Si tout est correct, vous devriez avoir quelque chose comme : - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -Vous pouvez maintenant accéder à votre plateforme via votre navigateur en mode HTTPS. - -> Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez définir l'adresse `centreon.url=https://` dans le fichier **/etc/centreon-map/map-config.properties** pour utiliser HTTPS au lieu de HTTP. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md#configurer-httpstls-sur-le-serveur-map). - -9. Configuration API de Gorgone - -Éditez le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** en remplaçant **127.0.0.1** -par le FQDN de votre serveur central, comme dans l'exemple suivant : - -```text -gorgone: - tpapi: - - name: centreonv2 - base_url: "https://centreon7.localdomain/centreon/api/latest/" - username: "centreon-gorgone" - password: "XXXXX" - - name: clapi - username: "centreon-gorgone" - password: "XXXXX" -``` - -Redémarrez le daemon Gorgone : - -```shell -systemctl restart gorgoned -``` - -Puis vérifiez le statut : - -```shell -systemctl status gorgoned -``` - -Si tout est correct, vous devriez avoir quelque chose comme cet exemple : - -```shell -● gorgoned.service - Centreon Gorgone - Loaded: loaded (/usr/lib/systemd/system/gorgoned.service; enabled; preset: enabled) - Active: active (running) since Thu 2026-10-08 09:27:46 UTC; 4h 10min ago - Invocation: 40225788460245609d05c9db103f1ff3 - Main PID: 807 (perl) - Tasks: 51 (limit: 4618) - Memory: 176.2M (peak: 241.4M) - CPU: 9.461s - CGroup: /system.slice/gorgoned.service - ├─ 807 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=error - ├─1073 gorgone-proxy - ├─1075 gorgone-proxy - ├─1076 gorgone-proxy - ├─1077 gorgone-proxy - ├─1080 gorgone-proxy - ├─1086 gorgone-engine - ├─1089 gorgone-audit - ├─1097 gorgone-legacycmd - ├─1098 gorgone-httpserver - ├─1100 gorgone-nodes - ├─1107 gorgone-statistics - ├─1108 gorgone-cron - ├─1113 gorgone-anomalydetection - ├─1125 gorgone-autodiscovery - ├─1133 gorgone-action - └─1137 gorgone-dbcleaner - -Oct 08 09:27:46 doc-central systemd[1]: Started gorgoned.service - Centreon Gorgone. -``` - -Vous devriez voir la ligne suivante dans les logs de Gorgone **/var/log/centreon-gorgone/gorgoned.log** : - -```text -2026-10-08 15:58:12 - INFO - [autodiscovery] -class- host discovery - sync started -``` +> Il est fortement recommandé de passer en mode HTTPS. Utilisez un certificat émis par une autorité de confiance. Les certificats auto-signés ne doivent pas être utilisés en production. ## URI personnalisée diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx index 6dad8aae2473..b3944dbbde5e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx @@ -79,7 +79,7 @@ dnf install -y centreon-mysql centreon ```shell apt update -apt install -y centreon-mysql +apt install -y centreon-mysql mysql-common apt install -y centreon # Sélectionner "Use Legacy Authentication Method" systemctl daemon-reload diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-repository.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-repository.mdx index 9f55c460d294..df2eb8a929d3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-repository.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-repository.mdx @@ -58,7 +58,7 @@ rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 ```shell -mysql_apt_config="mysql-apt-config_0.8.34-1_all.deb" +mysql_apt_config="mysql-apt-config_0.8.36-1_all.deb" curl -fJLO "https://dev.mysql.com/get/$mysql_apt_config" echo "mysql-apt-config mysql-apt-config/select-server select mysql-8.4-lts" | debconf-set-selections export DEBIAN_FRONTEND="noninteractive" @@ -66,8 +66,6 @@ apt install -y "./$mysql_apt_config" mysql_keyring=$(grep -ohm1 'signed-by=[^] ]*' /etc/apt/sources.list.d/mysql.list 2>/dev/null | cut -d= -f2) [ -z "$mysql_keyring" ] && mysql_keyring=/etc/apt/trusted.gpg.d/mysql.gpg ( set -o pipefail; curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2025 | gpg --dearmor --yes -o "$mysql_keyring" ) -apt update -apt install -y mysql-server mysql-common ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx index f81c4b81ae8c..b60417b4ed99 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx @@ -192,9 +192,10 @@ cat > /etc/mysql/conf.d/centreon-tls-client.cnf <<'EOF' [client] ssl-ca=/etc/mysql/centreon-tls/rootCA.pem ssl-verify-server-cert +EOF ``` -4. Démarrez MySQL. +4. Démarrez MariaDB. ```shell systemctl daemon-reload diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx index a120efafcbb4..2bc76fe2b8cd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_install-common.mdx @@ -141,7 +141,7 @@ SELinux n'est pas installé sur Debian 13, continuez. ### Configurer ou désactiver le pare-feu -Si votre pare-feu est actif, ajoutez les [règles de pare-feu](../administration/secure-platform.md#activer-firewalld). +Si vous avez un pare-feu est si celui-ci est actif, ajoutez les [règles de pare-feu](../administration/secure-platform.md#activer-firewalld). Vous pouvez également le désactiver le temps de l'installation en exécutant les commandes suivantes : ```shell diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx index c8fc67862b8e..384c8e92fec6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx @@ -5,7 +5,7 @@ Utilisez un certificat délivré par une autorité de confiance. Les certificats * Si vous disposez déjà d'un certificat validé par une autorité, passez à l'étape suivante. * Si vous ne disposez pas d'un certificat validé par une autorité, vous pouvez en générer un sur des plateformes telles que [Let's Encrypt](https://letsencrypt.org/). -* Si, à des fins de test, vous souhaitez utiliser un certificat auto-signé, suivez [cette procédure](../administration/self-signed-certificate.md). +- Si, à des fins de test, vous souhaitez utiliser un certificat auto-signé, [vous pouvez suivre cett procédure pour en créer un](./self-signed-certificate.md) avant d'activer le mode HTTPS sur votre serveur. Attention, vous devrez importer le certificat de l'autorité de certification (CA) dans votre navigateur. Supposons que vous disposiez des fichiers suivants dans **/etc/pki/centreon-tls/** : @@ -37,6 +37,7 @@ Supposons que vous disposiez des fichiers suivants dans **/etc/pki/centreon-tls/ ```shell cp /etc/pki/centreon-tls/rootCA.pem /usr/local/share/ca-certificates/centreon-dev.crt + update-ca-certificates ```     diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index 193886bd57c6..427979fe4071 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -178,28 +178,28 @@ Exécutez ensuite la commande suivante (sur le serveur central si vous utilisez ## Étape 5 : Installation web -1. Démarrez le serveur Apache avec la +1. Redémarrez le serveur Apache avec la commande suivante : ```shell -systemctl start httpd +systemctl restart httpd ``` ```shell -systemctl start httpd +systemctl restart httpd ``` ```shell -systemctl start apache2 +systemctl restart apache2 ``` diff --git a/versioned_docs/version-26.10/administration/secure-platform.md b/versioned_docs/version-26.10/administration/secure-platform.md index 8371ea8733c0..56bd62b96c78 100644 --- a/versioned_docs/version-26.10/administration/secure-platform.md +++ b/versioned_docs/version-26.10/administration/secure-platform.md @@ -561,696 +561,9 @@ Status for the jail: centreon ## Secure the web server with HTTPS -The [standard installation procedure from packages](../installation/installation-of-a-central-server/using-packages.md) lets you install your central server in HTTPS mode. If for some reason you chose to install it in HTTP mode, or you upgraded an HTTP central server and now want to switch to HTTPS, follow this procedure. +The [standard installation procedure from packages](../installation/installation-of-a-central-server/using-packages.md) lets you install your central server in HTTPS mode. If for some reason you chose to install it in HTTP mode, or you upgraded an HTTP central server and now want to switch to HTTPS, [follow this procedure](../installation/installation-of-a-central-server/using-packages.md#step-3-set-up-the-tls-configuration). -It is strongly recommended that you switch to HTTPS mode. Use a certificate issued by a trusted authority. Self-signed certificates must not be used in production. - -- If you already have a certificate validated by an authority, you can go directly to this [step](#activating-https-mode-on-your-web-server) to activate HTTPS mode on your Apache server. - -- If you do not have a certificate validated by an authority, you can generate one on platforms such as [Let's Encrypt](https://letsencrypt.org/). - -- If, for test purposes, you want to use a self-signed certificate, follow [this procedure](./self-signed-certificate.md) before activating HTTPS mode on your server. If you use a certificate that is not provided by a trusted authority, you will have to import the CA certificate into your browser. - -### Activating HTTPS mode on your web server - - - - -1. Install the SSL module for Apache: - -```shell -dnf install mod_ssl openssl -``` - -2. Install your certificates: - -Install your certificates (**server.pem** and **server-key.pem** in this example, and the CA certificate) by copying them to the Apache configuration: - -```shell -cp server-key.pem /etc/pki/tls/private/ -cp server.pem /etc/pki/tls/certs/ -cp rootCA.pem /etc/pki/tls/certs/ -``` - - - - -1. Install the SSL module for Apache: - -```shell -dnf install mod_ssl openssl -``` - -2. Install your certificates: - -Install your certificates (**server.pem** and **server-key.pem** in this example, and the CA certificate) by copying them to the Apache configuration: - -```shell -cp server-key.pem /etc/pki/tls/private/ -cp server.pem /etc/pki/tls/certs/ -cp rootCA.pem /etc/pki/tls/certs/ -``` - - - - -1. Install the SSL module for Apache: - -```shell -a2enmod ssl -systemctl restart apache2 -``` - -2. Install your certificates: - -Install your certificates (**server.pem** and **server-key.pem** in this example, and the CA certificate) by copying them to the Apache configuration: - -```shell -cp server-key.pem /etc/ssl/private/ -cp server.pem /etc/ssl/certs/ -cp rootCA.pem /etc/ssl/certs/ -``` - - - - -3. Back up the previous Apache configuration for Centreon: - - - - -```shell -cp /etc/httpd/conf.d/10-centreon.conf{,.origin} -``` - - - - -```shell -cp /etc/httpd/conf.d/10-centreon.conf{,.origin} -``` - - - - -```shell -cp /etc/apache2/sites-available/centreon.conf{,.origin} -``` - - - - -4. Edit the Centreon Apache configuration: - -> Centreon offers an example of a configuration file to enable HTTPS, available in the following directory: -> **/usr/share/centreon/examples/centreon.apache.https.conf** - - - - -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. - - - - -Edit the **/etc/httpd/conf.d/10-centreon.conf** file by adding the **\** section. - - - - -Edit the **/etc/apache2/sites-available/centreon.conf** file by adding the **\** section. - - - - -This is how the file looks before adding the lines: - -```apacheconf -Define base_uri "/centreon" -Define install_dir "/usr/share/centreon" - -ServerTokens Prod - - - RewriteEngine On - RewriteCond %{HTTPS} off - RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - -``` - -This is how the file should look after adding them: - - - - -```apacheconf -Define base_uri "/centreon" -Define install_dir "/usr/share/centreon" - -ServerTokens Prod - - - RewriteEngine On - RewriteCond %{HTTPS} off - RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - - - - ##################### - # SSL configuration # - ##################### - SSLEngine On - SSLProtocol All -SSLv3 -SSLv2 -TLSv1 -TLSv1.1 - SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA - SSLHonorCipherOrder On - SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/server.pem - SSLCertificateKeyFile /etc/pki/tls/private/server-key.pem - - Header set X-Frame-Options: "sameorigin" - Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict - Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" - ServerSignature Off - TraceEnable Off - - Alias ${base_uri}/api ${install_dir} - Alias ${base_uri} ${install_dir}/www/ - - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/www/$1" - - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" - - - ProxyTimeout 300 - ErrorDocument 404 ${base_uri}/index.html - Options -Indexes +FollowSymLinks - - - # https://github.com/SpiderLabs/ModSecurity/issues/652 - SecRuleRemoveById 200003 - - - - DirectoryIndex index.php - AllowOverride none - Require all granted - FallbackResource ${base_uri}/index.html - - - - AllowOverride none - Require all granted - - - - RedirectMatch ^/$ ${base_uri} - - -``` - -> Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your -> own certificate and key. - - - - -```apacheconf -Define base_uri "/centreon" -Define install_dir "/usr/share/centreon" - -ServerTokens Prod - - - RewriteEngine On - RewriteCond %{HTTPS} off - RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - - - - ##################### - # SSL configuration # - ##################### - SSLEngine On - SSLProtocol All -SSLv3 -SSLv2 -TLSv1 -TLSv1.1 - SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA - SSLHonorCipherOrder On - SSLCompression Off - SSLCertificateFile /etc/pki/tls/certs/server.pem - SSLCertificateKeyFile /etc/pki/tls/private/server-key.pem - - Header set X-Frame-Options: "sameorigin" - Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict - Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" - ServerSignature Off - TraceEnable Off - - Alias ${base_uri}/api ${install_dir} - Alias ${base_uri} ${install_dir}/www/ - - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/www/$1" - - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" - - - ProxyTimeout 300 - ErrorDocument 404 ${base_uri}/index.html - Options -Indexes +FollowSymLinks - - - # https://github.com/SpiderLabs/ModSecurity/issues/652 - SecRuleRemoveById 200003 - - - - DirectoryIndex index.php - AllowOverride none - Require all granted - FallbackResource ${base_uri}/index.html - - - - AllowOverride none - Require all granted - - - - RedirectMatch ^/$ ${base_uri} - - -``` - -> Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your -> own certificate and key. - - - - -```apacheconf -Define base_uri "/centreon" -Define install_dir "/usr/share/centreon" - -ServerTokens Prod - - - RewriteEngine On - RewriteCond %{HTTPS} off - RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI} - - - - ##################### - # SSL configuration # - ##################### - SSLEngine On - SSLProtocol All -SSLv3 -SSLv2 -TLSv1 -TLSv1.1 - SSLCipherSuite ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-DSS-AES256-GCM-SHA384:DHE-DSS-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-GCM-SHA256:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!DSS:!RC4:!SEED:!ADH:!IDEA - SSLHonorCipherOrder On - SSLCompression Off - SSLCertificateFile /etc/ssl/certs/server.pem - SSLCertificateKeyFile /etc/ssl/private/server-key.pem - - Header set X-Frame-Options: "sameorigin" - Header always edit Set-Cookie ^(.*)$ $1;HttpOnly;SameSite=Strict - Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains" - ServerSignature Off - TraceEnable Off - - Alias ${base_uri}/api ${install_dir} - Alias ${base_uri} ${install_dir}/www/ - - - AddOutputFilterByType BROTLI_COMPRESS text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/json - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/www/$1" - - - - ProxyPassMatch "fcgi://127.0.0.1:9042${install_dir}/api/index.php/$1" - - - ProxyTimeout 300 - ErrorDocument 404 ${base_uri}/index.html - Options -Indexes +FollowSymLinks - - - # https://github.com/SpiderLabs/ModSecurity/issues/652 - SecRuleRemoveById 200003 - - - - DirectoryIndex index.php - AllowOverride none - Require all granted - FallbackResource ${base_uri}/index.html - - - - AllowOverride none - Require all granted - - - - RedirectMatch ^/$ ${base_uri} - - -``` - -> Do not forget to change the **SSLCertificateFile** and **SSLCertificateKeyFile** directives with the path containing your own -> certificate and key. - - - - -5. Enable HttpOnly / Secure flags and hide the Apache server signature: - - - - -Edit the **/etc/php.d/50-centreon.ini** file: - -* Make sure that the `expose_php` parameter is disabled: - -```phpconf -expose_php = Off -``` - -* Add the path to the CA certificate that was used to sign the server's certificate: - - ```text - openssl.cafile=/etc/pki/tls/certs/rootCA.pem - curl.cainfo=/etc/pki/tls/certs/rootCA.pem - ``` - - - - -Edit the **/etc/php.d/50-centreon.ini** file: - -* Make sure that the `expose_php` parameter is disabled: - -```phpconf -expose_php = Off -``` - -* Add the path to the CA certificate that was used to sign the server's certificate: - - ```text - openssl.cafile=/etc/pki/tls/certs/rootCA.pem - curl.cainfo=/etc/pki/tls/certs/rootCA.pem - ``` - - - - -Edit the **/etc/php/8.4/mods-available/centreon.ini** file and add the following lines: - -```text -openssl.cafile=/etc/ssl/certs/rootCA.pem -curl.cainfo=/etc/ssl/certs/rootCA.pem -``` - - - - -6. Hide the default **/icons** directory: - - - - -Edit the **/etc/httpd/conf.d/autoindex.conf** file and comment the following line: - -```apacheconf -#Alias /icons/ "/usr/share/httpd/icons/" -``` - - - - -Edit the **/etc/httpd/conf.d/autoindex.conf** file and comment the following line: - -```apacheconf -#Alias /icons/ "/usr/share/httpd/icons/" -``` - - - - -> The default icons directory is already hidden. - - - - -7. You can perform this test to check that Apache is properly configured, by running the following command: - - - - -```apacheconf -apachectl configtest -``` - -The expected result is the following: - -```apacheconf -Syntax OK -``` - - - - -```apacheconf -apachectl configtest -``` - -The expected result is the following: - -```apacheconf -Syntax OK -``` - - - - -```apacheconf -apache2ctl configtest -``` - -The expected result is the following: - -```apacheconf -Syntax OK -``` - - - - -8. Restart the Apache and PHP processes to take the new configuration into account: - - - - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 - -``` - - - - -```shell -systemctl restart php-fpm httpd -``` - -Then check its status: - -```shell -systemctl status httpd -``` - -If everything is ok, you should have: - -```shell -● 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 - -``` - - - - -```shell -systemctl restart php8.4-fpm apache2 -``` - -Then check its status: - -```shell -systemctl status apache2 -``` - -If everything is ok, you should have: - -```shell -● apache2.service - The Apache HTTP Server - Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor pres> - Active: active (running) since Tue 2022-08-09 05:01:36 UTC; 3h 56min ago - Docs: https://httpd.apache.org/docs/2.4/ - Main PID: 518 (apache2) - Tasks: 11 (limit: 2356) - Memory: 18.1M - CPU: 1.491s - CGroup: /system.slice/apache2.service - ├─ 518 /usr/sbin/apache2 -k start - ├─1252 /usr/sbin/apache2 -k start - ├─1254 /usr/sbin/apache2 -k start - ├─1472 /usr/sbin/apache2 -k start - ├─3857 /usr/sbin/apache2 -k start - ├─3858 /usr/sbin/apache2 -k start - ├─3859 /usr/sbin/apache2 -k start - ├─3860 /usr/sbin/apache2 -k start - ├─3876 /usr/sbin/apache2 -k start - ├─6261 /usr/sbin/apache2 -k start - └─6509 /usr/sbin/apache2 -k start -``` - - - - -Now you can access your platform with your browser in HTTPS mode. - -> Once your web server is set to HTTPS mode, if you have a MAP server on your platform, you must set the `centreon.url=https://` inside the **/etc/centreon-map/map-config.properties** file to use HTTPS instead of HTTP. Otherwise recent web browsers may block communication between the two servers. The procedure is detailed [here](../graph-views/secure-your-map-platform.md#configure-httpstls-on-the-map-server). - -9. Gorgone API configuration - -Replace **127.0.0.1** with the FQDN of your central server in the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file, like in this example: - -```text -gorgone: - tpapi: - - name: centreonv2 - base_url: "https://centreon7.localdomain/centreon/api/latest/" - username: "centreon-gorgone" - password: "XXXXX" - - name: clapi - username: "centreon-gorgone" - password: "XXXXX" -``` - -Then restart the Gorgone daemon: - -```shell -systemctl restart gorgoned -``` - -Then check its status: - -```shell -systemctl status gorgoned -``` - -If everything is ok, you should have something like this (example on Debian): - -```shell -● gorgoned.service - Centreon Gorgone - Loaded: loaded (/usr/lib/systemd/system/gorgoned.service; enabled; preset: enabled) - Active: active (running) since Thu 2026-10-08 09:27:46 UTC; 4h 10min ago - Invocation: 40225788460245609d05c9db103f1ff3 - Main PID: 807 (perl) - Tasks: 51 (limit: 4618) - Memory: 176.2M (peak: 241.4M) - CPU: 9.461s - CGroup: /system.slice/gorgoned.service - ├─ 807 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=error - ├─1073 gorgone-proxy - ├─1075 gorgone-proxy - ├─1076 gorgone-proxy - ├─1077 gorgone-proxy - ├─1080 gorgone-proxy - ├─1086 gorgone-engine - ├─1089 gorgone-audit - ├─1097 gorgone-legacycmd - ├─1098 gorgone-httpserver - ├─1100 gorgone-nodes - ├─1107 gorgone-statistics - ├─1108 gorgone-cron - ├─1113 gorgone-anomalydetection - ├─1125 gorgone-autodiscovery - ├─1133 gorgone-action - └─1137 gorgone-dbcleaner - -Oct 08 09:27:46 doc-central systemd[1]: Started gorgoned.service - Centreon Gorgone. -``` - -You should see the following line in the Gorgone daemon log file **/var/log/centreon-gorgone/gorgoned.log**: - -```text -2026-10-08 15:58:12 - INFO - [autodiscovery] -class- host discovery - sync started -``` +> It is strongly recommended that you switch to HTTPS mode. Use a certificate issued by a trusted authority. Self-signed certificates must not be used in production. ## Custom URI diff --git a/versioned_docs/version-26.10/installation/_database-local-install.mdx b/versioned_docs/version-26.10/installation/_database-local-install.mdx index 7d71d9da6317..eedc7cb17410 100644 --- a/versioned_docs/version-26.10/installation/_database-local-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-local-install.mdx @@ -79,7 +79,7 @@ dnf install -y centreon-mysql centreon ```shell apt update -apt install -y centreon-mysql +apt install -y centreon-mysql mysql-common apt install -y centreon # Select "Use Legacy Authentication Method" systemctl daemon-reload diff --git a/versioned_docs/version-26.10/installation/_database-repository.mdx b/versioned_docs/version-26.10/installation/_database-repository.mdx index 9f55c460d294..df2eb8a929d3 100644 --- a/versioned_docs/version-26.10/installation/_database-repository.mdx +++ b/versioned_docs/version-26.10/installation/_database-repository.mdx @@ -58,7 +58,7 @@ rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-mysql-2023 ```shell -mysql_apt_config="mysql-apt-config_0.8.34-1_all.deb" +mysql_apt_config="mysql-apt-config_0.8.36-1_all.deb" curl -fJLO "https://dev.mysql.com/get/$mysql_apt_config" echo "mysql-apt-config mysql-apt-config/select-server select mysql-8.4-lts" | debconf-set-selections export DEBIAN_FRONTEND="noninteractive" @@ -66,8 +66,6 @@ apt install -y "./$mysql_apt_config" mysql_keyring=$(grep -ohm1 'signed-by=[^] ]*' /etc/apt/sources.list.d/mysql.list 2>/dev/null | cut -d= -f2) [ -z "$mysql_keyring" ] && mysql_keyring=/etc/apt/trusted.gpg.d/mysql.gpg ( set -o pipefail; curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2025 | gpg --dearmor --yes -o "$mysql_keyring" ) -apt update -apt install -y mysql-server mysql-common ``` diff --git a/versioned_docs/version-26.10/installation/_database-tls-conf.mdx b/versioned_docs/version-26.10/installation/_database-tls-conf.mdx index 532283594f99..9b1d6f898fc3 100644 --- a/versioned_docs/version-26.10/installation/_database-tls-conf.mdx +++ b/versioned_docs/version-26.10/installation/_database-tls-conf.mdx @@ -192,9 +192,10 @@ cat > /etc/mysql/conf.d/centreon-tls-client.cnf <<'EOF' [client] ssl-ca=/etc/mysql/centreon-tls/rootCA.pem ssl-verify-server-cert +EOF ``` -4. Start MySQL. +4. Start MariaDB. ```shell systemctl daemon-reload diff --git a/versioned_docs/version-26.10/installation/_install-common.mdx b/versioned_docs/version-26.10/installation/_install-common.mdx index 31d6bac0f571..9240ba2b606a 100644 --- a/versioned_docs/version-26.10/installation/_install-common.mdx +++ b/versioned_docs/version-26.10/installation/_install-common.mdx @@ -142,7 +142,7 @@ SELinux is not installed on Debian 13, continue. ### Configure or disable the firewall -If your firewall is active, add [firewall rules](../administration/secure-platform.md#enable-firewalld). +If you have a firewall and it is active, add [firewall rules](../administration/secure-platform.md#enable-firewalld). You can also disable the firewall during installation by running the following commands: ```shell diff --git a/versioned_docs/version-26.10/installation/_tls-certificates.mdx b/versioned_docs/version-26.10/installation/_tls-certificates.mdx index ff9404ecdcfb..ad509f355307 100644 --- a/versioned_docs/version-26.10/installation/_tls-certificates.mdx +++ b/versioned_docs/version-26.10/installation/_tls-certificates.mdx @@ -5,7 +5,7 @@ Use a certificate issued by a trusted authority. Self-signed certificates may be * If you already have a certificate validated by an authority, you can proceed to the next step. * If you do not have a certificate validated by an authority, you can generate one on platforms such as [Let's Encrypt](https://letsencrypt.org/). -* If, for test purposes, you want to use a self-signed certificate, follow [this procedure](../administration/self-signed-certificate.md). +- If, for test purposes, you want to use a self-signed certificate, follow [this procedure](./self-signed-certificate.md) before activating HTTPS mode on your server. Note that you will have to import the CA certificate into your browser. Let's say you have the following files in **/etc/pki/centreon-tls/**: @@ -37,6 +37,7 @@ Let's say you have the following files in **/etc/pki/centreon-tls/**: ```shell cp /etc/pki/centreon-tls/rootCA.pem /usr/local/share/ca-certificates/centreon-dev.crt + update-ca-certificates ```     diff --git a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md index b8e7ba1f454a..a04bb44ef3cc 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-central-server/using-packages.md @@ -178,28 +178,28 @@ Then execute the following command (on the central server if you are using a loc ## Step 5: Web installation -1. Start the Apache server with the +1. Restart the Apache server with the following command: ```shell -systemctl start httpd +systemctl restart httpd ``` ```shell -systemctl start httpd +systemctl restart httpd ``` ```shell -systemctl start apache2 +systemctl restart apache2 ``` From a6dd85da741205d1d36ec0325fc2e24d2c570306 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 9 Oct 2026 13:05:05 +0200 Subject: [PATCH 124/179] Fix link --- .../version-26.10/installation/_tls-certificates.mdx | 2 +- versioned_docs/version-26.10/installation/_tls-certificates.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx index 384c8e92fec6..557cea715140 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx @@ -5,7 +5,7 @@ Utilisez un certificat délivré par une autorité de confiance. Les certificats * Si vous disposez déjà d'un certificat validé par une autorité, passez à l'étape suivante. * Si vous ne disposez pas d'un certificat validé par une autorité, vous pouvez en générer un sur des plateformes telles que [Let's Encrypt](https://letsencrypt.org/). -- Si, à des fins de test, vous souhaitez utiliser un certificat auto-signé, [vous pouvez suivre cett procédure pour en créer un](./self-signed-certificate.md) avant d'activer le mode HTTPS sur votre serveur. Attention, vous devrez importer le certificat de l'autorité de certification (CA) dans votre navigateur. +- Si, à des fins de test, vous souhaitez utiliser un certificat auto-signé, [vous pouvez suivre cett procédure pour en créer un](../administration/self-signed-certificate.md) avant d'activer le mode HTTPS sur votre serveur. Attention, vous devrez importer le certificat de l'autorité de certification (CA) dans votre navigateur. Supposons que vous disposiez des fichiers suivants dans **/etc/pki/centreon-tls/** : diff --git a/versioned_docs/version-26.10/installation/_tls-certificates.mdx b/versioned_docs/version-26.10/installation/_tls-certificates.mdx index ad509f355307..00187316bac6 100644 --- a/versioned_docs/version-26.10/installation/_tls-certificates.mdx +++ b/versioned_docs/version-26.10/installation/_tls-certificates.mdx @@ -5,7 +5,7 @@ Use a certificate issued by a trusted authority. Self-signed certificates may be * If you already have a certificate validated by an authority, you can proceed to the next step. * If you do not have a certificate validated by an authority, you can generate one on platforms such as [Let's Encrypt](https://letsencrypt.org/). -- If, for test purposes, you want to use a self-signed certificate, follow [this procedure](./self-signed-certificate.md) before activating HTTPS mode on your server. Note that you will have to import the CA certificate into your browser. +- If, for test purposes, you want to use a self-signed certificate, follow [this procedure](../administration/self-signed-certificate.md) before activating HTTPS mode on your server. Note that you will have to import the CA certificate into your browser. Let's say you have the following files in **/etc/pki/centreon-tls/**: From 8e432034d14e96692f08685855616ea6d06e8c4d Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 9 Oct 2026 13:41:21 +0200 Subject: [PATCH 125/179] Fix anchor --- .../pollers-containers-prerequisites.md | 2 +- .../pollers-containers-prerequisites.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md index b9abdeb9ab02..766caa497a04 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md @@ -31,7 +31,7 @@ La méthode recommandée et sécurisée consiste à utiliser HTTPS. Des certific * Assurez-vous que le serveur central et Gorgone sont déjà installés et à jour dans la dernière version majeure. -* Si ce n'est pas déjà fait, configurez le HTTPS sur votre serveur central. Cela peut être fait dans le cadre de la [procédure d'installation](../installation-of-a-central-server/using-packages.md#étape-3--mettre-en-place-la-configuration-tls), ou [séparément](../../administration/secure-platform.md#activer-le-mode-https-sur-le-serveur-web). +* Si ce n'est pas déjà fait, configurez le HTTPS sur votre serveur central. Cela peut être fait dans le cadre de la [procédure d'installation](../installation-of-a-central-server/using-packages.md#étape-3--mettre-en-place-la-configuration-tls), ou séparément. Une fois HTTPS activé, mettez également à jour l'URL de l'API Gorgone : dans **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** sur le serveur central, définissez `base_url` sur `https:///centreon/api/latest/`, puis redémarrez Gorgone (`systemctl restart gorgoned`). Sinon, le serveur central rejettera chaque collecteur exécuté dans un conteneur avec une erreur `invalid token`. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md index e3c637db53ec..66f15310eed6 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md @@ -31,7 +31,7 @@ The recomended and secure way is to use HTTPS. This means that certificates are * Ensure the central server and Gorgone are already installed and up to date with the latest major version. -* If not already done, configure HTTPS on your central server. This can be done as part of the [installation procedure](../installation-of-a-central-server/using-packages.md#step-3-set-up-the-tls-configuration), or [separately](../../administration/secure-platform.md#activating-https-mode-on-your-web-server). +* If not already done, configure HTTPS on your central server. This can be done as part of the [installation procedure](../installation-of-a-central-server/using-packages.md#step-3-set-up-the-tls-configuration), or separately. Once HTTPS is enabled, also update the Gorgone API URL: in **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** on the central server, set `base_url` to `https:///centreon/api/latest/`, then restart Gorgone (`systemctl restart gorgoned`). Otherwise, the central server rejects every poller in a container with an `invalid token` error. From 4a33cc10394f7befe9fe564dca210e341b6c3a8d Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 9 Oct 2026 15:10:09 +0200 Subject: [PATCH 126/179] Changes following review --- .../version-26.10/upgrade/_intro.mdx | 2 +- .../version-26.10/upgrade/_upgrade-central.mdx | 2 +- .../version-26.10/upgrade/_upgrade-pollers.mdx | 2 +- versioned_docs/version-26.10/upgrade/_intro.mdx | 2 +- versioned_docs/version-26.10/upgrade/_upgrade-central.mdx | 2 +- versioned_docs/version-26.10/upgrade/_upgrade-pollers.mdx | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx index 6a1ea6eec21e..f493f72061b6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_intro.mdx @@ -61,7 +61,7 @@ Avant de monter de version votre plateforme Centreon, assurez-vous que les dép * BaseOS * AppStream * centreon -* centreon-modules, si vous utilisez Centreon Business Edition. +* centreon-business, si vous utilisez Centreon Business Edition.     diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx index 5d7bbcb1e6ca..4421d76472fe 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx @@ -19,7 +19,7 @@ import Link from '@docusaurus/Link'; 2. Supprimez les fichiers des dépôts : - {`rm /etc/yum.repos.d/centreon-${props.oldCentreonVersion}.repo\nrm /etc/yum.repos.d/centreon.repo`} + {`rm -f /etc/yum.repos.d/centreon-${props.oldCentreonVersion}.repo\nrm -f /etc/yum.repos.d/centreon.repo`} 3. Installez le nouveau dépôt : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-pollers.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-pollers.mdx index 365f321d9675..d79881a5c022 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-pollers.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-pollers.mdx @@ -39,7 +39,7 @@ Montez ensuite tous les composants de version à l'aide de la commande suivante ```shell -dnf update centreon\* +dnf update centreon\* -y ``` > Si vous avez installé MariaDB à partir de ses dépôts officiels, vous pouvez rencontrer un conflit. Consultez notre [procédure dédiée](../resources/known-issues.md#vous-avez-un-conflit-entre-les-paquets-mysql-common-et-mariadb-common) pour le contourner. diff --git a/versioned_docs/version-26.10/upgrade/_intro.mdx b/versioned_docs/version-26.10/upgrade/_intro.mdx index 1048f3557115..8663a1653a90 100644 --- a/versioned_docs/version-26.10/upgrade/_intro.mdx +++ b/versioned_docs/version-26.10/upgrade/_intro.mdx @@ -61,7 +61,7 @@ Before upgrading your Centreon platform, make sure the following package reposit * BaseOS * AppStream * centreon -* centreon-modules, if you are using Centreon Business Edition. +* centreon-business, if you are using Centreon Business Edition.     diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index a1c9b85f32ef..4b012aab3c30 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -19,7 +19,7 @@ import Link from '@docusaurus/Link'; 2. Remove the repository files: - {`rm /etc/yum.repos.d/centreon-${props.oldCentreonVersion}.repo\nrm /etc/yum.repos.d/centreon.repo`} + {`rm -f /etc/yum.repos.d/centreon-${props.oldCentreonVersion}.repo\nrm -f /etc/yum.repos.d/centreon.repo`} 3. Install the new repository: diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-pollers.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-pollers.mdx index 449ef892cc40..c02d5b5ef507 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-pollers.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-pollers.mdx @@ -39,7 +39,7 @@ Then upgrade all the components with the following command: ```shell -dnf update centreon\* +dnf update centreon\* -y ``` > If you installed MariaDB from their official repositories, you may run into a conflict issue. Read our [dedicated procedure](../resources/known-issues.md#you-have-a-conflict-between-packages-mysql-common-and-mariadb-common) for a workaround. From 75282236afab6f636872424c80963ebccc71b7d0 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 9 Oct 2026 15:30:32 +0200 Subject: [PATCH 127/179] Changes following review --- .../version-26.10/upgrade/_upgrade-central.mdx | 17 +++++++++++++++++ .../version-26.10/upgrade/_upgrade-central.mdx | 17 +++++++++++++++++ 2 files changed, 34 insertions(+) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx index 4421d76472fe..58c37c1105ab 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx @@ -116,6 +116,23 @@ dnf update -y "centreon*" --exclude=php-pecl-gnupg > Acceptez les nouvelles clés GPG des dépôts si elles vous sont proposées. +Les paquets RPM peuvent marquer certains fichiers de configuration pour qu'ils ne soient jamais écrasés lors d'une mise à jour. Si vous avez modifié l'un de ces fichiers et que le nouveau paquet en fournit une version différente, dnf conserve votre fichier et écrit la version du paquet à côté, avec l'extension .rpmnew. Par exemple, vous conservez centengine.cfg et obtenez aussi centengine.cfg.rpmnew. Aucune fusion n'est faite automatiquement. Comparez les deux fichiers et choisissez ce que vous voulez reporter : + +Voici les fichiers susceptibles d'être concernés. Vous n'aurez pas forcément un fichier .rpmnew pour chacun d'eux : seuls les fichiers que vous avez modifiés et dont le paquet fournit une nouvelle version en génèrent un. + +```shell +/etc/logrotate.d/centreon +/etc/httpd/conf.d/10-centreon.conf +/etc/php.d/50-centreon.ini +/etc/php/${PHP_MIN_VERSION}/mods-available/centreon.ini +/etc/php-fpm.d/centreon.conf +/etc/php/${PHP_MIN_VERSION}/fpm/pool.d/centreon.conf +/etc/systemd/system/php-fpm.service.d/centreon.conf +/lib/systemd/system/php${PHP_MIN_VERSION}-fpm.service.d/centreon.conf +/usr/share/centreon/.env +/usr/share/centreon/.env.local.php +``` + ### Étape 5 : Mettre à jour votre configuration Apache personnalisée Cette section s'applique uniquement si vous avez personnalisé votre configuration Apache. diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index 4b012aab3c30..f2238dd58b8f 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -116,6 +116,23 @@ dnf update -y "centreon*" --exclude=php-pecl-gnupg > Accept new GPG keys from the repositories as needed. +RPM packages can mark some configuration files so they are never overwritten on upgrade. If you modified one of those files and the new package ships a different version of it, dnf keeps your file and writes the package's version next to it with a .rpmnew extension. For example, you keep centengine.cfg and also get centengine.cfg.rpmnew. Nothing is merged automatically. Compare the two files and decide what to copy over. + +The following files may be affected. You won't necessarily get an .rpmnew file for each of them: one is only created for files that you modified and for which the package ships a new version. + +```shell +/etc/logrotate.d/centreon +/etc/httpd/conf.d/10-centreon.conf +/etc/php.d/50-centreon.ini +/etc/php/${PHP_MIN_VERSION}/mods-available/centreon.ini +/etc/php-fpm.d/centreon.conf +/etc/php/${PHP_MIN_VERSION}/fpm/pool.d/centreon.conf +/etc/systemd/system/php-fpm.service.d/centreon.conf +/lib/systemd/system/php${PHP_MIN_VERSION}-fpm.service.d/centreon.conf +/usr/share/centreon/.env +/usr/share/centreon/.env.local.php +``` + ### Step 5: Update your customized Apache configuration This section only applies if you customized your Apache configuration. From a58dd5fc11d05eb7f8aa26d24d18a6952029e496 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 9 Oct 2026 16:00:41 +0200 Subject: [PATCH 128/179] Changes following review --- .../installation/_database-local-install.mdx | 2 ++ .../installation/_database-remote-install.mdx | 22 +++++++------------ .../installation/_database-local-install.mdx | 2 ++ .../installation/_database-remote-install.mdx | 21 +++++++----------- 4 files changed, 20 insertions(+), 27 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx index b3944dbbde5e..1951cb50e413 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx @@ -61,6 +61,7 @@ Répondez **yes** à toutes les questions sauf à "Disallow root login remotely? ```shell dnf install -y mysql-server mysql dnf install -y centreon-mysql +grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf systemctl enable --now mysqld sed -Ei 's/LimitNOFILE\s\=\s[0-9]{1,}/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service systemctl daemon-reload @@ -72,6 +73,7 @@ systemctl restart mysqld ```shell dnf install -y centreon-mysql centreon +grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx index 6e12b8d0ff55..972ac63eebbe 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-remote-install.mdx @@ -77,14 +77,11 @@ systemctl restart mariadb ```shell dnf install -y mysql-server mysql dnf install -y centreon-mysql -systemctl enable --now mysqld -echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf +grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf +sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service systemctl daemon-reload -systemctl restart mysqld -systemctl list-units --type=service | grep -i mysql -sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service -sudo systemctl start mysqld -sudo systemctl status mysqld +systemctl enable --now mysqld +systemctl status mysqld ```     @@ -93,14 +90,11 @@ sudo systemctl status mysqld ```shell dnf install -y mysql-server mysql dnf install -y centreon-mysql -systemctl enable --now mysqld -echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf +grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf +sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service systemctl daemon-reload -systemctl restart mysqld -systemctl list-units --type=service | grep -i mysql -sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service -sudo systemctl start mysqld -sudo systemctl status mysqld +systemctl enable --now mysqld +systemctl status mysqld ```     diff --git a/versioned_docs/version-26.10/installation/_database-local-install.mdx b/versioned_docs/version-26.10/installation/_database-local-install.mdx index eedc7cb17410..434e8aaa877f 100644 --- a/versioned_docs/version-26.10/installation/_database-local-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-local-install.mdx @@ -61,6 +61,7 @@ Answer **yes** to all the questions except "Disallow root login remotely?". ```shell dnf install -y mysql-server mysql dnf install -y centreon-mysql +grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf systemctl enable --now mysqld sed -Ei 's/LimitNOFILE\s\=\s[0-9]{1,}/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service systemctl daemon-reload @@ -72,6 +73,7 @@ systemctl restart mysqld ```shell dnf install -y centreon-mysql centreon +grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf ```     diff --git a/versioned_docs/version-26.10/installation/_database-remote-install.mdx b/versioned_docs/version-26.10/installation/_database-remote-install.mdx index a15e11abd528..72b1c8fee096 100644 --- a/versioned_docs/version-26.10/installation/_database-remote-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-remote-install.mdx @@ -77,13 +77,11 @@ systemctl restart mariadb ```shell dnf install -y mysql-server mysql dnf install -y centreon-mysql -systemctl enable --now mysqld +grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf +sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service systemctl daemon-reload -systemctl restart mysqld -systemctl list-units --type=service | grep -i mysql -sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service -sudo systemctl start mysqld -sudo systemctl status mysqld +systemctl enable --now mysqld +systemctl status mysqld ```     @@ -92,14 +90,11 @@ sudo systemctl status mysqld ```shell dnf install -y mysql-server mysql dnf install -y centreon-mysql -systemctl enable --now mysqld -echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysql-server.cnf +grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf +sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service systemctl daemon-reload -systemctl restart mysqld -systemctl list-units --type=service | grep -i mysql -sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service -sudo systemctl start mysqld -sudo systemctl status mysqld +systemctl enable --now mysqld +systemctl status mysqld ```     From c3011f102aa884464b5c794a115b76e138f7548b Mon Sep 17 00:00:00 2001 From: smau Date: Fri, 9 Oct 2026 16:52:20 +0200 Subject: [PATCH 129/179] Update following QA feedback --- .../version-26.10/graph-views/map-web-install.md | 10 +++++----- .../version-26.10/graph-views/map-web-install.md | 11 +++++------ 2 files changed, 10 insertions(+), 11 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index 6bc213197969..e0dc7d039c38 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -396,21 +396,21 @@ Vous devez d'abord ajouter le dépôt MariaDB : ```shell -dnf module enable -y mariadb:10.11 +dnf module enable -y mariadb:11.8 ``` ```shell -dnf module enable -y mariadb:10.11 +dnf module enable -y mariadb:11.8 ``` ```shell -curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=13 --mariadb-server-version="mariadb-10.11" +curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=13 --mariadb-server-version="mariadb-11.8" ``` @@ -1059,9 +1059,9 @@ Par défaut, le module MAP n'est pas activé. Suivez cette procédure pour l'act 1. Connectez-vous à l'interface Centreon et allez à la page **Administration > Extensions > Map > Options**. ![image](../assets/graph-views/ng/switch-map-engine.png) -2. Dans la section **Informations de connexion**, définissez **Serveur Map Engine** sur **Oui**. +2. Dans la section **Informations de connexion**, saisissez l'adresse IP de votre serveur MAP dans le champ **Adresse du serveur Map Engine**. C'est l'adresse qu'utilise votre navigateur web pour joindre MAP. -3. Saisissez l'adresse IP de votre serveur MAP dans le champ **Adresse du serveur Map Engine**. Si vous avez installé MAP sur le serveur central, il s'agit de l'adresse IP du serveur central. Utilisez son adresse IP complète, et non l'adresse locale (localhost). Le port par défaut est 8081. Par exemple : ``http://10.25.xxx:8081``. +3. Renseignez ensuite le champ **Adresse du serveur MAP vue par le central**. C'est l'adresse qu'utilise le serveur central Centreon pour joindre MAP. Si MAP est installé sur le serveur central lui-même, saisir l'adresse IP du serveur central. 4. Cliquez sur le bouton **Test de connexion au serveur** pour tester la connexion. Ce test doit retourner le message **Test de connexion réussi**. diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index 60ab068c8b18..1e366f92899e 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -404,21 +404,21 @@ First you need to add the MariaDB repository: ```shell -dnf module enable -y mariadb:10.11 +dnf module enable -y mariadb:11.8 ``` ```shell -dnf module enable -y mariadb:10.11 +dnf module enable -y mariadb:11.8 ``` ```shell -curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=13 --mariadb-server-version="mariadb-10.11" +curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | sudo bash -s -- --os-type=debian --os-version=13 --mariadb-server-version="mariadb-11.8" ``` @@ -1073,11 +1073,10 @@ Install the Centreon Business repository. You can find this on the By default, the MAP module is not enabled. Perform the following procedure to enable it. 1. Log on to the Centreon interface and go to **Administration > Extensions > Map > Options**. - ![image](../assets/graph-views/ng/switch-map-engine.png) -2. In the **Connection information** section, set **Map Engine server** to **Yes**. +2. In the **Connection information** section, enter the IP address of your MAP server in the **MAP Engine server address** field. This is the address your web browser uses to connect to MAP. -3. Enter the IP address of your MAP server in the **Map Engine server address** field. If you installed MAP on the central server, this is the IP address of the central server. Use its full IP address, not the localhost. The default port is 8081 (for instance: ``http://10.25.xxx:8081``). +3. Then fill in the **MAP server address as seen by Central** field. This is the address that the Centreon central server uses to connect to MAP. If MAP is installed on the central server itself, enter the central server's IP address. 4. Click the **Test connection to server** button to test the connection. This test should return the **Connection test successful** message. From 7a470e85d2422640b0447f3e4616d809da76dbe1 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 12 Oct 2026 15:06:32 +0200 Subject: [PATCH 130/179] Fix link --- .../version-26.10/upgrade/_upgrade-central.mdx | 2 +- versioned_docs/version-26.10/upgrade/_upgrade-central.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx index 58c37c1105ab..f11748b51bd4 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/_upgrade-central.mdx @@ -310,7 +310,7 @@ commande suivante :     -5. Consultez les procédures dédiées à [Centreon MBI](../reporting/update.md) et à [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. +5. Consultez les procédures dédiées à [Centreon MBI](../reporting/upgrade.md) et à [Centreon MAP](../graph-views/map-web-upgrade.md) pour mettre à jour ces modules. ### Étape 8 : Actions post montée de version diff --git a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx index f2238dd58b8f..db07134688d0 100644 --- a/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx +++ b/versioned_docs/version-26.10/upgrade/_upgrade-central.mdx @@ -308,7 +308,7 @@ AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javasc     -5. Refer to the [Centreon MBI](../reporting/update.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. +5. Refer to the [Centreon MBI](../reporting/upgrade.md) and [Centreon MAP](../graph-views/map-web-upgrade.md) dedicated procedures to update these modules. ### Step 8: Post-upgrade actions From a08f2412c34c1a57d47ddf215208d09c64bd3a90 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 12 Oct 2026 15:10:40 +0200 Subject: [PATCH 131/179] Fix reference to wrong version --- .../version-26.10/upgrade/upgrade-mariadb.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md index 93210cdffa07..6c160ee469d8 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/upgrade/upgrade-mariadb.md @@ -68,7 +68,7 @@ Dans cet exemple, nous passons de la version 10.11 à la version 11.8. Adaptez l dnf module reset mariadb -y ``` -3. Installez la version 10.11 : +3. Installez la version 11.8 : ```shell dnf module enable -y mariadb:11.8 From 3732d7cf2b0e38668aed92bd661205b0da9bf0a9 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 12 Oct 2026 15:39:11 +0200 Subject: [PATCH 132/179] Changes following review --- .../installation/_database-local-install.mdx | 16 +--------------- .../installation/_database-local-install.mdx | 17 +---------------- 2 files changed, 2 insertions(+), 31 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx index 1951cb50e413..5ee0828262ed 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx @@ -60,7 +60,7 @@ Répondez **yes** à toutes les questions sauf à "Disallow root login remotely? ```shell dnf install -y mysql-server mysql -dnf install -y centreon-mysql +dnf install -y centreon-mysql centreon grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf systemctl enable --now mysqld sed -Ei 's/LimitNOFILE\s\=\s[0-9]{1,}/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service @@ -91,19 +91,5 @@ systemctl restart mysql     -Vous devez obligatoirement définir un mot de passe pour l'utilisateur root de la base de données (vous aurez besoin de ce mot de passe lors de l'[installation web](web-and-post-installation.md)). Il doit comporter au moins 8 caractères, dont des majuscules, des minuscules, un chiffre et un caractère spécial. Récupérez le mot de passe temporaire créé par MySQL : - -```shell -grep 'temporary password' /var/log/mysqld.log -``` - -Modifiez-le ensuite lorsque la commande suivante vous y invite : - -```shell -mysql_secure_installation -``` - -Répondez **yes** à toutes les questions sauf à "Disallow root login remotely?". -     diff --git a/versioned_docs/version-26.10/installation/_database-local-install.mdx b/versioned_docs/version-26.10/installation/_database-local-install.mdx index 434e8aaa877f..97a8ad434e0c 100644 --- a/versioned_docs/version-26.10/installation/_database-local-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-local-install.mdx @@ -60,7 +60,7 @@ Answer **yes** to all the questions except "Disallow root login remotely?". ```shell dnf install -y mysql-server mysql -dnf install -y centreon-mysql +dnf install -y centreon-mysql centreon grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf systemctl enable --now mysqld sed -Ei 's/LimitNOFILE\s\=\s[0-9]{1,}/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld.service @@ -91,20 +91,5 @@ systemctl restart mysql     - -It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](web-and-post-installation.md)). It must have at least 8 characaters, upper and lower case, a digit and a special character. Retrieve the temporary password created by MySQL: - -```shell -grep 'temporary password' /var/log/mysqld.log -``` - -Then change it when prompted by the following command: - -```shell -mysql_secure_installation -``` - -Answer **yes** to all the questions except "Disallow root login remotely?". -     From e5b0f86856a018e6732e441bf6f4e150559d82f5 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 12 Oct 2026 15:46:10 +0200 Subject: [PATCH 133/179] Changes following review --- .../installation/_database-local-install.mdx | 28 +++++++++++++++++++ .../installation/_database-local-install.mdx | 28 +++++++++++++++++++ 2 files changed, 56 insertions(+) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx index 5ee0828262ed..5f3487e10b68 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx @@ -68,6 +68,20 @@ systemctl daemon-reload systemctl restart mysqld ``` +Vous devez obligatoirement définir un mot de passe pour l'utilisateur root de la base de données (vous aurez besoin de ce mot de passe lors de l'[installation web](web-and-post-installation.md)). Il doit comporter au moins 8 caractères, dont des majuscules, des minuscules, un chiffre et un caractère spécial. Récupérez le mot de passe temporaire créé par MySQL : + +```shell +grep 'temporary password' /var/log/mysqld.log +``` + +Modifiez-le ensuite lorsque la commande suivante vous y invite : + +```shell +mysql_secure_installation +``` + +Répondez **yes** à toutes les questions sauf à "Disallow root login remotely?". +     @@ -76,6 +90,20 @@ dnf install -y centreon-mysql centreon grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf ``` +Vous devez obligatoirement définir un mot de passe pour l'utilisateur root de la base de données (vous aurez besoin de ce mot de passe lors de l'[installation web](web-and-post-installation.md)). Il doit comporter au moins 8 caractères, dont des majuscules, des minuscules, un chiffre et un caractère spécial. Récupérez le mot de passe temporaire créé par MySQL : + +```shell +grep 'temporary password' /var/log/mysqld.log +``` + +Modifiez-le ensuite lorsque la commande suivante vous y invite : + +```shell +mysql_secure_installation +``` + +Répondez **yes** à toutes les questions sauf à "Disallow root login remotely?". + diff --git a/versioned_docs/version-26.10/installation/_database-local-install.mdx b/versioned_docs/version-26.10/installation/_database-local-install.mdx index 97a8ad434e0c..236adfc8b2d5 100644 --- a/versioned_docs/version-26.10/installation/_database-local-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-local-install.mdx @@ -68,6 +68,20 @@ systemctl daemon-reload systemctl restart mysqld ``` +It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](web-and-post-installation.md)). It must have at least 8 characaters, upper and lower case, a digit and a special character. Retrieve the temporary password created by MySQL: + +```shell +grep 'temporary password' /var/log/mysqld.log +``` + +Then change it when prompted by the following command: + +```shell +mysql_secure_installation +``` + +Answer **yes** to all the questions except "Disallow root login remotely?". + @@ -76,6 +90,20 @@ dnf install -y centreon-mysql centreon grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf ``` +It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](web-and-post-installation.md)). It must have at least 8 characaters, upper and lower case, a digit and a special character. Retrieve the temporary password created by MySQL: + +```shell +grep 'temporary password' /var/log/mysqld.log +``` + +Then change it when prompted by the following command: + +```shell +mysql_secure_installation +``` + +Answer **yes** to all the questions except "Disallow root login remotely?". + From df3e058448125e01d2d9dfb7fdb6735a5caf2309 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 12 Oct 2026 17:45:05 +0200 Subject: [PATCH 134/179] Changes following review --- .../version-26.10/installation/_database-local-install.mdx | 1 + .../version-26.10/installation/_database-local-install.mdx | 1 + 2 files changed, 2 insertions(+) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx index 5f3487e10b68..fa738767a666 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-local-install.mdx @@ -88,6 +88,7 @@ Répondez **yes** à toutes les questions sauf à "Disallow root login remotely? ```shell dnf install -y centreon-mysql centreon grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf +systemctl start mysqld ``` Vous devez obligatoirement définir un mot de passe pour l'utilisateur root de la base de données (vous aurez besoin de ce mot de passe lors de l'[installation web](web-and-post-installation.md)). Il doit comporter au moins 8 caractères, dont des majuscules, des minuscules, un chiffre et un caractère spécial. Récupérez le mot de passe temporaire créé par MySQL : diff --git a/versioned_docs/version-26.10/installation/_database-local-install.mdx b/versioned_docs/version-26.10/installation/_database-local-install.mdx index 236adfc8b2d5..5c78b8698027 100644 --- a/versioned_docs/version-26.10/installation/_database-local-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-local-install.mdx @@ -88,6 +88,7 @@ Answer **yes** to all the questions except "Disallow root login remotely?". ```shell dnf install -y centreon-mysql centreon grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cnf.d' >> /etc/my.cnf +systemctl start mysqld ``` It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](web-and-post-installation.md)). It must have at least 8 characaters, upper and lower case, a digit and a special character. Retrieve the temporary password created by MySQL: From b2aa8d956de1c35a25532fbeb09ea756a719b6d6 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 13 Oct 2026 16:31:58 +0200 Subject: [PATCH 135/179] Changes following review (self-signed certificates) --- .../administration/self-signed-certificate.md | 214 ++++++++++++------ .../administration/self-signed-certificate.md | 208 +++++++++++------ 2 files changed, 278 insertions(+), 144 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md index c979c4303c11..f3e8a29f336e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md @@ -10,33 +10,25 @@ import TabItem from '@theme/TabItem'; ## Fichiers nécessaires pour établir des connexions TLS avec des certificats auto-signés -Cette procédure vous permet de créer les fichiers suivants : +Cette procédure vous permet de créer l'ensemble de fichiers suivant, qui suffit à sécuriser la connexion à l'interface web et à la base de données : | Fichier | Où le stocker | Rôle | |--------------|-----------------------------------|-------------------------------------------------------------------------| -| server-key.pem | Sur le serveur à sécuriser (central/distant, base de données...) | Clé privée de **server.pem** : reste secrète sur le serveur sécurisé. Sert à prouver l'identité du serveur. | -| server.pem | Sur le serveur à sécuriser (central/distant, base de données...) | Certificat signé, envoyé automatiquement à tout client qui tente de se connecter au serveur sécurisé. | -| rootCA.pem | Sur le client (navigateur, système d'exploitation...) | Certificat auto-signé de l'autorité de certification racine. Ce fichier public sert à valider le certificat **server.pem** reçu par le client. Vous devrez copier **rootCA.pem** sur toutes les machines qui communiqueront avec la machine sécurisée (celle qui a envoyé **server.pem**). | -| rootCA.key | Uniquement sur la machine qui génère l'autorité de certification, dans un dossier temporaire | Ce fichier ne joue aucun rôle en production. Il sert uniquement à signer **rootCA.pem** lors de sa création. | +| web-key.pem | Sur le serveur central/distant à sécuriser | Clé privée de **web.pem** : reste secrète sur le serveur sécurisé. Sert à prouver l'identité du serveur. | +| web.pem | Sur le serveur central/distant à sécuriser | Le certificat signé qui sera envoyé automatiquement à tout client tentant de se connecter au serveur central/distant sécurisé. | +| db-key.pem | Sur le serveur de base de données à sécuriser | Clé privée de **db.pem** : reste secrète sur le serveur sécurisé. Sert à prouver l'identité du serveur. | +| db.pem | Sur le serveur de base de données à sécuriser | Le certificat signé qui sera envoyé automatiquement à tout client tentant de se connecter au serveur de base de données sécurisé. | +| rootCA.pem | Sur le client (navigateur, OS...) | Certificat auto-signé de l'autorité de certification racine. Il s'agit d'un fichier public, qui sert à valider le certificat **web.pem** ou **db.pem** reçu par le client. **rootCA.pem** devra être copié sur toutes les machines qui interagiront avec la machine sécurisée (celle qui a envoyé **web.pem** ou **db.pem**). | +| rootCA.key | À conserver en lieu sûr, afin de pouvoir renouveler les certificats. | Clé privée de l'autorité de certification racine. Sert à signer **web.pem** et **db.pem**, ainsi qu'à signer de nouveaux certificats lorsqu'ils expirent (au bout de 397 jours). Ne la copiez jamais sur une autre machine. Si vous la perdez, vous devrez créer une nouvelle CA et redéployer **rootCA.pem** partout. | ## Ce que fait cette procédure -La procédure crée, dans des dossiers temporaires, les fichiers nécessaires pour établir une connexion TLS. Lorsque vous configurerez HTTPS sur un serveur, vous devrez déployer ces fichiers au bon emplacement. Par exemple, **/etc/pki** est l'emplacement par défaut des certificats sous EL. Sous Debian, le chemin par défaut est **/etc/ssl/certs**. +La procédure crée les fichiers nécessaires à la mise en place d'une connexion TLS, dans des dossiers temporaires. Lorsque vous configurez HTTPS sur un serveur, vous devez déployer les fichiers nécessaires au bon emplacement (la dernière étape explique où les copier). -Vous pouvez suivre cette procédure sur une plateforme Centreon dont la base de données est locale ou distante. +La procédure peut être exécutée sur une plateforme Centreon disposant d'une base de données locale ou distante. -* Si votre base de données est locale, exécutez les commandes des deux onglets sur votre serveur Centreon. -* Si votre base de données est distante, suivez la procédure deux fois : - * Sur votre serveur Centreon, créez une autorité de certification (étapes 1 à 3), puis exécutez les commandes des onglets **Sur le serveur central/distant**. - * Sur le serveur de base de données, créez une autre autorité de certification, puis exécutez les commandes des onglets **Sur le serveur de base de données**. - - Vous obtenez alors deux fichiers **rootCA.pem** différents. Copiez le fichier **rootCA.pem** du serveur de base de données sur les machines qui se connectent à la base de données (par exemple, votre serveur Centreon). Copiez le fichier **rootCA.pem** de votre serveur Centreon sur les machines qui se connectent à celui-ci. - - +* Si vous avez une base de données locale, exécutez les commandes des deux onglets sur votre serveur Centreon. +* Si vous avez une base de données distante, exécutez toute la procédure sur votre serveur Centreon (les deux onglets). La dernière étape explique comment copier **rootCA.pem**, **db.pem** et **db-key.pem** sur le serveur de base de données. ## Étape 1 : Créer les répertoires de sortie @@ -48,17 +40,17 @@ Pour l'autorité de certification : sudo mkdir -p /out/CA ``` -Pour le serveur central/distant, ou pour la base de données : +Pour chaque certificat : - + ```shell sudo mkdir -p /out/web ``` - + ```shell sudo mkdir -p /out/db @@ -78,7 +70,7 @@ sudo chmod 400 /out/CA/rootCA.key ## Étape 3 : Générer le certificat auto-signé de l'autorité de certification racine (10 ans) -Créez maintenant le certificat de l'autorité de certification. Ce document public identifie votre autorité de certification (nom, organisation, etc.). Vous le distribuerez ensuite à tous les clients et serveurs qui doivent faire confiance aux certificats qu'elle signe. +Cette étape crée le certificat de l'autorité de certification : le document public qui identifie votre autorité de certification (nom, organisation, etc.) et qui sera ensuite distribué à tout client ou serveur devant faire confiance aux certificats qu'elle signe. Ce certificat est "auto-signé", car aucune autorité ne se trouve au-dessus de lui : l'autorité de certification se porte garante d'elle-même. C'est un fonctionnement normal pour une autorité de certification racine. @@ -87,7 +79,7 @@ Ce certificat est "auto-signé", car aucune autorité ne se trouve au-dessus de * `-subj` définit les champs d'identité directement dans la ligne de commande : CN (Common Name) vaut « Test Dev CA », O (Organization) vaut « YourOrganization » et OU (Organizational Unit) vaut « R&D ». Remplacez ces valeurs par celles de votre organisation. ```shell -sudo openssl req -x509 -new -nodes -key /out/CA/rootCA.key \ +sudo openssl req -x509 -new -key /out/CA/rootCA.key \ -sha256 -days 3650 \ -subj "/CN=Test Dev CA/O=YourOrganization/OU=R&D" \ -out /out/CA/rootCA.pem @@ -98,108 +90,141 @@ sudo openssl req -x509 -new -nodes -key /out/CA/rootCA.key \ Il s'agit de la clé privée du serveur lui-même (du serveur central/distant ou de la base de données). Elle est distincte de la clé de l'autorité de certification : le serveur ne doit jamais partager une clé avec l'autorité de certification. - + ```shell -sudo openssl genrsa -out /out/web/server-key.pem 2048 +sudo openssl genrsa -out /out/web/web-key.pem 2048 ``` - + ```shell -sudo openssl genrsa -out /out/db/server-key.pem 2048 +sudo openssl genrsa -out /out/db/db-key.pem 2048 ``` -## Étape 5 : Créer le fichier de configuration des extensions OpenSSL pour les SAN +## Étape 5 : Générer une demande de signature de certificat -Les navigateurs et clients récents exigent qu'un certificat liste tous les noms d'hôte et adresses IP pour lesquels il est valide : c'est la liste SAN (Subject Alternative Name). Un CN seul ne suffit plus pour être considéré comme fiable. Cette étape crée un petit fichier de configuration qui définit : +Une CSR (Certificate Signing Request) est une demande générée à partir de la clé privée du serveur. Elle signifie : « Voici mon identité, merci de me signer ». Elle n'a aucun effet par elle-même. Ce fichier intermédiaire sert uniquement à l'étape 7 (vous pouvez le supprimer ensuite si vous le souhaitez). -* `basicConstraints = CA:FALSE` : ce certificat n'est pas autorisé à signer d'autres certificats (seule l'autorité de certification racine le peut). -* `keyUsage / extendedKeyUsage` : limite le certificat à son usage prévu, c'est-à-dire l'authentification d'un serveur TLS. -* `subjectAltName` : la liste des noms et adresses IP pour lesquels le certificat doit être valide. Ici : web, localhost, db et l'adresse IP 127.0.0.1. Modifiez cette liste pour qu'elle corresponde aux noms d'hôte réels par lesquels votre serveur sera joint. +Remplacez **centreon.example.com** ou **db.example.com** par le FQDN de votre serveur. Utilisez le même nom que la première entrée DNS du fichier **.ext** à l'étape 6. + + + ```shell -sudo tee /out/cert.ext > /dev/null < + + +```shell +sudo openssl req -new -key /out/db/db-key.pem -out /out/db/db.csr \ + -subj "/CN=db.example.com/O=Centreon" ``` -## Étape 6 : Générer une demande de signature de certificat + + + +## Étape 6 : Signer le certificat final avec l'autorité de certification racine (validité de 397 jours) + +C'est cette étape qui produit le certificat serveur utilisable : l'autorité de certification (son certificat et sa clé privée, créés aux étapes 2 et 3) signe la CSR de l'étape 5. -Une CSR (Certificate Signing Request) est une demande générée à partir de la clé privée du serveur. Elle signifie : « Voici mon identité, merci de me signer. » Elle n'a aucun effet par elle-même. Ce fichier intermédiaire sert uniquement à l'étape 7 (vous pouvez le supprimer ensuite si vous le souhaitez). +Créez d'abord un fichier qui définit les extensions du certificat. Les entrées `subjectAltName` doivent correspondre aux noms et adresses IP que les clients utilisent pour joindre le serveur. Sinon, la connexion est refusée. +Remplacez **centreon.example.com** et **192.168.1.10** par le FQDN et l'adresse IP que les utilisateurs et Gorgone utilisent pour accéder à l'interface web : - + ```shell -sudo openssl req -new -key /out/web/server-key.pem -out /out/web/server.csr \ - -subj "/CN=web/O=Centreon" +sudo openssl x509 -req -in /out/web/server.csr \ + -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ + -CAserial /out/CA/rootCA.srl -CAcreateserial \ + -out /out/web/server.pem -days 397 -sha256 \ + -extfile /out/cert.ext -extensions v3_req +``` + +```shell +sudo tee /out/web/web.ext > /dev/null <<'EOF' +[v3_req] +basicConstraints = critical, CA:FALSE +keyUsage = critical, digitalSignature, keyEncipherment +extendedKeyUsage = serverAuth +subjectAltName = @alt_names + +[alt_names] +DNS.1 = centreon.example.com +IP.1 = 192.168.1.10 +EOF ``` - + + +Remplacez **db.example.com** et **192.168.1.20** par le FQDN et l'adresse IP que le serveur central utilise pour se connecter à la base de données. Avec une base de données locale, le serveur central se connecte via **localhost** : conservez donc les entrées `localhost` et `127.0.0.1` : ```shell -sudo openssl req -new -key /out/db/server-key.pem -out /out/db/server.csr \ - -subj "/CN=db/O=Centreon" +sudo tee /out/db/db.ext > /dev/null <<'EOF' +[v3_req] +basicConstraints = critical, CA:FALSE +keyUsage = critical, digitalSignature, keyEncipherment +extendedKeyUsage = serverAuth +subjectAltName = @alt_names + +[alt_names] +DNS.1 = db.example.com +DNS.2 = localhost +IP.1 = 192.168.1.20 +IP.2 = 127.0.0.1 +EOF ``` -## Étape 7 : Signer le certificat final avec l'autorité de certification racine (validité de 397 jours) - -C'est cette étape qui produit le certificat serveur utilisable : l'autorité de certification (son certificat et sa clé privée, créés aux étapes 2 et 3) signe la CSR de l'étape 6, en appliquant les extensions et les SAN définis à l'étape 5. +Puis signez le certificat. La commande utilise les options suivantes : * `-days 397` : 397 jours est la durée de vie maximale actuellement acceptée par les principaux navigateurs (Apple, Google, Mozilla) pour les certificats de serveur TLS. Au-delà, les clients risquent de rejeter le certificat. * `-CAcreateserial` : crée, lors de la première exécution, un fichier de suivi des numéros de série (rootCA.srl), puis l'incrémente à chaque nouvelle signature. Chaque certificat émis par cette autorité de certification reçoit ainsi un numéro de série unique. +* `-extfile` / `-extensions v3_req` : ajoute les extensions définies dans le fichier **.ext**, notamment les noms et adresses IP pour lesquels le certificat est valide (`subjectAltName`). - + ```shell -sudo openssl x509 -req -in /out/web/server.csr \ +sudo openssl x509 -req -in /out/web/web.csr \ -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ -CAserial /out/CA/rootCA.srl -CAcreateserial \ - -out /out/web/server.pem -days 397 -sha256 \ - -extfile /out/cert.ext -extensions v3_req + -out /out/web/web.pem -days 397 -sha256 \ + -extfile /out/web/web.ext -extensions v3_req ``` - + ```shell -sudo openssl x509 -req -in /out/db/server.csr \ +sudo openssl x509 -req -in /out/db/db.csr \ -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ -CAserial /out/CA/rootCA.srl -CAcreateserial \ - -out /out/db/server.pem -days 397 -sha256 \ - -extfile /out/cert.ext -extensions v3_req + -out /out/db/db.pem -days 397 -sha256 \ + -extfile /out/db/db.ext -extensions v3_req ``` -## Étape 8 : Définir les permissions +## Étape 7 : Définir les permissions Les permissions suivent ici le principe du moindre privilège : * `0644` (lecture pour tous, écriture pour le propriétaire uniquement) pour les certificats publics : ils ne contiennent aucun secret. -* `0640` (lecture pour le propriétaire et le groupe, aucun accès pour les autres) pour la clé privée du serveur. Cette clé est sensible, mais un service exécuté sous un groupe spécifique aura probablement besoin de la lire. +* `0640` (lecture pour le propriétaire et le groupe, aucun accès pour les autres) pour la clé privée du serveur. Cette clé est sensible, mais un service exécuté sous un groupe spécifique aura probablement besoin de la lire. La [procédure d'installation](../installation/installation-of-a-central-server/using-packages.md) attribue le bon groupe (par ex. **mysql**) une fois les fichiers copiés. Pour l'autorité de certification racine : @@ -210,15 +235,62 @@ sudo chmod 0644 /out/CA/rootCA.pem Pour le serveur central/distant : ```shell -sudo chmod 0644 /out/web/server.pem -sudo chmod 0640 /out/web/server-key.pem +sudo chmod 0644 /out/web/web.pem +sudo chmod 0640 /out/web/web-key.pem ``` Pour la base de données : ```shell -sudo chmod 0644 /out/db/server.pem -sudo chmod 0640 /out/db/server-key.pem +sudo chmod 0644 /out/db/db.pem +sudo chmod 0640 /out/db/db-key.pem +``` + +Vous disposez maintenant des fichiers nécessaires dans votre dossier **/out**. Vous pouvez les copier aux bons emplacements sur vos serveurs (par ex. **/etc/pki/centreon-tls/** sur EL 9 ou 10 comme dans l'exemple ci-dessous, ou **/etc/ssl/certs/centreon-tls** sur Debian 13). + +Sur le serveur central/distant : + +```shell +sudo mkdir -p /etc/pki/centreon-tls +sudo cp /out/CA/rootCA.pem /out/web/web.pem /out/web/web-key.pem /etc/pki/centreon-tls/ ``` -Les 3 fichiers nécessaires se trouvent maintenant dans votre dossier **/out**. Vous pouvez les copier aux emplacements appropriés sur vos serveurs (et les renommer si besoin). +Pour la base de données : + +* Si votre base de données est locale, exécutez ces commandes sur le serveur central : + + ```shell + sudo mkdir -p /etc/pki/centreon-tls + sudo cp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem /etc/pki/centreon-tls/ + ``` + +* Si votre base de données est distante, créez le dossier sur le serveur de base de données : + + ```shell + sudo mkdir -p /etc/pki/centreon-tls + ``` + + Ensuite, sur le serveur central, copiez les fichiers sur le serveur de base de données à l'aide d'une méthode sécurisée, car **db-key.pem** est une clé privée. Remplacez **db.example.com** par l'adresse de votre serveur de base de données : + + ```shell + sudo scp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem root@db.example.com:/etc/pki/centreon-tls/ + ``` + + Si root ne peut pas se connecter en SSH sur le serveur de base de données, copiez les fichiers dans le dossier personnel d'un utilisateur qui le peut (remplacez **user**) : + + ```shell + sudo scp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem user@db.example.com:~/ + ``` + + Ensuite, sur le serveur de base de données, déplacez-les dans le bon dossier : + + ```shell + sudo mv ~/rootCA.pem ~/db.pem ~/db-key.pem /etc/pki/centreon-tls/ + sudo chown root:root /etc/pki/centreon-tls/*.pem + ``` + + Supprimez ensuite la clé privée du serveur central : + + ```shell + sudo rm /out/db/db-key.pem + ``` diff --git a/versioned_docs/version-26.10/administration/self-signed-certificate.md b/versioned_docs/version-26.10/administration/self-signed-certificate.md index b1a14d11820c..6cbe027bf624 100644 --- a/versioned_docs/version-26.10/administration/self-signed-certificate.md +++ b/versioned_docs/version-26.10/administration/self-signed-certificate.md @@ -10,33 +10,25 @@ import TabItem from '@theme/TabItem'; ## Files you need to set up TLS connections using self-signed certificates -This procedure allows you to create the following files: +This procedure allows you to create the following set of files, which is enough to secure the connection to the web interface and to the database: | File | Where to store it | Role | |--------------|-----------------------------------|-------------------------------------------------------------------------| -| server-key.pem | On the server you want to make secure (central/remote, database...) | Private key for **server.pem**: stays secret on the secure server. Used to prove the server's identity. | -| server.pem | On the server you want to make secure (central/remote, database...) | The signed certificate that will be sent automatically to any client that tries to connect to the secure server. | -| rootCA.pem | On the client (browser, OS...) | Root CA self-signed certificate. This is a public file, used to validate the **server.pem** certificate the client has received. **rootCA.pem** will have to be copied to all machines that will interact with the secure machine (that has sent **server.pem**). | -| rootCA.key | Only on the machine that generates the CA, stays in a temporary folder | This file plays no role in production. It is used only to sign **rootCA.pem** when creating it. | +| web-key.pem | On the central/remote server you want to make secure | Private key for **web.pem**: stays secret on the secure server. Used to prove the server's identity. | +| web.pem | On the central/remote server you want to make secure | The signed certificate that will be sent automatically to any client that tries to connect to the secure central/remote server. | +| db-key.pem | On the database server you want to make secure | Private key for **db.pem**: stays secret on the secure server. Used to prove the server's identity. | +| db.pem | On the database server you want to make secure | The signed certificate that will be sent automatically to any client that tries to connect to the secure database server. | +| rootCA.pem | On the client (browser, OS...) | Root CA self-signed certificate. This is a public file, used to validate the **web.pem** or **db.pem** certificate the client has received. **rootCA.pem** will have to be copied to all machines that will interact with the secure machine (that has sent **web.pem** or **db.pem**). | +| rootCA.key | Store it somewhere safe, so as to be able to renew the certificates. | Private key of the root CA. Used to sign **web.pem** and **db.pem**, and to sign new certificates when they expire (after 397 days). Never copy it to another machine. If you lose it, you have to create a new CA and redeploy **rootCA.pem** everywhere. | ## What this procedure does -The procedure creates the files you need to set up a TLS connection, in temporary folders. When you set up HTTPS on a server, you will need to deploy the necessary files to the correct location. Example: **/etc/pki** is the default location for certificates on EL. Debian's default path is **/etc/ssl/certs**. +The procedure creates the files you need to set up a TLS connection, in temporary folders. When you set up HTTPS on a server, you will need to deploy the necessary files to the correct location (the last step explains where to copy them). The procedure can be run on a Centreon platform that has a local database, or a remote one. * If you have a local database, run the commands in both tabs on your Centreon server. -* If you have a remote database, run the procedure twice: - * On your Centreon server, create a CA (steps 1 to 3), then run the commands in the **On the central/remote server** tabs. - * On the database server, create another CA, then run the commands in the **On the database server** tabs. - - You then have two different **rootCA.pem** files. Copy the **rootCA.pem** from the database server to the machines that connect to the database (for example, your Centreon server). Copy the **rootCA.pem** from your Centreon server to the machines that connect to it. - - +* If you have a remote database, run the whole procedure on your Centreon server (both tabs). The last step explains how to copy **rootCA.pem**, **db.pem** and **db-key.pem** to the database server. ## Step 1: Create output directories @@ -48,17 +40,17 @@ For the CA: sudo mkdir -p /out/CA ``` -For the central/remote server, or for the database: +For each certificate: - + ```shell sudo mkdir -p /out/web ``` - + ```shell sudo mkdir -p /out/db @@ -76,9 +68,9 @@ sudo openssl genrsa -out /out/CA/rootCA.key 4096 sudo chmod 400 /out/CA/rootCA.key ``` -## Step 3: Generate Root CA self-signed certificate (10 years) +## Step 3: Generate the root CA self-signed certificate (10 years) -Now we create the CA's actual certificate — the public document that identifies your CA (name, organization, etc.) and that will later be distributed to any client/server that needs to trust certificates it signs. +This step creates the CA's certificate: the public document that identifies your CA (name, organization, etc.) and that will later be distributed to any client/server that needs to trust certificates it signs. It's "self-signed" because there's no higher authority above it — the CA vouches for itself. This is normal and expected for a root CA. @@ -87,121 +79,144 @@ It's "self-signed" because there's no higher authority above it — the CA vouch * `-subj` sets the identity fields directly on the command line: CN (Common Name) is "Test Dev CA", O (Organization) is "YourOrganization", OU (Organizational Unit) is "R&D". Replace these to fit your organization. ```shell -sudo openssl req -x509 -new -nodes -key /out/CA/rootCA.key \ +sudo openssl req -x509 -new -key /out/CA/rootCA.key \ -sha256 -days 3650 \ -subj "/CN=Test Dev CA/O=YourOrganization/OU=R&D" \ -out /out/CA/rootCA.pem ``` -## Step 4: Generate leaf server private key (2048-bit RSA) +## Step 4: Generate the server private key (2048-bit RSA) This is the private key for the actual server (the central/remote server or the database). It's separate from the CA key. The server should never share a key with the CA. - + ```shell -sudo openssl genrsa -out /out/web/server-key.pem 2048 +sudo openssl genrsa -out /out/web/web-key.pem 2048 ``` - + ```shell -sudo openssl genrsa -out /out/db/server-key.pem 2048 +sudo openssl genrsa -out /out/db/db-key.pem 2048 ``` -## Step 5: Create OpenSSL extension config for SANs +## Step 5: Generate a Certificate Signing Request -Modern browsers and clients require a certificate to list all the hostnames/IPs it's valid for — this is called the Subject Alternative Name (SAN) list. A single CN is no longer trusted alone. This step writes a small config file describing: +A CSR is a request document, generated from the server's private key, that says "here's who I am, please sign me." It doesn't do anything on its own. It's an intermediate file, only useful as input to Step 6 (and can be deleted afterward if you like). -* `basicConstraints = CA:FALSE`: this certificate is not allowed to sign other certificates (only the root CA can). -* `keyUsage / extendedKeyUsage`: restricts the certificate to its intended purpose, which is authenticating a TLS server. -* `subjectAltName`: the actual list of names/IPs the certificate should be valid for. Here: web, localhost, db, and IP 127.0.0.1. Edit this list to match the actual hostnames your server will be reached by. +Replace **centreon.example.com** or **db.example.com** with the FQDN of your server. Use the same name as the first DNS entry of the **.ext** file in Step 6. + + + ```shell -sudo tee /out/cert.ext > /dev/null < + + +```shell +sudo openssl req -new -key /out/db/db-key.pem -out /out/db/db.csr \ + -subj "/CN=db.example.com/O=Centreon" ``` -## Step 6: Generate a Certificate Signing Request + + + +## Step 6: Sign the server certificate with the root CA (397 days validity) -A CSR is a request document, generated from the server's private key, that says "here's who I am, please sign me." It doesn't do anything on its own. It's an intermediate file, only useful as input to Step 7 (and can be deleted afterward if you like). +This is the step that actually produces the usable server certificate: the CA (its certificate and private key from Steps 2–3) signs the CSR from Step 5. +First, create a file that defines the certificate's extensions. The `subjectAltName` entries must match the names and IP addresses that clients use to reach the server. Otherwise, the connection is rejected. - + + +Replace **centreon.example.com** and **192.168.1.10** with the FQDN and IP address that users and Gorgone use to reach the web interface: ```shell -sudo openssl req -new -key /out/web/server-key.pem -out /out/web/server.csr \ - -subj "/CN=web/O=Centreon" +sudo tee /out/web/web.ext > /dev/null <<'EOF' +[v3_req] +basicConstraints = critical, CA:FALSE +keyUsage = critical, digitalSignature, keyEncipherment +extendedKeyUsage = serverAuth +subjectAltName = @alt_names + +[alt_names] +DNS.1 = centreon.example.com +IP.1 = 192.168.1.10 +EOF ``` - + + +Replace **db.example.com** and **192.168.1.20** with the FQDN and IP address that the central server uses to connect to the database. With a local database, the central server connects through **localhost**, so keep the `localhost` and `127.0.0.1` entries: ```shell -sudo openssl req -new -key /out/db/server-key.pem -out /out/db/server.csr \ - -subj "/CN=db/O=Centreon" +sudo tee /out/db/db.ext > /dev/null <<'EOF' +[v3_req] +basicConstraints = critical, CA:FALSE +keyUsage = critical, digitalSignature, keyEncipherment +extendedKeyUsage = serverAuth +subjectAltName = @alt_names + +[alt_names] +DNS.1 = db.example.com +DNS.2 = localhost +IP.1 = 192.168.1.20 +IP.2 = 127.0.0.1 +EOF ``` -## Step 7: Sign leaf cert with Root CA (397 days validity) - -This is the step that actually produces the usable server certificate: the CA (its cert + private key from Steps 2–3) signs the CSR from Step 6, applying the extensions/SANs defined in Step 5. +Then sign the certificate. The command uses the following options: * `-days 397`: 397 days is the current maximum lifetime accepted by major browsers (Apple/Google/Mozilla) for TLS server certificates. Going longer risks clients rejecting the certificate. * `-CAcreateserial`: creates a serial number tracking file (rootCA.srl) the first time it runs, and increments it on future signings, so every certificate issued by this CA gets a unique serial number. - - +* `-extfile` / `-extensions v3_req`: adds the extensions defined in the **.ext** file, including the names and IP addresses the certificate is valid for (`subjectAltName`). - + ```shell -sudo openssl x509 -req -in /out/web/server.csr \ +sudo openssl x509 -req -in /out/web/web.csr \ -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ -CAserial /out/CA/rootCA.srl -CAcreateserial \ - -out /out/web/server.pem -days 397 -sha256 \ - -extfile /out/cert.ext -extensions v3_req + -out /out/web/web.pem -days 397 -sha256 \ + -extfile /out/web/web.ext -extensions v3_req ``` - + ```shell -sudo openssl x509 -req -in /out/db/server.csr \ +sudo openssl x509 -req -in /out/db/db.csr \ -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ -CAserial /out/CA/rootCA.srl -CAcreateserial \ - -out /out/db/server.pem -days 397 -sha256 \ - -extfile /out/cert.ext -extensions v3_req + -out /out/db/db.pem -days 397 -sha256 \ + -extfile /out/db/db.ext -extensions v3_req ``` -## Step 8: Set permissions +## Step 7: Set permissions Permissions here follow the principle of least privilege: * `0644` (readable by everyone, writable only by owner) for public certificates — they contain no secrets. -* `0640` (readable by owner and group, not others) for the server's private key, since it's sensitive but likely needs to be read by a service running under a specific group. +* `0640` (readable by owner and group, not others) for the server's private key, since it's sensitive but likely needs to be read by a service running under a specific group. The [installation procedure](../installation/installation-of-a-central-server/using-packages.md) sets the correct group (e.g. **mysql**) once the files are copied. For the root CA: @@ -212,15 +227,62 @@ sudo chmod 0644 /out/CA/rootCA.pem For the central/remote server: ```shell -sudo chmod 0644 /out/web/server.pem -sudo chmod 0640 /out/web/server-key.pem +sudo chmod 0644 /out/web/web.pem +sudo chmod 0640 /out/web/web-key.pem ``` For the database: ```shell -sudo chmod 0644 /out/db/server.pem -sudo chmod 0640 /out/db/server-key.pem +sudo chmod 0644 /out/db/db.pem +sudo chmod 0640 /out/db/db-key.pem ``` -You now have the files you need in your **/out** folder. You can copy them to the correct locations on your servers (and rename them if you need to). +You now have the files you need in your **/out** folder. You can copy them to the correct locations on your servers (e.g. **/etc/pki/centreon-tls/** on EL 9 or 10 like in the example below, or **/etc/ssl/certs/centreon-tls** on Debian 13). + +On the central/remote server: + +```shell +sudo mkdir -p /etc/pki/centreon-tls +sudo cp /out/CA/rootCA.pem /out/web/web.pem /out/web/web-key.pem /etc/pki/centreon-tls/ +``` + +For the database: + +* If your database is local, run these commands on the central server: + + ```shell + sudo mkdir -p /etc/pki/centreon-tls + sudo cp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem /etc/pki/centreon-tls/ + ``` + +* If your database is remote, create the folder on the database server: + + ```shell + sudo mkdir -p /etc/pki/centreon-tls + ``` + + Then, on the central server, copy the files to the database server using a secure method, as **db-key.pem** is a private key. Replace **db.example.com** with the address of your database server: + + ```shell + sudo scp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem root@db.example.com:/etc/pki/centreon-tls/ + ``` + + If root cannot log in through SSH on the database server, copy the files to the home folder of a user who can (replace **user**): + + ```shell + sudo scp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem user@db.example.com:~/ + ``` + + Then, on the database server, move them to the right folder: + + ```shell + sudo mv ~/rootCA.pem ~/db.pem ~/db-key.pem /etc/pki/centreon-tls/ + sudo chown root:root /etc/pki/centreon-tls/*.pem + ``` + + Then delete the private key from the central server: + + ```shell + sudo rm /out/db/db-key.pem + ``` From 4411293c8e29ecd381c863082581f0ab26caebb2 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 13 Oct 2026 16:42:25 +0200 Subject: [PATCH 136/179] Fixes --- .../administration/self-signed-certificate.md | 24 +++++++------------ 1 file changed, 9 insertions(+), 15 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md index f3e8a29f336e..3edb7a87f553 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md @@ -18,12 +18,12 @@ Cette procédure vous permet de créer l'ensemble de fichiers suivant, qui suffi | web.pem | Sur le serveur central/distant à sécuriser | Le certificat signé qui sera envoyé automatiquement à tout client tentant de se connecter au serveur central/distant sécurisé. | | db-key.pem | Sur le serveur de base de données à sécuriser | Clé privée de **db.pem** : reste secrète sur le serveur sécurisé. Sert à prouver l'identité du serveur. | | db.pem | Sur le serveur de base de données à sécuriser | Le certificat signé qui sera envoyé automatiquement à tout client tentant de se connecter au serveur de base de données sécurisé. | -| rootCA.pem | Sur le client (navigateur, OS...) | Certificat auto-signé de l'autorité de certification racine. Il s'agit d'un fichier public, qui sert à valider le certificat **web.pem** ou **db.pem** reçu par le client. **rootCA.pem** devra être copié sur toutes les machines qui interagiront avec la machine sécurisée (celle qui a envoyé **web.pem** ou **db.pem**). | -| rootCA.key | À conserver en lieu sûr, afin de pouvoir renouveler les certificats. | Clé privée de l'autorité de certification racine. Sert à signer **web.pem** et **db.pem**, ainsi qu'à signer de nouveaux certificats lorsqu'ils expirent (au bout de 397 jours). Ne la copiez jamais sur une autre machine. Si vous la perdez, vous devrez créer une nouvelle CA et redéployer **rootCA.pem** partout. | +| rootCA.pem | Sur le client (navigateur, OS...) | Certificat auto-signé de l'autorité de certification racine. Il s'agit d'un fichier public, qui sert à valider le certificat **web.pem** ou **db.pem** reçu par le client. **rootCA.pem** devra être copié sur toutes les machines qui se connecteront à la machine sécurisée (celle qui a envoyé **web.pem** ou **db.pem**). | +| rootCA.key | À conserver en lieu sûr, afin de pouvoir renouveler les certificats. | Clé privée de l'autorité de certification racine. Sert à signer **web.pem** et **db.pem**, ainsi qu'à signer de nouveaux certificats lorsqu'ils expirent (au bout de 397 jours). Ne la copiez jamais sur une autre machine. Si vous la perdez, vous devrez créer une nouvelle autorité de certification et redéployer **rootCA.pem** partout. | ## Ce que fait cette procédure -La procédure crée les fichiers nécessaires à la mise en place d'une connexion TLS, dans des dossiers temporaires. Lorsque vous configurez HTTPS sur un serveur, vous devez déployer les fichiers nécessaires au bon emplacement (la dernière étape explique où les copier). +La procédure crée les fichiers nécessaires à la mise en place d'une connexion TLS, dans des répertoires temporaires. Lorsque vous configurez HTTPS sur un serveur, vous devez déployer les fichiers nécessaires au bon emplacement (la dernière étape explique où les copier). La procédure peut être exécutée sur une plateforme Centreon disposant d'une base de données locale ou distante. @@ -32,7 +32,7 @@ La procédure peut être exécutée sur une plateforme Centreon disposant d'une ## Étape 1 : Créer les répertoires de sortie -Créez des dossiers pour organiser les fichiers : un pour les fichiers propres à l'autorité de certification, un pour les fichiers destinés au service web ou au service de base de données. +Créez des répertoires pour organiser les fichiers : un pour les fichiers propres à l'autorité de certification, un pour les fichiers destinés au service web ou au service de base de données. Pour l'autorité de certification : @@ -85,7 +85,7 @@ sudo openssl req -x509 -new -key /out/CA/rootCA.key \ -out /out/CA/rootCA.pem ``` -## Étape 4 : Générer la clé privée du serveur final (RSA 2048 bits) +## Étape 4 : Générer la clé privée du serveur (RSA 2048 bits) Il s'agit de la clé privée du serveur lui-même (du serveur central/distant ou de la base de données). Elle est distincte de la clé de l'autorité de certification : le serveur ne doit jamais partager une clé avec l'autorité de certification. @@ -108,7 +108,7 @@ sudo openssl genrsa -out /out/db/db-key.pem 2048 ## Étape 5 : Générer une demande de signature de certificat -Une CSR (Certificate Signing Request) est une demande générée à partir de la clé privée du serveur. Elle signifie : « Voici mon identité, merci de me signer ». Elle n'a aucun effet par elle-même. Ce fichier intermédiaire sert uniquement à l'étape 7 (vous pouvez le supprimer ensuite si vous le souhaitez). +Une CSR (Certificate Signing Request) est une demande générée à partir de la clé privée du serveur. Elle signifie : « Voici mon identité, merci de me signer ». Elle n'a aucun effet par elle-même. Ce fichier intermédiaire sert uniquement à l'étape 6 (vous pouvez le supprimer ensuite si vous le souhaitez). Remplacez **centreon.example.com** ou **db.example.com** par le FQDN de votre serveur. Utilisez le même nom que la première entrée DNS du fichier **.ext** à l'étape 6. @@ -131,9 +131,9 @@ sudo openssl req -new -key /out/db/db-key.pem -out /out/db/db.csr \ -## Étape 6 : Signer le certificat final avec l'autorité de certification racine (validité de 397 jours) +## Étape 6 : Signer le certificat du serveur avec l'autorité de certification racine (validité de 397 jours) -C'est cette étape qui produit le certificat serveur utilisable : l'autorité de certification (son certificat et sa clé privée, créés aux étapes 2 et 3) signe la CSR de l'étape 5. +C'est cette étape qui produit le certificat du serveur utilisable : l'autorité de certification (son certificat et sa clé privée, créés aux étapes 2 et 3) signe la CSR de l'étape 5. Créez d'abord un fichier qui définit les extensions du certificat. Les entrées `subjectAltName` doivent correspondre aux noms et adresses IP que les clients utilisent pour joindre le serveur. Sinon, la connexion est refusée. @@ -142,13 +142,7 @@ Remplacez **centreon.example.com** et **192.168.1.10** par le FQDN et l'adresse -```shell -sudo openssl x509 -req -in /out/web/server.csr \ - -CA /out/CA/rootCA.pem -CAkey /out/CA/rootCA.key \ - -CAserial /out/CA/rootCA.srl -CAcreateserial \ - -out /out/web/server.pem -days 397 -sha256 \ - -extfile /out/cert.ext -extensions v3_req -``` +Remplacez **db.example.com** et **192.168.1.20** par le FQDN et l'adresse IP que le serveur central utilise pour se connecter à la base de données. Avec une base de données locale, le serveur central se connecte via **localhost** : conservez donc les entrées `localhost` et `127.0.0.1` : ```shell sudo tee /out/web/web.ext > /dev/null <<'EOF' From 49eab4db02cd78d50bd7a1063c88f06868e73f8f Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 13 Oct 2026 16:47:10 +0200 Subject: [PATCH 137/179] Fixes --- .../version-26.10/administration/self-signed-certificate.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md index 3edb7a87f553..1f648f858131 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md @@ -137,12 +137,10 @@ C'est cette étape qui produit le certificat du serveur utilisable : l'autorité Créez d'abord un fichier qui définit les extensions du certificat. Les entrées `subjectAltName` doivent correspondre aux noms et adresses IP que les clients utilisent pour joindre le serveur. Sinon, la connexion est refusée. -Remplacez **centreon.example.com** et **192.168.1.10** par le FQDN et l'adresse IP que les utilisateurs et Gorgone utilisent pour accéder à l'interface web : - -Remplacez **db.example.com** et **192.168.1.20** par le FQDN et l'adresse IP que le serveur central utilise pour se connecter à la base de données. Avec une base de données locale, le serveur central se connecte via **localhost** : conservez donc les entrées `localhost` et `127.0.0.1` : +Remplacez **centreon.example.com** et **192.168.1.10** par le FQDN et l'adresse IP que les utilisateurs et Gorgone utilisent pour accéder à l'interface web : ```shell sudo tee /out/web/web.ext > /dev/null <<'EOF' From 925e48dd6bfe4124abefa83b2cdddaefdf9b65fe Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Tue, 13 Oct 2026 18:01:29 +0200 Subject: [PATCH 138/179] Fixes --- .../installation/_database-configuration.mdx | 4 +- .../installation/_database-tls-conf.mdx | 68 ++++++++---------- .../installation/_interface-tls-conf.mdx | 38 +++++----- .../installation/_tls-certificates.mdx | 6 +- .../installation/_database-configuration.mdx | 6 +- .../installation/_database-local-install.mdx | 4 +- .../installation/_database-tls-conf.mdx | 70 +++++++++---------- .../installation/_interface-tls-conf.mdx | 38 +++++----- .../installation/_tls-certificates.mdx | 13 ++-- 9 files changed, 116 insertions(+), 131 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx index 6f81d7e78181..173d4cb13704 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-configuration.mdx @@ -1,9 +1,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -> Il est obligatoire de définir un mot de passe pour l'utilisateur root de la base de données. - -Vous devez obligatoirement définir un mot de passe pour l'utilisateur root de la base de données (vous aurez besoin de ce mot de passe lors de l'[installation web](web-and-post-installation.md)). +> Vous devez obligatoirement définir un mot de passe pour l'utilisateur root de la base de données (vous aurez besoin de ce mot de passe lors de l'[installation web](web-and-post-installation.md)). diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx index b60417b4ed99..9b39caaaee8a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx @@ -16,8 +16,8 @@ Cette section décrit comment mettre en place une connexion TLS entre le serveur cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' [mariadb] ssl_ca = /etc/pki/centreon-tls/rootCA.pem -ssl_cert = /etc/pki/centreon-tls/server.pem -ssl_key = /etc/pki/centreon-tls/server-key.pem +ssl_cert = /etc/pki/centreon-tls/db.pem +ssl_key = /etc/pki/centreon-tls/db-key.pem require_secure_transport = OFF tls_version = TLSv1.2,TLSv1.3 EOF @@ -26,8 +26,8 @@ EOF 2. Attribuez les permissions suivantes à la clé afin qu'elle soit lisible uniquement par l'utilisateur **mysql** : ```shell -chown root:mysql /etc/pki/centreon-tls/server-key.pem -chmod 0640 /etc/pki/centreon-tls/server-key.pem +chown root:mysql /etc/pki/centreon-tls/db-key.pem +chmod 0640 /etc/pki/centreon-tls/db-key.pem ``` 3. Configurez le client MariaDB en ligne de commande pour qu'il utilise TLS (vous en aurez besoin par la suite). @@ -88,8 +88,8 @@ done cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' [mariadb] ssl_ca = /etc/pki/centreon-tls/rootCA.pem -ssl_cert = /etc/pki/centreon-tls/server.pem -ssl_key = /etc/pki/centreon-tls/server-key.pem +ssl_cert = /etc/pki/centreon-tls/db.pem +ssl_key = /etc/pki/centreon-tls/db-key.pem require_secure_transport = OFF tls_version = TLSv1.2,TLSv1.3 EOF @@ -98,8 +98,8 @@ EOF 2. Attribuez les permissions suivantes à la clé afin qu'elle soit lisible uniquement par l'utilisateur **mysql** : ```shell -chown root:mysql /etc/pki/centreon-tls/server-key.pem -chmod 0640 /etc/pki/centreon-tls/server-key.pem +chown root:mysql /etc/pki/centreon-tls/db-key.pem +chmod 0640 /etc/pki/centreon-tls/db-key.pem ``` 3. Configurez le client MariaDB en ligne de commande pour qu'il utilise TLS (vous en aurez besoin par la suite). @@ -120,13 +120,7 @@ systemctl enable --now mariadb systemctl restart mariadb ``` -5. Sécurisez l'installation : - -```shell -mariadb-secure-installation -``` - -6. Vérifiez que le serveur utilise bien les certificats que vous avez définis, et non ceux qu'il génère automatiquement à son démarrage. +5. Vérifiez que le serveur utilise bien les certificats que vous avez définis, et non ceux qu'il génère automatiquement à son démarrage. ```shell mariadb -e "SHOW GLOBAL VARIABLES WHERE Variable_name IN ('have_ssl','ssl_ca','ssl_cert','ssl_key');" @@ -138,7 +132,7 @@ Le résultat attendu est le suivant : have_ssl YES and ssl_ca /etc/pki/centreon-tls/rootCA.pem ``` -7. Définissez les variables d'environnement que PHP utilisera pour communiquer avec la base de données en mode TLS. +6. Définissez les variables d'environnement que PHP utilisera pour communiquer avec la base de données en mode TLS. ```shell for f in /etc/centreon/.env /usr/share/centreon/.env; do @@ -159,11 +153,11 @@ done ```shell install -d -o root -g mysql -m 0750 /etc/mysql/centreon-tls cp /etc/pki/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem -cp /etc/pki/centreon-tls/server.pem /etc/mysql/centreon-tls/server.pem -cp /etc/pki/centreon-tls/server-key.pem /etc/mysql/centreon-tls/server-key.pem +cp /etc/pki/centreon-tls/db.pem /etc/mysql/centreon-tls/db.pem +cp /etc/pki/centreon-tls/db-key.pem /etc/mysql/centreon-tls/db-key.pem chown root:mysql /etc/mysql/centreon-tls/*.pem -chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/server.pem -chmod 0640 /etc/mysql/centreon-tls/server-key.pem +chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/db.pem +chmod 0640 /etc/mysql/centreon-tls/db-key.pem ``` 2. Configurez le service de base de données pour qu'il démarre en mode TLS et indiquez l'emplacement des certificats. @@ -176,8 +170,8 @@ for d in "${inc[@]}"; do cat > "$d/99-centreon-tls.cnf" <<'EOF' [mysqld] ssl_ca = /etc/mysql/centreon-tls/rootCA.pem -ssl_cert = /etc/mysql/centreon-tls/server.pem -ssl_key = /etc/mysql/centreon-tls/server-key.pem +ssl_cert = /etc/mysql/centreon-tls/db.pem +ssl_key = /etc/mysql/centreon-tls/db-key.pem require_secure_transport = OFF tls_version = TLSv1.2,TLSv1.3 EOF @@ -245,8 +239,8 @@ done cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' [mysqld] ssl_ca = /etc/pki/centreon-tls/rootCA.pem -ssl_cert = /etc/pki/centreon-tls/server.pem -ssl_key = /etc/pki/centreon-tls/server-key.pem +ssl_cert = /etc/pki/centreon-tls/db.pem +ssl_key = /etc/pki/centreon-tls/db-key.pem require_secure_transport = OFF tls_version = TLSv1.2,TLSv1.3 EOF @@ -255,8 +249,8 @@ EOF 2. Attribuez les permissions suivantes à la clé afin qu'elle soit lisible uniquement par l'utilisateur **mysql** : ```shell -chown root:mysql /etc/pki/centreon-tls/server-key.pem -chmod 0640 /etc/pki/centreon-tls/server-key.pem +chown root:mysql /etc/pki/centreon-tls/db-key.pem +chmod 0640 /etc/pki/centreon-tls/db-key.pem ``` 3. Configurez le client MySQL en ligne de commande pour qu'il utilise TLS (vous en aurez besoin par la suite). @@ -294,7 +288,7 @@ Current_tls_ca /etc/pki/centreon-tls/rootCA.pem 6. Sécurisez l'installation (dans la commande suivante, remplacez **my_password** par votre propre mot de passe). Définissez le mot de passe de votre choix : ```shell -db_root_password='ChangeMeStrong#2026' +db_root_password='my_password' mysql_root_auth=(--ssl-mode=DISABLED -u root) if ! mysql --ssl-mode=DISABLED -u root -e "SELECT 1" >/dev/null 2>&1; then mysql_temp_pw=$(grep 'temporary password is generated for root@localhost' /var/log/mysqld.log \ @@ -370,8 +364,8 @@ done cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' [mysqld] ssl_ca = /etc/pki/centreon-tls/rootCA.pem -ssl_cert = /etc/pki/centreon-tls/server.pem -ssl_key = /etc/pki/centreon-tls/server-key.pem +ssl_cert = /etc/pki/centreon-tls/db.pem +ssl_key = /etc/pki/centreon-tls/db-key.pem require_secure_transport = OFF tls_version = TLSv1.2,TLSv1.3 EOF @@ -380,8 +374,8 @@ EOF 2. Attribuez les permissions suivantes à la clé afin qu'elle soit lisible uniquement par l'utilisateur **mysql** : ```shell -chown root:mysql /etc/pki/centreon-tls/server-key.pem -chmod 0640 /etc/pki/centreon-tls/server-key.pem +chown root:mysql /etc/pki/centreon-tls/db-key.pem +chmod 0640 /etc/pki/centreon-tls/db-key.pem ``` 3. Configurez le client MySQL en ligne de commande pour qu'il utilise TLS (vous en aurez besoin par la suite). @@ -494,11 +488,11 @@ done ```shell install -d -o root -g mysql -m 0750 /etc/mysql/centreon-tls cp /etc/pki/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem -cp /etc/pki/centreon-tls/server.pem /etc/mysql/centreon-tls/server.pem -cp /etc/pki/centreon-tls/server-key.pem /etc/mysql/centreon-tls/server-key.pem +cp /etc/pki/centreon-tls/db.pem /etc/mysql/centreon-tls/db.pem +cp /etc/pki/centreon-tls/db-key.pem /etc/mysql/centreon-tls/db-key.pem chown root:mysql /etc/mysql/centreon-tls/*.pem -chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/server.pem -chmod 0640 /etc/mysql/centreon-tls/server-key.pem +chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/db.pem +chmod 0640 /etc/mysql/centreon-tls/db-key.pem ``` 2. Configurez le service de base de données pour qu'il démarre en mode TLS et indiquez l'emplacement des certificats. @@ -511,8 +505,8 @@ for d in "${inc[@]}"; do cat > "$d/99-centreon-tls.cnf" <<'EOF' [mysqld] ssl_ca = /etc/mysql/centreon-tls/rootCA.pem -ssl_cert = /etc/mysql/centreon-tls/server.pem -ssl_key = /etc/mysql/centreon-tls/server-key.pem +ssl_cert = /etc/mysql/centreon-tls/db.pem +ssl_key = /etc/mysql/centreon-tls/db-key.pem require_secure_transport = OFF tls_version = TLSv1.2,TLSv1.3 EOF diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx index a351748da694..e6177a289b8d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx @@ -14,8 +14,8 @@ echo 'Listen 443 https' > /etc/httpd/conf.d/ssl.conf 2. Renseignez les chemins des certificats dans la configuration HTTPS d'Apache pour Centreon : ```shell -sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ - -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/web.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/web-key.pem|g' \ /usr/share/centreon/examples/centreon-apache-https.conf \ > /etc/httpd/conf.d/00-centreon-tls.conf ``` @@ -39,8 +39,8 @@ echo 'Listen 443 https' > /etc/httpd/conf.d/ssl.conf 2. Renseignez les chemins des certificats dans la configuration HTTPS d'Apache pour Centreon : ```shell -sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ - -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/web.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/web-key.pem|g' \ /usr/share/centreon/examples/centreon-apache-https.conf \ > /etc/httpd/conf.d/00-centreon-tls.conf ``` @@ -73,26 +73,26 @@ systemctl restart mysqld -Activez tous les modules référencés par la configuration HTTPS officielle de Centreon : +1. Activez tous les modules référencés par la configuration HTTPS officielle de Centreon : -```shell -a2enmod ssl proxy proxy_fcgi headers deflate rewrite -``` + ```shell + a2enmod ssl proxy proxy_fcgi headers deflate rewrite + ``` -Renseignez les chemins des certificats dans la configuration HTTPS d'Apache pour Centreon : +2. Renseignez les chemins des certificats dans la configuration HTTPS d'Apache pour Centreon : -```shell -sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ - -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ - /usr/share/centreon/examples/centreon-apache-https.conf \ - > /etc/apache2/sites-available/00-centreon-tls.conf -``` + ```shell + sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/web.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/web-key.pem|g' \ + /usr/share/centreon/examples/centreon-apache-https.conf \ + > /etc/apache2/sites-available/00-centreon-tls.conf + ``` -Activez la configuration que vous venez d'appliquer. +3. Activez la configuration que vous venez d'appliquer. -```shell -a2ensite 00-centreon-tls -``` + ```shell + a2ensite 00-centreon-tls + ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx index 557cea715140..d76c597ee6ee 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx @@ -5,11 +5,11 @@ Utilisez un certificat délivré par une autorité de confiance. Les certificats * Si vous disposez déjà d'un certificat validé par une autorité, passez à l'étape suivante. * Si vous ne disposez pas d'un certificat validé par une autorité, vous pouvez en générer un sur des plateformes telles que [Let's Encrypt](https://letsencrypt.org/). -- Si, à des fins de test, vous souhaitez utiliser un certificat auto-signé, [vous pouvez suivre cett procédure pour en créer un](../administration/self-signed-certificate.md) avant d'activer le mode HTTPS sur votre serveur. Attention, vous devrez importer le certificat de l'autorité de certification (CA) dans votre navigateur. +* Si, à des fins de test, vous souhaitez utiliser un certificat auto-signé, [vous pouvez suivre cett procédure pour en créer un](../administration/self-signed-certificate.md) avant d'activer le mode HTTPS sur votre serveur. Attention, vous devrez importer le certificat de l'autorité de certification (CA) dans votre navigateur. -Supposons que vous disposiez des fichiers suivants dans **/etc/pki/centreon-tls/** : +Supposons que vous disposiez des fichiers suivants (dans notre exemple, dans **/etc/pki/centreon-tls/**) : - * rootCA.pem (public) + * rootCA.pem (public - non nécessaire si vous utilisez un certificat reconnu) * server.pem (certificat du serveur) * server-key.pem (clé privée du serveur) * CA/rootCA.\{key,pem\} (définissez les permissions suivantes : root:root, mode 0400) diff --git a/versioned_docs/version-26.10/installation/_database-configuration.mdx b/versioned_docs/version-26.10/installation/_database-configuration.mdx index f9c226666d0d..74d2ec404bd1 100644 --- a/versioned_docs/version-26.10/installation/_database-configuration.mdx +++ b/versioned_docs/version-26.10/installation/_database-configuration.mdx @@ -1,9 +1,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -> It is mandatory to set a password for the root user of the database. - -It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](web-and-post-installation.md)). +> It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](web-and-post-installation.md)). @@ -23,7 +21,7 @@ Retrieve the temporary password created by MySQL: grep 'temporary password' /var/log/mysqld.log ``` -Then change it when prompted by the following command (the password must have at least 8 characaters, upper and lower case, a digit and a special character): +Then change it when prompted by the following command (the password must have at least 8 characters, upper and lower case, a digit and a special character): ```shell mysql_secure_installation diff --git a/versioned_docs/version-26.10/installation/_database-local-install.mdx b/versioned_docs/version-26.10/installation/_database-local-install.mdx index 5c78b8698027..6f41e971a909 100644 --- a/versioned_docs/version-26.10/installation/_database-local-install.mdx +++ b/versioned_docs/version-26.10/installation/_database-local-install.mdx @@ -68,7 +68,7 @@ systemctl daemon-reload systemctl restart mysqld ``` -It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](web-and-post-installation.md)). It must have at least 8 characaters, upper and lower case, a digit and a special character. Retrieve the temporary password created by MySQL: +It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](web-and-post-installation.md)). It must have at least 8 characters, upper and lower case, a digit and a special character. Retrieve the temporary password created by MySQL: ```shell grep 'temporary password' /var/log/mysqld.log @@ -91,7 +91,7 @@ grep -q '^!includedir /etc/my.cnf.d' /etc/my.cnf || echo '!includedir /etc/my.cn systemctl start mysqld ``` -It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](web-and-post-installation.md)). It must have at least 8 characaters, upper and lower case, a digit and a special character. Retrieve the temporary password created by MySQL: +It is mandatory to set a password for the root user of the database (you will need this password during the [web installation](web-and-post-installation.md)). It must have at least 8 characters, upper and lower case, a digit and a special character. Retrieve the temporary password created by MySQL: ```shell grep 'temporary password' /var/log/mysqld.log diff --git a/versioned_docs/version-26.10/installation/_database-tls-conf.mdx b/versioned_docs/version-26.10/installation/_database-tls-conf.mdx index 9b1d6f898fc3..e4ea8767d6d4 100644 --- a/versioned_docs/version-26.10/installation/_database-tls-conf.mdx +++ b/versioned_docs/version-26.10/installation/_database-tls-conf.mdx @@ -16,8 +16,8 @@ This section describes how to set up a TLS connection between the central server cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' [mariadb] ssl_ca = /etc/pki/centreon-tls/rootCA.pem -ssl_cert = /etc/pki/centreon-tls/server.pem -ssl_key = /etc/pki/centreon-tls/server-key.pem +ssl_cert = /etc/pki/centreon-tls/db.pem +ssl_key = /etc/pki/centreon-tls/db-key.pem require_secure_transport = OFF tls_version = TLSv1.2,TLSv1.3 EOF @@ -26,8 +26,8 @@ EOF 2. Give the following permissions on the key so that it is readable by the **mysql** user only: ```shell -chown root:mysql /etc/pki/centreon-tls/server-key.pem -chmod 0640 /etc/pki/centreon-tls/server-key.pem +chown root:mysql /etc/pki/centreon-tls/db-key.pem +chmod 0640 /etc/pki/centreon-tls/db-key.pem ``` 3. Configure MariaDB CLI to use TLS (you will need it later). @@ -88,8 +88,8 @@ done cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' [mariadb] ssl_ca = /etc/pki/centreon-tls/rootCA.pem -ssl_cert = /etc/pki/centreon-tls/server.pem -ssl_key = /etc/pki/centreon-tls/server-key.pem +ssl_cert = /etc/pki/centreon-tls/db.pem +ssl_key = /etc/pki/centreon-tls/db-key.pem require_secure_transport = OFF tls_version = TLSv1.2,TLSv1.3 EOF @@ -98,8 +98,8 @@ EOF 2. Give the following permissions on the key so that it is readable by the **mysql** user only: ```shell -chown root:mysql /etc/pki/centreon-tls/server-key.pem -chmod 0640 /etc/pki/centreon-tls/server-key.pem +chown root:mysql /etc/pki/centreon-tls/db-key.pem +chmod 0640 /etc/pki/centreon-tls/db-key.pem ``` 3. Configure MariaDB CLI to use TLS (you will need it later). @@ -120,13 +120,7 @@ systemctl enable --now mariadb systemctl restart mariadb ``` -5. Secure the installation by defining a password for the database root account: - -```shell -mariadb-secure-installation -``` - -6. Check that the server is using the certificates you defined (not the certificates it generates automatically when it starts). +5. Check that the server is using the certificates you defined (not the certificates it generates automatically when it starts). ```shell mariadb -e "SHOW GLOBAL VARIABLES WHERE Variable_name IN ('have_ssl','ssl_ca','ssl_cert','ssl_key');" @@ -138,7 +132,7 @@ The expected result is: have_ssl YES and ssl_ca /etc/pki/centreon-tls/rootCA.pem ``` -7. Set the environment variables that will be used by PHP to communicate with the database in TLS mode. +6. Set the environment variables that will be used by PHP to communicate with the database in TLS mode. ```shell for f in /etc/centreon/.env /usr/share/centreon/.env; do @@ -159,11 +153,11 @@ done ```shell install -d -o root -g mysql -m 0750 /etc/mysql/centreon-tls cp /etc/pki/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem -cp /etc/pki/centreon-tls/server.pem /etc/mysql/centreon-tls/server.pem -cp /etc/pki/centreon-tls/server-key.pem /etc/mysql/centreon-tls/server-key.pem +cp /etc/pki/centreon-tls/db.pem /etc/mysql/centreon-tls/db.pem +cp /etc/pki/centreon-tls/db-key.pem /etc/mysql/centreon-tls/db-key.pem chown root:mysql /etc/mysql/centreon-tls/*.pem -chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/server.pem -chmod 0640 /etc/mysql/centreon-tls/server-key.pem +chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/db.pem +chmod 0640 /etc/mysql/centreon-tls/db-key.pem ``` 2. Configure the database service to start in TLS mode and specify the certificate locations. @@ -176,8 +170,8 @@ for d in "${inc[@]}"; do cat > "$d/99-centreon-tls.cnf" <<'EOF' [mysqld] ssl_ca = /etc/mysql/centreon-tls/rootCA.pem -ssl_cert = /etc/mysql/centreon-tls/server.pem -ssl_key = /etc/mysql/centreon-tls/server-key.pem +ssl_cert = /etc/mysql/centreon-tls/db.pem +ssl_key = /etc/mysql/centreon-tls/db-key.pem require_secure_transport = OFF tls_version = TLSv1.2,TLSv1.3 EOF @@ -245,8 +239,8 @@ done cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' [mysqld] ssl_ca = /etc/pki/centreon-tls/rootCA.pem -ssl_cert = /etc/pki/centreon-tls/server.pem -ssl_key = /etc/pki/centreon-tls/server-key.pem +ssl_cert = /etc/pki/centreon-tls/db.pem +ssl_key = /etc/pki/centreon-tls/db-key.pem require_secure_transport = OFF tls_version = TLSv1.2,TLSv1.3 EOF @@ -255,8 +249,8 @@ EOF 2. Give the following permissions on the key so that it is readable by the **mysql** user only: ```shell -chown root:mysql /etc/pki/centreon-tls/server-key.pem -chmod 0640 /etc/pki/centreon-tls/server-key.pem +chown root:mysql /etc/pki/centreon-tls/db-key.pem +chmod 0640 /etc/pki/centreon-tls/db-key.pem ``` 3. Configure MySQL CLI to use TLS (you will need it later). @@ -294,7 +288,7 @@ Current_tls_ca /etc/pki/centreon-tls/rootCA.pem 6. Secure the installation (replace **my_password** by your own in the following command). Define the password you want: ```shell -db_root_password='ChangeMeStrong#2026' +db_root_password='my_password' mysql_root_auth=(--ssl-mode=DISABLED -u root) if ! mysql --ssl-mode=DISABLED -u root -e "SELECT 1" >/dev/null 2>&1; then mysql_temp_pw=$(grep 'temporary password is generated for root@localhost' /var/log/mysqld.log \ @@ -370,8 +364,8 @@ done cat > /etc/my.cnf.d/centreon-tls.cnf <<'EOF' [mysqld] ssl_ca = /etc/pki/centreon-tls/rootCA.pem -ssl_cert = /etc/pki/centreon-tls/server.pem -ssl_key = /etc/pki/centreon-tls/server-key.pem +ssl_cert = /etc/pki/centreon-tls/db.pem +ssl_key = /etc/pki/centreon-tls/db-key.pem require_secure_transport = OFF tls_version = TLSv1.2,TLSv1.3 EOF @@ -380,8 +374,8 @@ EOF 2. Give the following permissions on the key so that it is readable by the **mysql** user only: ```shell -chown root:mysql /etc/pki/centreon-tls/server-key.pem -chmod 0640 /etc/pki/centreon-tls/server-key.pem +chown root:mysql /etc/pki/centreon-tls/db-key.pem +chmod 0640 /etc/pki/centreon-tls/db-key.pem ``` 3. Configure MySQL CLI to use TLS (you will need it later). @@ -489,16 +483,16 @@ done -1. Store the certificates in a location the database service can read. (By default, MySQL on Debian only reads certs under **/etc/mysql/**). +1. Store the certificates in a location the database service can read. (By default, MySQL on Debian only reads certificates under **/etc/mysql/**). ```shell install -d -o root -g mysql -m 0750 /etc/mysql/centreon-tls cp /etc/pki/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem -cp /etc/pki/centreon-tls/server.pem /etc/mysql/centreon-tls/server.pem -cp /etc/pki/centreon-tls/server-key.pem /etc/mysql/centreon-tls/server-key.pem +cp /etc/pki/centreon-tls/server.pem /etc/mysql/centreon-tls/db.pem +cp /etc/pki/centreon-tls/server-key.pem /etc/mysql/centreon-tls/db-key.pem chown root:mysql /etc/mysql/centreon-tls/*.pem -chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/server.pem -chmod 0640 /etc/mysql/centreon-tls/server-key.pem +chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/db.pem +chmod 0640 /etc/mysql/centreon-tls/db-key.pem ``` 2. Configure the database service to start in TLS mode and specify the certificate locations. @@ -511,8 +505,8 @@ for d in "${inc[@]}"; do cat > "$d/99-centreon-tls.cnf" <<'EOF' [mysqld] ssl_ca = /etc/mysql/centreon-tls/rootCA.pem -ssl_cert = /etc/mysql/centreon-tls/server.pem -ssl_key = /etc/mysql/centreon-tls/server-key.pem +ssl_cert = /etc/mysql/centreon-tls/db.pem +ssl_key = /etc/mysql/centreon-tls/db-key.pem require_secure_transport = OFF tls_version = TLSv1.2,TLSv1.3 EOF diff --git a/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx b/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx index 4c7db0b7e503..8de49b73c68a 100644 --- a/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx +++ b/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx @@ -14,8 +14,8 @@ echo 'Listen 443 https' > /etc/httpd/conf.d/ssl.conf 2. Enter the correct certificate paths in Centreon's Apache HTTPS configuration: ```shell -sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ - -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/web.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/web-key.pem|g' \ /usr/share/centreon/examples/centreon-apache-https.conf \ > /etc/httpd/conf.d/00-centreon-tls.conf ``` @@ -39,8 +39,8 @@ echo 'Listen 443 https' > /etc/httpd/conf.d/ssl.conf 2. Enter the correct certificate paths in Centreon's Apache HTTPS configuration: ```shell -sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ - -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ +sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/web.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/web-key.pem|g' \ /usr/share/centreon/examples/centreon-apache-https.conf \ > /etc/httpd/conf.d/00-centreon-tls.conf ``` @@ -73,26 +73,26 @@ systemctl restart mysqld -Enable every module the official Centreon HTTPS references: +1. Enable every module the official Centreon HTTPS references: -```shell -a2enmod ssl proxy proxy_fcgi headers deflate rewrite -``` + ```shell + a2enmod ssl proxy proxy_fcgi headers deflate rewrite + ``` -Enter the correct certificate paths in Centreon's Apache HTTPS configuration: +2. Enter the correct certificate paths in Centreon's Apache HTTPS configuration: -```shell -sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/server.pem|g' \ - -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/server-key.pem|g' \ - /usr/share/centreon/examples/centreon-apache-https.conf \ - > /etc/apache2/sites-available/00-centreon-tls.conf -``` + ```shell + sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/web.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/web-key.pem|g' \ + /usr/share/centreon/examples/centreon-apache-https.conf \ + > /etc/apache2/sites-available/00-centreon-tls.conf + ``` -Enable the configuration you just applied. +3. Enable the configuration you just applied. -```shell -a2ensite 00-centreon-tls -``` + ```shell + a2ensite 00-centreon-tls + ``` diff --git a/versioned_docs/version-26.10/installation/_tls-certificates.mdx b/versioned_docs/version-26.10/installation/_tls-certificates.mdx index 00187316bac6..dcb73998126f 100644 --- a/versioned_docs/version-26.10/installation/_tls-certificates.mdx +++ b/versioned_docs/version-26.10/installation/_tls-certificates.mdx @@ -5,14 +5,15 @@ Use a certificate issued by a trusted authority. Self-signed certificates may be * If you already have a certificate validated by an authority, you can proceed to the next step. * If you do not have a certificate validated by an authority, you can generate one on platforms such as [Let's Encrypt](https://letsencrypt.org/). -- If, for test purposes, you want to use a self-signed certificate, follow [this procedure](../administration/self-signed-certificate.md) before activating HTTPS mode on your server. Note that you will have to import the CA certificate into your browser. +* If, for test purposes, you want to use a self-signed certificate, follow [this procedure](../administration/self-signed-certificate.md) before activating HTTPS mode on your server. Note that you will have to import the CA certificate into your browser. -Let's say you have the following files in **/etc/pki/centreon-tls/**: +Say you have the following files (in our example, in **/etc/pki/centreon-tls/**): -* rootCA.pem (public) -* server.pem (server certificate) -* server-key.pem (server private key) -{/* * CA/rootCA.\{key,pem\} (set the following permissions: root:root, mode 0400) */} +* rootCA.pem (public - not needed if you are using a trusted certificate) +* web.pem (web server certificate) +* web-key.pem (web server private key) +* db.pem (database server certificate) +* db-key.pem (database server private key) 1. Install the root CA into the OS trust store of the central server's host machine: From 87ae9aeefc152363719b6c80594e2538c6395588 Mon Sep 17 00:00:00 2001 From: smau <102975713+smau-centreon@users.noreply.github.com> Date: Wed, 14 Oct 2026 09:35:54 +0200 Subject: [PATCH 139/179] Update versioned_docs/version-26.10/graph-views/map-web-install.md Co-authored-by: Jordan9131 <138499128+Jordan9131@users.noreply.github.com> --- versioned_docs/version-26.10/graph-views/map-web-install.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index 1e366f92899e..ff0a4f9eee78 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -437,7 +437,7 @@ dnf install mariadb-server ```shell -dnf install mariadb-server +dnf install -y mariadb11.8-server ``` From eb31eb8bfe07b642a4293c6d80ec798c79ba40f9 Mon Sep 17 00:00:00 2001 From: smau <102975713+smau-centreon@users.noreply.github.com> Date: Wed, 14 Oct 2026 09:36:19 +0200 Subject: [PATCH 140/179] Update i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md Co-authored-by: Jordan9131 <138499128+Jordan9131@users.noreply.github.com> --- .../version-26.10/graph-views/map-web-install.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index e0dc7d039c38..ff55ff798085 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -429,7 +429,7 @@ dnf install mariadb-server ```shell -dnf install mariadb-server +dnf install -y mariadb11.8-server ``` From 8723cee4043ca4b80a426e2baa678b78881d13c7 Mon Sep 17 00:00:00 2001 From: smau Date: Wed, 14 Oct 2026 10:49:48 +0200 Subject: [PATCH 141/179] Update following QA feedback --- .../version-26.10/graph-views/map-web-install.md | 8 ++------ .../version-26.10/graph-views/map-web-install.md | 8 ++------ 2 files changed, 4 insertions(+), 12 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index ff55ff798085..e110c013d42c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -395,16 +395,12 @@ Vous devez d'abord ajouter le dépôt MariaDB : -```shell -dnf module enable -y mariadb:11.8 -``` +Il n'y a pas de module à activer sur Alma / RHEL / Oracle Linux 10 : MariaDB 11.8 est fourni par le paquet `mariadb11.8-server`. Passez à l'étape suivante. -```shell -dnf module enable -y mariadb:11.8 -``` +Il n'y a pas de module à activer sur Alma / RHEL / Oracle Linux 10 : MariaDB 11.8 est fourni par le paquet `mariadb11.8-server`. Passez à l'étape suivante. diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index ff0a4f9eee78..a3bf277c4c94 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -403,16 +403,12 @@ First you need to add the MariaDB repository: -```shell -dnf module enable -y mariadb:11.8 -``` +There is no module stream to enable on Alma / RHEL / Oracle Linux 10: MariaDB 11.8 is provided by the `mariadb11.8-server` package. Go to the next step. -```shell -dnf module enable -y mariadb:11.8 -``` +There is no module stream to enable on Alma / RHEL / Oracle Linux 10: MariaDB 11.8 is provided by the `mariadb11.8-server` package. Go to the next step. From fc7af4737494cd7fb0b5a60756f6cd2749fbae3b Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 15 Oct 2026 11:12:35 +0200 Subject: [PATCH 142/179] Changes following review --- .../administration/self-signed-certificate.md | 134 ++++++++++++++++-- .../installation/_database-tls-conf.mdx | 12 +- .../installation/_interface-tls-conf.mdx | 4 +- .../installation/_tls-certificates.mdx | 13 +- .../administration/self-signed-certificate.md | 126 ++++++++++++++-- .../installation/_database-tls-conf.mdx | 16 +-- .../installation/_interface-tls-conf.mdx | 4 +- .../installation/_tls-certificates.mdx | 4 +- 8 files changed, 267 insertions(+), 46 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md index 1f648f858131..66b9a81e72a3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/self-signed-certificate.md @@ -238,51 +238,161 @@ sudo chmod 0644 /out/db/db.pem sudo chmod 0640 /out/db/db-key.pem ``` -Vous disposez maintenant des fichiers nécessaires dans votre dossier **/out**. Vous pouvez les copier aux bons emplacements sur vos serveurs (par ex. **/etc/pki/centreon-tls/** sur EL 9 ou 10 comme dans l'exemple ci-dessous, ou **/etc/ssl/certs/centreon-tls** sur Debian 13). +## Étape 8 : Copier les fichiers -Sur le serveur central/distant : +Vous disposez maintenant des fichiers nécessaires dans votre dossier **/out**. Vous pouvez les copier aux emplacements appropriés sur vos serveurs (par exemple **/etc/pki/centreon-tls/** sur EL 9 ou 10 comme dans l'exemple ci-dessous, ou **/etc/ssl/certs/centreon-tls** sur Debian 13). -```shell -sudo mkdir -p /etc/pki/centreon-tls -sudo cp /out/CA/rootCA.pem /out/web/web.pem /out/web/web-key.pem /etc/pki/centreon-tls/ -``` +1. Déplacez **rootCA.key** dans un endroit sûr, puis supprimez-le de votre répertoire **/out**. -Pour la base de données : +2. Sur le serveur central/distant : + + + + + ```shell + sudo mkdir -p /etc/pki/centreon-tls + sudo cp /out/CA/rootCA.pem /out/web/web.pem /out/web/web-key.pem /etc/pki/centreon-tls/ + ``` + + + + + ```shell + sudo mkdir -p /etc/pki/centreon-tls + sudo cp /out/CA/rootCA.pem /out/web/web.pem /out/web/web-key.pem /etc/pki/centreon-tls/ + ``` + + + + + ```shell + sudo mkdir -p /etc/ssl/certs/centreon-tls/ + sudo cp /out/CA/rootCA.pem /out/web/web.pem /out/web/web-key.pem /etc/ssl/certs/centreon-tls/ + ``` + + + + +3. Pour la base de données : * Si votre base de données est locale, exécutez ces commandes sur le serveur central : + + + ```shell sudo mkdir -p /etc/pki/centreon-tls sudo cp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem /etc/pki/centreon-tls/ ``` + + + + ```shell + sudo mkdir -p /etc/pki/centreon-tls + sudo cp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem /etc/pki/centreon-tls/ + ``` + + + + + ```shell + sudo mkdir -p /etc/ssl/certs/centreon-tls/ + sudo cp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem /etc/ssl/certs/centreon-tls/ + ``` + + + + * Si votre base de données est distante, créez le dossier sur le serveur de base de données : + + + + ```shell + sudo mkdir -p /etc/pki/centreon-tls + ``` + + + + ```shell sudo mkdir -p /etc/pki/centreon-tls ``` - Ensuite, sur le serveur central, copiez les fichiers sur le serveur de base de données à l'aide d'une méthode sécurisée, car **db-key.pem** est une clé privée. Remplacez **db.example.com** par l'adresse de votre serveur de base de données : + + + + ```shell + sudo mkdir -p /etc/ssl/certs/centreon-tls/ + ``` + + + + + Ensuite, sur le serveur central, copiez les fichiers vers le serveur de base de données à l'aide d'une méthode sécurisée, car **db-key.pem** est une clé privée. Remplacez **db.example.com** par l'adresse de votre serveur de base de données : + + + + + ```shell + sudo scp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem root@db.example.com:/etc/pki/centreon-tls/ + ``` + + + ```shell sudo scp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem root@db.example.com:/etc/pki/centreon-tls/ ``` - Si root ne peut pas se connecter en SSH sur le serveur de base de données, copiez les fichiers dans le dossier personnel d'un utilisateur qui le peut (remplacez **user**) : + + + + ```shell + sudo scp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem root@db.example.com:/etc/ssl/certs/centreon-tls/ + ``` + + + + + Si l'utilisateur root ne peut pas se connecter en SSH au serveur de base de données, copiez les fichiers dans le dossier personnel d'un utilisateur qui le peut (remplacez **user**) : ```shell sudo scp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem user@db.example.com:~/ ``` - Ensuite, sur le serveur de base de données, déplacez-les dans le bon dossier : + Puis, sur le serveur de base de données, déplacez-les dans le bon dossier : + + + ```shell sudo mv ~/rootCA.pem ~/db.pem ~/db-key.pem /etc/pki/centreon-tls/ sudo chown root:root /etc/pki/centreon-tls/*.pem ``` - Supprimez ensuite la clé privée du serveur central : + + ```shell - sudo rm /out/db/db-key.pem + sudo mv ~/rootCA.pem ~/db.pem ~/db-key.pem /etc/pki/centreon-tls/ + sudo chown root:root /etc/pki/centreon-tls/*.pem ``` + + + + + ```shell + sudo mv ~/rootCA.pem ~/db.pem ~/db-key.pem /etc/ssl/certs/centreon-tls/ + sudo chown root:root /etc/ssl/certs/centreon-tls/*.pem + ``` + + + + +4. Supprimez les clés privées du dossier **/out**, puisqu'elles se trouvent désormais à leur emplacement définitif : + + ```shell + sudo rm /out/web/web-key.pem /out/db/db-key.pem + ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx index 9b39caaaee8a..4aa124abe69b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_database-tls-conf.mdx @@ -152,9 +152,9 @@ done ```shell install -d -o root -g mysql -m 0750 /etc/mysql/centreon-tls -cp /etc/pki/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem -cp /etc/pki/centreon-tls/db.pem /etc/mysql/centreon-tls/db.pem -cp /etc/pki/centreon-tls/db-key.pem /etc/mysql/centreon-tls/db-key.pem +cp /etc/ssl/certs/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem +cp /etc/ssl/certs/centreon-tls/db.pem /etc/mysql/centreon-tls/db.pem +cp /etc/ssl/certs/centreon-tls/db-key.pem /etc/mysql/centreon-tls/db-key.pem chown root:mysql /etc/mysql/centreon-tls/*.pem chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/db.pem chmod 0640 /etc/mysql/centreon-tls/db-key.pem @@ -487,9 +487,9 @@ done ```shell install -d -o root -g mysql -m 0750 /etc/mysql/centreon-tls -cp /etc/pki/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem -cp /etc/pki/centreon-tls/db.pem /etc/mysql/centreon-tls/db.pem -cp /etc/pki/centreon-tls/db-key.pem /etc/mysql/centreon-tls/db-key.pem +cp /etc/ssl/certs/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem +cp /etc/ssl/certs/centreon-tls/db.pem /etc/mysql/centreon-tls/db.pem +cp /etc/ssl/certs/centreon-tls/db-key.pem /etc/mysql/centreon-tls/db-key.pem chown root:mysql /etc/mysql/centreon-tls/*.pem chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/db.pem chmod 0640 /etc/mysql/centreon-tls/db-key.pem diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx index e6177a289b8d..059e6a32a528 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx @@ -82,8 +82,8 @@ systemctl restart mysqld 2. Renseignez les chemins des certificats dans la configuration HTTPS d'Apache pour Centreon : ```shell - sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/web.pem|g' \ - -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/web-key.pem|g' \ + sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/ssl/certs/centreon-tls/web.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/ssl/certs/centreon-tls/web-key.pem|g' \ /usr/share/centreon/examples/centreon-apache-https.conf \ > /etc/apache2/sites-available/00-centreon-tls.conf ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx index d76c597ee6ee..9f48bb743b2b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_tls-certificates.mdx @@ -7,12 +7,13 @@ Utilisez un certificat délivré par une autorité de confiance. Les certificats * Si vous ne disposez pas d'un certificat validé par une autorité, vous pouvez en générer un sur des plateformes telles que [Let's Encrypt](https://letsencrypt.org/). * Si, à des fins de test, vous souhaitez utiliser un certificat auto-signé, [vous pouvez suivre cett procédure pour en créer un](../administration/self-signed-certificate.md) avant d'activer le mode HTTPS sur votre serveur. Attention, vous devrez importer le certificat de l'autorité de certification (CA) dans votre navigateur. -Supposons que vous disposiez des fichiers suivants (dans notre exemple, dans **/etc/pki/centreon-tls/**) : +Supposons que vous disposiez des fichiers suivants (dans notre exemple, dans **/etc/pki/centreon-tls/** sur EL 9 or 10, ou **/etc/ssl/certs/centreon-tls** sur Debian 13) : - * rootCA.pem (public - non nécessaire si vous utilisez un certificat reconnu) - * server.pem (certificat du serveur) - * server-key.pem (clé privée du serveur) - * CA/rootCA.\{key,pem\} (définissez les permissions suivantes : root:root, mode 0400) + * rootCA.pem (public - non nécessaire si vous utilisez un certificat reconnu) + * web.pem (certificat du serveur web) + * web-key.pem (clé privée du serveur web) + * db.pem (certificat du serveur de base de données) + * db-key.pem (clé privée du serveur de base de données) 1. Installez l'autorité de certification racine dans le trust store du système d'exploitation de la machine hébergeant le serveur central : @@ -36,7 +37,7 @@ Supposons que vous disposiez des fichiers suivants (dans notre exemple, dans **/ ```shell - cp /etc/pki/centreon-tls/rootCA.pem /usr/local/share/ca-certificates/centreon-dev.crt + cp /etc/ssl/certs/centreon-tls/rootCA.pem /usr/local/share/ca-certificates/centreon-dev.crt update-ca-certificates ``` diff --git a/versioned_docs/version-26.10/administration/self-signed-certificate.md b/versioned_docs/version-26.10/administration/self-signed-certificate.md index 6cbe027bf624..7057dd3d5ecf 100644 --- a/versioned_docs/version-26.10/administration/self-signed-certificate.md +++ b/versioned_docs/version-26.10/administration/self-signed-certificate.md @@ -238,36 +238,124 @@ sudo chmod 0644 /out/db/db.pem sudo chmod 0640 /out/db/db-key.pem ``` +## Step 8: Copy the files + You now have the files you need in your **/out** folder. You can copy them to the correct locations on your servers (e.g. **/etc/pki/centreon-tls/** on EL 9 or 10 like in the example below, or **/etc/ssl/certs/centreon-tls** on Debian 13). -On the central/remote server: +1. Move **rootCA.key** to a safe place, then delete it from your **/out** directory. -```shell -sudo mkdir -p /etc/pki/centreon-tls -sudo cp /out/CA/rootCA.pem /out/web/web.pem /out/web/web-key.pem /etc/pki/centreon-tls/ -``` +2. On the central/remote server: -For the database: + + + + ```shell + sudo mkdir -p /etc/pki/centreon-tls + sudo cp /out/CA/rootCA.pem /out/web/web.pem /out/web/web-key.pem /etc/pki/centreon-tls/ + ``` + + + + + ```shell + sudo mkdir -p /etc/pki/centreon-tls + sudo cp /out/CA/rootCA.pem /out/web/web.pem /out/web/web-key.pem /etc/pki/centreon-tls/ + ``` + + + + + ```shell + sudo mkdir -p /etc/ssl/certs/centreon-tls/ + sudo cp /out/CA/rootCA.pem /out/web/web.pem /out/web/web-key.pem /etc/ssl/certs/centreon-tls/ + ``` + + + + +3. For the database: * If your database is local, run these commands on the central server: + + + ```shell sudo mkdir -p /etc/pki/centreon-tls sudo cp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem /etc/pki/centreon-tls/ ``` + + + + ```shell + sudo mkdir -p /etc/pki/centreon-tls + sudo cp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem /etc/pki/centreon-tls/ + ``` + + + + + ```shell + sudo mkdir -p /etc/ssl/certs/centreon-tls/ + sudo cp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem /etc/ssl/certs/centreon-tls/ + ``` + + + + * If your database is remote, create the folder on the database server: + + + + ```shell + sudo mkdir -p /etc/pki/centreon-tls + ``` + + + + ```shell sudo mkdir -p /etc/pki/centreon-tls ``` + + + + ```shell + sudo mkdir -p /etc/ssl/certs/centreon-tls/ + ``` + + + + Then, on the central server, copy the files to the database server using a secure method, as **db-key.pem** is a private key. Replace **db.example.com** with the address of your database server: + + + + ```shell + sudo scp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem root@db.example.com:/etc/pki/centreon-tls/ + ``` + + + + ```shell sudo scp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem root@db.example.com:/etc/pki/centreon-tls/ ``` + + + + ```shell + sudo scp /out/CA/rootCA.pem /out/db/db.pem /out/db/db-key.pem root@db.example.com:/etc/ssl/certs/centreon-tls/ + ``` + + + + If root cannot log in through SSH on the database server, copy the files to the home folder of a user who can (replace **user**): ```shell @@ -276,13 +364,35 @@ For the database: Then, on the database server, move them to the right folder: + + + ```shell sudo mv ~/rootCA.pem ~/db.pem ~/db-key.pem /etc/pki/centreon-tls/ sudo chown root:root /etc/pki/centreon-tls/*.pem ``` - Then delete the private key from the central server: + + ```shell - sudo rm /out/db/db-key.pem + sudo mv ~/rootCA.pem ~/db.pem ~/db-key.pem /etc/pki/centreon-tls/ + sudo chown root:root /etc/pki/centreon-tls/*.pem ``` + + + + + ```shell + sudo mv ~/rootCA.pem ~/db.pem ~/db-key.pem /etc/ssl/certs/centreon-tls/ + sudo chown root:root /etc/ssl/certs/centreon-tls/*.pem + ``` + + + + +4. Delete the private keys from the **/out** folder, as they are now in their final locations: + + ```shell + sudo rm /out/web/web-key.pem /out/db/db-key.pem + ``` diff --git a/versioned_docs/version-26.10/installation/_database-tls-conf.mdx b/versioned_docs/version-26.10/installation/_database-tls-conf.mdx index e4ea8767d6d4..be5d425a2303 100644 --- a/versioned_docs/version-26.10/installation/_database-tls-conf.mdx +++ b/versioned_docs/version-26.10/installation/_database-tls-conf.mdx @@ -152,9 +152,9 @@ done ```shell install -d -o root -g mysql -m 0750 /etc/mysql/centreon-tls -cp /etc/pki/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem -cp /etc/pki/centreon-tls/db.pem /etc/mysql/centreon-tls/db.pem -cp /etc/pki/centreon-tls/db-key.pem /etc/mysql/centreon-tls/db-key.pem +cp /etc/ssl/certs/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem +cp /etc/ssl/certs/centreon-tls/db.pem /etc/mysql/centreon-tls/db.pem +cp /etc/ssl/certs/centreon-tls/db-key.pem /etc/mysql/centreon-tls/db-key.pem chown root:mysql /etc/mysql/centreon-tls/*.pem chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/db.pem chmod 0640 /etc/mysql/centreon-tls/db-key.pem @@ -217,7 +217,7 @@ for f in /etc/centreon/.env /usr/share/centreon/.env; do cat >> "$f" <<'EOF' DATABASE_SSL_ENABLED=1 DATABASE_VERIFY_SERVER_CERT=1 -DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +DATABASE_CA_PATH=/etc/ssl/certs/centreon-tls/rootCA.pem EOF done ``` @@ -487,9 +487,9 @@ done ```shell install -d -o root -g mysql -m 0750 /etc/mysql/centreon-tls -cp /etc/pki/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem -cp /etc/pki/centreon-tls/server.pem /etc/mysql/centreon-tls/db.pem -cp /etc/pki/centreon-tls/server-key.pem /etc/mysql/centreon-tls/db-key.pem +cp /etc/ssl/certs/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/rootCA.pem +cp /etc/ssl/certs/centreon-tls/db.pem /etc/mysql/centreon-tls/db.pem +cp /etc/ssl/certs/centreon-tls/db-key.pem /etc/mysql/centreon-tls/db-key.pem chown root:mysql /etc/mysql/centreon-tls/*.pem chmod 0644 /etc/mysql/centreon-tls/rootCA.pem /etc/mysql/centreon-tls/db.pem chmod 0640 /etc/mysql/centreon-tls/db-key.pem @@ -601,7 +601,7 @@ for f in /etc/centreon/.env /usr/share/centreon/.env; do cat >> "$f" <<'EOF' DATABASE_SSL_ENABLED=1 DATABASE_VERIFY_SERVER_CERT=1 -DATABASE_CA_PATH=/etc/pki/centreon-tls/rootCA.pem +DATABASE_CA_PATH=/etc/ssl/certs/centreon-tls/rootCA.pem EOF done ``` diff --git a/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx b/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx index 8de49b73c68a..d9c8c0e0dbe2 100644 --- a/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx +++ b/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx @@ -82,8 +82,8 @@ systemctl restart mysqld 2. Enter the correct certificate paths in Centreon's Apache HTTPS configuration: ```shell - sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/pki/centreon-tls/web.pem|g' \ - -e 's|/etc/pki/tls/private/ca.key|/etc/pki/centreon-tls/web-key.pem|g' \ + sed -e 's|/etc/pki/tls/certs/ca.crt|/etc/ssl/certs/centreon-tls/web.pem|g' \ + -e 's|/etc/pki/tls/private/ca.key|/etc/ssl/certs/centreon-tls/web-key.pem|g' \ /usr/share/centreon/examples/centreon-apache-https.conf \ > /etc/apache2/sites-available/00-centreon-tls.conf ``` diff --git a/versioned_docs/version-26.10/installation/_tls-certificates.mdx b/versioned_docs/version-26.10/installation/_tls-certificates.mdx index dcb73998126f..6c556ee4e3aa 100644 --- a/versioned_docs/version-26.10/installation/_tls-certificates.mdx +++ b/versioned_docs/version-26.10/installation/_tls-certificates.mdx @@ -7,7 +7,7 @@ Use a certificate issued by a trusted authority. Self-signed certificates may be * If you do not have a certificate validated by an authority, you can generate one on platforms such as [Let's Encrypt](https://letsencrypt.org/). * If, for test purposes, you want to use a self-signed certificate, follow [this procedure](../administration/self-signed-certificate.md) before activating HTTPS mode on your server. Note that you will have to import the CA certificate into your browser. -Say you have the following files (in our example, in **/etc/pki/centreon-tls/**): +Say you have the following files (in our example, in **/etc/pki/centreon-tls/** on EL 9 or 10, or **/etc/ssl/certs/centreon-tls** on Debian 13): * rootCA.pem (public - not needed if you are using a trusted certificate) * web.pem (web server certificate) @@ -37,7 +37,7 @@ Say you have the following files (in our example, in **/etc/pki/centreon-tls/**) ```shell - cp /etc/pki/centreon-tls/rootCA.pem /usr/local/share/ca-certificates/centreon-dev.crt + cp /etc/ssl/certs/centreon-tls/rootCA.pem /usr/local/share/ca-certificates/centreon-dev.crt update-ca-certificates ``` From cc0f198d37d2113f752253a2df16b9236bcda01f Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Thu, 15 Oct 2026 13:29:40 +0200 Subject: [PATCH 143/179] Changes following review (unhide remote registration) --- .../installation-of-a-remote-server/using-packages.md | 10 +++++----- .../installation-of-a-remote-server/using-packages.md | 10 +++++----- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md index db8523993074..07ab9004b9e0 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md @@ -158,7 +158,7 @@ procédure d'[installation web](../web-and-post-installation.md#installation-web > À l'étape **Initialisation de la supervision**, seules les actions 6 à 8 sont nécessaires. - +> La version Centreon du serveur cible n'est pas valide. Elle doit être supérieure ou égale à 26.10. -## Étape 6 : Étendre les droits du SGBD local +## Étape 7 : Étendre les droits du SGBD local Enfin, ajoutez à l'utilisateur de base de données **centreon** les droits nécessaires pour utiliser la commande **LOAD DATA INFILE** : @@ -295,12 +295,12 @@ SET GLOBAL local_infile=1; exit ``` -## Étape 7 : Rattacher le serveur distant au serveur central +## Étape 8 : Rattacher le serveur distant au serveur central Rendez-vous au chapitre [Rattacher un serveur distant à un serveur central](../../monitoring/monitoring-servers/add-a-remote-server-to-configuration.md). -## Étape 8 : Sécuriser votre plateforme +## Étape 9 : Sécuriser votre plateforme N'oubliez pas de sécuriser votre plateforme Centreon en suivant nos [recommandations](../../administration/secure-platform.md). diff --git a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md index 310e51cab844..23b5e642eb62 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-remote-server/using-packages.md @@ -158,7 +158,7 @@ systemctl start apache2 > In the step **Initialization of the monitoring**, only actions 6 to 8 need to be done. - +> Your Centreon target version is invalid. It should be greater than or equal to 26.10. -## Step 6: Extend local DBMS rights +## Step 7: Extend local DBMS rights Finally, add rights for the **centreon** database user to use **LOAD DATA INFILE** command: @@ -295,12 +295,12 @@ SET GLOBAL local_infile=1; exit ``` -## Step 7: Attach the remote server to the central server +## Step 8: Attach the remote server to the central server Go to [Attach a remote server to a central server](../../monitoring/monitoring-servers/add-a-remote-server-to-configuration.md). -## Step 8: Secure your platform +## Step 9: Secure your platform Remember to secure your Centreon platform following our [recommendations](../../administration/secure-platform.md). From 29a9576b209ae2844fb347eff0a24c3d73e65482 Mon Sep 17 00:00:00 2001 From: emgcentreon Date: Thu, 15 Oct 2026 15:42:45 +0200 Subject: [PATCH 144/179] Update update-centreon-platform.md --- .../version-26.10/update/update-centreon-platform.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md index 351537c75d55..3d2957505961 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md @@ -241,6 +241,16 @@ Cette procédure est identique à la mise à jour d'un serveur Centreon Central. ## Mise à jour des collecteurs + +Il est possible d'obtenir la commande d'installation d'un collecteur depuis l'interface de votre serveur central. +Exécuter la commande d'installation d'un collecteur le met à jour. + +1. Allez dans la liste des collecteurs dans **Configuration > Collecteurs > Collecteurs**. + +2. Dans la colonne **Actions**, cliquez le bouton **Copier la commande d'installation** + +3. Exécutez cette commande sur le collecteur pour le mettre à jour. + 1. Videz le cache : From 5be30cbfab0198d39f2987452eda18e72e49a951 Mon Sep 17 00:00:00 2001 From: emgcentreon Date: Thu, 15 Oct 2026 15:46:43 +0200 Subject: [PATCH 145/179] Update update-centreon-platform.md --- .../version-26.10/update/update-centreon-platform.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/versioned_docs/version-26.10/update/update-centreon-platform.md b/versioned_docs/version-26.10/update/update-centreon-platform.md index 96047ca03b5b..437d5256450b 100644 --- a/versioned_docs/version-26.10/update/update-centreon-platform.md +++ b/versioned_docs/version-26.10/update/update-centreon-platform.md @@ -236,6 +236,16 @@ This procedure is the same as to update a Centreon central server. ## Update the Pollers + +You can obtain the command installation for an existing poller from the central server interface. +Executing the installation command of an existing poller will udpate it. + +1. Go to the pollers list in **Configuration > Pollers > Pollers**. + +2. In the **Actions** column, click on the **Copy installation command** button. + +3. Execute the copied command on your poller to update it. + 1. Clean the cache: From 8483a781679b6f7f9e797748f5c29a92b5ae25c4 Mon Sep 17 00:00:00 2001 From: emgcentreon Date: Thu, 15 Oct 2026 15:49:04 +0200 Subject: [PATCH 146/179] Update update-centreon-platform.md --- .../version-26.10/update/update-centreon-platform.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md index 3d2957505961..f1bfe86e7821 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md @@ -241,9 +241,9 @@ Cette procédure est identique à la mise à jour d'un serveur Centreon Central. ## Mise à jour des collecteurs - -Il est possible d'obtenir la commande d'installation d'un collecteur depuis l'interface de votre serveur central. -Exécuter la commande d'installation d'un collecteur le met à jour. + +Il est possible d'obtenir la commande d'installation d'un collecteur existant depuis l'interface de votre serveur central. +Exécuter la commande d'installation d'un collecteur existant le met à jour. 1. Allez dans la liste des collecteurs dans **Configuration > Collecteurs > Collecteurs**. From 8a85e6a74a39d5b3ee75d5fc4a2526bbed570b22 Mon Sep 17 00:00:00 2001 From: emgcentreon Date: Thu, 15 Oct 2026 15:50:51 +0200 Subject: [PATCH 147/179] Update update-centreon-platform.md --- versioned_docs/version-26.10/update/update-centreon-platform.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/update/update-centreon-platform.md b/versioned_docs/version-26.10/update/update-centreon-platform.md index 437d5256450b..a62a186e5ea5 100644 --- a/versioned_docs/version-26.10/update/update-centreon-platform.md +++ b/versioned_docs/version-26.10/update/update-centreon-platform.md @@ -236,7 +236,7 @@ This procedure is the same as to update a Centreon central server. ## Update the Pollers - + You can obtain the command installation for an existing poller from the central server interface. Executing the installation command of an existing poller will udpate it. From 79cfb06c3e293ee99c131176a3343e3754bde20a Mon Sep 17 00:00:00 2001 From: emgcentreon Date: Thu, 15 Oct 2026 17:09:22 +0200 Subject: [PATCH 148/179] new form for poller install on vm or physical --- versioned_docs/version-26.10/update/update-centreon-platform.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/update/update-centreon-platform.md b/versioned_docs/version-26.10/update/update-centreon-platform.md index a62a186e5ea5..85ee1769f1e4 100644 --- a/versioned_docs/version-26.10/update/update-centreon-platform.md +++ b/versioned_docs/version-26.10/update/update-centreon-platform.md @@ -234,7 +234,7 @@ This procedure is the same as to update a Centreon central server. > server. ## Update the Pollers - + You can obtain the command installation for an existing poller from the central server interface. From ee90dea23c0cf98bf4822615c418f13f955db4a2 Mon Sep 17 00:00:00 2001 From: emgcentreon Date: Thu, 15 Oct 2026 17:09:45 +0200 Subject: [PATCH 149/179] Update update-centreon-platform.md --- versioned_docs/version-26.10/update/update-centreon-platform.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/update/update-centreon-platform.md b/versioned_docs/version-26.10/update/update-centreon-platform.md index 85ee1769f1e4..a62a186e5ea5 100644 --- a/versioned_docs/version-26.10/update/update-centreon-platform.md +++ b/versioned_docs/version-26.10/update/update-centreon-platform.md @@ -234,7 +234,7 @@ This procedure is the same as to update a Centreon central server. > server. ## Update the Pollers - + You can obtain the command installation for an existing poller from the central server interface. From 0beda5f368c121af989b265a898d314de4fee21f Mon Sep 17 00:00:00 2001 From: emgcentreon Date: Thu, 15 Oct 2026 17:15:49 +0200 Subject: [PATCH 150/179] poller update from interface --- .../version-26.10/update/update-centreon-platform.md | 3 +++ .../version-26.10/update/update-centreon-platform.md | 3 +++ 2 files changed, 6 insertions(+) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md index f1bfe86e7821..f148abc453f5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md @@ -251,6 +251,8 @@ Exécuter la commande d'installation d'un collecteur existant le met à jour. 3. Exécutez cette commande sur le collecteur pour le mettre à jour. + + 1. Videz le cache : @@ -332,6 +334,7 @@ Rien à faire pour cet OS. + ## Mise à jour silencieuse diff --git a/versioned_docs/version-26.10/update/update-centreon-platform.md b/versioned_docs/version-26.10/update/update-centreon-platform.md index a62a186e5ea5..9f6c3e991372 100644 --- a/versioned_docs/version-26.10/update/update-centreon-platform.md +++ b/versioned_docs/version-26.10/update/update-centreon-platform.md @@ -246,6 +246,8 @@ Executing the installation command of an existing poller will udpate it. 3. Execute the copied command on your poller to update it. + + 1. Clean the cache: @@ -327,6 +329,7 @@ Nothing to do for this OS. + ## Unattended update From a6bfe8a6f3ff68e5f82aeb90a8f2f9954d11eb47 Mon Sep 17 00:00:00 2001 From: smau Date: Thu, 15 Oct 2026 17:29:46 +0200 Subject: [PATCH 151/179] Document Gorgone custom URI (MON-209970) --- .../administration/secure-platform.md | 15 +++++++++++++++ .../migrate/migrate-from-debian-to-debian.md | 2 ++ .../migrate/migrate-from-el-to-debian.md | 2 ++ .../migrate/migrate-from-el-to-el.md | 2 ++ .../monitoring/discovery/administration.md | 2 ++ .../discovery/troubleshooting-hosts-discovery.md | 2 +- .../administration/secure-platform.md | 15 +++++++++++++++ .../migrate/migrate-from-debian-to-debian.md | 2 ++ .../migrate/migrate-from-el-to-debian.md | 2 ++ .../migrate/migrate-from-el-to-el.md | 2 ++ .../monitoring/discovery/administration.md | 2 ++ .../discovery/troubleshooting-hosts-discovery.md | 2 +- .../administration/secure-platform.md | 15 +++++++++++++++ .../installation/_interface-tls-conf.mdx | 4 +++- .../migrate/migrate-from-debian-to-debian.md | 2 ++ .../migrate/migrate-from-el-to-debian.md | 2 ++ .../migrate/migrate-from-el-to-el.md | 2 ++ .../monitoring/discovery/administration.md | 2 ++ .../discovery/troubleshooting-hosts-discovery.md | 2 +- .../administration/secure-platform.md | 15 +++++++++++++++ .../migrate/migrate-from-debian-to-debian.md | 2 ++ .../migrate/migrate-from-el-to-debian.md | 2 ++ .../migrate/migrate-from-el-to-el.md | 2 ++ .../monitoring/discovery/administration.md | 2 ++ .../discovery/troubleshooting-hosts-discovery.md | 2 +- .../administration/secure-platform.md | 15 +++++++++++++++ .../migrate/migrate-from-debian-to-debian.md | 2 ++ .../migrate/migrate-from-el-to-debian.md | 2 ++ .../migrate/migrate-from-el-to-el.md | 2 ++ .../monitoring/discovery/administration.md | 2 ++ .../discovery/troubleshooting-hosts-discovery.md | 2 +- .../administration/secure-platform.md | 15 +++++++++++++++ .../installation/_interface-tls-conf.mdx | 2 ++ .../migrate/migrate-from-debian-to-debian.md | 2 ++ .../migrate/migrate-from-el-to-debian.md | 2 ++ .../migrate/migrate-from-el-to-el.md | 2 ++ .../monitoring/discovery/administration.md | 2 ++ .../discovery/troubleshooting-hosts-discovery.md | 2 +- 38 files changed, 149 insertions(+), 7 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/secure-platform.md index 0e27d649b62c..26a90a085bdd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/administration/secure-platform.md @@ -1428,6 +1428,21 @@ systemctl restart apache2 +4. Mettez à jour l'URL utilisée par Gorgone pour appeler l'API Centreon. Dans le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml**, remplacez **/centreon** par votre nouveau chemin dans la valeur **base_url** : + +```yaml + gorgone: + tpapi: + - name: centreonv2 + base_url: "https:///monitoring/api/latest/" +``` + +5. Redémarrez Gorgone : + +```shell + systemctl restart gorgoned +``` + ## Activation du http2 Il est possible d'activer le protocole http2 pour améliorer les performances réseaux de Centreon. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-debian-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-debian-to-debian.md index 5d97deb06aaa..3283bc16c760 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-debian-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-debian-to-debian.md @@ -221,6 +221,8 @@ Si vous utilisez vos propres plugins personnalisés, synchronisez les répertoir password: "@GORGONE_PASSWORD@" ``` + > Si vous avez [personnalisé l'URI de Centreon](../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + 7. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) de tous vos serveurs de supervision (y compris celle du central). 8. Redémarrez les processus suivants : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-debian.md index 35623ef42556..7e3ea4d1924e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-debian.md @@ -225,6 +225,8 @@ Si vous utilisez vos propres plugins personnalisés, synchronisez les répertoir password: "@GORGONE_PASSWORD@" ``` + > Si vous avez [personnalisé l'URI de Centreon](../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + 7. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) de tous vos serveurs de supervision (y compris celle du central). 8. Redémarrez les processus suivants : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-el.md index 06c1577d8f11..066453c3b10d 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/migrate/migrate-from-el-to-el.md @@ -245,6 +245,8 @@ rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/c password: "@GORGONE_PASSWORD@" ``` + > Si vous avez [personnalisé l'URI de Centreon](../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + 7. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) de tous vos serveurs de supervision (y compris celle du central). 8. Redémarrez les processus suivants : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/discovery/administration.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/discovery/administration.md index 537e9760b99e..3bb891c19e9e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/discovery/administration.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/discovery/administration.md @@ -205,6 +205,8 @@ gorgone: password: PYNM5kcc ``` +> Si vous avez [personnalisé l'URI de Centreon](../../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + L'accès à l'API Rest, représenté par *centreonv2*, nécessite les identifiants d'un utilisateur ayant accès à l'API de configuration. Il est utilisé pour la découverte d'hôtes. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/discovery/troubleshooting-hosts-discovery.md b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/discovery/troubleshooting-hosts-discovery.md index 5381afd185c7..e6b3bca02681 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/discovery/troubleshooting-hosts-discovery.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-24.10/monitoring/discovery/troubleshooting-hosts-discovery.md @@ -36,7 +36,7 @@ ERROR - [autodiscovery] -class- host discovery - cannot get platform versions - ### Solution -Dans le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml**, remplacez la valeur **base_url** par **http://127.0.0.1/centreon/api/latest/** +Dans le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml**, remplacez la valeur **base_url** par **http://127.0.0.1/centreon/api/latest/**. Si vous avez [personnalisé l'URI de Centreon](../../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé. Redémarrez ensuite Gorgone avec `systemctl restart gorgoned`. ### Vérifications complémentaires diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/secure-platform.md index 93ec42ae62be..5d95d9b9508e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/administration/secure-platform.md @@ -1428,6 +1428,21 @@ systemctl restart apache2 +4. Mettez à jour l'URL utilisée par Gorgone pour appeler l'API Centreon. Dans le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml**, remplacez **/centreon** par votre nouveau chemin dans la valeur **base_url** : + +```yaml + gorgone: + tpapi: + - name: centreonv2 + base_url: "https:///monitoring/api/latest/" +``` + +5. Redémarrez Gorgone : + +```shell + systemctl restart gorgoned +``` + ## Activation du http2 Il est possible d'activer le protocole http2 pour améliorer les performances réseaux de Centreon. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-debian-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-debian-to-debian.md index 7bd7cb5682e1..355258d2125c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-debian-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-debian-to-debian.md @@ -221,6 +221,8 @@ Si vous utilisez vos propres plugins personnalisés, synchronisez les répertoir password: "@GORGONE_PASSWORD@" ``` + > Si vous avez [personnalisé l'URI de Centreon](../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + 7. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) de tous vos serveurs de supervision (y compris celle du central). 8. Redémarrez les processus suivants : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-debian.md index 77fef842d991..c6c14135e05f 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-debian.md @@ -225,6 +225,8 @@ Si vous utilisez vos propres plugins personnalisés, synchronisez les répertoir password: "@GORGONE_PASSWORD@" ``` + > Si vous avez [personnalisé l'URI de Centreon](../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + 7. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) de tous vos serveurs de supervision (y compris celle du central). 8. Redémarrez les processus suivants : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-el.md index 68e2181cf7a4..48395a446610 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/migrate/migrate-from-el-to-el.md @@ -245,6 +245,8 @@ rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/c password: "@GORGONE_PASSWORD@" ``` + > Si vous avez [personnalisé l'URI de Centreon](../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + 7. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) de tous vos serveurs de supervision (y compris celle du central). 8. Redémarrez les processus suivants : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/discovery/administration.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/discovery/administration.md index 537e9760b99e..3bb891c19e9e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/discovery/administration.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/discovery/administration.md @@ -205,6 +205,8 @@ gorgone: password: PYNM5kcc ``` +> Si vous avez [personnalisé l'URI de Centreon](../../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + L'accès à l'API Rest, représenté par *centreonv2*, nécessite les identifiants d'un utilisateur ayant accès à l'API de configuration. Il est utilisé pour la découverte d'hôtes. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/discovery/troubleshooting-hosts-discovery.md b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/discovery/troubleshooting-hosts-discovery.md index 5381afd185c7..e6b3bca02681 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/discovery/troubleshooting-hosts-discovery.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-25.10/monitoring/discovery/troubleshooting-hosts-discovery.md @@ -36,7 +36,7 @@ ERROR - [autodiscovery] -class- host discovery - cannot get platform versions - ### Solution -Dans le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml**, remplacez la valeur **base_url** par **http://127.0.0.1/centreon/api/latest/** +Dans le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml**, remplacez la valeur **base_url** par **http://127.0.0.1/centreon/api/latest/**. Si vous avez [personnalisé l'URI de Centreon](../../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé. Redémarrez ensuite Gorgone avec `systemctl restart gorgoned`. ### Vérifications complémentaires diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md index 34df59968b45..fae08df15511 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/secure-platform.md @@ -630,6 +630,21 @@ systemctl restart apache2 +4. Mettez à jour l'URL utilisée par Gorgone pour appeler l'API Centreon. Dans le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml**, remplacez **/centreon** par votre nouveau chemin dans la valeur **base_url** : + +```yaml + gorgone: + tpapi: + - name: centreonv2 + base_url: "https:///monitoring/api/latest/" +``` + +5. Redémarrez Gorgone : + +```shell + systemctl restart gorgoned +``` + ## Activation du http2 Il est possible d'activer le protocole http2 pour améliorer les performances réseaux de Centreon. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx index 059e6a32a528..7ebc33231c81 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/_interface-tls-conf.mdx @@ -99,7 +99,7 @@ systemctl restart mysqld > Une fois que votre serveur web est configuré en mode HTTPS et si vous avez un serveur MAP sur votre plateforme, vous devez définir l'adresse `centreon.url=https://` dans le fichier **/etc/centreon-map/map-config.properties** pour utiliser HTTPS au lieu de HTTP. Sinon, les navigateurs web récents peuvent bloquer la communication entre les deux serveurs. Voir la procédure détaillée [ici](../graph-views/secure-your-map-platform.md#configurer-httpstls-sur-le-serveur-map). -9. Configuration API de Gorgone +4. Configuration API de Gorgone Éditez le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** en remplaçant **127.0.0.1** par le FQDN de votre serveur central, comme dans l'exemple suivant : @@ -116,6 +116,8 @@ gorgone: password: "XXXXX" ``` +> Si vous avez [personnalisé l'URI de Centreon](../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + Redémarrez le daemon Gorgone : ```shell diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md index a4bc37948531..b40baa89f2d7 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md @@ -247,6 +247,8 @@ Si vous utilisez vos propres plugins personnalisés, synchronisez les répertoir password: "@GORGONE_PASSWORD@" ``` + > Si vous avez [personnalisé l'URI de Centreon](../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + 7. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) de tous vos serveurs de supervision (y compris celle du central). 8. Redémarrez les processus suivants : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md index dfe6a716c413..6d5ccb742eab 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-debian.md @@ -251,6 +251,8 @@ Si vous utilisez vos propres plugins personnalisés, synchronisez les répertoir password: "@GORGONE_PASSWORD@" ``` + > Si vous avez [personnalisé l'URI de Centreon](../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + 7. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) de tous vos serveurs de supervision (y compris celle du central). 8. Redémarrez les processus suivants : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md index 756b91156e41..f06421eab8f6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-el-to-el.md @@ -277,6 +277,8 @@ rsync -avz /usr/share/centreon/www/img/media root@:/usr/share/c password: "@GORGONE_PASSWORD@" ``` + > Si vous avez [personnalisé l'URI de Centreon](../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + 7. [Déployez la configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) de tous vos serveurs de supervision (y compris celle du central). 8. Redémarrez les processus suivants : diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/administration.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/administration.md index a767ae5c86d8..e96506a9a287 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/administration.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/administration.md @@ -205,6 +205,8 @@ gorgone: password: PYNM5kcc ``` +> Si vous avez [personnalisé l'URI de Centreon](../../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé dans la valeur **base_url**. + L'accès à l'API Rest, représenté par *centreonv2*, nécessite les identifiants d'un utilisateur ayant accès à l'API de configuration. Il est utilisé pour la découverte d'hôtes. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/troubleshooting-hosts-discovery.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/troubleshooting-hosts-discovery.md index 5381afd185c7..e6b3bca02681 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/troubleshooting-hosts-discovery.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/discovery/troubleshooting-hosts-discovery.md @@ -36,7 +36,7 @@ ERROR - [autodiscovery] -class- host discovery - cannot get platform versions - ### Solution -Dans le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml**, remplacez la valeur **base_url** par **http://127.0.0.1/centreon/api/latest/** +Dans le fichier **/etc/centreon-gorgone/config.d/31-centreon-api.yaml**, remplacez la valeur **base_url** par **http://127.0.0.1/centreon/api/latest/**. Si vous avez [personnalisé l'URI de Centreon](../../administration/secure-platform.md#uri-personnalisée), remplacez **/centreon** par votre chemin personnalisé. Redémarrez ensuite Gorgone avec `systemctl restart gorgoned`. ### Vérifications complémentaires diff --git a/versioned_docs/version-24.10/administration/secure-platform.md b/versioned_docs/version-24.10/administration/secure-platform.md index dc5b33447fe3..b134c12fd8e7 100644 --- a/versioned_docs/version-24.10/administration/secure-platform.md +++ b/versioned_docs/version-24.10/administration/secure-platform.md @@ -1432,6 +1432,21 @@ systemctl restart apache2 +4. Update the URL used by Gorgone to call the Centreon API. In the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file, replace **/centreon** with your new path in the **base_url** value: + +```yaml + gorgone: + tpapi: + - name: centreonv2 + base_url: "https:///monitoring/api/latest/" +``` + +5. Restart Gorgone: + +```shell + systemctl restart gorgoned +``` + ## Enabling http2 It is possible to enable the http2 protocol to improve Centreon's network performance. diff --git a/versioned_docs/version-24.10/migrate/migrate-from-debian-to-debian.md b/versioned_docs/version-24.10/migrate/migrate-from-debian-to-debian.md index 3b51ea94b3d4..f9f0ea4e6bfb 100644 --- a/versioned_docs/version-24.10/migrate/migrate-from-debian-to-debian.md +++ b/versioned_docs/version-24.10/migrate/migrate-from-debian-to-debian.md @@ -220,6 +220,8 @@ chapter for more information. password: "@GORGONE_PASSWORD@" ``` + > If you have [customized the Centreon URI](../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + 7. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) for all your monitoring servers (including the central). 8. Restart the following processes: diff --git a/versioned_docs/version-24.10/migrate/migrate-from-el-to-debian.md b/versioned_docs/version-24.10/migrate/migrate-from-el-to-debian.md index 1875c0a07799..dfb4621f7ef9 100644 --- a/versioned_docs/version-24.10/migrate/migrate-from-el-to-debian.md +++ b/versioned_docs/version-24.10/migrate/migrate-from-el-to-debian.md @@ -223,6 +223,8 @@ chapter for more information. password: "@GORGONE_PASSWORD@" ``` + > If you have [customized the Centreon URI](../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + 7. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) for all your monitoring servers (including the central). 8. Restart the following processes: diff --git a/versioned_docs/version-24.10/migrate/migrate-from-el-to-el.md b/versioned_docs/version-24.10/migrate/migrate-from-el-to-el.md index 1835722d2b7e..0f46a3149f8b 100644 --- a/versioned_docs/version-24.10/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-24.10/migrate/migrate-from-el-to-el.md @@ -243,6 +243,8 @@ chapter for more information. password: "@GORGONE_PASSWORD@" ``` + > If you have [customized the Centreon URI](../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + 7. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) for all your monitoring servers (including the central). 8. Restart the following processes: diff --git a/versioned_docs/version-24.10/monitoring/discovery/administration.md b/versioned_docs/version-24.10/monitoring/discovery/administration.md index c053f405c264..2a9c9ab15341 100644 --- a/versioned_docs/version-24.10/monitoring/discovery/administration.md +++ b/versioned_docs/version-24.10/monitoring/discovery/administration.md @@ -199,6 +199,8 @@ gorgone: password: PYNM5kcc ``` +> If you have [customized the Centreon URI](../../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + Access to RestAPI, represented by *centreonv2*, requires credentials of a user with *Reach API Configuration* access. It is used for Host Discovery. diff --git a/versioned_docs/version-24.10/monitoring/discovery/troubleshooting-hosts-discovery.md b/versioned_docs/version-24.10/monitoring/discovery/troubleshooting-hosts-discovery.md index 097025cdfef2..873dbf800cbf 100644 --- a/versioned_docs/version-24.10/monitoring/discovery/troubleshooting-hosts-discovery.md +++ b/versioned_docs/version-24.10/monitoring/discovery/troubleshooting-hosts-discovery.md @@ -36,7 +36,7 @@ ERROR - [autodiscovery] -class- host discovery - cannot get platform versions - ### Solution -In the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file, replace the **base_url** value with **http://127.0.0.1/centreon/api/latest/** +In the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file, replace the **base_url** value with **http://127.0.0.1/centreon/api/latest/**. If you have [customized the Centreon URI](../../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path. Then restart Gorgone with `systemctl restart gorgoned`. ### Additional checks diff --git a/versioned_docs/version-25.10/administration/secure-platform.md b/versioned_docs/version-25.10/administration/secure-platform.md index 6555e797c09c..53e266478670 100644 --- a/versioned_docs/version-25.10/administration/secure-platform.md +++ b/versioned_docs/version-25.10/administration/secure-platform.md @@ -1434,6 +1434,21 @@ systemctl restart apache2 +4. Update the URL used by Gorgone to call the Centreon API. In the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file, replace **/centreon** with your new path in the **base_url** value: + +```yaml + gorgone: + tpapi: + - name: centreonv2 + base_url: "https:///monitoring/api/latest/" +``` + +5. Restart Gorgone: + +```shell + systemctl restart gorgoned +``` + ## Enabling http2 It is possible to enable the http2 protocol to improve Centreon's network performance. diff --git a/versioned_docs/version-25.10/migrate/migrate-from-debian-to-debian.md b/versioned_docs/version-25.10/migrate/migrate-from-debian-to-debian.md index 22d8d555d807..fc7c781fbad0 100644 --- a/versioned_docs/version-25.10/migrate/migrate-from-debian-to-debian.md +++ b/versioned_docs/version-25.10/migrate/migrate-from-debian-to-debian.md @@ -217,6 +217,8 @@ chapter for more information. password: "@GORGONE_PASSWORD@" ``` + > If you have [customized the Centreon URI](../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + 7. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) for all your monitoring servers (including the central). 8. Restart the following processes: diff --git a/versioned_docs/version-25.10/migrate/migrate-from-el-to-debian.md b/versioned_docs/version-25.10/migrate/migrate-from-el-to-debian.md index bbb66f580004..a9c62204e3f4 100644 --- a/versioned_docs/version-25.10/migrate/migrate-from-el-to-debian.md +++ b/versioned_docs/version-25.10/migrate/migrate-from-el-to-debian.md @@ -220,6 +220,8 @@ chapter for more information. password: "@GORGONE_PASSWORD@" ``` + > If you have [customized the Centreon URI](../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + 7. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) for all your monitoring servers (including the central). 8. Restart the following processes: diff --git a/versioned_docs/version-25.10/migrate/migrate-from-el-to-el.md b/versioned_docs/version-25.10/migrate/migrate-from-el-to-el.md index 68e13f560c27..bbcb962a2e75 100644 --- a/versioned_docs/version-25.10/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-25.10/migrate/migrate-from-el-to-el.md @@ -241,6 +241,8 @@ chapter for more information. password: "@GORGONE_PASSWORD@" ``` + > If you have [customized the Centreon URI](../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + 7. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) for all your monitoring servers (including the central). 8. Restart the following processes: diff --git a/versioned_docs/version-25.10/monitoring/discovery/administration.md b/versioned_docs/version-25.10/monitoring/discovery/administration.md index c053f405c264..2a9c9ab15341 100644 --- a/versioned_docs/version-25.10/monitoring/discovery/administration.md +++ b/versioned_docs/version-25.10/monitoring/discovery/administration.md @@ -199,6 +199,8 @@ gorgone: password: PYNM5kcc ``` +> If you have [customized the Centreon URI](../../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + Access to RestAPI, represented by *centreonv2*, requires credentials of a user with *Reach API Configuration* access. It is used for Host Discovery. diff --git a/versioned_docs/version-25.10/monitoring/discovery/troubleshooting-hosts-discovery.md b/versioned_docs/version-25.10/monitoring/discovery/troubleshooting-hosts-discovery.md index 097025cdfef2..873dbf800cbf 100644 --- a/versioned_docs/version-25.10/monitoring/discovery/troubleshooting-hosts-discovery.md +++ b/versioned_docs/version-25.10/monitoring/discovery/troubleshooting-hosts-discovery.md @@ -36,7 +36,7 @@ ERROR - [autodiscovery] -class- host discovery - cannot get platform versions - ### Solution -In the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file, replace the **base_url** value with **http://127.0.0.1/centreon/api/latest/** +In the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file, replace the **base_url** value with **http://127.0.0.1/centreon/api/latest/**. If you have [customized the Centreon URI](../../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path. Then restart Gorgone with `systemctl restart gorgoned`. ### Additional checks diff --git a/versioned_docs/version-26.10/administration/secure-platform.md b/versioned_docs/version-26.10/administration/secure-platform.md index 56bd62b96c78..4514dc0c4c9b 100644 --- a/versioned_docs/version-26.10/administration/secure-platform.md +++ b/versioned_docs/version-26.10/administration/secure-platform.md @@ -631,6 +631,21 @@ systemctl restart apache2 +4. Update the URL used by Gorgone to call the Centreon API. In the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file, replace **/centreon** with your new path in the **base_url** value: + +```yaml + gorgone: + tpapi: + - name: centreonv2 + base_url: "https:///monitoring/api/latest/" +``` + +5. Restart Gorgone: + +```shell + systemctl restart gorgoned +``` + ## Enabling http2 It is possible to enable the http2 protocol to improve Centreon's network performance. diff --git a/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx b/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx index d9c8c0e0dbe2..deef13c54b20 100644 --- a/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx +++ b/versioned_docs/version-26.10/installation/_interface-tls-conf.mdx @@ -115,6 +115,8 @@ gorgone: password: "XXXXX" ``` +> If you have [customized the Centreon URI](../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + Then restart the Gorgone daemon: ```shell diff --git a/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md b/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md index 2c7ad23b75a8..b8e63b55511c 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md @@ -242,6 +242,8 @@ chapter for more information. password: "@GORGONE_PASSWORD@" ``` + > If you have [customized the Centreon URI](../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + 7. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) for all your monitoring servers (including the central). 8. Restart the following processes: diff --git a/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md b/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md index 12ebcbb01ef5..baeab9174677 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-el-to-debian.md @@ -246,6 +246,8 @@ chapter for more information. password: "@GORGONE_PASSWORD@" ``` + > If you have [customized the Centreon URI](../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + 7. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) for all your monitoring servers (including the central). 8. Restart the following processes: diff --git a/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md b/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md index 17c7cc827394..f24bea037c72 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-el-to-el.md @@ -265,6 +265,8 @@ chapter for more information. password: "@GORGONE_PASSWORD@" ``` + > If you have [customized the Centreon URI](../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + 7. [Deploy the configuration](../monitoring/monitoring-servers/deploying-a-configuration.md) for all your monitoring servers (including the central). 8. Restart the following processes: diff --git a/versioned_docs/version-26.10/monitoring/discovery/administration.md b/versioned_docs/version-26.10/monitoring/discovery/administration.md index 7443798fcfc2..65505e58aa69 100644 --- a/versioned_docs/version-26.10/monitoring/discovery/administration.md +++ b/versioned_docs/version-26.10/monitoring/discovery/administration.md @@ -199,6 +199,8 @@ gorgone: password: PYNM5kcc ``` +> If you have [customized the Centreon URI](../../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path in the **base_url** value. + Access to RestAPI, represented by *centreonv2*, requires credentials of a user with *Reach API Configuration* access. It is used for Host Discovery. diff --git a/versioned_docs/version-26.10/monitoring/discovery/troubleshooting-hosts-discovery.md b/versioned_docs/version-26.10/monitoring/discovery/troubleshooting-hosts-discovery.md index 097025cdfef2..873dbf800cbf 100644 --- a/versioned_docs/version-26.10/monitoring/discovery/troubleshooting-hosts-discovery.md +++ b/versioned_docs/version-26.10/monitoring/discovery/troubleshooting-hosts-discovery.md @@ -36,7 +36,7 @@ ERROR - [autodiscovery] -class- host discovery - cannot get platform versions - ### Solution -In the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file, replace the **base_url** value with **http://127.0.0.1/centreon/api/latest/** +In the **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** file, replace the **base_url** value with **http://127.0.0.1/centreon/api/latest/**. If you have [customized the Centreon URI](../../administration/secure-platform.md#custom-uri), replace **/centreon** with your custom path. Then restart Gorgone with `systemctl restart gorgoned`. ### Additional checks From b277252fe1caf93fffccac3ea56c088f0f2adb99 Mon Sep 17 00:00:00 2001 From: smau <102975713+smau-centreon@users.noreply.github.com> Date: Fri, 16 Oct 2026 09:52:45 +0200 Subject: [PATCH 152/179] Update versioned_docs/version-26.10/graph-views/map-web-install.md Co-authored-by: Jordan9131 <138499128+Jordan9131@users.noreply.github.com> --- versioned_docs/version-26.10/graph-views/map-web-install.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index a3bf277c4c94..a0d2033f35b3 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -403,7 +403,9 @@ First you need to add the MariaDB repository: -There is no module stream to enable on Alma / RHEL / Oracle Linux 10: MariaDB 11.8 is provided by the `mariadb11.8-server` package. Go to the next step. +```shell +dnf module enable -y mariadb:11.8 +``` From a616e61df91f4e1936ec6bf223d1965823f574a2 Mon Sep 17 00:00:00 2001 From: smau <102975713+smau-centreon@users.noreply.github.com> Date: Fri, 16 Oct 2026 09:53:08 +0200 Subject: [PATCH 153/179] Update versioned_docs/version-26.10/graph-views/map-web-install.md Co-authored-by: Jordan9131 <138499128+Jordan9131@users.noreply.github.com> --- versioned_docs/version-26.10/graph-views/map-web-install.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index a0d2033f35b3..52e4fbd09761 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -358,10 +358,8 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/e Install the following dependencies: - - ```shell -apt update && apt install lsb-release ca-certificates apt-transport-https software-properties-common wget gnupg2 curl +apt update && apt install lsb-release ca-certificates apt-transport-https wget gnupg2 curl ``` To install the Centreon repository, execute the following command: From 2419d55e58ef416664d48628814a66d87cb45a8a Mon Sep 17 00:00:00 2001 From: smau <102975713+smau-centreon@users.noreply.github.com> Date: Fri, 16 Oct 2026 09:53:24 +0200 Subject: [PATCH 154/179] Update i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md Co-authored-by: Jordan9131 <138499128+Jordan9131@users.noreply.github.com> --- .../version-26.10/graph-views/map-web-install.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index e110c013d42c..f816c3955e30 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -395,7 +395,9 @@ Vous devez d'abord ajouter le dépôt MariaDB : -Il n'y a pas de module à activer sur Alma / RHEL / Oracle Linux 10 : MariaDB 11.8 est fourni par le paquet `mariadb11.8-server`. Passez à l'étape suivante. +```shell +dnf module enable -y mariadb:11.8 +``` From 20fe353c5f5ef9791166647b69b770ee31350e19 Mon Sep 17 00:00:00 2001 From: smau <102975713+smau-centreon@users.noreply.github.com> Date: Fri, 16 Oct 2026 09:53:50 +0200 Subject: [PATCH 155/179] Update i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md Co-authored-by: Jordan9131 <138499128+Jordan9131@users.noreply.github.com> --- .../version-26.10/graph-views/map-web-install.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index f816c3955e30..a4dbfd16b4ec 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -351,10 +351,8 @@ dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/e Installez les dépendances suivantes : - - ```shell -apt update && apt install lsb-release ca-certificates apt-transport-https software-properties-common wget gnupg2 curl +apt update && apt install lsb-release ca-certificates apt-transport-https wget gnupg2 curl ``` Pour installer le dépôt Centreon, exécutez la commande suivante : From 9762ae446af8ace1aadbef6bf5a8a78e089334b4 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 16 Oct 2026 10:53:37 +0200 Subject: [PATCH 156/179] Changes following review (HA) --- .../administration/centreon-ha/operating-guide.md | 2 ++ .../administration/centreon-ha/troubleshooting-guide.md | 2 ++ .../installation-of-centreon-ha/cluster-elements.md | 6 ++++-- .../installation/installation-of-centreon-ha/faq.md | 2 +- .../administration/centreon-ha/operating-guide.md | 2 ++ .../administration/centreon-ha/troubleshooting-guide.md | 2 ++ .../installation-of-centreon-ha/cluster-elements.md | 6 ++++-- .../installation/installation-of-centreon-ha/faq.md | 2 +- 8 files changed, 18 insertions(+), 6 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/centreon-ha/operating-guide.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/centreon-ha/operating-guide.md index 22134d6f6562..4e2b60c7b2b3 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/centreon-ha/operating-guide.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/centreon-ha/operating-guide.md @@ -6,6 +6,8 @@ description: "Vérifier l'état du cluster, exécuter des bascules et gérer la > Sauf indication contraire, toutes les commandes de cette page doivent être exécutées en tant que « root ». +> Notez que certaines commandes, options ou sorties peuvent varier selon votre version de Pacemaker/Corosync. Reportez-vous à la documentation officielle correspondant à votre version. + ## Se connecter à Centreon sur le nœud actif L'accès à l'interface du nœud actif se fait via l'adresse IP de la VIP centrale. Cela signifie que vous utilisez toujours la même URL pour accéder à l'interface, que l'interface soit celle du nœud central 1 ou celle du nœud central 2. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/centreon-ha/troubleshooting-guide.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/centreon-ha/troubleshooting-guide.md index e5a618dfb579..461eb87deb62 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/centreon-ha/troubleshooting-guide.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/administration/centreon-ha/troubleshooting-guide.md @@ -6,6 +6,8 @@ description: "Diagnostiquer et résoudre les problèmes courants du cluster Cent import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +> Notez que certaines commandes, options ou sorties peuvent varier selon votre version de Pacemaker/Corosync. Reportez-vous à la documentation officielle correspondant à votre version. + ## Une "Failed action" est affichée dans `crm_mon` mais la ressource semble fonctionner correctement ```bash diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-centreon-ha/cluster-elements.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-centreon-ha/cluster-elements.md index 0db6470e5bd3..1a77dbbf9bd9 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-centreon-ha/cluster-elements.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-centreon-ha/cluster-elements.md @@ -80,6 +80,8 @@ Toutes ces ressources sont décrites dans le tableau ci-dessous. | `ms_mysql-master` | location | Définit quelle base de données est le nœud actif | | `vip_mysql` | service primitif | Adresse VIP pour le cluster de base de données | -## Nœuds actifs/passifs ou nœuds maître/esclave ? +## Nœuds actifs/passifs, master/slave, promoted/demoted -Dans ce chapitre, nous parlerons de nœuds actifs/passifs. Vous remarquerez peut-être que la sortie de certaines commandes utilise les termes maître et esclave : il s'agit de termes propres à Pacemaker et Corosync. Le maître désigne le nœud actif et l'esclave le nœud passif. +Dans ce chapitre, nous parlerons de nœuds actifs/passifs. Vous remarquerez peut-être que pour d'anciennes version de Pacemaker/Corosync la sortie de certaines commandes utilise les termes maître et esclave : il s'agit de termes propres à Pacemaker et Corosync. Le maître désigne le nœud actif et l'esclave le nœud passif. Dans les versions plus récentes de Pacemaker/Corosync, les termes employés sont "Promoted/demoted". + +> Notez que certaines commandes, options ou sorties peuvent varier selon votre version de Pacemaker/Corosync. Reportez-vous à la documentation officielle correspondant à votre version. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-centreon-ha/faq.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-centreon-ha/faq.md index e6d5ae34deae..ef77119a1207 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-centreon-ha/faq.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-centreon-ha/faq.md @@ -22,7 +22,7 @@ Les extensions nécessitent des fichiers de licence spécifiques pour fonctionne ## Qu'est-ce qui est supporté, et qu'est-ce qui ne l'est pas ? -Avec Centreon 25.10, les clusters HA peuvent être installés sur [tous les OS supportés](../compatibility.md#système-dexploitation), avec MariaDB comme SGBD. +Avec Centreon 26.10, les clusters HA peuvent être installés sur [tous les OS supportés](../compatibility.md#système-dexploitation), avec MariaDB comme SGBD. Le support pour les configurations HA n'est pas inclus dans le support standard de Centreon. Si vous souhaitez un support pour votre système HA, votre configuration HA doit être installée par Centreon Professional Services, et vous devez acheter un pack de support HA spécifique. diff --git a/versioned_docs/version-26.10/administration/centreon-ha/operating-guide.md b/versioned_docs/version-26.10/administration/centreon-ha/operating-guide.md index 04e20c404168..0b60cb50dcd2 100644 --- a/versioned_docs/version-26.10/administration/centreon-ha/operating-guide.md +++ b/versioned_docs/version-26.10/administration/centreon-ha/operating-guide.md @@ -6,6 +6,8 @@ description: "Check cluster status, perform failovers, and manage Centreon HA" > Unless otherwise stated, all commands in this page must be run as `root`. +> Note that some commands, options or outputs may differ with your version of Pacemaker/Corosync. Refer to the official documentation of your version. + ## Logging in to Centreon on the active node You access the interface of the active node via the IP address of the central VIP. This means that you always use the same URL to access the interface, whether the interface is that of central node 1 or of central node 2. diff --git a/versioned_docs/version-26.10/administration/centreon-ha/troubleshooting-guide.md b/versioned_docs/version-26.10/administration/centreon-ha/troubleshooting-guide.md index 1592590c64e9..555800e00330 100644 --- a/versioned_docs/version-26.10/administration/centreon-ha/troubleshooting-guide.md +++ b/versioned_docs/version-26.10/administration/centreon-ha/troubleshooting-guide.md @@ -6,6 +6,8 @@ description: "Diagnose and fix common Centreon HA cluster resource issues" import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +> Note that some commands, options or outputs may differ with your version of Pacemaker/Corosync. Refer to the official documentation of your version. + ## A failed action is displayed in `crm_mon` but the resource seems to be working fine ```bash diff --git a/versioned_docs/version-26.10/installation/installation-of-centreon-ha/cluster-elements.md b/versioned_docs/version-26.10/installation/installation-of-centreon-ha/cluster-elements.md index df7e56283ddb..8cbfbaaf112b 100644 --- a/versioned_docs/version-26.10/installation/installation-of-centreon-ha/cluster-elements.md +++ b/versioned_docs/version-26.10/installation/installation-of-centreon-ha/cluster-elements.md @@ -80,6 +80,8 @@ All these resources are described in the table below. | `ms_mysql-master` | location | Defines which database is the active node | | `vip_mysql` | primitive service | VIP address for the database cluster | -## Active/passive nodes or master/slave nodes? +## Active/passive nodes, master/slave, promoted/demoted -In this chapter, we will refer to active/passive nodes. You may notice that the output of some commands use the terms master and slave: these are Pacemaker and Corosync terms. Master means the active node and slave the passive node. +In this chapter, we will refer to active/passive nodes. You may notice that for old versions of Pacemaker/Corosync, the output of some commands use the terms master and slave: these are Pacemaker and Corosync terms. Master means the active node and slave the passive node. More recent versions of Pacemaker/Corosync use the terms "Promoted/demoted". + +> Note that some commands, options or outputs may differ with your version of Pacemaker/Corosync. Refer to the official documentation of your version. diff --git a/versioned_docs/version-26.10/installation/installation-of-centreon-ha/faq.md b/versioned_docs/version-26.10/installation/installation-of-centreon-ha/faq.md index eb4ec16c917e..091f92e6f5de 100644 --- a/versioned_docs/version-26.10/installation/installation-of-centreon-ha/faq.md +++ b/versioned_docs/version-26.10/installation/installation-of-centreon-ha/faq.md @@ -22,7 +22,7 @@ Extensions need specific license files to work on both central nodes smoothly. I ## What is supported, and what isn't? -With Centreon 25.10, HA clusters can be installed [on all supported OS](../compatibility.md#operating-systems), with MariaDB as DBMS. +With Centreon 26.10, HA clusters can be installed [on all supported OSs](../compatibility.md#operating-systems), with MariaDB as DBMS. Support for HA setups is not included in the Centreon standard support. If you want support for your HA system, your HA setup must be installed by Centreon Professional Services, and you need to purchase a specific HA support pack. From a92fae98831396c6e15e7e4aad772e7692d79f16 Mon Sep 17 00:00:00 2001 From: smau Date: Fri, 16 Oct 2026 11:01:23 +0200 Subject: [PATCH 157/179] Fix build (tab error) --- .../version-26.10/update/update-centreon-platform.md | 7 ++++++- .../version-26.10/update/update-centreon-platform.md | 7 ++++++- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md index f148abc453f5..60eb33c6de27 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/update/update-centreon-platform.md @@ -240,8 +240,9 @@ Cette procédure est identique à la mise à jour d'un serveur Centreon Central. ## Mise à jour des collecteurs - + + Il est possible d'obtenir la commande d'installation d'un collecteur existant depuis l'interface de votre serveur central. Exécuter la commande d'installation d'un collecteur existant le met à jour. @@ -250,8 +251,10 @@ Exécuter la commande d'installation d'un collecteur existant le met à jour. 2. Dans la colonne **Actions**, cliquez le bouton **Copier la commande d'installation** 3. Exécutez cette commande sur le collecteur pour le mettre à jour. + + @@ -334,6 +337,8 @@ Rien à faire pour cet OS. + + ## Mise à jour silencieuse diff --git a/versioned_docs/version-26.10/update/update-centreon-platform.md b/versioned_docs/version-26.10/update/update-centreon-platform.md index 9f6c3e991372..e0064347b5c5 100644 --- a/versioned_docs/version-26.10/update/update-centreon-platform.md +++ b/versioned_docs/version-26.10/update/update-centreon-platform.md @@ -235,8 +235,9 @@ This procedure is the same as to update a Centreon central server. ## Update the Pollers - + + You can obtain the command installation for an existing poller from the central server interface. Executing the installation command of an existing poller will udpate it. @@ -245,8 +246,10 @@ Executing the installation command of an existing poller will udpate it. 2. In the **Actions** column, click on the **Copy installation command** button. 3. Execute the copied command on your poller to update it. + + @@ -329,6 +332,8 @@ Nothing to do for this OS. + + ## Unattended update From 5e06b5e745fb2d8f983b7caa453dadaa864f35d7 Mon Sep 17 00:00:00 2001 From: smau <102975713+smau-centreon@users.noreply.github.com> Date: Fri, 16 Oct 2026 11:13:01 +0200 Subject: [PATCH 158/179] Update versioned_docs/version-26.10/graph-views/map-web-install.md Co-authored-by: Jordan9131 <138499128+Jordan9131@users.noreply.github.com> --- versioned_docs/version-26.10/graph-views/map-web-install.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index 52e4fbd09761..2597d8e95f75 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -491,8 +491,6 @@ dnf install https://dev.mysql.com/get/mysql84-community-release-el9-1.noarch.rpm - - ```shell dnf install https://dev.mysql.com/get/mysql84-community-release-el10-1.noarch.rpm -y ``` From c499db0d1af36810d42752b18c58384ac8190f3c Mon Sep 17 00:00:00 2001 From: smau <102975713+smau-centreon@users.noreply.github.com> Date: Fri, 16 Oct 2026 11:13:27 +0200 Subject: [PATCH 159/179] Update i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md Co-authored-by: Jordan9131 <138499128+Jordan9131@users.noreply.github.com> --- .../version-26.10/graph-views/map-web-install.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index a4dbfd16b4ec..124507ca6ec5 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -483,8 +483,6 @@ dnf install https://dev.mysql.com/get/mysql84-community-release-el9-1.noarch.rpm - - ```shell dnf install https://dev.mysql.com/get/mysql84-community-release-el10-1.noarch.rpm -y ``` From 4f3dfb503c59dbd183d99fb1054d7375ecaf96c3 Mon Sep 17 00:00:00 2001 From: smau Date: Fri, 16 Oct 2026 11:25:09 +0200 Subject: [PATCH 160/179] Apply QA suggestion --- .../version-26.10/graph-views/map-web-install.md | 11 ----------- .../version-26.10/graph-views/map-web-install.md | 11 ----------- 2 files changed, 22 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index a4dbfd16b4ec..f905f2c5d5e1 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -328,17 +328,6 @@ Vous devez d'abord installer le dépôt EPEL : dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm ``` -La commande doit retourner des résultats comme suit : - - - -```shell -Installed: - epel-release-10-.el10.noarch - -Complete! -``` - Ensuite installez le dépôt Centreon : ```shell diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index 52e4fbd09761..6a3dbc598c22 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -335,17 +335,6 @@ First you need to install an EPEL repository: dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm ``` -The command should return results as follows: - - - -```shell -Installed: - epel-release-10-.el10.noarch - -Complete! -``` - Then install the Centreon repository: ```shell From 3075744e9d463d0c5a6fdd7c7508c2117026b362 Mon Sep 17 00:00:00 2001 From: smau Date: Fri, 16 Oct 2026 11:39:04 +0200 Subject: [PATCH 161/179] Update following QA feedback --- .../version-26.10/graph-views/map-web-install.md | 4 ++-- versioned_docs/version-26.10/graph-views/map-web-install.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index 698512be9049..16a1922dd0ba 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -480,8 +480,8 @@ dnf install https://dev.mysql.com/get/mysql84-community-release-el10-1.noarch.rp ```shell -wget https://dev.mysql.com/get/mysql-apt-config_0.8.32-1_all.deb -dpkg -i mysql-apt-config_0.8.32-1_all.deb +wget https://dev.mysql.com/get/mysql-apt-config_0.8.36-1_all.deb +dpkg -i mysql-apt-config_0.8.36-1_all.deb apt update ``` diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index 3113bddee3c5..d18cf8499140 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -488,8 +488,8 @@ dnf install https://dev.mysql.com/get/mysql84-community-release-el10-1.noarch.rp ```shell -wget https://dev.mysql.com/get/mysql-apt-config_0.8.32-1_all.deb -dpkg -i mysql-apt-config_0.8.32-1_all.deb +wget https://dev.mysql.com/get/mysql-apt-config_0.8.36-1_all.deb +dpkg -i mysql-apt-config_0.8.36-1_all.deb apt update ``` From 9c471880a8c4bc9586a89f23872540da9847b0fe Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 16 Oct 2026 13:46:03 +0200 Subject: [PATCH 162/179] MON-209969 VM or physical --- .../pollers-containers-prerequisites.md | 22 +++++----- .../vm-or-physical.md | 40 +++++++++++++++++++ .../pollers-containers-prerequisites.md | 23 +++++------ .../vm-or-physical.md | 39 ++++++++++++++++++ .../version-26.10-sidebars.json | 20 ++++++---- 5 files changed, 113 insertions(+), 31 deletions(-) create mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md create mode 100644 versioned_docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md index 766caa497a04..9867afdeb795 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md @@ -1,25 +1,25 @@ --- id: pollers-containers-prerequisites -title: Prérequis pour les collecteurs en conteneur -description: "Configurer Centreon pour recevoir les connexions des collecteurs en conteneur" +title: Prérequis pour les collecteurs installés par commande générée +description: "Configurer Centreon pour recevoir les connexions des collecteurs installés par commande générée (installés sur une VM, une machine physique ou un conteneur)" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -Cette page explique comment configurer votre plateforme afin de pouvoir utiliser des collecteurs en conteneur. Cette procédure n'est à réaliser qu'une seule fois pour l'ensemble de la plateforme, avant d'installer votre premier collecteur en conteneur. Elle n'a aucun impact sur les autres modes de déploiement des collecteurs. +Cette page explique comment configurer votre plateforme afin de pouvoir utiliser des collecteurs installés par commande générée via l'interface (qu'ils soient installés sur une VM, une machine physique ou un conteneur). Cette procédure n'est à réaliser qu'une seule fois pour l'ensemble de la plateforme, avant d'installer votre premier collecteur de cette façon. Elle n'a aucun impact sur le mode de déploiement manuel de collecteurs. ## Quand utiliser cette procédure Cette page décrit la marche à suivre si les conditions suivantes sont réunies : * Vous venez d'installer une plateforme en version 26.10, ou vous avez mis à jour une plateforme qui ne comportait aucun collecteur en mode pullwss. -* Vous souhaitez utiliser des collecteurs en conteneur pour la première fois. +* Vous souhaitez utiliser des collecteurs installés par commande générée via l'interface pour la première fois (qu'ils soient installés sur une VM, une machine physique ou un conteneur). -> Si votre plateforme comportait des collecteurs en mode pullwss et que vous souhaitez désormais utiliser des collecteurs en conteneur, suivez la procédure [Adapter les anciennes configurations de collecteurs pullwss](./adapt-legacy-pullwss.md). +> Si votre plateforme comportait des collecteurs en mode pullwss et que vous souhaitez désormais utiliser des collecteurs installés par commande générée via l'interface, suivez la procédure [Adapter les anciennes configurations de collecteurs pullwss](./adapt-legacy-pullwss.md). ### Le mode pullwss -Par défaut, c'est le serveur central qui initie la connexion vers ses collecteurs. Or un collecteur qui s'exécute dans un conteneur ne peut pas accepter de connexions entrantes : ce mode ne fonctionne donc pas. +Par défaut, c'est le serveur central qui initie la connexion vers ses collecteurs. Or par exemple un collecteur qui s'exécute dans un conteneur ne peut pas accepter de connexions entrantes : ce mode ne fonctionne donc pas. Le mode **pullwss** inverse le sens de la connexion : c'est le collecteur qui ouvre une connexion WebSocket vers le serveur central, puis qui la maintient ouverte. @@ -27,13 +27,13 @@ La méthode recommandée et sécurisée consiste à utiliser HTTPS. Des certific ## Prérequis à l'installation -* Assurez-vous que votre conteneur soit conforme aux [prérequis d'installation d'un collecteur](../prerequisites.md#dimensionnement-dun-collecteur). +* Assurez-vous que votre conteneur ou votre machine hôte soit conforme aux [prérequis d'installation d'un collecteur](../prerequisites.md#dimensionnement-dun-collecteur). * Assurez-vous que le serveur central et Gorgone sont déjà installés et à jour dans la dernière version majeure. * Si ce n'est pas déjà fait, configurez le HTTPS sur votre serveur central. Cela peut être fait dans le cadre de la [procédure d'installation](../installation-of-a-central-server/using-packages.md#étape-3--mettre-en-place-la-configuration-tls), ou séparément. - Une fois HTTPS activé, mettez également à jour l'URL de l'API Gorgone : dans **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** sur le serveur central, définissez `base_url` sur `https:///centreon/api/latest/`, puis redémarrez Gorgone (`systemctl restart gorgoned`). Sinon, le serveur central rejettera chaque collecteur exécuté dans un conteneur avec une erreur `invalid token`. + Une fois HTTPS activé, mettez également à jour l'URL de l'API Gorgone : dans **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** sur le serveur central, définissez `base_url` sur `https:///centreon/api/latest/`, puis redémarrez Gorgone (`systemctl restart gorgoned`). Sinon, le serveur central rejettera ce type de collecteurs avec une erreur `invalid token`. * Le collecteur doit pouvoir joindre le serveur central. @@ -165,11 +165,11 @@ systemctl restart apache2 ## Étape 3 : Ajouter le collecteur à la configuration de la plateforme -Vous pouvez maintenant ajouter un collecteur en conteneur. Pour cela, [récupérez la commande adéquate depuis l'interface web Centreon](./using-containers.md). Le collecteur se connectera automatiquement au serveur central via pullwss. +Vous pouvez maintenant ajouter un collecteur en utilisant la commande générée automatiquement. Pour cela, [récupérez la commande depuis l'interface web Centreon](./using-containers.md). Le collecteur se connectera automatiquement au serveur central via pullwss. -## Si vous supprimez tous vos collecteurs en conteneur +## Si vous supprimez tous vos collecteurs installés via commande générée automatiquement -Si vous veniez à supprimer à l'avenir tous vos collecteurs en conteneur, n'oubliez pas d'annuler les étapes ci-dessus. +Si vous veniez à supprimer à l'avenir tous vos collecteurs installés via commande générée automatiquement, n'oubliez pas d'annuler les étapes ci-dessus. ## Dépanner l'installation diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md new file mode 100644 index 000000000000..b5a1b6fc240f --- /dev/null +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md @@ -0,0 +1,40 @@ +--- +id: vm-or-physical +title: Using a generated command (virtual or physical machine) +description: "Install a poller on a virtual or physical machine using a command generated in the Centreon interface" +--- + +> La fonctionnalité décrite ici est en phase bêta. + +Une commande personnalisée pour installer un collecteur sur une machine virtuelle ou physique peut être générée depuis l'interface de votre serveur central. + +## Prérequis + +* La machine sur laquelle vous allez installer le collecteur doit satisfaire les [prérequis d'installation d'un collecteur](../prerequisites.md#dimensionnement-dun-collecteur). +* Vous devez avoir créé un jeton de d'authentification de type collecteur. +* Sur le serveur central, [le module **pullwss** de Gorgone doit être configuré pour accepter les connexions entrantes](./pollers-containers-prerequisites.md). Cette opération n'est à réaliser qu'une seule fois, avant d'installer votre premier collecteur en utilisant une commande fournie par l'interface (qu'il soit installé sur une machine physique, une VM ou un conteneur). + +## Étape 1 : Générer la commande d'installation + +1. Sur l'interface du serveur central, cliquez sur la zone des collecteurs en haut à gauche de l'écran puis sur **Créer un collecteur**. + +![image](../../assets/installation/create-poller-banner.png) + +2. Remplissez le formulaire avec les informations concernant le collecteur : + + * **Nom du collecteur** : un nom unique pour ce collecteur. Il apparaîtra dans la liste des collecteurs. + * **Adresse du collecteur** : l'adresse de la machine hôte sur laquelle vous allez installer le collecteur. + > L'adresse du collecteur n'a aucune incidence sur la connectivité : Gorgone + > utilise PullWSS, c'est donc toujours le collecteur qui initie la connexion vers le + > serveur central, et non l'inverse. + * **Adresse du serveur central Centreon, telle que vue par ce collecteur** : l'URL que ce collecteur utilise pour joindre le serveur central, par exemple `http(s)://10.10.10.10/centreon`. Si votre serveur central est configuré en HTTPS, la connexion entre le serveur central et le collecteur sera automatiquement configurée en HTTPS aussi. + +3. Sélectionnez **VM ou physique** comme environnement du collecteur. + +4. Sélectionnez le [jeton d'authentification](#prérequis) que vous avez créé pour ce collecteur. + +5. Dans la section **Générer la commande d'installation**, cliquez sur le bouton et patientez le temps que la commande soit générée. + +6. Copiez la commande à l'aide du bouton situé en haut à droite du bloc de code et exécutez-la sur votre machine hôte. + +7. Cliquez sur le bouton **Exporter la configuration**. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md index 66f15310eed6..f18b4278a2aa 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md @@ -1,25 +1,25 @@ --- id: pollers-containers-prerequisites -title: Pollers in containers prerequisites -description: "Configuring Centreon to receive connections from pollers in containers" +title: Prerequisites for collectors installed via a generated command +description: "Configure Centreon to receive connections from collectors installed via a generated command (installed on a VM, a physical machine or a container)" --- import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -This page explains how to configure your platform to be able to use pollers in containers. You only have to perform this procedure once for the whole platform, before you install your first poller in a container. It has no impact on other poller deployment modes. +This page explains how to configure your platform to be able to use pollers installed via a command generated in the interface (whether they are installed on a VM, a physical machine or a container). You only have to perform this procedure once for the whole platform, before you install your first poller this way. It has no impact on the manual deployment mode. ## When to use this procedure This page describes what to do if the following conditions are met: * You have just installed a platform in version 26.10, or upgraded a platform that did not have any pollers in pullwss mode. -* You want to use pollers in containers for the first time. +* You want to use pollers installed via a command generated in the interface for the first time (whether they are installed on a VM, a physical machine or a container). -> If your platform had pollers in pullwss mode and you now wish to use pollers in containers, follow [Adapting legacy pullwss poller setups](./adapt-legacy-pullwss.md). +> If your platform had pollers in pullwss mode and you now wish to use pollers installed via a command generated in the interface, follow [Adapting legacy pullwss poller setups](./adapt-legacy-pullwss.md). ### Pullwss mode -By default, the central server initiates the connection to its pollers. However, a poller running in a container cannot accept incoming connections, so this mode does not work. +By default, the central server initiates the connection to its pollers. However, for example, a poller running in a container cannot accept incoming connections, so this mode does not work. **pullwss** mode reverses the direction: the poller opens a WebSocket connection to the central server and keeps it open. @@ -27,13 +27,13 @@ The recomended and secure way is to use HTTPS. This means that certificates are ## Installation requirements -* Make sure your container meets the [poller installation prerequisites](../prerequisites.md#poller-sizing). +* Make sure your container or your host machine meets the [poller installation prerequisites](../prerequisites.md#poller-sizing). * Ensure the central server and Gorgone are already installed and up to date with the latest major version. * If not already done, configure HTTPS on your central server. This can be done as part of the [installation procedure](../installation-of-a-central-server/using-packages.md#step-3-set-up-the-tls-configuration), or separately. - Once HTTPS is enabled, also update the Gorgone API URL: in **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** on the central server, set `base_url` to `https:///centreon/api/latest/`, then restart Gorgone (`systemctl restart gorgoned`). Otherwise, the central server rejects every poller in a container with an `invalid token` error. + Once HTTPS is enabled, also update the Gorgone API URL: in **/etc/centreon-gorgone/config.d/31-centreon-api.yaml** on the central server, set `base_url` to `https:///centreon/api/latest/`, then restart Gorgone (`systemctl restart gorgoned`). Otherwise, the central server rejects this type of pollers with an `invalid token` error. * The poller must be able to reach the central server. @@ -165,12 +165,11 @@ systemctl restart apache2 ## Add the poller to the platform's configuration -You can now add a poller in a container. To do so, [retrieve the correct command from the Centreon web interface](./using-containers.md). -The poller will automatically connect to the central server using pullwss. +You can now add a poller using the automatically generated command. To do so, [retrieve the command from the Centreon web interface](./using-containers.md). The poller will automatically connect to the central server using pullwss. -## If you delete all your pollers in containers +## If you delete all your collectors installed via an automatically generated command -If in the future you should delete all your pollers in containers, do not forget to undo the steps above. +If in the future you should delete all your pollers installed via an automatically generated command, do not forget to undo the steps above. ## Troubleshooting the installation diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md new file mode 100644 index 000000000000..c34b3072b5a5 --- /dev/null +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md @@ -0,0 +1,39 @@ +--- +id: vm-or-physical +title: Installing a poller on a physical or virtual machine +description: "Installing a poller on a physical or virtual machine from the Centreon interface" +--- + +> The following feature is in beta. + +A tailored command for installing a poller on a virtual or physical machine can be generated from the central server interface. + +## Prerequisites + +* The machine on which you will install the poller must fulfill the [poller installation prerequisites](../prerequisites.md#poller-sizing). +* YOu must have created a poller-type authentication token. + +## Step 1: generate the installation command + +1. In the interface of the central server, click the **Pollers** area at the top left. Then, click on **Create new poller**. + + ![image](../../assets/installation/create-poller-banner.png) + +2. Fill in the form with your poller's information: + + * **Poller name**: a unique name for this poller. It will appear in the list of pollers. + * **Poller address**: the address of the host machine where you are going to install the poller. + > The **Poller address** does not affect connectivity: Gorgone uses + > PullWSS, so the poller always initiates the connection to the central + > server, not the other way around. + * **Centreon Central address, as seen by this poller**: the URL this poller uses to reach the central server, e.g. `http(s)://10.10.10.10/centreon`. If your central server is configured in HTTPS, the connection between the central server and the poller will be automatically configured in HTTPS too. + +3. Select **VM or physical** as the poller's environment. + +4. Select the [authentication token](#prerequisites) you have created for this poller. + +5. In the **Generate installation command** section, click the button and wait for the command to be generated. + +6. Copy the command using the button at the top right of the code block and execute it on your host machine. + +7. Click **Export configuration**. diff --git a/versioned_sidebars/version-26.10-sidebars.json b/versioned_sidebars/version-26.10-sidebars.json index 5a34e206c7d5..2eadf71e1922 100644 --- a/versioned_sidebars/version-26.10-sidebars.json +++ b/versioned_sidebars/version-26.10-sidebars.json @@ -153,6 +153,18 @@ "type": "doc", "id": "installation/installation-of-a-poller/unattended-install-poller" }, + { + "type": "doc", + "id": "installation/installation-of-a-poller/vm-or-physical" + }, + { + "type": "doc", + "id": "installation/installation-of-a-poller/pollers-containers-prerequisites" + }, + { + "type": "doc", + "id": "installation/installation-of-a-poller/adapt-legacy-pullwss" + }, { "type": "category", "label": "Pollers in containers", @@ -164,17 +176,9 @@ "type": "doc", "id": "installation/installation-of-a-poller/using-containers" }, - { - "type": "doc", - "id": "installation/installation-of-a-poller/pollers-containers-prerequisites" - }, { "type": "doc", "id": "installation/installation-of-a-poller/using-containers-advanced-configuration" - }, - { - "type": "doc", - "id": "installation/installation-of-a-poller/adapt-legacy-pullwss" } ] }, From 5ce3efcf1e97ff5d88763021def7ed54081fbd4c Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 16 Oct 2026 13:59:06 +0200 Subject: [PATCH 163/179] Minor fixes --- .../installation/installation-of-a-poller/vm-or-physical.md | 4 ++-- .../installation/installation-of-a-poller/vm-or-physical.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md index b5a1b6fc240f..1e743139140c 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md @@ -11,7 +11,7 @@ Une commande personnalisée pour installer un collecteur sur une machine virtuel ## Prérequis * La machine sur laquelle vous allez installer le collecteur doit satisfaire les [prérequis d'installation d'un collecteur](../prerequisites.md#dimensionnement-dun-collecteur). -* Vous devez avoir créé un jeton de d'authentification de type collecteur. +* Vous devez avoir créé un jeton d'authentification de type collecteur. * Sur le serveur central, [le module **pullwss** de Gorgone doit être configuré pour accepter les connexions entrantes](./pollers-containers-prerequisites.md). Cette opération n'est à réaliser qu'une seule fois, avant d'installer votre premier collecteur en utilisant une commande fournie par l'interface (qu'il soit installé sur une machine physique, une VM ou un conteneur). ## Étape 1 : Générer la commande d'installation @@ -37,4 +37,4 @@ Une commande personnalisée pour installer un collecteur sur une machine virtuel 6. Copiez la commande à l'aide du bouton situé en haut à droite du bloc de code et exécutez-la sur votre machine hôte. -7. Cliquez sur le bouton **Exporter la configuration**. +7. Cliquez sur le bouton **Exporter la configuration**. Le collecteur apparaît dans la liste des collecteurs. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md index c34b3072b5a5..6b9a3ae156f8 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md @@ -36,4 +36,4 @@ A tailored command for installing a poller on a virtual or physical machine can 6. Copy the command using the button at the top right of the code block and execute it on your host machine. -7. Click **Export configuration**. +7. Click **Export configuration**. The poller appears in the list of pollers. From 9c5c4a339c18f7d5d3b2d9c20d33e0547d953d08 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 16 Oct 2026 16:47:15 +0200 Subject: [PATCH 164/179] MON-208043 --- .../installation/installation-of-a-poller/using-containers.md | 2 +- .../installation/installation-of-a-poller/using-containers.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-containers.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-containers.md index e6090f23525d..beeafcb9f1e2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-containers.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/using-containers.md @@ -47,7 +47,7 @@ fichiers `.env` et `docker-compose.yaml`, puis démarre l'ensemble des services. 2. Renseignez les informations concernant le collecteur : - * **Nom du collecteur** : un nom unique pour ce collecteur. Il apparaîtra dans la liste des collecteurs. + * **Nom du collecteur** : un nom unique pour ce collecteur. Il apparaîtra dans la liste des collecteurs. Le nom ne doit contenir ni espaces ni caractères spéciaux, et le premier caractère doit être alphanumérique. * **Adresse du collecteur** : l'adresse de la machine hôte sur laquelle vous allez installer le collecteur. > L'adresse du collecteur n'a aucune incidence sur la connectivité : Gorgone > utilise PullWSS, c'est donc toujours le collecteur qui initie la connexion vers le diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers.md index 4ad8b7953398..3c9af5800de0 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/using-containers.md @@ -47,7 +47,7 @@ and runs an installer script on the target container host. The script generates 2. Fill in the poller's information: - * **Poller name**: a unique name for this poller. It will appear in the list of pollers. + * **Poller name**: a unique name for this poller. It will appear in the list of pollers. The name must contain no spaces or special characters, and the first character must be alphanumeric. * **Poller address**: the address of the host machine where you are going to install the poller. > The **Poller address** does not affect connectivity: Gorgone uses > PullWSS, so the poller always initiates the connection to the central From bc150669aa2f4325622aff6bd9f63eabffc689c4 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 16 Oct 2026 17:12:25 +0200 Subject: [PATCH 165/179] Fix incorrect titles --- .../installation/installation-of-a-poller/vm-or-physical.md | 4 ++-- .../installation/installation-of-a-poller/vm-or-physical.md | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md index 1e743139140c..ca3ed7c4b2a2 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md @@ -1,7 +1,7 @@ --- id: vm-or-physical -title: Using a generated command (virtual or physical machine) -description: "Install a poller on a virtual or physical machine using a command generated in the Centreon interface" +title: À l'aide d'une commande générée automatiquement (VM ou machine physique) +description: "Installer un collecteur sur une machine virtuelle ou physique à l'aide d'une commande générée dans l'interface Centreon" --- > La fonctionnalité décrite ici est en phase bêta. diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md index 6b9a3ae156f8..f8afbd272ceb 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/vm-or-physical.md @@ -1,7 +1,7 @@ --- id: vm-or-physical -title: Installing a poller on a physical or virtual machine -description: "Installing a poller on a physical or virtual machine from the Centreon interface" +title: Using a generated command (virtual or physical machine) +description: "Install a poller on a virtual or physical machine using a command generated in the Centreon interface" --- > The following feature is in beta. From 12204c2a5c184c732a35c80a1074a3cf5eb00b99 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Fri, 16 Oct 2026 18:34:21 +0200 Subject: [PATCH 166/179] Update in-place migration procedure (to be transferred to The Watch once done) --- .../migrate/upgrade-debian-in-place.md | 182 +++++++++++------- 1 file changed, 117 insertions(+), 65 deletions(-) diff --git a/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md b/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md index 78b19a318665..5050e8cd2fa5 100644 --- a/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md +++ b/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md @@ -1,6 +1,6 @@ --- id: upgrade-debian-in-place -title: Upgrading Centreon and Debian (12 to 13) on the same server +title: Migrating from Debian 12 to Debian 13 on the same server, while upgrading Centreon to version 26.10 description: "In-place migration procedure for Debian - Debian 12 to 13" --- import Tabs from '@theme/Tabs'; @@ -8,7 +8,7 @@ import TabItem from '@theme/TabItem'; Use this procedure if you are running Centreon 24.04, 24.10 or 25.10 on Debian 12 and you wish to upgrade to Centreon 26.10 (only Debian 13 is supported for this version). -> Run every command as `root`. +> Run every command as `root`. Read each comment in the code blocks before running commands. +#### Configuration générale de l'ETL Dans le menu `Rapports > Monitoring Business Intelligence > Options générales > Options de l'ETL`, spécifiez les options suivantes : @@ -1329,7 +1371,7 @@ Pour activer la purge automatique des anciennes données, modifiez le fichier cr Vous pouvez exécuter ce cron quotidiennement ou hebdomadairement, en fonction du temps d'exécution du batch et de la charge générée sur le serveur. - + Redémarrez le service cron : @@ -1338,7 +1380,7 @@ systemctl restart crond ``` - + Redémarrez le service cron : @@ -1367,25 +1409,23 @@ Veuillez passer à la section suivante pour continuer l'installation. * Configurez et activez la rétention des données afin que seules les données requises soient importées et calculées. * Assurez-vous que [les données soient prêtes sur le serveur central](how-mbi-works.md#phase-1--les-données-sont-préparées-par-le-serveur-central). * Assurez-vous que le processus **gorgoned** finctionne correctement : `systemctl status gorgoned`. Si besoin, redémarrez-le: `systemctl restart gorgoned`. -* Attention, si vous créez la base de données MBI pour la première fois, vous devez importer toutes les données en une seule fois. Si vous disposez d'une grande quantité de données et/ou si vous démarrez le processus tard dans la journée, il est important de savoir que la phase de création de la base de données peut prendre un temps considérable, pouvant même se prolonger jusqu'au lendemain. Dans ce cas, vous devez désactiver [temporairement](#réactiver-lexécution-quotidienne-du-script) l'exécution quotidienne de l'ETL, jusqu'à ce que le provisionnement initial soit terminé, afin d'éviter les doublons ou d'autres problèmes. - - 1. Éditez le fichier cron **/etc/cron.d/centreon-bi-engine** et commentez la ligne suivante : +* Attention, si vous créez la base de données MBI pour la première fois, vous devez importer toutes les données en une seule fois. Si vous disposez d'une grande quantité de données et/ou si vous démarrez le processus tard dans la journée, il est important de savoir que la phase de création de la base de données peut prendre un temps considérable, pouvant même se prolonger jusqu'au lendemain. C'est pourquoi l'exécution quotidienne de l'ETL est désactivée par défaut : dans le fichier cron **/etc/cron.d/centreon-bi-engine**, la ligne suivante est commentée. Elle doit le rester jusqu'à ce que le provisionnement initial soit terminé, afin d'éviter les doublons ou d'autres problèmes. Vous la [réactiverez](#réactiver-lexécution-quotidienne-du-script) à la fin de la procédure. - ```shell - #30 4 * * * root /usr/share/centreon-bi/bin/centreonBIETL -d >> /var/log/centreon-bi/centreonBIETL.log 2>&1 - ``` + ```shell + #30 4 * * * root /usr/share/centreon-bi//bin/centreonBIETL -d >> /var/log/centreon-bi/centreonBIETL.log 2>&1 + ``` - 2. Redémarrez **crond**. + Si cette ligne n'est pas commentée (par exemple, si vous reconstruisez la base de données), commentez-la, puis redémarrez le service cron : - + ```shell systemctl restart crond ``` - + ```shell systemctl restart cron @@ -1413,7 +1453,7 @@ Vous pouvez l'exécuter en arrière-plan et rediriger la sortie du script vers u nohup /usr/share/centreon-bi//bin/centreonBIETL -r >> /var/log/centreon-bi/centreonBIETL.log 2>&1 & ``` -Regardez le fichier de log **/var/log/centreon-bi/centreonBIETL.log** : vous devriez voir des lignes avec les 4 parties suivantes : +La sortie s'affiche dans votre terminal ou, si vous avez exécuté la commande en arrière-plan, dans le fichier de log **/var/log/centreon-bi/centreonBIETL.log** (par exemple, utilisez `tail -f /var/log/centreon-bi/centreonBIETL.log` pour la suivre). Vous devriez voir des lignes avec les 4 parties suivantes : ```shell 2025-08-01 13:34:16 - INFO - [SCHEDULER] >>>>>>> start @@ -1434,27 +1474,33 @@ Regardez le fichier de log **/var/log/centreon-bi/centreonBIETL.log** : vous dev ### Réactiver l'exécution quotidienne du script -Une fois le processus de reconstruction des données terminé, vous pouvez activer le calcul des -statistiques. -Sur le serveur de reporting, éditez le fichier **/etc/cron.d/centreon-bi-engine** et décommentez la ligne suivante : +> **Cette étape est obligatoire.** Le calcul quotidien des statistiques est désactivé par défaut. Si vous ignorez cette étape, aucune statistique quotidienne ne sera calculée, et aucune erreur ne sera affichée. -```shell -#30 4 * * * root /usr/share/centreon-bi/bin/centreonBIETL -d >> /var/log/centreon-bi/centreonBIETL.log 2>&1 -``` +Une fois le processus de reconstruction des données terminé, réactivez le calcul quotidien des statistiques : - - +1. Sur le serveur de reporting, éditez le fichier **/etc/cron.d/centreon-bi-engine** et décommentez la ligne suivante (supprimez le `#` initial) : -Redémarrez le service cron sur le serveur de reporting : + ```shell + #30 4 * * * root /usr/share/centreon-bi//bin/centreonBIETL -d >> /var/log/centreon-bi/centreonBIETL.log 2>&1 + ``` + + La ligne doit maintenant ressembler à ceci : + + ```shell + 30 4 * * * root /usr/share/centreon-bi//bin/centreonBIETL -d >> /var/log/centreon-bi/centreonBIETL.log 2>&1 + ``` + +2. Redémarrez le service cron sur le serveur de reporting : + + + ```shell systemctl restart crond ``` - - -Redémarrez le service cron sur le serveur de reporting : + ```shell systemctl restart cron diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/migrate.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/migrate.md index 94e4bc9541ba..d2f158cb2292 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/migrate.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/migrate.md @@ -39,7 +39,7 @@ mysql_upgrade - Si des erreurs sont visibles, notamment sur les tables mysql innodb\_index\_stats, innodb\_table\_stats, gtid\_slave\_pos, cela peut être dû à une incompatibilité entre MySQL/MariaDB 5.5 et - MariaDB 10.11. Dans ce cas, effectuer les actions suivantes: + MariaDB 11.8. Dans ce cas, effectuer les actions suivantes: ```shell service mysql stop diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/update.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/update.md index 94c4f2dd862c..ed309d118c3a 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/update.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/update.md @@ -18,7 +18,7 @@ La mise à jour de Centreon MBI se fait en 2 étapes : 1. Mettre à jour le paquet: se connecter sur le serveur Centreon et exécuter la commande suivante : - + ```shell dnf clean all @@ -26,7 +26,7 @@ dnf update centreon-bi-server ``` - + ```shell dnf clean all @@ -34,10 +34,11 @@ dnf update centreon-bi-server ``` - + ```shell apt clean +apt update apt --only-upgrade install centreon-bi\* ``` @@ -64,7 +65,7 @@ systemctl stop gorgoned Puis mettre à jour les paquets, en exécutant la commande suivante: - + ```shell dnf clean all @@ -72,7 +73,7 @@ dnf update centreon-bi\* ``` - + ```shell dnf clean all @@ -80,10 +81,11 @@ dnf update centreon-bi\* ``` - + ```shell apt clean +apt update apt --only-upgrade install centreon-bi\* ``` @@ -93,23 +95,24 @@ apt --only-upgrade install centreon-bi\* Vous devez également mettre à jour Centreon Gorgone : - + ```shell dnf update centreon-gorgone\* ``` - + ```shell dnf update centreon-gorgone\* ``` - + ```shell +apt update apt --only-upgrade install centreon-gorgone\* ``` diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/upgrade.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/upgrade.md index 713905d795bf..2380878e1edd 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/upgrade.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/upgrade.md @@ -26,30 +26,67 @@ La montée de version de Centreon MBI se fait en 4 étapes : Voir [Introduction à la montée de version](../upgrade/introduction.md). -### Mettre à jour la clé de signature RPM - -Sous EL8, pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centreon sont changées régulièrement. Le dernier changement a eu lieu le 14 octobre 2021. Lorsque vous mettez Centreon à jour depuis une version plus ancienne, vous devez suivre la [procédure de changement de clé](../security/key-rotation.md#installation-existante), afin de supprimer l'ancienne clé et d'installer la nouvelle. - ## Étape 1 : Montée de version du paquet -Lors d'une montée de version majeure (ex: 20.10.x à 25.10.x) il faut en premier lieu mettre à jour +Lors d'une montée de version majeure (ex: 20.10.x à 26.10.x) il faut en premier lieu mettre à jour le dépôt contenant les paquets. Vous trouverez ce dépôt depuis votre compte sur notre [platefome de support, à la page **Dépôts**](https://support.centreon.com/hc/fr/categories/10341239833105-D%C3%A9p%C3%B4ts). -## Étape 2 : Mettre à jour l'interface +Sur le serveur de reporting, vous devez également installer le dépôt standard 26.10 : -1. Mettre à jour le paquet: se connecter sur le serveur Centreon et exécuter la commande suivante : + + - - +```shell +dnf install -y dnf-plugins-core +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo +dnf clean all --enablerepo=* +``` + + + ```shell -dnf clean all -dnf update centreon-bi-server +dnf install -y dnf-plugins-core +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo +dnf clean all --enablerepo=* +``` + + + + +> Si votre serveur de reporting est encore sous Debian 12, n'utilisez pas cette procédure. Suivez plutôt [Mettre à jour Centreon et Debian (12 vers 13) sur le même serveur](../migrate/upgrade-debian-in-place.md#step-11-upgrade-your-mbi-server-if-applicable) : cette procédure met à jour Debian et Centreon MBI en même temps et bascule les dépôts standard, business et plugins vers **trixie**. + +Sur Debian 13, les dépôts doivent pointer vers **trixie**. La ligne du dépôt standard est : + +```text +deb [signed-by=/etc/apt/keyrings/centreon.asc] https://packages.centreon.com/apt-standard/ trixie-26.10-stable main +``` + +La ligne du dépôt Business fournie sur le portail du support doit également utiliser **trixie**. Exécutez les commandes suivantes pour ajouter le dépôt standard : + +```shell +install -d /etc/apt/keyrings +wget -O /etc/apt/keyrings/centreon.asc https://apt-key.centreon.com +echo "deb [signed-by=/etc/apt/keyrings/centreon.asc] https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee /etc/apt/sources.list.d/centreon-26.10-stable.list +apt update +``` + +Vérifiez que toutes les lignes des dépôts Centreon utilisent **trixie** : + +```shell +grep -h "packages.centreon.com" /etc/apt/sources.list.d/*.list ``` + + +## Étape 2 : Mettre à jour l'interface + +1. Mettre à jour le paquet: se connecter sur le serveur Centreon et exécuter la commande suivante : + + ```shell @@ -58,7 +95,7 @@ dnf update centreon-bi-server ``` - + ```shell apt clean @@ -75,28 +112,8 @@ apt install --only-upgrade centreon-bi-server ## Étape 3 : Mettre à jour le serveur de reporting ### Prérequis de la version Java - - > Assurez-vous qu'une version de Java 17 (ou 18) est installée avant de commencer la procédure. - - - Pour vérifier quelle version de Java est installée, entrez la commande suivante : - - ```shell - java -version - ``` - - - Pour une mise à jour de Java en version 17 (ou 18), allez sur la [page officielle de téléchargement d'Oracle](https://www.oracle.com/java/technologies/downloads/#java17). - - - Si plusieurs versions de Java sont installées, vous devez activer la bonne version. Affichez les versions installées avec la commande suivante puis sélectionnez la version 17 (ou 18) : - - ```shell - sudo update-alternatives --config java - ``` - - Puis redémarrez le service : - - ```shell - systemctl restart cbis - ``` + +La version 26.10 nécessite Java 25. Lors de la mise à jour des paquets MBI, java (OpenJDK 25) sera automatiquement installé en tant que dépendance, si nécessaire. Le service **cbis** utilise toujours **/usr/lib/jvm/java-25-openjdk** sur Alma / RHEL / Oracle Linux et **/usr/lib/jvm/java-25-openjdk-amd64** sur Debian 13. Une fois la mise à jour terminée, vous pouvez supprimer les paquets Java 17 hérités de la version 25.10, si aucune autre application du serveur ne les utilise. ### Procédure de montée de version @@ -111,31 +128,33 @@ Vous pouvez maintenant procéder à la montée de version : 2. Puis mettez à jour les paquets, en exécutant la commande suivante : - + ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm dnf clean all -dnf update centreon-bi\* +dnf update -y centreon-bi\* centreon-perl-libs-common ``` - + ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -dnf clean all -dnf update centreon-bi\* +apt clean +apt update +apt install -y --only-upgrade centreon-bi-reporting-server centreon-perl-libs-common ``` - - +Assurez-vous que le service **cron** est installé, activé et actif (il peut être absent sur les serveurs installés à l'origine sous Debian 12) : ```shell -apt clean -apt install --only-upgrade centreon-bi-reporting-server +apt install -y cron +systemctl enable --now cron +systemctl is-active cron ``` +La dernière commande doit renvoyer `active`. + @@ -161,7 +180,23 @@ apt install --only-upgrade centreon-bi-reporting-server 2. Voir [Mettre à jour MariaDB](../upgrade/upgrade-mariadb.md). -3. Démarrez le service **cbis** : + Sur Debian 13, si le paquet demande s'il faut remplacer `/etc/mysql/mariadb.conf.d/50-server.cnf`, conservez la version actuellement installée (répondez **N**). La version du paquet définit `bind-address = 127.0.0.1`, et le serveur central ne pourrait alors plus accéder à la base de données de reporting. + +3. Vérifiez que MariaDB fonctionne : + + ```shell + systemctl is-active mariadb + ``` + + La commande doit renvoyer `active`. Sur Debian 13, vérifiez également que MariaDB écoute toujours sur toutes les interfaces : + + ```shell + grep "^bind-address" /etc/mysql/mariadb.conf.d/50-server.cnf + ``` + + La valeur doit être `0.0.0.0`. Si elle est à `127.0.0.1`, remettez-la à `0.0.0.0` et redémarrez MariaDB avec `systemctl restart mariadb`. + +4. Démarrez le service **cbis** : ```shell systemctl start cbis diff --git a/versioned_docs/version-26.10/assets/reporting/installation/centreon-mysql.cnf b/versioned_docs/version-26.10/assets/reporting/installation/centreon-mysql.cnf new file mode 100644 index 000000000000..d5ee8ea23914 --- /dev/null +++ b/versioned_docs/version-26.10/assets/reporting/installation/centreon-mysql.cnf @@ -0,0 +1,54 @@ +[mysqld] +#datadir=/var/lib/mysql +#tmpdir = /var/lib/mysql/tmp +port = 3306 + +max_heap_table_size=512M +open_files_limit = 32000 +group_concat_max_len = 1M + +#By request( all engines) +tmp_table_size=512M +sort_buffer_size = 64M +join_buffer_size = 256M + +#During load or enable keys +bulk_insert_buffer_size = 1G +myisam_sort_buffer_size=1G + +table_open_cache = 2048 +thread_cache_size = 64 + +#Time out and linked problems +connect_timeout=28800 +innodb_lock_wait_timeout=28800 +wait_timeout=28800 +interactive_timeout=28800 +max_allowed_packet = 128M + +#Low query +slow_query_log=1 +slow_query_log_file=slow-queries.log +long_query_time=120 + +#At startup +key_buffer_size = 1G +innodb_buffer_pool_size = 1G + + +#Innob DB +innodb_stats_on_metadata=0 +innodb_flush_method=O_DIRECT +innodb_flush_log_at_trx_commit=2 +innodb_log_buffer_size=1G #taille buffer redo log +innodb_log_file_size=512M +innodb_file_per_table=1 +innodb_open_files=1024 +innodb_max_dirty_pages_pct=30 + + +[mysqld_safe] +log-error=/var/log/mysqld.log +pid-file=/var/run/mysqld/mysqld.pid +innodb_lock_wait_timeout=1500 + diff --git a/versioned_docs/version-26.10/assets/reporting/installation/centreon.cnf b/versioned_docs/version-26.10/assets/reporting/installation/centreon.cnf index cf63beaea6e9..2cb442c4dbe0 100644 --- a/versioned_docs/version-26.10/assets/reporting/installation/centreon.cnf +++ b/versioned_docs/version-26.10/assets/reporting/installation/centreon.cnf @@ -45,7 +45,6 @@ innodb_flush_method=O_DIRECT innodb_flush_log_at_trx_commit=2 innodb_log_buffer_size=1G #taille buffer redo log innodb_log_file_size=512M -innodb_log_files_in_group=3 innodb_file_per_table=1 innodb_open_files=1024 innodb_max_dirty_pages_pct=30 diff --git a/versioned_docs/version-26.10/reporting/installation.md b/versioned_docs/version-26.10/reporting/installation.md index a5bd3b1e6a57..c1b11211ba7b 100644 --- a/versioned_docs/version-26.10/reporting/installation.md +++ b/versioned_docs/version-26.10/reporting/installation.md @@ -80,9 +80,9 @@ considerations. - + -- Centreon Web 25.10 +- Centreon Web 26.10 - Check that `date.timezone` is correctly configured in the `/etc/php.d/50-centreon.ini` or `/etc/php.d/20-timezone.ini` file (same as the one returned by the `timedatectl status` command). - Avoid using the following variables in the configuration file `/etc/my.cnf`. They interrupt the @@ -90,6 +90,8 @@ considerations. - wait_timeout - interactive_timeout + This only applies to the monitoring database. The [optimized configuration file](#optimize-the-database) of the reporting database sets these variables to 28800 seconds on purpose. + #### Users and groups | User | Group | @@ -98,9 +100,9 @@ considerations. | apache (existing) | centreonBI | - + -- Centreon Web 25.10 +- Centreon Web 26.10 - Check that `date.timezone` is correctly configured in the `/etc/php.d/50-centreon.ini` or `/etc/php.d/20-timezone.ini` file (same as the one returned by the `timedatectl status` command). - Avoid using the following variables in the configuration file `/etc/my.cnf`. They interrupt the @@ -108,6 +110,8 @@ considerations. - wait_timeout - interactive_timeout + This only applies to the monitoring database. The [optimized configuration file](#optimize-the-database) of the reporting database sets these variables to 28800 seconds on purpose. + #### Users and groups | User | Group | @@ -116,23 +120,25 @@ considerations. | apache (existing) | centreonBI | - + -- Centreon Web 25.10 -- Check that `date.timezone` is correctly configured in the `/etc/php/8.2/mods-available/centreon.ini` or `/etc/php/8.2/mods-available/timezone.ini` file +- Centreon Web 26.10 +- Check that `date.timezone` is correctly configured in the `/etc/php/8.4/mods-available/centreon.ini` or `/etc/php/8.4/mods-available/timezone.ini` file (same as the one returned by the `timedatectl status` command). - Avoid using the following variables in the configuration file `/etc/mysql/mariadb.cnf`. They interrupt the execution of long queries and can stop ETL or report generation jobs: - wait_timeout - interactive_timeout -- When creating the CentreonBI user, you must execute the following command: `adduser centreonBI --force-badname` + + This only applies to the monitoring database. The [optimized configuration file](#optimize-the-database) of the reporting database sets these variables to 28800 seconds on purpose. +- When creating the CentreonBI user, you must execute the following command: `adduser centreonBI --allow-bad-names` #### Users and groups | User | Group | |----------------------|------------------------------| | centreonBI (new) | www-data,centreon,centreonBI | -| apache (existing) | centreonBI | +| www-data (existing) | centreonBI | @@ -288,75 +294,37 @@ vgdisplay vg_data | grep -i free* - Firewalld: Disabled ([look here](../installation/installation-of-a-central-server/using-packages.md#configure-or-disable-the-firewall)) - SELinux: Disabled ([look here](../installation/installation-of-a-central-server/using-packages.md#disable-selinux)) -> Make sure that the reporting server and the central server have the same time zone; otherwise report publications will fail (the link to download them will be missing). -> The same time zone must be displayed with the `timedatectl` command. -> You can change the time zone with this command: -> ->```shell ->timedatectl set-timezone Europe/Paris ->``` - -Be sure to optimize MariaDB/MySQL on your reporting server. -You will need at least 12 GB of RAM in order to use the [following file](../assets/reporting/installation/centreon.cnf). - -> If you want to use a different directory than `/var/lib/mysql/`, edit the **datadir** and **tmpdir** variables in the centreon.cnf file. - -Make sure a **tmp** folder is created inside the same partition as **/var/lib/mysql**. - -> Do not set these MariaDB optimizations on your monitoring server. - -If you are using MySQL: +Make sure that the reporting server and the central server have the same time zone; otherwise report publications will fail (the link to download them will be missing). The `/etc/localtime` file must also exist on the reporting server; otherwise the `install.sh` script will fail to create the database schema. -1. Perform the following action: - - - - -In the `/etc/my.cnf.d/mysql-server.cnf` file, add: - -```shell -log_bin_trust_function_creators=1 -``` - - - +1. Set the time zone of the reporting server to the same time zone as the central server (for example, `Europe/Paris`): -In the `/etc/my.cnf.d/mysql-server.cnf` file, add: + ```shell + timedatectl set-timezone Europe/Paris + ``` -```shell -log_bin_trust_function_creators=1 -``` + If the central server uses UTC, use `Etc/UTC` rather than `UTC`. If the reporting server already reports UTC, `timedatectl set-timezone UTC` does nothing and does not create `/etc/localtime`. - - +2. Check that `/etc/localtime` exists and points to the right time zone: -In the `/etc/mysql/mysql.cnf` file, add: + ```shell + ls -l /etc/localtime + ``` -```shell -[mysqld] -log_bin_trust_function_creators=1 -``` + The output should look like this: `/etc/localtime -> ../usr/share/zoneinfo/Europe/Paris`. - - +Be sure to optimize MariaDB/MySQL on your reporting server. +You WILL need at least 12 GB of RAM in order to use the optimized configuration file. Without this, the database doesn't start. Download the file that matches your database: -2. Restart MySQL. +- MariaDB: [centreon.cnf](../assets/reporting/installation/centreon.cnf) +- MySQL: [centreon-mysql.cnf](../assets/reporting/installation/centreon-mysql.cnf) -3. Check the database to confirm this variable is applied: +You will save this file as `85-centreon-bi.cnf` when you [optimize the database](#optimize-the-database). Keep this name: the `85-` prefix makes sure the file is read after the `80-centreon.cnf` file installed by Centreon packages, so that its values are not overridden. -```shell -show global variables like 'log_bin_trust_function_creators'; -+---------------------------------+-------+ -| Variable_name | Value | -+---------------------------------+-------+ -| log_bin_trust_function_creators | ON | -``` +> If you want to use a different directory than `/var/lib/mysql/`, edit the **datadir** and **tmpdir** variables in the `85-centreon-bi.cnf` file. -If the variable is not turned on, set it manually: +Make sure a **tmp** folder is created inside the same partition as **/var/lib/mysql**. -```shell -mysql> SET GLOBAL log_bin_trust_function_creators = 1; -``` +> Do not set these MariaDB optimizations on your monitoring server. Users and groups: @@ -379,21 +347,21 @@ The actions listed in this chapter must be performed on the **Centreon Central S 2. Then run the following commands: - + ```shell dnf install centreon-bi-server ``` - + ```shell dnf install centreon-bi-server ``` - + Install **gpg**: @@ -420,9 +388,74 @@ apt install centreon-bi-server In the central database, grant trigger rights to the **centreon** user: +1. Find the host(s) on which the **centreon** user exists: + + ```shell + SELECT user, host FROM mysql.user WHERE user = 'centreon'; + ``` + +2. Grant the rights to the **centreon** user: + + ```shell + GRANT TRIGGER ON centreon.* TO 'centreon'@''; + GRANT TRIGGER ON centreon_storage.* TO 'centreon'@''; + ``` + + Replace **<host>** with the value returned by the previous query (for example, `localhost` if the database is local to the central server, or `%` or an IP address if it is remote). If the query returns several hosts, run these commands for each of them. + +### Allow function creation (MySQL only) + +If the central database uses MySQL, perform the following actions on the server that hosts it before you enable the extension. Otherwise, the installation fails with `ERROR 1419`: the extension appears as installed, but its menu and options are missing. + +1. Perform the following action: + + + + +In the `/etc/my.cnf.d/mysql-server.cnf` file, add: + +```shell +log_bin_trust_function_creators=1 +``` + + + + +In the `/etc/my.cnf.d/mysql-server.cnf` file, add: + +```shell +log_bin_trust_function_creators=1 +``` + + + + +Create the `/etc/mysql/conf.d/90-centreon-bi.cnf` file and add: + +```shell +[mysqld] +log_bin_trust_function_creators=1 +``` + + + + +2. Restart MySQL. + +3. Check the database to confirm this variable is applied: + ```shell -GRANT TRIGGER ON centreon.* TO `centreon`@'%'; -GRANT TRIGGER ON centreon_storage.* TO `centreon`@'%'; +show global variables like 'log_bin_trust_function_creators'; ++---------------------------------+-------+ +| Variable_name | Value | ++---------------------------------+-------+ +| log_bin_trust_function_creators | ON | +``` + +If the variable is not turned on, set it manually: + +```shell +mysql> SET GLOBAL log_bin_trust_function_creators = 1; ``` ### Enable the extension @@ -440,14 +473,17 @@ menu, *Reports > Monitoring Business Intelligence > General Options*: | Tabs | Option | Value | |----------------------------------------------------------------------------------------|----------------------------|--------------------------------------------------------------------------------------| | Scheduler options | CBIS Host | IP address of the reporting server | -| ETL options | Reporting engine uses a dedicated MySQL server | Yes | | -| Reporting widgets | Reporting MariaDB database | IP address of the reporting base (default = IP address of the reporting server) | +| ETL options | Reporting engine uses a dedicated MySQL server | Yes | +| Reporting widgets* | Reporting MariaDB database | IP address of the reporting base (default = IP address of the reporting server) | +| Reporting widgets* | Password | Password of the **centreonbi** database user on the reporting server | -\**The connection test will not work at this point in the installation*. +\* *The connection test will not work at this point in the installation.* -### Access to the Central database +> The **Password** field of the **Reporting widgets** tab is prefilled with **centreonbi**. This is not the password that the installation scripts (**centreonMysqlRights.pl** and **install.sh**) set for the **centreonbi** user. If you keep the default value, the widgets cannot connect to the reporting database, and the connection test fails with the following error: `Access denied for user 'centreonbi'@''`. -Download the license sent by the Centreon team to start configuring the general options. +The password can be updated in **Reporting > Monitoring Business Intelligence > General Options > Reporting widgets**. + +### Access to the Central database @@ -459,11 +495,15 @@ The MariaDB monitoring database is hosted on the central monitoring server. Run the command below to allow the reporting server to connect to the databases on the monitoring server. Use the following option: + ```shell -perl /usr/share/centreon/www/modules/centreon-bi-server/tools/centreonMysqlRights.pl --root-password=@ROOTPWD@ +perl /usr/share/centreon/www/modules/centreon-bi-server/tools/centreonMysqlRights.pl --root-password=@MYSQLROOTPASSWORD@ ``` -**@ROOTPWD@**: Root password of the MariaDB monitoring database. -If there is no password for the "root" user, do not specify the **root-password** option. + +This script will return the password for the CentreonBI user. +The password can be updated in **Reports > Monitoring Business Intelligence > General options > Reporting Widgets**. + +@MYSQLROOTPASSWORD@: The root password of the MariaDB monitoring database. If there is no password for the "root" user, do not specify the root-password option. @@ -475,11 +515,13 @@ Run the command below to allow the reporting server to connect to the databases Use the following option: ```shell -perl /usr/share/centreon/www/modules/centreon-bi-server/tools/centreonMysqlRights.pl --root-password=@ROOTPWD@ +perl /usr/share/centreon/www/modules/centreon-bi-server/tools/centreonMysqlRights.pl --root-password=@MYSQLROOTPASSWORD@ ``` -**@ROOTPWD@**: Root password of the MySQL monitoring database. -If there is no password for the "root" user, do not specify the **root-password** option. +This script will return the password for the CentreonBI user. +The password can be updated in **Reports > Monitoring Business Intelligence > General options > Reporting Widgets**. + +@MYSQLROOTPASSWORD@: The root password of the MariaDB monitoring database. If there is no password for the "root" user, do not specify the root-password option. @@ -528,7 +570,7 @@ GRANT ALL PRIVILEGES ON centreon_storage.* TO 'centreonbi'@'$BI_ENGINE_IP$'; If you use MariaDB replication for your **monitoring databases**, some views are created during the installation of Centreon MBI. You must exclude them from replication by adding the following line to the **my.cnf** -file of the slave server or mariadb.cnf on Debian 12. +file of the slave server or mariadb.cnf on Debian 13. ```shell replicate-wild-ignore-table=centreon.mod_bi_%v01,centreon.mod_bi_%V01 ``` @@ -538,7 +580,7 @@ Then, create the views manually on the slave server: ```bash mysql centreon < /tmp/view_creation.sql ``` -#### Debian 12 specific configuration +#### Debian 13 specific configuration MariaDB must listen on all interfaces instead of listening on localhost/127.0.0.1 (default value). Edit the following file: ```shell /etc/mysql/mariadb.conf.d/50-server.cnf @@ -554,7 +596,7 @@ systemctl restart mariadb If you use MySQL replication for your **monitoring databases**, some views are created during the installation of Centreon MBI. You must exclude them from replication by adding the following line to the **my.cnf** -file of the slave server or mysql.cnf on Debian 12. +file of the slave server. On Debian 13, add it to the **[mysqld]** section of a file inside `/etc/mysql/conf.d/` (for example `/etc/mysql/conf.d/centreon.cnf`). ```shell replicate-wild-ignore-table=centreon.mod_bi_%v01,centreon.mod_bi_%V01 @@ -570,15 +612,16 @@ Then, create the views manually on the slave server: mysql centreon < /tmp/view_creation.sql ``` -#### Debian 12 specific configuration +#### Debian 13 specific configuration -MySQL must listen on all interfaces instead of listening on localhost/127.0.0.1 (default value). Edit the following file: +MySQL must listen on all interfaces instead of listening on localhost/127.0.0.1 (default value). Add the following lines to a file inside `/etc/mysql/conf.d/` (for example `/etc/mysql/conf.d/centreon.cnf`): ```shell -/etc/mysql/mysql.conf.d/mysqld.cnf +[mysqld] +bind-address=0.0.0.0 ``` -Set **bind-address** to **0.0.0.0** and restart **mysql**. +Then restart **mysql**. ```shell systemctl restart mysql @@ -640,45 +683,51 @@ During database installation, note the password for the database's **root** acco 1. Install the standard repository: - + ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` - + ```shell dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el9/centreon-25.10.repo +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo dnf clean all --enablerepo=* dnf update ``` - + Install the required packages: ```shell -apt install lsb-release ca-certificates apt-transport-https software-properties-common wget gnupg2 +apt update && apt install -y lsb-release ca-certificates apt-transport-https wget gnupg2 curl cron +systemctl enable --now cron ``` -Install the Centreon repositories: +Check that the **cron** service is active: ```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list -echo "deb https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list +systemctl is-active cron ``` -Then import the repository key: +The command must return `active`. + +Install the Centreon repositories: ```shell -wget -O- https://apt-key.centreon.com | gpg --dearmor | tee /etc/apt/trusted.gpg.d/centreon.gpg > /dev/null 2>&1 +install -d /etc/apt/keyrings +wget -O /etc/apt/keyrings/centreon.asc https://apt-key.centreon.com + +echo "deb [signed-by=/etc/apt/keyrings/centreon.asc] https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee /etc/apt/sources.list.d/centreon-26.10-stable.list +echo "deb [signed-by=/etc/apt/keyrings/centreon.asc] https://packages.centreon.com/apt-plugins-stable/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/centreon-plugins.list apt update ``` @@ -694,27 +743,27 @@ apt update #### Install dependencies - + Install the **epel** repository: ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` Enable the **codeready-builder** repositories: ```shell -subscription-manager repos --enable codeready-builder-for-rhel-8-x86_64-rpms +subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms ``` - + Install the **epel** repository: ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` Enable the **codeready-builder** repositories: @@ -724,55 +773,55 @@ dnf config-manager --set-enabled ol8_codeready_builder ``` - + Install the **epel** repository: ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm ``` -Enable the **powertools** repository: +Enable the **crb** repository: ```shell -dnf config-manager --set-enabled 'powertools' +dnf config-manager --set-enabled 'crb' ``` - + Install the **epel** repository: ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm ``` Enable the **codeready-builder** repositories: ```shell -subscription-manager repos --enable codeready-builder-for-rhel-9-x86_64-rpms +subscription-manager repos --enable codeready-builder-for-rhel-10-x86_64-rpms ``` - + Install the **epel** repository: ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm ``` Enable the **codeready-builder** repositories: ```shell -dnf config-manager --set-enabled ol9_codeready_builder +dnf config-manager --set-enabled ol10_codeready_builder ``` - + Install the **epel** repository: ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm ``` Run the following command: @@ -782,7 +831,7 @@ dnf config-manager --set-enabled 'crb' ``` - + No dependencies need to be installed. @@ -794,21 +843,21 @@ No dependencies need to be installed. - + ```shell dnf install MariaDB-server MariaDB-client ``` - + ```shell dnf install MariaDB-server MariaDB-client ``` - + ```shell apt update @@ -823,10 +872,10 @@ apt install mariadb-server mariadb-client - + ```shell -dnf install https://dev.mysql.com/get/mysql84-community-release-el8-1.noarch.rpm +dnf install https://dev.mysql.com/get/mysql84-community-release-el9-1.noarch.rpm dnf config-manager --enable mysql-8.4-lts-community dnf module disable mysql dnf install mysql-community-server @@ -834,7 +883,7 @@ systemctl start mysqld ``` - + ```shell dnf install -y mysql-server mysql @@ -844,18 +893,14 @@ echo "default-authentication-plugin=mysql_native_password" >> /etc/my.cnf.d/mysq systemctl daemon-reload systemctl restart mysqld systemctl list-units --type=service | grep -i mysql -sudo sed -Ei 's/LimitNOFILE\s*=\s*[0-9]+/LimitNOFILE = 32000/' /usr/lib/systemd/system/mysqld -sudo systemctl start mysqld -sudo systemctl status mysqld ``` - + ```shell apt update apt install -y centreon-mysql -# Sélectionner "Use Legacy Authentication Method" systemctl daemon-reload systemctl restart mysql ``` @@ -869,22 +914,21 @@ systemctl restart mysql #### Install the MBI module on the MBI server - + ```shell -echo "deb https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-25.10-stable main" | tee -a /etc/apt/sources.list.d/centreon-25.10-stable.list dnf install centreon-bi-reporting-server ``` - + ```shell dnf install centreon-bi-reporting-server ``` - + ```shell apt update @@ -894,21 +938,7 @@ apt install centreon-bi-reporting-server -Then, ensure a version of Java 17 (or 18) is installed before you start the procedure. - - - If you need to check the Java version, enter the following command: - - ```shell - java -version - ``` - - - If you need to upgrade the Java installation to Java 17 (or 18), go to the [Oracle official download](https://www.oracle.com/java/technologies/downloads/#java17) page. - - - If several Java versions are installed, you need to activate the right version. Display the installed versions using the following command and select the Java 17 (or 18) version: - - ```shell - sudo update-alternatives --config java - ``` +When installing 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. #### Enable services @@ -929,10 +959,10 @@ systemctl start gorgoned && systemctl enable gorgoned - + -Make sure that the optimized configuration [file](../assets/reporting/installation/centreon.cnf) provided -in the prerequisites is present in `/etc/my.cnf.d/`, then restart the MariaDB service: +Copy the [optimized configuration file](../assets/reporting/installation/centreon.cnf) provided +in the prerequisites to `/etc/my.cnf.d/85-centreon-bi.cnf`, then restart the MariaDB service: ```shell systemctl restart mariadb @@ -964,10 +994,10 @@ socket=$PATH_TO_SOCKET$ ``` - + -Make sure that the optimized configuration [file](../assets/reporting/installation/centreon.cnf) provided -in the prerequisites is present in `/etc/my.cnf.d/`, then restart the MariaDB service: +Copy the [optimized configuration file](../assets/reporting/installation/centreon.cnf) provided +in the prerequisites to `/etc/my.cnf.d/85-centreon-bi.cnf`, then restart the MariaDB service: ```shell systemctl restart mariadb @@ -999,16 +1029,10 @@ socket=$PATH_TO_SOCKET$ ``` - - -Make sure that the optimized configuration [file](../assets/reporting/installation/centreon.cnf) -provided in the requirements is present in `/etc/mysql/mariadb.conf.d/`. + -Rename the file to `80-centreon.cnf`: - -```shell -mv centreon.cnf 80-centreon.cnf -``` +Copy the [optimized configuration file](../assets/reporting/installation/centreon.cnf) +provided in the prerequisites to `/etc/mysql/mariadb.conf.d/85-centreon-bi.cnf`. MariaDB should listen to all interfaces instead of localhost/127.0.0.1, which is the default. Edit the following file: @@ -1052,9 +1076,9 @@ socket=$PATH_TO_SOCKET$ - + -Ensure that the [optimized configuration file](../assets/reporting/installation/centreon.cnf) provided in the prerequisites is present in `/etc/my.cnf.d/`, then restart the MySQL service: +Copy the [optimized configuration file](../assets/reporting/installation/centreon-mysql.cnf) provided in the prerequisites to `/etc/my.cnf.d/85-centreon-bi.cnf`, then restart the MySQL service: ```shell systemctl restart mysql @@ -1066,7 +1090,7 @@ You must modify the **LimitNOFILE** limitation. Changing this option in `/etc/my mkdir -p /etc/systemd/system/mysql.service.d/ echo -ne "[Service]\nLimitNOFILE=32000\n" | tee /etc/systemd/system/mysql.service.d/limits.conf systemctl daemon-reload -systemctl restart mysql +systemctl enable mysql ``` If the MySQL service fails to start, delete the *ib_logfile* files (MySQL MUST be stopped) and then restart MySQL again: @@ -1083,21 +1107,11 @@ socket=$PATH_TO_SOCKET$ ``` - + -Ensure that the [optimized configuration file](../assets/reporting/installation/centreon.cnf) provided in the prerequisites is present in `/etc/my.cnf.d/`, then restart the MySQL service: - - -```shell -systemctl restart mysql -``` - -You must modify the **LimitNOFILE** limitation. Changing this option in `/etc/my.cnf` will NOT work. +Copy the [optimized configuration file](../assets/reporting/installation/centreon-mysql.cnf) provided in the prerequisites to `/etc/my.cnf.d/85-centreon-bi.cnf`, then restart the MySQL service: ```shell -mkdir -p /etc/systemd/system/mysql.service.d/ -echo -ne "[Service]\nLimitNOFILE=32000\n" | tee /etc/systemd/system/mysql.service.d/limits.conf -systemctl daemon-reload systemctl restart mysql ``` @@ -1115,35 +1129,30 @@ socket=$PATH_TO_SOCKET$ ``` - + -Ensure that the [optimized configuration file](../assets/reporting/installation/centreon.cnf) provided in the prerequisites is present in `/etc/mysql/mysql.conf.d/`. +Copy the [optimized configuration file](../assets/reporting/installation/centreon-mysql.cnf) provided in the prerequisites to `/etc/mysql/conf.d/85-centreon-bi.cnf`. Do not name it `80-centreon.cnf`: this would overwrite the file installed by the **centreon-mysql** package. -Rename the file as `80-centreon.cnf`: +MySQL must listen to all interfaces instead of localhost/127.0.0.1, which is the default value. Add the following lines to a file inside `/etc/mysql/conf.d/` (for example `/etc/mysql/conf.d/centreon.cnf`): ```shell -mv centreon.cnf 80-centreon.cnf -``` - -MySQL must listen to all interfaces instead of localhost/127.0.0.1, which is the default value. Edit the following file: - -```shell -/etc/mysql/mysql.conf.d/mysqld.cnf +[mysqld] +bind-address=0.0.0.0 ``` -Set the **bind-address** parameter to **0.0.0.0** and restart mysql. +Then restart mysql. ```shell systemctl restart mysql ``` -You must modify the **LimitNOFILE** limitation. Changing this option in `/etc/my.cnf` will NOT work. +You must modify the **LimitNOFILE** limitation. Changing this option in the MySQL configuration files (`/etc/mysql/my.cnf` or `/etc/mysql/conf.d/`) will NOT work. ```shell mkdir -p /etc/systemd/system/mysql.service.d/ echo -ne "[Service]\nLimitNOFILE=32000\n" | tee /etc/systemd/system/mysql.service.d/limits.conf systemctl daemon-reload -systemctl restart mysql +systemctl enable mysql ``` If the MySQL service fails to start, delete the *ib_logfile* files (MySQL MUST be stopped) and then restart MySQL again: @@ -1153,7 +1162,7 @@ rm -f /var/lib/mysql/ib_logfile* systemctl start mysql ``` -If you are using a specific socket file for MySQL, edit the `/etc/my.cnf` file and add the following to the [client] section: +If you are using a specific socket file for MySQL, add the following to the [client] section of a file inside `/etc/mysql/conf.d/` (for example `/etc/mysql/conf.d/centreon.cnf`): ```shell socket=$PATH_TO_SOCKET$ @@ -1168,7 +1177,7 @@ socket=$PATH_TO_SOCKET$ ### Secure the database It is mandatory to secure the root access of the database before installing Centreon. -If you use a local database, execute the following command on the central server, otherwise on the database server: +Execute the following commands on the reporting server: @@ -1177,17 +1186,43 @@ If you use a local database, execute the following command on the central server mariadb-secure-installation ``` +Answer **yes** to all questions except "Disallow root login remotely?" + -```shell -mysql_secure_installation -``` +1. Define the password you want for the database **root** user (replace **my_password** by your own in the following command): + + ```shell + db_root_password='my_password' + mysql_root_auth=(--ssl-mode=DISABLED -u root) + if ! mysql --ssl-mode=DISABLED -u root -e "SELECT 1" >/dev/null 2>&1; then + mysql_temp_pw=$(grep 'temporary password is generated for root@localhost' /var/log/mysqld.log \ + 2>/dev/null | tail -1 | sed -E 's/.*root@localhost: //') + if [ -z "$mysql_temp_pw" ]; then + echo "Could not authenticate to MySQL as root" >&2 + exit 1 + fi + mysql_root_auth=(--ssl-mode=DISABLED --connect-expired-password -u root -p"${mysql_temp_pw}") + fi + ``` + +2. Then replace the default autogenerated password with yours: + + ```shell + mysql "${mysql_root_auth[@]}" --verbose < -- Answer **yes** to all questions except "Disallow root login remotely?" - It is mandatory to define a password for the **root** user of the database. You will need this password during the [web-installation](../installation/web-and-post-installation.md). > See advanced procedures to [Secure your MBI platform](../reporting/secure-your-mbi-platform.md). @@ -1196,7 +1231,7 @@ mysql_secure_installation #### Start configuring -Make sure the MariaDB reporting system is started and then run the commands below and answer the questions: +Make sure the MariaDB reporting system is started and then run the commands below and answer the questions. For the "database type for reporting databse" select MySQL or MariaDB, do not leave the default option "Automatic Discovery" as this will result in an error. ```shell /usr/share/centreon-bi/config/install.sh @@ -1209,7 +1244,7 @@ Once the installation is complete, continue to the next chapter to configure the #### Problem with the SSH exchange key -In some cases, SSH key exchange fails. +In some cases, SSH key exchange fails, for example when password authentication is disabled on the monitoring server (`PasswordAuthentication no` in `/etc/ssh/sshd_config`). To solve the problem, do the following manually: Switch to the `centreonBI` user: @@ -1233,10 +1268,10 @@ cat /home/centreonBI/.ssh/id_ed25519.pub Now, **on the monitoring server**: -Create a `.ssh` folder that `centreonBI` will own, restrict permissions on this folder and paste into the `authorized_keys` file the contents of its public key on the reporting server (shown earlier): +Create a `.ssh` folder that `centreonBI` will own, restrict permissions on this folder and on the `authorized_keys` file, and paste into the `authorized_keys` file the contents of its public key on the reporting server (shown earlier): ```bash -mkdir -p /home/centreonBI/.ssh/ && chown centreonBI: /home/centreonBI/.ssh/ && chmod 700 /home/centreonBI/.ssh/ && echo "@reporting pub key content@" > /home/centreonBI/.ssh/authorized_keys +mkdir -p /home/centreonBI/.ssh/ && chown centreonBI: /home/centreonBI/.ssh/ && chmod 700 /home/centreonBI/.ssh/ && echo "@reporting pub key content@" > /home/centreonBI/.ssh/authorized_keys && chown centreonBI: /home/centreonBI/.ssh/authorized_keys && chmod 600 /home/centreonBI/.ssh/authorized_keys ``` The key exchange must then be validated by a first connection that will accept the SSH server signature. @@ -1249,7 +1284,6 @@ ssh centreonBI@@MONITORING_SERVER@ Then exit the `centreonBI` session with `exit` or `Ctrl-D` on both servers. To continue, run the installation script (`/usr/share/centreon-bi/config/install.sh`) as above and answer **Yes** when asked to proceed with the SSH key exchange. -You will get an error when creating the USER, because it already exists. This is not a blocking step. ## Step 4: Configure the ETL @@ -1335,7 +1369,7 @@ Avoid scheduled periods for statistical calculations with Centreon MBI ETL and r You can run this cron daily or weekly, depending on the batch execution time and the load generated on the server. - + Restart the cron service: @@ -1344,7 +1378,7 @@ systemctl restart crond ``` - + Restart the cron service: @@ -1371,24 +1405,23 @@ systemctl restart cron * Configure the ETL and enable data retention so that only the required data is imported and calculated. * Make sure that [the data on the central server is ready](how-mbi-works.md#phase-1-data-is-prepared-by-the-central-server). * Make sure that the **gorgoned** process works fine: `systemctl status gorgoned`. If needed, restart it: `systemctl restart gorgoned`. -* Bear in mind that if you are building the MBI database for the first time, you have to import all of the data in one go. If you have a large amount of data and/or if you start the process late in the day, it's important to be aware that the database building phase might take a significant amount of time, possibly extending into the next day. In this case, you need to disable the daily build [temporarily](#reenable-daily-script-execution), until the initial build is complete, so as to avoid duplicate entries or other problems. - 1. Edit the **/etc/cron.d/centreon-bi-engine** cronfile and comment out the following line: +* Bear in mind that if you are building the MBI database for the first time, you have to import all of the data in one go. If you have a large amount of data and/or if you start the process late in the day, it's important to be aware that the database building phase might take a significant amount of time, possibly extending into the next day. This is why the daily build is disabled by default: in the **/etc/cron.d/centreon-bi-engine** cronfile, the following line is commented out. It must stay commented out until the initial build is complete, so as to avoid duplicate entries or other problems. You will [reenable it](#reenable-daily-script-execution) at the end of the procedure. - ```shell - #30 4 * * * root /usr/share/centreon-bi/bin/centreonBIETL -d >> /var/log/centreon-bi/centreonBIETL.log 2>&1 - ``` + ```shell + #30 4 * * * root /usr/share/centreon-bi//bin/centreonBIETL -d >> /var/log/centreon-bi/centreonBIETL.log 2>&1 + ``` - 2. Restart **crond**. + If this line is not commented out (for example, if you are rebuilding the database), comment it out, then restart the cron service: - + ```shell systemctl restart crond ``` - + ```shell systemctl restart cron @@ -1416,7 +1449,7 @@ You may want to run it in the background and redirect the script's output to a l nohup /usr/share/centreon-bi//bin/centreonBIETL -r >> /var/log/centreon-bi/centreonBIETL.log 2>&1 & ``` -Go to the **/var/log/centreon-bi/centreonBIETL.log** log file: you should see some lines appear with 4 parts like: +The output is displayed in your terminal or, if you ran the command in the background, in the **/var/log/centreon-bi/centreonBIETL.log** log file (for example, use `tail -f /var/log/centreon-bi/centreonBIETL.log` to follow it). You should see some lines appear with 4 parts like: ```shell 2025-08-01 13:34:16 - INFO - [SCHEDULER] >>>>>>> start @@ -1437,25 +1470,33 @@ Go to the **/var/log/centreon-bi/centreonBIETL.log** log file: you should see so ### Reenable daily script execution -Once the data building process is complete, you can reenable the daily calculation of statistics. +> **This step is mandatory.** The daily calculation of statistics is disabled by default. If you skip this step, no daily statistics will be calculated, and no error will be displayed. -1. On the reporting server, edit the **/etc/cron.d/centreon-bi-engine** file and uncomment the following line: +Once the data building process is complete, reenable the daily calculation of statistics: + +1. On the reporting server, edit the **/etc/cron.d/centreon-bi-engine** file and uncomment the following line (remove the leading `#`): + + ```shell + #30 4 * * * root /usr/share/centreon-bi//bin/centreonBIETL -d >> /var/log/centreon-bi/centreonBIETL.log 2>&1 + ``` + + The line should now look like this: ```shell - #30 4 * * * root /usr/share/centreon-bi/bin/centreonBIETL -d >> /var/log/centreon-bi/centreonBIETL.log 2>&1 + 30 4 * * * root /usr/share/centreon-bi//bin/centreonBIETL -d >> /var/log/centreon-bi/centreonBIETL.log 2>&1 ``` 2. Restart the cron service on the reporting server: - + ```shell systemctl restart crond ``` - + ```shell systemctl restart cron @@ -1464,6 +1505,8 @@ systemctl restart cron +> Make sure the **centreonBIETL** batch only starts once **eventReportBuilder** has ended on the monitoring server (check the cron file **etc/cron.d/centreon** on the monitoring server). + The installation of Centreon MBI is now complete. You can start creating [jobs](concepts.md#jobs) in order to generate reports. See [the tutorial](../getting-started/analyze-resources-availability.md). ## Monitor your MBI server with Centreon diff --git a/versioned_docs/version-26.10/reporting/migrate.md b/versioned_docs/version-26.10/reporting/migrate.md index ea8b43fe0ed0..8104c37509e7 100644 --- a/versioned_docs/version-26.10/reporting/migrate.md +++ b/versioned_docs/version-26.10/reporting/migrate.md @@ -39,7 +39,7 @@ mysql_upgrade - If you see errors, especially on the following tables mysql innodb_index_stats, innodb_table_stats, gtid_slave_pos, it might be caused by an incompatibility between MySQL/MariaDB 5.5 and - MariaDB 10.11. In that case, follow the procedure below: + MariaDB 11.8. In that case, follow the procedure below: ```shell service mysql stop diff --git a/versioned_docs/version-26.10/reporting/update.md b/versioned_docs/version-26.10/reporting/update.md index 22a67f32f65f..e5ea4d71183c 100644 --- a/versioned_docs/version-26.10/reporting/update.md +++ b/versioned_docs/version-26.10/reporting/update.md @@ -18,7 +18,7 @@ Centreon MBI is updated in two steps: 1. Update the package, run the following commands: - + ```shell dnf clean all @@ -26,7 +26,7 @@ dnf update centreon-bi-server ``` - + ```shell dnf clean all @@ -34,10 +34,11 @@ dnf update centreon-bi-server ``` - + ```shell apt clean +apt update apt --only-upgrade install centreon-bi\* ``` @@ -65,7 +66,7 @@ systemctl stop gorgoned Then run the following commands: : - + ```shell dnf clean all @@ -73,7 +74,7 @@ dnf update centreon-bi\* ``` - + ```shell dnf clean all @@ -81,10 +82,11 @@ dnf update centreon-bi\* ``` - + ```shell apt clean +apt update apt --only-upgrade install centreon-bi\* ``` @@ -94,23 +96,24 @@ apt --only-upgrade install centreon-bi\* You also need to update Centreon Gorgone: - + ```shell dnf update centreon-gorgone\* ``` - + ```shell dnf update centreon-gorgone\* ``` - + ```shell +apt update apt --only-upgrade install centreon-gorgone\* ``` diff --git a/versioned_docs/version-26.10/reporting/upgrade.md b/versioned_docs/version-26.10/reporting/upgrade.md index d870968993b0..77714636cb72 100644 --- a/versioned_docs/version-26.10/reporting/upgrade.md +++ b/versioned_docs/version-26.10/reporting/upgrade.md @@ -26,29 +26,66 @@ The upgrade of Centreon MBI consists of four steps: See [Introduction to upgrade](../upgrade/introduction.md). -### Update the RPM signing key - -On EL8, 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](../security/key-rotation.md#existing-installation) to remove the old key and install the new one. - ## Step 1: Update the repository -When you upgrade from a previous major version to 25.10.x, you first need to update the repository on your Central & Reporting servers. +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](https://support.centreon.com/hc/en-us/categories/10341239833105-Repositories). -## Step 2: Upgrade the extension interface +On the reporting server, you also need to install the 26.10 standard repository: -1. Update the package, run the following commands: + + - - +```shell +dnf install -y dnf-plugins-core +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo +dnf clean all --enablerepo=* +``` + + + ```shell -dnf clean all -dnf update centreon-bi-server +dnf install -y dnf-plugins-core +dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo +dnf clean all --enablerepo=* +``` + + + + +> If your reporting server still runs Debian 12, do not use this procedure. Follow [Upgrading Centreon and Debian (12 to 13) on the same server](../migrate/upgrade-debian-in-place.md#step-11-upgrade-your-mbi-server-if-applicable) instead: it upgrades Debian and Centreon MBI together and switches the standard, business and plugins repositories to **trixie**. + +On Debian 13, the repositories must point to **trixie**. The standard repository line is: + +```text +deb [signed-by=/etc/apt/keyrings/centreon.asc] https://packages.centreon.com/apt-standard/ trixie-26.10-stable main +``` + +The Business repository line you get from the support portal must also use **trixie**. Run the following commands to add the standard repository: + +```shell +install -d /etc/apt/keyrings +wget -O /etc/apt/keyrings/centreon.asc https://apt-key.centreon.com +echo "deb [signed-by=/etc/apt/keyrings/centreon.asc] https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee /etc/apt/sources.list.d/centreon-26.10-stable.list +apt update +``` + +Check that all Centreon repository lines use **trixie**: + +```shell +grep -h "packages.centreon.com" /etc/apt/sources.list.d/*.list ``` + + +## Step 2: Upgrade the extension interface + +1. Update the package, run the following commands: + + ```shell @@ -57,7 +94,7 @@ dnf update centreon-bi-server ``` - + ```shell apt clean @@ -75,28 +112,8 @@ Update button to update the extension and the widgets. ## Step 3: Upgrade the reporting server ### Java version requirement - - > Ensure a version of Java 17 (or 18) is installed before you start the procedure. - - - If you need to check the Java version, enter the following command: - - ```shell - java -version - ``` - - - If you need to upgrade the Java installation to Java 17 (or 18), go to the [Oracle official download](https://www.oracle.com/java/technologies/downloads/#java17) page. - - - If several Java versions are installed, you need to activate the right version. Display the installed versions using the following command and select the Java 17 (or 18) version: - - ```shell - sudo update-alternatives --config java - ``` - - Then restart the service: - - ```shell - systemctl restart cbis - ``` + +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 @@ -111,31 +128,33 @@ Now you can start the upgrade process: 2. Then run the following commands: - + ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm +dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm dnf clean all -dnf update centreon-bi\* +dnf update -y centreon-bi\* centreon-perl-libs-common ``` - + ```shell -dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm -dnf clean all -dnf update centreon-bi\* +apt clean +apt update +apt install -y --only-upgrade centreon-bi-reporting-server centreon-perl-libs-common ``` - - +Make sure the **cron** service is installed, enabled and active (it may be missing on servers originally installed on Debian 12): ```shell -apt clean -apt install --only-upgrade centreon-bi-reporting-server +apt install -y cron +systemctl enable --now cron +systemctl is-active cron ``` +The last command must return `active`. + @@ -161,7 +180,23 @@ apt install --only-upgrade centreon-bi-reporting-server 2. See [Upgrading MariaDB](../upgrade/upgrade-mariadb.md). -3. Start the **cbis** service: + On Debian 13, if the package asks whether to replace `/etc/mysql/mariadb.conf.d/50-server.cnf`, keep your currently installed version (answer **N**). The package version sets `bind-address = 127.0.0.1`, and the central server would then no longer be able to reach the reporting database. + +3. Check that MariaDB is running: + + ```shell + systemctl is-active mariadb + ``` + + The command must return `active`. On Debian 13, also check that MariaDB still listens on all interfaces: + + ```shell + grep "^bind-address" /etc/mysql/mariadb.conf.d/50-server.cnf + ``` + + The value must be `0.0.0.0`. If it is `127.0.0.1`, set it back to `0.0.0.0` and restart MariaDB with `systemctl restart mariadb`. + +4. Start the **cbis** service: ```shell systemctl start cbis From f99dc060648746d6bcdc4e144516219fa2b7c33a Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 19 Oct 2026 11:29:56 +0200 Subject: [PATCH 169/179] In-place Debian migration cleanup (before transfer to The Watch) --- .../migrate/upgrade-debian-in-place.md | 207 ++++++++++++------ 1 file changed, 136 insertions(+), 71 deletions(-) diff --git a/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md b/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md index 5050e8cd2fa5..9ebe4c94302e 100644 --- a/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md +++ b/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md @@ -424,14 +424,40 @@ If you have a local database, run this on the central server. If your database i This step is the database health check after the upgrade. It confirms that the new MariaDB 11.8 is running, writable, upgraded internally, and that the Centreon databases are still there. The comments give the expected result, with the MySQL variant after the dash. + + + ```bash -systemctl is-active mariadb # active — [MySQL] mysql -mariadb -e "SELECT @@version, @@read_only" # 11.8.x, 0 — [MySQL] 8.4.x, 0 -mariadb-upgrade --check-if-upgrade-is-needed && echo "run: mariadb-upgrade" || echo "done" # [MySQL] skip +# check that mariadb is active (for MySQL, replace "mariadb" with "mysql") +systemctl is-active mariadb +# check that the MariaDB versin is 11.8.x, and read-only is 0 +mariadb -e "SELECT @@version, @@read_only" +# check whether MariaDB’s system tables need upgrading, and print a message telling you what to do +mariadb-upgrade --check-if-upgrade-is-needed && echo "run: mariadb-upgrade" || echo "done" +# check which Centreon databases exist mariadb -e "SHOW DATABASES" | grep -E "^centreon(_storage|_map)?$" -journalctl -u mariadb --since "-1h" | grep -iE "error|warning" | tail -n 20 # [MySQL] tail /var/log/mysql/error.log +# show the most recent errors and warnings that MariaDB logged in the last hour +journalctl -u mariadb --since "-1h" | grep -iE "error|warning" | tail -n 20 +``` + + + + +```bash +# check that MySQL is active +systemctl is-active mysql +# check that the MySQL versin is 8.4.x, and read-only is 0 +mysql -e "SELECT @@version, @@read_only" +# check which Centreon databases exist +mysql -e "SHOW DATABASES" | grep -E "^centreon(_storage|_map)?$" +# look for recent MySQL errors and warnings in two different places, because MySQL can log to either one (or both) depending on its configuration +journalctl -u mysql --since "-1h" | grep -iE "error|warning" | tail -n 20 +grep -iE "error|warning" /var/log/mysql/error.log | tail -n 20 ``` + + + * If MariaDB isn't active, or the version query shows read_only = 1 (the database refuses writes), use [the troubleshooting table from step 4](#45-troubleshooting). * If the check prints "run: mariadb-upgrade", run mariadb-upgrade. It takes its login details from /root/.my.cnf. When it works, it finishes with return code 0 after 8 phases, and running the check again reports that no upgrade is needed. Why this happens: the MariaDB package normally updates the database's internal system tables during the upgrade. It can't do this if the MariaDB root account has a password, and it won't warn you. MariaDB 11.8 then runs on system tables still in the 10.11 format. If root logs in through unix_socket (no password), the package does it by itself, as it did on the database servers we tested. @@ -454,21 +480,19 @@ First, clear your browser cache so you don't see old pages from 25.10. (If you u To restart Centreon on the new version, run these commands on the central server: ```bash +# clear the web application cache. cd /usr/share/centreon && sudo -u www-data php bin/console cache:clear +# let the web server and Broker access each other's files. usermod -a -G centreon-broker www-data usermod -a -G www-data centreon-broker -sudo -u www-data php /usr/share/centreon/bin/console w:m:c --dry-run # "No invalid commands found." +# check for invalid Engine and Broker commands. If the check lists any, run it again without **--dry-run** to remove them. (`w:m:c` is short for `web:monitoring-server:clean-engine-broker-command`.) +sudo -u www-data php /usr/share/centreon/bin/console w:m:c --dry-run +# restart the monitoring services systemctl restart cbd centengine gorgoned centreontrapd -systemctl start centreon-map-engine # [MAP] +# If you have MAP, start the MAP engine +systemctl start centreon-map-engine ``` -What these commands do: - -* Clear the web application cache. -* Let the web server and Broker access each other's files. -* Check for invalid Engine and Broker commands. If the check lists any, run it again without **--dry-run** to remove them. (`w:m:c` is short for `web:monitoring-server:clean-engine-broker-command`.) -* Restart the monitoring services, and start the MAP engine if you use MAP. - If you use MAP, check that it works: * `systemctl is-active centreon-map-engine` should print `active`. @@ -479,12 +503,12 @@ If you use MAP, check that it works: 1. Export the central server's configuration with **Generate**, **Move export files** and **Restart all** checked. If you skip **Move export files**, the new files stay in `/var/cache/centreon/config` and Engine 26.10 keeps using the old configuration. -2. Restart the services one last time +2. Restart the services one last time: - ```bash - systemctl restart cbd centengine centreontrapd gorgoned - systemctl start cron - ``` + ```bash + systemctl restart cbd centengine centreontrapd gorgoned + systemctl start cron + ``` This makes the services load the new configuration and turns scheduled jobs (cron) back on. @@ -492,41 +516,64 @@ If you use MAP, check that it works: 1. Run these commands on the central server: - ```bash - systemctl enable centengine cbd gorgoned centreontrapd snmptrapd.socket php8.4-fpm apache2 cron - systemctl enable centreon-map-engine 2>/dev/null # [MAP] - systemctl enable mariadb # [local database] or local MAP database — [MySQL] mysql - diff <(awk '{print $1}' /root/upgrade-2610-backup/enabled-units.txt | sort) \ - <(systemctl list-unit-files --state=enabled | awk '{print $1}' | sort) # php8.2 → php8.4 expected - systemctl reboot - ``` + + + +```bash +# make sure all Centreon services, the web server, PHP 8.4, cron and the database start automatically at boot +systemctl enable centengine cbd gorgoned centreontrapd snmptrapd.socket php8.4-fpm apache2 cron +# if you have MAP, set the Centreon MAP engine service to start automatically at boot, while hiding any messages it prints +systemctl enable centreon-map-engine 2>/dev/null +# ruen this on the machine that hosts each database: it sets the database service to start automatically each time the server boots +systemctl enable mariadb +# Compare the list of services enabled before the upgrade (saved in step 1.2) with the current list. The only expected difference is php8.2-fpm replaced by php8.4-fpm. Anything else deserves a look. +diff <(awk '{print $1}' /root/upgrade-2610-backup/enabled-units.txt | sort) \ + <(systemctl list-unit-files --state=enabled | awk '{print $1}' | sort) # php8.2 → php8.4 expected + +# reboot the server +systemctl reboot +``` + + + - What these commands do: +```bash +# make sure all Centreon services, the web server, PHP 8.4, cron and the database start automatically at boot +systemctl enable centengine cbd gorgoned centreontrapd snmptrapd.socket php8.4-fpm apache2 cron +# if you have MAP, set the Centreon MAP engine service to start automatically at boot, while hiding any messages it prints +systemctl enable centreon-map-engine 2>/dev/null +# ruen this on the machine that hosts each database: it sets the database service to start automatically each time the server boots +systemctl enable mysql +# Compare the list of services enabled before the upgrade (saved in step 1.2) with the current list. The only expected difference is php8.2-fpm replaced by php8.4-fpm. Anything else deserves a look. +diff <(awk '{print $1}' /root/upgrade-2610-backup/enabled-units.txt | sort) \ + <(systemctl list-unit-files --state=enabled | awk '{print $1}' | sort) # php8.2 → php8.4 expected + +# reboot the server +systemctl reboot +``` - * Make sure all Centreon services, the web server, PHP 8.4, cron and the database start automatically at boot. - * Compare the list of services enabled before the upgrade (saved in step 1.2) with the current list. The only expected difference is php8.2-fpm replaced by php8.4-fpm. Anything else deserves a look. - * Reboot the server. + + 2. After the reboot, check that everything works: ```bash -uname -r # 6.12.x -systemctl --failed # 0 units +# check that the release version of the Linux kernel the server is currently running is 6.12.x +uname -r +# list all systemd unitsthat are currently in a failed state: there should be 0 +systemctl --failed +# check whether each of the main Centreon-related services is running (each should be active) for u in centengine cbd gorgoned centreontrapd php8.4-fpm apache2 mariadb centreon-map-engine cron; do printf "%s=%s " $u $(systemctl is-active $u); done; echo -ls /etc/cron.d/ # centreon, centstorage -ss -ulnp | grep ":162 " # SNMP traps: UDP 162 held by systemd -logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" # nothing (else table below) -systemctl is-active centreontrapd # active (see the table below) +# check that cron files include at least centreon and centstorage +ls /etc/cron.d/ +# check whether something on the server is listening for SNMP traps, which arrive on UDP port 162 +ss -ulnp | grep ":162 " +# check the log rotation configuration for problems, without actually rotating any logs. It should return nothing +logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" +# check whether the centreontrapd service is currently running +systemctl is-active centreontrapd ``` -What you should see: - -* The kernel version starts with 6.12. -* No failed services. -* Each service reports active. -* The Centreon cron files (centreon, centstorage) are in /etc/cron.d/. -* Port UDP 162, used for SNMP traps, is held by systemd. - | What you see | What it means and what to do | | -------------------------------------------- | ------------------------------------------------------------------------------------ | | `snmptrapd` is inactive | Normal on Debian 13. It starts on demand when the first trap arrives. | @@ -558,14 +605,20 @@ Allow about 6 minutes per poller. Do each poller one at a time. 5. Reboot, then export the poller's configuration from the central server, with **Generate**, **Move export files** and **Restart** all checked. 6. Check that everything works: - ```bash - systemctl --failed # 0 units - systemctl is-active centengine gorgoned centreontrapd # all active - grep -E "Centreon Engine 26.10|Configuration loaded" /var/log/centreon-engine/centengine.log | tail -n 2 - ss -tn | grep -E ":5669|:5556" # Broker (5669) and Gorgone (5556) connected to the central - ls -l /etc/snmp/centreon_traps/centreontrapd.sdb # file is not empty - logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" # nothing (else 1.4) - ``` +```bash +# list all systemd unitsthat are currently in a failed state: there should be 0 +systemctl --failed +# all services should be active +systemctl is-active centengine gorgoned centreontrapd +# check the Centreon Engine log to confirm that the engine started with version 26.10 and loaded its configuration +grep -E "Centreon Engine 26.10|Configuration loaded" /var/log/centreon-engine/centengine.log | tail -n 2 +# List active connections on ports 5669 (Broker) and 5556 (Gorgone) (they should be connected to the central server) +ss -tn | grep -E ":5669|:5556" +# check that the file is not empty (it contains the details of the SQLite database file that centreontrapd uses to look up SNMP trap definitions) +ls -l /etc/snmp/centreon_traps/centreontrapd.sdb +# check the log rotation configuration for problems without rotating anything. Should return nothing +logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" +``` ### If `centreontrapd` stops by itself @@ -594,19 +647,23 @@ On the reporting server, make sure no ETL run is in progress: check with `ps -ef 1. **Back up the server:** - ```bash - B=/root/upgrade-2610-backup; mkdir -p $B - tar czf $B/etc-$(hostname).tar.gz -C / etc; dpkg -l > $B/dpkg-l.txt - systemctl list-unit-files --state=enabled > $B/enabled-units.txt - ``` +```bash +# set up a backup directory +B=/root/upgrade-2610-backup; mkdir -p $B +# back up the server’s configuration and record the list of installed packages before the upgrade. +tar czf $B/etc-$(hostname).tar.gz -C / etc; dpkg -l > $B/dpkg-l.txt +# save the list of systemd units that are set to start automatically, into a text file in the backup directory +systemctl list-unit-files --state=enabled > $B/enabled-units.txt +``` Also back up the reporting database, as described on the MBI page [Backing up and restoring MBI](../reporting/backup-restore.md). 2. **Make sure cron is installed** (see step 1.4). - ```bash - dpkg -l cron | grep -q "^ii" || apt-get install -y cron - ``` +```bash +# if cron is installed, the command prints nothing. If it isn't installed, it installs it +dpkg -l cron | grep -q "^ii" || apt-get install -y cron +``` 3. **Stop the services:** @@ -623,16 +680,26 @@ On the reporting server, make sure no ETL run is in progress: check with `ps -ef ### 11.3 Check and restart ```bash -dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' # nothing -dpkg -l "centreon-bi*" | awk '/^ii/{print $2, $3}' # 26.10.0 -java -version 2>&1 | head -n 1 # openjdk 25 -grep ExecStart /lib/systemd/system/cbis.service | grep -o "java-[0-9]*-openjdk" # java-25-openjdk -find /etc -name "*.dpkg-dist" | grep -E "centreon|mysql" # keep yours (bind-address) -systemctl is-active mariadb # local reporting DB (MySQL: mysql) +# lists packages that are in an unusual or broken state: there should be nothing +dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' +# checks that the centreon-bi-server and centreon-bi-engine packages are in version 26.10.0 +dpkg -l "centreon-bi*" | awk '/^ii/{print $2, $3}' +# check that your versoini of java is openjdk 25 +java -version 2>&1 | head -n 1 +# check which Java version the cbis service is configured to use: it should be java-25-openjdk +grep ExecStart /lib/systemd/system/cbis.service | grep -o "java-[0-9]*-openjdk" +# find new configuration files that an upgrade installed alongside your existing ones, instead of replacing them, for Centreon and MySQL/MariaDB. +find /etc -name "*.dpkg-dist" | grep -E "centreon|mysql" +# check that your MBI database is active (if you have MySQL, replace "mariadb" with "mysql") +systemctl is-active mariadb +# start services systemctl start cbis; systemctl enable --now gorgoned cron -systemctl is-active cbis gorgoned cron # all active -ls /etc/cron.d/ | grep centreon-bi # engine, purge, backup-reporting-server -tail -n 20 /var/log/centreon-bi/cbis.$(date +%F).log # no "Connection test … failed" +# check whether the cbis, gorgoned, and cron services are all currently running +systemctl is-active cbis gorgoned cron +# check whether the Centreon MBI scheduled tasks (cron jobs) are in place (engine, purge, backup-reporting-server) +ls /etc/cron.d/ | grep centreon-bi +# should not contain "Connection test … failed" +tail -n 20 /var/log/centreon-bi/cbis.$(date +%F).log ``` Then reboot and check again that `cbis`, `gorgoned` and `cron` are active. After 07:30 on the next weekday, `/var/log/centreon-bi/centreonBIETL.log` should show the ETL run. @@ -643,8 +710,6 @@ Then reboot and check again that `cbis`, `gorgoned` and `cron` are active. After ## Known issues -Here is the table without the Ticket column: - | When | You see | Do | | --- | --- | --- | | MBI server | Nothing: ETL, purge, backup never run (`cron` absent) | 1.4: install/enable `cron`; check `centreonBIETL.log` next weekday | From 8f413138f46cc642e2070170926e7433945e90b8 Mon Sep 17 00:00:00 2001 From: emgcentreon Date: Mon, 19 Oct 2026 12:03:00 +0200 Subject: [PATCH 170/179] Update versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md --- .../pollers-containers-prerequisites.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md b/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md index 75f05f15b68e..fe17eb9f4d5c 100644 --- a/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md +++ b/versioned_docs/version-26.10/installation/installation-of-a-poller/pollers-containers-prerequisites.md @@ -167,7 +167,7 @@ systemctl restart apache2 You can now add a poller using the automatically generated command. To do so, retrieve the command from the Centreon web interface (in the poller section at the top left of the screen, whether you want to install a poller [on a container](./using-containers.md) or [on a VM or a physical machine](vm-or-physical.md)). The poller will automatically connect to the central server using pullwss. -## If you delete all your collectors installed via an automatically generated command +## If you delete all your pollers installed via an automatically generated command If in the future you should delete all your pollers installed via an automatically generated command, do not forget to undo the steps above. From e2b102e37fd40a6cba3804c7f8fa27a498abc8b5 Mon Sep 17 00:00:00 2001 From: emgcentreon Date: Mon, 19 Oct 2026 14:16:26 +0200 Subject: [PATCH 171/179] Update commands.md --- .../version-26.10/monitoring/basic-objects/commands.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/versioned_docs/version-26.10/monitoring/basic-objects/commands.md b/versioned_docs/version-26.10/monitoring/basic-objects/commands.md index 81afa07c8053..b7b694b92595 100644 --- a/versioned_docs/version-26.10/monitoring/basic-objects/commands.md +++ b/versioned_docs/version-26.10/monitoring/basic-objects/commands.md @@ -197,6 +197,8 @@ apt install centreon-connector-ssh +## Optimization connectors + ### Perl connector Centreon Perl Connector is free software from Centreon available under the Apache Software License version 2 (ASL 2.0). From acfc08edd149703de1d35b86d4dc2a75f8aea8d6 Mon Sep 17 00:00:00 2001 From: emgcentreon Date: Mon, 19 Oct 2026 14:28:59 +0200 Subject: [PATCH 172/179] Update commands.md --- .../version-26.10/monitoring/basic-objects/commands.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/basic-objects/commands.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/basic-objects/commands.md index 90d9240e5ac9..846f01592421 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/basic-objects/commands.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/monitoring/basic-objects/commands.md @@ -165,6 +165,8 @@ dnf install centreon-connector-ssh ``` shell apt install centreon-connector-ssh ``` + + ## Connecteurs d'optimisation From 1aaa934d45928e660b0a3ce682fb204f281fee5c Mon Sep 17 00:00:00 2001 From: smau Date: Mon, 19 Oct 2026 15:29:26 +0200 Subject: [PATCH 173/179] Apply QA comments --- .../version-26.10/graph-views/map-web-install.md | 14 ++++++++++++++ .../version-26.10/graph-views/map-web-install.md | 14 ++++++++++++++ 2 files changed, 28 insertions(+) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md index e110c013d42c..2e1080a5cfc6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-install.md @@ -288,6 +288,14 @@ GRANT SELECT, INSERT ON centreon.* TO 'centreon_map'@''; Le privilège INSERT ne sera utilisé que pendant le processus d'installation afin de créer une nouvelle sortie Centreon Broker. Il sera révoqué ultérieurement ([à cette étape](#étape-6--appliquer-la-configuration-broker-et-redémarrer-map-engine)). +> Si le serveur MAP Engine est un serveur séparé, la base de données qui héberge **centreon** et **centreon_storage** doit accepter ses connexions. Sur Debian 13, MariaDB écoute sur 127.0.0.1 par défaut : sur le serveur de base de données du central, éditez **/etc/mysql/mariadb.conf.d/50-server.cnf**, définissez le paramètre **bind-address** à **0.0.0.0**, puis redémarrez la base de données : +> +> ```shell +> systemctl restart mariadb +> ``` +> +> Si un pare-feu est activé sur le serveur de base de données, autorisez le port 3306 depuis le serveur MAP Engine. + ### Étape 3 : installer le serveur MAP Engine #### Installation des paquets @@ -542,6 +550,12 @@ sudo systemctl status mysqld +> **Debian 13 :** après l'installation, l'utilisateur **root** utilise le plugin auth_socket et `mysql_secure_installation` ne peut pas définir son mot de passe (la commande boucle sur "SET PASSWORD has no significance"). Définissez d'abord le mot de passe, puis lancez `mysql_secure_installation` avec ce mot de passe : +> +> ```shell +> mysql -e "ALTER USER 'root'@'localhost' IDENTIFIED WITH 'caching_sha2_password' BY '';" +> ``` + ```shell apt update apt install -y centreon-mysql diff --git a/versioned_docs/version-26.10/graph-views/map-web-install.md b/versioned_docs/version-26.10/graph-views/map-web-install.md index a3bf277c4c94..cefa417d2780 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-install.md +++ b/versioned_docs/version-26.10/graph-views/map-web-install.md @@ -295,6 +295,14 @@ GRANT SELECT, INSERT ON centreon.* TO 'centreon_map'@''; The INSERT privilege will only be used during the installation process in order to create new Centreon Broker output. It will be revoked later ([at this step](#step-6-apply-centreon-broker-configuration-and-restart-map-engine-service)). +> If the MAP Engine server is a separate server, the database hosting **centreon** and **centreon_storage** must accept connections from it. On Debian 13, MariaDB listens on 127.0.0.1 by default: on the central database server, edit **/etc/mysql/mariadb.conf.d/50-server.cnf**, set the **bind-address** parameter to **0.0.0.0**, then restart the database: +> +> ```shell +> systemctl restart mariadb +> ``` +> +> If a firewall is enabled on the database server, allow port 3306 from the MAP Engine server. + ### Step 3: Install MAP Engine server #### Package installation @@ -550,6 +558,12 @@ sudo systemctl status mysqld +> **Debian 13:** after the installation, the **root** user uses the auth_socket plugin and `mysql_secure_installation` cannot set its password (it loops on "SET PASSWORD has no significance"). Set the password first, then run `mysql_secure_installation` with it: +> +> ```shell +> mysql -e "ALTER USER 'root'@'localhost' IDENTIFIED WITH 'caching_sha2_password' BY '';" +> ``` + ```shell apt update apt install -y centreon-mysql From df010c70504ffd2ad3dacfd07ab0bb37e2763729 Mon Sep 17 00:00:00 2001 From: cg-tw <83637804+cg-tw@users.noreply.github.com> Date: Mon, 19 Oct 2026 18:40:55 +0200 Subject: [PATCH 174/179] Remove in-place migration procedure (transferred to The Watch) --- .../migrate/migrate-from-debian-to-debian.md | 2 +- .../migrate/upgrade-debian-in-place.md | 632 --------------- .../migrate/migrate-from-debian-to-debian.md | 2 +- .../migrate/upgrade-debian-in-place.md | 749 ------------------ .../version-26.10-sidebars.json | 4 - 5 files changed, 2 insertions(+), 1387 deletions(-) delete mode 100644 i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/upgrade-debian-in-place.md delete mode 100644 versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md index b40baa89f2d7..ccbb2b82720b 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/migrate-from-debian-to-debian.md @@ -8,7 +8,7 @@ import TabItem from '@theme/TabItem'; ## Prérequis -Cette procédure ne s'applique que si vous souhaitez migrer de Debian vers une version plus récente de Debian, sur des serveurs différents. La procédure de migration de Debian 12 vers Debian 13 sur le même serveur (migration in-place) sera bientôt disponible sur notre plateforme communautaire The Watch. +Cette procédure ne s'applique que si vous souhaitez migrer de Debian vers une version plus récente de Debian, sur des serveurs différents. La procédure de migration de Debian 12 vers Debian 13 sur le même serveur (migration in-place) est disponible sur notre plateforme communautaire The Watch. Tous les serveurs de votre architecture (serveur central, serveurs distants et collecteurs) doivent avoir la même version majeure de Centreon. Il est également recommandé d'avoir la même version mineure. diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/upgrade-debian-in-place.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/upgrade-debian-in-place.md deleted file mode 100644 index 78b19a318665..000000000000 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/migrate/upgrade-debian-in-place.md +++ /dev/null @@ -1,632 +0,0 @@ ---- -id: upgrade-debian-in-place -title: Upgrading Centreon and Debian (12 to 13) on the same server -description: "In-place migration procedure for Debian - Debian 12 to 13" ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Use this procedure if you are running Centreon 24.04, 24.10 or 25.10 on Debian 12 and you wish to upgrade to Centreon 26.10 (only Debian 13 is supported for this version). - -> Run every command as `root`. - - -## Step 1: Before you start - -### 1.1 Take a snapshot of each server - -Snapshot every server (central server, database server, MAP server, MBI server). If you have a remote database, take both snapshots at the same time, with Centreon stopped if possible. It is the only way to roll back quickly. - -### 1.2 Create dumps - -Snapshots let you roll back a whole server quickly, but they do not replace backups. They usually share the VM's storage, capture databases only in a crash-consistent state, and cannot restore a single database or file. Once your snapshots are done, also make the backups below. - - ```bash - B=/root/upgrade-2610-backup; mkdir -p $B - # On the server that hosts the database - mysqldump --single-transaction --routines --triggers --events centreon | gzip > $B/centreon.sql.gz - mysqldump --single-transaction --routines --triggers --events centreon_storage | gzip > $B/centreon_storage.sql.gz - mysqldump --single-transaction --routines --triggers --events centreon_map | gzip > $B/centreon_map.sql.gz # [MAP], where it lives - zcat $B/centreon_storage.sql.gz | tail -n 1 # "-- Dump completed on …" - # On every server - tar czf $B/etc-$(hostname).tar.gz -C / etc - dpkg -l > $B/dpkg-l.txt - systemctl list-unit-files --state=enabled > $B/enabled-units.txt # compared in step 9 - ``` - -### 1.3 Check the state of the server - -Before starting the upgrade, check that the server is in the expected state: Debian 12, Centreon 25.10, enough free disk space, and working package repositories. If any result differs from the expected one, fix it before going further. - - ```bash - cat /etc/debian_version # 12.x - dpkg -l centreon-web | awk '/^ii/{print $3}' # 25.10.x - df -h / /var /var/lib/mysql # several GB free (~1,300 packages) - apt-get update # no error (a broken repository blocks the upgrade to Debian 13) - ``` - -### 1.4 Check that cron and logrotate are installed (on every Centreon server) - -Centreon needs **cron** to run its scheduled jobs and **logrotate** to rotate its logs. Minimal Debian images often include neither, and nothing warns you when they are missing. - -```bash -ls /etc/cron.d/ | grep -iE "centreon|centstorage" # Centreon jobs here? -dpkg -l cron | grep -q "^ii" || apt-get install -y cron # install if missing -systemctl enable --now cron && systemctl is-active cron # active -dpkg -l logrotate | grep -q "^ii" || apt-get install -y logrotate -chmod 644 /etc/logrotate.d/cbd /etc/logrotate.d/centengine 2>/dev/null -logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" # nothing -``` - -- **Without cron**, the Centreon jobs never run and no error is shown. This affects the MBI jobs (ETL, purge, backup) in particular. -- **Without logrotate**, Centreon logs are never rotated. -- **The `chmod 644` line** is a workaround. The Broker and Engine logrotate files are shipped with permissions `0664`, so logrotate ignores them. A package upgrade can restore `0664`, so check again in step 9. - -## Step 2: Update your Centreon version to the latest minor - -Follow the update procedures for your version ([24.04](https://archives-docs.centreon.com/24.04/docs/update/update-centreon-platform/), [24.10](https://docs.centreon.com/docs/24.10/update/update-centreon-platform/) or [25.10](https://docs.centreon.com/docs/25.10/update/update-centreon-platform.md)). Update your central server, your pollers and your remote servers. - - - -## Step 3: Update Debian 12 to the latest version - -The following commands bring the server to the latest Debian 12 minor version before the major migration to Debian 13. - -```bash -apt-get update -DEBIAN_FRONTEND=noninteractive apt-get -y -o Dpkg::Options::=--force-confold full-upgrade -cat /etc/debian_version # latest 12.x version -systemctl reboot -``` - -| If… | Do | -| ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | -| `apt-get update` fails on the **MaxScale** line (`NO_PUBKEY`) in `mariadb.list` | Comment **only that line** (the file also holds the MariaDB Server repository) | -| [MySQL] `mysql-apt-config` is upgraded (seen 0.8.36 → 0.8.40) | Nothing: `mysql.list` is kept | - -After the reboot, check that the web interface works and that the pollers are connected. You can update the servers in any order (central server or database server first). - -## Step 4: Upgrade a remote database server (if applicable) - -Do this only if your database runs on its own server, separate from the central. Before you start, make sure Centreon is already stopped on the central server. - -### 4.1 Back up the configuration and stop the database - -Run these commands on the **database server**: - -```bash -B=/root/upgrade-2610-backup; mkdir -p $B/apt-bookworm -cp -a /etc/apt/sources.list /etc/apt/sources.list.d /etc/mysql $B/apt-bookworm/ -systemctl stop mariadb # MySQL: systemctl stop mysql -``` - -This saves your current APT repositories and MySQL/MariaDB configuration, then stops the database. - -### 4.2 Upgrade the server - -1. **Update the repositories:** steps 5.1, 5.2 and 5.3. Here you only need the standard repository and the plugins repository. The `centreon-mariadb` and `centreon-mysql` packages come from the standard repository. -2. **Run the simulation (step 5.4).** You should see: - - `mariadb-server` 11.8, or `mysql-community-server` 8.4.x-1debian13 - - `centreon-mariadb` or `centreon-mysql` at 26.10 - - no `centreon-web`, because it is not installed on this server -3. **Run the upgrade (step 6).** - -### 4.3 Check the result - -```bash -dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' # nothing -cat /etc/debian_version # 13.x -systemctl is-active mariadb # active (MySQL: mysql) -mariadb -e "SELECT @@version, @@read_only" # 11.8.x, 0 (MySQL: 8.4.x, 0) -mariadb-upgrade --check-if-upgrade-is-needed && echo "run: mariadb-upgrade" || echo "done" # MySQL: skip this line -mariadb -e "SHOW DATABASES" | grep -E "^centreon(_storage)?$" # both databases listed -tail -n 5 /var/log/mysql/error.log # MySQL only: "ready for connections. Version: '8.4.x'" -find /etc/mysql -name "*.dpkg-dist" # keep your own file -systemctl enable mariadb && systemctl reboot # MySQL: mysql -``` - -For MySQL, use `mysql` instead of `mariadb` in the commands above. - -### 4.4 Check the connection from the central - -After the reboot, run this on the **central server**, replacing `` with the address of your database server: - -```bash -timeout 3 bash -c '/3306' && echo OK -``` - -It should print `OK`. (This command is used because `nc` is not installed by default.) - -### 4.5 Troubleshooting - -| If you see | What to do | -| --- | --- | -| A file named `50-server.cnf.dpkg-dist` | **Keep your own file** and ignore the new one. The new file sets `bind-address = 127.0.0.1`, which only allows local connections, so the central could no longer reach the database. Your file should have `bind-address = 0.0.0.0` (or the server's IP address) and `utf8mb4`. | -| MariaDB does not start | Run `systemctl start mariadb`, then read the details with `journalctl -u mariadb`. The usual cause is an option in your tuning file that was removed or renamed in the new MariaDB version. | -| `read_only` is 1 | Run `mariadb -e "SET GLOBAL read_only=OFF"`, then delete the `read_only` line from your configuration. That setting is meant for replica servers. | - -## Step 5: Switch the repositories (on every server you upgrade) - -The commands edit your existing repository files (either deb822 *.sources files or one-line *.list files). Do not add a new file next to an old one: the 25.10 and 26.10 repositories would mix. - -```bash -B=/root/upgrade-2610-backup; mkdir -p $B/apt-bookworm -cp -a /etc/apt/sources.list /etc/apt/sources.list.d $B/apt-bookworm/ # rollback -cp -a /etc/apache2/sites-available/centreon.conf $B/apache-centreon.conf.2510 2>/dev/null -ls /etc/apt/sources.list.d/ -``` - -### 5.1 On your Debian OS - -Point APT at the Debian 13 repositories instead of Debian 12. It only edits configuration files, nothing is downloaded or upgraded yet. - -```bash -[ -f /etc/apt/sources.list.d/debian.sources ] && sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/debian.sources -sed -i 's/bookworm/trixie/g' /etc/apt/sources.list -grep -rqs "trixie-backports" /etc/apt/sources.list /etc/apt/sources.list.d/ || \ - echo "deb http://deb.debian.org/debian/ trixie-backports main non-free-firmware" >> /etc/apt/sources.list -``` - -### 5.2 On Centreon - -**5.2 Centreon** (any file name: `centreon-25.10-stable.list`, `centreon-stable.list`, …) - -Point the Centreon repositories at the 26.10 packages for Debian 13. It only edits APT configuration files, nothing is upgraded yet. - -```bash -for f in $(grep -lE "packages.centreon.com|centreon.jfrog.io" /etc/apt/sources.list.d/*.list); do - sed -i -E -e 's/bookworm-25\.10-[a-z-]+/trixie-26.10-stable/g' -e 's/ (bookworm|bullseye) / trixie /g' "$f" - echo "== $f"; cat "$f" -done -grep -qs "apt-plugins-stable/\? trixie" /etc/apt/sources.list.d/*.list || \ - echo "deb https://packages.centreon.com/apt-plugins-stable/ trixie main" > /etc/apt/sources.list.d/centreon-plugins-stable.list -mv centreon-25.10-stable.list centreon-26.10-stable.list -``` - -| Repository line | Required? | -| ---------------------------------------------------------------------------------- | --------------------------------------------------------------------- | -| `apt-standard/ …` | **Yes** | -| `apt-plugins-stable/ trixie` | **Yes**: trixie builds of the Perl libs (Net::Curl, Libssh::Session…) | -| `apt-business/ …` | Only with Business modules (**required on the MBI server**) | -| `apt-plugins-testing/ bookworm` (or `apt-plugins-testing trixie` after the switch) | Optional | -| `centreon.jfrog.io/…/apt-connectors-stable/` | Optional | - -File names keep `25.10`: cosmetic (`mv centreon-25.10-stable.list centreon-26.10-stable.list` if you want). - -### 5.3 On the database server - -Run this on every server that hosts a database: the central server (if the database is local), the remote database server, and the MAP or MBI server. - -Update the database repositories for Debian 13. For MariaDB it also changes the version, from 10.11 to 11.8. It only edits APT configuration files and upgrades nothing yet. - - - - -```bash -for f in /etc/apt/sources.list.d/mariadb.sources /etc/apt/sources.list.d/mariadb.list; do - [ -f "$f" ] || continue - sed -i -e 's|mariadb-server/10.11/|mariadb-server/11.8/|' -e 's/bookworm/trixie/g' "$f" - echo "== $f"; grep -vE "^\s*#|^\s*$" "$f" -done -``` - - - - -```bash -[ -f /etc/apt/sources.list.d/mysql.list ] && sed -i 's/ bookworm / trixie /g' /etc/apt/sources.list.d/mysql.list -echo "mysql-apt-config mysql-apt-config/repo-codename select trixie" | debconf-set-selections -echo "== /etc/apt/sources.list.d/mysql.list"; grep -vE "^\s*#|^\s*$" /etc/apt/sources.list.d/mysql.list -``` - - - - -| If… | Do / know | -| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| No `mariadb.*` file | MariaDB comes from Debian: Debian 13 ships 11.8, nothing to do | -| [MySQL] `mysql.list` points to `mysql-8.0` | **Stop**: `repo.mysql.com` trixie has no 8.0. Upgrade to 8.4 LTS on Debian 12 first (trixie has `mysql-8.4-lts`, `mysql-9.7-lts`, `mysql-innovation`, plus `mysql-apt-config`, `mysql-tools`) | -| [MySQL] debconf line skipped | A later `mysql-apt-config` reconfiguration (`dpkg-reconfigure`, new package version) may write `bookworm` back. With it: kept (checked; prints a harmless `gpg: cannot open '/dev/tty'`) | -| `*.disabled`, `*.old_*` files | Ignored by apt | -| MaxScale line commented in step 3 | Stays commented | - -### 5.4 Check and simulate - -This step is a dry-run check before the real upgrade. It verifies that the repository changes are correct and simulates the upgrade, so you can spot problems while nothing has been modified yet. The comment at the end of each line is the expected result. - -```bash -grep -rn bookworm /etc/apt/sources.list /etc/apt/sources.list.d/ | grep -v ":\s*#" # nothing -apt clean && apt-get update # no W:/E: -apt-get -s full-upgrade > $B/sim.txt -tail -n 3 $B/sim.txt # N upgraded / new / removed -grep -iE "broken|unmet" $B/sim.txt # nothing -grep -E "^Inst (centreon-web|php8.4-fpm|mariadb-server|mysql-community-server) " $B/sim.txt -grep -E "^Remv centreon" $B/sim.txt # nothing -``` - -* If the simulation shows broken packages, stop and restore the sources: `cp -a $B/apt-bookworm/* /etc/apt/`. -* If everything matches the expected results, you can proceed to the real upgrade. If not, fix the repositories first. Nothing has changed on the system at this point, so the check is safe to repeat. - -## Step 6: Upgrade (every server you upgrade) - -This is the real upgrade to Debian 13. It runs the upgrade in the background, in two stages, and then lets you watch its progress. - -```bash -systemd-run --unit=upg2610 /bin/sh -c 'export DEBIAN_FRONTEND=noninteractive; O="-o Dpkg::Options::=--force-confold -o Dpkg::Options::=--force-confdef"; apt-get -y $O upgrade --without-new-pkgs > /root/upgrade-2610-backup/upg-step1.log 2>&1 && apt-get -y $O full-upgrade > /root/upgrade-2610-backup/upg-step2.log 2>&1' -watch -n 10 'pgrep -x apt-get; pgrep -x dpkg; tail -n 2 /root/upgrade-2610-backup/upg-step2.log' # done when both pgrep print nothing -``` - -- Don't interrupt it and don't reboot until it's finished, even if it seems slow (about 1,300 packages). -- Duration: central ~10–15 min, database/MBI server ~6 min, poller ~6 min. -- `systemd-run`: the upgrade survives an SSH disconnection (`openssh-server` is upgraded). -- Wait on the **processes**, not on the unit state (unreliable while systemd itself is upgraded). -- Expected in the logs: `chmod: cannot access '/var/cache/centreon/config/broker/*'` and `…/engine/*`. -- **Do not reboot yet.** - -Then stop Centreon again on the central server. The 26.10 packages restart the services (and cron, if it was upgraded), but the database schema stays at 25.10 until you run the update wizard in step 8. Until then, Gorgone logs `Unknown column 'uid' in 'field list'` / `[legacycmd] Cannot get configuration for pollers` every 15 s. - -```bash -systemctl stop centengine cbd gorgoned centreontrapd cron -systemctl stop centreon-map-engine 2>/dev/null # [MAP] -``` - -## Step 7: Checks after the packages - -### 7.1 Run checks - -This step is the post-upgrade verification (7.1 to 7.4), followed by switching the web stack to PHP 8.4. It checks that the upgrade to Debian 13 went cleanly and that nothing was left half-done. The comment on each line is the expected result. - -```bash -# 7.1 dpkg -dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' # nothing ("rc" = removed, OK) -grep -hE "^(W|E):|dpkg: (error|erreur)" /root/upgrade-2610-backup/upg-step*.log # nothing -cat /etc/debian_version # 13.x -dpkg -l centreon-web centreon-engine centreon-broker centreon-gorgone php8.4-fpm | awk '/^ii/{print $2, $3}' -# 7.2 Perl / libraries left on Debian 12 -dpkg -l | awk '/^ii/ && $3 ~ /deb12/ {print $2, $3}' # only obsolete Debian libs (libperl5.36, perl-modules-5.36…) -perl -MCrypt::OpenSSL::AES -MNet::Curl -MLibssh::Session -e 'print "OK\n"' # OK -# 7.3 Config files kept by --force-confold -find /etc -name "*.dpkg-dist" -o -name "*.ucf-dist" | grep -E "apache2|centreon|php|mysql" -# 7.4 PHP 8.4 -systemctl enable --now php8.4-fpm; systemctl disable --now php8.2-fpm 2>/dev/null -systemctl restart apache2 -curl -s -o /dev/null -w "%{http_code}\n" http://localhost/centreon/ # 200 -``` - -| If… (7.2 / 7.3) | Do | -| ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | -| A Centreon or `lib*-perl` package still `deb12`, or Perl not OK | `apt-get install --reinstall `; check `apt-plugins-stable trixie` (5.2) | -| [MAP] `openjdk-17-jre-headless` still `deb12` | Normal: MAP 26.10 uses Java 25 (`openjdk-25-jre-headless`, now default). After validation: `apt purge openjdk-17-jre-headless` | -| `apache2/…/centreon.conf.dpkg-dist` | **Apache merge** (step 2): 26.10 adds the Gorgone websocket `ProxyPass` block | -| `/etc/centreon-engine/centengine.cfg.dpkg-dist`, `/etc/centreon-broker/central-module.json.dpkg-dist` | Keep yours (generated by the export) | -| `/etc/mysql/mariadb.conf.d/50-server.cnf.dpkg-dist` | Keep yours (package sets `bind-address = 127.0.0.1`) | -| [MAP] `/etc/centreon-map/map-config.properties.dpkg-dist` | Keep yours: it is a template (`%CENTREON_BROKER_ADDRESS%`, `%CENTREON_PWD%`…) | - -### 7.2 Check the database - -If you have a local database, run this on the central server. If your database is on a separate server, run this on that server, not on the central. - -This step is the database health check after the upgrade. It confirms that the new MariaDB 11.8 is running, writable, upgraded internally, and that the Centreon databases are still there. The comments give the expected result, with the MySQL variant after the dash. - -```bash -systemctl is-active mariadb # active — [MySQL] mysql -mariadb -e "SELECT @@version, @@read_only" # 11.8.x, 0 — [MySQL] 8.4.x, 0 -mariadb-upgrade --check-if-upgrade-is-needed && echo "run: mariadb-upgrade" || echo "done" # [MySQL] skip -mariadb -e "SHOW DATABASES" | grep -E "^centreon(_storage|_map)?$" -journalctl -u mariadb --since "-1h" | grep -iE "error|warning" | tail -n 20 # [MySQL] tail /var/log/mysql/error.log -``` - -* If MariaDB isn't active, or the version query shows read_only = 1 (the database refuses writes), use [the troubleshooting table from step 4](#45-troubleshooting). -* If the check prints "run: mariadb-upgrade", run mariadb-upgrade. It takes its login details from /root/.my.cnf. When it works, it finishes with return code 0 after 8 phases, and running the check again reports that no upgrade is needed. - Why this happens: the MariaDB package normally updates the database's internal system tables during the upgrade. It can't do this if the MariaDB root account has a password, and it won't warn you. MariaDB 11.8 then runs on system tables still in the 10.11 format. If root logs in through unix_socket (no password), the package does it by itself, as it did on the database servers we tested. - -## Step 8: Finalize the upgrade on the central server - -### 8.1 On the web interface - -First, clear your browser cache so you don't see old pages from 25.10. (If you use MAP, its documentation has the same step.) - -1. Run the update wizard to 26.10. Click Finish only once. - The wizard log may show `Undefined array key "is_reverse"` in `Update-25.11.0.php`. If you use the Centreon Monitoring Agent, check the connection mode of each agent configuration. It should be set to "agent initiated", which is the default. -2. Update the modules in **Administration > Extensions > Manager**. Update them one at a time, and wait for each to finish before starting the next. - * If you use MAP, update both the MAP module and the MAP widget. They have separate buttons. - * Avoid **Update all**. On both test platforms, it left auto-discovery not updated until a second request. If you use it anyway, check that auto-discovery shows version 26.10. -3. Apply the updates in the Monitoring Connector Manager. - -### 8.2 On the central server - -To restart Centreon on the new version, run these commands on the central server: - -```bash -cd /usr/share/centreon && sudo -u www-data php bin/console cache:clear -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -sudo -u www-data php /usr/share/centreon/bin/console w:m:c --dry-run # "No invalid commands found." -systemctl restart cbd centengine gorgoned centreontrapd -systemctl start centreon-map-engine # [MAP] -``` - -What these commands do: - -* Clear the web application cache. -* Let the web server and Broker access each other's files. -* Check for invalid Engine and Broker commands. If the check lists any, run it again without **--dry-run** to remove them. (`w:m:c` is short for `web:monitoring-server:clean-engine-broker-command`.) -* Restart the monitoring services, and start the MAP engine if you use MAP. - -If you use MAP, check that it works: - -* `systemctl is-active centreon-map-engine` should print `active`. -* Run `for p in $(pgrep -x java); do readlink -f /proc/$p/exe; done`. The result should contain `java-25-openjdk`. -* Run `grep -E "ERROR|Connection with Broker established" /var/log/centreon-map/centreon-map-engine.log | tail -n 5`. You should see that the connection with Broker is established. A few `Error while connecting to Broker` messages are normal while Broker restarts. - -### 8.3 Export the configuration from the web interface - -1. Export the central server's configuration with **Generate**, **Move export files** and **Restart all** checked. If you skip **Move export files**, the new files stay in `/var/cache/centreon/config` and Engine 26.10 keeps using the old configuration. - -2. Restart the services one last time - - ```bash - systemctl restart cbd centengine centreontrapd gorgoned - systemctl start cron - ``` - - This makes the services load the new configuration and turns scheduled jobs (cron) back on. - -## Step 9: Make sure everything starts at boot, then reboot - -1. Run these commands on the central server: - - ```bash - systemctl enable centengine cbd gorgoned centreontrapd snmptrapd.socket php8.4-fpm apache2 cron - systemctl enable centreon-map-engine 2>/dev/null # [MAP] - systemctl enable mariadb # [local DB] or local MAP DB — [MySQL] mysql - diff <(awk '{print $1}' /root/upgrade-2610-backup/enabled-units.txt | sort) \ - <(systemctl list-unit-files --state=enabled | awk '{print $1}' | sort) # php8.2 → php8.4 expected - systemctl reboot - ``` - - What these commands do: - - * Make sure all Centreon services, the web server, PHP 8.4, cron and the database start automatically at boot. - * Compare the list of services enabled before the upgrade (saved in step 1.2) with the current list. The only expected difference is php8.2-fpm replaced by php8.4-fpm. Anything else deserves a look. - * Reboot the server. - -2. After the reboot, check that everything works: - -```bash -uname -r # 6.12.x -systemctl --failed # 0 units -for u in centengine cbd gorgoned centreontrapd php8.4-fpm apache2 mariadb centreon-map-engine cron; do printf "%s=%s " $u $(systemctl is-active $u); done; echo -ls /etc/cron.d/ # centreon, centstorage -ss -ulnp | grep ":162 " # SNMP traps: UDP 162 held by systemd -logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" # nothing (else table below) -systemctl is-active centreontrapd # active (see the table below) -``` - -What you should see: - -* The kernel version starts with 6.12. -* No failed services. -* Each service reports active. -* The Centreon cron files (centreon, centstorage) are in /etc/cron.d/. -* Port UDP 162, used for SNMP traps, is held by systemd. - -| What you see | What it means and what to do | -| -------------------------------------------- | ------------------------------------------------------------------------------------ | -| `snmptrapd` is inactive | Normal on Debian 13. It starts on demand when the first trap arrives. | -| `centreontrapd` is inactive, with exit **0/SUCCESS** | The trap database is empty. See step 10, centreontrapd. | -| `cron` is inactive | Run `systemctl enable --now cron` (See step 1.4.) | -| `logrotate.service` failed (`Ignoring cbd` / `centengine`) | `chmod 644 /etc/logrotate.d/cbd /etc/logrotate.d/centengine`; `systemctl start logrotate` | - -Finally, check the web interface: - -* **Configuration > Pollers**: all pollers are running and were updated recently. There should be no duplicate **Central** entry. (The 26.10 Broker registers the central under a new instance ID, so a duplicate can appear.) -* **Resources Status**: force a check, acknowledge a problem and set a downtime, to confirm they work. -* Graphs are drawn. -* Gorgone is connected. - -## Step 10: Upgrade the pollers (after the central) - -Allow about 6 minutes per poller. Do each poller one at a time. - -1. Back up and update Debian 12. Do the system part of step 1.2, then step 3 (Debian 12 point release and reboot). -2. Stop the monitoring services: - - ```bash - systemctl stop centengine gorgoned centreontrapd - ``` - -3. Upgrade to Debian 13 and Centreon 26.10. Do steps 5.1 and 5.2 (APT repositories, standard and plugins), then step 5.4 and step 6. - After step 5.4, you should see `centreon-poller`, `centreon-engine`, `centreon-broker` and `centreon-gorgone` at 26.10.0, plugins built for `deb13`, and no package removed. -4. Check the result. Do steps 7.1 and 7.2. If `centengine.cfg.dpkg-dist` exists, keep your own file. -5. Reboot, then export the poller's configuration from the central server, with **Generate**, **Move export files** and **Restart** all checked. -6. Check that everything works: - - ```bash - systemctl --failed # 0 units - systemctl is-active centengine gorgoned centreontrapd # all active - grep -E "Centreon Engine 26.10|Configuration loaded" /var/log/centreon-engine/centengine.log | tail -n 2 - ss -tn | grep -E ":5669|:5556" # Broker (5669) and Gorgone (5556) connected to the central - ls -l /etc/snmp/centreon_traps/centreontrapd.sdb # file is not empty - logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" # nothing (else 1.4) - ``` - -### If `centreontrapd` stops by itself - -If the trap database `centreontrapd.sdb` is empty, `centreontrapd` stops one second after it starts. In `/var/log/centreon/centreontrapd.log`, you will see `MySQL error: no such table: cfg_nagios`. systemd reports `inactive (dead)` with status **0/SUCCESS**, so there is no alert, and **no SNMP trap is processed**. - -To fix it: - -1. In the web interface, go to **Configuration > SNMP Traps > Generate**. -2. Select the poller. -3. Check **Generate traps database**, **Apply configurations** and **Restart centreontrapd**. - -The upgrade does not cause this problem. It was also seen on 25.10 after a simple reboot. - -### What to expect - -- Acknowledgements and downtimes survive the poller upgrade, thanks to retention. -- The `downtimes` history gets a new row when Engine restarts. This is normal. - -## Step 11: Upgrade your MBI server (if applicable) - -The central server needs nothing extra. `centreon-bi-server` is upgraded in step 6, and the MBI module and widgets are updated in step 8. - -On the reporting server, make sure no ETL run is in progress: check with `ps -ef | grep -i etl` that none is in progress. - -### 11.1 Before the upgrade - -1. **Back up the server:** - - ```bash - B=/root/upgrade-2610-backup; mkdir -p $B - tar czf $B/etc-$(hostname).tar.gz -C / etc; dpkg -l > $B/dpkg-l.txt - systemctl list-unit-files --state=enabled > $B/enabled-units.txt - ``` - - Also back up the reporting database, as described on the MBI page [Backing up and restoring MBI](../reporting/backup-restore.md). - -2. **Make sure cron is installed** (see step 1.4). - - ```bash - dpkg -l cron | grep -q "^ii" || apt-get install -y cron - ``` - -3. **Stop the services:** - - ```bash - systemctl stop cbis gorgoned cron - ``` - -### 11.2 Upgrade - -1. Do step 3 (Debian 12 point release and reboot), if not already done. -2. Do steps 5.1 and 5.2 (standard, **business** and plugins repositories), then step 5.3 (MariaDB or MySQL repository). -3. Do step 5.4, then step 6. In the simulation, you should see `centreon-bi-reporting-server`, `centreon-bi-engine`, `centreon-bi-etl` and `centreon-bi-report` at 26.10.0, plus `openjdk-25-jdk`. No package should be removed. - -### 11.3 Check and restart - -```bash -dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' # nothing -dpkg -l "centreon-bi*" | awk '/^ii/{print $2, $3}' # 26.10.0 -java -version 2>&1 | head -n 1 # openjdk 25 -grep ExecStart /lib/systemd/system/cbis.service | grep -o "java-[0-9]*-openjdk" # java-25-openjdk -find /etc -name "*.dpkg-dist" | grep -E "centreon|mysql" # keep yours (bind-address) -systemctl is-active mariadb # local reporting DB (MySQL: mysql) -systemctl start cbis; systemctl enable --now gorgoned cron -systemctl is-active cbis gorgoned cron # all active -ls /etc/cron.d/ | grep centreon-bi # engine, purge, backup-reporting-server -tail -n 20 /var/log/centreon-bi/cbis.$(date +%F).log # no "Connection test … failed" -``` - -Then reboot and check again that `cbis`, `gorgoned` and `cron` are active. After 07:30 on the next weekday, `/var/log/centreon-bi/centreonBIETL.log` should show the ETL run. - -### Good to know - -- **Java 25, not 17.** MBI 26.10 uses Java 25. `centreon-bi-engine` pulls in `openjdk-25-jdk`, and `cbis.service` runs `/usr/lib/jvm/java-25-openjdk-amd64/bin/java` directly. The Java 17 left over from Debian 12 is unused. After validation, remove it with `apt purge openjdk-17-*`. - -## Known issues - -Here is the table without the Ticket column: - -| When | You see | Do | -| --- | --- | --- | -| MBI server | Nothing: ETL, purge, backup never run (`cron` absent) | 1.4: install/enable `cron`; check `centreonBIETL.log` next weekday | -| Reboot (central, poller) | `centreontrapd` inactive, exit 0, `no such table: cfg_nagios` | Generate the SNMP traps database, restart centreontrapd | -| Any server, after the upgrade | `logrotate.service` failed, `Ignoring cbd … writable by group or others`; or no logrotate at all (25.10) | 1.4: install logrotate, `chmod 644` cbd/centengine | -| Step 2 | dpkg error, `chmod … .ssh/id_rsa` | `dpkg --configure -a`, all `ii` | -| Steps 2, 8 (extensions) | `cache:clear` error, `Cannot rename` / `Failed to read file …/symfon_` | One module at a time; `cache:clear` alone; check versions | -| Step 8 (_Update all_) | auto-discovery still on 25.10 after the batch | Update it again, check 26.10 | -| Steps 2, 8 (wizard) | Last step sent twice, HTTP 500 | Click Finish once; update done anyway | -| Step 8 (wizard log) | `Undefined array key "is_reverse"` in `Update-25.11.0.php` | Check Monitoring Agent connection modes | -| Export | `auto_reschedule_checks is no longer available` | Warning only | -| Steps 2, 6 (package logs) | `chmod: cannot access '/var/cache/centreon/config/broker/*'` | Harmless | -| 25.10 pollers | Ack closed in history when the service enters a downtime | Pollers on latest 25.10 first; upgrade them soon | -| MBI doc | Java 17 required, no Debian 13 tab, no cron | Follow section 11 | -| Official doc | No Debian 12 → 13 path for 25.10 → 26.10 | This document | -| Step 6 → 8 | Gorgone `Unknown column 'uid'` every 15 s | Stop Centreon again after step 6 | -| Steps 2, 7 (custom Apache) | `centreon.conf.dpkg-dist`, new vhost not applied | Apache merge | -| 4b, 7.3, 11 | `50-server.cnf.dpkg-dist` with `bind-address = 127.0.0.1` | Keep yours | -| Step 7.2 | Plugins / Gorgone cannot load a Perl module | Reinstall from trixie; `apt-plugins-stable trixie` | -| Step 8 export | Engine still on the old config | Export again with **Move** checked | -| Step 9 | `snmptrapd` inactive | Normal (socket-activated) | -| MariaDB 11.8 tools | `mysql: Deprecated program name …` | Cosmetic; use `mariadb` | -| 4b, 7.5 (MariaDB root with a password) | `mariadb-upgrade --check-if-upgrade-is-needed` → needed after the upgrade, nothing logged | Run `mariadb-upgrade` yourself | -| Step 3 | `NO_PUBKEY` on the MaxScale line | Comment only that line | - -## MariaDB/MySQL equivalents - -| Item | MariaDB | MySQL (Oracle `repo.mysql.com`) | -| ---------------- | ----------------------------------------------------- | ---------------------------------- | -| Service, client | `mariadb` | `mysql` | -| Dump | `mysqldump` / `mariadb-dump` | `mysqldump` | -| Centreon package | `centreon-mariadb` | `centreon-mysql` | -| Repository file | `mariadb.sources` or `mariadb.list` | `mysql.list` + `mysql-apt-config` | -| Version | 10.11 → **11.8** (major) | **8.4 → 8.4** LTS, Debian 13 build | -| Data upgrade | `mariadb-upgrade`, run by the package | automatic at server start | -| Root access | `sudo mariadb` if `unix_socket`, else `/root/.my.cnf` | `/root/.my.cnf` | -| Config dir | `/etc/mysql/mariadb.conf.d/` | `/etc/mysql/mysql.conf.d/` | diff --git a/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md b/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md index b8e63b55511c..fe347049c3de 100644 --- a/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md +++ b/versioned_docs/version-26.10/migrate/migrate-from-debian-to-debian.md @@ -8,7 +8,7 @@ import TabItem from '@theme/TabItem'; ## Prerequisites -This procedure only applies if you wish to migrate from Debian to a newer version of Debian, on another server. The procedure to migrate from Debian 12 to Debian 13 on the same server (in-place migration) will be available soon on our community platform The Watch. +This procedure only applies if you wish to migrate from Debian to a newer version of Debian, on another server. The procedure to migrate from Debian 12 to Debian 13 on the same server (in-place migration) is available on our community platform The Watch. All servers (central, remote and pollers) in your architecture must have the same major version of Centreon. It is also recommended that they have the same minor version. diff --git a/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md b/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md deleted file mode 100644 index 9ebe4c94302e..000000000000 --- a/versioned_docs/version-26.10/migrate/upgrade-debian-in-place.md +++ /dev/null @@ -1,749 +0,0 @@ ---- -id: upgrade-debian-in-place -title: Migrating from Debian 12 to Debian 13 on the same server, while upgrading Centreon to version 26.10 -description: "In-place migration procedure for Debian - Debian 12 to 13" ---- -import Tabs from '@theme/Tabs'; -import TabItem from '@theme/TabItem'; - -Use this procedure if you are running Centreon 24.04, 24.10 or 25.10 on Debian 12 and you wish to upgrade to Centreon 26.10 (only Debian 13 is supported for this version). - -> Run every command as `root`. Read each comment in the code blocks before running commands. - - -## Step 1: Before you start - -### 1.1 Take a snapshot of each server - -Snapshot every server (central server, database server, MAP server, MBI server). If you have a remote database, take both snapshots at the same time, with Centreon stopped if possible. It is the only way to roll back quickly. - -### 1.2 Create dumps - -Snapshots let you roll back a whole server quickly, but they do not replace backups. They usually share the VM's storage, capture databases only in a crash-consistent state, and cannot restore a single database or file. Once your snapshots are done, also make the backups below. - - ```bash - B=/root/upgrade-2610-backup; mkdir -p $B - # On the server that hosts the database (local or remote) - mysqldump --single-transaction --routines --triggers --events centreon | gzip > $B/centreon.sql.gz - mysqldump --single-transaction --routines --triggers --events centreon_storage | gzip > $B/centreon_storage.sql.gz - # On your MAP server, if you have one - mysqldump --single-transaction --routines --triggers --events centreon_map | gzip > $B/centreon_map.sql.gz - zcat $B/centreon_storage.sql.gz | tail -n 1 # Expected results: "-- Dump completed on …" - # On every server - tar czf $B/etc-$(hostname).tar.gz -C / etc - dpkg -l > $B/dpkg-l.txt - systemctl list-unit-files --state=enabled > $B/enabled-units.txt - ``` - -### 1.3 Check that cron and logrotate are installed (on every Centreon server) - -Centreon needs **cron** to run its scheduled jobs and **logrotate** to rotate its logs. Minimal Debian images often include neither, and nothing warns you when they are missing. Run the following commands and follow the instructions in the comments. - -```bash -# list the cron job files installed by Centreon: are there any? -ls /etc/cron.d/ | grep -iE "centreon|centstorage" -# check whether cron is installed and install it if it is missing, then activate it and check that it is active -dpkg -l cron | grep -q "^ii" || apt-get install -y cron -systemctl enable --now cron && systemctl is-active cron -# make sure logrotate is installed, install it if it is missing -dpkg -l logrotate | grep -q "^ii" || apt-get install -y logrotate -# set the permissions of the two Centreon rotation configurations, for Centreon Broker (cbd) and Centreon Engine (centengine) -chmod 644 /etc/logrotate.d/cbd /etc/logrotate.d/centengine 2>/dev/null -# do a dry run that parses the whole configuration and shows what it would do without rotating anything -logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" -``` - -- **Without cron**, the Centreon jobs never run and no error is shown. This affects the MBI jobs (ETL, purge, backup) in particular. -- **Without logrotate**, Centreon logs are never rotated. -- **The `chmod 644` line** is a workaround. The Broker and Engine logrotate files are shipped with permissions `0664`, so logrotate ignores them. A package upgrade can restore `0664`, so check again in step 9. - -## Step 2: Prepare your platform for the upgrade - -### 2.1 Upgrade your Centreon version to version 25.10 - -* If you are in version 24.04 or 24.10 on Debian 12, upgrade your version to version 25.10. (See the upgrade procedures for versions [24.04](https://docs.centreon.com/docs/upgrade/upgrade-from-24-04/) and [24.10](https://docs.centreon.com/docs/upgrade/upgrade-from-24-10/)). -* If you are already in version 25.10, [update your platform to the latest minor version](https://docs.centreon.com/docs/25.10/update/update-centreon-platform.md). - -Upgrade/update your central server, your pollers and your remote servers. - -### 2.2 Check the state of the server - -Before starting the upgrade, check that the server is in the expected state: Debian 12, enough free disk space, and working package repositories. If any result differs from the expected one, fix it before going further. - - ```bash - # check that the version of Debian is 12.x - cat /etc/debian_version - # check that your Centreon version is 25.10.x - dpkg -l centreon-web | awk '/^ii/{print $3}' - # check that your have several GB free (the migration installs ~1,300 packages) - df -h / /var /var/lib/mysql - # update your system: there should be no errors (e.g., a broken repository blocks the upgrade to Debian 13) - apt-get update - ``` - - - -## Step 3: Update Debian 12 to the latest version - -The following commands bring the server to the latest Debian 12 minor version before the major migration to Debian 13. - -```bash -apt-get update -# upgrade every installed package to the newest available version, without asking any questions, and keep your existing configuration files -DEBIAN_FRONTEND=noninteractive apt-get -y -o Dpkg::Options::=--force-confold full-upgrade -# check that you have the latest 12.x version -cat /etc/debian_version -# reboot your machine -systemctl reboot -``` - -| If… | Do | -| ------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | -| `apt-get update` fails on the **MaxScale** line (`NO_PUBKEY`) in `mariadb.list` | Comment **only that line** (the file also holds the MariaDB server repository) | -| If you have MySQL, if `mysql-apt-config` is upgraded | Nothing: `mysql.list` is kept | - -After the reboot, check that the web interface works and that the pollers are connected. You can update the servers in any order (central server or database server first). - -## Step 4: Upgrade a remote database server (if applicable) - -Do this only if your database runs on its own server, separate from the central. Before you start, make sure Centreon is already stopped on the central server. If needed, stop all Centreon services: - -```shell -systemctl stop centengine cbd gorgoned smtptrapd centreontrapd snmpd -``` - -### 4.1 Back up the configuration and stop the database - -Run these commands on the **database server**: - -```bash -# create the backup folder used in the rest of the procedure, with a subfolder for the apt configuration -B=/root/upgrade-2610-backup; mkdir -p $B/apt-bookworm -# back up the apt sources and the MySQL/MariaDB configuration -cp -a /etc/apt/sources.list /etc/apt/sources.list.d /etc/mysql $B/apt-bookworm/ -# stop your database: if you have MySQL, do "systemctl stop mysql" instead -systemctl stop mariadb -``` - -### 4.2 Upgrade the server - -1. **Update the repositories:** steps 5.1, 5.2 and 5.3. Here you only need the standard repository and the plugins repository. The `centreon-mariadb` and `centreon-mysql` packages come from the standard repository. -2. **Run the simulation (step 5.4).** You should see: - - `mariadb-server` 11.8, or `mysql-community-server` 8.4.x-1debian13 - - `centreon-mariadb` or `centreon-mysql` at 26.10 - - no `centreon-web`, because it is not installed on this server -3. **Run the upgrade (step 6).** - -### 4.3 Check the result - -```bash -# list any packages in an abnormal state. you should have none -dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' -# check that your version of Debian is 13.x -cat /etc/debian_version -# check that your database is active (if you have MySQL, replace "mariadb" by "mysql") -systemctl is-active mariadb -# check the version of your database. MariaDB should be 11.8.x, MySQL should be 8.4.x. Both should have read-only as 0 -mariadb -e "SELECT @@version, @@read_only" -## check and upgrade mariadb: skip this line if you have MySQL -mariadb-upgrade --check-if-upgrade-is-needed && echo "run: mariadb-upgrade" || echo "done" -# check that both databases are listed -mariadb -e "SHOW DATABASES" | grep -E "^centreon(_storage)?$" -# if you have MySQL, check the logs for any errors. The correct log mesage is "ready for connections. Version: '8.4.x'" -tail -n 5 /var/log/mysql/error.log -# list the new MariaDB/MySQL config files that the upgrade didn’t apply because you had modified the originals -find /etc/mysql -name "*.dpkg-dist" -# enable the database and restart it: use mysql instead of mariadb if applicable. -systemctl enable mariadb && systemctl reboot -``` - -For MySQL, use `mysql` instead of `mariadb` in the commands above. - -### 4.4 Check the connection from the central - -After the reboot, run this on the **central server**, replacing `` with the address of your database server: - -```bash -timeout 3 bash -c '/3306' && echo OK -``` - -It should print `OK`. (This command is used because `nc` is not installed by default.) - -### 4.5 Troubleshooting - -| If you see | What to do | -| --- | --- | -| A file named `50-server.cnf.dpkg-dist` | **Keep your own file** and ignore the new one. The new file sets `bind-address = 127.0.0.1`, which only allows local connections, so the central could no longer reach the database. Your file should have `bind-address = 0.0.0.0` (or the server's IP address) and `utf8mb4`. | -| MariaDB does not start | Run `systemctl start mariadb`, then read the details with `journalctl -u mariadb`. The usual cause is an option in your tuning file that was removed or renamed in the new MariaDB version. | -| `read_only` is 1 | Run `mariadb -e "SET GLOBAL read_only=OFF"`, then delete the `read_only` line from your configuration. That setting is meant for replica servers. | - -## Step 5: Switch the repositories (on every server you upgrade) - -The commands edit your existing repository files (either deb822 *.sources files or one-line *.list files). Do not add a new file next to an old one: the 25.10 and 26.10 repositories would mix. - -```bash -# create a the backup folder -B=/root/upgrade-2610-backup; mkdir -p $B/apt-bookworm -# save the apt repository configuration -cp -a /etc/apt/sources.list /etc/apt/sources.list.d $B/apt-bookworm/ -# back up the Apache configuration file for the Centreon web interface -cp -a /etc/apache2/sites-available/centreon.conf $B/apache-centreon.conf.2510 2>/dev/null -# list the extra apt repository files configured on the server -ls /etc/apt/sources.list.d/ -``` - -### 5.1 On your Debian OS - -Point APT at the Debian 13 repositories instead of Debian 12. It only edits configuration files, nothing is downloaded or upgraded yet. - -```bash -[ -f /etc/apt/sources.list.d/debian.sources ] && sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/debian.sources -sed -i 's/bookworm/trixie/g' /etc/apt/sources.list -grep -rqs "trixie-backports" /etc/apt/sources.list /etc/apt/sources.list.d/ || \ - echo "deb http://deb.debian.org/debian/ trixie-backports main non-free-firmware" >> /etc/apt/sources.list -``` - -### 5.2 On Centreon - -**5.2 Centreon** (any file name: `centreon-25.10-stable.list`, `centreon-stable.list`, …) - -Point the Centreon repositories at the 26.10 packages for Debian 13. It only edits APT configuration files, nothing is upgraded yet. - -```bash -for f in $(grep -lE "packages.centreon.com|centreon.jfrog.io" /etc/apt/sources.list.d/*.list); do - sed -i -E -e 's/bookworm-25\.10-[a-z-]+/trixie-26.10-stable/g' -e 's/ (bookworm|bullseye) / trixie /g' "$f" - echo "== $f"; cat "$f" -done -grep -qs "apt-plugins-stable/\? trixie" /etc/apt/sources.list.d/*.list || \ - echo "deb https://packages.centreon.com/apt-plugins-stable/ trixie main" > /etc/apt/sources.list.d/centreon-plugins-stable.list -mv centreon-25.10-stable.list centreon-26.10-stable.list -``` - -| Repository line | Required? | -| ---------------------------------------------------------------------------------- | --------------------------------------------------------------------- | -| `apt-standard/ …` | **Yes** | -| `apt-plugins-stable/ trixie` | **Yes**: trixie builds of the Perl libs (Net::Curl, Libssh::Session…) | -| `apt-business/ …` | Only with Business modules (**required on the MBI server**) | -| `apt-plugins-testing/ bookworm` (or `apt-plugins-testing trixie` after the switch) | Optional | -| `centreon.jfrog.io/…/apt-connectors-stable/` | Optional | - -File names keep `25.10`: cosmetic (`mv centreon-25.10-stable.list centreon-26.10-stable.list` if you want). - -### 5.3 On the database server - -Run this on every server that hosts a database: the central server (if the database is local), the remote database server, and the MAP or MBI server. - -Update the database repositories for Debian 13. For MariaDB it also changes the version, from 10.11 to 11.8. It only edits APT configuration files and upgrades nothing yet. - - - - -```bash -for f in /etc/apt/sources.list.d/mariadb.sources /etc/apt/sources.list.d/mariadb.list; do - [ -f "$f" ] || continue - sed -i -e 's|mariadb-server/10.11/|mariadb-server/11.8/|' -e 's/bookworm/trixie/g' "$f" - echo "== $f"; grep -vE "^\s*#|^\s*$" "$f" -done -``` - - - - -```bash -[ -f /etc/apt/sources.list.d/mysql.list ] && sed -i 's/ bookworm / trixie /g' /etc/apt/sources.list.d/mysql.list -echo "mysql-apt-config mysql-apt-config/repo-codename select trixie" | debconf-set-selections -echo "== /etc/apt/sources.list.d/mysql.list"; grep -vE "^\s*#|^\s*$" /etc/apt/sources.list.d/mysql.list -``` - - - - -| If… | Do / know | -| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| No `mariadb.*` file | MariaDB comes from Debian: Debian 13 ships 11.8, nothing to do | -| if you have mySQL: `mysql.list` points to `mysql-8.0` | **Stop**: `repo.mysql.com` trixie has no 8.0. Upgrade to 8.4 LTS on Debian 12 first (trixie has `mysql-8.4-lts`, `mysql-9.7-lts`, `mysql-innovation`, plus `mysql-apt-config`, `mysql-tools`) | -| if you have mySQL: debconf line skipped | A later `mysql-apt-config` reconfiguration (`dpkg-reconfigure`, new package version) may write `bookworm` back. With it: kept (checked; prints a harmless `gpg: cannot open '/dev/tty'`) | -| `*.disabled`, `*.old_*` files | Ignored by apt | -| MaxScale line commented in step 3 | Stays commented | - -### 5.4 Check and simulate - -This step is a dry-run check before the real upgrade. It verifies that the repository changes are correct and simulates the upgrade, so you can spot problems while nothing has been modified yet. The comment at the end of each line is the expected result. - -```bash -# check that no active line in the apt source files still points to Debian 12. There should be nothing -grep -rn bookworm /etc/apt/sources.list /etc/apt/sources.list.d/ | grep -v ":\s*#" -# clear apt’s local package cache, then download the package lists from the newly configured Debian 13 repositories. no line should start with W: or E: -apt clean && apt-get update -# simulate the full upgrade without changing anything and save the result to a file -apt-get -s full-upgrade > $B/sim.txt -# check the number of upgraded/new/removed packages -tail -n 3 $B/sim.txt -# check that no simulation file for dependency problems would stop or break the upgrade -grep -iE "broken|unmet" $B/sim.txt -# check which versions the upgrade would install for the web interface, PHP, and the database server -grep -E "^Inst (centreon-web|php8.4-fpm|mariadb-server|mysql-community-server) " $B/sim.txt -# check that the upgrade would remove no Centreon package -grep -E "^Remv centreon" $B/sim.txt -``` - -* If the simulation shows broken packages, stop and restore the sources: `cp -a $B/apt-bookworm/* /etc/apt/`. -* If everything matches the expected results, you can proceed to the real upgrade. If not, fix the repositories first. Nothing has changed on the system at this point, so the check is safe to repeat. - -## Step 6: Upgrade (every server you upgrade) - -This is the real upgrade to Debian 13. It runs the upgrade in the background, in two stages, and then lets you watch its progress. - -```bash -# run the actual Debian 13 / Centreon 26.10 upgrade in the background -systemd-run --unit=upg2610 /bin/sh -c 'export DEBIAN_FRONTEND=noninteractive; O="-o Dpkg::Options::=--force-confold -o Dpkg::Options::=--force-confdef"; apt-get -y $O upgrade --without-new-pkgs > /root/upgrade-2610-backup/upg-step1.log 2>&1 && apt-get -y $O full-upgrade > /root/upgrade-2610-backup/upg-step2.log 2>&1' -# show every 10 seconds whether apt or dpkg is still running. The upgrade is done when both pgrep print nothing -watch -n 10 'pgrep -x apt-get; pgrep -x dpkg; tail -n 2 /root/upgrade-2610-backup/upg-step2.log' -``` - -- Don't interrupt it and don't reboot until it's finished, even if it seems slow (about 1,300 packages). -- Duration: central ~10–15 min, database/MBI server ~6 min, poller ~6 min. -- `systemd-run`: the upgrade survives an SSH disconnection (`openssh-server` is upgraded). -- Wait on the **processes**, not on the unit state (unreliable while systemd itself is upgraded). -- Expected in the logs: `chmod: cannot access '/var/cache/centreon/config/broker/*'` and `…/engine/*`. -- **Do not reboot yet.** - -Then stop Centreon again on the central server. The 26.10 packages restart the services (and cron, if it was upgraded), but the database schema stays at 25.10 until you run the update wizard in step 8. Until then, Gorgone logs `Unknown column 'uid' in 'field list'` / `[legacycmd] Cannot get configuration for pollers` every 15 s. - -```bash -systemctl stop centengine cbd gorgoned centreontrapd cron -## If you have MAP, run this -systemctl stop centreon-map-engine 2>/dev/null -``` - -## Step 7: Checks after the packages - -### 7.1 Run checks - -This step is the post-upgrade verification (7.1 to 7.4), followed by switching the web stack to PHP 8.4. It checks that the upgrade to Debian 13 went cleanly and that nothing was left half-done. The comment on each line is the expected result. - -```bash -# 7.1 list any package that isn’t in a normal state: the command should print nothing -dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' -# search both upgrade logs for warnings and errors: there should be nothing -grep -hE "^(W|E):|dpkg: (error|erreur)" /root/upgrade-2610-backup/upg-step*.log -# check that the Debian version is 13.x -cat /etc/debian_version -# show the installed version of the main Centreon packages and of PHP-FPM -dpkg -l centreon-web centreon-engine centreon-broker centreon-gorgone php8.4-fpm | awk '/^ii/{print $2, $3}' -# 7.2 list any installed packages whose version still carries a Debian 12 marker. There should be only obsolete Debian libs (libperl5.36, perl-modules-5.36…) -dpkg -l | awk '/^ii/ && $3 ~ /deb12/ {print $2, $3}' -# check that three Perl modules used by Centreon still load correctly after the upgrade (if they do, it prints OK) -perl -MCrypt::OpenSSL::AES -MNet::Curl -MLibssh::Session -e 'print "OK\n"' -# 7.3 list the new config files the upgrade set aside for Apache, Centreon, PHP and MySQL/MariaDB -find /etc -name "*.dpkg-dist" -o -name "*.ucf-dist" | grep -E "apache2|centreon|php|mysql" -# 7.4 switche PHP-FPM from the old PHP 8.2 service to the new PHP 8.4 one -systemctl enable --now php8.4-fpm; systemctl disable --now php8.2-fpm 2>/dev/null -# restart Apache -systemctl restart apache2 -# check that the Centreon interface responds (with an HTTP 200 status code) -curl -s -o /dev/null -w "%{http_code}\n" http://localhost/centreon/ -``` - -| If… (7.2 / 7.3) | Do | -| ----------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | -| A Centreon or `lib*-perl` package still `deb12`, or Perl not OK | `apt-get install --reinstall `; check `apt-plugins-stable trixie` (5.2) | -| If you have MAP, `openjdk-17-jre-headless` still `deb12` | Normal: MAP 26.10 uses Java 25 (`openjdk-25-jre-headless`, now default). After validation: `apt purge openjdk-17-jre-headless` | -| `apache2/…/centreon.conf.dpkg-dist` | **Apache merge** (step 2): 26.10 adds the Gorgone websocket `ProxyPass` block | -| `/etc/centreon-engine/centengine.cfg.dpkg-dist`, `/etc/centreon-broker/central-module.json.dpkg-dist` | Keep yours (generated by the export) | -| `/etc/mysql/mariadb.conf.d/50-server.cnf.dpkg-dist` | Keep yours (package sets `bind-address = 127.0.0.1`) | -| If you have MAP, `/etc/centreon-map/map-config.properties.dpkg-dist` | Keep yours: it is a template (`%CENTREON_BROKER_ADDRESS%`, `%CENTREON_PWD%`…) | - -### 7.2 Check the database - -If you have a local database, run this on the central server. If your database is on a separate server, run this on that server, not on the central. - -This step is the database health check after the upgrade. It confirms that the new MariaDB 11.8 is running, writable, upgraded internally, and that the Centreon databases are still there. The comments give the expected result, with the MySQL variant after the dash. - - - - -```bash -# check that mariadb is active (for MySQL, replace "mariadb" with "mysql") -systemctl is-active mariadb -# check that the MariaDB versin is 11.8.x, and read-only is 0 -mariadb -e "SELECT @@version, @@read_only" -# check whether MariaDB’s system tables need upgrading, and print a message telling you what to do -mariadb-upgrade --check-if-upgrade-is-needed && echo "run: mariadb-upgrade" || echo "done" -# check which Centreon databases exist -mariadb -e "SHOW DATABASES" | grep -E "^centreon(_storage|_map)?$" -# show the most recent errors and warnings that MariaDB logged in the last hour -journalctl -u mariadb --since "-1h" | grep -iE "error|warning" | tail -n 20 -``` - - - - -```bash -# check that MySQL is active -systemctl is-active mysql -# check that the MySQL versin is 8.4.x, and read-only is 0 -mysql -e "SELECT @@version, @@read_only" -# check which Centreon databases exist -mysql -e "SHOW DATABASES" | grep -E "^centreon(_storage|_map)?$" -# look for recent MySQL errors and warnings in two different places, because MySQL can log to either one (or both) depending on its configuration -journalctl -u mysql --since "-1h" | grep -iE "error|warning" | tail -n 20 -grep -iE "error|warning" /var/log/mysql/error.log | tail -n 20 -``` - - - - -* If MariaDB isn't active, or the version query shows read_only = 1 (the database refuses writes), use [the troubleshooting table from step 4](#45-troubleshooting). -* If the check prints "run: mariadb-upgrade", run mariadb-upgrade. It takes its login details from /root/.my.cnf. When it works, it finishes with return code 0 after 8 phases, and running the check again reports that no upgrade is needed. - Why this happens: the MariaDB package normally updates the database's internal system tables during the upgrade. It can't do this if the MariaDB root account has a password, and it won't warn you. MariaDB 11.8 then runs on system tables still in the 10.11 format. If root logs in through unix_socket (no password), the package does it by itself, as it did on the database servers we tested. - -## Step 8: Finalize the upgrade on the central server - -### 8.1 On the web interface - -First, clear your browser cache so you don't see old pages from 25.10. (If you use MAP, its documentation has the same step.) - -1. Run the update wizard to 26.10. Click Finish only once. - The wizard log may show `Undefined array key "is_reverse"` in `Update-25.11.0.php`. If you use the Centreon Monitoring Agent, check the connection mode of each agent configuration. It should be set to "agent initiated", which is the default. -2. Update the modules in **Administration > Extensions > Manager**. Update them one at a time, and wait for each to finish before starting the next. - * If you use MAP, update both the MAP module and the MAP widget. They have separate buttons. - * Avoid **Update all**. On both test platforms, it left auto-discovery not updated until a second request. If you use it anyway, check that auto-discovery shows version 26.10. -3. Apply the updates in the Monitoring Connector Manager. - -### 8.2 On the central server - -To restart Centreon on the new version, run these commands on the central server: - -```bash -# clear the web application cache. -cd /usr/share/centreon && sudo -u www-data php bin/console cache:clear -# let the web server and Broker access each other's files. -usermod -a -G centreon-broker www-data -usermod -a -G www-data centreon-broker -# check for invalid Engine and Broker commands. If the check lists any, run it again without **--dry-run** to remove them. (`w:m:c` is short for `web:monitoring-server:clean-engine-broker-command`.) -sudo -u www-data php /usr/share/centreon/bin/console w:m:c --dry-run -# restart the monitoring services -systemctl restart cbd centengine gorgoned centreontrapd -# If you have MAP, start the MAP engine -systemctl start centreon-map-engine -``` - -If you use MAP, check that it works: - -* `systemctl is-active centreon-map-engine` should print `active`. -* Run `for p in $(pgrep -x java); do readlink -f /proc/$p/exe; done`. The result should contain `java-25-openjdk`. -* Run `grep -E "ERROR|Connection with Broker established" /var/log/centreon-map/centreon-map-engine.log | tail -n 5`. You should see that the connection with Broker is established. A few `Error while connecting to Broker` messages are normal while Broker restarts. - -### 8.3 Export the configuration from the web interface - -1. Export the central server's configuration with **Generate**, **Move export files** and **Restart all** checked. If you skip **Move export files**, the new files stay in `/var/cache/centreon/config` and Engine 26.10 keeps using the old configuration. - -2. Restart the services one last time: - - ```bash - systemctl restart cbd centengine centreontrapd gorgoned - systemctl start cron - ``` - - This makes the services load the new configuration and turns scheduled jobs (cron) back on. - -## Step 9: Make sure everything starts at boot, then reboot - -1. Run these commands on the central server: - - - - -```bash -# make sure all Centreon services, the web server, PHP 8.4, cron and the database start automatically at boot -systemctl enable centengine cbd gorgoned centreontrapd snmptrapd.socket php8.4-fpm apache2 cron -# if you have MAP, set the Centreon MAP engine service to start automatically at boot, while hiding any messages it prints -systemctl enable centreon-map-engine 2>/dev/null -# ruen this on the machine that hosts each database: it sets the database service to start automatically each time the server boots -systemctl enable mariadb -# Compare the list of services enabled before the upgrade (saved in step 1.2) with the current list. The only expected difference is php8.2-fpm replaced by php8.4-fpm. Anything else deserves a look. -diff <(awk '{print $1}' /root/upgrade-2610-backup/enabled-units.txt | sort) \ - <(systemctl list-unit-files --state=enabled | awk '{print $1}' | sort) # php8.2 → php8.4 expected - -# reboot the server -systemctl reboot -``` - - - - -```bash -# make sure all Centreon services, the web server, PHP 8.4, cron and the database start automatically at boot -systemctl enable centengine cbd gorgoned centreontrapd snmptrapd.socket php8.4-fpm apache2 cron -# if you have MAP, set the Centreon MAP engine service to start automatically at boot, while hiding any messages it prints -systemctl enable centreon-map-engine 2>/dev/null -# ruen this on the machine that hosts each database: it sets the database service to start automatically each time the server boots -systemctl enable mysql -# Compare the list of services enabled before the upgrade (saved in step 1.2) with the current list. The only expected difference is php8.2-fpm replaced by php8.4-fpm. Anything else deserves a look. -diff <(awk '{print $1}' /root/upgrade-2610-backup/enabled-units.txt | sort) \ - <(systemctl list-unit-files --state=enabled | awk '{print $1}' | sort) # php8.2 → php8.4 expected - -# reboot the server -systemctl reboot -``` - - - - -2. After the reboot, check that everything works: - -```bash -# check that the release version of the Linux kernel the server is currently running is 6.12.x -uname -r -# list all systemd unitsthat are currently in a failed state: there should be 0 -systemctl --failed -# check whether each of the main Centreon-related services is running (each should be active) -for u in centengine cbd gorgoned centreontrapd php8.4-fpm apache2 mariadb centreon-map-engine cron; do printf "%s=%s " $u $(systemctl is-active $u); done; echo -# check that cron files include at least centreon and centstorage -ls /etc/cron.d/ -# check whether something on the server is listening for SNMP traps, which arrive on UDP port 162 -ss -ulnp | grep ":162 " -# check the log rotation configuration for problems, without actually rotating any logs. It should return nothing -logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" -# check whether the centreontrapd service is currently running -systemctl is-active centreontrapd -``` - -| What you see | What it means and what to do | -| -------------------------------------------- | ------------------------------------------------------------------------------------ | -| `snmptrapd` is inactive | Normal on Debian 13. It starts on demand when the first trap arrives. | -| `centreontrapd` is inactive, with exit **0/SUCCESS** | The trap database is empty. See step 10, centreontrapd. | -| `cron` is inactive | Run `systemctl enable --now cron` (See step 1.4.) | -| `logrotate.service` failed (`Ignoring cbd` / `centengine`) | `chmod 644 /etc/logrotate.d/cbd /etc/logrotate.d/centengine`; `systemctl start logrotate` | - -Finally, check the web interface: - -* **Configuration > Pollers**: all pollers are running and were updated recently. There should be no duplicate **Central** entry. (The 26.10 Broker registers the central under a new instance ID, so a duplicate can appear.) -* **Resources Status**: force a check, acknowledge a problem and set a downtime, to confirm they work. -* Graphs are drawn. -* Gorgone is connected. - -## Step 10: Upgrade the pollers (after the central) - -Allow about 6 minutes per poller. Do each poller one at a time. - -1. Back up and update Debian 12. Do the system part of step 1.2, then step 3 (Debian 12 point release and reboot). -2. Stop the monitoring services: - - ```bash - systemctl stop centengine gorgoned centreontrapd - ``` - -3. Upgrade to Debian 13 and Centreon 26.10. Do steps 5.1 and 5.2 (APT repositories, standard and plugins), then step 5.4 and step 6. - After step 5.4, you should see `centreon-poller`, `centreon-engine`, `centreon-broker` and `centreon-gorgone` at 26.10.0, plugins built for `deb13`, and no package removed. -4. Check the result. Do steps 7.1 and 7.2. If `centengine.cfg.dpkg-dist` exists, keep your own file. -5. Reboot, then export the poller's configuration from the central server, with **Generate**, **Move export files** and **Restart** all checked. -6. Check that everything works: - -```bash -# list all systemd unitsthat are currently in a failed state: there should be 0 -systemctl --failed -# all services should be active -systemctl is-active centengine gorgoned centreontrapd -# check the Centreon Engine log to confirm that the engine started with version 26.10 and loaded its configuration -grep -E "Centreon Engine 26.10|Configuration loaded" /var/log/centreon-engine/centengine.log | tail -n 2 -# List active connections on ports 5669 (Broker) and 5556 (Gorgone) (they should be connected to the central server) -ss -tn | grep -E ":5669|:5556" -# check that the file is not empty (it contains the details of the SQLite database file that centreontrapd uses to look up SNMP trap definitions) -ls -l /etc/snmp/centreon_traps/centreontrapd.sdb -# check the log rotation configuration for problems without rotating anything. Should return nothing -logrotate -d /etc/logrotate.conf 2>&1 | grep -E "^error|Ignoring" -``` - -### If `centreontrapd` stops by itself - -If the trap database `centreontrapd.sdb` is empty, `centreontrapd` stops one second after it starts. In `/var/log/centreon/centreontrapd.log`, you will see `MySQL error: no such table: cfg_nagios`. systemd reports `inactive (dead)` with status **0/SUCCESS**, so there is no alert, and **no SNMP trap is processed**. - -To fix it: - -1. In the web interface, go to **Configuration > SNMP Traps > Generate**. -2. Select the poller. -3. Check **Generate traps database**, **Apply configurations** and **Restart centreontrapd**. - -The upgrade does not cause this problem. It was also seen on 25.10 after a simple reboot. - -### What to expect - -- Acknowledgements and downtimes survive the poller upgrade, thanks to retention. -- The `downtimes` history gets a new row when Engine restarts. This is normal. - -## Step 11: Upgrade your MBI server (if applicable) - -The central server needs nothing extra. `centreon-bi-server` is upgraded in step 6, and the MBI module and widgets are updated in step 8. - -On the reporting server, make sure no ETL run is in progress: check with `ps -ef | grep -i etl` that none is in progress. - -### 11.1 Before the upgrade - -1. **Back up the server:** - -```bash -# set up a backup directory -B=/root/upgrade-2610-backup; mkdir -p $B -# back up the server’s configuration and record the list of installed packages before the upgrade. -tar czf $B/etc-$(hostname).tar.gz -C / etc; dpkg -l > $B/dpkg-l.txt -# save the list of systemd units that are set to start automatically, into a text file in the backup directory -systemctl list-unit-files --state=enabled > $B/enabled-units.txt -``` - - Also back up the reporting database, as described on the MBI page [Backing up and restoring MBI](../reporting/backup-restore.md). - -2. **Make sure cron is installed** (see step 1.4). - -```bash -# if cron is installed, the command prints nothing. If it isn't installed, it installs it -dpkg -l cron | grep -q "^ii" || apt-get install -y cron -``` - -3. **Stop the services:** - - ```bash - systemctl stop cbis gorgoned cron - ``` - -### 11.2 Upgrade - -1. Do step 3 (Debian 12 point release and reboot), if not already done. -2. Do steps 5.1 and 5.2 (standard, **business** and plugins repositories), then step 5.3 (MariaDB or MySQL repository). -3. Do step 5.4, then step 6. In the simulation, you should see `centreon-bi-reporting-server`, `centreon-bi-engine`, `centreon-bi-etl` and `centreon-bi-report` at 26.10.0, plus `openjdk-25-jdk`. No package should be removed. - -### 11.3 Check and restart - -```bash -# lists packages that are in an unusual or broken state: there should be nothing -dpkg -l | awk 'NR>5 && $1 != "ii" && $1 != "rc"' -# checks that the centreon-bi-server and centreon-bi-engine packages are in version 26.10.0 -dpkg -l "centreon-bi*" | awk '/^ii/{print $2, $3}' -# check that your versoini of java is openjdk 25 -java -version 2>&1 | head -n 1 -# check which Java version the cbis service is configured to use: it should be java-25-openjdk -grep ExecStart /lib/systemd/system/cbis.service | grep -o "java-[0-9]*-openjdk" -# find new configuration files that an upgrade installed alongside your existing ones, instead of replacing them, for Centreon and MySQL/MariaDB. -find /etc -name "*.dpkg-dist" | grep -E "centreon|mysql" -# check that your MBI database is active (if you have MySQL, replace "mariadb" with "mysql") -systemctl is-active mariadb -# start services -systemctl start cbis; systemctl enable --now gorgoned cron -# check whether the cbis, gorgoned, and cron services are all currently running -systemctl is-active cbis gorgoned cron -# check whether the Centreon MBI scheduled tasks (cron jobs) are in place (engine, purge, backup-reporting-server) -ls /etc/cron.d/ | grep centreon-bi -# should not contain "Connection test … failed" -tail -n 20 /var/log/centreon-bi/cbis.$(date +%F).log -``` - -Then reboot and check again that `cbis`, `gorgoned` and `cron` are active. After 07:30 on the next weekday, `/var/log/centreon-bi/centreonBIETL.log` should show the ETL run. - -### Good to know - -- **Java 25, not 17.** MBI 26.10 uses Java 25. `centreon-bi-engine` pulls in `openjdk-25-jdk`, and `cbis.service` runs `/usr/lib/jvm/java-25-openjdk-amd64/bin/java` directly. The Java 17 left over from Debian 12 is unused. After validation, remove it with `apt purge openjdk-17-*`. - -## Known issues - -| When | You see | Do | -| --- | --- | --- | -| MBI server | Nothing: ETL, purge, backup never run (`cron` absent) | 1.4: install/enable `cron`; check `centreonBIETL.log` next weekday | -| Reboot (central, poller) | `centreontrapd` inactive, exit 0, `no such table: cfg_nagios` | Generate the SNMP traps database, restart centreontrapd | -| Any server, after the upgrade | `logrotate.service` failed, `Ignoring cbd … writable by group or others`; or no logrotate at all (25.10) | 1.4: install logrotate, `chmod 644` cbd/centengine | -| Step 2 | dpkg error, `chmod … .ssh/id_rsa` | `dpkg --configure -a`, all `ii` | -| Steps 2, 8 (extensions) | `cache:clear` error, `Cannot rename` / `Failed to read file …/symfon_` | One module at a time; `cache:clear` alone; check versions | -| Step 8 (_Update all_) | auto-discovery still on 25.10 after the batch | Update it again, check 26.10 | -| Steps 2, 8 (wizard) | Last step sent twice, HTTP 500 | Click Finish once; update done anyway | -| Step 8 (wizard log) | `Undefined array key "is_reverse"` in `Update-25.11.0.php` | Check Monitoring Agent connection modes | -| Export | `auto_reschedule_checks is no longer available` | Warning only | -| Steps 2, 6 (package logs) | `chmod: cannot access '/var/cache/centreon/config/broker/*'` | Harmless | -| 25.10 pollers | Ack closed in history when the service enters a downtime | Pollers on latest 25.10 first; upgrade them soon | -| MBI doc | Java 17 required, no Debian 13 tab, no cron | Follow section 11 | -| Official doc | No Debian 12 → 13 path for 25.10 → 26.10 | This document | -| Step 6 → 8 | Gorgone `Unknown column 'uid'` every 15 s | Stop Centreon again after step 6 | -| Steps 2, 7 (custom Apache) | `centreon.conf.dpkg-dist`, new vhost not applied | Apache merge | -| 4b, 7.3, 11 | `50-server.cnf.dpkg-dist` with `bind-address = 127.0.0.1` | Keep yours | -| Step 7.2 | Plugins / Gorgone cannot load a Perl module | Reinstall from trixie; `apt-plugins-stable trixie` | -| Step 8 export | Engine still on the old config | Export again with **Move** checked | -| Step 9 | `snmptrapd` inactive | Normal (socket-activated) | -| MariaDB 11.8 tools | `mysql: Deprecated program name …` | Cosmetic; use `mariadb` | -| 4b, 7.5 (MariaDB root with a password) | `mariadb-upgrade --check-if-upgrade-is-needed` → needed after the upgrade, nothing logged | Run `mariadb-upgrade` yourself | -| Step 3 | `NO_PUBKEY` on the MaxScale line | Comment only that line | - -## MariaDB/MySQL equivalents - -| Item | MariaDB | MySQL (Oracle `repo.mysql.com`) | -| ---------------- | ----------------------------------------------------- | ---------------------------------- | -| Service, client | `mariadb` | `mysql` | -| Dump | `mysqldump` / `mariadb-dump` | `mysqldump` | -| Centreon package | `centreon-mariadb` | `centreon-mysql` | -| Repository file | `mariadb.sources` or `mariadb.list` | `mysql.list` + `mysql-apt-config` | -| Version | 10.11 → **11.8** (major) | **8.4 → 8.4** LTS, Debian 13 build | -| Data upgrade | `mariadb-upgrade`, run by the package | automatic at server start | -| Root access | `sudo mariadb` if `unix_socket`, else `/root/.my.cnf` | `/root/.my.cnf` | -| Config dir | `/etc/mysql/mariadb.conf.d/` | `/etc/mysql/mysql.conf.d/` | diff --git a/versioned_sidebars/version-26.10-sidebars.json b/versioned_sidebars/version-26.10-sidebars.json index 1168882d2eed..91e251182166 100644 --- a/versioned_sidebars/version-26.10-sidebars.json +++ b/versioned_sidebars/version-26.10-sidebars.json @@ -1328,10 +1328,6 @@ { "type": "doc", "id": "migrate/migrate-from-debian-to-debian" - }, - { - "type": "doc", - "id": "migrate/upgrade-debian-in-place" } ] } From c6137d78604373af22183761c67e49fc37058e33 Mon Sep 17 00:00:00 2001 From: smau Date: Tue, 20 Oct 2026 10:36:23 +0200 Subject: [PATCH 175/179] Fix OS versions for MAP upgrade topic --- .../version-26.10/graph-views/map-web-upgrade.md | 6 +++--- versioned_docs/version-26.10/graph-views/map-web-upgrade.md | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md index 85e2d27c0b4d..98e9dcc2fc14 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md @@ -40,7 +40,7 @@ Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centre 2. Pour mettre à jour le module Centreon MAP, exécutez les commandes suivantes : - + - Sur le serveur central : @@ -55,7 +55,7 @@ Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centre ``` - + - Sur le serveur central : @@ -70,7 +70,7 @@ Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centre ``` - + - Sur le serveur central : diff --git a/versioned_docs/version-26.10/graph-views/map-web-upgrade.md b/versioned_docs/version-26.10/graph-views/map-web-upgrade.md index 6a43a2353139..d7ef31da1b91 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-upgrade.md +++ b/versioned_docs/version-26.10/graph-views/map-web-upgrade.md @@ -42,7 +42,7 @@ For security reasons, the keys used to sign Centreon RPMs are rotated regularly. 2. To update the Centreon MAP module, run the following commands: - + - On the central server: @@ -57,7 +57,7 @@ For security reasons, the keys used to sign Centreon RPMs are rotated regularly. ``` - + - On the central server: @@ -72,7 +72,7 @@ For security reasons, the keys used to sign Centreon RPMs are rotated regularly. ``` - + - On the central server: From d4e6b90b63589a6d73f5776e36ae718fe90f284f Mon Sep 17 00:00:00 2001 From: smau Date: Tue, 20 Oct 2026 10:49:22 +0200 Subject: [PATCH 176/179] Add migration comment (MAP) --- .../graph-views/map-web-upgrade.md | 42 ++---------------- .../graph-views/map-web-upgrade.md | 44 +++---------------- 2 files changed, 10 insertions(+), 76 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md index 98e9dcc2fc14..5c035f6a5bcb 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md @@ -16,7 +16,9 @@ import TabItem from '@theme/TabItem'; Assurez-vous que le serveur central et le serveur MAP fonctionnent sous un [système d'exploitation pris en charge par cette version](../installation/compatibility.md#système-dexploitation). -Si l'un de vos serveurs fonctionne sous un système d'exploitation qui n'est plus pris en charge, vous ne pouvez pas le monter de version directement. Migrez d'abord votre plateforme vers un système d'exploitation pris en charge : +> Vous pouvez monter de version seulement depuis Alma / RHEL / Oracle Linux 9. + +Si l'un de vos serveurs fonctionne sous un système d'exploitation qui n'est plus pris en charge, vous ne pouvez pas monter MAP de version directement. Migrez d'abord votre plateforme vers un système d'exploitation pris en charge : - Pour le serveur central, voir [Migrer une plateforme](../migrate/introduction.md). - Pour le serveur MAP, voir [Migrer l'extension](map-web-migrate.md). @@ -37,10 +39,7 @@ Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centre sudo systemctl stop centreon-map-engine ``` -2. Pour mettre à jour le module Centreon MAP, exécutez les commandes suivantes : - - - +2. Pour mettre à jour le module Centreon MAP, exécutez les commandes suivantes (depuis Alma / RHEL / Oracle Linux 9) : - Sur le serveur central : @@ -54,39 +53,6 @@ Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centre sudo dnf update centreon-map-engine ``` - - - - - Sur le serveur central : - - ``` shell - sudo dnf update centreon-map-web-client - ``` - - - Sur le serveur MAP : - - ``` shell - sudo dnf update centreon-map-engine - ``` - - - - - - Sur le serveur central : - - ``` shell - sudo apt install --only-upgrade centreon-map-web-client - ``` - - - Sur le serveur MAP : - - ``` shell - sudo apt install --only-upgrade centreon-map-engine - ``` - - - - 3. Videz le cache de votre navigateur. 4. Finalisez la mise à jour du module et du widget dans l'interface Centreon **Administration > Extensions > Gestionnaire**. diff --git a/versioned_docs/version-26.10/graph-views/map-web-upgrade.md b/versioned_docs/version-26.10/graph-views/map-web-upgrade.md index d7ef31da1b91..6c1baafe93ee 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-upgrade.md +++ b/versioned_docs/version-26.10/graph-views/map-web-upgrade.md @@ -14,11 +14,15 @@ import TabItem from '@theme/TabItem'; ## Prerequisites +> You can upgrade from + ### Check your operating system Make sure that the central server and the MAP server run an [operating system supported by this version](../installation/compatibility.md#operating-systems). -If one of your servers runs an operating system that is no longer supported, you cannot upgrade it directly. First migrate your platform to a supported operating system: +> You can only upgrade from Alma / RHEL / Oracle Linux 9. + +If one of your servers runs an operating system that is no longer supported, you cannot upgrade MAP directly. First migrate your platform to a supported operating system: - For the central server, see [Migrating a platform](../migrate/introduction.md). - For the MAP server, see [Migrating the extension](map-web-migrate.md). @@ -39,10 +43,7 @@ For security reasons, the keys used to sign Centreon RPMs are rotated regularly. sudo systemctl stop centreon-map-engine ``` -2. To update the Centreon MAP module, run the following commands: - - - +2. To update the Centreon MAP module, run the following commands (from Alma / RHEL / Oracle Linux 9): - On the central server: @@ -56,39 +57,6 @@ For security reasons, the keys used to sign Centreon RPMs are rotated regularly. sudo dnf update centreon-map-engine ``` - - - - - On the central server: - - ``` shell - sudo dnf update centreon-map-web-client - ``` - - - On the MAP server: - - ``` shell - sudo dnf update centreon-map-engine - ``` - - - - - - On the central server: - - ``` shell - sudo apt install --only-upgrade centreon-map-web-client - ``` - - - On the MAP server: - - ``` shell - sudo apt install --only-upgrade centreon-map-engine - ``` - - - - 3. Clear your browser cache. 4. Finalize the update of the module and the widget in the Centreon interface **Administration > Extensions > Manager**. From bb9e3e2a28912f9f8bcac379c86d862c97521594 Mon Sep 17 00:00:00 2001 From: smau Date: Tue, 20 Oct 2026 10:58:23 +0200 Subject: [PATCH 177/179] Restore tab --- .../version-26.10/graph-views/map-web-upgrade.md | 8 +++++++- .../version-26.10/graph-views/map-web-upgrade.md | 8 +++++++- 2 files changed, 14 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md index 5c035f6a5bcb..3d1155241721 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/graph-views/map-web-upgrade.md @@ -39,7 +39,10 @@ Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centre sudo systemctl stop centreon-map-engine ``` -2. Pour mettre à jour le module Centreon MAP, exécutez les commandes suivantes (depuis Alma / RHEL / Oracle Linux 9) : +2. Pour mettre à jour le module Centreon MAP, exécutez les commandes suivantes : + + + - Sur le serveur central : @@ -53,6 +56,9 @@ Pour des raisons de sécurité, les clés utilisées pour signer les RPMs Centre sudo dnf update centreon-map-engine ``` + + + 3. Videz le cache de votre navigateur. 4. Finalisez la mise à jour du module et du widget dans l'interface Centreon **Administration > Extensions > Gestionnaire**. diff --git a/versioned_docs/version-26.10/graph-views/map-web-upgrade.md b/versioned_docs/version-26.10/graph-views/map-web-upgrade.md index 6c1baafe93ee..43fc6956feb7 100644 --- a/versioned_docs/version-26.10/graph-views/map-web-upgrade.md +++ b/versioned_docs/version-26.10/graph-views/map-web-upgrade.md @@ -43,7 +43,10 @@ For security reasons, the keys used to sign Centreon RPMs are rotated regularly. sudo systemctl stop centreon-map-engine ``` -2. To update the Centreon MAP module, run the following commands (from Alma / RHEL / Oracle Linux 9): +2. To update the Centreon MAP module, run the following commands: + + + - On the central server: @@ -57,6 +60,9 @@ For security reasons, the keys used to sign Centreon RPMs are rotated regularly. sudo dnf update centreon-map-engine ``` + + + 3. Clear your browser cache. 4. Finalize the update of the module and the widget in the Centreon interface **Administration > Extensions > Manager**. From f233b60f6b8cb9bdeb7d042ca1bb02eaf57459a2 Mon Sep 17 00:00:00 2001 From: emgcentreon Date: Tue, 20 Oct 2026 11:05:46 +0200 Subject: [PATCH 178/179] removed steps for Debian 13 and EL 10 --- .../version-26.10/reporting/upgrade.md | 102 +++-------------- .../version-26.10/reporting/upgrade.md | 108 +++--------------- 2 files changed, 35 insertions(+), 175 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/upgrade.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/upgrade.md index 2380878e1edd..bedb0563e56e 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/upgrade.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/upgrade.md @@ -6,7 +6,13 @@ description: "Monter de version Centreon MBI vers une nouvelle version majeure" import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -> Lors d'une montée de version < 18.10.x vers une version >= 18.10.x, vous devez: +> Si l'un de vos serveurs tourne sur un système d'exploitation qui n'est [plus supporté](../installation/compatibility.md#système-dexploitation), vous ne pouvez pas monter de version MBI directement. +> Vous devez d'abord migrer votre plateforme vers un système d'exploitation supporté : +> +> - Pour le serveur central, consultez notre [introduction à la migration](../migrate/introduction.md). +> - Pour le serveur MBI, consultez [migrer l'extension](./migrate.md) + +> Lors d'une montée de version < 18.10.x vers une version >= 18.10.x, vous devez : > > - Récupérer une nouvelle licence via le support Centreon > - Vous assurer que votre serveur de reporting est [basé sur un OS supporté](../installation/compatibility.md). Si ce n'est @@ -35,77 +41,21 @@ Vous trouverez ce dépôt depuis votre compte sur notre [platefome de support, Sur le serveur de reporting, vous devez également installer le dépôt standard 26.10 : - - - ```shell dnf install -y dnf-plugins-core dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo dnf clean all --enablerepo=* ``` - - - -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo -dnf clean all --enablerepo=* -``` - - - - -> Si votre serveur de reporting est encore sous Debian 12, n'utilisez pas cette procédure. Suivez plutôt [Mettre à jour Centreon et Debian (12 vers 13) sur le même serveur](../migrate/upgrade-debian-in-place.md#step-11-upgrade-your-mbi-server-if-applicable) : cette procédure met à jour Debian et Centreon MBI en même temps et bascule les dépôts standard, business et plugins vers **trixie**. - -Sur Debian 13, les dépôts doivent pointer vers **trixie**. La ligne du dépôt standard est : - -```text -deb [signed-by=/etc/apt/keyrings/centreon.asc] https://packages.centreon.com/apt-standard/ trixie-26.10-stable main -``` - -La ligne du dépôt Business fournie sur le portail du support doit également utiliser **trixie**. Exécutez les commandes suivantes pour ajouter le dépôt standard : - -```shell -install -d /etc/apt/keyrings -wget -O /etc/apt/keyrings/centreon.asc https://apt-key.centreon.com -echo "deb [signed-by=/etc/apt/keyrings/centreon.asc] https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee /etc/apt/sources.list.d/centreon-26.10-stable.list -apt update -``` - -Vérifiez que toutes les lignes des dépôts Centreon utilisent **trixie** : - -```shell -grep -h "packages.centreon.com" /etc/apt/sources.list.d/*.list -``` - - - - ## Étape 2 : Mettre à jour l'interface 1. Mettre à jour le paquet: se connecter sur le serveur Centreon et exécuter la commande suivante : - - - ```shell dnf clean all dnf update centreon-bi-server ``` - - - -```shell -apt clean -apt update -apt install --only-upgrade centreon-bi-server -``` - - - - 2. Mettre à jour l'interface: se connecter à l'interface web de Centreon et se rendre dans le menu **Administration > Extension > Manager** puis cliquer sur le bouton de mise à jour de l'extension et des widgets. @@ -127,7 +77,7 @@ Vous pouvez maintenant procéder à la montée de version : 2. Puis mettez à jour les paquets, en exécutant la commande suivante : - + ```shell @@ -135,26 +85,6 @@ dnf install -y https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarc dnf clean all dnf update -y centreon-bi\* centreon-perl-libs-common ``` - - - - -```shell -apt clean -apt update -apt install -y --only-upgrade centreon-bi-reporting-server centreon-perl-libs-common -``` - -Assurez-vous que le service **cron** est installé, activé et actif (il peut être absent sur les serveurs installés à l'origine sous Debian 12) : - -```shell -apt install -y cron -systemctl enable --now cron -systemctl is-active cron -``` - -La dernière commande doit renvoyer `active`. - @@ -170,7 +100,7 @@ La dernière commande doit renvoyer `active`. systemctl start gorgoned && systemctl enable gorgoned ``` -## Étape 4 : mise à jour de MariaDB +## Étape 4 : mise à jour de la base de données 1. Arrêtez le service **cbis** : @@ -178,9 +108,9 @@ La dernière commande doit renvoyer `active`. systemctl stop cbis ``` -2. Voir [Mettre à jour MariaDB](../upgrade/upgrade-mariadb.md). +2. Voir [Mettre à jour MariaDB](../upgrade/upgrade-mariadb.md) ou [Mettre à jour MySQL](../upgrade/upgrade-mysql.md). - Sur Debian 13, si le paquet demande s'il faut remplacer `/etc/mysql/mariadb.conf.d/50-server.cnf`, conservez la version actuellement installée (répondez **N**). La version du paquet définit `bind-address = 127.0.0.1`, et le serveur central ne pourrait alors plus accéder à la base de données de reporting. + 3. Vérifiez que MariaDB fonctionne : @@ -188,13 +118,13 @@ La dernière commande doit renvoyer `active`. systemctl is-active mariadb ``` - La commande doit renvoyer `active`. Sur Debian 13, vérifiez également que MariaDB écoute toujours sur toutes les interfaces : +La commande doit renvoyer `active`. 4. Démarrez le service **cbis** : diff --git a/versioned_docs/version-26.10/reporting/upgrade.md b/versioned_docs/version-26.10/reporting/upgrade.md index 77714636cb72..47f688c2c50c 100644 --- a/versioned_docs/version-26.10/reporting/upgrade.md +++ b/versioned_docs/version-26.10/reporting/upgrade.md @@ -6,7 +6,13 @@ description: "Upgrade Centreon MBI to a new major version" import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; -> When updating from version < 18.10 to a version >= 18.10, you need to +> If one of your servers runs an operating system that is [no longer supported](../installation/compatibility.md#operating-systems), 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](../migrate/introduction.md). +> - For the MBI server, see [Migrating the extension](migrate.md). + +> 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](../installation/compatibility.md). You may use the @@ -34,50 +40,14 @@ You will find the new "Business" repository on the "Repositories" page in your [ On the reporting server, you also need to install the 26.10 standard repository: - + ```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el9/centreon-26.10.repo -dnf clean all --enablerepo=* -``` - - - - -```shell -dnf install -y dnf-plugins-core -dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/26.10/el10/centreon-26.10.repo -dnf clean all --enablerepo=* -``` - - - - -> If your reporting server still runs Debian 12, do not use this procedure. Follow [Upgrading Centreon and Debian (12 to 13) on the same server](../migrate/upgrade-debian-in-place.md#step-11-upgrade-your-mbi-server-if-applicable) instead: it upgrades Debian and Centreon MBI together and switches the standard, business and plugins repositories to **trixie**. - -On Debian 13, the repositories must point to **trixie**. The standard repository line is: - -```text -deb [signed-by=/etc/apt/keyrings/centreon.asc] https://packages.centreon.com/apt-standard/ trixie-26.10-stable main -``` - -The Business repository line you get from the support portal must also use **trixie**. Run the following commands to add the standard repository: - -```shell -install -d /etc/apt/keyrings -wget -O /etc/apt/keyrings/centreon.asc https://apt-key.centreon.com -echo "deb [signed-by=/etc/apt/keyrings/centreon.asc] https://packages.centreon.com/apt-standard/ $(lsb_release -sc)-26.10-stable main" | tee /etc/apt/sources.list.d/centreon-26.10-stable.list -apt update -``` - -Check that all Centreon repository lines use **trixie**: - -```shell -grep -h "packages.centreon.com" /etc/apt/sources.list.d/*.list +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 ``` - @@ -85,26 +55,11 @@ grep -h "packages.centreon.com" /etc/apt/sources.list.d/*.list 1. Update the package, run the following commands: - - - ```shell dnf clean all dnf update centreon-bi-server ``` - - - -```shell -apt clean -apt update -apt install --only-upgrade 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. @@ -127,37 +82,12 @@ Now you can start the upgrade process: 2. Then run the following commands: - - - ```shell 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 ``` - - - -```shell -apt clean -apt update -apt install -y --only-upgrade centreon-bi-reporting-server centreon-perl-libs-common -``` - -Make sure the **cron** service is installed, enabled and active (it may be missing on servers originally installed on Debian 12): - -```shell -apt install -y cron -systemctl enable --now cron -systemctl is-active cron -``` - -The last command must return `active`. - - - - 3. Start the scheduler service: ```shell @@ -170,7 +100,7 @@ The last command must return `active`. systemctl start gorgoned && systemctl enable gorgoned ``` -## Step 4: Upgrade the MariaDB database +## Step 4: Upgrade the database 1. Stop the **cbis** service: @@ -178,9 +108,9 @@ The last command must return `active`. systemctl stop cbis ``` -2. See [Upgrading MariaDB](../upgrade/upgrade-mariadb.md). +2. See [Upgrading MariaDB](../upgrade/upgrade-mariadb.md) or [Upgrade MySQL](../upgrade/upgrade-mysql.md). - On Debian 13, if the package asks whether to replace `/etc/mysql/mariadb.conf.d/50-server.cnf`, keep your currently installed version (answer **N**). The package version sets `bind-address = 127.0.0.1`, and the central server would then no longer be able to reach the reporting database. + 3. Check that MariaDB is running: @@ -188,13 +118,13 @@ The last command must return `active`. systemctl is-active mariadb ``` - The command must return `active`. On Debian 13, also check that MariaDB still listens on all interfaces: +The command must return `active`. 4. Start the **cbis** service: From 243038f75de059151308714976f9c3bc71c31fba Mon Sep 17 00:00:00 2001 From: emgcentreon Date: Tue, 20 Oct 2026 11:16:29 +0200 Subject: [PATCH 179/179] Apply batched suggestions from code review Co-authored-by: emgcentreon --- .../version-26.10/reporting/upgrade.md | 3 ++- versioned_docs/version-26.10/reporting/upgrade.md | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/upgrade.md b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/upgrade.md index bedb0563e56e..448e117d3ca6 100644 --- a/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/upgrade.md +++ b/i18n/fr/docusaurus-plugin-content-docs/version-26.10/reporting/upgrade.md @@ -118,7 +118,8 @@ dnf update -y centreon-bi\* centreon-perl-libs-common systemctl is-active mariadb ``` -La commande doit renvoyer `active`.