Bug#399523: rpc.statd[2058]: unable to register (statd, 1, udp).
Nicolas Boullis
Version: 1:1.0.10-4
Severity: important
Hi,
I have a host that tries to mount a remote directory via NFS.
Unfortunately, locking does not work. In syslog, I can see:
kernel: lockd: cannot monitor WW.XX.YY.ZZ
kernel: lockd: failed to monitor WW.XX.YY.ZZ
(and then my application failing because of the failure to lock)
And before that, looking for the rpc.statd startup:
rpc.statd[2058]: Version 1.0.10 Starting
portmap[2065]: connect from 127.0.0.1 to set(status): request from
unprivileged port
rpc.statd[2058]: unable to register (statd, 1, udp).
Although I don't think it makes a big difference, note that this is
inside a UML host.
Cheers,
Nicolas Boullis
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages nfs-common depends on:
ii adduser 3.99 Add and remove users and groups
ii libc6 2.3.6.ds1-7 GNU C Library: Shared libraries
ii libcomer 1.39+1.40-WIP-2006.10.02+dfsg-2 common error description library
ii libevent 1.1a-1 An asynchronous event notification
ii libgssap 0.10-4 A mechanism-switch gssapi library
ii libkrb53 1.4.4-4 MIT Kerberos runtime libraries
ii libnfsid 0.17-3 An nfs idmapping library
ii librpcse 0.14-2 allows secure rpc communication us
ii lsb-base 3.1-15 Linux Standard Base 3.1 init scrip
ii netbase 4.27 Basic TCP/IP networking system
ii portmap 5-21 The RPC portmapper
ii ucf 2.0016 Update Configuration File: preserv
nfs-common recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Steinar H. Gunderson
> Although I don't think it makes a big difference, note that this is
> inside a UML host.
Could you please try outside UML?
/* Steinar */
--
Homepage: http://www.sesse.net/
Nicolas Boullis
Steinar H. Gunderson wrote:
> On Mon, Nov 20, 2006 at 12:03:30PM +0100, Nicolas Boullis wrote:
>
>>Although I don't think it makes a big difference, note that this is
>>inside a UML host.
>
> Could you please try outside UML?
I just managed to find a host where I could copy my whole filesystem. I
could not reproduce the problem there, so it might be UML-specific.
Note that inside UML, running "/etc/init.d/nfs-common restart" fixes the
problem, with this in the log:
rpc.statd[2168]: Version 1.0.10 Starting
Cheers,
Nicolas
Nicolas Boullis
On Tue, Nov 21, 2006 at 06:15:30PM +0100, Steinar H. Gunderson wrote:
> On Tue, Nov 21, 2006 at 05:22:07PM +0100, Nicolas Boullis wrote:
> >> Could you please try outside UML?
> > I just managed to find a host where I could copy my whole filesystem. I
> > could not reproduce the problem there, so it might be UML-specific.
> >
> > Note that inside UML, running "/etc/init.d/nfs-common restart" fixes the
> > problem, with this in the log:
> > rpc.statd[2168]: Version 1.0.10 Starting
>
> Given that the kernel is sending odd messages here, I'm fairly sure this is
> not a bug in nfs-utils (which only covers the userspace part), but rather a
> bug in the UML kernel; thus, I'm closing the bug.
The kernel gave those error messages because it could not talk to the
rpc.statd server. And before that, there were those error messages from
the rpc.statd and portmap servers:
rpc.statd[2058]: Version 1.0.10 Starting
portmap[2065]: connect from 127.0.0.1 to set(status): request from unprivileged port
rpc.statd[2058]: unable to register (statd, 1, udp).
Hence, I think the problem is not that clearly in the kernel: it looks
like portmap rejected the registration of rpc.statd...
Since running "/etc/init.d/nfs-common restart" fixes the problem, I
would have thought that it was doing something wrong the furst time it
was run.
Hence, I think that:
- there is still a bug somewhere, which means the bug should not be
closed;
- the bug is somewhat specific since my attempt to reproduce it
on a different host was a failure, which means the bug should be
downgraded to normal;
- the bug probably is either in nfs-common or in portmap or in
user-mode-linux, which means the bug should be reassigned to all 3
packages.
Anyway, I don't want to do the re-openning my self since I don't want to
play open-and-close ping-pong. ;-)
Markus Schulz
original /var. It looks like the boot-scipts (/etc/rcS.d/) need some
files from /var to mount the nfs share proper.
--
Markus Schulz
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?