Re: Re: Timeout connecting to device

[Christian Limpach <christian.limpach@gmail.com>]

On 8/24/05, Rusty Russell <rusty@rustcorp.com.au> 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.

    christian