Unanswered questions

Hello everyone,I’m trying to monitor Proxmox VMs using Centreon with the Proxmox VE Rest API plugin. I’ve followed the official documentation as well as the steps described on these pages:Centreon Plugin Packs Documentation : https://docs.centreon.com/pp/integrations/plugin-packs/procedures/virtualization-proxmox-ve-restapi/Proxmox VE Rest API Plugin Procedure : https://docs.centreon.com/docs/monitoring/pluginpacks/#checking-the-monitoring-procedureI’ve configured the plugin with the correct credentials and macros, but I’m facing two issues:When I run the plugin manually or through Centreon, I get the following error:UNKNOWN: 401 authentication failureI also installed the Proxmox VE connector directly from Centreon and configured my host using the provided template. However, when I check the host availability, it shows 100% undetermined.I’m wondering if this could be related to:the realm (pam vs pve),SSL settings,or something else.Another point: the VM.monitoring command no longer exis

Hello,IF someone can help me!!I want to configure centreon to be able to open ticket on jira software but i have this errorversion: Centreon 25.10.10Open Ticket rule save - update failed : Error while executing the insert query : Error while executing the statement : SQLSTATE[42S22]: Column not found: 1054 Unknown column 'provider_name' in 'INSERT INTO' 

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?     

Hello,I have configured the Centreon Monitoring Agent (CMA) for my Windows server.However, when I try to create a host in Centreon and assign the host template OS-Windows-Centreon-Monitoring-Agent-custom, this template does not appear in the host creation form.The template is present and visible in Configuration > Hosts > Templates, but it is not available in the template selection list when creating or editing a host.I am using Centreon 24.10.26 and I do not have a commercial license installed.Has anyone encountered this issue before or knows why this template is not available for host assignment?Thank you for your help.

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

Hello,Is anyone else facing this kind of issue?A map in a custom view or a dashboard is randomly displayed as the map or the map homepage (the page listing all maps).If the page is refreshed, the map is correctly displayed but not all the time. Sometime we need to refresh the page two or three times in order to get the map displayed instead of the map list.It seems to occur only with chrome (148.0.7778.179) , not edge. I can’t test with firefox.the problem appears after updating to 24.10.23Thanks

in my environment i also use passive checks, some tests results submitted once a week or month.with one of the latest centreon version (in mycase Centreon 25.10.14) passive checks also gets down if host check fails and stays in this state until next passive test result.i’m using activated “Disable Service Checks When Host Down”with older centreon versions the passive checks weren’t changed if a hosts get down and you use this option (only the active ones).I’m not sure with what version this behavior changed, it think with 24.10 it worked like before

Hello, I am currently monitoring the IP SLA on a Cisco 9300.I am having trouble retrieving the jitter metric.However, this metric is clearly visible on the router side.Could you help me?sudo -u centreon-engine /usr/lib/centreon/plugins//centreon_cisco_standard_snmp.pl --plugin=network::cisco::standard::snmp::plugin --mode=ipsla --hostname=XXX --snmp-version='3'  --snmp-username=XXX  --authprotocol=SHA --authpassphrase=XXX --privprotocol=AES --privpassphrase=XXX--filter-tag='10006'  --warning-CompletionTime=50 --critical-CompletionTime=100  --use-new-perfdataOK: RTT '10006' Status : operation sense is 'ok', Completion Time : 7, Number Over Thresholds : 0 | '10006#completion_time'=7;0:50;0:100;0; '10006#number_over_thresholds'=0;;;; ----    Information on the router side ------------RTENTRAL#show ip sla statistics 10006IPSLAs Latest Operation StatisticsIPSLA operation id: 10006Type of operation: icmp-jitter        Latest RTT: 5 millisecondsLatest operation start time: 16:02:41 UTC Wed Ju

Hi,The Connector Manager is empty: Extensions are “all green”: Versions on the central server: $ dnf list | grep centreon-stable-24centreon-auto-discovery-server.noarch 24.10.14-1.el8 @rhel-8-centreon-stable-24_10-noarch-rpmscentreon-broker.x86_64 24.10.20-1.el8 @rhel-8-centreon-stable-24_10-x86_64-rpmscentreon-broker-cbd.x86_64 24.10.20-1.el8 @rhel-8-centreon-stable-24_10-x86_64-rpmscentreon-broker-cbmod.x86_64 24.10.20-1.el8 @rhel-8-centreon-stable-24_10-x86_64-rpmscentreon-broker-core.x86_64 24.10.20-1.el8 @rhel

Hier c’était https://download.centreon.com qui était injoignable et aujourd’hui… erreur 404…Y a-t-il un problème?

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 community,I followed the official installation guide https://docs.centreon.com/fr/docs/24.10/installation/installation-of-a-central-server/using-packages/ for Debian 12 (MariaDB for SGDB), adhering to it step by step.A post-installation note states: NOTICE: Not enabling PHP 8.2 FPM by default.NOTICE: To enable PHP 8.2 FPM in Apache2 do:NOTICE: a2enmod proxy_fcgi setenvifNOTICE: a2enconf php8.2-fpm Executed the following commands:systemctl daemon-reloada2enmod proxy_fcgi setenvif rewritea2enconf php8.2-fpma2ensite centreon Attempt to connect to the interface via http://<IP>/centreon; the Centreon configuration wizard does not appear: a blank page appears after ‘Centreon is loading...’. The aim is to perform a production migration from Alma 9 Centreon 24.10 to Debian 12 24.10 and upgrade to version 25.10. Thank you for your valuable contributions.

Background:This is not an App Registration. The requirement relates to an Enterprise Application configured with Single Sign-On (SSO) using SAML. This SAML SSO uses a signing certificate with an expiry date. We would like to track this expiry date in Centreon so that we can plan for renewal and avoid any service disruption.Questions:Is there a plugin pack, connector, or Centreon monitoring method that allows us to retrieve the expiry date of this certificate? If this is not supported natively, is there a method recommended by Centreon for monitoring it, for example via Microsoft Graph, an API, or a custom script? If specific development is required, could you confirm the most suitable approach for integrating this properly into Centreon?We would also be interested in any documentation, configuration examples, or best practices on this subject.Thank you in advance for your feedback.

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

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 

Hello,I want to fully automate the installation and registration of a poller on the central with Ansible.For RPMs or even transcribing the 'registerServerTopology.sh' script, this is no problem.I even managed to generate via a playbook the 'gorgon' configuration of the poller.On the other hand I cannot manage to transcribe the 'poller wizard' module of the interface. I noticed this was using an internal REST API, but I can't find any info on the subject.The objective of this playbook is to install, configure, and declare the poller without administrator intervention (among other things, restarting the gorgon service on the central and the poller)Thank you for your helpPhilippe

Why this appear in command line ? Is there any solution to show command line or  correct this ?  

Bonjour,Je suis confronté à un souci avec la sonde “Swap” pour les environment Windows (via SNMP), cette sonde renvoi la valeur cumulée de la mémoire + la swap.L’argument --real-swap permettait de me retourner la valeur équivalent à la swap, sauf que cela me retourne une valeur négative :Exemple :SERVEUR - 4w 1d - 13m 23s - CRITICAL: Swap Total: 4.00 GB Used: -425.00 MB (-10.38%) Free: 4.42 GB (110.38%)Merci de vos retours.

Last week (May 18, 2026) I was successfully able to upgrade from 24.04 to 24.10 on our backup/test system. All is well there. This weekend I attempted to upgrade our production system from 24.04 to 24.10. I used the exact same guide but it seems like many packages are missing from the 24.10 repos.Both systems are running Oracle Linux 8.10, fully up to date.  As you can see there are some packages available but no “centreon” files like centreon-web. I noticed that centreon-24.10-stable-noarch has no available packages at all, I’m guessing this is where the issue lies. This in on the server that I installed 24.10 on last week using the same guide. Can’t find the package in any of the dnf repos but as you can see I installed it last Monday, using the same repos from the guide.

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.*")'

