回覆: [phosphor-host-ipmid] Question about IPMI SDR
Chris Chen (TPI)
Chris.Chen3 at flex.com
Mon Nov 8 22:37:43 AEDT 2021
Hi all,
I think I figured out the error message is due to the phosphor-health-monitor package. The phosphor-health-monitor doesn't have the interface of org.freedesktop.DBus.ObjectManager and with the GetManagedObjects method call, so the getSensorMap() in the intel-ipmi-oem would be failed.
=====
root at hudsonbay-obmc:~# busctl introspect xyz.openbmc_project.HealthMon /
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
org.freedesktop.DBus.Introspectable interface - - -
.Introspect method - s -
org.freedesktop.DBus.Peer interface - - -
.GetMachineId method - s -
.Ping method - - -
org.freedesktop.DBus.Properties interface - - -
.Get method ss v -
.GetAll method s a{sv} -
.Set method ssv - -
.PropertiesChanged signal sa{sv}as - -
=====
As I know, the phosphor-health-monitor is a part of the base phosphor package. But there are some questions in my mind still and would like to get help here.
1.
is it only for monitoring CPU and memory sensor values? it looks like there is no explanation of it is in the phosphor-health-monitor repo.
2.
can I remove it? If yes, will I miss any features?
Thanks
Regards,
Chris Chen
________________________________
寄件者: openbmc <openbmc-bounces+chris.chen3=flex.com at lists.ozlabs.org> 代表 Chris Chen (TPI) <Chris.Chen3 at flex.com>
寄件日期: 2021年11月8日 下午 12:01
收件者: openbmc at lists.ozlabs.org <openbmc at lists.ozlabs.org>
主旨: [phosphor-host-ipmid] Question about IPMI SDR
Hi all,
We have added 3 temp sensors by using entity-manager, and looks like we can list them with temp value reading successfully as below.
=====
root at hudsonbay-obmc:~# ipmitool sdr elist
BMC | 00h | ok | 7.1 | 27 degrees C
DIMM P0 ABCD P1 | 01h | ok | 7.1 | 35 degrees C
DIMM P1 EFGH | 02h | ucr | 7.1 | 40 degrees C
Get SDR 0003 command failed: Invalid data field in request
Get SDR 0003 command failed: Invalid data field in request
Get SDR 0003 command failed: Invalid data field in request
Get SDR 0003 command failed: Invalid data field in request
Get SDR 0003 command failed: Invalid data field in request
root at hudsonbay-obmc:~#
=====
However, there is a kind of error message "Get SDR 0003 command failed: Invalid data field in request" always been shown behind it. I take a look at it via journal log in OpenBMC what error it is. That is:
=====
Jan 01 00:01:24 hudsonbay-obmc ipmid[157]: GetMangagedObjects for getSensorMap failed
Jan 01 00:01:24 hudsonbay-obmc ipmid[157]: getSensorDataRecord: getSensorMap error
Jan 01 00:01:24 hudsonbay-obmc ipmid[157]: ipmiStorageGetSDR: fail to get SDR
root at hudsonbay-obmc:~# journalctl -o json-pretty MESSAGE="GetMangagedObjects for getSensorMap failed"
{
"_BOOT_ID" : "d932ab64935943c1b937993b3d4c0510",
"__REALTIME_TIMESTAMP" : "84903987",
"_SYSTEMD_CGROUP" : "/system.slice/phosphor-ipmi-host.service",
"PRIORITY" : "3",
"_CAP_EFFECTIVE" : "1ffffffffff",
"CODE_FUNC" : "helper_log",
"_SYSTEMD_UNIT" : "phosphor-ipmi-host.service",
"_SYSTEMD_SLICE" : "system.slice",
"_UID" : "0",
"_HOSTNAME" : "hudsonbay-obmc",
"MESSAGE" : "GetMangagedObjects for getSensorMap failed",
"__MONOTONIC_TIMESTAMP" : "84903992",
"_MACHINE_ID" : "3e55a692862e4acfbfec1956db0d0ee0",
"_SYSTEMD_INVOCATION_ID" : "20eebfb3a701452ebfc226117b2cbbe9",
"SYSLOG_IDENTIFIER" : "ipmid",
"_TRANSPORT" : "journal",
"ERROR" : "Invalid request descriptor",
"_PID" : "157",
"__CURSOR" : "s=2d0eebf065d24b7fba5a24a670d2ffbf;i=30d;b=d932ab64935943c1b937993b3d4c0510;m=50f8838;t=50f8833;x=defc23b87af8e29b",
"TRANSACTION_ID" : "3524473669",
"CODE_LINE" : "76",
"CODE_FILE" : "/usr/src/debug/intel-ipmi-oem/0.1+git999-r0/recipe-sysroot/usr/include/phosphor-logging/log.hpp",
"_SOURCE_REALTIME_TIMESTAMP" : "84903950",
"_EXE" : "/usr/bin/ipmid",
"_GID" : "0",
"_COMM" : "ipmid",
"_CMDLINE" : "ipmid"
}
=====
I have tried to figure out it but with limited capability, can someone help to provide some suggestions for me? I mean how to fix it, or I'm able to ignore it because the SDR has been listed?
Thank you.
Regards,
Chris Chen
Legal Disclaimer :
The information contained in this message may be privileged and confidential.
It is intended to be read only by the individual or entity to whom it is addressed
or by their designee. If the reader of this message is not the intended recipient,
you are on notice that any distribution of this message, in any form,
is strictly prohibited. If you have received this message in error,
please immediately notify the sender and delete or destroy any copy of this message!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20211108/b9ae0cea/attachment-0001.htm>
More information about the openbmc
mailing list