Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

telegraf stops sending data to influx #4731

Closed
ElFishi opened this issue Sep 21, 2018 · 5 comments · Fixed by #4846
Closed

telegraf stops sending data to influx #4731

ElFishi opened this issue Sep 21, 2018 · 5 comments · Fixed by #4846
Labels
area/mqtt bug unexpected problem or unintended behavior
Milestone

Comments

@ElFishi
Copy link

ElFishi commented Sep 21, 2018

I use telegraf to collect MQTT data and send the to Influx.
In irregular intervals telegraf stops sending data. The instance is still there but seems to do nothing. When telegraf is restarted everything works again as expected.

System info:

Telegraf v1.7.4 (git: release-1.7 578db7e)
Raspbian GNU/Linux 9 (stretch), Rpi 3
trace.txt

stack trace is attached.

@glinton
Copy link
Contributor

glinton commented Sep 21, 2018

How is your resource utilization at the time it stops reporting? I wonder if they get exhausted.

@danielnelson
Copy link
Contributor

Possible duplicate of #4580 and/or #4594.

@ElFishi
Copy link
Author

ElFishi commented Sep 21, 2018

I monitor CPU loads and memory. Maximum load around the time the data flow stopped was 0.25, available memory around 700MB.

Correct me if I'm wrong, but 4580 sounds as if there is no data flowing to Influx at all. My problem is that it all works and then stops at some random time.
4594 is concerned with MQTT disconnects. I, too, have disconnects in my journal but according to the log telegraf always reconnects successfully.
E.g. the lines before the SIGQUIT in my stack trace look like this:

Sep 18 17:30:25 Zorin telegraf[481]: 2018-09-18T15:30:25Z E! Error in plugin [inputs.mqtt_consumer]: E! MQTT Connection lost
Sep 18 17:30:25 Zorin telegraf[481]: error: pingresp not received, disconnecting
Sep 18 17:30:25 Zorin telegraf[481]: MQTT Client will try to reconnect
Sep 18 17:30:25 Zorin telegraf[481]: 2018-09-18T15:30:25Z I! MQTT Client Connected
Sep 18 20:52:35 Zorin telegraf[481]: 2018-09-18T18:52:35Z E! Error in plugin [inputs.mqtt_consumer]: E! MQTT Connection lost
Sep 18 20:52:35 Zorin telegraf[481]: error: pingresp not received, disconnecting
Sep 18 20:52:35 Zorin telegraf[481]: MQTT Client will try to reconnect
Sep 18 20:52:35 Zorin telegraf[481]: 2018-09-18T18:52:35Z I! MQTT Client Connected
Sep 18 21:12:45 Zorin telegraf[481]: 2018-09-18T19:12:45Z E! Error in plugin [inputs.mqtt_consumer]: E! MQTT Connection lost
Sep 18 21:12:45 Zorin telegraf[481]: error: pingresp not received, disconnecting
Sep 18 21:12:45 Zorin telegraf[481]: MQTT Client will try to reconnect
Sep 18 21:12:45 Zorin telegraf[481]: 2018-09-18T19:12:45Z I! MQTT Client Connected
Sep 20 22:41:54 Zorin telegraf[481]: SIGQUIT: quit

@danielnelson danielnelson added bug unexpected problem or unintended behavior area/mqtt labels Sep 22, 2018
@danielnelson
Copy link
Contributor

Can you test if this change helps: #4846 (comment)

@ElFishi
Copy link
Author

ElFishi commented Oct 14, 2018

installed it and its working. But since my problem is very intermittent I can't confirm it improved anything. Will check back if the problem occurs again.

@danielnelson danielnelson added this to the 1.8.2 milestone Oct 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/mqtt bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants