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

[inputs.exec]: metric parse error: expected field at offset 110: #4063

Closed
timcooijmans opened this issue Apr 23, 2018 · 2 comments · Fixed by #4065
Closed

[inputs.exec]: metric parse error: expected field at offset 110: #4063

timcooijmans opened this issue Apr 23, 2018 · 2 comments · Fixed by #4065
Labels
bug unexpected problem or unintended behavior regression something that used to work, but is now broken
Milestone

Comments

@timcooijmans
Copy link

Hi,

My previously working input.exec script suddenly doesn't work anymore since the update to Telegraf 1.6.0.

I'm getting the following error:
Error in plugin [inputs.exec]: metric parse error: expected field at offset 110: "energy,meter=main imported_1=23786.317,exported_1=469.162,imported_2=23870.795,exported_2=1060.053,l1_import=00.254,l1_export=00.000,l2_import=00.201,l2_export=00.000,l3_import=00.693,l3_export=00.000\n"

Config:

[[inputs.exec]]
        commands = ["python /etc/telegraf/readmeter.py"]
        timeout = "20s"
        data_format = "influx"

Any idea what's going wrong?

@albundy83
Copy link
Contributor

It could be caused by this commit: 8e51568
You should check if your python command return a correct exit code...

@danielnelson
Copy link
Contributor

We rewrote the line protocol parser in 1.6, I expect this is just a bug in the new parser. Looks like it is caused by the double leading zero on floats: 00.693, if you can change these to 0.693 it should pass in 1.60, but I'll fix it proper for 1.6.1.

@danielnelson danielnelson added this to the 1.6.1 milestone Apr 23, 2018
@danielnelson danielnelson added bug unexpected problem or unintended behavior regression something that used to work, but is now broken labels Apr 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug unexpected problem or unintended behavior regression something that used to work, but is now broken
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants