Public bug reported:
After a new install from scratch, there is a problem with rpcbind and the nfs
client :
after boot, the shared directories are NOT mounted and if I try to mount them
manually:
> mount -a
it says
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
the process list gives:
> ps aux | grep rpc | grep -v grep
root 846 0.0 0.0 0 0 ? S< Jul17 0:00 [rpciod]
root 876 0.0 0.0 2860 660 ? Ss Jul17 0:00 rpc.idmapd
In syslog, I can see that rpc.statd failed to start:
Jul 16 12:31:20 techniciens-3 rpc.statd[2217]: Version 1.2.5 starting
Jul 16 12:31:20 techniciens-3 rpc.statd[2217]: failed to create RPC listeners,
exiting
Jul 16 12:31:36 techniciens-3 rpc.statd[2223]: Version 1.2.5 starting
Jul 16 12:31:36 techniciens-3 rpc.statd[2223]: Flags: TI-RPC
Jul 16 12:31:36 techniciens-3 rpc.statd[2223]: failed to create RPC listeners,
exiting
Jul 16 12:31:40 techniciens-3 rpc.statd[2230]: Version 1.2.5 starting
Jul 16 12:31:40 techniciens-3 rpc.statd[2230]: Flags: TI-RPC
Jul 16 12:31:40 techniciens-3 rpc.statd[2230]: failed to create RPC listeners,
exiting
Jul 16 12:31:40 techniciens-3 rpc.statd[2234]: Version 1.2.5 starting
Jul 16 12:31:40 techniciens-3 rpc.statd[2234]: Flags: TI-RPC
Jul 16 12:31:40 techniciens-3 rpc.statd[2234]: failed to create RPC listeners,
exiting
Jul 16 12:31:48 techniciens-3 rpc.statd[2242]: Version 1.2.5 starting
Jul 16 12:31:48 techniciens-3 rpc.statd[2242]: Flags: TI-RPC
The solution I have found is to start rpcbind manually
> rpcbind
then mounting works fine:
> mount -a
and after that, the process list gives:
> ps aux | grep rpc | grep -v grep
root 846 0.0 0.0 0 0 ? S< Jul17 0:00 [rpciod]
root 876 0.0 0.0 2860 660 ? Ss Jul17 0:00 rpc.idmapd
root 5700 0.0 0.0 2692 852 ? Ss 08:54 0:00 rpcbind
statd 5705 0.0 0.0 3152 1252 ? Ss 08:54 0:00 rpc.statd
--no-notify
Everything used to work perfectly with nfs client running Ubuntu 10.04 but
since then, portmap has been replaced by rpcbind. This happens on three
different computers running Ubuntu 12.04. All the other clients (still under
10.04) do not face that problem.
/etc/fstab on the client:
myserver:/exports/communs /Reseau/Communs nfs defaults,sync,rw
0 0
myserver:/exports/software /Reseau/Logiciels nfs
defaults,sync,rw 0 0
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nfs-common 1:1.2.5-3ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19
Uname: Linux 3.2.0-26-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
Date: Wed Jul 18 14:22:43 2012
InstallationMedia: Ubuntu 12.04 "Precise" - Build i386 LIVE Binary
20120426-12:41
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=fr_BE.utf8
SHELL=/bin/bash
SourcePackage: nfs-utils
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: nfs-utils (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026111
Title:
NFS shared folder not available after boot (RPC issue)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1026111/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
