[522138.025198] svc: failed to register nfsdv3 RPC service (errno 97).
[522138.073102] svc: failed to register lockdv1 RPC service (errno 97).
[522138.079548] NFSD: the nfsdcld client tracking upcall will be removed in 3.10. Please transition to using nfsdcltrack.
[522138.090304] NFSD: starting 90-second grace period (net c092a080)
[522261.874420] NFSD: Unable to end grace period: -110
updated to nfs-kernel-server 2.3.3-3 on 18.06.2, but still broken with the same error messages. nfsd not shown in ps.
When you install a package, is the baseline package for that release installed or does opkg upgrade to the latest by default.
Edit:
Looking at the Packages Download page it seems they are continuously built for current release. It seems opkg has no choice but to install what is available.
How does the advice not to upgrade packages apply to installing a packages
@mbo2o raises a good point. It all "works" when the dependencies are either not installed, or provide the same ABI as what is being expected. If the already-installed TLS library is "different" (which has been a recent problem), then installing a "newly built" package against a newer API would cause a problem as well.
In the past, people who have used scripts to "upgrade all upgradable packages" have run into problems.
I've scratched my head as to what the failure mechanism there is, but its unfortunately not obvious to me.
With it being relatively easy to flash and install a "full set" of needed packages, I still consider that the best option for anyone not building their own images.
sysupgrade on master supplies
-k include in backup a list of current installed packages at
/etc/backup/installed_packages.txt
which it accomplishes with
# Format: pkg-name<TAB>{rom,overlay,unkown}
# rom is used for pkgs in /rom, even if updated later
find /usr/lib/opkg/info -name "*.control" \( \
\( -exec test -f /rom/{} \; -exec echo {} rom \; \) -o \
\( -exec test -f /overlay/upper/{} \; -exec echo {} overlay \; \) -o \
\( -exec echo {} unknown \; \) \
\) | sed -e 's,.*/,,;s/\.control /\t/' > ${INSTALLED_PACKAGES}
(at least as of late May, 2019, prior to any future v19 release)
Same here. I built a fresh firmware with image builder (18.06.2). After restart nfsd:
Tue Jun 4 12:27:06 2019 kern.warn kernel: [80189.144502] svc: failed to register nfsdv3 RPC service (errno 124).
Tue Jun 4 12:27:06 2019 kern.warn kernel: [80189.182449] NFSD: the nfsdcld client tracking upcall will be removed in 3.10. Please transition to using nfsdcltrack.
Tue Jun 4 12:27:06 2019 kern.info kernel: [80189.193261] NFSD: starting 90-second grace period (net 80444040)
Tue Jun 4 12:27:06 2019 daemon.warn rpc.statd[9290]: Running as root. chown /var/lib/nfs to choose different user```
If anyone finds the magic to making NFS work, please post the solution. Thanks. Although the DLNA music server is working on the router, I can't add anything, at the moment
Tue Jun 4 20:47:50 2019 kern.info kernel: [ 7.562924] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Tue Jun 4 20:47:52 2019 kern.warn kernel: [ 16.544397] svc: failed to register nfsdv3 RPC service (errno 97).
Tue Jun 4 20:47:52 2019 kern.warn kernel: [ 16.633794] NFSD: the nfsdcld client tracking upcall will be removed in 3.10. Please transition to using nfsdcltrack.
Related logs:
Tue Jun 4 20:47:52 2019 daemon.err rpc.mountd[2845]: Could not bind socket: (98) Address in use
Tue Jun 4 20:47:52 2019 daemon.warn rpc.mountd[2845]: mountd: No V2 or V3 listeners created!
Tue Jun 4 20:47:52 2019 daemon.err rpc.statd[2844]: failed to create RPC listeners, exiting
I can't use PXE boot (which is serving large files over NFS) anymore. Running OpenWrt 18.06.2 r7676-cddd7b4c77.
@jeff do you mean that the upcoming 'nfs-kernel-server' update might fix the issue? It doesn't look that I have it at the latest version and I do have a rather fresh OpenWRT install:
root@OpenWrt:~# mv /etc/rc.d/S20network /etc/rc.d/S14network
root@OpenWrt:~# reboot
root@OpenWrt:~# Connection to openwrt.lan closed by remote host.
Connection to openwrt.lan closed.
waited a bit... then on the client:
davygrvy@kahaluia:~$ sudo mount /media/BigMedia
[sudo] password for davygrvy:
mount.nfs: requested NFS version or transport protocol is not supported
Examining the router:
root@OpenWrt:~# dmesg |tail
[ 16.515162] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[ 18.470155] br-lan: port 1(eth0.1) entered learning state
[ 18.528762] svc: failed to register nfsdv3 RPC service (errno 97).
[ 18.612527] svc: failed to register lockdv1 RPC service (errno 97).
[ 18.619027] NFSD: the nfsdcld client tracking upcall will be removed in 3.10. Please transition to using nfsdcltrack.
[ 18.629709] NFSD: starting 90-second grace period (net c092a080)
[ 21.520133] br-lan: port 1(eth0.1) entered forwarding state
[ 21.525861] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 140.640080] NFSD: Unable to end grace period: -110
[ 355.116753] NFSD: Unable to create client record on stable storage: -110
root@OpenWrt:~#
I thought starting portmap after the network was up would have solved this, but nope. I did fix minidlna coming up before the disk was ready by reordering, though
For those of you not willing to wait for a permanent fix, here's a temporary one. It looks that the 'nfs-kernel-server_2.1.1-1' version build for OpenWRT 17.01 is working perfectly fine with OpenWRT 18.06.2 stable build which I'm using.
OK, step by step, in a way which even less advanced users should understand what they're doing
Remove the current version of 'nfs-kernel-server':
opkg remove --autoremove nfs-kernel-server
Update opkg repo, we'll still need the dependencies for 'nfs-kernel-server_2.1.1-1' to be fetched and installed:
opkg update
Check the architecture you're using by executing:
grep DISTRIB_ARCH /etc/openwrt_release
Get the 'nfs-kernel-server_2.1.1-1' for your architecture. In my case it's 'arm_cortex-a9_vfpv3' as I'm using Linksys WRT32X. Replace the <DISTRIB_ARCH> with proper value in command below:
logread | grep nfsd
Sat Jun 8 09:23:42 2019 kern.info kernel: [ 7.555859] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Sat Jun 8 09:23:44 2019 kern.warn kernel: [ 16.805921] NFSD: the nfsdcld client tracking upcall will be removed in 3.10. Please transition to using nfsdcltrack.
logread | grep rpc
Sat Jun 8 09:23:44 2019 daemon.notice rpc.mountd[2872]: Version 2.1.1 starting
Sat Jun 8 09:23:44 2019 daemon.notice rpc.statd[2871]: Version 2.1.1 starting
Sat Jun 8 09:23:44 2019 daemon.warn rpc.statd[2871]: Flags: No-Daemon
Sat Jun 8 09:23:44 2019 daemon.notice rpc.statd[2871]: Initializing NSM state
Sat Jun 8 09:23:44 2019 daemon.warn rpc.statd[2871]: Running as root. chown /var/lib/nfs to choose different user
I'm also able to PXE boot with resources shared over NFS.
For the "conflicts" - you have to run 'opkg update' prior to installing the .ipk package - the error you get informs you that opkg wasn't able to find required packages in the repository. It is covered by point 2. in the instruction I wrote. You have to remember that opkg local package repository is cleared every time you reboot.