search

openbmc / phosphor-state-manager

Apache License 2.0
11 stars 21 forks source link

phosphor-systemd-target-monitor intermittently failing on startup with org.freedesktop.DBus.Error.ServiceUnknown: #10

Closed geissonator closed 4 years ago

geissonator commented 4 years ago

Seeing this intermittently where it fails to subscribe to system signals. It restarts and is fine but something is up with the system dbus api's. Either they are not registered yet on the bus or systemd is just overloaded

"SDBUSERR" : "sd_bus_call: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable"

Nov 05 21:37:47 witherspoon rsyslogd[164]: warning: ~ action is deprecated, consider using the 'stop' statement instead [v8.1910.0 try https://www.rsyslog.com/e/2307 ]
Nov 05 21:37:47 witherspoon phosphor-systemd-target-monitor[163]: Failed to subscribe to systemd signals
Nov 05 21:37:48 witherspoon phosphor-systemd-target-monitor[163]: terminate called after throwing an instance of 'sdbusplus::xyz::openbmc_project::Common::Error::InternalFailure'
Nov 05 21:37:48 witherspoon phosphor-systemd-target-monitor[163]:   what():  xyz.openbmc_project.Common.Error.InternalFailure: The operation failed internally.
Nov 05 21:37:47 witherspoon rsyslogd[164]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.1910.0]
Nov 05 21:37:47 witherspoon phosphor-systemd-target-monitor[163]: The operation failed internally.
Nov 05 21:37:47 witherspoon rsyslogd[164]: [origin software="rsyslogd" swVersion="8.1910.0" x-pid="164" x-info="https://www.rsyslog.com"] start
geissonator commented 4 years ago

A pcap shows that the service is starting and trying to talk with systemd before systemd has registered itself on Dbus. I'm not finding any obvious ways to wait for systemd to have registered itself on Dbus.

amboar commented 4 years ago

Sounds like a bug should be opened against systemd?