<html><body><p><tt><font size="2">"openbmc" <openbmc-bounces+austenc=us.ibm.com@lists.ozlabs.org> wrote on 08/10/2017 09:20:54 AM:<br><br>> From: Andrew Jeffery <andrew@aj.id.au></font></tt><br><tt><font size="2">> To: David Müller (ELSOFT AG) <d.mueller@elsoft.ch>, openbmc@lists.ozlabs.org</font></tt><br><tt><font size="2">> Date: 08/10/2017 09:21 AM</font></tt><br><tt><font size="2">> Subject: Re: Crashing Phosphor Settings Manager</font></tt><br><tt><font size="2">> Sent by: "openbmc" <openbmc-bounces+austenc=us.ibm.com@lists.ozlabs.org></font></tt><br><tt><font size="2">> <br>> Hi Dave,<br>> <br>> On Thu, Aug 10, 2017, at 23:07, David Müller (ELSOFT AG) wrote:<br>> > Hello<br>> > <br>> > While trying to further debug my problem, I had the idea to check how<br>> > things are done on the AST2500 eval board. So I built and install a new<br>> > flash image using the "evb-ast2500" configuration.<br>> > <br>> > Unfortunately the symtoms are the same as with my custom configuration.<br>> > <br>> > - The evb-ast2500 OpenBMC configuration is known to be good, isn't it?<br>> > <br>> > - Which process/service is responsible for the "/org/openbmc/control"<br>> > object?<br></font></tt><br><tt><font size="2">I don't think there is any one process that is responsible for /org/openbmc/control.</font></tt><br><tt><font size="2">It is a parent of other processes though. </font></tt><br><br><tt><font size="2">org.openbmc.control.Bmc /org/openbmc/control/bmc0</font></tt><br><tt><font size="2">org.openbmc.control.Power /org/openbmc/control/power0</font></tt><br><tt><font size="2">org.openbmc.control.Chassis /org/openbmc/control/chassis0</font></tt><br><tt><font size="2">org.openbmc.control.BmcFlash /org/openbmc/control/flash</font></tt><br><br><tt><font size="2">So it appears not 1 of the 4 processes is starting up on the evb-ast2500 build.</font></tt><br><tt><font size="2">That is not a bad thing though. The org.openbmc.control (any org.openbmc really)</font></tt><br><tt><font size="2">is in violation of the dbus spec and as such we have moved most services over to</font></tt><br><tt><font size="2">xyz.openbmc_project. Seems like the evb-ast2500 is ready to have the </font></tt><br><tt><font size="2">settings_manager.py from phosphor/settingd repository fixed up.</font></tt><br><br><tt><font size="2">So you can ignore that message and focus on the /xyz/openbmc/control interfaces</font></tt><br><br><tt><font size="2">> > <br>> > <br>> > root@evb-ast2500:~# cat /etc/os-release<br>> > ID="openbmc-phosphor"<br>> > NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference Distro)"<br>> > VERSION="v1.99.8-208"<br>> > VERSION_ID="v1.99.8-208-g4ee67571-dirty"<br>> > PRETTY_NAME="Phosphor OpenBMC (Phosphor OpenBMC Project Reference<br>> > Distro) v1.99.8-208"<br>> > BUILD_ID="v1.99.8"<br>> > <br>> > <br>> > <br>> > Aug 10 11:28:27 evb-ast2500 daemon.info systemd[1]: Starting Phosphor<br>> > Settings Manager...<br>> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:<br>> > Traceback (most recent call last):<br>> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:<br>> > File "/usr/sbin/settings_manager.py", line 262, in <module><br>> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:<br>> > allobjects = create_object(s.SETTINGS)<br>> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:<br>> > File "/usr/sbin/settings_manager.py", line 72, in create_object<br>> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:<br>> > retries=10, interval=0.1)<br>> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:<br>> > File "/usr/lib/python2.7/site-packages/obmc/mapper/bindings.py", line<br>> > 66, in get_subtree_paths<br>> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:<br>> > retries, interval)<br>> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:<br>> > File "/usr/lib/python2.7/site-packages/obmc/mapper/bindings.py", line<br>> > 42, in retry<br>> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:<br>> > return func()<br>> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:<br>> > File "/usr/lib/python2.7/site-packages/obmc/mapper/bindings.py", line<br>> > 65, in <lambda><br>> > Aug 10 11:28:29 evb-ast2500 daemon.info settings_manager.py[1033]:<br>> > path, de/lib/python2.7/site-packages/dbus/connection.py", line 651, in<br>> > call_blocking<br>> > Aug 10 11:40:45 evb-ast2500 daemon.info settings_manager.py[1589]:<br>> > message, timeout)<br>> > Aug 10 11:40:45 evb-ast2500 daemon.info settings_manager.py[1589]:<br>> > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.FileNotFound:<br>> > path or object not found: /org/openbmc/control<br>> > Aug 10 11:40:45 evb-ast2500 daemon.notice systemd[1]:<br>> > org.openbmc.settings.Host<br>> > .service: Main process exited, code=exited, status=1/FAILURE<br>> > Aug 10 11:40:45 evb-ast2500 daemon.err systemd[1]: Failed to start<br>> > Phosphor Settings Manager.<br>> > Aug 10 11:40:45 evb-ast2500 daemon.notice systemd[1]:<br>> > org.openbmc.settings.Host.service: Unit entered failed state.<br>> > Aug 10 11:40:45 evb-ast2500 daemon.warn systemd[1]:<br>> > org.openbmc.settings.Host.service: Failed with result 'exit-code'.<br>> > Aug 10 11:40:46 evb-ast2500 daemon.info systemd[1]:<br>> > org.openbmc.settings.Host.service: Service hold-off time over,<br>> > scheduling restart.<br>> > Aug 10 11:40:46 evb-ast2500 daemon.info systemd[1]: Stopped Phosphor<br>> > Settings Manager.<br>> <br>> Your best bet might be to open an issue on Github. I had a quick search<br>> and couldn't see any existing issues that were relevant.<br>> <br>> Andrew<br>> <br>> > <br>> > <br>> > Dave<br>> <br></font></tt><BR>
</body></html>