Failed to start D-Bus System Message Bus after system migration

This document (000021223) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 15 SP4
SUSE Linux Enterprise Server for SAP Applications 15 SP4

Situation

After an OS migration from SUSE 12 SP5 to SUSE 15 SP4, the dbus.service systemd service cannot be started. The messages are similar to the following:

# /bin/systemctl status 'dbus.service'
× dbus.service - D-Bus System Message Bus
     Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
     Active: failed (Result: exit-code) since Mon 2023-09-11 09:45:42 EDT; 1s ago
TriggeredBy: × dbus.socket
       Docs: man:dbus-daemon(1)
    Process: 20726 ExecStart=/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only (code=exited, status=127)
   Main PID: 20726 (code=exited, status=127)

Sep 11 09:45:42 sles15-sp4 systemd[1]: Started D-Bus System Message Bus.
Sep 11 09:45:42 sles15-sp4 dbus-daemon[20726]: /usr/bin/dbus-daemon: /lib64/libdbus-1.so.3: no version information available (required by /usr/bin/dbus-daemon)
Sep 11 09:45:42 sles15-sp4 dbus-daemon[20726]: /usr/bin/dbus-daemon: /lib64/libdbus-1.so.3: no version information available (required by /usr/bin/dbus-daemon)
Sep 11 09:45:42 sles15-sp4 dbus-daemon[20726]: /usr/bin/dbus-daemon: symbol lookup error: /usr/bin/dbus-daemon: undefined symbol: _dbus_no_memory_message, version LIBDBUS_PRIVATE_1.12.2
Sep 11 09:45:42 sles15-sp4 systemd[1]: dbus.service: Main process exited, code=exited, status=127/n/a
Sep 11 09:45:42 sles15-sp4 systemd[1]: dbus.service: Failed with result 'exit-code'.
Sep 11 09:45:42 sles15-sp4 systemd[1]: dbus.service: Start request repeated too quickly.
Sep 11 09:45:42 sles15-sp4 systemd[1]: dbus.service: Failed with result 'exit-code'.
Sep 11 09:45:42 sles15-sp4 systemd[1]: Failed to start D-Bus System Message Bus.

After running chkbin /usr/bin/dbus-daemon, the following were observed:

#--[ Checking File Ownership ]-------------------------------------#
/usr/bin/dbus-daemon           - from RPM: dbus-1-1.12.2-150400.18.8.1.x86_64
/usr/bin/dbus-daemon:          - from RPM:      [  Not Owned  ]
 :MD5SUM
/usr/bin/dbus-daemon:          - from RPM:      [  Not Owned  ]
 :MD5SUM
/lib64/ld-linux-x86-64.so.2    - from RPM: glibc-2.31-150300.52.2.x86_64
/lib64/libdbus-1.so.3          - from RPM:      [   SymLink   ]
 ->/lib64/libdbus-1.so.3.8.11  - from RPM:      [  Not Owned  ]
 :MD5SUM bdb1ef08c873c70a1fb6c6659c20c6a0
<snip>
 
 #--[ Shared Library Dependencies ]---------------------------------#
# ldd /usr/bin/dbus-daemon
/usr/bin/dbus-daemon: /lib64/libdbus-1.so.3: no version information available (required by /usr/bin/dbus-daemon)
/usr/bin/dbus-daemon: /lib64/libdbus-1.so.3: no version information available (required by /usr/bin/dbus-daemon)
        linux-vdso.so.1 (0x00007ffe1a381000)
<snip>

Resolution

Do the following:

Remove /lib64/libdbus-1.so.3
Reboot
Run systemctl status dbus.service to confirm the dbus service started

Cause

In SLES 15 SP4, the directory structure changes compared to SLES 12 SP5. In this specific case, the directory /lib64 has not been cleaned up during the migration, leaving /lib64/libdbus-1.so.3. The root cause is unknown, as the issue could not be duplicated.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

Document ID:000021223
Creation Date: 04-Oct-2023
Modified Date:06-Nov-2023
- SUSE Linux Enterprise Server
- SUSE Linux Enterprise Server for SAP Applications

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com