Unanswered questions

Hi,I recently updated to version 24.10.15 from 24.10.14I also updated some third party plugins at the same time.Since that update I have had the problem that occassionally the services running the plugins (Dell iDRAC among others) are timed out after a while. Could be every other hour or after a day or two.All services using those plugins are moved to “Unknown” with information “(Process Timeout)”Restarting the poller in the GUI solves the problem but why is this happening and any solution?Running the same plugin in the CLI works without any problems so it seems to be a poller issue. OK: All 2 components are ok [2/2 psus]. | 'PSU1#hardware.powersupply.power.watt'=200W;;;0; 'PSU2#hardware.powersupply.power.watt'=180W;;;0; 'hardware.psu.count'=2;;;;Checking poer suppliespower supply 'PSU1' status is 'ok' [instance: 1.1] [value: 200]power supply 'PSU2' status is 'ok' [instance: 1.2] [value: 180]  

SymptomsWhen a host is linked to a host category, the update fails with the following error in the logs:  [ERROR] Rollback of 'PartialUpdateHost' transaction {"custom":{"trace":"#0 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHostValidation.php(258): Core\\Host\\Application\\Exception\\HostException::idsDoNotExist()\n#1 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHost.php(438): Core\\Host\\Application\\UseCase\\PartialUpdateHost\\PartialUpdateHostValidation->assertAreValidCategories()\n#2 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHost.php(183): Core\\Host\\Application\\UseCase\\PartialUpdateHost\\PartialUpdateHost->updateHostCategories()\n#3 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHost.php(152): Core\\Host\\Application\\UseCase\\PartialUpdateHost\\PartialUpdateHost->updatePropertiesInTransaction()\n#4 /usr/shar

Hi,After upgrading the agent to 25.0.4 (from 25.0.3) it returns No storage found (filters issue).The default FILTERSTORAGETYPE from 25.0.3 is hrstoragefixeddisk, and seems not to work and need .*Is ths will be fixed,because it is a problem when you update the agent in mass.Thanks 

Est-il possible d’utiliser le magasin d’autorités de certification Windows plutôt que de devoir spécifier un chemin vers un fichier de certificat en dur ?Les autorités de certification étant déjà déployées sur mes serveurs via des GPO, il serait pertinent de pouvoir s’appuyer sur ce mécanisme existant plutôt que de maintenir des fichiers séparés.  Is it possible to use the Windows Certification Authorities store instead of specifying a hard-coded path to a certificate file?Since the certification authorities are already deployed to my servers via Group Policy, it would make sense to leverage this existing mechanism rather than maintaining separate certificate files.

HelloI’m using the database::oracle plugin to replace the old one I was using before.Almost everything works fine, except that it does not find 2 tablespaces, SYSTEM and UNDOTBS1, which were perfectly found by the old plugin :  $ /usr/lib64/nagios/plugins/Poller/check_oracle_health.sh -connect ALIAS --name SYSTEM --username XXXX --password YYY --warning 90 --critical 95 --mode list-tablespacesSYSTEMOK - have fun$ /usr/lib64/nagios/plugins/Poller/check_oracle_health.sh -connect ALIAS --name SYSTEM --username XXXX --password YYYY --warning 90 --critical 95 --mode tablespace-usageOK - tbs SYSTEM usage is 11.05% | 'tbs_system_usage_pct'=11.05%;90;95 'tbs_system_usage'=565MB;4608;4864;0;5120 'tbs_system_alloc'=632MB;;;0;5120Unfortunately, with the official oracle plugin, it’s not found :  $ /usr/lib/centreon/plugins//centreon_oracle.pl --plugin=database::oracle::plugin --hostname 1.2.3.4 --port 1524 --servicename SID--username XXXX--password YYY --mode tablespace-usage --filter-tables

Hello,I’m facing an issue with discovery jobs stuck in Running state on my Centreon platform.Context Multiple discovery jobs configured per poller Providers used: VMware (ESXi & VM discovery, ~20 jobs with filters) AWX (2 jobs: pre-prod and prod) Pollers are sized according to Centreon recommendations Jobs are scheduled sequentially with intervals, running once per day IssueRecently, some discovery jobs are getting stuck in Running state indefinitely. On the central server, I get errors indicating that the job cannot be launched because it is already in Running state It is impossible to restart the job from the UI (even after waiting a long time and after restarting gorgoned service ) Checks already performed Reviewed gorgoned logs on central and pollers Checked VMware daemon logs on pollers No explicit errors found explaining the blockage Verified that jobs are not overlapping by design (sequential scheduling) Observations The issue appeared recently (no maj

Voici une version adaptée intégrant ce contexte : Bonjour à tous,Nous supervisons actuellement des conteneurs OpenVZ avec Centreon.Nous disposons d’un ancien plugin “fait maison” qui permet de contrôler l’état des conteneurs (notamment la partie démarrage), mais il commence à dater et nous souhaitons savoir s’il existe aujourd’hui une méthode plus standard / officielle pour superviser correctement cet aspect.Notre besoin est de : Détecter un échec de démarrage d’un conteneur Vérifier que le conteneur est réellement en état running Disposer d’un statut clair et fiable dans Centreon (OK / CRITICAL si le conteneur n’est pas démarré) Éviter de maintenir un script custom si une solution packagée existe Nous n’avons pas trouvé de plugin officiel Centreon Plugin Pack dédié à OpenVZ pour cette vérification spécifique.Existe-t-il : Un plugin officiel Centreon compatible OpenVZ ? Une bonne pratique recommandée (via SNMP, agent, API, commande système côté hôte) ? Un mode opératoire vali

Bonjour,J’ai une question par rapport à l’Activité métiers (Business Activity). Récemment, on m’a demandé de créer des activités métiers pour mes serveurs, mes applications hébergées. Cependant, je l’ai créé que depuis la semaine dernière. Cependant, les applications et les serveurs existaient depuis pas mal d’année. Par contre, quand je génère un rapport pour mon activité métier, il n’affiche que les valeurs à partir de la création de l’activité métier pour mes serveurs et mes applications. Est-ce normal? Comment je peux faire pour que ce rapport prend toute l’historique de mes serveurs et de mes applications? Ou ce n’est pas du tout possible?Aussi, j’avais déjà quelques activités métiers en place depuis pas mal d’année. Et j’ai modifié les plages d’horaire de rapport de 24x7 en heures ouvrées de 8h à 20h et aussi supprimer quelques indicateurs non utiles à mes rapports. Est-ce que j’aurai une réécriture de mes historique d’activités métiers dans ce cas là, ou bien c’est comme si je r

Hi,in my Centreon on premise version 25.10.9, if i go the page:Configuration → Connectors → Monitoring Connectorsand i click to the botton “Update all”, i get this error: “An error occured while installing the following monitoring connector :+ base-genericReason: Authentication failed, company not foundSo the following monitoring connector were not processed+ base-generic” while on file /var/log/centreon/license-manager.log a this line appears [2026-04-07T15:35:24+02:00] ERROR : 0|0|[RestUnauthorizedException] https://api.imp.centreon.com/v2/auth/instance : Authentication failed, company not found | {"custom":null,"exception":null,"default":{"request_infos":{"uri":"/centreon/api/internal.php?object=centreon_pp_manager_pluginpack&action=updateAllPluginPacks","http_method":"GET","server":"10.40.11.150"}}} The license is an IT100This issue happened after the upgrade from version 24.* to 25.* How can i fix this issue?     

Following a recent update of the plugins on my Centreon servers, I am facing issues with the Fortinet plugin, specifically impacting the SD-WAN and VPN services. Could you please assist me in resolving this issue? Unknown option: include-vdomain at /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl line 4524.  Unknown option: include-vdom at /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl line 4524.

Hello,Somebody know a fresh project for have a notification per mail with html ?I see GitHub - mcinquin/centreon-notifications: New notifications for Centreon but it’s 9 years old.HTML/formatted Notification | Community stil in the backlog apparently ?Regards,B’

Hello everyone, I have update my centreon of the version 23 to 24.Since, i have this error "SSL certificate problem: unable to get local issuer certificate for" this error appears when I want to add a hostdo you know this problem? How to fix it?

Hello,I am facing an issue on a fresh installation of Centreon 25.10 running on Red Hat Enterprise Linux 9.7.Context Centreon installation: fresh install / from scratch OS: RHEL 9.7 Connector in use: Windows NSClient05 RestAPI License: IT-100 Plugin Pack installed online from the web interface Goal: use Windows disk discovery Issue observedWhen I open the discovery rule:OS-Windows-NSClient05-Restapi-Disk-NameI get the following error in the Centreon web interface:Command execution issue: status code '127'(command: /usr/lib/centreon/plugins//centreon_windows_local.pl --plugin=os::windows::local::plugin --mode=list-storages --hostname=127.0.0.1 --disco-format)Checks already performedThe script called by the rule does not exist on the server:ls /usr/lib/centreon/plugins/centreon_windows_local.pl# ls: cannot access '/usr/lib/centreon/plugins/centreon_windows_local.pl': No such file or directoryThe following plugin package is already installed:dnf install centreon-plugin-Operating

Hello,I am experiencing an issue with my Centreon IT‑100 license. The “Add Token” button is no longer available in my Centreon interface and has been replaced by “Choose Subscription”, which prevents me from re‑registering or activating my token.According to the Centreon community, this situation occurs when an IT‑100 license is still linked to a previous server, and an unlink operation must be performed on Centreon’s side. This was explained in discussions where moderators indicated that the problem happens when the token has already been registered or when an offline license remains attached to the platform.It was also mentioned that only the Centreon team can unlink the license in such cases, and users were asked to provide their server fingerprint so that the operation can be performed. [thewatch.c...ntreon.com] [thewatch.c...ntreon.com]Here is the fingerprint of my current server:👉 11b3a090fa1e2d59e34af7a4c2d7b3d3edd52a67a574584972ec8297b5f921d1Could you please unlink my IT‑100 l

Bonjour,J’essaie de mettre en place CMA sur des serveurs. Pour plusieurs raisons, je ne peux qu’utiliser qu’un certificat auto-signé sur le serveur collecteur.Le certificat est généré sans CN mais avec l’adresse IP en SAN.Malheureusement, sur l’agent j’ai ce message :2026-03-13 14:05:02.070] [centreon-monitoring-agent] [error] [bireactor.cc:97] 0x562fa0ee41a0 client peer:10.0.25.6:4317 fail read from stream[2026-03-13 14:05:02.070] [centreon-monitoring-agent] [error] [bireactor.cc:147] 0x562fa0ee41a0 client peer 10.0.25.6:4317 fail write to stream[2026-03-13 14:05:02.070] [centreon-monitoring-agent] [error] [bireactor.cc:187] 0x562fa0ee41a0 peer:10.0.25.6:4317 client::OnDone(failed to connect to all addresses; last error: UNKNOWN: ipv4:10.0.25.6:4317: Peer name 10.0.25.6 is not in peer certificate) Il ne semble pas voir l’adresse IP dans le SAN. Est-ce que j’ai raté quelque chose ? Merci.

Hello,I’m encountering an issue with ACL behavior after service discovery in Centreon.Environment: OS: Red Hat Enterprise Linux 9.6 Centreon version: 25.10.9 (Central + Poller + MySQL 8) SELinux: disabled Context: I have configured user ACLs to restrict actions (menus, features, etc.). For resources, I did not create any specific restriction since all users should see all resources. Therefore, I am using the default “All Resources” ACL. Issue:When new services are discovered via service discovery: Non-admin users cannot see the newly created services. Even after logging out and logging back in, the services are still not visible. The only way to make them visible is to manually click the “Reload ACL” button. Additional observations: The log file /var/log/centreon/centAcl.log is always empty. Running the ACL reload command manually does not solve the issue: sudo -u apache /usr/bin/php -q /usr/share/centreon/cron/centAcl.php This command produces no output and does not make

I set up an IDP using the pysaml2 python library and want to connect it to Centreon via SAML, but I can’t find the SP Centreon metadata. Where can I find it?

Hi, we have a new DELL ME5012 Storage.is there a Centreon Plugin ? or other plugins / check what can i use for this Storage ?SNMP and so on

Hi,In the 24.10.22 release notes we can read:> [API] The API no longer returns "null" when trying to acces the /monitoring/servers endpoint (it will now returns the IP address of the pollers). What’s about the /monitoring/downtimes endpoint? Shouldn’t all the endpoints with the same erratic behaviour be fixed once? 

Hello,I’m facing an issue with a discovery rule in Centreon where the inclusion filter does not seem to work as expected.Context: I created a discovery rule to include only interfaces with names containing StackPort. My inclusion rule is configured as: Macro: $name$ Regexp: ^StackPort* Expected behavior:Only interfaces like StackPort1, StackPort2, etc. should be discovered.Actual behavior:When I run the discovery command manually, I can see interfaces such as:'StackPort2' [speed = 160000][status = up][id = 124][type = propVirtual]However, when I perform a manual scan from the Centreon UI, the inclusion filter does not seem to apply, and other interfaces are still discovered.Command used to list interfaces in CLI :sudo -u centreon-engine /usr/lib/centreon/plugins/centreon_cisco_standard_snmp.pl --plugin='network::cisco::standard::snmp::plugin' --mode=list-interfaces --hostname='10.0.0.8' --snmp-version='2c' --snmp-community='public' --disco-show<?xml version="1.0" encoding

Bonjour,Je supervise mes switchs cisco avec le connecteur Cisco Standard, cela fonctionne pour l’ensemble des services, sauf deux qui me retournent l’erreur indiquée en titre :spanning-tree AAA serviceLa vue configurée sur les switchs intègrent bien l’ensemble des OID (view ISO).Le spanning tree et le service AAA sont bien configurés sur les switchsJ’ai la même erreur pour tous les switchs (cisco 9200 et 9300)Savez-vous quelle pourrait être la cause de ce retour ?NB : j’utilise la dernière version de Centreon 24.10.21Merci d’avance

I would like a scenario to trigger another scenario as a countermeasure when it is critical, but I don't know how to do it.

Bonjour,Je souhaite avoir des précisions concernant les services de supervision embarqués dans Centreon Monitoring Agent (CMA), notamment sur leur personnalisation.Environnement OS : Red Hat Enterprise Linux 9.6 Plateforme : Centreon 25.10.9 Architecture : Centreon + Poller + DB sur le même serveur SELinux désactivé ContexteLors du déploiement de CMA sur les serveurs, nous constatons que les sondes embarquées sont bien présentes, mais nous ne trouvons pas de moyen clair pour personnaliser leur configuration.En particulier : l’entrée de registreComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Centreon\CentreonMonitoringAgent ne semble pas indiquer de fichier de configuration permettant de modifier ces sondes ; nous souhaiterions adapter certains comportements des contrôles natifs embarqués. BesoinNous aimerions notamment : Modifier la planification de la supervision des mises à jour Windows, ainsi que du contrôle Pending Reboot, pour ne lancer ces vérifications que toutes les 4 heures ; P

I cant find much about the CVE or the Vulnerability and I am unsure how to handle it. Out OpenVAS is reporting a RCE for centreon-web with a WontFix. Is it fixed? Will it be fixed? How to handle it? The Vulnerability is described in this PDF: https://www.synacktiv.com/sites/default/files/2021-07/Centreon_Multiple_vulnerabilities_0.pdfBut the named CVE cant be found andywhere. 

Hi,[root@centreonpollerorcentral sudoers.d]# grep User_Alias /etc/sudoers.d/*[Cc]entreon*/etc/sudoers.d/centreon:User_Alias      CENTREON=%centreon/etc/sudoers.d/centreon-gorgone:User_Alias      GORGONE=centreon-gorgone/etc/sudoers.d/centreon-plugins:User_Alias      CENTREON_COLLECT_USERS=centreon-engine,centreon-gorgone/etc/sudoers.d/sudoersCentreonLinuxPlugins:User_Alias      CENTREON_COLLECT_USERS=centreon-engine,centreon-gorgoneIt raises a warning from sudo, also, what’s this sudoers entry for?