[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#740574: libtirpc1: Still causes statd from the nfs-common package to fail



Control: severity -1 grave
Control: found -1 0.2.3-1


Hi,
I still experience the NFS failure (bug #740574) after upgrading to
libtirpc1/0.2.3-1:

[UPGRADE] libc6:amd64 2.19-1 -> 2.19-4
[UPGRADE] libc6:i386 2.19-1 -> 2.19-4
[UPGRADE] libc6-i386:amd64 2.19-1 -> 2.19-4
[UPGRADE] libc6-i686:i386 2.19-1 -> 2.19-4
[UPGRADE] libc6-x32:amd64 2.19-1 -> 2.19-4
[UPGRADE] libtirpc1:amd64 0.2.2-5 -> 0.2.3-1

With these versions, nfs-kernel-server fails to restart.
The errors in /var/log/syslog are:

rpc.statd[5399]: Version 1.2.8 starting
sm-notify[5400]: Version 1.2.8 starting
dnsmasq-dhcp[2864]: DHCPREQUEST(eth0) 192.168.1.240 00:24:73:ce:55:81
dnsmasq-dhcp[2864]: DHCPACK(eth0) 192.168.1.240 00:24:73:ce:55:81 switch3com
console-kit-daemon[3729]: GLib-CRITICAL: Source ID 80 was not found when attempting to remove it
rpc.mountd[3091]: Caught signal 15, un-registering and exiting.
kernel: [ 1348.798956] nfsd: last server has exited, flushing export cache
kernel: [ 1349.904840] svc: failed to register lockdv1 RPC service (errno 13).
kernel: [ 1349.904849] lockd_up: makesock failed, error=-13
rpc.nfsd[7107]: error starting threads: errno 13 (Permission denied)


As reported by others, downgrading to libtirpc1/0.2.2-5 and libc6/2.19-1 (and restarting rpcbind, nfs-common, and nfs-kernel-server) makes the issue vanish.

I think this bug is grave, since it prevents NFS from working.

Please fix this issue.
Thank you.


--
Matteo


Reply to: