Infra Monitoring Platform

Hello,When a host goes down, all its services go to the UNKNOWN state to prevent unnecessary checks and notification spam. I believe this behavior is caused by the engine setting “Disable Service Checks When Host Down” being enabled.While this setting addresses one issue, in my case it creates another.I have many services that do not need to be checked frequently. Some are being checked once a day, while others are passive services that may not receive updates for weeks.All these services go to the UNKNOWN state when their host go down and remain in that state even after the host comes back up.They will stay UNKNOWN until the next scheduled check or passive update is received which, as mentioned, could take weeks.To work around this, I have to manually force check all affected services, sometimes involving thousands of services at once. Since the GUI limits bulk forced checks to 100 services at a time, I ended up writing an API script to handle this…This behavior does not occur when th

ANAHEIM, CA JULY 17: Los Angeles Angels pitcher Reid Detmers 48 pitching in the course of an MLB baseball video game towards the Detroit Tigers performed upon July 17, 2026 at Angel Stadium in just Anaheim, CA. Picture through John CordesIcon Sportswire through Getty Pictures Icon Sportswire as a result of Getty ImagesI definitely preferred the Guardians in direction of concentration Reid Detmers this offseason asking yourself he was upon the verge of a breakout which occurred! Season in direction of revisit the self can look at our larger sized exchange deadline piece below as we focus on a broader pool of Designs the Guardians may possibly just take. Towards create my place crystal clear, I assume the Guardians in the direction of crank out lesser moves, including investing Bo Naylor and having a castoffundervalued reliever. However Daniel Schneemann Jersey, in just the consideration of looking into long run greater moves, we are executing a sequence seeking at some of these larger s

I am encountering persistent authentication issues while trying to access the REST API of a Dell ME4012 storage system. Despite providing valid credentials and testing multiple configurations, the REST API consistently returns an Authentication Unsuccessful error.Steps to ReproduceAttempt to log in to the Dell ME4012 REST API using curl:curl -k -X POST https://192.168.1.3/api/login \ -H "Content-Type: application/json" \ -d '{"username": "Admin", "password": "Password"}'Observe the following response:<RESPONSE VERSION="L100"> <OBJECT basetype="status" name="status" oid="1"> <PROPERTY name="response" type="string" display-name="Response">Invalid sessionkey</PROPERTY> </OBJECT></RESPONSE>Attempted the same with both controllers (192.168.1.3 and 192.168.1.4), but the same error occurs.Repeated the test with:HTTP Basic AuthenticationBoth curl and the centreon_dell_me4_restapi.pl pluginNo changes in the outcome.Expected BehaviorAuthentication shoul

Windows CMA Plugin - does it exist a service to check network lan state and traffic like SNMP?

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,we need to upgrade an existing Centreon poller from Centreon 23.10 to Centreon 24.04 in order to align it with our Central server, which is currently running Centreon 24.04.The poller is running Debian 11 (Bullseye).The repository previously used for Centreon 24.04 was:https://packages.centreon.com/apt-standard-24.04-stable/However, the Bullseye distribution is no longer available.The Bookworm distribution is still reachable:https://packages.centreon.com/apt-standard-24.04-stable/dists/bookworm/but its package indexes are currently empty.For example, the current InRelease reports:main/binary-amd64/Packages: 0 bytesmain/binary-all/Packages: 0 bytesAs a result, APT cannot retrieve any Centreon 24.04 standard packages.We have another working Centreon 24.04 server running Debian 12, which was upgraded while these packages were still available.It currently has, among others:centreon-engine   24.04.19-1+deb12u1centreon-broker   24.04.19-1+deb12u1centreon-gorgone  24.04.14-1+deb12u1cent

Hello,Since at least mid-September 2026, every download from packages.centreon.com (the .repo file, repodata and RPMs) is answered with a 302 redirect to centreon-delivery-pulp-packages-prod.s3.amazonaws.com (eu-west-1) with a pre-signed URL. Our servers are only allowed to reach *.centreon.com on the firewall, so the install/upgrade fails: # dnf config-manager --add-repo https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repoAdding repo from: https://packages.centreon.com/rpm-standard/25.10/el8/centreon-25.10.repoCurl error (35): SSL connect error for https://centreon-delivery-pulp-packages-prod.s3.amazonaws.com/artifact/a2/97161e...?response-content-disposition=attachment%3Bfilename%3Dcentreon-25.10.repo&X-Amz-...[redacted][OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to centreon-delivery-pulp-packages-prod.s3.amazonaws.com:443 ]Error: Configuration of repo failed Environment: AlmaLinux 8.10, Centreon 24.04 → upgrading to 25.10 on Oracle Linux 9, hosted o

Hello,Currently, when I open a ticket via open-tickets using dashboard or centreon_notification_centreon_opentickets_api.pl , only the host receives the ACK, even though the default acknowledgement configuration is set to acknowledge services attached to the host.Ideally, the open-tickets ACK should respect the default acknowledgement configuration for hosts, or this parameter should be configurable within the provider.

Hello Seems to be that the rpm repo is down. This worked just fine last week. 2026-09-21 17:42:30+00:00 - INFO - Centreon official repositories installation...Adding repo from: https://packages.centreon.com/artifactory/rpm-standard/24.10/el9/centreon-24.10.repoStatus code: 404 for https://packages.centreon.com/artifactory/rpm-standard/24.10/el9/centreon-24.10.repo (IP: 10.200.100.19)Error: Configuration of repo failed2026-09-21 17:42:31+00:00 - ERROR - Could not install Centreon repositoryAnyone watching who could take a look ? RgdsEndre

Hello,We are experiencing an issue with the Dell iDRAC SNMP plugin when monitoring the processor component on a Dell server using iDRAC10.We are using: Centreon Plugin: centreon_dell_idrac.pl Plugin version: 20260800 (ffe6bb7) Mode: hardware Component: processor SNMP version: 2c The check returns:UNKNOWN: Processor 'CPU.Socket.0' state is 'unknown'However, with --verbose --debug, we get:Checking processorsprocessor 'CPU.Socket.0' status is 'ok' [instance: 1.1] [state: unknown]The SNMP values returned by the iDRAC are:.1.3.6.1.4.1.674.10892.5.4.1100.30.1.4.1.1 = 0.1.3.6.1.4.1.674.10892.5.4.1100.30.1.5.1.1 = 3.1.3.6.1.4.1.674.10892.5.4.1100.30.1.26.1.1 = CPU.Socket.0According to the Centreon plugin source, OID .30.1.4 is processorDeviceStateSettings and is mapped using DellStateSettings, while .30.1.5 is processorDeviceStatus.The current Centreon mapping for processorDeviceStateSettings appears to be:1 => unknown2 => enabled4 => notReady6 => enabledAndNotReadyThere is

Hello,On 24.10.xx, when you create a new Recurrent Downtime with an account not full admin. The list of services is empty. Even with the ACL “All resources” assigned. When checking with naviagtor dev tools. We can see an 403 error when list the services. No issues with other resources types.  

Bonjour,Je souhaite monitorer un partage CIFS via le plugin centreon_plugins.pl --plugin apps::protocols::cifs::plugin --mode connectionJ’utilise la commande suivante :/usr/lib/centreon/centreon-plugins/src/centreon_plugins.pl --plugin apps::protocols::cifs::plugin --mode connection --hostname=mon_serveur --cifs-username=’mon_utilisateur’ --cifs-password=’mon_mot_de_passe’  --directory='mon_partage'La commande en putty fonctionne très bien avec l’utilisateur centreon-engine mais dès que je l’implémente dans Centreon j’ai le message permission denied.J’ai réalisé le test de copier la commande depuis Centreon vers la console et la commande fonctionne bien.Merci pour vos suggestions.

Hello,I can’t add a new host in Centreon 24.10.30 :Iam logged in admin. I have this error : You are not authorized to access this resource [2026-09-08T16:16:56.077895+02:00] app.DEBUG: Checking if route matches updates endpoint [] {"token":null,"uid":""}[2026-09-08T16:16:56.082005+02:00] request.INFO: Matched route "FindCurrentUserParameters". {"route":"FindCurrentUserParameters","route_parameters":{"_route":"FindCurrentUserParameters","_controller":"Core\\User\\Infrastructure\\API\\FindCurrentUserParameters\\FindCurrentUserParametersController","version":"latest","base_uri":"centreon/"},"request_uri":"https://toto.local/centreon/api/latest/configuration/users/current/parameters","method":"GET"} {"token":null,"uid":""}[2026-09-08T16:16:56.085213+02:00] security.DEBUG: Checking for authenticator support. {"firewall_name":"api","authenticators":3} {"token":null,"uid":""}[2026-09-08T16:16:56.085239+02:00] security.DEBUG: Checking support on authenticator. {"firewall_name":"api","authentic

Since the latest update to 24.10.29, the new prod.deprecations.log is growing constantly on every api request, containing messages like[2026-08-31T09:05:45.595490+02:00] deprecation.INFO: User Deprecated: Since symfony/validator 6.4: Method "Symfony\Component\Validator\ValidatorBuilder::setDoctrineAnnotationReader()" is deprecated without replacement. [2026-08-31T09:05:45.609523+02:00] deprecation.INFO: User Deprecated: Since symfony/framework-bundle 6.4: The "annotations.cached_reader" service is deprecated without replacement.[2026-08-31T09:05:45.609736+02:00] deprecation.INFO: User Deprecated: Since symfony/framework-bundle 6.4: The "annotations.reader" service is deprecated without replacement. [2026-08-31T09:05:45.609874+02:00] deprecation.INFO: User Deprecated: Since symfony/framework-bundle 6.4: The "annotations.cache_adapter" service is deprecated without replacement.[2026-08-31T09:05:45.610093+02:00] deprecation.INFO: User Deprecated: Since symfony/validator 6.4: Method "Symfo

Bonjour,Je ne parviens plus à afficher plusieurs ligne dans le ‘Status Information’ de me services.Avant j’envoyais depuis un script perl :print “Resultat a afficher:<br> informations à afficher\n”; Ca affichait bien sur 2 lignes (Grace au <br>):Resultat a afficher:informations à afficher Or maintenant ca affiche :   Resultat a afficher:<br> informations à afficher Le saut de ligne HTML <br> ne semble plus marcher …. et j’ai ressayé plusieurs variantes: \r ou \n .. mais rien à faire…Une idée ?

Hello, one of my clients has reported that they are having trouble accessing their Centreon platform in production following an automatic version update on their server.How can this feature be disabled in Centreon?Thank you for your help

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

Bonjour,Pour un CMA en version 24.10.17, on ne peut pas effectuer une découverte des services via l’interface Configuration/Services/Scan. Lorsque nous renseignons le nom de la VM le champ de recherche du type de service disparait...Savez-vous pourquoi et surtout, je cherche à monitorer les services (comme c’est actuellement fait avec SNMP).Merci d’avance !

Bonjour Je me pose des questions quand à l’utilisation des récurent down time.Jusque là je n’utilisait que des périodes temporelles.Mais d’après mes constatation si la période est appliquée à un hôte (par exemple jours ouvrés seulement), et que les services de l’hôte sont sur du 24x7 alors si un service est KO le week end, j’aurais quand même une notification. Je souhaite donc remplacé ça par un downtime (au niveau de l’hôte ou du groupe d’hôte).  Mais que ce passe-t-il si mon service tombe KO pendant le downtime et reste KO même lors des premier contrôle en dehors du downtime ? vais-je recevoir mes notifications (en dehors du downtime biensûr) ? Merci d’avance pour vos éclairages Contexte : Centreon 24.10

Hello,Centreon version : 24.10.29I only have a single, standalone central server, nothing else. Actions on the web interface are not being applied like acknowledging an altert, planning downtime or forcing a check control. I noticed that exporting the configuration does not trigger write in gorgoned.log nor centengine.logI also noticed that gorgone service is running fine, but is not listening on port 8085 for API calls from the web interface. IS this normal behavior ?Also, centreon-web.log last write timestamp is 22 July (2 weeks ago) which means the actions I am launching from the web UI are not being detected somehow. I checked write permissions in centreon directories. They seem fine :/etc/centreon # ls -l /etc/centreon-engine/total 304-rw-rw-r-- 1 www-data centreon-engine 4005 24 juil. 18:18 centengine.cfg-rw-rw-r-- 1 www-data centreon-engine 17509 24 juil. 18:18 commands.cfgdrwxrwxr-x 2 www-data centreon-engine 4096 6 nov. 2024 conf.d-rw-rw-r-- 1 www-data centreon-engine