xm list error changeset:6796

xm list error changeset:6796

[Ted Kaczmarek]

FC4, tyan 2462 SMP Athlon, 2 gig, appears that xend toasts, I noticed
that purging /var/lib/xenstored/store/domain/ appears to allow xend to
restart after this type pf error.

The problem mostly occurs after issuing an xm shutdowm to a DomU.

Unexpected error: xen.xend.XendProtocol.XendError

Please report to xen-devel@lists.xensource.com
Traceback (most recent call last):
  File "/usr/sbin/xm", line 10, in ?
    main.main(sys.argv)
  File
"/usr/src/redhat/SOURCES/xen-unstable/dist/install/usr/lib/python/xen/xm/main.py", line 710, in main
    rc = cmd(args)
  File
"/usr/src/redhat/SOURCES/xen-unstable/dist/install/usr/lib/python/xen/xm/main.py", line 231, in xm_list
    info = server.xend_domain(dom)
  File
"/usr/src/redhat/SOURCES/xen-unstable/dist/install/usr/lib/python/xen/xend/XendClient.py", line 217, in xend_domain
    return self.xendGet(self.domainurl(id))
  File
"/usr/src/redhat/SOURCES/xen-unstable/dist/install/usr/lib/python/xen/xend/XendClient.py", line 152, in xendGet
    return self.client.xendGet(url, args)
  File
"/usr/src/redhat/SOURCES/xen-unstable/dist/install/usr/lib/python/xen/xend/XendProtocol.py", line 86, in xendGet
    return self.xendRequest(url, "GET", args)
  File
"/usr/src/redhat/SOURCES/xen-unstable/dist/install/usr/lib/python/xen/xend/XendProtocol.py", line 170, in xendRequest
    val = self.handleStatus(resp.version, resp.status, resp.reason)
  File
"/usr/src/redhat/SOURCES/xen-unstable/dist/install/usr/lib/python/xen/xend/XendProtocol.py", line 106, in handleStatus
    return self.handleException(XendError(message))
  File
"/usr/src/redhat/SOURCES/xen-unstable/dist/install/usr/lib/python/xen/xend/XendProtocol.py", line 132, in handleExcepti on
    raise err
xen.xend.XendProtocol.XendError: Internal server error

Regards,
Ted

Re: xm list error changeset:6796

[Steven Hand]

>FC4, tyan 2462 SMP Athlon, 2 gig, appears that xend toasts, I noticed
>that purging /var/lib/xenstored/store/domain/ appears to allow xend to
>restart after this type pf error.
>
>The problem mostly occurs after issuing an xm shutdowm to a DomU.

Can you check if it's been fixed by cset 6828? 

cheers,

S.

Re: xm list error changeset:6796

[Ted Kaczmarek]

On Wed, 2005-09-14 at 23:38 +0100, Steven Hand wrote:
> >FC4, tyan 2462 SMP Athlon, 2 gig, appears that xend toasts, I noticed
> >that purging /var/lib/xenstored/store/domain/ appears to allow xend to
> >restart after this type pf error.
> >
> >The problem mostly occurs after issuing an xm shutdowm to a DomU.
> 
> Can you check if it's been fixed by cset 6828? 
> 
> cheers,
> 
> S.
Sure as soon as it is in the unstable tar ball. Might be helpful to
stuff the changeset into the tarballs name also for us non mercurial
literate users :-)


Regards,
Ted

Re: xm list error changeset:6796

[Ted Kaczmarek]

On Wed, 2005-09-14 at 23:38 +0100, Steven Hand wrote:
> >FC4, tyan 2462 SMP Athlon, 2 gig, appears that xend toasts, I noticed
> >that purging /var/lib/xenstored/store/domain/ appears to allow xend to
> >restart after this type pf error.
> >
> >The problem mostly occurs after issuing an xm shutdowm to a DomU.
> 
> Can you check if it's been fixed by cset 6828? 
> 
> cheers,
> 
> S.

xm list is definetly behaving better, xm destroy is still having issues.

The best test for xm destroy in my case is to try to start a domain that
is unable to mount root filesystem, once that happens the only way to
get rid of that domain is to kill xend and purge the files. Doing an xm
list shows the domain crashed. Will start a new thread on this.

Regards,
Ted

Re: xm list error changeset:6796

[Sean Dague]

[-- Attachment #1.1: Type: text/plain, Size: 1428 bytes --]

On Thu, Sep 15, 2005 at 08:34:45AM -0400, Ted Kaczmarek wrote:
> On Wed, 2005-09-14 at 23:38 +0100, Steven Hand wrote:
> > >FC4, tyan 2462 SMP Athlon, 2 gig, appears that xend toasts, I noticed
> > >that purging /var/lib/xenstored/store/domain/ appears to allow xend to
> > >restart after this type pf error.
> > >
> > >The problem mostly occurs after issuing an xm shutdowm to a DomU.
> > 
> > Can you check if it's been fixed by cset 6828? 
> > 
> > cheers,
> > 
> > S.
> 
> xm list is definetly behaving better, xm destroy is still having issues.
> 
> The best test for xm destroy in my case is to try to start a domain that
> is unable to mount root filesystem, once that happens the only way to
> get rid of that domain is to kill xend and purge the files. Doing an xm
> list shows the domain crashed. Will start a new thread on this.

Dan Smith, can you create a test case for xm-test for that condition?

	-Sean

-- 
__________________________________________________________________

Sean Dague                                       Mid-Hudson Valley
sean at dague dot net                            Linux Users Group
http://dague.net                                 http://mhvlug.org

There is no silver bullet.  Plus, werewolves make better neighbors
than zombies, and they tend to keep the vampire population down.
__________________________________________________________________

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

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

Re: xm list error changeset:6796

[Ted Kaczmarek]

On Thu, 2005-09-15 at 08:34 -0400, Ted Kaczmarek wrote:
> On Wed, 2005-09-14 at 23:38 +0100, Steven Hand wrote:
> > >FC4, tyan 2462 SMP Athlon, 2 gig, appears that xend toasts, I noticed
> > >that purging /var/lib/xenstored/store/domain/ appears to allow xend to
> > >restart after this type pf error.
> > >
> > >The problem mostly occurs after issuing an xm shutdowm to a DomU.
> > 
> > Can you check if it's been fixed by cset 6828? 
> > 
> > cheers,
> > 
> > S.
> 
> xm list is definetly behaving better, xm destroy is still having issues.
> 
> The best test for xm destroy in my case is to try to start a domain that
> is unable to mount root filesystem, once that happens the only way to
> get rid of that domain is to kill xend and purge the files. Doing an xm
> list shows the domain crashed. Will start a new thread on this.
> 
> Regards,
> Ted
Got xm list to poop again, with changeset  6831
Had four Domu's going, from 4th domu terminal issued a reboot, after
that.
[root@inyoureyes ~]# xm list
Unexpected error: xen.xend.XendProtocol.XendError

Please report to xen-devel@lists.xensource.com
Traceback (most recent call last):
  File "/usr/sbin/xm", line 10, in ?
    main.main(sys.argv)
  File "/usr/lib/python/xen/xm/main.py", line 717, in main
    rc = cmd(args)
  File "/usr/lib/python/xen/xm/main.py", line 230, in xm_list
    info = server.xend_domain(dom)
  File "/usr/lib/python/xen/xend/XendClient.py", line 217, in
xend_domain
    return self.xendGet(self.domainurl(id))
  File "/usr/lib/python/xen/xend/XendClient.py", line 152, in xendGet
    return self.client.xendGet(url, args)
  File "/usr/lib/python/xen/xend/XendProtocol.py", line 86, in xendGet
    return self.xendRequest(url, "GET", args)
  File "/usr/lib/python/xen/xend/XendProtocol.py", line 170, in
xendRequest
    val = self.handleStatus(resp.version, resp.status, resp.reason)
  File "/usr/lib/python/xen/xend/XendProtocol.py", line 106, in
handleStatus
    return self.handleException(XendError(message))
  File "/usr/lib/python/xen/xend/XendProtocol.py", line 132, in
handleException
    raise err
xen.xend.XendProtocol.XendError: Internal server error

Also the mailing lists seem to be having issues most of the day.

Regards,
Ted

Re: xm list error changeset:6796

[David F Barrera]

On Thu, 2005-09-15 at 12:00 -0400, Ted Kaczmarek wrote:
> On Thu, 2005-09-15 at 08:34 -0400, Ted Kaczmarek wrote:
> > On Wed, 2005-09-14 at 23:38 +0100, Steven Hand wrote:
> > > >FC4, tyan 2462 SMP Athlon, 2 gig, appears that xend toasts, I noticed
> > > >that purging /var/lib/xenstored/store/domain/ appears to allow xend to
> > > >restart after this type pf error.
> > > >
> > > >The problem mostly occurs after issuing an xm shutdowm to a DomU.
> > > 
> > > Can you check if it's been fixed by cset 6828? 
> > > 
> > > cheers,
> > > 
> > > S.
> > 
> > xm list is definetly behaving better, xm destroy is still having issues.
> > 
> > The best test for xm destroy in my case is to try to start a domain that
> > is unable to mount root filesystem, once that happens the only way to
> > get rid of that domain is to kill xend and purge the files. Doing an xm
> > list shows the domain crashed. Will start a new thread on this.
> > 
> > Regards,
> > Ted
> Got xm list to poop again, with changeset  6831
> Had four Domu's going, from 4th domu terminal issued a reboot, after
> that.
> [root@inyoureyes ~]# xm list
> Unexpected error: xen.xend.XendProtocol.XendError
> 
> Please report to xen-devel@lists.xensource.com
> Traceback (most recent call last):
>   File "/usr/sbin/xm", line 10, in ?
>     main.main(sys.argv)
>   File "/usr/lib/python/xen/xm/main.py", line 717, in main
>     rc = cmd(args)
>   File "/usr/lib/python/xen/xm/main.py", line 230, in xm_list
>     info = server.xend_domain(dom)
>   File "/usr/lib/python/xen/xend/XendClient.py", line 217, in
> xend_domain
>     return self.xendGet(self.domainurl(id))
>   File "/usr/lib/python/xen/xend/XendClient.py", line 152, in xendGet
>     return self.client.xendGet(url, args)
>   File "/usr/lib/python/xen/xend/XendProtocol.py", line 86, in xendGet
>     return self.xendRequest(url, "GET", args)
>   File "/usr/lib/python/xen/xend/XendProtocol.py", line 170, in
> xendRequest
>     val = self.handleStatus(resp.version, resp.status, resp.reason)
>   File "/usr/lib/python/xen/xend/XendProtocol.py", line 106, in
> handleStatus
>     return self.handleException(XendError(message))
>   File "/usr/lib/python/xen/xend/XendProtocol.py", line 132, in
> handleException
>     raise err
> xen.xend.XendProtocol.XendError: Internal server error

Yeah, we are seeing that, too.
> 
> Also the mailing lists seem to be having issues most of the day.
> 
> Regards,
> Ted
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
> 
-- 
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                        Euripides

Re: xm list error changeset:6796

[Ted Kaczmarek]

On Thu, 2005-09-15 at 10:22 -0400, Sean Dague wrote:
> On Thu, Sep 15, 2005 at 08:34:45AM -0400, Ted Kaczmarek wrote:
> > On Wed, 2005-09-14 at 23:38 +0100, Steven Hand wrote:
> > > >FC4, tyan 2462 SMP Athlon, 2 gig, appears that xend toasts, I noticed
> > > >that purging /var/lib/xenstored/store/domain/ appears to allow xend to
> > > >restart after this type pf error.
> > > >
> > > >The problem mostly occurs after issuing an xm shutdowm to a DomU.
> > > 
> > > Can you check if it's been fixed by cset 6828? 
> > > 
> > > cheers,
> > > 
> > > S.
> > 
> > xm list is definetly behaving better, xm destroy is still having issues.
> > 
> > The best test for xm destroy in my case is to try to start a domain that
> > is unable to mount root filesystem, once that happens the only way to
> > get rid of that domain is to kill xend and purge the files. Doing an xm
> > list shows the domain crashed. Will start a new thread on this.
> 
> Dan Smith, can you create a test case for xm-test for that condition?
> 
> 	-Sean

Just got a panic on Dom0 as well

Test Case
Bring up 4 DomU's
from terminal on 4th DomU issue a reboot
xm list is toast

And this leads to the panic on Dom0

xm create -c domain4
Using config file "/etc/xen/domain4".
Traceback (most recent call last):
  File "/usr/sbin/xm", line 10, in ?
    main.main(sys.argv)
  File "/usr/lib/python/xen/xm/main.py", line 729, in main
    handle_xend_error(argv[1], args[0], ex)
  File "/usr/lib/python/xen/xm/main.py", line 163, in handle_xend_error
    raise ex
xen.xend.XendProtocol.XendError: (3, 'No such process')

And the panic
kernel/workqueue.c:170

Unfortunately my only console cable was on the wrong machine :-(
If needed I may be able to reproduce, got hg down, must say the
mercurial cheat sheet is splendid. 

Are you guys getting any mails from the list?

Starting to suspect my ISP, as my mail volume is very light today.


Ted