My system has been running Leap 42.1 for years without issue. Recently I get random boot failures where the desktop doesn’t start.
/var/log/messages has the following and many similar messages.
dbus[812]: [system] Failed to activate service ‘org.freedesktop.systemd1’: timed out
systemd-logind[835]: Failed to enable subscription: Activation of org.freedesktop.systemd1 timed out
Restarting the system works but the problem randomly occurs again.
If you recursively grep for “dbus.socket” and “dbus.service” in ‘/usr/lib/systemd/’ you should find that, there’s quite a number of systemd services which are dependent on the systemd D-Bus service and socket.
The systemd D-Bus service and socket are started due to “After=”, “Requires=”, “Wants=” and “Requisite=” systemd dependencies in other systemd services but, there ain’t no record of either the systemd D-Bus service or, the associated socket, being started in the systemd Journal – for whatever reason …
Below is the output of busctl as you asked (system booted fine for this session), followed by the recursive grep from /usr/lib/systemd/.
The problem seems random. The system boots and runs normally and every once in a while Fails.
When it fails, I cannot log in. Desktop is black. Nor can I ssh into the system.
busctl status org.freedesktop.systemd1
Failed to get credentials: No such process
Output of recursive grep:
egrep -R “dbus.socket” *
system/multi-user.target.wants/systemd-logind.service:# Ask for the dbus socket. If running over kdbus, the socket will
system/multi-user.target.wants/systemd-logind.service:Wants=dbus.socket
system/multi-user.target.wants/systemd-logind.service:After=dbus.socket
system/multi-user.target.wants/dbus.service:Requires=dbus.socket
system/display-manager.service:Wants=remote-fs.target dbus.socket systemd-user-sessions.service
system/display-manager.service:After=remote-fs.target dbus.socket systemd-user-sessions.service getty@tty7.service plymouth-quit.service
system/dbus-org.freedesktop.login1.service:# Ask for the dbus socket. If running over kdbus, the socket will
system/dbus-org.freedesktop.login1.service:Wants=dbus.socket
system/dbus-org.freedesktop.login1.service:After=dbus.socket
system/systemd-logind.service:# Ask for the dbus socket. If running over kdbus, the socket will
system/systemd-logind.service:Wants=dbus.socket
system/systemd-logind.service:After=dbus.socket
system/dbus.service:Requires=dbus.socket
Binary file systemd matches
mythtv@b9:/usr/lib/systemd> egrep -R “dbus.service” *
system/wickedd-auto4.service:Requisite=dbus.service
system/wickedd-auto4.service:After=local-fs.target dbus.service SuSEfirewall2_init.service
system/wickedd-dhcp4.service:Requisite=dbus.service
system/wickedd-dhcp4.service:After=local-fs.target dbus.service SuSEfirewall2_init.service
system/wickedd-dhcp6.service:Requisite=dbus.service
system/wickedd-dhcp6.service:After=local-fs.target dbus.service SuSEfirewall2_init.service
system/wickedd-nanny.service:Requisite=dbus.service
system/wickedd-nanny.service:After=local-fs.target dbus.service SuSEfirewall2_init.service wickedd.service
system/wickedd.service:Requisite=dbus.service
journalctl doesn’t recognize --vacuum-time.
–help doesn’t show any options for clearing the journals.
Maybe an old version? Output of --version is shown below.
I didn’t remember to take account of the systemd Journal version differences – as an example and taking account of the fact that on this system I usually keep only a few months of systemd Journal –
# journalctl --disk-usage
Archived and active journals take up 648.0M in the file system.
# journalctl --vacuum-time=12months
Vacuuming done, freed 0B of archived journals from /run/log/journal.
Vacuuming done, freed 0B of archived journals from /var/log/journal.
Vacuuming done, freed 0B of archived journals from /var/log/journal/02d4bd6562f443dc87a4204963c403f6.
# journalctl --vacuum-time=6months
Vacuuming done, freed 0B of archived journals from /var/log/journal.
Vacuuming done, freed 0B of archived journals from /var/log/journal/02d4bd6562f443dc87a4204963c403f6.
Vacuuming done, freed 0B of archived journals from /run/log/journal.
# journalctl --vacuum-time=5months
Vacuuming done, freed 0B of archived journals from /var/log/journal/02d4bd6562f443dc87a4204963c403f6.
Vacuuming done, freed 0B of archived journals from /run/log/journal.
Vacuuming done, freed 0B of archived journals from /var/log/journal.
# journalctl --vacuum-time=4months
Vacuuming done, freed 0B of archived journals from /var/log/journal/02d4bd6562f443dc87a4204963c403f6.
Vacuuming done, freed 0B of archived journals from /run/log/journal.
Vacuuming done, freed 0B of archived journals from /var/log/journal.
#
Of course, the systemd journaling on your system is an other version – on this Leap 15.4 system, the systemd Journal version is:
