Infra Monitoring Platform

Bonjour,En suivant la procédure d’upgrade 25.10 > 26.10, il est évoqué pour les pollers, de récupérer la clé de déchiffrement en fin de documentation.Mes pollers sont “direct related” au Central.Lorsque je lance la commande avec les creds “admin”, j’ai une erreur “Authentication failed” alors que ces derniers sont fonctionnels en mode web. (et le firewalling poller > central est bien open sur TCP/443)Soit je n’utilise pas les bons “creds admin”, soit il y a une subtilité que je n’ai pas comprise / option non cochée dans le user “admin” ?Je suppose que c’est une nouvelle feature de sécurité liée à la 26.10 (chiffrement des échanges Poller <> Central ?) car je n’ai jamais fais cette action depuis que je m’occupe des upgrades de notre instance (version 21.04) Quelqu’un saurait-il me guider ? Par avance, merci !

Hi,All is in the title.

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

Hello,I'm experiencing an issue with Centreon 25.10.18 where Centreon Broker fails to start after exporting/reloading the configuration._Environment:_Oracle Linux 8centreon-web-25.10.18-1.el8centreon-central-25.10.18-1.el8centreon-broker-25.10.14-1.el8centreon-broker-cbd-25.10.14-1.el8centreon-engine-25.10.14-1.el8centreon-engine-daemon-25.10.14-1.el8centreon-gorgone-25.10.10-1.el8The database is running on AWS RDS._Problem:_After exporting/reloading the poller configuration, the db_password in:/etc/centreon-broker/central-broker.jsonis generated as an encrypted value:"db_password": "encrypt::..."When cbd is restarted, central-broker-master immediately exits with:[config] [error] No usable encrypted password: Decryption finalization failed: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt[core] [error] Error during cbd exit: No usable encrypted password: Decryption finalization failed: error:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decryptThe w

Hello Centreon Community, We’re running some tests on Gitlab, and we want to trigger alarms on Centreon once the tests fails. We didn’t find a plugin that can connect Centreon with Gitlab.Is it possible to create alarms in Centreon through API calls ? Is there another alternative to do so without API calls ?We’re using Centreon 2.8.23  

Hello,My two database nodes are now slaves after an unsuccessful attempt to switch from slave to master.I am looking for a way to switch my primary node back to MASTER status. Currently, it is the active one operating in the HA setup. Previous command # pcs resource move ms_mysql    Error: to move promotable clone resources you must use the promotable clone id (ms_mysql-clone)    Error: Errors have occurred, therefore pcs is unable to continue # pcs resource move ms_mysql-clone    Warning: Creating location constraint 'cli-ban-ms_mysql-clone-on-BDD_SECONDARY_NODE' with a score of -INFINITY for resource ms_mysql-clone on BDD_SECONDARY_NODE.            This will prevent ms_mysql-clone from running on BDD_SECONDARY_NODE until the constraint is removed            This will be the case even if BDD_SECONDARY_NODE is the last node in the cluster Result:[root@BDD_SECONDARY_NODE]# /usr/share/centreon-ha/bin/mysql-check-status.shConnection SLAVE Status 'BDD_PRIMARY_NODE' [OK]Connection SLAVE Sta

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

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,I am contacting you to ask whether you have any procedures or recommendations to mitigate the PHP2Shell vulnerability associated with CVE-2026-109618 and CVE-2026-109619.Our Centreon instance is running version 24.10.14 on AlmaLinux 9.Thank you in advance for your assistance. I look forward to hearing from you.Best regards,

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

Box ScoreIt appears to be protected in direction of say that Brewers lefthander Kyle Harrison will not be upon the postseason , who recorded the to start with 5 outs of today recreation versus the Pirates functioning in the vicinity of specifically a firstinning double, then gave up a few hits, 2 walks, and strike 2 batters with 2 outs within the moment, allowing for 5 operates 4 attained through the period he entered his August 31 start off towards the Cubs with a 2.79 Generation about 103 13 innings this year, nevertheless he previously sits with a 4.25 Generation higher than 112 13 innings, allowing for 24 operates 21 attained above his previous 9 innings throughout 4 appearances. The pace is however there, nonetheless the condition is not Custom Jersey, and it all however a certainty with a lot less than 2 months until eventually the postseason that Harrison will not be upon the roster this the negative favourable information?Milwaukee bullpen mainly preferred him up toward attain

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

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