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/
Home Products Support Community News


Re: [Xen-devel] Re: Timeout connecting to device

To: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Timeout connecting to device
From: Christian Limpach <christian.limpach@xxxxxxxxx>
Date: Wed, 24 Aug 2005 09:25:18 +0100
Cc: Arun Sharma <arun.sharma@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 24 Aug 2005 08:23:30 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=r+S374ez0Dqn55fTmQvdFWPb/HuVZZPu/nENPxOHx/n2R6/MIlwyuOgZqnE5KCwo3FnDgahb9hQ98qZoL14vwBzEWudWFsBUnfYTKZUmcXvI7egfdgp6grrvTLMJXzCKnG1jF5qdGL8OyFgzsWOjEdolubGiuoLNQ9bjNx5uTmw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1124858620.17004.96.camel@xxxxxxxxxxxxxxxxxxxxx>
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>
References: <430A387C.2030108@xxxxxxxxx> <430BCF14.2040409@xxxxxxxxx> <1124858620.17004.96.camel@xxxxxxxxxxxxxxxxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 8/24/05, Rusty Russell <rusty@xxxxxxxxxxxxxxx> wrote:
> > - is there a way to debug xenstored? It doesn't seem to be logging much.
> Yes, add --trace-file=/tmp/trace to the invocation of xenstored, and
> you'll see all the conversations that the store has.

You can set XENSTORED_TRACE in /usr/sbin/xend's environment causing it
to add the --trace-file option to the invocation of xenstored.  You'll
need to do this in your boot script because after restarting
xenstored, the backends won't notice any new changes anymore.

> > - Could we add some debug flags elsewhere as well (xenbus with debug=1?)
> > to make debugging problems of this nature easier?
> The trace file is actually better in my experience.  Also look for
> "error" nodes in the store (although Christian removed some of those
> paths in the merge).

I only removed the ones which were not fatal because I was under the
impression initally that adding an error node does indicate a final
error after which it would be up to a control tool to sort out the
failure or report it.


Xen-devel mailing list