matthew_eli
Senior Member
Hi all,
I encountered a problem I've not faced before with RT-N66U about the built-in NFS server; using NFS server in RT-AC68U and setting it like I had in RT-N66U, results in no NFS server at the router boot. Let me explain better; I use NFS for mounting the Hard Disk on USB and then reading it by my WDTV Live over ethernet. When I had Rt-N66U I set the NFS as in the following image:

and all works flawlessly, since from the router boot. Instead, with my new RT-AC68U, .38_1 firmware by Merlin, using the same settings, I need to manually turn off and on the NFS exports or simply changing any settings of it for having the export mount seen by my WDTV. Most probably using the WDTV is not the best way to debug if the NFS exports are working normally and thus I would ask you a way for testing it effectively.
I enclose in the following what log reports for the NFS:
When I change the settings and the service starts correctly (at least it is accessible by WDTV):
When the service starts at boot (there are 2 differents date, but it's for the NTP read, it happens all in few seconds):
Could you help me in figuring this problem out?
I encountered a problem I've not faced before with RT-N66U about the built-in NFS server; using NFS server in RT-AC68U and setting it like I had in RT-N66U, results in no NFS server at the router boot. Let me explain better; I use NFS for mounting the Hard Disk on USB and then reading it by my WDTV Live over ethernet. When I had Rt-N66U I set the NFS as in the following image:

and all works flawlessly, since from the router boot. Instead, with my new RT-AC68U, .38_1 firmware by Merlin, using the same settings, I need to manually turn off and on the NFS exports or simply changing any settings of it for having the export mount seen by my WDTV. Most probably using the WDTV is not the best way to debug if the NFS exports are working normally and thus I would ask you a way for testing it effectively.
I enclose in the following what log reports for the NFS:
When I change the settings and the service starts correctly (at least it is accessible by WDTV):
Code:
Jan 13 09:20:03 statd[2339]: Version 1.1.6 Starting
Jan 13 09:20:03 statd[2339]: statd running as root. chown /var/lib/nfs/sm to choose different user
Jan 13 09:20:03 kernel: svc: failed to register lockdv1 RPC service (errno 97).
When the service starts at boot (there are 2 differents date, but it's for the NTP read, it happens all in few seconds):
Code:
Jan 1 01:00:43 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Jan 1 01:00:43 kernel: Installing knfsd (copyright (C) 1996 [email protected]).
...
Jan 1 01:00:44 statd[1202]: statd running as root. chown /var/lib/nfs/sm to choose different user
Jan 1 01:00:44 kernel: svc: failed to register lockdv1 RPC service (errno 97).
...
Jan 12 16:40:59 mountd[1218]: Caught signal 15, un-registering and exiting.
Jan 12 16:40:59 kernel: nfsd: last server has exited, flushing export cache
...
Jan 12 16:41:54 kernel: svc: failed to register nfsdv3 RPC service (errno 111).
Jan 12 16:41:54 kernel: nfsd: last server has exited, flushing export cache
Jan 12 16:41:54 nfsd[1531]: nfssvc: writing fds to kernel failed: errno 111 (Connection refused)
Jan 12 16:41:54 kernel: svc: failed to register nfsdv3 RPC service (errno 111).
Jan 12 16:41:54 nfsd[1531]: nfssvc: writing fds to kernel failed: errno 111 (Connection refused)
Jan 12 16:41:54 kernel: nfsd: last server has exited, flushing export cache
Jan 12 16:41:54 kernel: nfsd: last server has exited, flushing export cache
Jan 12 16:41:54 nfsd[1531]: nfssvc: Address already in use
Jan 12 16:41:55 mountd[1541]: unable to register (mountd, 1, udp).
Could you help me in figuring this problem out?