Unanswered questions

Pour une supervision sur des serveurs windows avec CMA, pourquoi centreon remonte des chiffres en PetraBytes ou ExaBytes lorsque l'occupation du swap augmente alors que la taille qui lui est alloué n'est que de quelques Giga ?Merci d’avance ! 

There is a typo error on the last perl for Merakisub get_network_wireless_usage_history {      my ($self, %options) = @_;      return $self->request_api(          endpoint => '/networks/' . $options{network_id} . '/wireless/usageHistory',          get_param => [              'deviceSerial ='. $options{serial},              'timespan=' . $self->{timespan} ],          hostname => $self->get_shard_hostname(serial => $options{serial})      )  } sed -i "s/'deviceSerial ='/'deviceSerial='/" /usr/lib/centreon/plugins/centreon_cisco_meraki_restapi.pl If it can help somone ...

Hi, is there an manual , how can i reset the password for my local “admin”  account ? LDAP Admin - no problem Thanks

Hi,I don’t know if it changed recently or if it has always be like that, but I noticed the following: if --expected-content has a value, then --critical-content is ignored. It means, if one want to check both a return code and the presence of a string in the page content, one should not use --critical-content=’ %{code} != 200 and %{code} != 401’ --expected-string=foo (because then only the presence of “foo” would be checked!), but what must be used is  --critical-content=’ %{code} != 200 and %{code} != 401 or %{content} !~ /foo/mi’.Is it something that changed recently? Is this something reliable (ie: it won’t change in the futur) ? 

Hello, one of my clients has reported that they are having trouble accessing their Centreon platform in production following an automatic version update on their server.How can this feature be disabled in Centreon?Thank you for your help

Hi all,After upgrading my centreon server from 24.10.28 to 24.10.29, i have the following message in Veeam NRPE pack, Job-Status template :Unknown option: job-source at C:\Windows\TEMP\par-5349522d5341555645474152444524\cache-aae92fcc173f7627981cd721c3222fff97df252e\inc\lib/centreon/plugins/alternative/Getopt.pm line 81.I didn’t had previoulsy this messageI tried to update my centreon nsclient++ to the latest on my veeam server, but had still thisSomeone could tell me how to fix that?Thanks!

Hello I’am checking the sensor component but I have criticals when ethernet is down and as no amperes which is normal. Sensor 'Ethernet1/26 Lane 1 Transceiver Bias Current Sensor/300044004' is 0 A  How can I filter this I tried several ways with no result.  --filter='(?!.*is.*0.*A.*)'--filter='(?!.*is.*0.*)'-filter='^(?!.*is.*0.*)'--filter-perfdata-adv='not (%(value) == 0)'--filter-perfdata-adv='not (%(label) !~ "sensors.amperes.*")'--filter-perfdata-adv='not (%(label) =~ "sensors.amperes.*")'--filter-perfdata-adv='not (%(label) == "sensors.amperes.*")'

