Package: rpcbind
Version: 0.2.0-6
Severity: normal
Please note that I am reporting this bug against rpcbind instead of
nfs-utils because that is where I believe the real problem lies as
this problem did not occur when using portmap.
I use the -p option with rpc.mountd to force it to use a known port
number so it works behind an iptables firewall. When this is done,
rpc.mountd reports the following at startup:
root@myth# /etc/init.d/nfs-kernel-server start ~
Exporting directories for NFS kernel daemon....
Starting NFS kernel daemon: nfsd mountdrpc.mountd: svc_tli_create: could not
bind to requested address
rpc.mountd: svc_tli_create: could not bind to requested address
rpc.mountd: svc_tli_create: could not bind to requested address
rpc.mountd: svc_tli_create: could not bind to requested address
The "could not bind" errors occur when rpc.mountd is unable to bind
the NFSv3 support after successfully binding the NFSv2 support. The
following output from rpcinfo -p confirms that rpc.mountd is only able
to bind the NFSv2 support.
root@myth# rpcinfo -p ~
program vers proto port service
100000 4 tcp 111 portmapper
100000 3 tcp 111 portmapper
100000 2 tcp 111 portmapper
100000 4 udp 111 portmapper
100000 3 udp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 53729 status
100024 1 tcp 41274 status
100021 1 udp 47618 nlockmgr
100021 3 udp 47618 nlockmgr
100021 4 udp 47618 nlockmgr
100021 1 tcp 41685 nlockmgr
100021 3 tcp 41685 nlockmgr
100021 4 tcp 41685 nlockmgr
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100005 1 udp 786 mountd
100005 1 tcp 786 mountd
This results in the following errors when trying to mount an exported
directory on another system using NFSv3:
root@opus# mount -v -o vers=3 myth:/myth /mnt /home/david
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Wed Apr 27 19:41:25 2011
mount.nfs: trying text-based options 'vers=3,addr=192.168.1.6'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 192.168.1.6 prog 100003 vers 3 prot TCP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 192.168.1.6 prog 100005 vers 3 prot UDP port 786
mount.nfs: portmap query retrying: RPC: Program/version mismatch
mount.nfs: prog 100005, trying vers=3, prot=6
mount.nfs: trying 192.168.1.6 prog 100005 vers 3 prot TCP port 786
mount.nfs: portmap query failed: RPC: Program/version mismatch
mount.nfs: Operation not permitted
As mentioned above, this problem did not occur when portmap could be
used instead of rpcbind. Now that nfs-common requires rpcbind, the
only way to make NFSv3 usable when using the rpc.mountd -p option is
to also use the -N2 option. The -N2 option disables NFSv2 support and
allows rpc.mountd to bind its NFSv3 support.
David Engel
[email protected]
[email protected]
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32.39 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rpcbind depends on:
ii insserv 1.14.0-2.1 Tool to organize boot sequence usi
ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib
ii libtirpc1 0.2.1-1 transport-independent RPC library
ii libwrap0 7.6.q-19 Wietse Venema's TCP wrappers libra
ii lsb-base 3.2-27 Linux Standard Base 3.2 init scrip
rpcbind recommends no packages.
rpcbind suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
