All of lore.kernel.org
 help / color / mirror / Atom feed
From: David F Barrera <dfbp@us.ibm.com>
To: Ted Kaczmarek <tedkaz@optonline.net>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Steven Hand <Steven.Hand@cl.cam.ac.uk>
Subject: Re: xm list error changeset:6796
Date: Thu, 15 Sep 2005 11:14:50 -0500	[thread overview]
Message-ID: <1126800890.6025.12.camel@dbarrera_tp> (raw)
In-Reply-To: <1126800038.4140.28.camel@pluto.linsolutions.com>

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

      reply	other threads:[~2005-09-15 16:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-14 22:22 xm list error changeset:6796 Ted Kaczmarek
2005-09-14 22:38 ` Steven Hand
2005-09-14 23:02   ` Ted Kaczmarek
2005-09-15 12:34   ` Ted Kaczmarek
2005-09-15 14:22     ` Sean Dague
2005-09-15 16:45       ` Ted Kaczmarek
2005-09-15 16:00     ` Ted Kaczmarek
2005-09-15 16:14       ` David F Barrera [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1126800890.6025.12.camel@dbarrera_tp \
    --to=dfbp@us.ibm.com \
    --cc=Steven.Hand@cl.cam.ac.uk \
    --cc=tedkaz@optonline.net \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.