Hello Centreon Support Team, I initially installed Centreon on CentOS. Since CentOS is no longer supported, I migrated my server to AlmaLinux by performing a fresh installation and then restoring my Centreon database. The migration went smoothly. Everything is working correctly: the platform is operational, the supervision is functioning as expected, and I have not encountered any issues except one. I am unable to activate my IT-100 license. During the activation process, I receive an error indicating that the instance is already registered. I have attached the relevant log messages below."timestamp":"2026-07-01T16:00:11.186Z","path":"\/v2\/license-manager\/instance","message":"Instance already registered.","code":409,"company":"@LACCESS.XXXXXXXXXXX","fingerprint":"XXXXXXXXXXXXX","client":"user","it100":true} | {"custom":null,"exception":null,"default":{"request_infos":{"uri":"/monitoring/api/internal.php?object=centreon_license_manager&action=registerInstance","http_method":"POST"

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.

Hello,I try to monitor our docker swarm with Centreon and I’m facing an issue with “service status” check of the docker plugin pack (API not SSH)Got a task in desired state=running but state=pending because this container cannot start (wrong placement rule) [root@swarm1:~]# docker service ps mzcuervresdb ID NAME IMAGE NODE DESIRED STATE CURRENT STATE ERRORwbd3dz5c051t stack-traefik_traefik.1 traefik:v3.7 Running Pending about an hour ago "no suitable node (scheduling …"(...)If I look more deeply this task[root@swarm1:~]# docker inspect wbd3dz5c051tq8wf8hjf9jy0f(...) "Status": { "Timestamp": "2026-07-22T09:59:36.52320026Z", "State": "pending", "Message": "pending task scheduling", "Err": "no suitable node (scheduling constraints not satisfied on 2 nodes; 1 node not available for n

HelloI’ve set-up CMA on my central + poller + an agent.In centreon, I’m unable to select host template “ OS-Linux-Centreon-Monitoring-Agent[-custom] “ template. I can see them in host templates and edit the -custom one.They just don’t appear in the host template selection list

Hello.Is there a plugin that can be used to get the DNS zone expiration from SOA?I have tried with the DNS Service connector, using --mode=request --search-type='SOA' but it doesn’t show the complete SOA. With --verbose or --debug the result is the same, only the response time.Regards

Hi guys,I need Help to change data collection from poolers.I mean in my configuration all poolers should communicate with the main Centreon Engine 23.04.4 via VIP address. But for some poolers after a reboot of main Centreon server they are sending data directly to Centreon servers without passing through the VIP and until now I didn’t find how or where to force the pooler to communicate only with the VIP.Can you please help me in this case ?  

At present, Centreon is not yet widely recognized across Canada, particularly in regions such as Western and Northern Canada, including Winnipeg, Saskatoon, Edmonton, and Vancouver. In my opinion, to increase visibility and drive adoption of this platform, it would be beneficial to consider establishing a headquarters or regional offices in these markets.Currently, Centreon appears to have a primary presence in Toronto, while many Canadian IT organizations already rely on well-established U.S.-based platforms such as Datadog, Splunk, and other similar solutions.To strengthen its position in the Canadian market, Centreon will likely need to invest further in local presence, strategic partnerships, and marketing efforts.

captureThe url provided https://raw.githubusercontent.com/centreon/centreon-collect/refs/tags/25.10.15-latest/agent/installer/scripts_linux/install_cma.shdoes not exist 

HelloWhen using service template :OS-Linux-Cpu-Centreon-Monitoring-Agent -> Generic-Passive-CMA-Service-custom -> Generic-Passive-CMA-Service check command is set to :/usr/lib/centreon/plugins//centreon_linux_local.pl --plugin='os::linux::local::plugin' --mode='cpu'  --warning-core='' --critical-core='' --warning-average='' --critical-average='' --statefile-dir=''   but when --statefile-dir=’’, plugin tries to write in /, which results in :     UNKNOWN: Cannot write statefile '/cache_linux_local_me_cpu_a181a603769c1f98ad927e7367c7aa51'. Need write/exec permissions on directory. => the flag --statefile-dir=’’ should be removed from the default command / template

We are experiencing an issue after upgrading Centreon to the latest version. We recently upgraded our Centreon platform to the latest version 24.10.27 and have observed an issue affecting multiple monitored serviceSince the upgrade, several services that were previously working correctly are now reporting an UNKNOWN status.The plugin output reported for the affected services is: - UNKNOWN: No locks counter found with given filters- UNKNOWN: No locks waits counter found with given filtersWe would like to understand if:- There are any known issues after upgrading Centreon that could cause services to return UNKNOWN status.- Any plugin changes or compatibility issues introduced in recent Centreon versions could explain this behavior.- There are any known fixes or troubleshooting recommendations for similar cases. Any guidance or suggestions would be greatly appreciated.

Hi,I need to supervise a cluster Fortigate. But i need to know the state of all interfaces, interfaces in Master Fortigate and interfaces in Slave Fortigate. But i see lalways status of interfaces Master Fortigate and i dont see status of Slave Fortigate.Question : how can i see state of interfaces Slave Fortigate.Thank for your help.

Hello,I am experiencing an issue after upgrading my Centreon server to 25.10.13.EnvironmentCentreon Central: 25.10.13 Centreon Web: 25.10.13 Centreon Broker: 25.10.7 Centreon Engine: 25.10.7 MariaDB: 10.11.18 AlmaLinux 9ProblemAfter exporting the configuration from the Centreon Web interface, the broker configuration file is regenerated and the database password is written as an encrypted value:"db_password": "encrypt::..."When cbd starts, it immediately fails with:No usable encrypted password: Decryption finalization failed: error:1C800064:Provider routines::bad decryptThe broker continuously crashes and is restarted by the watchdog.Investigation performedMariaDB is running correctly. The centreon database account works correctly. Manual connection to centreon_storage succeeds:mysql -u centreon -p centreon_storage/etc/centreon-engine/engine-context.json exists. Gorgone, Engine and MariaDB are running correctly. Symfony secrets seem healthy:php /usr/share/centreon/bin/console secrets:l