"Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)" after yum update.

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux 7.

Issue

  • Restarting any service report error Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39).

Resolution

  • These steps should be done using Rescue mode after chroot.
  • Create the symbolic link as /var is on separate partition.

# mv -f /var/run /var/run.runmove~
# ln -sfn /run /var/run
# mv -f /var/lock /var/lock.lockmove~
# ln -sfn /run/lock /var/lock
  • Reboot the system.

Root Cause

  • The system has separate /var file system on a separate partition.

Diagnostic Steps

# systemctl stop rsyslog
Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)
Failed to stop rsyslog.service: Unit rsyslog.service not loaded.

# systemctl enable syslog-ng
Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments