Re: [Xen-API] XCP 1.6 VM.get_all_records API Call hanging

[2rushikeshj@xxxxxxxxx]

On Thu, 3 Jan 2013 16:44:14 +0550, xen-api-bounces@xxxxxxxxxxxxx wrote:
> All,
> 
> I have been playing with Xen Cloud Platform 1.6 in the lab and have been 
> noticing some strange behaviour when using the API to drive it. Using 
> XenCenter worked some of the time but then appeared to freeze, not refresh 
> and then on re-connecting get stuck on "Synchronising". I put this down to 
> the client software and switched instead to writing my own client interface 
> using Ruby and the FOG libraries. This worked well but I started seeing the 
> same lock-ups. After digging about I realised that it always locks up at the 
> same point namely the VM.get_all_records call.
> 
> The call is received as the xensource.log shows:
> 
> xapi: [debug|xcp-test2|105923 INET 0.0.0.0:80|dispatch:VM.get_all_records 
> D:7f14fc2bea45|api_readonly] VM.get_all_records
> 
> But nothing is received and the clients TCP connection times out.
> 
> This problem happens for well over 50% of the calls made to the API so I am 
> interested to know if anyone else is having this problem?
> 

Your Cluster Host Count and VM count ( ON & OFF ) will be  helpful.

Usual errors are to be checked in xensource.log, messages, kern.log

Try to get only list of VM ids and then do a get_record for each VM to see if 
you get caught in same problem



> Regards,
> 
> Dave-- 
> Future Publishing Limited (registered company number 2008885) is a wholly 
> owned subsidiary of Future plc (registered company number 3757874), both of 
> which are incorporated in England and Wales and share the same registered 
> address at Beauford Court, 30 Monmouth Street, Bath BA1 2BW.
> 
> This email and any files transmitted with it are confidential and intended 
> solely for the use of the individual or entity to which they are addressed. 
> If you have received this email in error please reply to this email and then 
> delete it. Please note that any views or opinions presented in this email are 
> solely those of the author and do not necessarily represent those of Future.
> 
> The recipient should check this email and any attachments for the presence of 
> viruses. Future accepts no liability for any damage caused by any virus 
> transmitted by this email.
> 
> Future may regularly and randomly monitor outgoing and incoming emails and 
> other telecommunications on its email and telecommunications systems. By 
> replying to this email you give your consent to such monitoring.
> 
> *****
> Save resources: think before you print.
> 
> 
> _______________________________________________
> Xen-api mailing list
> Xen-api@xxxxxxxxxxxxx
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api


_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api