[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#437525: marked as done (nfs-kernel-server: Kernel prints "RPC: failed to contact portmap (errno -5)")



Your message dated Mon, 15 Feb 2010 02:41:26 +0100
with message-id <20100215014126.GA23458@galadriel.inutil.org>
and subject line Re: Bug#437525: The bug is about the kernel warning
has caused the Debian Bug report #437525,
regarding nfs-kernel-server: Kernel prints "RPC: failed to contact portmap (errno -5)"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
437525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437525
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.1.1~git-20070709-3
Severity: normal

Hi.

I get this message whenever I restart nfs-kernel-server (dmesg).

 nfsd: unexporting all filesystems
 RPC: failed to contact portmap (errno -5).
 NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery
 directory
 NFSD: starting 90-second grace period

This message was printed once in dmesg:

  lockd_up: makesock failed, error=-5

I don't have iptables rules in this host.

I don't know if this is actually a bug, but this message
had me looking for it for a while and confused me :)
I couldn't mount NFS shares from other hosts because
portmap was bound to the loopback interface.

Regards,
Nelson.-




-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.21-2-686 (SMP w/1 CPU core)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages nfs-kernel-server depends on:
ii  libblkid1         1.40.2-1               block device id library
ii  libc6             2.6.1-1                GNU C Library: Shared libraries
ii  libcomerr2        1.40.2-1               common error description library
ii  libgssapi2        0.11-1                 A mechanism-switch gssapi library
ii  libkrb53          1.6.dfsg.1-6           MIT Kerberos runtime libraries
ii  libnfsidmap2      0.20-0                 An nfs idmapping library
ii  librpcsecgss3     0.14-2                 allows secure rpc communication us
ii  libwrap0          7.6.dbs-14             Wietse Venema's TCP wrappers libra
ii  lsb-base          3.1-24                 Linux Standard Base 3.1 init scrip
ii  nfs-common        1:1.1.1~git-20070709-3 NFS support files common to client
ii  ucf               3.001                  Update Configuration File: preserv

nfs-kernel-server recommends no packages.

-- no debconf information


--- End Message ---
--- Begin Message ---
On Fri, Aug 14, 2009 at 12:32:20AM +0200, Moritz Muehlenhoff wrote:
> On Mon, Aug 27, 2007 at 11:41:56PM +0200, Steinar H. Gunderson wrote:
> > reassign 437525 linux-image-2.6.21-2-686
> > thanks
> > 
> > On Mon, Aug 27, 2007 at 04:32:42PM -0500, Nelson Castillo wrote:
> > > As I told you before, I reported the bug (the message printed by
> > > the kernel) because I found the message to be misleading and I
> > > wasted some time with it.
> > 
> > OK, that wasn't really clear to me, among all the other discussion.
> > 
> > > Since you could not reproduce the message I reported
> > > (RPC: failed to contact portmap (errno -5)), perhaps you
> > > should close the bug (I guess you'll know what to do best).
> > 
> > Well, it doesn't have anything to do with the NFS userspace, so I'm
> > reassigning it to the kernel. I don't really think there's much to be done
> > about it, though, so I'd guess it will simply get closed. Thanks for taking
> > care to report it in any case :-)
> 
> Does this still occur with current kernels/NFS code?

No further feedback, closing the bug.

If anyone reencounters the problem, please reopen this bug.

Cheers,
        Moritz


--- End Message ---

Reply to: