When my TW, 15.3, Fedora, Debian, Mageia, etc. test boxes on LAN boot I have an alias to connect them manually to my server, this 15.2 PC, as needed, with content taking the form:
mount servername:/exportname
Since zypper up last night, attempts from clients to connect bring this response:
Created symlink /run/systemd/system/remote-fs.target.wants/rpc-statd.service -> /usr/lib/systemd/system/rpc-statd.service.
mount.nfs: requested NFS version or transport protocol is not supported
Only nfs string on client end in journal is:
<date/time> <hostname> kernel: Netfs 'nfs' registered for caching
On server, result is similarly uninformative:
# journalctl -b | grep nfs
Aug 03 01:14:34 00srv systemd[1]: nfs-server.service: Failed with result 'exit-code'.
# systemctl status nfs-server
● nfs-server.service - NFS server and services
Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled; vendor preset: disabled)
Drop-In: /usr/lib/systemd/system/nfs-server.service.d
└─nfsserver.conf, options.conf
/run/systemd/generator/nfs-server.service.d
└─order-with-mounts.conf
Active: failed (Result: exit-code) since Tue 2021-08-03 01:14:34 EDT; 18h ago
Aug 03 01:14:34 00srv systemd[1]: nfs-server.service: Failed with result 'exit-code'.
# cat /etc/nfsserver.conf
cat: /etc/nfsserver.conf: No such file or directory
# lsmod | grep nfs
nfsd 438272 1
auth_rpcgss 110592 1 nfsd
nfs_acl 16384 1 nfsd
lockd 114688 1 nfsd
grace 16384 2 nfsd,lockd
sunrpc 479232 5 nfsd,auth_rpcgss,lockd,nfs_acl
# uname -r
5.3.18-lp152.84-default
# showmount -e
clnt_create: RPC: Program not registered
Clients have fstab entries of the form:
servername:/exportname <mountpoint> nfs [ro,rw],noauto,nosuid,soft,rsize=8192,wsize=8192 0 0
/etc/exports on server was last written 6 years ago. Today is first failure ever noted.
What needs to be changed to fix this?