hostnamectl not working, system_bus_socket in /run/dbus not in /var/run/dbus
I am running Centos 7 in a virtual machine. We use systemctl and hostnamectl, so dbus is included when we build our image as a dependency of systemd.
In the past, we have had no issue with dbus running correctly, and therefore hostnamectl, etc. Yesterday I generated a new image (without changing any settings) and we ran into this issue. Hostnamectl, systemd-logind.service and a couple of other services failed to run. Eventually, we found that it was due to the location of system_bus_socket. It was created in /run/dbus and should have been created in /var/run/dbus instead. Once a symlink was created to /var/run/dbus, all the failed systems ran correctly.
My question is why was the system_bus_socket created where it was? Is this a change of behavior? I checked the logs, and the version of dbus that yum installed was dbus-libs-1.10.24-7.el7.x86_64
Actually, the following packages were installed:
dbus x86_64 1:1.10.24-7.el7 centos-os 245 k
dbus-glib x86_64 0.100-7.el7 centos-os 102 k
dbus-libs x86_64 1:1.10.24-7.el7 centos-os 169 k
dbus-python x86_64 1.1.1-9.el7 centos-os 206 k
Last edited by hieberm; 05-22-2018 at 08:52 AM.
Reason: Adding all dbus packages installed
|