Page History

Scroll Ignore

scroll-pdf	true
scroll-office	true
scroll-chm	true
scroll-docbook	true
scroll-eclipsehelp	true
scroll-epub	true
scroll-html	true

Panel

title	Sommaire

Table of Contents

maxLevel	4
style	none

Description

Les logs de la rétention Mongodb du Scheduler sont classés par catégorie afin de pouvoir différencier les types de log :

Gestion du module
Connexion à la base de données
Sauvegarde
Chargement
Suppression des lignes de retention obsolètes.

Gestion du module

Sur réception du signal SIGUSR1 le module va effectuer un dump de sa mémoire, pour tout autre signal, le module va s'éteindre

Code Block
[2021YYYY-04MM-21DD 10HH:24MM:49SS] INFO : [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] The worker with the pid XXXX received a signal XX

Arrêt critique

Quand le processus de pilotage s'arrête de façon inopinée

Code Block
[2021YYYY-04MM-21DD 10HH:24MM:49SS] ERROR : [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] I am a worker with pid: XXXX and my master process YYYY is dead, I exit.

Demande d'un dump de la mémoire

Le dump est fait

Python 2.6

Code Block
[2021YYYY-04MM-21DD 10HH:24MM:49SS] ERROR : [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] (support-only) MEMORY DUMP (to be sent to the support): xxxxxxxx xxxxxxxx xxxxxxxx

Python 2.7

Code Block
[2021YYYY-04MM-21DD 10HH:24MM:49SS] ERROR : [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] (support-only) Memory information dumped to file FFFFFFF (to be sent to the support)

Le dump a échoué

Python 2.6

Code Block
[2021YYYY-04MM-21DD 10HH:24MM:49SS] ERROR : [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] MEMORY DUMP: FAIL check if guppy lib is installed

Python 2.7

Code Block
[2021YYYY-04MM-21DD 10HH:24MM:49SS] ERROR : [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] (support-only) MEMORY DUMP: FAIL check if meliae lib is installed

Connexion à la base de données

Connexion normale

Code Block

