Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 480048

Summary: multipathd doesn't close pipe fds on a failed fork
Product: Red Hat Enterprise Linux 5 Reporter: Ben Marzinski <bmarzins>
Component: device-mapper-multipathAssignee: Ben Marzinski <bmarzins>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: urgent    
Version: 5.3CC: agk, bmarzins, bmr, christophe.varoqui, coughlan, djansa, dmair, dwysocha, edamato, egoggin, heinzm, jplans, junichi.nomura, kueda, laurie.barry, lmb, mbroz, prockai, syeghiay, tranlan
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-02 11:46:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 481740    

Description Ben Marzinski 2009-01-14 18:17:32 UTC
When multipathd tries to fork a callout, if it fails, it doesn't close the pipe fds necessary to talk to the callout.  Also, when multipathd fails to execute a callout, it doesn't print any useful error messages.

Comment 1 Tom Coughlan 2009-01-15 19:23:35 UTC
*** Bug 480170 has been marked as a duplicate of this bug. ***

Comment 3 laurie barry 2009-01-16 00:54:52 UTC
Is RH planning to fix this for RHEL5.3?  We need to determine how much longer our test bed/test resources will be consumed with this release and whether we need to regression test another RHEL5.3 RC?

Laurie

Comment 4 Ben Marzinski 2009-01-16 22:55:06 UTC
The fix for this is committed. The plan is to release this as a z-stream release.  Although I noticed this bug looking at 478643, as far as I know, nobody has ever hit it.  The error reporting is very helpful to tell if people are running into 478643, and need to increase their max_fds, but as long as you follow the workaround in that bugzilla, you should be fine.

Comment 8 Ben Marzinski 2009-07-08 20:58:16 UTC
The release notes in bz #478643 have all the information that's necessary.

Comment 10 errata-xmlrpc 2009-09-02 11:46:40 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2009-1377.html