Your message dated Wed, 5 Apr 2006 23:09:45 +0200
with message-id <[EMAIL PROTECTED]>
and subject line nfs-kernel-server: lockd service doesn't register with
portmapper
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: nfs-kernel-server
Version: 1:1.0.6-3.1
Severity: important
The lockd service is not registered with the portmapper, resulting in
NFS clients being able to perform locking on a mounted NFS export.
Here is the output from a pmap_dump:
buffaloberry:/home/jamesm# pmap_dump
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 999 status
100024 1 tcp 1002 status
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100227 3 udp 2049
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100227 3 tcp 2049
100005 1 udp 602 mountd
100005 1 tcp 605 mountd
100005 2 udp 602 mountd
100005 2 tcp 605 mountd
100005 3 udp 602 mountd
100005 3 tcp 605 mountd
Here is a 'ps' showing that the kernel's lockd is running.....
buffaloberry:/home/jamesm# ps auxww | grep lockd | grep -v grep | grep -v
kblockd
root 2041 0.0 0.0 0 0 ? S Sep02 0:00 [lockd]
And here is the netstat showing that it's listening on external ports.....
buffaloberry:/home/jamesm# netstat -atu | grep 327
tcp 0 0 *:32770 *:* LISTEN
udp 0 0 *:32768 *:*
buffaloberry:/home/jamesm#
So, if I manually use pmap_set to enter this information into the portmapper,
everything starts to work correctly - leading to my diagnosis that the problem
lies with the lock daemon not registering with the portmapper.........
buffaloberry:~# cat portmap_nlockmgr
100021 3 tcp 32770 nlockmgr
100021 1 tcp 32770 nlockmgr
100021 1 udp 32768 nlockmgr
100021 3 udp 32768 nlockmgr
100021 4 udp 32768 nlockmgr
100021 4 tcp 32770 nlockmgr
buffaloberry:~# pmap_set < portmap_nlockmgr
buffaloberry:~#
Everything is hunky-dory and works fine now, with the obvious problem that
these ports may change across reboot, and it's a bit of a hack really anyway!
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.5-perfctr
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages nfs-kernel-server depends on:
ii debconf 1.4.30.13 Debian configuration management sy
ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an
ii libwrap0 7.6.dbs-8 Wietse Venema's TCP wrappers libra
ii nfs-common 1:1.0.6-3.1 NFS support files common to client
ii sysvinit 2.86.ds1-1 System-V like init
-- no debconf information
--- End Message ---
--- Begin Message ---
On Mon, Mar 27, 2006 at 02:17:04AM +0200, Steinar H. Gunderson wrote:
> This definitely works for me under 1.0.7-3:
No response for a week, so I'm taking the liberty to close this bug, assuming
it was fixed in 1.0.7 somewhere. Feel free to reopen if you still see it. :-)
/* Steinar */
--
Homepage: http://www.sesse.net/
--- End Message ---
