I installed rasdaemon on Debian 13 to try to get more information on an AER error, but received warnings from this code that ipmitool could not be located:
Feb 09 07:44:19 mirab4n2 rasdaemon[24303]: rasdaemon: Recording jm_payload0_event events
Feb 09 07:47:18 mirab4n2 rasdaemon[24303]: rasdaemon: aer_event store: 0x555ee69f35e8
Feb 09 07:47:18 mirab4n2 rasdaemon[24303]: rasdaemon: register inserted at db
Feb 09 07:47:18 mirab4n2 rasdaemon[26634]: sh: 1: ipmitool: not found
It wasn't found because I blacklist its installation, because if it's installed it (and tools like Prometheus that will use it) fail because none of my (desktop) systems have IPMI devices:
Feb 09 09:01:28 mirab4n2 rasdaemon[33670]: rasdaemon: aer_event store: 0x563424718f48
Feb 09 09:01:28 mirab4n2 rasdaemon[33670]: rasdaemon: register inserted at db
Feb 09 09:01:28 mirab4n2 rasdaemon[340722]: Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
Feb 09 09:01:28 mirab4n2 rasdaemon[33670]: Failed to execute ipmitool
What is the preferred solution to eliminating these diagnostics on systems where IPMI is not available? The flag use_ipmitool seems to be designed for a different problem.
I installed rasdaemon on Debian 13 to try to get more information on an AER error, but received warnings from this code that
ipmitoolcould not be located:It wasn't found because I blacklist its installation, because if it's installed it (and tools like Prometheus that will use it) fail because none of my (desktop) systems have IPMI devices:
What is the preferred solution to eliminating these diagnostics on systems where IPMI is not available? The flag
use_ipmitoolseems to be designed for a different problem.