RHEL7: after updating dbus from dbus-1.6.12 to dbus-1.10.24, the system is broken, messages such as "Lost the name org.freedesktop.PolicyKit1 - exiting" are seen in the journal

Solution Verified - Updated -

Issue

  • busctl command throws the following error message

    # busctl
    Failed to connect to bus: Connection refused
    

    Note: in some situations, you may see a No such file or directory error message instead of Connection refused.

  • polkit.service unit is not running and status shows the following message

    # systemctl status polkit.service
    ● polkit.service - Authorization Manager
       Loaded: loaded (/usr/lib/systemd/system/polkit.service; static; vendor preset: enabled)
       Active: inactive (dead) since Mon 2019-06-03 11:35:21 CEST; 21min ago
    [...]
    [...] polkitd[638]: Loading rules from directory /etc/polkit-1/rules.d
    [...] polkitd[638]: Loading rules from directory /usr/share/polkit-1/rules.d
    [...] polkitd[638]: Finished loading, compiling and executing 2 rules
    [...] polkitd[638]: Lost the name org.freedesktop.PolicyKit1 - exiting
    
  • NetworkManager.service unit is in activating state instead of active state

    # systemctl status NetworkManager
    ● NetworkManager.service - Network Manager
       Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
       Active: activating (start) since Mon 2019-06-03 11:53:26 CEST; 1min 3s ago
    [...]
    
    # systemctl list-jobs
     JOB UNIT                   TYPE  STATE  
    1791 NetworkManager.service start running
    
  • systemd-login.service unit is failing continuously

    # systemctl status systemd-logind
    ● systemd-logind.service - Login Service
       Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled)
       Active: failed (Result: start-limit) since Mon 2019-06-03 11:35:21 CEST; 21min ago
    [...]
    [...] systemd[1]: start request repeated too quickly for systemd-logind.service
    [...] systemd[1]: Failed to start Login Service.
    [...] systemd[1]: Unit systemd-logind.service entered failed state.
    [...] systemd[1]: systemd-logind.service failed.
    
  • The journal since boot shows various error messages related to dbus (excerpts, messages repeated multiple times)

    # journalctl -b -p err
    systemd-logind[640]: Failed to connect to system bus: Connection refused
    systemd-logind[640]: Failed to fully start up daemon: Connection refused
    login[671]: pam_systemd(login:session): Failed to connect to system bus: Connection refused
    NetworkManager[835]: <error> [1559554611.6628] dispatcher: could not get dispatcher proxy! Could not connect: Connection refused
    NetworkManager[835]: <error> [1559554611.6856] auth: could not get polkit proxy: Could not connect: Connection refused
    

    Note: in some situations, you may see No such file or directory error messages instead of Connection refused.

Environment

  • Red Hat Enterprise Linux 7
    • dbus-1.10.24

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In