WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] unclean shutdown

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] unclean shutdown
From: John Levon <levon@xxxxxxxxxxxxxxxxx>
Date: Wed, 24 Jan 2007 20:03:41 +0000
Delivery-date: Wed, 24 Jan 2007 12:01:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
Shutting down xend gives in xend.log:

[2007-01-24 11:46:09 xend 100902] DEBUG (SrvServer:76) SrvServer.cleanup()
[2007-01-24 11:46:09 xend 100902] DEBUG (XMLRPCServer:185) 
XMLRPCServer.cleanup()
[2007-01-24 11:46:09 xend 100902] ERROR (XMLRPCServer:192) (134, 'Transport 
endpoint is not connected')
Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/xen/xend/server/XMLRPCServer.py", line 
189, in cleanup
  File "<string>", line 1, in shutdown
error: (134, 'Transport endpoint is not connected')

Should we be catching this and keeping quiet in this case?

regards
john

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

<Prev in Thread] Current Thread [Next in Thread>