Infra Monitoring Platform

SymptomsWhen a host is linked to a host category, the update fails with the following error in the logs:  [ERROR] Rollback of 'PartialUpdateHost' transaction {"custom":{"trace":"#0 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHostValidation.php(258): Core\\Host\\Application\\Exception\\HostException::idsDoNotExist()\n#1 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHost.php(438): Core\\Host\\Application\\UseCase\\PartialUpdateHost\\PartialUpdateHostValidation->assertAreValidCategories()\n#2 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHost.php(183): Core\\Host\\Application\\UseCase\\PartialUpdateHost\\PartialUpdateHost->updateHostCategories()\n#3 /usr/share/centreon/src/Core/Host/Application/UseCase/PartialUpdateHost/PartialUpdateHost.php(152): Core\\Host\\Application\\UseCase\\PartialUpdateHost\\PartialUpdateHost->up

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=d

Hello,I’m facing an issue with discovery jobs stuck in Running state on my Centreon platform.Context Multiple discovery jobs configured per poller Providers used: VMware (ESXi & VM discovery, ~20 jobs with filters) AWX (2 jobs: pre-prod and prod) Pollers are sized according to Centreon recommendations Jobs are scheduled sequentially with intervals, running once per day IssueRecently, some discovery jobs are getting stuck in Running state indefinitely. On the central server, I get errors indicating that the job cannot be launched because it is already in Running state It is impossible to restart the job from the UI (even after waiting a long time and after restarting gorgoned service ) Checks already performed Reviewed gorg

Voici une version adaptée intégrant ce contexte : Bonjour à tous,Nous supervisons actuellement des conteneurs OpenVZ avec Centreon.Nous disposons d’un ancien plugin “fait maison” qui permet de contrôler l’état des conteneurs (notamment la partie démarrage), mais il commence à dater et nous souhaitons savoir s’il existe aujourd’hui une méthode plus standard / officielle pour superviser correctement cet aspect.Notre besoin est de : Détecter un échec de démarrage d’un conteneur Vérifier que le conteneur est réellement en état running Disposer d’un statut clair et fiable dans Centreon (OK / CRITICAL si le conteneur n’est pas démarré) Éviter de maintenir un script custom si une solution packagée existe Nous n’avons pas trouvé de plugin officiel Centreon Plugin Pack dédié à OpenVZ pour cette vérification spécifique.Existe-t-il : Un plugin

Bonjour,J’ai une question par rapport à l’Activité métiers (Business Activity). Récemment, on m’a demandé de créer des activités métiers pour mes serveurs, mes applications hébergées. Cependant, je l’ai créé que depuis la semaine dernière. Cependant, les applications et les serveurs existaient depuis pas mal d’année. Par contre, quand je génère un rapport pour mon activité métier, il n’affiche que les valeurs à partir de la création de l’activité métier pour mes serveurs et mes applications. Est-ce normal? Comment je peux faire pour que ce rapport prend toute l’historique de mes serveurs et de mes applications? Ou ce n’est pas du tout possible?Aussi, j’avais déjà quelques activités métiers en place depuis pas mal d’année. Et j’ai modifié les plages d’horaire de rapport de 24x7 en heures ouvrées de 8h à 20h et aussi supprimer quelques indicateurs non utiles à mes rapports. Est-ce que j’aurai une réécriture de mes historique d’activités métiers dans ce cas là, ou bien c’

Hello, just here to share to the community an issue that i encountered, the underlying issue, and how it can be resovled.This happened on a quite heavily loaded central server (poller included), and my end users reported receiving load of emails alerts regularly, but during bursts of a few minutes.After investigating the commands failing, there was nothing to correleate them, any service could fail, and all failed with the same output: “Execute command failed”. Something strange was at work here.After going more in the logs, especially centreon-engine logs, i find it. “Too many open files”. Here is the issue.At first i supposed there was permissions issues or something, but this is irrelevent as all can happend to any commands usually working fine. So i dig deeper on the internet, and here i find it, the Linux File Des

Following a recent update of the plugins on my Centreon servers, I am facing issues with the Fortinet plugin, specifically impacting the SD-WAN and VPN services. Could you please assist me in resolving this issue? Unknown option: include-vdomain at /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl line 4524.  Unknown option: include-vdom at /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl line 4524.

Hello everyone, I have update my centreon of the version 23 to 24.Since, i have this error "SSL certificate problem: unable to get local issuer certificate for" this error appears when I want to add a hostdo you know this problem? How to fix it?

Hello,I have a strange behaviour in my centreon (Centreon Engine 24.10.17).I´ve configured a passive check, set active checks enabled to no, passive checks enabled to yes, is volatile to no. Also check freshness to no: Now my Application sends an alert via centreon API and the service goes to warning state as expected.As soon as I acknowledge the service the active check command (which is a dummy command) gets executed and the service is in unknown state and therfore not acknowledged. Sticky acknoledge works but is unfortunately no option.So first question: Why is the check command executed on acknowledgement and second: how can I disable that?Thank

Hello,I am facing an issue on a fresh installation of Centreon 25.10 running on Red Hat Enterprise Linux 9.7.Context Centreon installation: fresh install / from scratch OS: RHEL 9.7 Connector in use: Windows NSClient05 RestAPI License: IT-100 Plugin Pack installed online from the web interface Goal: use Windows disk discovery Issue observedWhen I open the discovery rule:OS-Windows-NSClient05-Restapi-Disk-NameI get the following error in the Centreon web interface:Command execution issue: status code '127'(command: /usr/lib/centreon/plugins//centreon_windows_local.pl --plugin=os::windows::local::plugin --mode=list-storages --hostname=127.0.0.1 --disco-format)

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

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]  

Bonjour, dès que je veux modifier, créer , supprimer un objet j’ai cette erreur qui apparaît du jour au lendemain. Pouvez vous m’aidez svp ?

I set up an IDP using the pysaml2 python library and want to connect it to Centreon via SAML, but I can’t find the SP Centreon metadata. Where can I find it?

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

Hail,  

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? 

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]Howeve

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