Why 'virt-manager' failed to launch with 'server ping error' in Red Hat Enterprise Linux 6.3?

Solution Unverified - Updated -

Environment

  • Red Hat Enterprise Linux 6.3

Issue

  • Getting Error while launching virt-manager:
 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: server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)
  • Detailed Error:
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: server ping error: IDL:omg.org/CORBA/COMM_FAILURE:1.0)

Resolution

1] Restart the messagebus service and access virtmanager:

   # service messagebus restart

2] Access virt-manager with command:

   # dbus-launch --exit-with-session virt-manager

Diagnostic Steps

  • Check uuid from server:
# dbus-uuidgen --get
# cat /var/lib/dbus/machine-id
  • Take backup of /var/lib/dbus/machine-id file.
  • If the outputs above are not same, recreate Fix:
dbus-uuidgen > /var/lib/dbus/machine-id

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.