Crashing Phosphor Settings Manager

[Chris Austen]

David Müller (ELSOFT AG) <d.mueller at elsoft.ch> wrote on 08/11/2017 09:47:42
AM:

> From: David Müller (ELSOFT AG) <d.mueller at elsoft.ch>
> To: Chris Austen <austenc at us.ibm.com>
> Cc: Andrew Jeffery <andrew at aj.id.au>, openbmc at lists.ozlabs.org
> Date: 08/11/2017 09:47 AM
> Subject: Re: Crashing Phosphor Settings Manager
>
> Hello
>
> Thanks for the hint.
>
> Chris Austen wrote:
>
> > I don't think there is any one process that is responsible for
> > /org/openbmc/control. It is a parent of other processes though.
> >
> > org.openbmc.control.Bmc       /org/openbmc/control/bmc0
> > org.openbmc.control.Power     /org/openbmc/control/power0
> > org.openbmc.control.Chassis   /org/openbmc/control/chassis0
> > org.openbmc.control.BmcFlash  /org/openbmc/control/flash
> >
> > So it appears not 1 of the 4 processes is starting up on the
> > evb-ast2500 build. That is not a bad thing though.  The
> > org.openbmc.control (any org.openbmc really) is in violation of the
> > dbus spec and as such we have moved most services over to
> > xyz.openbmc_project.  Seems like the evb-ast2500 is ready to have
> > the settings_manager.py from phosphor/settingd repository fixed up.
> >
> > So you can ignore that message and focus on the /xyz/openbmc/control
> > interfaces
>
> This should be "/xyz/openbmc_project/control", isn't it?

oops yes... openbmc_project

Chris

>
>
> Dave
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170811/5b9a4229/attachment.html>