virt-manager failed to connect to socket /tmp/dbus -error.
Detailed Error:
Error starting Virtual Machine Manager: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-H3dWpSBlXJ: Connection refused)
Traceback (most recent call last):
File "/usr/share/virt-manager/virt-manager.py", line 383, in <module>
main()
File "/usr/share/virt-manager/virt-manager.py", line 315, in main
config = virtManager.config.vmmConfig(appname, appversion, glade_dir)
File "/usr/share/virt-manager/virtManager/config.py", line 98, in __init__
self.conf.add_dir(self.conf_dir, gconf.CLIENT_PRELOAD_NONE)
GError: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details - 1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-H3dWpSBlXJ: Connection refused)
X-Server: Xming running on Windows7, virt-manager started via SSH Connection. (Putty X11 tunnel enabled)
Eventhough it shows correct uuid:
[root@NTNX-12AM2K480036-D ~]# dbus-uuidgen --get
cd36ef14c5f40ace93f5e0ed0000001a
[root@NTNX-12AM2K480036-D ~]# cat /var/lib/dbus/machine-id
cd36ef14c5f40ace93f5e0ed0000001a
Fix: dbus-uuidgen > /var/lib/dbus/machine-id - recreate it
and then start the virt-manager.
https://bugzilla.redhat.com/show_bug.cgi?id=598200
More details.
Nice article ! your solution works... how do u achive it ?
ReplyDeleteOr, rather than launching virt-manager as root from the su'd shell, go back to a shell under your own user ID, launch virt-manager from there, and enter the root PW when prompted... Since the gnome session was started under your own account, launching a gnome tool (at least in this case) as root doesn't find the correct gnome instance.
ReplyDeleteI also found I could launch as: dbus-launch --exit-with-session virt-manager which was a clue to. I restarted both messagebus and livirtd which did not make this issue go away but ultimately after deleting an instance which looked corrupted from the libvirt logs(IO errors) I could then launch normally again(virt-manager).
ReplyDelete