Centreon Broker, c'est quoi et ne peux pas ouvrir la base de donnée

Bonjour,
Suite a des fichiers qui grossissais sur mon Debian, j’ai été voir quel fichier/dossier prenais de la place. Et je suis tombé sur les fichier log central-broker.log qui fait 3,5 Go et un central-broker.log.old qui en fait 9,5Go
Du coup, j’essaye de voir ce qu’il ce passe et il y a cette suite de log qui ce répète:

Centreon Broker 18.10.0 log file opened
[1589882870] config: module applier: loading directory ‹ /usr/lib/centreon-broker/modules ›
[1589882870] info: dumper: module for Centreon Broker 18.10.0
[1589882870] info: NEB: module for Centreon Broker 18.10.0
[1589882870] info: stats: module for Centreon Broker 18.10.0
[1589882870] info: BAM: module for Centreon Broker 18.10.0
[1589882870] info: storage: module for Centreon Broker 18.10.0
[1589882870] info: correlation: module for Centreon Broker 18.10.0
[1589882870] info: notification: module for Centreon Broker 18.10.0
[1589882870] info: TCP: module for Centreon Broker 18.10.0
[1589882870] info: TLS: module for Centreon Broker 18.10.0
[1589882870] info: TLS: loading GNU TLS version 3.6.7
[1589882870] info: graphite: module for Centreon Broker 18.10.0
[1589882870] info: influxdb: module for Centreon Broker 18.10.0
[1589882870] info: lua: module for Centreon Broker 18.10.0
[1589882870] info: RRD: module for Centreon Broker 18.10.0
[1589882870] info: RRD: using rrdtool 1.7.1
[1589882870] info: SQL: module for Centreon Broker 18.10.0
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-input ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-input › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-input ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-input › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-extcommands-engine-poller-module-1 ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-extcommands-engine-poller-module-1 › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-extcommands-engine-poller-module-1 ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-extcommands-engine-poller-module-1 › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-cfg-broker-poller-module-1 ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-cfg-broker-poller-module-1 › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-cfg-broker-poller-module-1 ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-cfg-broker-poller-module-1 › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.cache.central-broker-cfg-broker-poller-module-1 ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.cache.central-broker-cfg-broker-poller-module-1 › reached, NOT erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-cfg-engine-poller-module-1 ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-cfg-engine-poller-module-1 › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-cfg-engine-poller-module-1 ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-cfg-engine-poller-module-1 › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.cache.central-broker-cfg-engine-poller-module-1 ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.cache.central-broker-cfg-engine-poller-module-1 › reached, NOT erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-db-cfg-reader ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-db-cfg-reader › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-db-cfg-reader ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-db-cfg-reader › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-nodeevents ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-nodeevents › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-nodeevents ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-nodeevents › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.cache.central-broker-nodeevents ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.cache.central-broker-nodeevents › reached, NOT erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-sql ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-sql › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-sql ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-sql › reached, erasing file
[1589882870] error: could not open database: Can’t connect to local MySQL server through socket ‹ /var/run/mysqld/mysqld.sock › (2) QMYSQL: Unable to connect
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-storage ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-storage › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-storage ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-storage › reached, erasing file
[1589882870] error: could not open database: Can’t connect to local MySQL server through socket ‹ /var/run/mysqld/mysqld.sock › (2) QMYSQL: Unable to connect
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-rrd ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-rrd › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-rrd ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-rrd › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-correlation ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-correlation › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-correlation ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-correlation › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.cache.central-broker-correlation ›
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-bam-monitoring ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.memory.central-broker-bam-monitoring › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-bam-monitoring ›
[1589882870] info: file: end of file ‹ /var/lib/centreon-broker//central-broker.queue.central-broker-bam-monitoring › reached, erasing file
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.cache.central-broker-bam-monitoring ›
[1589882870] error: BAM: command_file parameter not set
[1589882870] error: parsing error on ‹ /etc/centreon-broker/correlation.xml ›: No such file or directory
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.cache.central-broker-nodeevents.new ›
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.cache.central-broker-cfg-broker-poller-module-1.new ›
[1589882870] info: file: opening new file ‹ /var/lib/centreon-broker//central-broker.cache.central-broker-cfg-engine-poller-module-1.new ›
Centreon Broker 18.10.0 log file closed

Mais je ne sais pas ce que c’est « Centreon Broker » et « central-broker » et je n’arrive pas a trouver d’informations que je comprend en ligne.
Et puis, si quelqu’un a une idée de comment je peux régler le problème de connection a la base de donnée?
Cordiallement

Bonjour,

et bien Centreon est un outil de supervision, un peu comme Nagios par exemple.
Tu dois avoir les paquets centreon-broker et centreon-engin installés, tu peux vérifier avec dpkg -l | grep centreon
Si tu n’utilise pas ce service tu peux désinstaller les paquets centreon. Mais ce serait bien de savoir pourquoi ils sont là.

Pour la base de données, les infos du log centreon-broker ne sont pas suffisantes, tu as un serveur mysql / mariadb installé sur cette machine ? Quelle est sa version ? Est-ce que mysql -u root te permet de te connecter sur mysql ?

Un lancement de

aptitude  search   centreon

et de

apt-cache policy centreon-broker

devrait vous permettre de savoir si ce logiciel est installé et s’il sort bien des dépôts Debian.

En ce qui concerne les journaux qui atteignent une taille disproportionnée, il est vrai que le paquet centreon-broker n’a pas été empaqueté en tenant compte de cette problématique puisqu’il ne recommande pas le paquet logrotate.

Les paquets centreon* ne se sont pas installés tout seul . Demandez à l’administrateur :smile: pourquoi ils sont présents.

Cordialement,
Regards,
Mit freundlichen Grüßen,
مع تحياتي الخالصة


F. Petitjean
Ingénieur civil du Génie Maritime.

« On ne perd pas son temps en aiguisant ses outils. »
Proverbe français

« Moi, lorsque je n’ai rien à dire, je veux qu’on le sache. » (R. Devos)

Ils sont effectivement installé, ça doit être moi qui les ai installé, mais je ne sais plus pour quel raison malheureusement

Non, je ne peux pas me connecter à mysql de cette manière. J’ai déjà utilisé sqlite et mariaDB sur ma machine, donc j’ai encore mariaDB normalement

Hum, c’est moi l’administrateur :innocent: c’est mon PC personnel. J’ai bien conscience que je ne le gère pas au mieux, mais j’essaye de faire de mon mieux. D’ailleurs, je vais voir comment avoir une gestion des fichiers log un peut correct et essayer de les vérifier régulièrement

C’est un autre sujet que centreon qui mériterait peut-être un sujet à part, mais du coup on va déjà s’assurer que tu as effectivement un serveur mariaDB démarré. C’est quoi le message d’erreur quand tu tentes un mysql -u root ?
Sinon tu peux regarder avec systemctl status mariadb pour voir ce que ça dit.

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Unit mariadb.service could not be found.

C’est assez étrange, il me semble que j’avais réussis a utiliser mariaDB dans le passé

Mais tout cela est-il encore installé ?
Peut-être que tu as le paquet mysql de la communauté mysql ? Pour lister les paquets installés qui contiennent mariadb ou sql dans leur nom: dpkg -l | egrep -i "mariadb|sql"

Tu peux regarder aussi si tu as encore des fichiers de configuration dans le répertoire /etc/mysql, ou même si tu as encore des bases de données dans /var/lib/mysql ?