Recently active topics

Hello,I’m facing an issue with a discovery rule in Centreon where the inclusion filter does not seem to work as expected.Context: I created a discovery rule to include only interfaces with names containing StackPort. My inclusion rule is configured as: Macro: $name$ Regexp: ^StackPort* Expected behavior:Only interfaces like StackPort1, StackPort2, etc. should be discovered.Actual behavior:When I run the discovery command manually, I can see interfaces such as:'StackPort2' [speed = 160000][status = up][id = 124][type = propVirtual]However, when I perform a manual scan from the Centreon UI, the inclusion filter does not seem to apply, and other interfaces are still discovered.Command used to list interfaces in CLI :sudo -u centreon-engine /usr/lib/centreon/plugins/centreon_cisco_standard_snmp.pl --plugin='network::cisco::standard::snmp::plugin' --mode=list-interfaces --hostname='10.0.0.8' --snmp-version='2c' --snmp-community='public' --disco-show<?xml version="1.0" encoding

Hello,Since my last upgrade to 24.10.12, some of my graph’s legends are broken.the metrics are correctly named, but the graphs legend shows “default” instead of metric name.for example : performance data and the graph is : graph legendin parameters > data, metrics name are OK for this service. Any idea how to fix this ?

Bonjour,Je supervise mes switchs cisco avec le connecteur Cisco Standard, cela fonctionne pour l’ensemble des services, sauf deux qui me retournent l’erreur indiquée en titre :spanning-tree AAA serviceLa vue configurée sur les switchs intègrent bien l’ensemble des OID (view ISO).Le spanning tree et le service AAA sont bien configurés sur les switchsJ’ai la même erreur pour tous les switchs (cisco 9200 et 9300)Savez-vous quelle pourrait être la cause de ce retour ?NB : j’utilise la dernière version de Centreon 24.10.21Merci d’avance

I would like a scenario to trigger another scenario as a countermeasure when it is critical, but I don't know how to do it.

Bonjour,Je souhaite avoir des précisions concernant les services de supervision embarqués dans Centreon Monitoring Agent (CMA), notamment sur leur personnalisation.Environnement OS : Red Hat Enterprise Linux 9.6 Plateforme : Centreon 25.10.9 Architecture : Centreon + Poller + DB sur le même serveur SELinux désactivé ContexteLors du déploiement de CMA sur les serveurs, nous constatons que les sondes embarquées sont bien présentes, mais nous ne trouvons pas de moyen clair pour personnaliser leur configuration.En particulier : l’entrée de registreComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Centreon\CentreonMonitoringAgent ne semble pas indiquer de fichier de configuration permettant de modifier ces sondes ; nous souhaiterions adapter certains comportements des contrôles natifs embarqués. BesoinNous aimerions notamment : Modifier la planification de la supervision des mises à jour Windows, ainsi que du contrôle Pending Reboot, pour ne lancer ces vérifications que toutes les 4 heures ; P

Hello,I’m encountering an issue with ACL behavior after service discovery in Centreon.Environment: OS: Red Hat Enterprise Linux 9.6 Centreon version: 25.10.9 (Central + Poller + MySQL 8) SELinux: disabled Context: I have configured user ACLs to restrict actions (menus, features, etc.). For resources, I did not create any specific restriction since all users should see all resources. Therefore, I am using the default “All Resources” ACL. Issue:When new services are discovered via service discovery: Non-admin users cannot see the newly created services. Even after logging out and logging back in, the services are still not visible. The only way to make them visible is to manually click the “Reload ACL” button. Additional observations: The log file /var/log/centreon/centAcl.log is always empty. Running the ACL reload command manually does not solve the issue: sudo -u apache /usr/bin/php -q /usr/share/centreon/cron/centAcl.php This command produces no output and does not make

Hello, just wondering because i’m unsure about what i read and heard about the new Log Management product.Is this only something that is available in Cloud or is product able to be installed within existing on premise installations of centreon Infrastructure Monitoring ?I heared that Centreon has some “special sauce” to improve reliability and scalability to ensure log ingestion but i didn’t read explicitely if there was support for on premise installation and i would like some precisions on that.Thank you

Hi, i installed a new VM - REDHAT 9 .. STEP 2 https://docs.centreon.com/docs/24.10/installation/installation-of-a-central-server/using-packages/#step-2-installation dnf install -y centreon-mariadb centreon whats wrong ?   Error: Transaction test error:  file /usr/share/mysql/charsets/Index.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64  file /usr/share/mysql/charsets/armscii8.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64  file /usr/share/mysql/charsets/ascii.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64  file /usr/share/mysql/charsets/cp1250.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64  file /usr/share/mysql/charsets/cp1251.xml from install of mysql-common-8.0.43-1.el9_6.x86_

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,[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? 

Hello, I’m currently migrating our centreon on-premise infrastructure to a new set of servers, and I’m trying to import my AD users again on the new platform. However I mirrored the configuration of the previous platform, but in trying to import users, nothing is found. The alias is resolved, the 636 port is not blocked, and certificate is integrated to the trust bundle. Do you know where I could find the logs of this part of the LDAP connector ? I know where to find the system’s LDAP attempts but not this one… Thanks ! Cheers 

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]  

I am usring /usr/lib64/nagios/plugins/check_centreon_nrpe3 to monitor windows CPU/Memory. And centreon can get CPU & Memeory status. But when I use the same command try to monitor disk space, system show error:Failed to execute check_drivesize: 2: ϵͳÕÒ²»µœÖž¶šµÄÎÄŒþ¡£. The full command is bellow./usr/lib64/nagios/plugins/check_centreon_nrpe3 -H 10.3.3.200 -p 5666 -2 -P 8192 -2 -P 8192 -n -c check_drivesize -a "drive=C:" Centreon version is 25.10. NSClient version is 0.11.24 The nsclient.ini files: [/modules]CheckEventLog = 1CheckNSCP = 1CheckSystem = 1CheckDisk = 1CheckService = 1WEBServer = 1NRPEServer = 1NSClientServer = 1CheckExternalScripts = 1CheckHelpers = 1[/settings/NRPE/server]verify mode = peer-certtls version = tlsv1.2+insecure = falsepassword = *allowed hosts = 10.3.3.10,127.0.0.1port=5666use ssl=falsepayload length=8192allow arguments = 1allow nasty_meta_chars = 1allow nasty characters = 1[/settings/default][/settings/external scripts]allow arguments = 1allow nasty_met

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 

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? 

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,