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 no more working when changing ip adress in DNS name of InfluxDB server #3648

Closed
sebastien-prudhomme opened this issue Jan 9, 2018 · 3 comments · Fixed by #3924
Closed
Assignees
Labels
area/influxdb bug unexpected problem or unintended behavior
Milestone

Comments

@sebastien-prudhomme
Copy link

sebastien-prudhomme commented Jan 9, 2018

System info:

Telegraf v1.5.0 on CentOS 6.5

Steps to reproduce:

  1. Start Telegraf pointing to influxdb.example.com (a CNAME to gateway.example.com, which is a reverse-proxy to the real InfluxDB server)
  2. Telegraf works fine.
  3. Change IP address of gateway.example.com
  4. Wait several minutes/hours so that DNS servers and DNS cache take into account the new IP address
  5. curl -v http://influxdb.example.com/ping works fine on the server with the Telegraf agent
  6. Telegraf does not work anymore except if you restart it

Seems that IP address of the InfluxDB server is cached by the Telegraf agent (or perhaps a Go library) and never updated.

@danielnelson danielnelson added this to the 1.6.0 milestone Jan 9, 2018
@danielnelson danielnelson added the bug unexpected problem or unintended behavior label Jan 9, 2018
@jesus-sayar
Copy link

I have the same problem!

@andor-pierdelacabeza
Copy link

Obey the TTL!

@danielnelson
Copy link
Contributor

@andor-pierdelacabeza lol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/influxdb bug unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants