[Xen-users] "xm" dying with "Bad File Descriptor

To:	xen-users@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-users] "xm" dying with "Bad File Descriptor
From:	Paul Tomblin <ptomblin@xxxxxxxxx>
Date:	Thu, 24 Jun 2010 11:28:06 -0400
Delivery-date:	Thu, 24 Jun 2010 08:30:09 -0700
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=tWOFffYvuNjHTdXtFqfhvVhaW0AtT+Yk3kVOh1CFwFA=; b=Zv7+XqqwWx4PUjdxN8ldYcq9YDmxpUuUHY1MMXyPDM1jwimn0jebKSMVs4CN6s2SC8 il3sZWtnR61KLWfmMsJATQwuYdJHhulo8MXdnzjoT/9RNTnPrg1KMAUgtrsY3hO3rjaZ YHtHIhO9FH3tNFOdvPVbf9Q/VdHbsWuKN/KTg=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=UZAlqKHgCAOn+10ieKT6Us8lgdBIIg8P4KwANsuiPzDjgKhzOTwKreNO5ycQtQd4eb Z845JdddtmCV0zA2a6yvl1IgqsKiUOTUvPhYFnu3PvwFXXep4IauJV/4lfdkCaTLG2Qn qFr6by2qkTTA9m9197Br/MJcTqeYuWWZAVz70=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-users-request@lists.xensource.com?subject=help>
List-id:	Xen user discussion <xen-users.lists.xensource.com>
List-post:	<mailto:xen-users@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-users-bounces@xxxxxxxxxxxxxxxxxxx

I recently (in the last 24 hours) succeeded in moving all my domUs from a dom0 that was running on a 686-based server to one that is running on a newer amd64-based server. I used the latest Debian Stable for both. The domUs are all running fine, but in the last few hours I've discovered that the "xm" command is dying with an error "Error: (9, 'Bad file descriptor')". /var/log/xen/xend-debug.log seems to imply that a socket has shut down:

Traceback (most recent call last):

File "/usr/lib/python2.5/SocketServer.py", line 464, in process_request_thread

self.finish_request(request, client_address)

File "/usr/lib/python2.5/SocketServer.py", line 254, in finish_request

self.RequestHandlerClass(request, client_address, self)

File "/usr/lib/xen-3.2-1/lib/python/xen/util/xmlrpclib2.py", line 106, in <lambda>

requestHandler(allowed, x, y, z)),

File "/usr/lib/xen-3.2-1/lib/python/xen/util/xmlrpclib2.py", line 65, in __init__

server)

File "/usr/lib/python2.5/SocketServer.py", line 522, in __init__

self.handle()

File "/usr/lib/python2.5/BaseHTTPServer.py", line 316, in handle

self.handle_one_request()

File "/usr/lib/python2.5/BaseHTTPServer.py", line 310, in handle_one_request

method()

File "/usr/lib/xen-3.2-1/lib/python/xen/util/xmlrpclib2.py", line 82, in do_POST

self.send_response(200)

File "/usr/lib/python2.5/BaseHTTPServer.py", line 368, in send_response

(self.protocol_version, code, message))

File "/usr/lib/python2.5/socket.py", line 274, in write

self.flush()

File "/usr/lib/python2.5/socket.py", line 261, in flush

self._sock.sendall(buffer)

error: (32, 'Broken pipe')

I've seen numerous mentions of this error on the net, including a Bugzilla bug filed over a year ago. Does anybody know what causes this, and is there a way to recover short of rebooting every time it happens? My xen setup ran flawlessly for several years on the old server, and I'm hoping the new one will work as well.

--
http://www.linkedin.com/in/paultomblin
http://careers.stackoverflow.com/ptomblin

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

WARNING - OLD ARCHIVES

xen-users

[Xen-users] "xm" dying with "Bad File Descriptor