Recently active topics

DescriptionHello,We are facing a critical issue after upgrading Centreon from 25.10.2 to 25.10.6 on a production platform.Context Centreon license: IT-100 Centreon version: 25.10.6 (upgrade from 25.10.2) Architecture: 1 × Centreon Central – Oracle Linux 9.7 1 × Centreon Poller – Oracle Linux 9.7 Use case: Oracle Database supervision (standard Centreon Oracle plugins) Issue observedSince upgrading to 25.10.6, the supervision is completely broken.All service macros are generated with the prefix raw::, for example: raw::$_SERVICEOUTPUT$ raw::$_HOSTADDRESS$ raw::$_SERVICESTATE$ This raw:: prefix is not interpreted by centreon-engine, which causes: Invalid command lines Plugins failing to execute Services stuck in CRITICAL / UNKNOWN Global supervision failure (including basic checks like Ping) What we verified / tried The issue appeared immediately after the upgrade to 25.10.6 The same configuration was working correctly in 25.10.2 Rollback of centreon-engine on the

Bonjour, J’ai remarqué que la découverte des Datastores étaient faites sur le Vcenter et non sur les ESX.Le problème que je rencontre est que depuis le Vcenter tous les datastores sont visibles or depuis les ESX ce n’est pas le cas. Je me retrouve donc avec des services sur mes ESX essayant de voir des datastores auxquels ils n’ont pas accès. Avez vous une solution qui permettrait de valider que l’ESX voit bien ces datastores avant de les ajouter dans les services ? Merci 

Bonjour,Existe t-il des checks, plugins spécifiques aux serveurs windows rds/tse ?

La fonction d’export CSV est-elle / sera implémentée dans les resources table comme dans la page ressources status ?

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 ?

Hi,I have centreon 24.10.18 when trying to visualise graphs from the web interface I have a “fail to fetch” error on chromium and “network error when attempting to fetch ressource” in firefox. This is for all hosts data I have tried.I tried the following without success:I looked in centreon logs under /var/log/centreon /var/log/centreon-gorgone /var/log/centreon-broker /var/log/centreon-engineI could not find anything that seems related to the error in the web browser but I might have overllooked something as there is a large amount of logs.I restarted centreon services: cbd centengine centreontrapd gorgoned . Then rebooted the server I cleared browser cache I tried with another userAny suggestions on what I should try next? 

Goodmorning,I’ve a router with 2 IP address, example IP 10.0.0.1 LAN and 1.1.1.2 WAN.I add the host with FQDN that reply to LAN IP address 10.0.0.1.I try to duplicate ping service, called ping_1, and in EXTRAOPTIONS I put -H 1.1.1.2 to ping the WAN IP via another internet connection, to monitor if WAN link is working.After exporting the configuration I’ve this result: Performance data10.0.0.1rta=10.750ms;200.000;400.000;0; 10.0.0.1pl=0%;20;50;0;100 10.0.0.1rtmax=11.008ms;;;; 10.0.0.1rtmin=10.607ms;;;; 1.1.1.2rta=1.027ms;200.000;400.000;0; 1.1.1.2pl=0%;20;50;0;100 1.1.1.2rtmax=1.063ms;;;; 1.1.1.2rtmin=1.010ms;;;;Command/usr/lib64/nagios/plugins/check_icmp-H 10.0.0.1-n 5-w 200,20%-c 400,50%-H 10.0.0.11.1.1.2 It’s possible to overwrite the IP address from 10.0.0.1 to 1.1.1.2?If it’s not possible, in this scenario, if WAN link goes down - IP 1.1.1.2 not reachable via ping but LAN IP 10.0.0.1 continue to ping, I receive any alarm form Centreon?Thanks

Bonjour,Je vous explique ma situation pour imager la problématique.Aujourd’hui j’aimerai que lorsqu’un host est down par exemple, qu’il envoie en journée une notification à un client (ActeurA) mais qu’à partir disons de 19h à 7h qu’il envoie au groupe astreinte (ActeurB).La problématique étant qu’aujourd’hui on peux ne pas créer de règles pour faire cela ou du moins pas à ma connaissance.

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/#/data-loading/.d3.min.js:1 Error: <rect> attribute x: Expected length, "NaN".d3.m

Hi,Since the NSClient++ project has been on a long break (from april 2018 and november 2023) we have never included its releases in our continuous integration processes. But since then, the project show an impressive level of activity.As we have been very busy doig a lot of other things, we have fallen far behind on this updating the base version of NSClient++ used for our builds.We’re currently trying to bridge this gap and given the wide number of changes, we may expect some regressions.Please feel welcome to use this pre-release and give us feedback here!Here are the known issues (I’ll update them as they’ll be found):The old authentication (using --legacy-password and no login) does not seem to work anymore. Since it’s not a good practice, you’re invited to switch to  --username and --password. NB: the apps::nsclient::restapi::plugin needs this commit to handle this authentication process. 

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 ?

