Bug 713082 - multiprocessing.Pipe problem: "handle out of range in select()"
Summary: multiprocessing.Pipe problem: "handle out of range in select()"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: python
Version: 6.1
Hardware: Unspecified
OS: Linux
high
urgent
Target Milestone: rc
: ---
Assignee: Dave Malcolm
QA Contact: Petr Šplíchal
URL:
Whiteboard:
Depends On:
Blocks: 849992
TreeView+ depends on / blocked
 
Reported: 2011-06-14 08:45 UTC by Igor Lvovsky
Modified: 2016-06-01 01:42 UTC (History)
5 users (show)

Fixed In Version: python-2.6.6-21.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 849992 (view as bug list)
Environment:
Last Closed: 2011-12-06 10:24:22 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1564 0 normal SHIPPED_LIVE python bug fix and enhancement update 2011-12-06 00:39:12 UTC

Description Igor Lvovsky 2011-06-14 08:45:01 UTC
Description of problem:

In vdsm-4.9 code we use multiprocessing.Pipe to communicate with subprocesses.
In several scenarios when we trying to run sufficiently large amount of VMs, the pipe ends raise the exception: "handle out of range in select()".
Actually, it's kind of regression from vdsm-4.5 (we didn't use multiprocessing in vdsm-4.5)

We found same issue (including the patch and reproducer) in python's issue tracker:
 http://bugs.python.org/issue10527


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 6 errata-xmlrpc 2011-12-06 10:24:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1564.html


Note You need to log in before you can comment on or make changes to this bug.