NFS Issues after Truenas Core to Scale dragonfish upgrade

TrueNAS General
1

Ok so I bit the bullet and moved from core to scale. My plan was to migrate to Dragonfish, the last supported in-place upgrade, and then move up from there.

After the upgrade, SMB is working well. NFS however, not so much.

The NFS service is refusing to start, and the the issue appears to be with rpcbind.

rpcbind is running as `/sbin/rpcbind -f -w -h 10.0.0.241`. At one time, long past that was the address of my Core system, but its been 192.168.20.241 for at least 5 years now.

Googling around I see that the problem appears to be a host=10.0.0.241 entry in /etc/nfsd.conf.d/local.conf.
I removed that and rebooted, but it made no difference. Also tried change it to 0.0.0.0 with no effect. After the restart the host= entry returns like a bad smell.

After more searching it seems that the address to bind to is now specified in /usr/lib/systemd/system/rpcbind.socket, but that file is as vanilla as could be and does not mention the 10.0.0.241 address anywhere.

Does anyone have a clue where this rpcbind parameter might be coming from?

2

/etc/init.d/rpcbind sources /etc/defaults/rpcbind if it exists. It does exist and has the offending -h option in it. So i removed it the option, but after a reboot it was back. Renaming that file caused rpcbind to come up without the address.

Now similar but different problem
rpc.nfsd: unable to bind AF_INET TCP socket: errno 99 (Cannot assign requested address)

Again the issue is a host= parameter in /etc/nfs.conf.d/local.conf, and again it comes back when deleted.

Too late to debug now. Will try again tomorrow

3

So I couldn’t work this out, so I bit the bullet and downloaded the latest scale version “goldeneye”. Installed it as a cold install and then imported the config I had saved from my old core setup.

NFS issue was still there after this.

So…. looking around the gui I clicked on the three-dots right of the “NFS Shares” panel. Under that is “config” and that is where I found the bind address item with the wrong address in it. Removed the content of that field, saved the config and restarted NFS and it’s all now working.