Bug 134013 - glibc-2.3.3-59 breaks NFS mountd & statd
Summary: glibc-2.3.3-59 breaks NFS mountd & statd
Keywords:
Status: CLOSED DUPLICATE of bug 133982
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-09-28 23:12 UTC by Felipe Alfaro Solana
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:05:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Output of "strace rpc.mountd" (81.44 KB, text/plain)
2004-09-28 23:13 UTC, Felipe Alfaro Solana
no flags Details

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.


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