-
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
Cannot set mount_points option in disk input #5980
Comments
Agree, have the same error. It has started to work after removing the line. |
We're having the same issue on all the servers that updated last night |
Sorry all, must have been introduced when we updated the toml library. Fix is easy though, we just need to add struct tags for these fields, will definitely make it in the next release. |
Any idea on when that might be ? Just to know if we can wait for it or if we should plan to remove the field everywhere in the meantime somehow |
Currently the plan is to release 1.11.1 on the 25th, depending on if other important bugs are found, in the meantime here are some builds of 1.11.0 including this patch: |
Alright those packages do work fine, that'll do in the meantime, thanks ! |
In case it helps others (perhaps using armhf architecture like me, so they can't use the temporary packages posted by Daniel above), you can 'hold back' the old version of Telegraf so it won't get upgraded by a
You can then update the rest of your system without upgrading telegraf. :) Once the new version (hopefully with working mount_points option) is released, you can use:
... after that, new telegraf releases will be considered when do a update & upgrade with aptitude, as usual. |
Relevant telegraf.conf:
System info:
Telegraf 1.11.0 (git: HEAD c9d8f7b)
Distributor ID: Ubuntu
Description: Ubuntu 16.04.6 LTS
(same results on 18.04LTS as well.)
Steps to reproduce:
Expected behavior:
the service running normally as it had before.
Actual behavior:
had to comment out mount_points on all ubuntu telegraf.conf configs and restart service.
Additional info:
on the bright side, now the grafana output looks like a modern art piece...
The text was updated successfully, but these errors were encountered: