-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[[inputs.ntpq]] works, but produce errors in the log "E! Error ntpq: parsing int: u" #2386
Comments
Same here. More output, if it helps debugging:
|
I think this error is related to vary number of columns provided by
Character that is splitting columns is a regular space, so adjusting My propose is a little bit "hacky":
What do you think? |
I wonder if ought to first enable
From
If we do this the parser will need to change quite a bit, but I think I would either try tokenizing with a regex or possibly iterating right to left. |
I do not have this option in my binary. Which version of
result:
|
I guess Regex replacement on the whole line sounds good, if you want to line up the whitespace for no reason other than because you are crazy like me you could do:
|
As a proof that I am, I've used |
- added test cases for SHM remotes; - slightly changed the fix for influxdata#2386 to improve and fix the parsing of SHM remotes.
Bug report
telegraf.service log shows the error every 10s: "E! Error ntpq: parsing int: u"
Relevant telegraf.conf:
System info:
Steps to reproduce:
Expected behavior:
no errors
Actual behavior:
errors
Additional info:
output of ntpq is:
The text was updated successfully, but these errors were encountered: