Version: 1:1.1.1~git-20070709-3 On Sun, Aug 12, 2007 at 10:38:59PM -0500, Nelson Castillo wrote: >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
On Sun, Aug 12, 2007 at 10:51:38PM -0500, Nelson Castillo wrote: >On 8/12/07, Steinar H. Gunderson <[EMAIL PROTECTED]> wrote: >>On Sun, Aug 12, 2007 at 08:28:30PM -0500, Nelson Castillo wrote: >>>I'm using Debian sid and I upgraded the system today >>>(the last complete upgrade was about one month ago). >>>I get the "failed to contact portmap" errors. >> >>Is the portmapper running at all? (ps aux | grep portmap) >> >>>I am stuck. I used the proposed workaround (fsid=0) and it didn't work. >> >>I believe this is a separate bug. Please open a new one. > >Done. I opened: > >Bug#437525: nfs-kernel-server: Kernel prints "RPC: failed to contact >portmap (errno -5)" > >In my case, portmap was bound to the loopback address in >/etc/default/portmap. Removing this option allowed me to do the remote >mount. I don't know if #437525 is actually a bug, It isn't. >but at least the message is misleading and it's ok to have it >documented somewhere. The portmap man page is very clear about that. >Thanks for your help. > >-- >http://arhuaco.org >http://emQbit.com Nelson, Thank you for the report. I'm clossing this bug accordingly. Best Regards, Aníbal Monsalve Salazar -- http://v7w.com/anibal
signature.asc
Description: Digital signature
