Recently active topics

Hello,Since the upgrade from 24.10 to 25.10, all ping services no longer work.I am using the “Base-Ping-LAN” template and the “base-centreon-ping” command.Linux ALMALINUX 9Over SSH, all my pings work correctly. In my firewall, ICMP traffic passes correctly.Version 25.10.4Was there any change between 24.10 and 25.10?How can this be resolved?I also set up a new VM and a clean installation of Centreon 25.10, I added a host for ping and I'm having the same issue.---------------------Français---------------BonjourDepuis le passage de 24.10 à 25.10, tous les services ping ne fonctionnent plusJ’utilise le modèle “Base-Ping-LAN” et la commande “base-centreon-ping”Linux ALMALINUX 9 En SSH, tous mes pings fonctionnent correctement. Dans mon firewall les flux ICMP passent correctement.Version 25.10.4Y a t’il eu un changement entre 24.10 et 25.10 ?Comment solutionner?J’ai aussi installé une nouvelle VM et une installation propre de centreon 25.10, j’ai mis un hote en ping et j’ai aussi le même sou

A new update for Centreon web 24.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-24.10.16

A new update for Centreon awie 24.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-awie-24.10.3

A new update for Centreon web 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-web-24.04.20

A new update for Centreon awie 24.04 is available. Click the version button in Product Updates to access detailed release notes:centreon-awie-24.04.3

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

Bonjour, Maintenant que j’arrive à faire communiquer correctement mon poller avec quelques clients CMA, je n’arrive toujours pas à superviser les services windows.  J’ai mon service qui est correctement nommé dans le FILTERNAME mais Centreon m’indique le message suivant : Est-ce que vous auriez une idée d’où je me serais trompé niveau configuration? Merci

Bonjour,Je viens de migrer mon centreon 22.10 vers 25.10 centos7 vers Debian12. Tout est parfaitement fonctionnel mis à part les macros des services par groupe d’hôtes qui ne sont plus interprétées et non présentes dans le fichier /etc/centreon-engine/services.cfgEn revanche les macros des services par hôtes et les macros d’hôtes sont elles bien interprétées et présentes dans les fichiers de config.Est ce qu’il y a un changement dans la prise en charge de ses macros ?J’ai essayé de passer par des templates pour mettre les macros mais comme se sont des templates lées à des services de groupes d’hôtes le résultat est le même. Merci pour vos retours 

We are facing an issue with the centreon_vmware process that started after a Centreon update applied in mid-December.Issue descriptionThe centreon_vmware service fails to start with the following error:# systemctl status centreon_vmware.servicecentreon_vmware.service - Centreon VMWareLoaded: loaded (/lib/systemd/system/centreon_vmware.service; enabled)Active: failed (Result: exit-code)Process: ExecStart=/usr/bin/perl /usr/bin/centreon_vmware.pl $OPTIONSStatus: 255/EXCEPTIONCan't use string ("Could not decode JSON from ''...") as a HASH refat /usr/share/perl5/centreon/script/credentialsencryption.pm line 55.LogsThe centreon_vmware.log shows the following messages:No vault config file given. Applying default: /var/lib/centreon/vault/vault.jsonNo Engine context config file given. Applying default: /etc/centreon-engine/engine-context.jsonThe given configuration file /var/lib/centreon/vault/vault.json does not exist.Something happened during init() method that makes Centreonvault not usable

2025-07-20 03:22:57 - DEBUG - => Send data: {"security":{"credentials":{"login":"centreon-gorgone","password":"Jxx5@yyT8!My"}}}Logs, even at debug level should not leak credential of a system user. This log file is by default world readable (/var/log/centreon-gorgone/gorgoned.log).

Bonjour j’ai une version open source de centreon donc aucune licence payante. Cependant j’aurai aimé utilisé le CMA. Cependant dans la doc technique il est indiqué qu’il faut installer les connecteurs de supervisions qui fourniront les modèles pour les hôtes. Mais je n’y ai donc pas accès. Il y a t-il une autre possibilité ?Merci d’avance !

Hello, I’m getting this error right after logging in with my Google account. If I refresh the page the error disappears, but it comes back every time I log in again. I’ve already cleared my browser cache, but it didn’t help. Has anyone had this issue before? Thanks in advance!

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]  

Bonjour,Je demande à l’aide car je sèche depuis plusieurs jours de recherche 😑J’ai lu la doc DSM, debug la partie SNMP, mais j’en arrive toujours au même, les slots restent en status pending et lors de la réception d’une trap j’ai le message dans les log dsm ERROR - [find_slot_id] cannot find slot [alarm id = 23132##APBUREAU [host id = 200] [pool prefix = AP] La partie trap SNMP est ok, le service passif est bien configuré et relié. Je ne trouve pas de problème de configuration. 

🇬🇧Hello,I’d like to monitor a few database files to track their growth and guide the developers. I started testing the CIFS plugin, but I can’t get accurate graphs for all the files in a folder. I finally found a syntax that works.​/usr/lib/centreon/plugins//centreon_protocol_cifs.pl --plugin=apps::protocols::cifs::plugin --mode=files-size --hostname='192.168.0.1' --cifs-username='DOMAIN/USER' --cifs-password='xxxxxxxxxxx' --timeout='' --file='/Depot/truc.1' --directory='/Depot' --max-depth='5' --warning-size='' --critical-size='' --verbose --file='/Depot/bidule.exe' --file='/Depot/machin.exe' --file='/Depot/Test.htm' --file='/Depot/chose.ps1'Listing all the files works, but obviously it doesn’t work if new files are added…So I have two questions:How can I monitor an entire folder without having to list every single file? Is that possible? How many files can I monitor without overloading the system? If I have 2,000 files, will Centreon go crazy trying to display all of them?When I

Hello, I am trying to set up Centreon 24.04 on Debian 12. When I access the Centreon GUI, I encounter a loading issue. Checking the Apache2 logs reveals the following error: [proxy_fcgi:error] [pid 29198] [client 192.168.1.33:61829] AH01071: Got error 'PHP message: PHP Fatal error: Uncaught RuntimeException: Unable to create the "cache" directory (/var/cache/centreon/symfony). in /usr/share/centreon/vendor/symfony/http-kernel/Kernel.php:598 Stack trace: #0 /usr/share/centreon/vendor/symfony/http-kernel/Kernel.php(505): Symfony\Component\HttpKernel\Kernel->buildContainer() #1 /usr/share/centreon/vendor/symfony/http-kernel/Kernel.php(763): Symfony\Component\HttpKernel\Kernel->initializeContainer() #2 /usr/share/centreon/vendor/symfony/http-kernel/Kernel.php(185): Symfony\Component\HttpKernel\Kernel->preBoot() #3 /usr/share/centreon/api/index.php(47): Symfony\Component\HttpKernel\Kernel->handle() #4 {main} thrown in /usr/share/centreon/vendor/symfony/http-kernel/Kernel.php on

A new update for Centreon pp manager 24.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-pp-manager-24.10.7

A new update for Centreon mbi 24.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-mbi-24.10.8

A new update for Centreon map 24.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-map-24.10.13

A new update for Centreon license manager 24.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-license-manager-24.10.5

A new update for Centreon it edition extensions 24.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-it-edition-extensions-24.10.9

A new update for Centreon bam 24.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-bam-24.10.10

A new update for Centreon autodiscovery 24.10 is available. Click the version button in Product Updates to access detailed release notes:centreon-autodiscovery-24.10.9