Recently active topics

!-->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.

Fresh install on Alma 9 as per Unattended installation of a central server | Centreon Documentation.Simple single server for everything setup. GUI seems to work, but the poller does not  come up: # systemctl restart centengine# systemctl status centengine | nl     1  × centengine.service - Centreon Engine     2       Loaded: loaded (/usr/lib/systemd/system/centengine.service; enabled; preset: disabled)     3       Active: failed (Result: exit-code) since Tue 2026-04-28 14:48:08 CEST; 5s ago     4     Duration: 42ms     5      Process: 67873 ExecStart=/usr/sbin/centengine /etc/centreon-engine/centengine.cfg (code=exited, status=1/FAILURE)           …    15  Apr 28 14:48:08 dev12 centengine[67873]: No module configuration file provided in the Engine configuration file.    16  Apr 28 14:48:08 dev12 systemd[1]: centengine.service: Main process exited, code=exited, status=1/FAILURE    17  Apr 28 14:48:08 dev12 systemd[1]: centengine.service: Failed with result 'exit-code'.What do I have to

Bonjour j’aimerai passer à la version 25.10. SI jamais celle ci me pose des problèmes est ce que le downgrade de version est-il possible ou faut-il privilégier de restaurer une backup de la 24.10 ?

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,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?     

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

Bonjour,Avec l’agent CMA, est-il possible de faire remonter le nombre d’utilisateurs connectés simultanément, et dans l’idéal, les logins ?Merci d’avance !

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]  

Every month, Centreon extends its monitoring connector catalog and implements new ones, allowing you to connect your IT monitoring with more ITOps tools.The result: increased visibility and business observability capabilities. We also offer enhancements and fixes on existing connectors. Here is the latest news on your best allies: our monitoring connectors!This April update includes a lot of enhancements and bug fixes, as well as three new connectors : Hitachi E Series CMA, Linux Libvirt SSH and Palo Alto firewall API . More details on this month’s monitoring connectors can be found in the release note.Would you like to contribute or suggest improvements? Join us on The Watch or GitHub, where you can also show your support by giving us a star.Additionally, feel free to participate in discussions about plugins and connectors (monitoring packs, Plugin Packs) right here on The Watch.See you next month for more new features!

The Watch celebrates its 4th anniversary… and brings you giftsIt has now been four years since The Watch has been serving the Centreon user community. Four years of shared experiences, valuable contributions, peer support, and passionate discussions around IT monitoring.To mark this milestone and end the year on a high note, we are thrilled to announce the launch of the The Watch Loyalty Program! A program that rewards your engagementYour actions on The Watch, whether asking a question, posting an answer, liking, voting, etc already allow you to earn points. What’s new as of today is that these points can now be converted into real physical rewards, delivered straight to your home: mugs, backpacks, water bottles, and many other Centreon-branded items. How does it work?It couldn’t be simpler: You are an active member of The Watch. Your actions automatically earn points, visible on your profile or in the community leaderboard. These points are transferred in real time to the The Watc

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

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.