Skip to contentSkip to conversation

nfs lockd error message

DISCUSSION prabhakara_r 2 participants 2 messages Oct 29, 2001

lore
Share & tools
lore
#0 lore raw

hi all,
i am getting an error message "portmap: server localhost not responding, timed out" followed by "portmap: makesock failed, error = -5" after I recompiled the kernel with some changes in tcp files under ipv4 dir. the system hangs for minutes and then boots as usual. though i am damn sure that i haven't done any changes to NFS source code, i am still getting this error message. subsequently the system also shows "NFS lockd failed" while shutting down.could anyone of u pls tell me why i am getting this error and how to solve this problem.

kindly CC the suggestion to email address:
[email protected]

thanks in advance!
Prabhakar.R

Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com

Buy Music, Video, CD-ROM, Audio-Books and Music Accessories from http://www.planetm.co.in

#1 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

" " == prabhakara r <prabhakara_r> writes:

> hi all,
> i am getting an error message "portmap: server localhost not
> responding, timed out" followed by "portmap: makesock
> failed, error = -5" after I recompiled the kernel with some
> changes in tcp files under ipv4 dir. the system hangs for
> minutes and then boots as usual. though i am damn sure that
> i haven't done any changes to NFS source code, i am still
> getting this error message. subsequently the system also
> shows "NFS lockd failed" while shutting down.could anyone of
> u pls tell me why i am getting this error and how to solve
> this problem.

The problem isn't with the kernel but with your setup. For some reason, the kernel is unable to contact the portmapper in order to register a service.

That can mean either that you are starting rpc.portmap after you start lockd, or that you have blocked access from 'localhost' (either using the tcp_wrappers, or using ipchains).

Cheers,
Trond