[Ovirt-devel] error with gssapi

dima vasiletc pronix.service at gmail.com
Wed Jul 1 10:51:42 UTC 2009


Hello
i set for root rsa key and login in second node.
this is error appear after run "libvirt-qpid --broker 
main.forex-24h.com" on second node

2009-jul-01 10:41:38 info QMF Agent Initialized: 
broker=main.forex-24h.com:5672 interval=3 storeFile=
2009-jul-01 10:41:39 debug QMF Agent attempting to connect to the broker...
2009-jul-01 10:41:39 debug ConnectionImpl created for \x00-

2009-jul-01 10:41:39 info Connecting to tcp:main.forex-24h.com:5672
2009-jul-01 10:41:39 debug TCPConnector created for \x00-

2009-jul-01 10:41:39 debug RECV [37926 main.forex-24h.com:5672] INIT(0-10)
2009-jul-01 10:41:39 trace RECV [37926 main.forex-24h.com:5672]: 
Frame[BEbe; channel=0; {ConnectionStartBody: 
server-properties={qpid.federation_tag:V2:36:str16(9b4534b8-ec7a-489c-97aa-8c39a0af5b4f)}; 
mechanisms=str16{V2:0:str16()}; locales=str16{V2:5:str16(en_US)}; }]
2009-jul-01 10:41:39 debug CyrusSasl::start()
2009-jul-01 10:41:39 debug min_ssf: 0, max_ssf: 256
2009-jul-01 10:41:39 debug Exception constructed: Sasl error: SASL(-4): 
no mechanism available: No worthy mechs found 
(qpid/client/SaslFactory.cpp:226)
2009-jul-01 10:41:39 warning Closing connection due to internal-error: 
Sasl error: SASL(-4): no mechanism available: No worthy mechs found 
(qpid/client/SaslFactory.cpp:226)
2009-jul-01 10:41:39 trace SENT [37926 main.forex-24h.com:5672]: 
Frame[BEbe; channel=0; {ConnectionCloseBody: reply-code=501; 
reply-text=internal-error: Sasl error: SASL(-4): no mechanism available: 
No worthy mechs found (qpid/client/SaslFactory.cpp:226); }]
2009-jul-01 10:41:39 trace RECV [37926 main.forex-24h.com:5672]: 
Frame[BEbe; channel=0; {ConnectionCloseOkBody: }]
2009-jul-01 10:41:39 debug Exception constructed: internal-error: Sasl 
error: SASL(-4): no mechanism available: No worthy mechs found 
(qpid/client/SaslFactory.cpp:226)
2009-jul-01 10:41:39 debug Exception constructed: internal-error: Sasl 
error: SASL(-4): no mechanism available: No worthy mechs found 
(qpid/client/SaslFactory.cpp:226)
2009-jul-01 10:41:39 debug Connection failed: exception=internal-error: 
Sasl error: SASL(-4): no mechanism available: No worthy mechs found 
(qpid/client/SaslFactory.cpp:226)


also i check this list

    * Networking issues prevent node from communicating properly with
      server. (Ok, i connect using ssh)
    * DNS configuration issues prevent getting DNS SRV records for
      various services. (Ok, all querys resolved correct)
    * DNS configuration issues cause kerberos authentication to
      fail.(not know how to check)
    * Time skew causes kerberos authentication to fail.(kinit admin on
      second node work correct)
    * Time skew causes timestamps from node sent to WUI to seem to be
      out of date and so get marked as unavailable (no recent
      keepalive). (time on both servers are similar)

What i must check else ?



On 06/25/2009 09:50 PM, Ian Main wrote:
> On Thu, 25 Jun 2009 13:56:24 +0400
> dima vasiletc<pronix.service at gmail.com>  wrote:
>
>    
>> Hello
>> I found on ovirt.org instruction for set unavailable(enable) to
>> available(enable)
>> i run "ruby /usr/share/ovirt-server/qmf-libvirt-example.rb"
>> and get
>>
>> Error caching credentials; attempting to continue...
>> Connecting to amqp://main.forex-24h.com:5672..
>> /usr/lib/ruby/site_ruby/1.8/qpid/delegates.rb:209:in
>> `connection_start'/usr/lib/ruby/site_ruby/1.8/qpid/delegates.rb:209:
>> [BUG] Segmentation fault
>> ruby 1.8.6 (2008-08-11) [x86_64-linux]
>>      
>
> qmf-libvirt-example has to access the ovirt qpid kerberos ticket in order
> to connect to qpidd.  In order to that it has to be run as root.
>
> If everything else is working (looks like it is) then that should fix it.
>
>      Ian
>
> _______________________________________________
> Ovirt-devel mailing list
> Ovirt-devel at redhat.com
> https://www.redhat.com/mailman/listinfo/ovirt-devel
>
>    


-- 
? ?????????, ???????

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20090701/74e687de/attachment.htm>


More information about the ovirt-devel mailing list