Bug 134013

Summary: glibc-2.3.3-59 breaks NFS mountd & statd
Product: [Fedora] Fedora Reporter: Felipe Alfaro Solana <felipe_alfaro>
Component: glibcAssignee: Jakub Jelinek <jakub>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: rawhideCC: barryn
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:05:59 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:
Attachments:
Description Flags
Output of "strace rpc.mountd" none

Description Felipe Alfaro Solana 2004-09-28 23:12:33 UTC 
Description of problem:
Since upgrading to glibc-2.3.3-59, rpc.mountd and rpc.statd are unable
to start. Downgrading to glibc-2.3.3-55 fixes the problem.
Please, look at the attached "strace_rpc_mountd": it's the output
generated by "strace rpc.mountd".

Version-Release number of selected component (if applicable):
glibc-2.3.3-59
nfs-utils-1.0.6-34

How reproducible:
Always (even with SELinux support disabled)

Steps to Reproduce:
1. Upgrade to glibc-2.3.3-59
2. "/etc/init.d/nfslock start" will fail
3. "/etc/init.d/nfs start" will fail
  
Actual results:
Both rpc.mountd and rpc.statd fail to start. It seems a socket-related
problem, although I can't tell for sure.

Expected results:
Both rpc.mountd and rpc.statd should work. NFS is a important
component for many customers.

Additional info:
I have attached the output of "strace rpc.mountd" for further analysis.
Comment 1 Felipe Alfaro Solana 2004-09-28 23:13:17 UTC 
Created attachment 104465 [details]
Output of "strace rpc.mountd"
Comment 2 Ulrich Drepper 2004-09-29 00:29:28 UTC 

*** This bug has been marked as a duplicate of 133982 ***
Comment 3 Red Hat Bugzilla 2006-02-21 19:05:59 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.