* Michael Prokop mika@grml.org [070712 17:52]:
- Frank Eisenblaetter feisenbl@gmx.de [20070711 23:04]:
- Michael Prokop mika@grml.org [070711 21:42]:
- Frank Eisenblaetter feisenbl@gmx.de [20070711 21:15]:
[...]
mount.nfs: rpc.statd is not running but is required for remote locking Either use "-o nolocks" to keep locks local, or start statd.
If I try to start rpc.statd with
# /etc/init.d/nfs-common
it takes about 1 minute to finish "Starting NFS common utilities: statd.", but id doesn't change anything.
[...]
Please try running: wget http://snapshot.debian.net/archive/2007/06/03/debian/pool/main/p/portmap/por... dpkg -i portmap_6.0-0_i386.deb Restart portmap Restart nfs-common
[...]
Thanks for fast reply. I downgraded portmap to 6.0-0 as you descibed but that didn't change anything. I still get the same error message as described above. It takes about 3 min to finish a
Restart portmap
Very interesting. On my system it works after booting and when running:
# Restart nfs-common
then.
I just stumbled upon:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432511
Are you using kernel 2.6.22? I'm using 2.6.22-grml here with all packages being up2date (what will be available soon as new develrelease 1.0-1). Looks like a portmap/nfs-common<->2.6.22 issue.
portmap 6.0-0
# uname -r 2.6.20-grml
nfs-common 1:1.1.0-6
After reboot portmap gets started automatically.
# ps ax | grep portmap 4409 ? Ss 0:00 /sbin/portmap -i 127.0.0.1
If I try to start nfs-common:
# Restart nfs-common Stopping NFS common utilities: idmapd statd. Starting NFS common utilities: statd
At this point there is a delay of about 3 min till I get a new prompt.
If I do a:
# ps ax | grep statd
I see no rpc.statd or somthing like that.
I don't think it's the same problem as in bug #432511 because I cannot restart nfs-common.
Regards, Frank