Open mmachenry opened 3 days ago
@evilmumi let's continue in one issue rather than splitting up.
@mmachenry or @evilmumi can you please check if this behavior was introduced in a certain version? A first debugging session on slack revealed that the underlying MQTT library itself seems to cause the issue...
I have Auto Update configurated for my telegraf Container. So maybe it came in the last 2-3 releases. But at the moment not clear how to test it? Can i just use an old version?
Relevant telegraf.conf
Logs from Telegraf
System info
Telegraf-1.32.1 Ubuntu-20.04.3 LTS
Docker
version: "3" services: influxdb: image: influxdb:2.7.10 # influxdb:latest ports:
DOCKER_INFLUXDB_INIT_ADMIN_TOKEN=$KTS_TELEMETRY_INFLUXDB_TOKEN
grafana: image: grafana/grafana:11.2.0 # grafana/grafana:latest environment:
influxdb
mqtt_telegraf: image: telegraf:1.32.1 environment:
volumes: influxdb-storage: grafana-storage:
Steps to reproduce
Expected behavior
The telegraf instance should reconnect to the MQTT broker upon having network connectivity again and then begin producing data to insert into InfluxDB as normal.
Actual behavior
Upon reconnection, a bunch of cached data is dumped to InfluxDB and shortly there after, no new data is ingested. If telegraf is rebooted, it reconnects normally and produces data. A reboot to telegraf should not be required. It does not notice that it's broken so a manual effort is require to realize data is not being ingested to InfluxDB and a manual forced restart needs to be triggered.
Additional info
A more full version of the logs which did not fit here is located on gitst. https://gist.github.com/mmachenry/59139541bbb628abff0c648d37eb41fb