Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 117200 - nfs: rpc.nfsd startup failed
Summary: nfs: rpc.nfsd startup failed
Keywords:
Status: CLOSED DUPLICATE of bug 117115
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils
Version: rawhide
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-01 15:26 UTC by Brian Millett
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:01:43 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Brian Millett 2004-03-01 15:26:20 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b)
Gecko/20040226 Firefox/0.8.0+

Description of problem:
The /etc/init.d/nfs service fails starting up the nfsdaemon.
This worked for kernel-2.6.3-1.110.

In /var/log/boot.log all I get is:
 nfs: rpc.nfsd startup failed

in /var/log/messages I get:
 nfs: rpc.nfsd startup failed

then later I get this:
  kernel: nfsd: Unknown symbol locks_remove_posix

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

How reproducible:
Always

Steps to Reproduce:
1.install kernel-2.6.3-1.116
2.boot
3.read messages
    

Expected Results:  not fail, but start clean.

Additional info:
Comment 1 Bill Nottingham 2004-03-02 06:14:03 UTC 

*** This bug has been marked as a duplicate of 117115 ***
Comment 2 Bill Nottingham 2004-03-02 06:14:12 UTC 
*** This bug has been marked as a duplicate of 117116 ***

*** This bug has been marked as a duplicate of 117116 ***
Comment 3 Red Hat Bugzilla 2006-02-21 19:01:43 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.