Crashing Phosphor Settings Manager

Chris Austen austenc at us.ibm.com
Fri Aug 11 08:04:42 AEST 2017



"openbmc" <openbmc-bounces+austenc=us.ibm.com at lists.ozlabs.org> wrote on
08/10/2017 09:20:54 AM:

> From: Andrew Jeffery <andrew at aj.id.au>
> To: David Müller (ELSOFT AG) <d.mueller at elsoft.ch>,
openbmc at lists.ozlabs.org
> Date: 08/10/2017 09:21 AM
> Subject: Re: Crashing Phosphor Settings Manager
> Sent by: "openbmc" <openbmc-bounces+austenc=us.ibm.com at lists.ozlabs.org>
>
> Hi Dave,
>
> On Thu, Aug 10, 2017, at 23:07, David Müller (ELSOFT AG) wrote:
> > Hello
> >
> > While trying to further debug my problem, I had the idea to check how
> > things are done on the AST2500 eval board. So I built and install a new
> > flash image using the "evb-ast2500" configuration.
> >
> > Unfortunately the symtoms are the same as with my custom configuration.
> >
> > - The evb-ast2500 OpenBMC configuration is known to be good, isn't it?
> >
> > - Which process/service is responsible for the "/org/openbmc/control"
> >   object?

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

> >
> >
> > root at evb-ast2500:~# cat /etc/os-release
> > ID="openbmc-phosphor"
> > NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"
> > VERSION="v1.99.8-208"
> > VERSION_ID="v1.99.8-208-g4ee67571-dirty"
> > PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference
> > Distro) v1.99.8-208"
> > BUILD_ID="v1.99.8"
> >
> >
> >
> > Aug 10 11:28:27 evb-ast2500 daemon.info systemd[1]: Starting Phosphor
> > Settings Manager...
> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:
> > Traceback (most recent call last):
> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:
> > File "/usr/sbin/settings_manager.py", line 262, in <module>
> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:
> > allobjects = create_object(s.SETTINGS)
> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:
> > File "/usr/sbin/settings_manager.py", line 72, in create_object
> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:
> > retries=10, interval=0.1)
> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:
> > File "/usr/lib/python2.7/site-packages/obmc/mapper/bindings.py", line
> > 66, in get_subtree_paths
> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:
> > retries, interval)
> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:
> > File "/usr/lib/python2.7/site-packages/obmc/mapper/bindings.py", line
> > 42, in retry
> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:
> > return func()
> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:
> > File "/usr/lib/python2.7/site-packages/obmc/mapper/bindings.py", line
> > 65, in <lambda>
> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:
> > path, de/lib/python2.7/site-packages/dbus/connection.py", line 651, in
> > call_blocking
> > Aug 10 11:40:45 evb-ast2500 daemon.info settings_manager.py[1589]:
> > message, timeout)
> > Aug 10 11:40:45 evb-ast2500 daemon.info settings_manager.py[1589]:
> > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.FileNotFound:
> > path or object not found: /org/openbmc/control
> > Aug 10 11:40:45 evb-ast2500 daemon.notice systemd[1]:
> > org.openbmc.settings.Host
> > .service: Main process exited, code=exited, status=1/FAILURE
> > Aug 10 11:40:45 evb-ast2500 daemon.err systemd[1]: Failed to start
> > Phosphor Settings Manager.
> > Aug 10 11:40:45 evb-ast2500 daemon.notice systemd[1]:
> > org.openbmc.settings.Host.service: Unit entered failed state.
> > Aug 10 11:40:45 evb-ast2500 daemon.warn systemd[1]:
> > org.openbmc.settings.Host.service: Failed with result 'exit-code'.
> > Aug 10 11:40:46 evb-ast2500 daemon.info systemd[1]:
> > org.openbmc.settings.Host.service: Service hold-off time over,
> > scheduling restart.
> > Aug 10 11:40:46 evb-ast2500 daemon.info systemd[1]: Stopped Phosphor
> > Settings Manager.
>
> Your best bet might be to open an issue on Github. I had a quick search
> and couldn't see any existing issues that were relevant.
>
> Andrew
>
> >
> >
> > Dave
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20170810/e1b06ef3/attachment.html>


More information about the openbmc mailing list