Unanswered questions

Hello,After upgrading Centreon on AlmaLinux 9 from version 24.10.23 to 24.10.24, I am no longer able to modify any host, for example rename it.When I try to save the modification, I get the following error message: Unexpected return statusI am able to clone the host, but modifying an existing host is not possible.In /var/log/centreon/centreon-web.log, I can see the following error:[2026-05-05T14:23:47+02:00] ERROR : Error during host/hostTemplate update | {"custom":{"hostId":332,"isTemplate":false,"exception":{"message":"Unexpected return status","trace":"#0 /usr/share/centreon/www/include/configuration/configObject/host/DB-Func.php(2912): callHostApi()\n#1 /usr/share/centreon/www/include/configuration/configObject/host/DB-Func.php(2820): updateByApi()\n#2 /usr/share/centreon/www/include/configuration/configObject/host/formHost.php(1156): updateHostInAPI()\n#3 /usr/share/centreon/www/include/configuration/configObject/host/host.php(102): require_once('...')\n#4 /usr/share/centreon/www/

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.

Bonjour,Nous avons plusieurs tâches de découvertes d’hôtes .Existe-t-il un plugin permettant de remonter une alerte dans le cas d’erreur ou de dysfonctionnement d’une tache de découverte?Aujourd’hui le seul moyen , que je connaisse, pour vérifier l’état des taches est d’aller manuellement regarder dans le menu  Configuration > Hôtes > Découverte.Cdt

Hi there,We’ve just purchased several Cisco Catalyst 1300 switches.The OS has changed with these switches, meaning the standard templates are no longer working, namely Environment, Memory and CPU.Has anyone bought those same switches and looked into it?Thanks,Elise

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

Bonjour,Nous utilisons Centreon 25.10 sur des serveurs RHEL 9.6 avec le Centreon Monitoring Agent, CMA, pour superviser des serveurs Windows en mode push.Nous utilisons le service template Windows CMA suivant :OS-Windows-Services-Auto-Centreon-Monitoring-Agent-customL’objectif de ce contrôle est de superviser les services Windows configurés en démarrage automatique et actuellement arrêtés.Le service est configuré avec les macros suivantes :STARTAUTO = trueFILTERNAME = .*FILTERDISPLAY = .*SERVICE_TYPE = serviceSTART_TYPE = autoCRITICALSTATE = stoppedMalgré la valeur SERVICE_TYPE=service, le contrôle remonte plusieurs Windows Kernel Drivers comme des services arrêtés.Exemple de retour d’alerte :CRITICAL: services: 4 stopped, 132 runningCRITICAL: dam is stoppedCRITICAL: sacdrv is stoppedCRITICAL: SentinelELAM is stoppedCRITICAL: WdBoot is stoppedSur le serveur Windows, ces objets ne sont pas des services Windows classiques visibles dans services.msc. Ce sont des Kernel Drivers.Vérificatio

!-->Followed https://docs.centreon.com/docs/installation/installation-of-a-central-server/using-virtual-machines/ to install the latest 25.10 Alma OVA on an ESXi 6.7 host. Had to manually start the VM, root login & setup seemed to work. Login to web UI also worked ... except I ended up right in the main interface, never got to see the install wizard. I guess I can poke around and manually apply all the things the wizard does. But isn't there a way to force an initialization from scratch? I have already re-run the OVA install with the same result. It looks a bit fishy as it doesn’t ask for any parameters, but just dumps a minimally sized VM with DHCP.

Hello everyone, I'm having an issue—apparently a communication problem—between my two collectors and my central server. After investigating and conducting extensive research, particularly in the logs, I'm seeing errors when reading the socket data coming from the poller's IP. Here's an excerpt:Central:central-broker-master.logPoller 1:centengine.log For your information, the operating systems are AlmaLinux 8 for the central server and AlmaLinux 9 for the pollers. I installed the latest updates on 25.10.25 Could you help me resolve this issue and let me know if there are any similar cases currently? Thank you.

since update to 22.04.13, my partition /var/log is saturated.(centreon 22.04.13 /debian 11)in options log of engine configuration “  Syslog Logging Option “ was set to yesi set it to “no” but with no effect, every logging of centreon are looging to syslog it seems that all a other options of logging has no effecti’ve set every logging to “no” but still no effect (restart config; reboot central ...) to sum up :logging options of poller/engine configuation are not taken into accountdoes anybody has this problem, and how to solve it ? thanks

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?     

Bonjour,suite à la mise à jour de centreon (passage à la version 25.10), la licence IT semble ne plus fonctionner.Dans Administration\Extensions\Gestionnaire, elle est bien active (Date de fin de licence : 31/12/9999). J’ai vérifier l’empreinte “Fingerprint” dans le fichier de licence /etc/centreon/license.d/epp.licence ainsi que les permissions d’accès. Tout est OK.Cependant dans Configuration\Connecteurs de supervision, je ne vois plus de connecteurs, j’ai le message “Aucun connecteurs de supervision trouvé”.Dans Administration\Paramètres\Centreon web, le test “Tester la connexion Internet “ échoue, j’ai le message suivant : Could not establish connection to Centreon IMP servers (Page not found)Dans le fichier log /var/log/centreon/license-manager.log, j’ai lerreur suivante : ERROR : 0|0|[RestNotFoundException] https://api.imp.centreon.com/api/license-manager/instance/subscription : Page not found.Le test avec la commande “curl -s https://api.imp.centreon.com/api/license-manager/inst

I am usring /usr/lib64/nagios/plugins/check_centreon_nrpe3 to monitor windows CPU/Memory. And centreon can get CPU & Memeory status. But when I use the same command try to monitor disk space, system show error:Failed to execute check_drivesize: 2: ϵͳÕÒ²»µœÖž¶šµÄÎÄŒþ¡£. The full command is bellow./usr/lib64/nagios/plugins/check_centreon_nrpe3 -H 10.3.3.200 -p 5666 -2 -P 8192 -2 -P 8192 -n -c check_drivesize -a "drive=C:" Centreon version is 25.10. NSClient version is 0.11.24 The nsclient.ini files: [/modules]CheckEventLog = 1CheckNSCP = 1CheckSystem = 1CheckDisk = 1CheckService = 1WEBServer = 1NRPEServer = 1NSClientServer = 1CheckExternalScripts = 1CheckHelpers = 1[/settings/NRPE/server]verify mode = peer-certtls version = tlsv1.2+insecure = falsepassword = *allowed hosts = 10.3.3.10,127.0.0.1port=5666use ssl=falsepayload length=8192allow arguments = 1allow nasty_meta_chars = 1allow nasty characters = 1[/settings/default][/settings/external scripts]allow arguments = 1allow nasty_met

Bonjour,Je souhaite installé un nouveau paquet qui est Linux/Windows CMAMais j’ai un message d’erreur quand je clique sur “+” : Unauthorized: Authentication failed, matching instance is null Ma licence est pourtant marqué “valide”Je suis en version 24.10.14 Quelqu’un a déjà eu ce problème ?Merci d’avance pour vos retours.Bonne journée

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 

Hi all,I’m figureing out how to monitor Centreon MAP with the Centreon MAP pack.An api username/password is asked but where can I found these elements ?jfr

Bonjour,Depuis que j’ai migré vers la version 25.10.5, je suis obligé de redémarrer mon collecteur tous les jours.Le matin je me connecte et le collecteur semble tourner mais nb de machines : 0 et sur la ligne je retrouve la date de la dernière mise à jour de mon collecteur sur fond Orange.Je redémarre mon collecteur et tout se remet à jour naturellement...Comment puis-je outrepasser cette opération qui n’était pas nécessaire sur la version précédente. Il doit y avoir un paramètre qui bloque l’uptime du collecteur.Merci pour vos retoursBonne journée 

Here is the English translation of your text:---I have installed Centreon version 25.10.9 on a Red Hat 8 operating system. I am using the open-source edition. The server IP is 192.168.1.100. I added a poller with the IP 192.168.1.101. This poller encountered a failure, so I completely reinstalled it on a virtual machine, keeping the IP address the same as 192.168.1.101. The OS is still Red Hat 8. I successfully registered the poller to the server, but when I check the web interface under Configuration > Pollers, it shows that this poller is not running.The poller's log file at /var/log/centreon-gorgone/gorgoned.log contains the following errors:```2026-04-26 21:04:39 - ERROR - [core] unknown identity: proxy-1-2-bdaf280f86b038d7ec34c7862026-04-26 21:04:39 - ERROR - [core] unknown identity: obGRGh1cHuwvZPYCNdVpwH1UrOVxYCUbbSSp4CF2oxc=2026-04-26 21:04:39 - ERROR - [core] unknown identity: proxy-1-2-bdaf280f86b038d7ec34c7862026-04-26 21:04:39 - ERROR - [core] unknown identity: obGRGh1cH

Hello The Watch,We are updating from version 24.10.23 to 25.10.10.We are encountering an error during installation. CMA is blocking the update... Thanks a lot,Best Regards,Vincent

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

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

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

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

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’