[support] last night's 15.2 updates killed NFS server
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:
On 04/08/2021 03.58, Felix Miata wrote: ...
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'.
That IS informative. It would be better if it also printed what exit-code, but...
Additional data:
# 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'.
Well, the next step I would do is "systemctl start nfs-server" and then status, and look at the journal. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Carlos E. R. composed on 2021-08-04 04:06 (UTC+0200):
Felix Miata wrote:
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'.
That IS informative. It would be better if it also printed what exit-code, but...
Useless information without the code or what the code means. :(
Additional data:
# 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'.
Well, the next step I would do is "systemctl start nfs-server" and then status, and look at the journal.
# systemctl start nfs-server Job for nfs-server.service canceled. # 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 22:51:45 EDT; 1min 25s ago Process: 14242 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS) Process: 14239 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS) Process: 14238 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE) Aug 03 22:51:45 00srv systemd[1]: nfs-server.service: Failed with result 'exit-code'. 00srv:~ # journalctl -b | tail -n# Aug 03 22:51:45 00srv rpc.mountd[14228]: Could not make a socket: (97) Address family not supported by protocol Aug 03 22:51:45 00srv rpc.mountd[14228]: Could not make a socket: (97) Address family not supported by protocol Aug 03 22:51:45 00srv rpc.mountd[14228]: Could not make a socket: (97) Address family not supported by protocol Aug 03 22:51:45 00srv rpc.mountd[14228]: Could not make a socket: (97) Address family not supported by protocol Aug 03 22:51:45 00srv rpc.mountd[14228]: Could not make a socket: (97) Address family not supported by protocol Aug 03 22:51:45 00srv rpc.mountd[14228]: Could not make a socket: (97) Address family not supported by protocol Aug 03 22:51:45 00srv systemd[1]: nfs-server.service: Failed with result 'exit-code'. Is 97 an exit code? If yes, where does one discover its meaning? # systemctl list-sockets | egrep 'nfs|rpc|ount' /run/rpcbind.sock rpcbind.socket rpcbind.service 0.0.0.0:111 rpcbind.socket rpcbind.service 0.0.0.0:111 rpcbind.socket rpcbind.service # systemctl status rpcbind.socket ● rpcbind.socket - RPCbind Server Activation Socket Loaded: loaded (/usr/lib/systemd/system/rpcbind.socket; enabled; vendor preset: disabled) Active: active (running) since Tue 2021-08-03 01:14:25 EDT; 21h ago Listen: /run/rpcbind.sock (Stream) 0.0.0.0:111 (Stream) 0.0.0.0:111 (Datagram) Tasks: 0 CGroup: /rpcbind.socket Clear as mud where to look or what to look for. :( -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 04.08.2021 06:03, Felix Miata wrote:
Carlos E. R. composed on 2021-08-04 04:06 (UTC+0200):
Felix Miata wrote:
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'.
That IS informative. It would be better if it also printed what exit-code, but...
Useless information without the code or what the code means. :(
Additional data:
# 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'.
Well, the next step I would do is "systemctl start nfs-server" and then status, and look at the journal.
# systemctl start nfs-server Job for nfs-server.service canceled. # 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 22:51:45 EDT; 1min 25s ago Process: 14242 ExecStopPost=/usr/sbin/exportfs -f (code=exited, status=0/SUCCESS) Process: 14239 ExecStopPost=/usr/sbin/exportfs -au (code=exited, status=0/SUCCESS) Process: 14238 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=1/FAILURE)
Aug 03 22:51:45 00srv systemd[1]: nfs-server.service: Failed with result 'exit-code'. 00srv:~ # journalctl -b | tail -n# Aug 03 22:51:45 00srv rpc.mountd[14228]: Could not make a socket: (97) Address family not supported by protocol Aug 03 22:51:45 00srv rpc.mountd[14228]: Could not make a socket: (97) Address family not supported by protocol Aug 03 22:51:45 00srv rpc.mountd[14228]: Could not make a socket: (97) Address family not supported by protocol Aug 03 22:51:45 00srv rpc.mountd[14228]: Could not make a socket: (97) Address family not supported by protocol Aug 03 22:51:45 00srv rpc.mountd[14228]: Could not make a socket: (97) Address family not supported by protocol Aug 03 22:51:45 00srv rpc.mountd[14228]: Could not make a socket: (97) Address family not supported by protocol Aug 03 22:51:45 00srv systemd[1]: nfs-server.service: Failed with result 'exit-code'.
Is 97 an exit code?
No, it is not. Exit code is 1 of command "exportfs -r" as is clearly printed by "systemctl status nfs-server".
If yes, where does one discover its meaning?
It tells you in plain text - "Address family is not supported by protocol". Educated guess is that it attempts to create IPv6 listening socket and fails.
# systemctl list-sockets | egrep 'nfs|rpc|ount' /run/rpcbind.sock rpcbind.socket rpcbind.service 0.0.0.0:111 rpcbind.socket rpcbind.service 0.0.0.0:111 rpcbind.socket rpcbind.service # systemctl status rpcbind.socket ● rpcbind.socket - RPCbind Server Activation Socket Loaded: loaded (/usr/lib/systemd/system/rpcbind.socket; enabled; vendor preset: disabled) Active: active (running) since Tue 2021-08-03 01:14:25 EDT; 21h ago Listen: /run/rpcbind.sock (Stream) 0.0.0.0:111 (Stream) 0.0.0.0:111 (Datagram) Tasks: 0 CGroup: /rpcbind.socket
Clear as mud where to look or what to look for. :(
Felix Miata composed on 2021-08-03 21:58 (UTC-0400): ... I also asked on https://forums.opensuse.org/showthread.php/557862-last-night-s-updates-kille... where ultimately it was found removing /etc/sysconfig/nfs, which did not belong to any package/rpm, solved the problem. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 04/08/2021 23.08, Felix Miata wrote:
Felix Miata composed on 2021-08-03 21:58 (UTC-0400): ... I also asked on https://forums.opensuse.org/showthread.php/557862-last-night-s-updates-kille... where ultimately it was found removing /etc/sysconfig/nfs, which did not belong to any package/rpm, solved the problem.
That seems to me to be the wrong move. Instead, you have to edit the file and find the offending setting. The file doesn't come from any rpm, that is well known. It comes from "/usr/share/fillup-templates/sysconfig.nfs", which in turn is installed by nfs-client.rpm YaST would edit that sysconfig file. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Carlos E. R. composed on 2021-08-04 23:38 (UTC+0200):
On Felix Miata wrote:
Felix Miata composed on 2021-08-03 21:58 (UTC-0400): ... I also asked on https://forums.opensuse.org/showthread.php/557862-last-night-s-updates-kille... where ultimately it was found removing /etc/sysconfig/nfs, which did not belong to any package/rpm, solved the problem.
That seems to me to be the wrong move.
Instead, you have to edit the file and find the offending setting.
I did a diff between the (then) current version and the previous version, which showed nothing different that was not a comment line, so that looked like a very tough approach to troubleshooting.
The file doesn't come from any rpm, that is well known. It comes from "/usr/share/fillup-templates/sysconfig.nfs", which in turn is installed by nfs-client.rpm
YaST would edit that sysconfig file.
Given # rpm -q --whatprovides /etc/sysconfig/nfs file /etc/sysconfig/nfs is not owned by any package and dcurtisfra's response #5 in the forum thread and the non-diff diff it seemed perfectly reasonable to try eliminating it. YaST in my eyes is a convenience, not a requirement, so one ought to be able to find a solution without using it if desired. IIRC, if I ever used YaST to configure NFS, it would have been many many moons ago, maybe around SuSE 8.2. It's harder to learn things using the easy way, which be YaST. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 05/08/2021 00.25, Felix Miata wrote:
Carlos E. R. composed on 2021-08-04 23:38 (UTC+0200):
On Felix Miata wrote:
Felix Miata composed on 2021-08-03 21:58 (UTC-0400): ... I also asked on https://forums.opensuse.org/showthread.php/557862-last-night-s-updates-kille... where ultimately it was found removing /etc/sysconfig/nfs, which did not belong to any package/rpm, solved the problem.
That seems to me to be the wrong move.
Instead, you have to edit the file and find the offending setting.
I did a diff between the (then) current version and the previous version, which showed nothing different that was not a comment line, so that looked like a very tough approach to troubleshooting.
The file doesn't come from any rpm, that is well known. It comes from "/usr/share/fillup-templates/sysconfig.nfs", which in turn is installed by nfs-client.rpm
YaST would edit that sysconfig file.
Given # rpm -q --whatprovides /etc/sysconfig/nfs file /etc/sysconfig/nfs is not owned by any package and dcurtisfra's response #5 in the forum thread and the non-diff diff it seemed perfectly reasonable to try eliminating it.
IMHO, that is not correct.
YaST in my eyes is a convenience, not a requirement, so one ought to be able to find a solution without using it if desired. IIRC, if I ever used YaST to configure NFS, it would have been many many moons ago, maybe around SuSE 8.2. It's harder to learn things using the easy way, which be YaST.
It doesn't need to be yast. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
Carlos E. R. composed on 2021-08-05 00:28 (UTC+0200):
Felix Miata wrote:
Given # rpm -q --whatprovides /etc/sysconfig/nfs file /etc/sysconfig/nfs is not owned by any package and dcurtisfra's response #5 in the forum thread and the non-diff diff it seemed perfectly reasonable to try eliminating it.
IMHO, that is not correct.
Mine is on https://paste.opensuse.org/view/raw/76320380 Assuming NFS works for you, maybe you'd like to diff yours to mine, or upload yours so I can diff. Maybe there's a difference that isn't a comment. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 05/08/2021 00.54, Felix Miata wrote:
Carlos E. R. composed on 2021-08-05 00:28 (UTC+0200):
Felix Miata wrote:
Given # rpm -q --whatprovides /etc/sysconfig/nfs file /etc/sysconfig/nfs is not owned by any package and dcurtisfra's response #5 in the forum thread and the non-diff diff it seemed perfectly reasonable to try eliminating it.
IMHO, that is not correct.
Mine is on https://paste.opensuse.org/view/raw/76320380 Assuming NFS works for you, maybe you'd like to diff yours to mine, or upload yours so I can diff. Maybe there's a difference that isn't a comment.
My nfs client starts, but I'm not home and it has nowhere to connect to. minas-tirith:~ # egrep -v "^[[:space:]]*$|^#" /etc/sysconfig/nfs USE_KERNEL_NFSD_NUMBER="4" MOUNTD_PORT="" NFS_SECURITY_GSS="no" NFS4_SUPPORT="yes" SM_NOTIFY_OPTIONS="" NFS_START_SERVICES="no" NFS3_SERVER_SUPPORT="yes" STATD_OPTIONS="" NFS4_SERVER_MINOR_VERSION="0" NFSV4LEASETIME="" RPC_PIPEFS_DIR="" SVCGSSD_OPTIONS="" NFSD_OPTIONS="" GSSD_OPTIONS="" MOUNTD_OPTIONS="--manage-gids" NFS_GSSD_AVOID_DNS="no" STATD_PORT="" STATD_HOSTNAME="" LOCKD_TCPPORT="" LOCKD_UDPPORT="" minas-tirith:~ # -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
participants (3)
-
Andrei Borzenkov -
Carlos E. R. -
Felix Miata