Recently active topics

I cant find much about the CVE or the Vulnerability and I am unsure how to handle it. Out OpenVAS is reporting a RCE for centreon-web with a WontFix. Is it fixed? Will it be fixed? How to handle it? The Vulnerability is described in this PDF: https://www.synacktiv.com/sites/default/files/2021-07/Centreon_Multiple_vulnerabilities_0.pdfBut the named CVE cant be found andywhere. 

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

Hi,In the 24.10.22 release notes we can read:> [API] The API no longer returns "null" when trying to acces the /monitoring/servers endpoint (it will now returns the IP address of the pollers). What’s about the /monitoring/downtimes endpoint? Shouldn’t all the endpoints with the same erratic behaviour be fixed once? 

Hi,[root@centreonpollerorcentral sudoers.d]# grep User_Alias /etc/sudoers.d/*[Cc]entreon*/etc/sudoers.d/centreon:User_Alias      CENTREON=%centreon/etc/sudoers.d/centreon-gorgone:User_Alias      GORGONE=centreon-gorgone/etc/sudoers.d/centreon-plugins:User_Alias      CENTREON_COLLECT_USERS=centreon-engine,centreon-gorgone/etc/sudoers.d/sudoersCentreonLinuxPlugins:User_Alias      CENTREON_COLLECT_USERS=centreon-engine,centreon-gorgoneIt raises a warning from sudo, also, what’s this sudoers entry for? 

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

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.23

Hail,  

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 

We are testing upgrade from 23.10 to 24.10 using VM clone of production and we are seeing some issues.central-broker-master.log contains errors we have never seen before[2025-04-04T11:57:13.036+03:00] [sql] [error] PB actual end time 18446744073709551615 -> NULL[2025-04-04T11:57:13.036+03:00] [sql] [error] PB actual end time 18446744073709551615 -> NULL[2025-04-04T11:57:13.087+03:00] [sql] [error] PB actual end time 18446744073709551615 -> NULL[2025-04-04T11:57:13.087+03:00] [sql] [error] PB actual end time 18446744073709551615 -> NULLAnyone know what does PB stand for in this error, there is not much information to much of debugging with this very brief error message.Also for some reason Centreon Broker does not show any configured inputs or outputs, they are all simply gone after update. Anyone else seen this happen?

More detailed, more user-friendly, and more comprehensive.Based on valuable feedback from both our external and internal users, we deeply reworked the Centreon Monitoring Agent documentation. This new version split the original page in different pages, to provide a more readable and easier experience.We also fixed some errors and added details about certificate configuration & troubleshooting.Explore the updated version nowFeedbacks are more than welcome !

Hi everyone, I'm currently working with Centreon and the VMware 8 connector. I’ve successfully configured the ‘host-status' mode, but I’m running into a 401 Unauthorized error with other services. Has anyone encountered this specific issue with the new vSphere 8 integration? Any guidance on debugging the API authentication would be greatly appreciated.

Hi, we have a new DELL ME5012 Storage.is there a Centreon Plugin ? or other plugins / check what can i use for this Storage ?SNMP and so on