Hello,Here is the context: I want to have a single dashboard view for each customer.To do this, I created a viewerclientA user with a very restricted viewerclientA ACL that only allows read access to dashboards. In addition, I shared the relevant dashboard with my admin account for the viewerclientA account, so it can access it.However, they cannot see certain widgets on the dashboard. Could you please advise me on the changes that need to be made to the ACL in order to gain access?The error message can be seen in the photo.​​​​​​  

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]  

Hello, After upgrading from 24.04 to 25.10 we encounter an issue with centreon-engine reload. When the reload is performed the variable/macro $CENTREONPLUGINS$ becomes empty and the checks that depend on it fail. Restarting the service solves the issue. In the centreon-engine logfile I found the following:[2026-02-04T08:44:34.117+01:00] [process] [info] [683729] Reloading...[2026-02-04T08:44:34.117+01:00] [process] [info] [683729] Starting to reload configuration.[2026-02-04T08:44:34.249+01:00] [config] [error] [683729] Cannot apply new configuration: Could not modify a host escalation: host escalation objects can only be added or removed, this is likely a software bug that you should report to Centreon Engine developers[2026-02-04T08:44:34.340+01:00] [config] [error] [683729] Error: Could not modify a service escalation: service escalation objects can only be added or removed, this is likely a software bug that you should report to Centreon Engine developers I checked also the logfile

Bonjour, est-il possible via une version open source de centreon en 25.10. D’avoir via les tableaux de bords un graphique présentant la disponibilité des hôtes appartenant à un host group sur 1 mois par exemple ?

Bonjour,Nous avons actuellement une sonde du genre /usr/lib/centreon/plugins/centreon_protocol_http.pl --plugin=apps::protocols::http::plugin --mode=expected-content --hostname=hostname --proto='https' --port='443' --urlpath='/api/' --expected-string='"status":"pass"' --ssl-opt="SSL_verify_mode => SSL_VERIFY_NONE"OK: HTTP test(s) | 'size'=29B;;;0; 'time'=0.538s;;;0; /usr/lib/centreon/plugins/centreon_protocol_http.pl \  --plugin=apps::protocols::http::plugin \  --mode=json-content \  --hostname=url \  --proto='https' --port='443' \  --urlpath='/api' \  --header='Accept: application/json' \  --lookup='$.status' \  --threshold-value='values' \  --warning-string='' \  --critical-string='^(?!pass$)' \  --ssl-opt='SSL_verify_mode => SSL_VERIFY_NONE'OK: 1 element(s) found | 'count'=1;;;0; 'time'=0.599s;;;0;curl -s  https://url<?xml version="1.0" encoding="UTF-8"?><root><status>pass</status><version>0.10</version></root>  Nous aimerions utiliser

hi,I want use assume role with plugin AWS. ex: Amazon RDSmy poller is a aws instance with right role.my poller need proxy for get cloudwatch metrics.aws say than to set environnement variable 'no_proxy' in my case.what is the best practice to set environement variable ‘no_proxy’ for all check of poller. 

Hello Watchers!At Centreon, we are constantly exploring new ways to make your IT operations smoother and more insightful. Today, we’re looking into a strategic topic and we’d love to get your thoughts: The convergence of Monitoring and Cybersecurity.Since Centreon already monitors your assets (OS, web servers, databases, networking gear) and often knows their versions, we are considering an integration that crosses this data with real-time CVE (Common Vulnerabilities and Exposures) databases.The vision: A new security bulletin is released, and Centreon immediately flags the 15 servers in your infrastructure that are at risk—without you needing to trigger a manual scan.Before we dive deeper into this feature, we want to hear about your current reality:How do you manage vulnerabilities today? Do you use dedicated tools or is it a more manual process? Are you satisfied with your current setup? Do you find these solutions too complex, too disconnected from your daily ops, or do they perfec

I am experiencing an error after upgrading Centreon from version 24.04 to version 25.10 OS (Debian 12).Could you please assist me? An Error Occurred: Internal Server ErrorOops! An Error OccurredThe server returned a "500 Internal Server Error".Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.

Hello All.I just upgraded the server to 24.10.18 from 24.10.13. No error at all.After that I was no longer able to log on the console either with my LDAP account or the local admin : I always get a authentication failed error.I restarted the server, same issue.In the login.log file there was a message : Authentication failed for 'admin' : invalid credentialsAfter a few trials I got : [INFO] User is blocked: maximum number of authentication attempts was reached {"contact_alias":"admin"}I checked the password in the mariadb databse and found i was not correct compared to the hash version. Ok I changed it using that post : Then the connexion asked me to change the password and now I can log in using the admin password. Ouf !!But the ldap connexion is still failing. In the centreon-web log file I read that :[2026-01-30T09:50:20+0100] [ERROR] An error occurred during authentication {"custom":{"trace":"TypeError: ldap_get_entries(): Argument #2 ($result) must be of type LDAP\\Result, bool gi