Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)

CentOS 7 / CloudLinux 7 / RHEL 7 may show the following error while restarting Apache/Exim or similar apps:
Error getting authority: Error initializing authority: Could not connect: Connection refused (g-io-error-quark, 39)

Further track, can be found through journalctl:
journalctl -xb

shows

Dec 09 09:37:47 beret.ethii.com NetworkManager[629]: <warn> [1512790667.5892] bus-manager: could not create org.freedesktop.DBus proxy (Error calling StartServiceByName for org.freedesktop.DBus: The connection is closed); only the private D-Bus socket will be availableDec 09 09:37:47 beret.ethii.com NetworkManager[629]: Error while sending AddMatch() message: The connection is closed


It basically means your dbus service is off or inactive. You may start the dbus to resolve the error

systemctl start dbus.service
  • cloudlinux, centos 7, rhel 7, linux, dbus
  • 0 istifadəçi bunu faydalı hesab edir
Bu cavab sizə kömək etdi?

Uyğun məqalələr

R1soft Backup Error - Failed To Backup LVM/MD Configuration

It looks like R1Soft manages it's own lvm.static file to process lvm backups. But sometimes it...

Does R1Soft work with LVM?

It does. But it is not fully supported as of 28th November, 2017. If you have a solid logical...

[957833.048873] EXT4-fs warning (device dm-0): ext4_dx_add_entry:2016: Directory index full!

A dedicated server customer came with an error of failed WHM login. When I tried to enter, I...

lfd on ***.***.***: ModSecurity persistent IP database size alert

LFD was throwing the following error for sometime in a server: ModSecurity persistent IP...

Fatal error: Uncaught exception 'Google_IO_Exception' with message 'Couldn't resolve host 'accounts.google.com''

Sometimes, Google library can return the following error: Fatal error: Uncaught exception...