Red Hat Bugzilla – Bug 1541061
systemd should provide clear indication in the system log that connection to system bus failed
Last modified: 2018-04-10 07:26:26 EDT
Description of problem: Currently, it is not really obvious that systemd didn't connect properly to dbus-daemon during system boot. When systemd is not connected to the dbus then some of its APIs are not available and system is overall in the degraded state. Right now we do the very poor job when it comes to reporting this situation. Version-Release number of selected component (if applicable): systemd-219-42.el7_4.7 How reproducible: rarely Steps to Reproduce: 1. This issue is hard to reproduce, but when it happens it is even harder to recognize from the log that it occurred. Actual results: systemd is not connected to dbus, there is no clear indication in the log Expected results: systemd is not connected to dbus, but it is possible to recognize the issue by looking at the system log Additional info: https://github.com/systemd/systemd/pull/7851
fix merged to staging branch -> https://github.com/lnykryn/systemd-rhel/pull/191 -> post
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0711