ipmi works or not?

Help! (Home for newbies)
1

i installed munin via epel reposity but it gives error on reading ipmi:

2011/04/20-14:45:01 CONNECT TCP Peer: “127.0.0.1:35871” Local: “127.0.0.1:4949”
2011/04/20-14:45:03 [14595] Error output from ipmi_fans:
2011/04/20-14:45:03 [14595] Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
2011/04/20-14:45:03 [14595] Get Device ID command failed
2011/04/20-14:45:03 [14595] Unable to open SDR for reading
2011/04/20-14:45:03 [14595] Error output from ipmi_fans:
2011/04/20-14:45:03 [14595] Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
2011/04/20-14:45:03 [14595] Get Device ID command failed
2011/04/20-14:45:03 [14595] Unable to open SDR for reading
2011/04/20-14:45:03 [14595] Error output from ipmi_temp:
2011/04/20-14:45:03 [14595] Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
2011/04/20-14:45:03 [14595] Get Device ID command failed
2011/04/20-14:45:03 [14595] Unable to open SDR for reading
2011/04/20-14:45:03 [14595] Error output from ipmi_temp:
2011/04/20-14:45:03 [14595] Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
2011/04/20-14:45:03 [14595] Get Device ID command failed
2011/04/20-14:45:03 [14595] Unable to open SDR for reading
2011/04/20-14:45:06 [14595] Error output from yum:
2011/04/20-14:45:06 [14595] Can’t open /var/lib/munin/plugin-state/yum.state for reading: No such file or directory
2011/04/20-14:45:06 [14595] Please read ‘munindoc yum’ to understand why if the file does not exist.
2011/04/20-14:45:06 [14595] Service ‘yum’ exited with status 2/0.

i checked ipmi in webmin:
Started now? Unknown
Executing /etc/rc.d/init.d/ipmi status …

ipmi_msghandler module loaded.
ipmi_si module loaded.
ipmi_devintf module loaded.
/dev/ipmi0 exists.

so how can i know its working or not? or what can problem in there?

2

I’ve never used IPMI before, but after a little Googling, it looks like that error could mean you’re looking at a configuration issue or a hardware issue.

It’s not always enough to just enable the daemon, sometimes there’s configuration to do to go along with that.

In this case, I unfortunately don’t know what that configuration is though :slight_smile:

-Eric