Recently active topics

Hello.Could you please add an additional check for the remaining life percentage of SSDs to the 'disk-usage' mode of the 'storage::hp::3par::ssh::plugin'?Currently, the plugin retrieves data using the command: "showpd -showcols Id,State,Type,Size_MB,Free_MB".I propose extending this command to include an additional column, 'LifeLeft_PCT'- that is:3PAR01 cli% showpd -showcols Id,State,Type,Size_MB,Free_MB,LifeLeft_PCTId State Type Size_MB Free_MB LifeLeft_PCT 0 normal SSD 872448 785408 99 1 normal SSD 872448 785408 99 2 normal SSD 872448 785408 98 3 normal SSD 872448 785408 96 4 normal SSD 872448 785408 96 5 normal SSD 872448 785408 96 6 normal SSD 872448 785408 97 7 normal SSD 872448 785408 97 8 normal SSD 872448 785408 97 9 normal SSD 872448 785408 9810 normal SSD 872448 785408 9911 normal SSD 872448 785408

Please note that the only procedures supported and maintained by Centreon are those published in the official documentation. If you have a question about this article, post it in the comments.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 start1.1 Take a snapshot of each serverSnapshot 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 dumpsSnapshots 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,

Bonjour,Suite upgrade en 26.10, nous venons de nous apercevoir que nous n’avions plus la possibilité de décrire les arguments dans les commandes Centreon.Est-ce une issue connue ? La méthode a t’elle évoluée ? Dans l’attente de votre retour.Corentin Launay

Hello,we need to upgrade an existing Centreon poller from Centreon 23.10 to Centreon 24.04 in order to align it with our Central server, which is currently running Centreon 24.04.The poller is running Debian 11 (Bullseye).The repository previously used for Centreon 24.04 was:https://packages.centreon.com/apt-standard-24.04-stable/However, the Bullseye distribution is no longer available.The Bookworm distribution is still reachable:https://packages.centreon.com/apt-standard-24.04-stable/dists/bookworm/but its package indexes are currently empty.For example, the current InRelease reports:main/binary-amd64/Packages: 0 bytesmain/binary-all/Packages: 0 bytesAs a result, APT cannot retrieve any Centreon 24.04 standard packages.We have another working Centreon 24.04 server running Debian 12, which was upgraded while these packages were still available.It currently has, among others:centreon-engine   24.04.19-1+deb12u1centreon-broker   24.04.19-1+deb12u1centreon-gorgone  24.04.14-1+deb12u1cent

Dear Customer, Dear UsersThe PHP project has released security updates addressing two critical vulnerabilities, CVE-2026-109618 and CVE-2026-109619, which may allow unauthenticated remote code execution.Centreon Cloud customers Following the announcement, Centreon immediately applied the temporary mitigations recommended by PHP. These changes were deployed without any observed impact on the service.Once the corrected packages became available, they were tested and validated before being deployed across all Centreon Cloud environments.All Centreon Cloud environments are now up to date and protected. No action is required from Centreon Cloud customers. Centreon On-Premise customers - action required PHP is not supplied, packaged or maintained by Centreon. It is installed through the packages provided by your Linux distribution or the community repository used by your organisation.For on-premise installations, the administration and maintenance of the operating system and its dependencies

Bonjour,Je voudrais savoir s’il existe un script d’installation silencieuse pour l’agent CMA sur Windows Server (2019 par exemple)Contexte : - Environnement : Cluster HyperV 2019- Environ 60 machines virtuelles et à 95 % sous Windows Server 2019 (le restant est soit du Linux soit de plus ancien OS Windows)- Quelques QNAP - Mon serveur Centreon est sous Debian 12 - Centreon version 25.10.1- Licence IT 100 activé- Centreon et l’agent Windows (Connexion TLS ‘Agent vers Server’ OK, Certifs générés depuis la VM OK ) semblent fonctionner à 99,99% (un faux négatif sur un disque QNAP, je chercherais pourquoi plus tard )- infos en option : gestion d’un parc informatique d’environ 250 PCs sur 20 sites distants → objectif : Superviser l’ensemble de nos serveurs et j’ai la flemme d’installer / configurer l’agent autant de fois 😂  Dans l’idée, exécuter le script d’installation silencieuse avec ou non les différentes options d’installation telle que le token, l’emplacement du log_file et log_level,

Hi,All is in the title.

Hi,Since the last update (version 20.10.4), I’ve been experiencing issues with my VMware setup. The account field in /etc/centreon/centreon_vmware.json is empty, and when I try to resend the login from the Centreon UI in the "Additional Connector Configurations" section, I get the following error:[parameters.vcenters[0].username] The string is empty, but a non-empty string was expected.This issue occurs on all my vCenter hosts. Do you have a solution? When I recreate a vCenter, it works fine. 

Bonjour,Mon infra Centreon est actuellement en 24.10 avec des serveurs Debian 12. Le but serait de passer en 26.10 avec Debian 13. Mais, sur la documentation officielle, je comprends que 26.10 ne supporte pas Debian 13 et je dois faire une migration. (Matrice des montées de version possibles | Centreon Documentation)Mais sur la même page, je vois que c’est compatible : De plus, sur Watch, je découvre une procédure pour faire exactement ce que je souhaite : Migrating from Debian 12 to Debian 13 on the same server, while upgrading Centreon to version 26.10 | CommunityJe souhaite donc savoir si la 26.10 est clairement et officiellement supportée sur Debian 13 ?Merci d’avance !

Please note that the only procedures supported and maintained by Centreon are those published in the official documentation. If you have a question about this article, post it in the comments.Centreon Infra Monitoring now offers a Matrix42 connector for Centreon Open Tickets, allowing your operators to open Matrix42 incidents directly from the monitoring console. This article provides a detailed guide to the complete configuration process from creating an API token to tracking the ticket within Matrix42. Centreon Open Tickets in a nutshell Centreon Open Tickets is an ITSM integration module. It turns one or more monitoring alerts into a ticket in your IT service management tool, with no copy-pasting between two interfaces.In practice, it lets you:Open a ticket in one click on a host or service in alert, prefilled with the host, service, state, duration and check output. Automatically acknowledge the resource when the ticket is created. Keep the alert ↔ ticket link: the ticket ID is sto

Bonjour,En suivant la procédure d’upgrade 25.10 > 26.10, il est évoqué pour les pollers, de récupérer la clé de déchiffrement en fin de documentation.Mes pollers sont “direct related” au Central.Lorsque je lance la commande avec les creds “admin”, j’ai une erreur “Authentication failed” alors que ces derniers sont fonctionnels en mode web. (et le firewalling poller > central est bien open sur TCP/443)Soit je n’utilise pas les bons “creds admin”, soit il y a une subtilité que je n’ai pas comprise / option non cochée dans le user “admin” ?Je suppose que c’est une nouvelle feature de sécurité liée à la 26.10 (chiffrement des échanges Poller <> Central ?) car je n’ai jamais fais cette action depuis que je m’occupe des upgrades de notre instance (version 21.04) Quelqu’un saurait-il me guider ? Par avance, merci !

Hello,I am experiencing an issue after upgrading my Centreon server to 25.10.13.EnvironmentCentreon Central: 25.10.13 Centreon Web: 25.10.13 Centreon Broker: 25.10.7 Centreon Engine: 25.10.7 MariaDB: 10.11.18 AlmaLinux 9ProblemAfter exporting the configuration from the Centreon Web interface, the broker configuration file is regenerated and the database password is written as an encrypted value:"db_password": "encrypt::..."When cbd starts, it immediately fails with:No usable encrypted password: Decryption finalization failed: error:1C800064:Provider routines::bad decryptThe broker continuously crashes and is restarted by the watchdog.Investigation performedMariaDB is running correctly. The centreon database account works correctly. Manual connection to centreon_storage succeeds:mysql -u centreon -p centreon_storage/etc/centreon-engine/engine-context.json exists. Gorgone, Engine and MariaDB are running correctly. Symfony secrets seem healthy:php /usr/share/centreon/bin/console secrets:l

Hello,I'm experiencing an issue with Centreon 25.10.18 where Centreon Broker fails to start after exporting/reloading the configuration._Environment:_Oracle Linux 8centreon-web-25.10.18-1.el8centreon-central-25.10.18-1.el8centreon-broker-25.10.14-1.el8centreon-broker-cbd-25.10.14-1.el8centreon-engine-25.10.14-1.el8centreon-engine-daemon-25.10.14-1.el8centreon-gorgone-25.10.10-1.el8The database is running on AWS RDS._Problem:_After exporting/reloading the poller configuration, the db_password in:/etc/centreon-broker/central-broker.jsonis generated as an encrypted value:"db_password": "encrypt::..."When cbd is restarted, central-broker-master immediately exits with:[config] [error] No usable encrypted password: Decryption finalization failed: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt[core] [error] Error during cbd exit: No usable encrypted password: Decryption finalization failed: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decryptThe w

At present, Centreon is not yet widely recognized across Canada, particularly in regions such as Western and Northern Canada, including Winnipeg, Saskatoon, Edmonton, and Vancouver. In my opinion, to increase visibility and drive adoption of this platform, it would be beneficial to consider establishing a headquarters or regional offices in these markets.Currently, Centreon appears to have a primary presence in Toronto, while many Canadian IT organizations already rely on well-established U.S.-based platforms such as Datadog, Splunk, and other similar solutions.To strengthen its position in the Canadian market, Centreon will likely need to invest further in local presence, strategic partnerships, and marketing efforts.

Hello Centreon Community, We’re running some tests on Gitlab, and we want to trigger alarms on Centreon once the tests fails. We didn’t find a plugin that can connect Centreon with Gitlab.Is it possible to create alarms in Centreon through API calls ? Is there another alternative to do so without API calls ?We’re using Centreon 2.8.23  

Hello,My two database nodes are now slaves after an unsuccessful attempt to switch from slave to master.I am looking for a way to switch my primary node back to MASTER status. Currently, it is the active one operating in the HA setup. Previous command # pcs resource move ms_mysql    Error: to move promotable clone resources you must use the promotable clone id (ms_mysql-clone)    Error: Errors have occurred, therefore pcs is unable to continue # pcs resource move ms_mysql-clone    Warning: Creating location constraint 'cli-ban-ms_mysql-clone-on-BDD_SECONDARY_NODE' with a score of -INFINITY for resource ms_mysql-clone on BDD_SECONDARY_NODE.            This will prevent ms_mysql-clone from running on BDD_SECONDARY_NODE until the constraint is removed            This will be the case even if BDD_SECONDARY_NODE is the last node in the cluster Result:[root@BDD_SECONDARY_NODE]# /usr/share/centreon-ha/bin/mysql-check-status.shConnection SLAVE Status 'BDD_PRIMARY_NODE' [OK]Connection SLAVE Sta

The new RUST plugins (will) supports SNMPv1?I’m testing on a device that allow only v1 and it seems no.snmpwalksnmpwalk -v1 -c **** 10.*.*.* .1.3.6.1.2.1.1.1SNMPv2-MIB::sysDescr.0 = STRING: ****with rs plugin/usr/lib/centreon/plugins/centreon-plugin-rust-snmp -H 10.*.*.* -v 1 -c **** --json /usr/lib/centreon/plugins/rs-collections/applications-protocol-snmp/sysdesc.json --check-responseUNKNOWN: Could not connect to 10.*.*.*:161 is the hostname and the snmp community correct ? Resource temporarily unavailable (os error 11)With TCPdump I see that it force SNMPv2c GetBulk, a function not present on SNMPv111:41:08.191089 IP (tos 0x0, ttl 64, id 14733, offset 0, flags [DF], proto UDP (17), length 68) 10.*.*.*.59760 > 10.*.*.*.161: [bad udp cksum 0x3caa -> 0x6f89!] { SNMPv2c C="*" { GetBulk(24) R=1 N=1 M=1 .1.3.6.1.2.1.1.1 } }