Issues related to applications and software problems
-
lightman47
- Posts: 1521
- Joined: 2014/05/21 20:16:00
- Location: Central New York, USA
Post
by lightman47 » 2018/10/05 16:35:43
My boot.log in the last day or two started containing failed messages about ipmievd. When I do systemctl status for it, this is in the result
Code: Select all
ipmievd[884]: Could not open device at /dev/ipmi0 or /dev/ipmi/0 or /dev/ipmidev/0: No such file or directory
I don't understand why suddenly this is showing up. I've disabled the network service as NM is running. Upon seeing this message, I re-enabled network and restarted, but to no avail - the ipmievd.service still failed..
Thanks
Last edited by
lightman47 on 2018/10/06 21:33:44, edited 1 time in total.
-
avij
- Retired Moderator
- Posts: 3046
- Joined: 2010/12/01 19:25:52
- Location: Helsinki, Finland
-
Contact:
Post
by avij » 2018/10/05 17:24:31
Do you actually want to run that daemon, or are you only concerned about that new error message?
Is this a physical server or a virtual machine?
Which kernel are you running? See uname -a.
-
TrevorH
- Site Admin
- Posts: 33202
- Joined: 2009/09/24 10:40:56
- Location: Brighton, UK
Post
by TrevorH » 2018/10/05 17:33:57
Does your machine actually have an IPMI? Mostly that's something only on server class machines, things like iDRAC/iLO etc are IPMI devices, used for remote controlling the machine.
-
lightman47
- Posts: 1521
- Joined: 2014/05/21 20:16:00
- Location: Central New York, USA
Post
by lightman47 » 2018/10/05 17:42:49
Sorry - real machine (hp elite laptop), weekly updated CentOS 7 (1804). I've no idea what that service is, nor how it got installed. I'd assumed it came in on CentOS but now I wonder.
Code: Select all
$ uname -a
Linux {machine.domain} 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
EDIT:
I did a
sudo yum provides ipmiev\* and got no matches found.
-
avij
- Retired Moderator
- Posts: 3046
- Joined: 2010/12/01 19:25:52
- Location: Helsinki, Finland
-
Contact:
Post
by avij » 2018/10/05 17:56:03
You probably don't want/need that service at all. Try systemctl disable ipmievd.service.
-
lightman47
- Posts: 1521
- Joined: 2014/05/21 20:16:00
- Location: Central New York, USA
Post
by lightman47 » 2018/10/05 18:13:43
OK, I've disabled it. Thank you.
I've ssh'ed into my other machines and queried the status on the service ... it doesn't exist. This includes the similarly (but not exactly) configured laptop I am using currently.
Do you "off the top" know what installs it? If not, I have updated lists of installed packages on each machine and could just go through finding what's installed on that machine that is on no other.
-
avij
- Retired Moderator
- Posts: 3046
- Joined: 2010/12/01 19:25:52
- Location: Helsinki, Finland
-
Contact:
Post
by avij » 2018/10/05 18:25:44
ipmievd comes from ipmitool (
yum provides '*/ipmievd'). As for why you have that ipmitool installed, perhaps you have one of these packages installed:
Code: Select all
# repoquery --whatrequires --recursive ipmitool --disablerepo=epel
bmc-snmp-proxy-0:1.8.18-7.el7.noarch
exchange-bmc-os-info-0:1.8.18-7.el7.noarch
fence-agents-all-0:4.0.11-86.el7.x86_64
fence-agents-all-0:4.0.11-86.el7_5.2.x86_64
fence-agents-all-0:4.0.11-86.el7_5.3.x86_64
fence-agents-ipmilan-0:4.0.11-86.el7.x86_64
fence-agents-ipmilan-0:4.0.11-86.el7_5.2.x86_64
fence-agents-ipmilan-0:4.0.11-86.el7_5.3.x86_64
-
avij
- Retired Moderator
- Posts: 3046
- Joined: 2010/12/01 19:25:52
- Location: Helsinki, Finland
-
Contact:
Post
by avij » 2018/10/05 18:30:03
Another way to see why you have that ipmitool installed is to try to remove it with yum remove ipmitool. The packages that require ipmitool are listed in the "Removing for dependencies" section.
-
lightman47
- Posts: 1521
- Joined: 2014/05/21 20:16:00
- Location: Central New York, USA
Post
by lightman47 » 2018/10/05 18:46:21
Code: Select all
Dependencies Resolved
================================================================================
Package Arch Version Repository Size
================================================================================
Removing:
ipmitool x86_64 1.8.18-7.el7 @base 1.5 M
Removing for dependencies:
inxi noarch 3.0.21-1.el7 @epel 900 k
python2-xapps-overrides x86_64 1.0.4-12.el7 @epel 1.2 k
python34-xapps-overrides x86_64 1.0.4-12.el7 @epel 1.2 k
xapps x86_64 1.0.4-12.el7 @epel 5.7 M
xplayer x86_64 1.6.0-4.el7 @epel 7.2 M
Transaction Summary
================================================================================
Remove 1 Package (+5 Dependent packages)
-
avij
- Retired Moderator
- Posts: 3046
- Joined: 2010/12/01 19:25:52
- Location: Helsinki, Finland
-
Contact:
Post
by avij » 2018/10/05 18:57:49
Looks like inxi is the package that pulls in ipmitool (and others packages pull in inxi and other deps) (
repoquery --requires inxi).
Code: Select all
# yum info inxi
...
Name : inxi
Repo : epel/x86_64
Summary : A full featured system information script
URL : http://smxi.org/docs/inxi.htm
Description : Inxi offers a wide range of built-in options, as well as a good number of extra
: features which require having the script recommends installed on the system.
Maybe it's just me, but I think the description is fairly pointless. The summary "A full featured system information script" is a better description.