[2021YYYY-04MM-21DD 10HH:24MM:49SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] We are creating mongo connection [uri=mongodb://192.168.1.120/?safe=false] [database=shinken] [ssh=True]
[2021YYYY-04MM-21DD 10HH:24MM:49SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] Connection created in : 0.200s

La connexion échoue

Code Block

[2021YYYY-04MM-21DD 10HH:24MM:49SS] WARNING: [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] Mongo connection failed 1/X time, we will try again
[2021YYYY-04MM-21DD 10HH:24MM:49SS] WARNING: [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] Mongo connection failed Y/X times, we will try again
[2021YYYY-04MM-21DD 10HH:24MM:49SS] ERROR  : [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] Mongo connection failed X/X times, we stop trying

La connexion a été perdue ou n'existe pas

Code Block
[2021YYYY-04MM-21DD 10HH:24MM:49SS] INFO : [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] We need to create a mongo connection

suivi des logs de la connexion normale

La connexion n'a pas pu être établie

Code Block
[2021YYYY-04MM-21DD 10HH:24MM:49SS] INFO : [ SCHEDULERNAME ] [ MongodbRetention ] [ SOUS-SECTION ] Could not create mongo connection

Erreurs pendant la suppression d'anciennes données ou lors de la sauvegarde

Si une erreur survient pendant une opération en base de données, les logs suivants vont apparaître :

Code Block

title	Exemple

[2019YYYY-07MM-10DD 16HH:19MM:10SS] WARNING: [SCHEDULERNAME] [ MongodbRetention ] [ SOUS-SECTION ] We have been disconnected of mongo. Will retry [1/3]
[2019YYYY-07MM-10DD 16HH:19MM:10SS] WARNING: [SCHEDULERNAME] [ MongodbRetention ] [ SOUS-SECTION ] We have been disconnected of mongo. Will retry [2/3]
[2019YYYY-07MM-10DD 16HH:19MM:10SS] WARNING: [SCHEDULERNAME] [ MongodbRetention ] [ SOUS-SECTION ] We have been disconnected of mongo. Will retry [3/3]
[2019YYYY-07MM-10DD 16HH:19MM:10SS] ERROR  : [SCHEDULERNAME] [ MongodbRetention ] [ SOUS-SECTION ] After 3 tries, we couldn't connect to mongo

Code Block

[2019YYYY-07MM-10DD 16HH:19MM:10SS] ERROR  : [SCHEDULERNAME] [ MongodbRetention ] [ SOUS-SECTION ] We have an error:[ERROR MESSAGE]
[2019YYYY-07MM-10DD 16HH:19MM:10SS] ERROR  : [SCHEDULERNAME] [ MongodbRetention ] [ SOUS-SECTION ] (stack du Traceback)
[2019YYYY-07MM-10DD 16HH:19MM:10SS] ERROR  : [SCHEDULERNAME] [ MongodbRetention ] [ SOUS-SECTION ] ...

Erreur de configuration du module

Si plusieurs url mongo sont précisées

Code Block

[2021YYYY-04MM-20DD 13HH:52MM:26SS] ERROR  : [ SCHEDULERNAME ] [ MODULES-MANAGER ] The instance MongodbRetention raised an error: Multiples urls were found in the module's configuration file. I disable it and set it to restart it later

Sauvegarde en rétention

Pour la sauvegarde de la rétention, trois types de logs existent:

Section	Description
SAVE GLOBAL	Correspond au processus global de la sauvegarde
SAVE WORKERS	Corresponds à un sous-processus de SAVE GLOBAL, qui s'occupe de la file d'attente des différents workers de la sauvegarde
SAVE WORKER X	C'est un sous-processus de SAVE WORKERS, correspondant à un worker numéroté X qui permet de sauvegarder une partie des informations du Scheduler en base. Le nombre de workers est paramétrable dans les paramètres du module. ( voir Rétention en base de donnée centralisée par royaume ( Module MongodbRetention ) )

SAVE GLOBAL

Les logs SAVE GLOBAL donnent des informations relatives au fonctionnement global du module ou de sa configuration.

Code Block

title	Exemple

[2019YYYY-07MM-10DD 14HH:34MM:39SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ SAVE GLOBAL ] Starting to save retention data. [XXX:hosts] [XXX:checks] (Database used = mongodb://HOST/?safe=false, use ssh = False)
[2019YYYY-07MM-10DD 14HH:34MM:39SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ SAVE GLOBAL ] SUCCESS Retention data was saved into mongodb. Total time X.XXs

Erreurs

Les erreurs lors de la sauvegarde de la rétention sont aussi enregistrées dans les logs sous cette forme:

Code Block

[2021YYYY-04MM-20DD 11HH:26MM:57SS] ERROR  : [ SCHEDULERNAME ] [ MODULES-MANAGER ] The instance MongodbRetention raised an error: ERROR MESSAGE. Total time XX.XXs. I disable it and set it to restart it later

Exemples

Code Block

language	bash

[2021YYYY-04MM-20DD 11HH:26MM:57SS] ERROR  : [ SCHEDULERNAME ] [ MODULES-MANAGER  ] The instance MongodbRetention raised an error: [ SAVE GLOBAL ] FAILED Retention data could not be saved in mongodb. Total time 22.20s. I disable it and set it to restart it later

Code Block

[2021YYYY-04MM-20DD 11HH:26MM:57SS] ERROR  : [ SCHEDULERNAME ] [ MODULES-MANAGER  ] The instance MongodbRetention raised an error: [ SAVE GLOBAL ] FAILED Retention data could not be saved in mongodb because mongo is unreachable. Total time 2.11s. I disable it and set it to restart it later

SAVE WORKERS

Les logs SAVE WORKERS donnent l'état de chaque worker de sa création à son succès/échec.

Code Block

title	Exemple

[2019YYYY-07MM-10DD 14HH:34MM:44SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ SAVE WORKERS ] Starting worker X with pid XXXXX. Try: X/X
[2019YYYY-07MM-10DD 14HH:34MM:54SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ SAVE WORKERS ] The worker X did SUCCESS (after X try)

La préparation des données à sauvegarder a été longue :

Code Block
[2019YYYY-07MM-10DD 14HH:34MM:44SS] WARNING: [ SCHEDULERNAME ] [ MongodbRetention ] [ PERF ] [ X.XXXs ] atomization duration

Des erreurs empêchent le bon déroulé de la sauvegarde :

Code Block
[2019YYYY-07MM-10DD 14HH:34MM:44SS] INFO : [ SCHEDULERNAME ] [ MongodbRetention ] [ SAVE WORKERS ] some workers did fail to exit or encountered an error. The retention save can be incomplete

Code Block
[2019YYYY-07MM-10DD 14HH:34MM:44SS] ERROR : [ SCHEDULERNAME ] [ MongodbRetention ] [ SAVE WORKERS ] Too many tries failed

Code Block
[2019YYYY-07MM-10DD 14HH:34MM:44SS] ERROR : [ SCHEDULERNAME ] [ MongodbRetention ] [ SAVE WORKERS ] Cannot start the XXXXX worker process as there is not enough memory

Code Block

[2019YYYY-07MM-10DD 14HH:34MM:44SS] ERROR  : [ SCHEDULERNAME ] [ MongodbRetention ] [ SAVE WORKERS ] Cannot start the worker X process: XX. Exiting the retention save, killing all currently launched workers

SAVE WORKER X

Les logs SAVE WORKER X donne pour le worker ayant l'identifiant X, les statistiques sur les sauvegardes qu'il a effectuées : le nombre d'éléments, résultat et temps d'exécution.

Code Block

title	Exemple

[2019YYYY-07MM-10DD 14HH:34MM:44SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ SAVE WORKER 0 ] Updating retention with elements: checks [ XXX ] -- hosts [ XX ] in mongodb
[2019YYYY-07MM-10DD 14HH:34MM:44SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ SAVE WORKER 0 ]  Retention data saved into mongodb in X.XXX seconds

Erreurs

Code Block
[2019YYYY-07MM-10DD 14HH:34MM:44SS] WARNING: [ SCHEDULERNAME ] [ MongodbRetention ] [ SAVE WORKER X ] The worker (pid:XXXX \| try:XX) did not exit on time (XX s). We are restarting it.

Code Block
[2021YYYY-04MM-20DD 12HH:06MM:15SS] ERROR : [ SCHEDULERNAME ] [ MongodbRetention ] [ SAVE WORKER X ] Failed connection with the following message : ERROR MESSAGE

Chargement de la rétention

Les logs fournissent des informations liées au chargement de la rétention, permettant de suivre son avancée et l'état sur la connexion à Mongo.

Code Block

[2019YYYY-07MM-10DD 16HH:19MM:10SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ LOAD RETENTION ] [ HOSTS / CLUSTERS ] [ X.XXXs ] We took X    hosts/clusters  from the retention [ in scheduler hosts/clusters : without retention=X    / total=1    ]
[2019YYYY-07MM-10DD 16HH:19MM:10SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ LOAD RETENTION ] [ HOSTS / CLUSTERS ] No host/cluster are needed for retention load (scheduler already have all X    hosts retention data).
[2019YYYY-07MM-10DD 16HH:19MM:10SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ LOAD RETENTION ] [ CHECKS           ] [ X.XXXs ] We took X    checks          from the retention [ in scheduler checks         : without retention=XX   / total=XX   ]
[2019YYYY-07MM-10DD 16HH:19MM:10SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ LOAD RETENTION ] [ CHECKS           ] No checks       are needed for retention load (scheduler already have all X    checks retention data).
[2019YYYY-07MM-10DD 16HH:19MM:10SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ LOAD RETENTION ] [ X.XXXs]  Total number of elements load from mongo database: X    ( scheduler have a total of XX   elements )
[2019YYYY-07MM-10DD 14HH:35MM:37SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ LOAD RETENTION ] [ X.XXXs ] SUCCESS Retention data loaded successfully.

Erreurs

Les erreurs lors du chargement de la rétention sont aussi enregistrées dans les logs sous cette forme:

Code Block
[2019YYYY-07MM-10DD 16HH:19MM:10SS] ERROR : [ SCHEDULERNAME ] [ MongodbRetention ] [ LOAD RETENTION ] FAILED Retention data could not be loaded from mongodb: ERROR MESSAGE DETAILS

Code Block
[2019YYYY-07MM-10DD 16HH:19MM:10SS] ERROR : [ SCHEDULERNAME ] [ MongodbRetention ] [ LOAD RETENTION ] error querying host entries: ERROR MESSAGE. Module exiting.

Code Block
[2019YYYY-07MM-10DD 16HH:19MM:10SS] ERROR : [ SCHEDULERNAME ] [ MongodbRetention ] [ LOAD RETENTION ] error querying checks entries: ERROR MESSAGE. Module exiting.

Suppression des anciennes rétentions

Les logs de suppression permettent de voir le nombre d'objets supprimés (triés par hôtes et checks) ainsi que la date à partir de laquelle la rétention est conservée.

Code Block

title	Exemple avec des objets à supprimer

[2019YYYY-07MM-10DD 15HH:54MM:53SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ DELETE OLD RETENTION   ] We will delete all retention data that were saved before the XXXX-XX-XX XX:XX UTC (X days)
[2019YYYY-07MM-10DD 15HH:54MM:53SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ DELETE OLD RETENTION   ]  - Deleting XXX hosts from old retention [XXXX by XXXX]
[2019YYYY-07MM-10DD 15HH:54MM:53SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ DELETE OLD RETENTION   ]  - XXX  - hosts deleted in X.XXXs
[2019YYYY-07MM-10DD 15HH:54MM:53SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ DELETE OLD RETENTION   ]  - Deleting XXX services from old retention [XXXX by XXXX]
[2019YYYY-07MM-10DD 15HH:54MM:53SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ DELETE OLD RETENTION   ]  - XXX  - services deleted in X.XXXs
[2019YYYY-07MM-10DD 15HH:54MM:53SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ DELETE OLD RETENTION   ] Total time for deleting XXXX entries = X.XXXs

Code Block

title	Exemple sans objets à supprimer

[2019YYYY-07MM-10DD 14HH:35MM:13SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ DELETE OLD RETENTION   ] We will delete all retention data that were saved before the XXXX-XX-XX XX:XX UTC (X days)
[2019YYYY-07MM-10DD 14HH:35MM:16SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ DELETE OLD RETENTION   ] There is no data to delete
[2019YYYY-07MM-10DD 14HH:35MM:16SS] INFO   : [ SCHEDULERNAME ] [ MongodbRetention ] [ DELETE OLD RETENTION   ] Total time for deleting 0 entries = X.XXXs

Page tree

Versions Compared

Old Version 22

New Version 23

Key

Description

Gestion du module

Arrêt critique

Demande d'un dump de la mémoire

Le dump est fait

Python 2.6

Python 2.7

Le dump a échoué

Python 2.6

Python 2.7

Connexion à la base de données

Connexion normale

La connexion échoue

La connexion a été perdue ou n'existe pas

La connexion n'a pas pu être établie

Erreurs pendant la suppression d'anciennes données ou lors de la sauvegarde

Erreur de configuration du module

Sauvegarde en rétention

SAVE GLOBAL

Erreurs

Exemples

SAVE WORKERS

SAVE WORKER X

Erreurs

Chargement de la rétention

Erreurs

Suppression des anciennes rétentions