Infra Monitoring Platform

Hello, Since the update from 24.10.15 to 24.10.18, the graph date picker is broken on our instance.Quick time ranges like “Last 3 hours” are working normally but if we want to zoom on a graph or set a manual time range, it fails 100%. The issue comes from the Javascript not selecting the right start/end date for the API call. In browser console we’ve got messages like :moment-timezone-with-data.min.js:1 Moment Timezone has no data for 2026-02-03 09:48. See http://momentjs.com/timezone/docs/#/data-loading/.moment-timezone-with-data.min.js:1 Moment Timezone has no data for 2026-02-03 10:24. See http://momentjs.com/timezone/docs/#/data-loading/.moment-timezone-with-data.min.js:1 Moment Timezone has no data for 2026-02-03 09:48. See http://momentjs.com/timezone/docs/#/data-loading/.moment-timezone-with-data.min.js:1 Moment Timezone has no data for 2026-02-03 10:24. See http://momentjs.com/timezone/docs

I downloaded the VMware version 25.10.deb12.standard-1766075705.ovaI then followed these instructionshttps://docs.centreon.com/docs/installation/installation-of-a-central-server/using-virtual-machines/Unfortunately, despite this I cannot connect with a web browser.I can ping the ip address but I also cannot ssh onto the server with puttyFells like I am missing some instructions

Hi,When “Detection by browser” is selected, and while my browser is set to en_US, there are numerous part in the UI that are still displayed in French.It’s ok (ie: all is displayed in English) if I set “en_US” in my Centreon profile.

Hi,I migrated Centreon from 23.10 to 24.10.17 on January 22. I've been notified of a problem with the export, which no longer works in Customviews.For example, export from a service-monitoring :/var/log/php-fpm/centreon-error.log[09-Feb-2026 10:35:16 UTC] PHP Warning: Undefined variable $db in /usr/share/centreon/www/widgets/service-monitoring/src/export.php on line 443The rest of the interface works fine.I have a development platform with the same version number on which I cannot reproduce the problem. It works fine.Anay idea ?

Hello,Are there any checks available to verify:See for a check on the status of managed devices (synchronised/conflict, etc.) (Fortimanager) For storage, see for provisioning monitoring and an alert above 80% (ESX)  

Hello,I’m in the process to upgrade/mirgrate from 21.04 to 24.10.The “Central” is working and now I’m deploying new “Remote Poller” by following the procedure :Migrate from an EL-type OS to Debian | Centreon DocumentationSo I install a fresh Debian 12 and install the package as indicated here Migrate from an EL-type OS to Debian | Centreon DocumentationHowever the documentation is unclear to me …Once the remote poller installation is OK, I just have to replace the configuration on the central and try to push the configuration ?If its the case, then the conf cannot be pushed.Should we “register the server” ? I suppose no as it

Hi, I’ve recently installed a mediawiki server and configured in the Centreon settings.But when I look in the cron logs I can see :root@STR-PRD-L-CEN01:~# tail /var/log/centreon/knowledgebase.logWiki is not configured. You can disable cron in /etc/cron.d/centreon for wiki synchronization.Wiki is not configured. You can disable cron in /etc/cron.d/centreon for wiki synchronization.In the database, I can see the rights settings :MariaDB [centreon]> SELECT * FROM options WHERE options.key LIKE 'kb_wiki%';+---------------------+--------------------------------------------+| key                 | value                                      |+---------------------+--------------------------------------------+| kb_wiki_password    | ****************                    || kb_wiki_url         | https://centreon.********/mediawiki/ || kb_wiki_account     | centreon                                   |

Hello,I want to change some common services using the “mass change” option with the “replacement”.When applying the new config, I get a blank page.Appache error.log display the following error when applying the config :[Fri Feb 20 11:53:57.636143 2026] [proxy_fcgi:error] [pid 373731:tid 373731] [client XXXXXXXXX:1111] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught InvalidArgumentException: The command ID does not exist. in /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php:2711\nStack trace:\n#0 /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php(1608): updateService_MC()\n#1 /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php(1536): updateServiceInDBForOnPrem()\n#2 /usr/share/centreon/www/include/configuration/co

