Jenna,
Probably it's caused by the problem fixed in  http://gerrit.ovirt.org/#change,216  You could have a try.


On 12/13/2011 02:16 PM, Jenna Johnson wrote:
Guys,

   Installed most recent vdsmd and vdsclient on rehl 6.2.Could anybody help to take a look?

   After installation, vdsmd can't open connection with libvirt:
  MainThread::INFO::2011-12-13 09:41:17,667::vdsm::76::vds::(run) VDSM main thread ended. Waiting for 1 other threads...
MainThread::INFO::2011-12-13 09:41:17,667::vdsm::79::vds::(run) <_MainThread(MainThread, started 140169981224704)>
MainThread::INFO::2011-12-13 09:41:17,667::vdsm::79::vds::(run) <Thread(libvirtEventLoop, started daemon 140169902909184)>
MainThread::INFO::2011-12-13 09:41:17,715::vdsm::71::vds::(run) I am the actual vdsm 4.9-0
MainThread::ERROR::2011-12-13 09:41:17,881::vdsm::74::vds::(run) Traceback (most recent call last):
  File "/usr/share/vdsm/vdsm", line 72, in run
    serve_clients(log)
  File "/usr/share/vdsm/vdsm", line 40, in serve_clients
    cif = clientIF.clientIF(log)
  File "/usr/share/vdsm/clientIF.py", line 113, in __init__
    self._libvirt = libvirtconnection.get()
  File "/usr/share/vdsm/libvirtconnection.py", line 111, in get
    conn = libvirt.openAuth('qemu:///system', auth, 0

for libvirt client trace:
09:41:20.182: 11842: debug : doRemoteOpen:511 : proceeding with name = qemu:///system
09:41:20.182: 11842: debug : doRemoteOpen:521 : Connecting with transport 1
09:41:20.182: 11842: debug : doRemoteOpen:568 : Proceeding with sockname /var/run/libvirt/libvirt-sock
09:41:20.182: 11842: debug : doRemoteOpen:648 : Trying authentication
09:41:20.183: 11842: debug : remoteAuthSASL:2618 : Client initialize SASL authentication
09:41:20.185: 11842: debug : remoteAuthSASL:2680 : Client start negotiation mechlist 'DIGEST-MD5'
09:41:20.185: 11842: debug : remoteAuthSASL:2730 : Server start negotiation with mech DIGEST-MD5. Data 0 bytes (nil)
09:41:20.185: 11842: debug : remoteAuthSASL:2744 : Client step result complete: 0. Data 129 bytes 0x1fa7650
09:41:20.185: 11842: debug : remoteAuthSASL:2787 : Client step result 1. Data 255 bytes 0x204eaa0
09:41:20.185: 11842: debug : remoteAuthSASL:2800 : Server step with 255 bytes 0x204eaa0
09:41:20.186: 11842: error : virNetClientProgramDispatchError:170 : authentication failed: authentication failed
09:41:20.186: 11842: debug : do_open:1062 : driver 2 remote returned ERROR

libvirtd trace:
13:55:36.455: 2213: error : remoteDispatchAuthSaslStep:2107 : authentication failed: authentication failed
13:55:36.477: 2208: error : virNetSocketReadWire:911 : End of file while reading data: Input/output error
13:55:36.664: 2212: error : virNetSASLSessionServerStep:624 : authentication failed: Failed to start SASL negotiation: -13 (SASL(-13): authentication failure: client response doesn't match what we generated)

checked sasdblist:
sasldblistusers2,see vdsm

libvirtd.conf:
listen_addr="0" # by vdsm
unix_sock_group="kvm" # by vdsm
unix_sock_rw_perms="0770" # by vdsm
auth_unix_rw="sasl" # by vdsm
save_image_format="lzop" # by vdsm
log_outputs="1:file:/var/log/libvirtd.log" # by vdsm
log_filters="1:libvirt 3:event 3:json 1:util 1:qemu" # by vdsm
auth_tcp="none" # by vdsm
listen_tcp=1 # by vdsm
listen_tls=0 # by vdsm


_______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel