All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "prabhakara_r" <prabhakara_r@indiatimes.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: nfs lockd error message
Date: 29 Oct 2001 18:11:37 +0100	[thread overview]
Message-ID: <shssnc2e5h2.fsf@charged.uio.no> (raw)
In-Reply-To: <200110291642.WAA30251@WS0005.indiatimes.com>
In-Reply-To: <200110291642.WAA30251@WS0005.indiatimes.com>

>>>>> " " == 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

      reply	other threads:[~2001-10-29 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-29 16:51 nfs lockd error message prabhakara_r
2001-10-29 17:11 ` Trond Myklebust [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=shssnc2e5h2.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prabhakara_r@indiatimes.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.