nfsd: can't register svc name

Status
Not open for further replies.

ObiTobi

Patron
Joined
Jul 12, 2013
Messages
316
Hi,

after latest Update FreeNAS-9.10-STABLE-201606270534 (dd17351) I have always this message on boot

ps -J 0 -af | grep rpc
2100 - Is 0:00.02 /usr/sbin/rpcbind
2741 - Ss 0:00.02 /usr/sbin/rpc.statd
2744 - Ss 0:00.03 /usr/sbin/rpc.lockd

On NFS Config I have only "Enable NFS v4" checkbox enabled
 
D

dlavigne

Guest
Is the ps and its output the message or is that you looking to see if the services are started?
 
D

dlavigne

Guest
What is the exact problem you want assistance with? eg what is not working and how do you have it configured?
 

memel.parduin

Dabbler
Joined
Feb 13, 2012
Messages
42
Same here.

Current config: FreeNAS-9.10-STABLE-201606270534 (dd17351), AMD Athlon II X2 270, Asus M4A88T-M, 4x 4GB DDR3 Kingston ValueRam, RAID-Z2 6x 3TB WD Red WD30EFRX, 2x 8GB Sandisk Cruzer Fit

I have a couple of NFS shares, default configured, which I can successfully mount on my Ubuntu 16.04 system.

However, after a certain amount of time (usually the night), all of my shares become unresponsive. Restarting nfsd is needed to get them working again. I've been trying to find out what possibly could go wrong here, but I'm still a bit of a noob. However, the error message shown at nfsd startup is new to me, so I wonder if that could be a pointer to whatever is causing this.

Perhaps any of you boys&girls can help me solve this. If there's any more info I can provide please let me know.
 

memel.parduin

Dabbler
Joined
Feb 13, 2012
Messages
42
[root@audhumla] ~# cat /var/log/messages | grep svc
Jul 21 03:03:58 audhumla nfsd: can't register svc name
Jul 21 03:04:38 audhumla nfsd: can't register svc name
Jul 21 13:36:41 audhumla nfsd: can't register svc name
Jul 21 14:53:33 audhumla nfsd: can't register svc name
Jul 22 03:03:59 audhumla nfsd: can't register svc name
Jul 22 03:04:37 audhumla nfsd: can't register svc name
Jul 22 19:48:49 audhumla nfsd: can't register svc name
Jul 23 03:04:08 audhumla nfsd: can't register svc name
Jul 23 03:04:47 audhumla nfsd: can't register svc name
Jul 23 09:18:57 audhumla nfsd: can't register svc name
Jul 23 10:18:07 audhumla nfsd: can't register svc name

[root@audhumla] ~# cat /var/log/messages | grep nfs
Jul 21 03:03:58 audhumla nfsd[1624]: can't bind udp addr 10.8.0.1: Can't assign requested address
Jul 21 03:03:58 audhumla nfsd: can't register svc name
Jul 21 03:04:37 audhumla nfsd[7717]: can't bind udp addr 10.8.0.1: Can't assign requested address
Jul 21 03:04:38 audhumla nfsd: can't register svc name
Jul 21 13:36:41 audhumla notifier: nfsd not running? (check /var/run/nfsd.pid).
Jul 21 13:36:41 audhumla notifier: nfsuserd not running?
Jul 21 13:36:41 audhumla notifier: Starting nfsuserd.
Jul 21 13:36:41 audhumla notifier: Starting nfsd.
Jul 21 13:36:41 audhumla nfsd: can't register svc name
Jul 21 14:53:32 audhumla notifier: Stopping nfsd.
Jul 21 14:53:33 audhumla notifier: Stopping nfsuserd.
Jul 21 14:53:33 audhumla notifier: Starting nfsuserd.
Jul 21 14:53:33 audhumla notifier: Starting nfsd.
Jul 21 14:53:33 audhumla nfsd: can't register svc name
Jul 22 03:03:58 audhumla nfsd[1632]: can't bind udp addr 10.8.0.1: Can't assign requested address
Jul 22 03:03:59 audhumla nfsd: can't register svc name
Jul 22 03:04:37 audhumla nfsd: can't register svc name
Jul 22 19:48:49 audhumla notifier: Stopping nfsd.
Jul 22 19:48:49 audhumla notifier: Stopping nfsuserd.
Jul 22 19:48:49 audhumla notifier: Starting nfsuserd.
Jul 22 19:48:49 audhumla notifier: Starting nfsd.
Jul 22 19:48:49 audhumla nfsd: can't register svc name
Jul 23 03:04:08 audhumla nfsd[1632]: can't bind udp addr 10.8.0.1: Can't assign requested address
Jul 23 03:04:08 audhumla nfsd: can't register svc name
Jul 23 03:04:47 audhumla nfsd[7721]: can't bind udp addr 10.8.0.1: Can't assign requested address
Jul 23 03:04:47 audhumla nfsd: can't register svc name
Jul 23 09:18:57 audhumla notifier: nfsd not running? (check /var/run/nfsd.pid).
Jul 23 09:18:57 audhumla notifier: Stopping nfsuserd.
Jul 23 09:18:57 audhumla notifier: Starting nfsuserd.
Jul 23 09:18:57 audhumla notifier: Starting nfsd.
Jul 23 09:18:57 audhumla nfsd: can't register svc name
Jul 23 09:19:37 audhumla notifier: Stopping nfsd.
Jul 23 09:19:37 audhumla notifier: Stopping nfsuserd.
Jul 23 10:18:02 audhumla notifier: nfsd not running? (check /var/run/nfsd.pid).
Jul 23 10:18:03 audhumla notifier: nfsuserd not running?
Jul 23 10:18:07 audhumla notifier: Starting nfsuserd.
Jul 23 10:18:07 audhumla notifier: Starting nfsd.
Jul 23 10:18:07 audhumla nfsd: can't register svc name


Looks like nfsd protests on not finding 10.8.0.1 bind address? I'll try and disable that one to see what happens.
 

memel.parduin

Dabbler
Joined
Feb 13, 2012
Messages
42
Ok, a little step further I guess.

[root@audhumla] ~# cat /var/log/messages | grep svc
Jul 24 03:03:47 audhumla nfsd: can't register svc name
[root@audhumla] ~# cat /var/log/messages | grep nfs
Jul 24 03:03:47 audhumla nfsd: can't register svc name
Jul 24 03:04:27 audhumla nfsd[7732]: Can't read stable storage file: Operation not permitted


This last message is new, so I had a look at my periodic snapshot tasks. It appears that my system takes a snapshot of my postgresql jail every night at 03:03. I use this jail for my davical server I'm running. But I can't see how that possibly could affect NFS.

Running the command ObiTobi does in his post shows:

[root@audhumla] ~# ps -J 0 -af | grep rpc
1377 - Is 0:00.03 /usr/sbin/rpcbind -h 192.168.178.16
1635 - Ss 0:00.02 /usr/sbin/rpc.statd -h 192.168.178.16
1638 - Ss 0:00.02 /usr/sbin/rpc.lockd


So for tonight I'll disable the snapshot task on zpool1/jails/postgresql. Next episode tomorrow ;)
 

memel.parduin

Dabbler
Joined
Feb 13, 2012
Messages
42
Well...

Everything still the same, disabling the snapshot task didn't make any difference at all.

[root@audhumla] ~# cat /var/log/messages | grep nfs
Jul 24 03:03:47 audhumla nfsd: can't register svc name
Jul 24 03:04:27 audhumla nfsd[7732]: Can't read stable storage file: Operation not permitted


Also at the same time. I tried to login to my Ubuntu 16.04 client, which mounts my NFS shares at boot/logon, but it became completely unresponsive after entering my credentials. Had to reboot the whole lot. :(

Any suggestions anyone? It'd be much appreciated :)
 

Ludensen

Cadet
Joined
Mar 12, 2016
Messages
6
As this thread was the first result when googling the "error message" that names this thread.
Here's an answer regarding the "nfsd: cant register svc name"-message

Citating from this entry on the bug-tracker:
It's not a bug or an error even. It's just an informative message.
In plain language it means no Kerberos tickets are configured.
 
Last edited:

csj

iXsystems
iXsystems
Joined
Oct 20, 2017
Messages
18
What bugs me about this is this particular error message:

Code:
Jul 24 03:04:27 audhumla nfsd[7732]: Can't read stable storage file: Operation not permitted


In NFSv4 land, the nfsd process opens up a nfs-stablerestart file as well as a nfs-stablerestart.bak that lives in a directory at /var/db

If the nfsd process can't open this file, it will fail with the error message you are seeing in your log file, and your nfs shares will go into a catatonic state. Make sure the physical disk in which /var/db is stored isn't failing. Also make sure nothing else on the server is touching those files.
 
Status
Not open for further replies.
Top