Bonjour, L'API api.imp.centreon.com est joignable depuis mon serveur, mais l'enregistrement du token retourne 'Empty company token'. Pouvez-vous vérifier l'association du token LKEY.ad427603c5d9-45aa-ae34-4bf1a80247f1 avec ma société dans IMP ? Cordialement, 

Hello everyone, I’m new here but using Centreon for a few years.I recently installed the Infor ION Grid Monitoring Connector.Https protocol, port and credentials are OKCLI returns all the information I need with both application and node modes but the result can’t be displayed in the GUI, instead the UNKNOWN : 401 Unauthorized is displayedThe --debug option only adds a few strange lines such as :=> Recv header: HTTP/1.1 401 Unauthorized<td>HTTP ERROR: 401 Unauthorized<p>Problem accessing /grid/rest/nodes<pre id="message">Authentication failed - Invalid credentials</pre>  Centreon version is 25.10.9 (IT-100) and all plugins are up to date.Does anyone have any ideas on how to resolve this issue ?Best Regards Olivier

[root@shvit-centreo01 rpm]# dnf -y updateUpdating Subscription Management repositories.This system has release set to 9 and it receives updates only for this release.Red Hat Enterprise Linux 9 for x86_64 - AppStream (RPMs)                                               28 kB/s | 4.5 kB     00:00Red Hat Enterprise Linux 9 for x86_64 - BaseOS (RPMs)                                                  49 kB/s | 4.1 kB     00:00epel_9                                                                                                 46 kB/s | 2.3 kB     00:00Foreman_Client_el9                                                                                     58 kB/s | 1.5 kB     00:00puppet_el9                                                                                             38 kB/s | 1.5 kB     00:00Error: Problem 1: package mysql-libs-8.0.45-1.el9_7.x86_64 from @System requires mysql-common(x86-64) = 8.0.45-1.el9_7, but none of the providers can be installed  - package MariaDB-common-

Hello,I have a script to verify that the reboot tasks are running properly on certain virtual machines. For most of the VM fleet, this script works, but for three VMs, I’m seeing this message in Centreon. So I logged into those machines and saw that there was indeed a reboot task, and that it had even been executed the night before.Here is the script in question filter=enabled eq 1 and has_run eq 1 and title in ('Shutdown','shutdown','reboot','Reboot')warning=task_status = 'running' and most_recent_run_time < -60mcritical=task_status not in ('running') and exit_code > 0perf-config=*(ignored:true)show-all Does anyone know why the script does not recognize the reboot task? Best regards,

Bonjour,Nous utilisons Centreon 25.10 sur des serveurs RHEL 9.6 avec le Centreon Monitoring Agent, CMA, pour superviser des serveurs Windows en mode push.Nous utilisons le service template Windows CMA suivant :OS-Windows-Services-Auto-Centreon-Monitoring-Agent-customL’objectif de ce contrôle est de superviser les services Windows configurés en démarrage automatique et actuellement arrêtés.Le service est configuré avec les macros suivantes :STARTAUTO = trueFILTERNAME = .*FILTERDISPLAY = .*SERVICE_TYPE = serviceSTART_TYPE = autoCRITICALSTATE = stoppedMalgré la valeur SERVICE_TYPE=service, le contrôle remonte plusieurs Windows Kernel Drivers comme des services arrêtés.Exemple de retour d’alerte :CRITICAL: services: 4 stopped, 132 runningCRITICAL: dam is stoppedCRITICAL: sacdrv is stoppedCRITICAL: SentinelELAM is stoppedCRITICAL: WdBoot is stoppedSur le serveur Windows, ces objets ne sont pas des services Windows classiques visibles dans services.msc. Ce sont des Kernel Drivers.Vérificatio