WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Bug: xm commands hanging due to poor threading in xend

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Bug: xm commands hanging due to poor threading in xend
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sun, 22 Jan 2006 11:05:20 +1100
Delivery-date: Sun, 22 Jan 2006 00:13:33 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcYev6sWzLsWgQluTJOUzu+/+fOTxQAJ5rIg
Thread-topic: [Xen-devel] Bug: xm commands hanging due to poor threading in xend
FWIW, I had a xend crash in -testing where I issued two 'xm create'
commands for two different domains in quick succession, eg at the same
command prompt typing the second one as soon as the first had finished.

I was in a bit of a hurry to get the domains running again so I wasn't
in a position to take any debug information.

James

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Matt Ayres
> Sent: Sunday, 22 January 2006 06:19
> To: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-devel] Bug: xm commands hanging due to poor threading in
> xend
> 
> I have noticed my most major issue with putting xend into full
> production is with many xm commands being issued it hangs and only
> starts working (sometimes) after a "service xend restart".  I created
a
> bug a long time for this and have attached 3 different sets of logs
> using xen-bugtool.  This happens to most servers after running for 3-4
> days.  Those that have little activity on the xend daemon (older
servers
> that were upgraded) can go 2 weeks+ at this point.  Once Xen gets to
> this state even restarting xend so the list command (and others) work,
> running "xm shutdown -a"  will guarantee an internal server error from
> xend.
> 
> I've also run into this once:
> 
> Message from syslogd@vm20 at Fri Jan 20 23:16:52 2006 ...
> vm20 xenstored: xenstored corruption: connection id -1: err No such
file
> or directory: No child '(null)' found
> Error: Error connecting to xend: Connection refused.  Is xend running?
> 
> This is all using -unstable.  There are not many commits to
3.0-testing
> specifically regarding xend/tdb/xenstore so tracking it at this point
> seems useless.
> 
> Bug url: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=465
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel