Phosphor-host-check failing when running sdbus commands

[Andrew Geissler]

> On May 11, 2021, at 9:38 AM, Brandon Ong <Brandon.Ong at fii-na.com> wrote:
> 
> Hi All,
> 
> This is the issue I encountered and I’m still stuck on..
> 
> Using journalctl -u phosphor-reset-host-check at 0.service
>  
> Apr 28 23:28:18 kudo systemd[1]: Starting Check Host0 status on BMC reset...
> Apr 28 23:28:20 kudo phosphor-host-check[973]: Check if host is running
> Apr 28 23:28:20 kudo phosphor-host-check[973]: Error in mapper call for control host, use default service
> Apr 28 23:28:25 kudo phosphor-host-check[973]: Error in call to control host Execute
> Apr 28 23:28:25 kudo phosphor-host-check[973]: terminate called after throwing an instance of 'sdbusplus::exception::SdBusError'
> Apr 28 23:28:25 kudo phosphor-host-check[973]:   what():  sd_bus_call: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
> Apr 28 23:28:33 kudo systemd[1]: phosphor-reset-host-check at 0.service: Main process exited, code=dumped, status=6/ABRT
> Apr 28 23:28:33 kudo systemd[1]: phosphor-reset-host-check at 0.service: Failed with result 'core-dump'.
> Apr 28 23:28:33 kudo systemd[1]: Failed to start Check Host0 status on BMC reset.

You may want to try out https://gerrit.openbmc-project.xyz/q/topic:%22bmc-reset-host-up%22+(status:open%20OR%20status:merged)

I’ve been refactoring this code path. You’d want to be sure you have the phosphor-host-ipmid, phosphor-state-manager, and phosphor-dbus-interface commits. The pldm one’s are not needed.

> 
> Thanks,
> Brandon