Why dbus-broker failed to start and throws the error Invalid XML in /etc/dbus-1/system.d/org.fedoraproject.Setroubleshootd.conf +1: no element found?

Solution Verified - Updated -

Issue

  • dbus-broker failed to start after leapp upgrade and giving the below error

    Aug 13 15:14:56 localhost.localdomain dbus-broker-launch[11170]: Invalid XML in /etc/dbus-1/system.d/org.fedoraproject.Setroubleshootd.conf +1: no element found
Aug 13 15:14:56 localhost.localdomain dbus-broker-launch[11170]: ERROR run @ ../src/launch/main.c +152: Return code 1
Aug 13 15:14:56 localhost.localdomain dbus-broker-launch[11170]:       main @ ../src/launch/main.c +178
Aug 13 15:14:56 localhost.localdomain dbus-broker-launch[11170]: Exiting due to fatal error: -131
Aug 13 15:14:56 localhost.localdomain systemd[1]: dbus-broker.service: Main process exited, code=exited,   status=1/FAILURE

  • Network was not working, and unable to implement the ssh connection.

Environment

  • Red Hat Enterprise Linux 9 and above

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