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

ping input on ipv6 hosts return -2 #2865

Closed
damm opened this issue May 30, 2017 · 4 comments
Closed

ping input on ipv6 hosts return -2 #2865

damm opened this issue May 30, 2017 · 4 comments

Comments

@damm
Copy link

damm commented May 30, 2017

Bug report

Relevant telegraf.conf:

[inputs.ping]]
urls = ["ipv4.google.com","ipv6.l.google.com"]

System info:

Gentoo Linux; using linux tarball/gz 1.3.0

Steps to reproduce:

  1. ...Install Telegraf
    2 ...On an ipv6 enabled host configure the ping plugin to ping ipv6 hosts

Expected behavior:

It to return an address and ping it and store the results.

Actual behavior:

It fails to return an address. Chonograf shows this host but returns no data.

Additional info:

2017-05-30_03:04:05.04508 2017-05-30T03:04:05Z E! Error in plugin [inputs.ping]: ping: unknown host ipv6.l.google.com, exit status 2
2017-05-30_03:04:05.04513 2017-05-30T03:04:05Z E! Error in plugin [inputs.ping]: Fatal error processing ping output
2017-05-30_03:04:10.05653 2017-05-30T03:04:10Z E! Error in plugin [inputs.ping]: ping: unknown host ipv6.l.google.com, exit status 2
2017-05-30_03:04:10.05656 2017-05-30T03:04:10Z E! Error in plugin [inputs.ping]: Fatal error processing ping output
2017-05-30_03:04:15.06391 2017-05-30T03:04:15Z E! Error in plugin [inputs.ping]: ping: unknown host ipv6.l.google.com, exit status 2
@rlex
Copy link

rlex commented May 30, 2017

pinging ipv6 on linux requires ping6 binary, which (it seems) not supported in telegraf ATM.

@danielnelson
Copy link
Contributor

Sometimes it requires ping6 but it depends on the system, we are tracking support for ipv6 on #2159 so I'm going to close this issue.

@damm
Copy link
Author

damm commented May 30, 2017

@rlex it worked previously? so what changed?

@danielnelson doesn't seem that helpful of a response there. As it worked previously and stopped working now; I assume something in telegraf changed.

ipv6 has been working natively for me for almost a year; I'll be quite honest my Gentoo is older than it should be and the ping6 binary hasn't been touched in that time. (Yeah I'm sure my coreutils is dated) but that shouldn't matter as it's returning -2 which kinda makes me think it's running the wrong binary

Lastly I have ping6; thanks for the other issue but I will comment this update is rather unsatisfying. It worked; it doesn't now; yeah very unsatisfying excuses.

@danielnelson
Copy link
Contributor

Can you add the output of running ping ipv6.l.google.com?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants