[SOLVED] systemd-logind failures

[upnort]

I see systemd-logind.service failures when starting CentOS 7 containers. I have one Ubuntu Server container that does not have this problem.

I searched the web to no avail.

The logs and systemctl output indicate an inability to connect to dbus.

Thanks again for any help.

systemctl status systemd-logind

* systemd-logind.service - Login Service
   Loaded: loaded (/etc/systemd/system/systemd-logind.service; static; vendor preset: disabled)
   Active: failed (Result: start-limit) since Thu 2018-05-31 15:24:07 CDT; 37min ago
     Docs: man:systemd-logind.service(8)
           man:logind.conf(5)
           http://www.freedesktop.org/wiki/Software/systemd/logind
           http://www.freedesktop.org/wiki/Software/systemd/multiseat
  Process: 82 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
 Main PID: 82 (code=exited, status=1/FAILURE)
   Status: "Shutting down..."

May 31 15:24:07 www systemd[1]: Failed to start Login Service.
May 31 15:24:07 www systemd[1]: Unit systemd-logind.service entered failed state.
May 31 15:24:07 www systemd[1]: systemd-logind.service failed.
May 31 15:24:07 www systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
May 31 15:24:07 www systemd[1]: start request repeated too quickly for systemd-logind.service
May 31 15:24:07 www systemd[1]: Failed to start Login Service.
May 31 15:24:07 www systemd[1]: Unit systemd-logind.service entered failed state.
May 31 15:24:07 www systemd[1]: systemd-logind.service failed.

Attempting to run systemd-logind directly:

/usr/lib/systemd/systemd-logind
Failed to connect to system bus: No such file or directory
Failed to fully start up daemon: No such file or directory

systemctl status dbus.service

* dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib/systemd/system/dbus.service; static; vendor preset: disabled)
   Active: active (running) since Thu 2018-05-31 15:24:07 CDT; 40min ago
     Docs: man:dbus-daemon(1)
 Main PID: 56 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           `-56 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation

May 31 15:24:07 www systemd[1]: Started D-Bus System Message Bus.
May 31 15:24:07 www systemd[1]: Starting D-Bus System Message Bus...

systemctl status dbus.socket

* dbus.socket - D-Bus System Message Bus Socket
   Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static; vendor preset: disabled)
   Active: active (running) since Thu 2018-05-31 15:24:07 CDT; 40min ago
   Listen: /run/dbus/system_bus_socket (Stream)

May 31 15:24:07 www systemd[1]: Listening on D-Bus System Message Bus Socket.
May 31 15:24:07 www systemd[1]: Starting D-Bus System Message Bus Socket.

/run/dbus/system_bus_socket does exist.

proxmox-ve: 5.2-2 (running kernel: 4.15.17-2-pve)
pve-manager: 5.2-1 (running version: 5.2-1/0fcd7879)
pve-kernel-4.15: 5.2-2
pve-kernel-4.13: 5.1-45
pve-kernel-4.15.17-2-pve: 4.15.17-10
pve-kernel-4.15.17-1-pve: 4.15.17-9
pve-kernel-4.15.15-1-pve: 4.15.15-6
pve-kernel-4.13.16-3-pve: 4.13.16-49
pve-kernel-4.13.16-2-pve: 4.13.16-48
pve-kernel-4.13.16-1-pve: 4.13.16-46
pve-kernel-4.13.13-6-pve: 4.13.13-42
pve-kernel-4.13.13-5-pve: 4.13.13-38
pve-kernel-4.13.13-4-pve: 4.13.13-35
pve-kernel-4.13.13-3-pve: 4.13.13-34
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-4
libpve-common-perl: 5.0-32
libpve-guest-common-perl: 2.0-16
libpve-http-server-perl: 2.0-9
libpve-storage-perl: 5.0-23
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.0-3
lxcfs: 3.0.0-1
novnc-pve: 0.6-4
proxmox-widget-toolkit: 1.0-18
pve-cluster: 5.0-27
pve-container: 2.0-23
pve-docs: 5.2-4
pve-firewall: 3.0-9
pve-firmware: 2.0-4
pve-ha-manager: 2.0-5
pve-i18n: 1.0-5
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.1-5
pve-xtermjs: 1.0-5
qemu-server: 5.0-26
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.9-pve1~bpo9

 

[upnort]

I found the problem. /var/run is not sym linked to /run.

Odd how this happened only in some CentOS 7 containers but not all.

mv -f /var/run/* /run/; rm -rf /var/run; ln -s /run /var/run; reboot

 

[rubictus]

thanks, i had the same issue. Possibly because of using tmpfs for /run. (I'm running my containers on SSD)