[phosphor-state-manager] Error reading HostFirmware condition, error: sd_bus_call: org.freedesktop.DBus.Error.ServiceUnknown

Jordan Chang jordan.chang at ufispace.com
Mon Apr 18 20:31:04 AEST 2022


Hi Sir/Madam,
I am implementing the power control mechanisms for my platform, and
encounter the problem in below:
*phosphor-host-state-manager[341]: Error reading HostFirmware condition,
error: sd_bus_call: org.freedesktop.DBus.Error.ServiceUnknown: The name is
not activatable, service: xyz.openbmc_project.Control.Host path:
/xyz/openbmc_project/control/host0*

I am using the host0-ready gpio pin to determine the HostFirmwareCondition
is running or not. However, the service
*xyz.openbmc_project.State.Host.HostState* could not be established since
the dbus call method of  *xyz.openbmc_project.Control.Host *returns an
error. Therefore, I have printed some debug messages starting with Ufi to
ensure the xyz.openbmc_project.State.HostCondition.Gpio service is involved
in phosphor-host-state-manager. Not sure why the bus call function of
*xyz.openbmc_project.Control.Host
service* failed. Which packages or settings should I configure to enable
this service?  Could someone give me some instructions or suggestions?
Thank you!

```
root at siad:~# obmcutil state
CurrentBMCState     : xyz.openbmc_project.State.BMC.BMCState.NotReady
CurrentPowerState   : xyz.openbmc_project.State.Chassis.PowerState.On
Error finding '/xyz/openbmc_project/state/host0' service: Input/output error

---------------------------------------------------------------------------------------------------------------------------
root at siad:~# busctl call  xyz.openbmc_project.ObjectMapper
 /xyz/openbmc_project /object_mapper xyz.openbmc_project.ObjectMapper
GetSubTree sias ""  0 1  "xyz.op enbmc_project.Condition.HostFirmware"
a{sa{sas}} 2 "/xyz/openbmc_project/Gpios/host0" 1
"xyz.openbmc_project.State.Hos tCondition.Gpio" 4
"org.freedesktop.DBus.Introspectable" "org.freedesktop.DBus.P eer"
"org.freedesktop.DBus.Properties" "xyz.openbmc_project.Condition.HostFirmwa
re" "/xyz/openbmc_project/control/host0" 1
"xyz.openbmc_project.Control.Host" 5  "org.freedesktop.DBus.Introspectable"
"org.freedesktop.DBus.Peer" "org.freedeskt op.DBus.Properties"
"xyz.openbmc_project.Condition.HostFirmware" "xyz.openbmc_pr
oject.Control.Host"

---------------------------------------------------------------------------------------------------------------------------
root at siad:~# busctl get-property
xyz.openbmc_project.State.HostCondition.Gpio
/xyz/openbmc_project/Gpios/host0
 xyz.openbmc_project.Condition.HostFirmware  CurrentFirmwareCondition
s "xyz.openbmc_project.Condition.HostFirmware.FirmwareCondition.Running"

---------------------------------------------------------------------------------------------------------------------------
root at siad:~# journalctl | grep -i phosphor-host-state-manager
Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Check if host is
running
Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Ufi:
mapper1=/xyz/openbmc_project/Gpios/host0
Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Ufi:
mapper1=/xyz/openbmc_project/control/host0
Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Ufi:
mapper2=xyz.openbmc_project.State.HostCondition.Gpio
Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Ufi:
mapper2=xyz.openbmc_project.Control.Host
Apr 18 08:19:14 siad phosphor-host-state-manager[341]: terminate called
after throwing an instance of 'sdbusplus::exception::SdBusError'
Apr 18 08:19:14 siad phosphor-host-state-manager[341]:   what():
 sd_bus_call: org.freedesktop.DBus.Error.ServiceUnknown: The name is not
activatable
Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Ufi:
path=/xyz/openbmc_project/control/host0
Apr 18 08:19:13 siad phosphor-host-state-manager[341]: Ufi:
services=xyz.openbmc_project.Control.Host
Apr 18 08:19:14 siad phosphor-host-state-manager[341]: Error reading
HostFirmware condition, error: sd_bus_call:
org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable,
service: xyz.openbmc_project.Control.Host path:
/xyz/openbmc_project/control/host0
Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Check if host is
running
Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
mapper1=/xyz/openbmc_project/Gpios/host0
Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
mapper1=/xyz/openbmc_project/control/host0
Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
mapper2=xyz.openbmc_project.State.HostCondition.Gpio
Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
mapper2=xyz.openbmc_project.Control.Host
Apr 18 08:19:24 siad phosphor-host-state-manager[366]: terminate called
after throwing an instance of 'sdbusplus::exception::SdBusError'
Apr 18 08:19:24 siad phosphor-host-state-manager[366]:   what():
 sd_bus_call: org.freedesktop.DBus.Error.ServiceUnknown: The name is not
activatable
Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
path=/xyz/openbmc_project/control/host0
Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Ufi:
services=xyz.openbmc_project.Control.Host
Apr 18 08:19:24 siad phosphor-host-state-manager[366]: Error reading
HostFirmware condition, error: sd_bus_call:
org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable,
service: xyz.openbmc_project.Control.Host path:
/xyz/openbmc_project/control/host0

```

Best regards,
Jordan Chang

-- 
******************************
This e-mail is confidential. If you are not 
the intended recipient, you must not disclose, distribute or use the 
information in it as this could be a breach of confidentiality.If you have 
received this message in error, please advise us immediately by return 
e-mail and delete the document. The address from which this message has 
been sent is strictly for business mail only and the company reserves the 
right to monitor the contents of communications and take action where and 
when it is deemed necessary.
Thank you for your co-operation.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20220418/5dfc99aa/attachment.htm>


More information about the openbmc mailing list