Results 1 to 2 of 2

Thread: systemd and DBus problem on fresh installed system

  1. #1

    Default systemd and DBus problem on fresh installed system

    Dear all,
    Recently I tried to do a fresh install on 2 desktops of openSUSE 42.3, after completing the installation and rebooting some systemd service took very long to start and end up failing. These are at least: systemd-logind, wicked(d), display-manager and ModemManager. After digging a bit further into the failing of the wicked services I found out that somehow systemd does not listen (correctly) on the DBus messagebus. Therefor it doesn't notice that org.opensuse.Network.* is registered and after a time-out period systemd kills the wicked services. I guess the same applies for the display-manager, because eventually the graphical interface and KDE desktop is shown.


    Which version did I try
    - installing openSUSE 42.3 with NET-installer
    - installing openSUSE 42.3 with USB-iso (and disconnected from network)
    - installing openSUSE 42.2 with USB-iso (both connected and disconnected to network)

    I tried to install as much as possible, and no change in package selection (just the default KDE desktop)

    What I observed
    (Almost) all DBus related systemd service fail, because systemd doesn't recognize/see the registered DBus interface. I think this all has to do with this log message at startup:
    Code:
    mrt 30 10:38:40 media dbus[1168]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
    If I start wicked from the command-line, like this:
    Code:
    $ /usr/lib/wicked/bin/wickedd-auto4 --systemd --foreground &
    $ /usr/lib/wicked/bin/wickedd-dhcp4 --systemd --foreground &
    $ /usr/lib/wicked/bin/wickedd-dhcp6 --systemd --foreground &
    $ /usr/sbin/wickedd --systemd --foreground &
    $ /usr/sbin/wickedd-nanny --systemd --foreground &
    $ /usr/sbin/wicked ifup all
    it works, I see org.opensuse.Network.* messages passing by in dbus-monitor and I can remotely login by using ssh. So I assume the DBus messagebus (system bus) is functioning, but it is systemd who has trouble connection/read it.

    What I tried
    comparing the new installation with a working openSUSE 42.3. As far as I can see the relevant systemd and dbus configuration files are the same.

    Below are some command output which I think are relevant, if more information is needed please don't hesitate to ask.
    Code:
    $ systemctl status -l 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 vr 2018-03-30 13:06:41 CEST; 11min ago
       Listen: /run/dbus/system_bus_socket (Stream)
    
    mrt 30 13:06:41 media systemd[1]: Listening on D-Bus System Message Bus Socket.
    Code:
    $ systemctl status -l 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 vr 2018-03-30 13:06:41 CEST; 11min ago
         Docs: man:dbus-daemon(1)
     Main PID: 1117 (dbus-daemon)
        Tasks: 1 (limit: 512)
       CGroup: /system.slice/dbus.service
               └─1117 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
    
    mrt 30 13:15:42 media dbus[1117]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
    mrt 30 13:15:42 media dbus[1117]: [system] Failed to activate service 'org.freedesktop.UDisks2': timed out
    mrt 30 13:16:07 media dbus[1117]: [system] Failed to activate service 'org.freedesktop.RealtimeKit1': timed out
    mrt 30 13:16:07 media dbus[1117]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
    mrt 30 13:16:07 media dbus[1117]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
    mrt 30 13:16:07 media dbus[1117]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
    mrt 30 13:16:07 media dbus[1117]: [system] Activating systemd to hand-off: service name='org.bluez' unit='dbus-org.bluez.service'
    mrt 30 13:16:32 media dbus[1117]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
    mrt 30 13:16:32 media dbus[1117]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
    mrt 30 13:16:32 media dbus[1117]: [system] Failed to activate service 'org.bluez': timed out
    Code:
    $ systemctl status -l systemd-logind.service
    ● systemd-logind.service - Login Service
       Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled)
       Active: failed (Result: start-limit) since vr 2018-03-30 13:06:43 CEST; 13min 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: 1171 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
     Main PID: 1171 (code=exited, status=1/FAILURE)
       Status: "Shutting down..."
    
    mrt 30 13:06:43 media systemd[1]: Failed to start Login Service.
    mrt 30 13:06:43 media systemd[1]: systemd-logind.service: Unit entered failed state.
    mrt 30 13:06:43 media systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
    mrt 30 13:06:43 media systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart.
    mrt 30 13:06:43 media systemd[1]: Stopped Login Service.
    mrt 30 13:06:43 media systemd[1]: systemd-logind.service: Start request repeated too quickly.
    mrt 30 13:06:43 media systemd[1]: Failed to start Login Service.
    mrt 30 13:06:43 media systemd[1]: systemd-logind.service: Unit entered failed state.
    mrt 30 13:06:43 media systemd[1]: systemd-logind.service: Failed with result 'start-limit'.
    Code:
    $ systemctl status -l wickedd-dhcp4.service
    ● wickedd-dhcp4.service - wicked DHCPv4 supplicant service
       Loaded: loaded (/usr/lib/systemd/system/wickedd-dhcp4.service; enabled; vendor preset: disabled)
       Active: failed (Result: timeout) since vr 2018-03-30 13:08:11 CEST; 10min ago
      Process: 1123 ExecStart=/usr/lib/wicked/bin/wickedd-dhcp4 --systemd --foreground (code=exited, status=0/SUCCESS)
     Main PID: 1123 (code=exited, status=0/SUCCESS)
    
    mrt 30 13:06:43 media wickedd-dhcp4[1123]: created /org/opensuse/Network/DHCP4/Interface as child of /org/opensuse/Network/DHCP4, class <anonymous>
    mrt 30 13:06:43 media wickedd-dhcp4[1123]: ni_dbus_server_register_object(path=Interface/2, handle=0x2455d20)
    mrt 30 13:06:43 media wickedd-dhcp4[1123]: created /org/opensuse/Network/DHCP4/Interface/2 as child of /org/opensuse/Network/DHCP4/Interface, class dhcp4-device
    mrt 30 13:06:43 media wickedd-dhcp4[1123]: ni_objectmodel_bind_compatible_interfaces(object=/org/opensuse/Network/DHCP4/Interface/2, class=dhcp4-device)
    mrt 30 13:06:43 media wickedd-dhcp4[1123]: Created dhcp4 device for 'eth0' and index 2
    mrt 30 13:06:43 media wickedd-dhcp4[1123]: Using netlink event receive buffer of 1048576 bytes
    mrt 30 13:08:11 media systemd[1]: wickedd-dhcp4.service: Start operation timed out. Terminating.
    mrt 30 13:08:11 media systemd[1]: Failed to start wicked DHCPv4 supplicant service.
    mrt 30 13:08:11 media systemd[1]: wickedd-dhcp4.service: Unit entered failed state.
    mrt 30 13:08:11 media systemd[1]: wickedd-dhcp4.service: Failed with result 'timeout'.
    Code:
    $ busctl --system
    Failed to connect to bus: No such file or directory
    Code:
    $ stat /run/dbus/system_bus_socket 
      Bestand: '/run/dbus/system_bus_socket'
      Grootte: 0            Blokken: 0            IO-blok: 4096   socket
    Apparaat: 13h/19d   Inode: 17821        Koppelingen: 1
    Toegang: (0666/srw-rw-rw-)   UID: (    0/    root)   GID: (    0/    root)
    Toegang:   2018-03-30 13:16:29.135403588 +0200
    Gewijzigd: 2018-03-30 13:06:41.018010577 +0200
    Veranderd: 2018-03-30 13:06:41.018010577 +0200
    Ontstaan:  -
    Code:
    $ lsof /run/dbus/system_bus_socket 
    COMMAND    PID       USER   FD   TYPE             DEVICE SIZE/OFF  NODE NAME
    systemd      1       root   28u  unix 0xffff8800a26eac00      0t0 17819 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus    3u  unix 0xffff8800a26eac00      0t0 17819 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus    9u  unix 0xffff8800a25ab000      0t0 20043 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   10u  unix 0xffff8800a26b7800      0t0 21952 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   11u  unix 0xffff8800a391bc00      0t0 21984 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   12u  unix 0xffff8800a301ec00      0t0 23285 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   13u  unix 0xffff88008cf4b400      0t0 23548 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   15u  unix 0xffff8800895f2c00      0t0 24465 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   16u  unix 0xffff8800a15fb000      0t0 41683 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   17u  unix 0xffff88008d03bc00      0t0 39933 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   18u  unix 0xffff8800a1c2f400      0t0 40965 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   19u  unix 0xffff88008d03b400      0t0 40968 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   20u  unix 0xffff88008d063000      0t0 40805 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   21u  unix 0xffff88008d075c00      0t0 41497 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   22u  unix 0xffff88008d1bec00      0t0 42066 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   23u  unix 0xffff8800a097f400      0t0 41669 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   24u  unix 0xffff88008cfd5c00      0t0 41676 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   25u  unix 0xffff880089094000      0t0 42278 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   26u  unix 0xffff88008d076400      0t0 42284 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   27u  unix 0xffff88008d06f400      0t0 42292 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   28u  unix 0xffff8800a15fb800      0t0 42294 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   31u  unix 0xffff88007d5c8c00      0t0 41913 /run/dbus/system_bus_socket type=STREAM
    dbus-daem 1117 messagebus   32u  unix 0xffff880089799800      0t0 41918 /run/dbus/system_bus_socket type=STREAM
    desktop.s 1637       boss    8u  unix 0xffff88008d035000      0t0 41542 /tmp/runtime-boss/kio_desktophX1637.1.slave-socket type=STREAM
    Hope someone can help me.
    Thanks in advange.

  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: systemd and DBus problem on fresh installed system

    First,
    I've found that there is little purpose to installing openSUSE without an active network connection. The network should be active whether wireless or wired and doesn't have to be connected to anything (eg Internet), otherwise the result is an installation that's more trouble than it's worth to configure networking later.

    Am not sure what your problem might be, only close inspection of your installation logs might reveal what happened.

    You can find your logs and more
    https://en.opensuse.org/openSUSE:Report_a_YaST_bug

    But,
    If you'd like to try installing again with a shotgun approach, "Enable online sources" will give you access to fixes, new features and additional options not in the originally published install media.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •