Closed growly closed 2 months ago
This is caused by a patch that Debian applies, see #153 for all the details if you care :slightly_smiling_face:
I think the workaround would currently be to start the exporter with --freeipmi.path=/usr/bin
and use just sudo
in the config file. The fact that the prefix gets added to an absolute path seems a bit silly indeed, I'll take a look at that.
In the next release, your totally correct approach of setting the collector_cmd
to /usr/bin/sudo
should also work.
tysm 🙏
Not sure why this is happening, whether it's to do with how the user is set up (PATH) or whether it's part of this codebase, but in trying to force
sudo
collection on Debian 12.0 it seems as if ipmi_exporter tries to force/usr/sbin/
as a prefix for the command.Here's my ipmi_local.yml:
With this I get the following error deep in syslog:
Failed to collect SEL data" target=[local] error="error running /usr/sbin/sudo: fork/exec /usr/sbin/sudo: no such file or directory:
Fair enough, my sudo lives in /usr/bin and there's no link from /usr/sbin.
So I tried making it an absolute path:
But then I get this!
The fix is to add a symlink from /usr/sbin/sudo to /usr/bin/sudo, but that's not gonna work out of the box. Seems like this is surprising behaviour for specifying a an absolute command.
Don't have a moment to find the culprit in the codebase so sorry I can't do more of my own homework. Thought I'd report the issue anyway.