NFS service not working after migration from TrueNAS 13.3 to TrueNAS 24.10

TrueNAS General
1

Hi there,

I recently migrated my NAS from TrueNAS 13.3 to TrueNAS 24.10 (new install from scratch + upload of the saved parameters from the older to the newer system).

After the migration, the NFS service does not start anymore. It show the following error message:

[EFAULT] Dec 08 10:54:23 systemd[1]: Starting nfs-server.service - NFS server and services… Dec 08 10:54:23 rpc.nfsd[2693]: rpc.nfsd: unable to bind AF_INET TCP socket: errno 99 (Cannot assign requested address) Dec 08 10:54:23 rpc.nfsd[2693]: rpc.nfsd: unable to set any sockets for nfsd Dec 08 10:54:23 systemd[1]: nfs-server.service: Main process exited, code=exited, status=1/FAILURE Dec 08 10:54:23 systemd[1]: nfs-server.service: Failed with result ‘exit-code’. Dec 08 10:54:23 systemd[1]: Stopped nfs-server.service - NFS server and services. Dec 08 14:30:12 systemd[1]: Starting nfs-server.service - NFS server and services… Dec 08 14:30:12 rpc.nfsd[2533]: rpc.nfsd: unable to bind AF_INET TCP socket: errno 99 (Cannot assign requested address) Dec 08 14:30:12 rpc.nfsd[2533]: rpc.nfsd: unable to set any sockets for nfsd Dec 08 14:30:12 systemd[1]: nfs-server.service: Main process exited, code=exited, status=1/FAILURE Dec 08 14:30:12 systemd[1]: nfs-server.service: Failed with result ‘exit-code’. Dec 08 14:30:12 systemd[1]: Stopped nfs-server.service - NFS server and services. Dec 08 14:40:40 systemd[1]: Starting nfs-server.service - NFS server and services… Dec 08 14:40:40 rpc.nfsd[2697]: rpc.nfsd: unable to bind AF_INET TCP socket: errno 99 (Cannot assign requested address) Dec 08 14:40:40 rpc.nfsd[2697]: rpc.nfsd: unable to set any sockets for nfsd Dec 08 14:40:40 systemd[1]: nfs-server.service: Main process exited, code=exited, status=1/FAILURE Dec 08 14:40:40 systemd[1]: nfs-server.service: Failed with result ‘exit-code’. Dec 08 14:40:40 systemd[1]: Stopped nfs-server.service - NFS server and services. Dec 08 14:48:42 systemd[1]: Starting nfs-server.service - NFS server and services… Dec 08 14:48:42 rpc.nfsd[2600]: rpc.nfsd: unable to bind AF_INET TCP socket: errno 99 (Cannot assign requested address) Dec 08 14:48:42 rpc.nfsd[2600]: rpc.nfsd: unable to set any sockets for nfsd Dec 08 14:48:42 systemd[1]: nfs-server.service: Main process exited, code=exited, status=1/FAILURE Dec 08 14:48:42 systemd[1]: nfs-server.service: Failed with result ‘exit-code’. Dec 08 14:48:42 systemd[1]: Stopped nfs-server.service - NFS server and services. Dec 08 23:26:31 systemd[1]: Starting nfs-server.service - NFS server and services… Dec 08 23:26:31 rpc.nfsd[17143]: rpc.nfsd: unable to bind AF_INET TCP socket: errno 99 (Cannot assign requested address) Dec 08 23:26:31 rpc.nfsd[17143]: rpc.nfsd: unable to set any sockets for nfsd Dec 08 23:26:31 systemd[1]: nfs-server.service: Main process exited, code=exited, status=1/FAILURE Dec 08 23:26:31 systemd[1]: nfs-server.service: Failed with result ‘exit-code’. Dec 08 23:26:31 systemd[1]: Stopped nfs-server.service - NFS server and services. Dec 08 23:40:40 systemd[1]: Starting nfs-server.service - NFS server and services… Dec 08 23:40:40 rpc.nfsd[30031]: rpc.nfsd: unable to bind AF_INET TCP socket: errno 99 (Cannot assign requested address) Dec 08 23:40:40 rpc.nfsd[30031]: rpc.nfsd: unable to set any sockets for nfsd Dec 08 23:40:40 systemd[1]: nfs-server.service: Main process exited, code=exited, status=1/FAILURE Dec 08 23:40:40 systemd[1]: nfs-server.service: Failed with result ‘exit-code’. Dec 08 23:40:40 systemd[1]: Stopped nfs-server.service - NFS server and services. Dec 12 14:40:35 systemd[1]: Starting nfs-server.service - NFS server and services… Dec 12 14:40:35 rpc.nfsd[187665]: rpc.nfsd: unable to bind AF_INET TCP socket: errno 99 (Cannot assign requested address) Dec 12 14:40:35 rpc.nfsd[187665]: rpc.nfsd: unable to set any sockets for nfsd Dec 12 14:40:35 systemd[1]: nfs-server.service: Main process exited, code=exited, status=1/FAILURE Dec 12 14:40:35 systemd[1]: nfs-server.service: Failed with result ‘exit-code’. Dec 12 14:40:35 systemd[1]: Stopped nfs-server.service - NFS server and services.

I also cannot save the settings for the NFS service. When I click on save after editing the settings, I get the following error message:

[EINVAL] nfs_update.bindip.0: Please provide a valid ip address

Could you please help on how to solve this problem ?

Thanks in advance,
Olivier.

2

It sounds like maybe you’ve configured NFS to bind to an IP the server doesn’t have anymore. Did your IP addresses change after migration? What’s output of midclt call nfs.config?

3

Thanks for your prompt reply.

Here is the output of the midclt command:

{“id”: 1, “servers”: 2, “allow_nonroot”: false, “protocols”: [“NFSV3”], “v4_v3owner”: false, “v4_krb”: false, “bindip”: [“192.168.0.10”], “mountd_port”: null, “rpcstatd_port”: null, “rpclockd_port”: null, “mountd_log”: false, “statd_lockd_log”: false, “v4_domain”: “”, “v4_krb_enabled”: false, “userd_manage_gids”: false, “v4_owner_major”: “”, “keytab_has_nfs_spn”: false, “managed_nfsd”: true}

I did not change the server ip address as part as the migration. The system’s ipv4 address is 192.168.2.10

The 192.168.0.10 that appears in the output is probably quite old, as I moved to 192.168.2.* a while ago

4

Perhaps you uploaded the wrong configuration file. Anyway, that’s why NFS isn’t starting.

5

I could not find a way to change to change this bindip parameter in the user interface.

Do you know how to proceed?

6

Should be visible as an option. If you need to do this quickly midclt call nfs.update '{"bindip": []}'

7

Problem solved! Thank you so much for your help

8

No problem. I confirmed this appears to be a UI bug (preventing removing invalid bind ips).