Centreon Infra Monitoring

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 

Hello,I am looking for a way to install the latest version of Centreon on our platform.I was hoping to find a Docker Image that would make it straightforward, unfortunately I found no image, whether official or not. My only findings was an article describing the installation for a test environment with Vagrant, and hinting on the possibility of doing it with Docker : https://www.centreon.com/blog/comment-demarrer-rapidement-un-centreon-21-04-avec-vagrant/It make me wonder: is there any known limitations with installing Centreon on a docker image or is it just something that no one ever felt the need to document?Thank you for your time!Regards,jla 

Hello,Most of the Centreon web menu pages appear blank since the update. I've cleared my browser cache, tested in incognito mode, and cleared the Symfony cache. Nothing works.I checked the logs in /var/log/apache2/error.log and found this, but it might be unrelated:[Thu May 14 12:46:32.281519 2026] [proxy_fcgi:error] [pid 774:tid 774] [client 82.66.247.24:65357] AH01071: Got error 'PHP message: PHP Warning:  Undefined variable $sessionKeyFreeze in /usr/share/centreon/www/include/Administration/parameters/general/form.php on line 279; PHP message: PHP Warning:  touch(): Utime failed: Syst\xc3\xa8me de fichiers accessible en lecture seulement in /usr/share/centreon/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php on line 178; PHP message: PHP Warning:  touch(): Utime failed: Syst\xc3\xa8me de fichiers accessible en lecture seulement in /usr/share/centreon/vendor/smarty/smarty/libs/sysplugins/smarty_template_compiled.php on line 188', referer: http://xxxxxxxxxxxxxxxxxxxx/

Bonjour a tous, lors de l’update nous avons le message suivant dans apache et la page web reste grise: [Fri Mar 29 14:03:50.300703 2024] [proxy_fcgi:error] [pid 78541] [client 10.80.112.1:62988] AH01071: Got error 'PHP message: PHP Fatal error:  Uncaught  --> Smarty: unable to write file /usr/share/centreon/GPL_LIB/SmartyCache/compile/wrt6606bc364946a0_76211331 <-- \n  thrown in /usr/share/centreon/vendor/smarty/smarty/libs/sysplugins/smarty_internal_runtime_writefile.php on line 60', referer: https://***************/centreon/install/upgrade.php Impossible de mettre a jour, le répertoire en question et ces parent sont tous en:/usr/share/centreon/GPL_LIB/SmartyCache# ls -lrttotal 40drwxrwxr-x 2 centreon centreon  4096 Oct 10 19:14 configdrwxrwxr-x 2 centreon centreon  4096 Oct 10 19:14 cachedrwxrwxr-x 2 centreon centreon 28672 Mar 29 18:45 compile /usr/share# ls -lrt centreontotal 52-rw-r--r--  1 centreon centreon 3203 Oct  2 16:22 container.php-rw-r--r--  1 centreon centreon 5600

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/

Hello,I recently upgraded a Centreon platform from 24.04 to 24.10 on AlmaLinux 9.The upgrade initially failed because of PHP dependency conflicts (PHP 8.1 vs PHP 8.2 modular filtering), but the platform is now running correctly with:PHP 8.2.30centreon-web 24.10.24API responding correctlyGorgone runningPollers and monitoring workingHowever, I still have an issue with host templates.When editing  templates in the UI, I get:"Host template not found"In the logs, I see API calls like:PATCH /centreon/api/latest/configuration/hosts/templates/<id> 2026-05-06T14:39:52+0200] [ERROR] Host template not found {"custom":{"host_template_id":737},"exception":null,"default":{"request_infos":{"uri":"/centreon/api/latest/configuration/hosts/templates/737","http_method":"PATCH","server":"127.0.0.1"}}} [2026-05-06T14:39:52+0200] [DEBUG] Data not found. Generating a not found response {"custom":null,"exception":null,"default":{"request_infos": The templates DO exist in database with:host_register = 0h

Hello,Unable to modify host model after upgrading version  24.10.23 to version 24.10.24, errors are : [2026-05-07T15:23:21+02:00] ERROR : Error during host/hostTemplate update | {"custom":{"hostId":264,"isTemplate":false,"exception":{"message":"You are not authorized to access this resource","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/main.get.php(292): include_once('...')\n#5 {main}"}},"exception":null,"default":{"request_infos":{"uri":"/centreon/main.get.php?p=60101","http_method":"POST","server":"toto.local"}}}

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

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

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

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

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

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 have a strange behaviour in my centreon (Centreon Engine 24.10.17).I´ve configured a passive check, set active checks enabled to no, passive checks enabled to yes, is volatile to no. Also check freshness to no: Now my Application sends an alert via centreon API and the service goes to warning state as expected.As soon as I acknowledge the service the active check command (which is a dummy command) gets executed and the service is in unknown state and therfore not acknowledged. Sticky acknoledge works but is unfortunately no option.So first question: Why is the check command executed on acknowledgement and second: how can I disable that?Thanks in advance

Hi!I’m trying to follow the tutorialto implement monitoring of SAP SCC. Two issues:HTTP basic authentication: it’s not clear from the tutorial how to get a plain simple HTTP basic auth. Took me hour to figure out (use the source, Luke!) that you just need to pass ‘basic’ like this: "authorization": {"basic": 1,"username": "%(constants.username)","password": "%(constants.password)"}, I would add it to the original post, but the comments are locked. Please add it, so people save a lot of time. Path depth. SAP will respond with a JSON of this type: { "subaccounts": [ { "description": "SAP BAS", "displayName": "SAP BAS", "tunnel": { "state": "Connected", "connectedSinceTimeStamp": 1720773876375, "connections": 0, "applicationConnections": [], "serviceChannels": [], "subaccountCertificate": { "notAfterTimeStamp": 1749540416000, "notBeforeTimeStamp": 1718000816000, "subjectDN": "CN=B0CADA20E31311EBBF8AD