-
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
systemd_units plugin reports errors for "not-found" units #7990
Labels
bug
unexpected problem or unintended behavior
Comments
squidpickles
added a commit
to squidpickles/telegraf
that referenced
this issue
Aug 16, 2020
3 tasks
Similar fix for the problem is in PR #8381. |
ssoroka
pushed a commit
that referenced
this issue
Nov 12, 2020
@squidpickles can you please test with current master after PR #7991 was merged!? |
ssoroka
pushed a commit
that referenced
this issue
Nov 13, 2020
@srebhan It works! Fantastic, thanks. |
arstercz
pushed a commit
to arstercz/telegraf
that referenced
this issue
Mar 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SystemD's output when listing units changed in v245. When units are in
not-found
state, they include a●
glyph in front. Previously, using--no-legend
disabled output of this glyph, but now it's included regardless of that setting.Related bug report: systemd/systemd#15077
It appears the fix was merged, but I have encountered several systems running v246 (latest release) that still have this problem.
Adding
--plain
to the command invocation works across the old (pre-v245) and newer versions.The text was updated successfully, but these errors were encountered: