Gestion/Utilisation d'influxdb

Exemple de log :

ts=2024-05-30T14:37:52.243598Z lvl=info msg="index opened with 8 partitions" log_id=0pUUolUW000 service=storage-engine index=tsi
ts=2024-05-30T14:37:52.253707Z lvl=info msg="loading changes (start)" log_id=0pUUolUW000 service=storage-engine engine=tsm1 op_name="field indices" op_event=start
ts=2024-05-30T14:37:52.253803Z lvl=info msg="loading changes (end)" log_id=0pUUolUW000 service=storage-engine engine=tsm1 op_name="field indices" op_event=end op_elapsed=0.099ms
ts=2024-05-30T14:37:52.255302Z lvl=info msg="Opened file" log_id=0pUUolUW000 service=storage-engine engine=tsm1 service=filestore path=/var/lib/influxdb2/engine/data/0d18ea589f79e054/autogen/1922/000000001-000000001.tsm id=0 duration=1.114ms
ts=2024-05-30T14:37:52.255469Z lvl=info msg="Opened shard" log_id=0pUUolUW000 service=storage-engine service=store op_name=tsdb_open index_version=tsi1 path=/var/lib/influxdb2/engine/data/0d18ea589f79e054/autogen/1922 duration=37.991ms

Les commandes influx à l'intérieur du container retournent :

 Error: failed to find bucket "telegraf": Get "http://monitor-influxdb:8086/api/v2/buckets?name=telegraf&org=cbna": dial tcp 172.29.0.3:8086: connect: connection refused

Solution : forcé la suppression du dossier contenant les data d'influxdb2. ATTENTION : perte de données ! Commande : rm -fr /var/lib/influxdb2/engine/data/. Cela ne nous pose pas de problème car nous ne souhaitons pas les garder !