Re: Re: Timeout connecting to device

[Rusty Russell <rusty@rustcorp.com.au>]

On Tue, 2005-08-23 at 18:36 -0700, Arun Sharma wrote:
>  > XENBUS xs_read_watch: 0

This is harmless, in fact expected.  It's a debugging message which
should go away...

> # find . -name *end
> ./a9b503a7-2494-409f-9e06-2bd1f9283953/device/vbd/768/backend
> ./45194ebb-4029-4131-9013-d17cd3dbc828/device/vbd/768/backend
> ./53ffa08b-5f90-45a4-9671-8d6fff7f8509/backend
> ./53ffa08b-5f90-45a4-9671-8d6fff7f8509/backend/vbd/a9b503a7-2494-409f-9e06-2bd1f9283953/768/frontend
> ./53ffa08b-5f90-45a4-9671-8d6fff7f8509/backend/vbd/45194ebb-4029-4131-9013-d17cd3dbc828/768/frontend
> 
> Couple of questions:
> 
> - 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.

Grovelling around the store by looking in /var/lib/xenstored/store is
pretty simple, as you have found, but I know there were a few efforts to
have a nicer browser...

> - 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).

Cheers,
Rusty.
-- 
A bad analogy is like a leaky screwdriver -- Richard Braakman