Hello, i upgrade this morning in 25.10.8, i have all my snmp metric in error… When i try in command line : I see : --snmp-community='encrypt::encryptchain” i have a UNKNOWN: SNMP GET Request: TimeoutWhen I replace 'encrypt' with the name of my unencrypted community, I get“OK: Ram Total: 7.57 GB Used (-buffers/cache): 733.53 MB (9.46%) Free”Thank you in advance; most of my metrics are malfunctioning.Best regards 

Hello everyone,I have a question regarding the X509 Certificate check (https://docs.centreon.com/pp/integrations/plugin-packs/procedures/applications-protocol-x509/)I’m wondering if its possible to check the whole chain of certificate ?The situation is as follow :ROOT → CA → CERTThe Root is still OK The CA cert is expired The Cert is OK (but signed with a expired certificate)The usecase is when we are using deepssl.So that’s mean we will never see the cert in CRITICAL status, but only when the CA will be expired.UNKNOWN: Error creating SSL socket: , SSL error: SSL connect attempt failed error:0A000086:SSL routines::certificate verify failed I’m now wondering if we can monitor the whole cert chain for

I’ve installed a fresh server Debian 12 with Centreon 25.10But  the Custom View is not listed with the Home entry.I only got the Dashboard entryIs there some option to activate this menuI’ve already checks the ACL

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

Hi,I project to migrate to 25.10 and I install a new server on almalinux 9.6.I’m following the installation from the official documentation, and when I reached the MariaDB installation step, there was a conflict with mysql-common :  Total                                                                                                                                                                                                         13 MB/s | 192 MB     00:14Test de la transactionLa vérification de la transaction a réussi.Lancement de la transaction de testLes paquets téléchargés ont été mis en cache jusqu’à la prochaine transaction réussie.Vous pouvez supprimer les paquets en cache en exécutant « dnf clean packages ».Erreur : Erreur de la transaction de test :  le fichier /usr/share/mysql/charsets/Index.xml entre en conflit avec les tentatives d'installation de mysql-common-8.0.43-1.el9_6.x86_64 et MariaDB-comm

HiWhen i want to add services on hosts, i have this message in centreon-error.log : PHP Fatal error:  Uncaught InvalidArgumentException: The command ID does not exist. in /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php:2123Stack trace:#0 /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php(1863): insertServiceForOnPremise()#1 /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php(1826): insertServiceInDBForOnPremise()#2 /usr/share/centreon/www/include/configuration/configObject/service/formService.php(1159): insertServiceInDB()#3 /usr/share/centreon/www/include/configuration/configObject/service/serviceByHost.php(108): require_once('...')#4 /usr/share/centreon/www/main.get.php(277): include_once('...')#5 {main}  thrown in /usr/share/centreon/www/include/configuration/configObject/service/DB-Func.php on line 2123 I use cen

Hello everyone,We are migrating our Centreon 21.04.20 version to the latest version 24.04.We built a new Debian server and a fresh install of Centreon, it is running correctly.Now that we are ready to migrate to this platform, we have the following error when importing the centreon_storage SQL export.Deadlock found when trying to get lock; try restarting transaction The export file is around 16G and the import to the mariadb is very slow. Did you have any ideas to solve this issue ?​​​

Hello,I have a strange behavior regarding the “ping” command.The command return that the host is down but the status displayed is “UNKNOW” instead of “CRITICAL”, is it a bug or a bad configuration due to upgrade from 24.10 to 25.10 ?The test in SSH return the good status. 

Hi,  currently i run on the last 24.10.18 .i want to change the password for a local user.. but there is no password field ?no SAML/or WEB SSO , standard login with LDAP user an local user what can i do ? it is a BUG ?

Bonjour,Nous utilisons actuellement la version 22.10.25 de Centreon (sous licence) sur RHEL 8 et souhaitons faire évoluer le produit vers la dernière version pleinement supportée et maintenue.Est-il possible de se faire accompagner par le support Centreon ? Existe-t’il à défaut des documents techniques permettant de garantir une migration ? Est-il déjà possible de disposer de conteneurisation ?Merci pour vos retours,Bien cordialement,Jean

Lorsque l’on met le service en downtime, les check sont toujours fait.Est-ce qu’il faudrait passer le service en mode passif ?Est-ce que l’option “disable service check when host is down” pourrais être également mis en place sur les downtimes ?

Lorsque l’on a un host qui est en mode désactivé, les services associés ne s’affichent pas dans la vue des services.Il est donc impossible de vérifier/modifier ces services.Est-ce logique ?Je suppose que c’est le choix fait au niveau du Centreon Core.