NetworkManager.service failed to start post reboot due to dbus-broker.service failure

Solution Verified - Updated -

Issue

  • After the reboot, access to network resources is unavailable.
  • The status indicates that the NetworkManager service has failed to start due to a dependency issue.
  • After rebooting the server, the NetworkManager service fails to start, resulting in the server being unable to connect to the network. The error message indicates a "Dependency failed for Network Manager".

    Nov 04 16:19:03 rhelserver systemd[1]: Dependency failed for Network Manager.
    Nov 04 16:19:03 rhelserver systemd[1]: NetworkManager.service: Job NetworkManager.service/start failed with result 'dependency'.
    
    Nov 04 16:39:43 rhelserver dbus-broker-launch[9004]: Missing configuration file in /etc/selinux/targeted/contexts/dbus_contexts +1: /etc/selinux/targeted/contexts/dbus_contexts
    Nov 04 16:39:43 rhelserver dbus-broker-launch[9004]: ERROR run @ ../src/launch/main.c +152: Return code 1
    Nov 04 16:39:43 rhelserver dbus-broker-launch[9004]:       main @ ../src/launch/main.c +178
    Nov 04 16:39:43 rhelserver dbus-broker-launch[9004]: Exiting due to fatal error: -131
    Nov 04 16:39:43 rhelserver systemd[1]: dbus-broker.service: Main process exited, code=exited, status=1/FAILURE
    

Environment

  • Red Hat Enterprise Linux 9
    • NetworkManager
    • dbus-broker

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content