On 20/07/18 12:05, David Sommerseth wrote:
> Hi,
> 
> Just wondering if more people have seen issues with dbus-1.10.24-7 on SL.  The 
> host I'm seeing these issue on are running SL 7.4 as the base install, with 
> security and fastbugs repos enabled.
> 
> The issue I'm seeing is:
> 
> # systemctl reload dbus
> Job for dbus.service failed because the control process exited with error code. See "systemctl status dbus.service" and "journalctl -xe" for details.
> # journalctl -u dbus
> Jul 20 11:59:48 server dbus[689]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses
> Jul 20 11:59:48 server dbus-daemon[689]: dbus[689]: [system] Unable to reload configuration: Configuration file needs one or more <listen> elements giving addresses
> Jul 20 11:59:48 server systemd[1]: dbus.service: control process exited, code=exited status=1
> Jul 20 11:59:48 server dbus-send[6087]: Error org.freedesktop.DBus.Error.Failed: Configuration file needs one or more <listen> elements giving addresses
> Jul 20 11:59:48 server systemd[1]: Reload failed for D-Bus System Message Bus.
> # rpm -qV dbus ; echo $?  # verifying no dbus files modified
> 0
> # rpm -q dbus
> dbus-1.10.24-7.el7.x86_64
> 
> 
> If I do a 'yum downgrade dbus dbus-libs' which gives me
> dbus-1.6.12-17.el7.x86_64.rpm, everything works as expected again.
> 
> Is this a known issue?  Is it specific to SL, or something others have seen on
> RHEL or CentOS as well?

I figured out this issue.  It was simply related to a missing reboot, so the
D-Bus daemon running was the old dbus-1.6 version, which didn't understand the
new config changes which was shipped with dbus-1.10.  But rebooting was safe
in this case, and everything works as expected again.

Sorry about the noise.

-- 
kind regards,

David Sommerseth