Bug#740574: Confirmation of bug 740574
Hello:
I can add another confirmation of this bug. My symptoms and solution
were the same as reported above.
For reference, my experience was as follows:
NFS failed to restart after upgrade from 1:1.2.8-5 to 1:1.2.8-6.
Reverting to previously working nfs-common and nfs-kernel-server
packages did not work. Downgrading from libtirpc1 0.2.2-5.1 to
libtirpc1 to 0.2.2-5 did bring NFS back up after restart of rpcbind,
nfs-common and nfs-kernel-server. I did not reboot during the course of
problem/solution.
My syslog showed similar information to that quoted above:
Mar 2 04:03:06 localhost rpc.statd[14412]: Version 1.2.8 starting
Mar 2 04:03:06 localhost sm-notify[14413]: Version 1.2.8 starting
Mar 2 04:03:06 localhost sm-notify[14413]: Already notifying clients;
Exiting!
Mar 2 04:03:06 localhost rpc.statd[14412]: Failed to read
/var/lib/nfs/state: Success
Mar 2 04:03:06 localhost rpc.statd[14412]: Initializing NSM state
Mar 2 04:03:06 localhost rpc.statd[14412]: failed to create RPC
listeners, exiting
Mar 2 04:03:40 localhost kernel: [295442.728274] svc: failed to
register lockdv1 RPC service (errno 13).
Mar 2 04:03:40 localhost rpc.nfsd[14954]: error starting threads: errno
13 (Permission denied)
$ uname -a
Linux 3.11-2-amd64 #1 SMP Debian 3.11.10-1 (2013-12-04) x86_64 GNU/Linux
With thanks,
James Fregeau
Reply to: