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] xend "invalid token" error

To: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xend "invalid token" error
From: Jon Mason <jdmason@xxxxxxxxxx>
Date: Mon, 10 Oct 2005 18:16:33 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 10 Oct 2005 23:15:06 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20051010224931.GC6264@xxxxxxxxxxxxx>
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>
Mail-followup-to: Ewan Mellor <ewan@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
References: <20051010205020.GA10245@xxxxxxxxxx> <20051010224931.GC6264@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.8i
On Mon, Oct 10, 2005 at 11:49:31PM +0100, Ewan Mellor wrote:
> On Mon, Oct 10, 2005 at 03:50:21PM -0500, Jon Mason wrote:
> > I am geting the following error when I start xend on x86 and amd64
> > # /etc/init.d/xend start
> > invalid token
> > Exception in thread Watcher:Traceback (most recent call last):
> >    File "/usr/lib/python2.3/threading.py", line 442, in __bootstrap
> >      self.run()
> >    File "/usr/lib/python2.3/threading.py", line 422, in run
> >      self.__target(*self.__args, **self.__kwargs)
> >    File "/usr/lib/python/xen/xend/xenstore/xswatch.py", line 43, in 
> > watchMain
> >      we = cls.xs.read_watch()
> >  RuntimeError: invalid token
> I thought this had been fixed by changeset 7289:5134f3c512c8.  Could you
> confirm?
I did a mercurial pull 10 minutes ago, and I am still seeing the error.
Also, I am seeing this on python 2.4.


Xen-devel mailing list