[opensuse] Can't mount NFS
OpenSUSE Tumbleweed 20181116 My NFS recently stopped working and I don't know why. I haven't changed anything. Here is what happens when I try a local mount (I'm on madhatter 192.168.2.1): root@madhatter:~# exportfs /home 192.168.0.0/255.255.0.0 /software 192.168.0.0/255.255.0.0 /multimedia 192.168.0.0/255.255.0.0 root@madhatter:~# mount 192.168.2.1:/home/mounts/build /mnt mount.nfs: requested NFS version or transport protocol is not supported root@madhatter:~# In the output of journalctl -f I get: Nov 18 22:44:07 madhatter rpc.gssd[948]: ERROR: can't open nfs/clnt1b/info: Invalid argument Nov 18 22:44:07 madhatter rpc.gssd[948]: ERROR: failed to parse nfs/clnt1b/info Nov 18 22:44:07 madhatter rpc.gssd[948]: ERROR: can't openat nfs/clnt1b: No such file or directory Nov 18 22:44:07 madhatter rpc.gssd[948]: ERROR: can't openat nfs/clnt1b: No such file or directory What is this? I do have Kerberos set up but I'm just trying to do a mount without Kerberos. I'm not sure what this rpc.gssd process is or whether it is screwing things up. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, 19 Nov 2018 08:26:48 -0800 Scott Simpson <ssimpson@alumni.usc.edu> wrote:
OpenSUSE Tumbleweed 20181116
My NFS recently stopped working and I don't know why. I haven't changed anything. Here is what happens when I try a local mount (I'm on madhatter 192.168.2.1):
root@madhatter:~# exportfs /home 192.168.0.0/255.255.0.0 /software 192.168.0.0/255.255.0.0 /multimedia 192.168.0.0/255.255.0.0
what is the full contents of /etc/exports?
root@madhatter:~# mount 192.168.2.1:/home/mounts/build /mnt mount.nfs: requested NFS version or transport protocol is not supported root@madhatter:~#
mount -v might show more information.
In the output of journalctl -f I get:
Nov 18 22:44:07 madhatter rpc.gssd[948]: ERROR: can't open nfs/clnt1b/info: Invalid argument Nov 18 22:44:07 madhatter rpc.gssd[948]: ERROR: failed to parse nfs/clnt1b/info Nov 18 22:44:07 madhatter rpc.gssd[948]: ERROR: can't openat nfs/clnt1b: No such file or directory Nov 18 22:44:07 madhatter rpc.gssd[948]: ERROR: can't openat nfs/clnt1b: No such file or directory
What is this? I do have Kerberos set up but I'm just trying to do a mount without Kerberos. I'm not sure what this rpc.gssd process is or whether it is screwing things up.
I don't know either but google quickly finds http://man7.org/linux/man-pages/man8/gssd.8.html so I strongly suspect its something to do with kerberos. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Did some debugging. Looks like it isn't listening on rpcinfo: root@madhatter:/people/ssimpson# mount -v 192.168.2.1:/home/mounts/build /mnt mount.nfs: timeout set for Mon Nov 19 11:40:25 2018 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.2.1,clientaddr=192.168.2.1' mount.nfs: mount(2): Connection refused mount.nfs: trying text-based options 'addr=192.168.2.1' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered Doing a "rpcinfo -p" yields root@madhatter:/people/ssimpson# rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 38320 status 100024 1 tcp 40897 status 100004 2 udp 673 ypserv 100004 1 udp 673 ypserv 100004 2 tcp 673 ypserv 100004 1 tcp 673 ypserv 100007 3 udp 720 ypbind 100007 2 udp 720 ypbind 100007 1 udp 720 ypbind 100007 3 tcp 720 ypbind 100007 2 tcp 720 ypbind 100007 1 tcp 720 ypbind root@madhatter:/people/ssimpson# No NFS. That's odd. Check systemctl: root@madhatter:/people/ssimpson# systemctl status nfsserver ● nfsserver.service - Alias for NFS server Loaded: loaded (/usr/lib/systemd/system/nfsserver.service; enabled; vendor preset: disabled) Active: active (exited) since Sun 2018-11-18 22:01:26 PST; 13h ago Main PID: 1047 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CGroup: /system.slice/nfsserver.service Nov 18 22:01:26 madhatter systemd[1]: Starting Alias for NFS server... Nov 18 22:01:26 madhatter systemd[1]: Started Alias for NFS server. root@madhatter:/people/ssimpson# systemctl status nfs ● nfs.service - Alias for NFS client Loaded: loaded (/usr/lib/systemd/system/nfs.service; enabled; vendor preset: disabled) Drop-In: /run/systemd/generator/nfs.service.d └─50-insserv.conf-$remote_fs.conf Active: active (exited) since Sun 2018-11-18 22:01:26 PST; 13h ago Main PID: 1044 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CGroup: /system.slice/nfs.service Nov 18 22:01:26 madhatter systemd[1]: Starting Alias for NFS client... Nov 18 22:01:26 madhatter systemd[1]: Started Alias for NFS client. root@madhatter:/people/ssimpson# Says started but exited. Checking for those pids: root@madhatter:/people/ssimpson# ps wwuxa |egrep '1044|1047' root 18319 0.0 0.0 5424 216 pts/3 S+ 11:40 0:00 grep -E --color=auto 1044|1047 root@madhatter:/people/ssimpson# Not there. That's odd. Restarting nfsserver. Says to check "journalctl -xe". This yields: Nov 19 11:41:34 madhatter systemd[1]: Starting Kernel Module supporting RPCSEC_GSS... -- Subject: Unit auth-rpcgss-module.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit auth-rpcgss-module.service has begun starting up. Nov 19 11:41:34 madhatter mount[18330]: mount: /home: /dev/mapper/cr_home already mounted on /home. Nov 19 11:41:34 madhatter systemd[1]: home.mount: Mount process exited, code=exited status=32 Nov 19 11:41:34 madhatter systemd[1]: home.mount: Failed with result 'exit-code'. Nov 19 11:41:34 madhatter systemd[1]: Failed to mount /home. -- Subject: Unit home.mount has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit home.mount has failed. -- -- The result is RESULT. Nov 19 11:41:34 madhatter systemd[1]: Dependency failed for NFS server and services. -- Subject: Unit nfs-server.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nfs-server.service has failed. -- -- The result is RESULT. Some kind of dependency failure (my home directory is encrypted and mounted but I did notice an error on boot I didn't see before). Not sure what dependency I'm missing. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I disabled krb5kdc and kadmind with systemctl disable krb5kdc systemctl disable kadmind and removed the package gssproxy (don't know if this made any difference) and rebooted and my nfs server is back up: ssimpson@madhatter:~$ lsmod |grep nfs nfsd 425984 9 nfs_acl 16384 1 nfsd lockd 118784 1 nfsd grace 16384 2 nfsd,lockd auth_rpcgss 73728 3 nfsd,rpcsec_gss_krb5 sunrpc 421888 19 nfsd,auth_rpcgss,lockd,rpcsec_gss_krb5,nfs_acl ssimpson@madhatter:~$ rpcinfo -p |grep nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100227 3 tcp 2049 nfs_acl 100003 3 udp 2049 nfs 100227 3 udp 2049 nfs_acl ssimpson@madhatter:~$ Therefore, my conclusion is that some update decided since I was running Kerberos, my nfs shares should be Kerberized. Changing the behavior when I haven't modified any files doesn't sound like a sound strategy. Anyways, that's what I get for running a bleeding edge distribution (Tumbleweed). Happy that my automounts and nfs are running again. On 11/19/18 11:47 AM, Scott Simpson wrote:
Did some debugging. Looks like it isn't listening on rpcinfo:
root@madhatter:/people/ssimpson# mount -v 192.168.2.1:/home/mounts/build /mnt mount.nfs: timeout set for Mon Nov 19 11:40:25 2018 mount.nfs: trying text-based options 'vers=4.2,addr=192.168.2.1,clientaddr=192.168.2.1' mount.nfs: mount(2): Connection refused mount.nfs: trying text-based options 'addr=192.168.2.1' mount.nfs: prog 100003, trying vers=3, prot=6 mount.nfs: portmap query retrying: RPC: Program not registered mount.nfs: prog 100003, trying vers=3, prot=17 mount.nfs: portmap query failed: RPC: Program not registered
Doing a "rpcinfo -p" yields
root@madhatter:/people/ssimpson# rpcinfo -p program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 38320 status 100024 1 tcp 40897 status 100004 2 udp 673 ypserv 100004 1 udp 673 ypserv 100004 2 tcp 673 ypserv 100004 1 tcp 673 ypserv 100007 3 udp 720 ypbind 100007 2 udp 720 ypbind 100007 1 udp 720 ypbind 100007 3 tcp 720 ypbind 100007 2 tcp 720 ypbind 100007 1 tcp 720 ypbind root@madhatter:/people/ssimpson#
No NFS. That's odd. Check systemctl:
root@madhatter:/people/ssimpson# systemctl status nfsserver ● nfsserver.service - Alias for NFS server Loaded: loaded (/usr/lib/systemd/system/nfsserver.service; enabled; vendor preset: disabled) Active: active (exited) since Sun 2018-11-18 22:01:26 PST; 13h ago Main PID: 1047 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CGroup: /system.slice/nfsserver.service
Nov 18 22:01:26 madhatter systemd[1]: Starting Alias for NFS server... Nov 18 22:01:26 madhatter systemd[1]: Started Alias for NFS server. root@madhatter:/people/ssimpson# systemctl status nfs ● nfs.service - Alias for NFS client Loaded: loaded (/usr/lib/systemd/system/nfs.service; enabled; vendor preset: disabled) Drop-In: /run/systemd/generator/nfs.service.d └─50-insserv.conf-$remote_fs.conf Active: active (exited) since Sun 2018-11-18 22:01:26 PST; 13h ago Main PID: 1044 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 4915) Memory: 0B CGroup: /system.slice/nfs.service
Nov 18 22:01:26 madhatter systemd[1]: Starting Alias for NFS client... Nov 18 22:01:26 madhatter systemd[1]: Started Alias for NFS client. root@madhatter:/people/ssimpson#
Says started but exited. Checking for those pids:
root@madhatter:/people/ssimpson# ps wwuxa |egrep '1044|1047' root 18319 0.0 0.0 5424 216 pts/3 S+ 11:40 0:00 grep -E --color=auto 1044|1047 root@madhatter:/people/ssimpson#
Not there. That's odd. Restarting nfsserver. Says to check "journalctl -xe". This yields:
Nov 19 11:41:34 madhatter systemd[1]: Starting Kernel Module supporting RPCSEC_GSS... -- Subject: Unit auth-rpcgss-module.service has begun start-up -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit auth-rpcgss-module.service has begun starting up. Nov 19 11:41:34 madhatter mount[18330]: mount: /home: /dev/mapper/cr_home already mounted on /home. Nov 19 11:41:34 madhatter systemd[1]: home.mount: Mount process exited, code=exited status=32 Nov 19 11:41:34 madhatter systemd[1]: home.mount: Failed with result 'exit-code'. Nov 19 11:41:34 madhatter systemd[1]: Failed to mount /home. -- Subject: Unit home.mount has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit home.mount has failed. -- -- The result is RESULT. Nov 19 11:41:34 madhatter systemd[1]: Dependency failed for NFS server and services. -- Subject: Unit nfs-server.service has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit nfs-server.service has failed. -- -- The result is RESULT.
Some kind of dependency failure (my home directory is encrypted and mounted but I did notice an error on boot I didn't see before). Not sure what dependency I'm missing.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
19.11.2018 19:26, Scott Simpson пишет:
OpenSUSE Tumbleweed 20181116
My NFS recently stopped working and I don't know why. I haven't changed anything.
And you did not install any updates? Try to recall when it started, check what updates were installed before; try to boot from snapshot preceding these updates.
Here is what happens when I try a local mount (I'm on madhatter 192.168.2.1):
root@madhatter:~# exportfs /home 192.168.0.0/255.255.0.0 /software 192.168.0.0/255.255.0.0 /multimedia 192.168.0.0/255.255.0.0 root@madhatter:~# mount 192.168.2.1:/home/mounts/build /mnt mount.nfs: requested NFS version or transport protocol is not supported root@madhatter:~#
In the output of journalctl -f I get:
Nov 18 22:44:07 madhatter rpc.gssd[948]: ERROR: can't open nfs/clnt1b/info: Invalid argument Nov 18 22:44:07 madhatter rpc.gssd[948]: ERROR: failed to parse nfs/clnt1b/info Nov 18 22:44:07 madhatter rpc.gssd[948]: ERROR: can't openat nfs/clnt1b: No such file or directory Nov 18 22:44:07 madhatter rpc.gssd[948]: ERROR: can't openat nfs/clnt1b: No such file or directory
What is this?
As far as I can tell this simply means that NFS connection went away. I'd start with sniffing network - is there any traffic between client and server at all? Run tcpfump/tshark/wireshark with suitable packet size (you can actually set it to 1500 to capture full packets) during mount and upload somewhere.
I do have Kerberos set up but I'm just trying to do a mount without Kerberos. I'm not sure what this rpc.gssd process is or whether it is screwing things up.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/11/2018 18.54, Andrei Borzenkov wrote:
19.11.2018 19:26, Scott Simpson пишет:
OpenSUSE Tumbleweed 20181116
My NFS recently stopped working and I don't know why. I haven't changed anything.
And you did not install any updates? Try to recall when it started, check what updates were installed before; try to boot from snapshot preceding these updates.
Here is what happens when I try a local mount (I'm on madhatter 192.168.2.1):
root@madhatter:~# exportfs /home 192.168.0.0/255.255.0.0 /software 192.168.0.0/255.255.0.0 /multimedia 192.168.0.0/255.255.0.0 root@madhatter:~# mount 192.168.2.1:/home/mounts/build /mnt mount.nfs: requested NFS version or transport protocol is not supported root@madhatter:~#
One option when mounting nfs is to specify version: (fstab) SomeMachine:/data/nfs/ /data/nfs nfs4 noauto,nofail,_netdev,user,users,lazytime 0 0 "nfs" means nfs version 3. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E.R. wrote:
On 19/11/2018 18.54, Andrei Borzenkov wrote:
19.11.2018 19:26, Scott Simpson пишет:
OpenSUSE Tumbleweed 20181116
My NFS recently stopped working and I don't know why. I haven't changed anything.
And you did not install any updates? Try to recall when it started, check what updates were installed before; try to boot from snapshot preceding these updates.
Here is what happens when I try a local mount (I'm on madhatter 192.168.2.1):
root@madhatter:~# exportfs /home 192.168.0.0/255.255.0.0 /software 192.168.0.0/255.255.0.0 /multimedia 192.168.0.0/255.255.0.0 root@madhatter:~# mount 192.168.2.1:/home/mounts/build /mnt mount.nfs: requested NFS version or transport protocol is not supported root@madhatter:~#
One option when mounting nfs is to specify version:
(fstab) SomeMachine:/data/nfs/ /data/nfs nfs4 noauto,nofail,_netdev,user,users,lazytime 0 0
"nfs" means nfs version 3.
There have been reasons to use that, but given that Scott's setup used to work, that is most likely not a solution here. -- Per Jessen, Zürich (1.2°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/11/2018 20.31, Per Jessen wrote:
Carlos E.R. wrote:
On 19/11/2018 18.54, Andrei Borzenkov wrote:
19.11.2018 19:26, Scott Simpson пишет:
OpenSUSE Tumbleweed 20181116
One option when mounting nfs is to specify version:
(fstab) SomeMachine:/data/nfs/ /data/nfs nfs4 noauto,nofail,_netdev,user,users,lazytime 0 0
"nfs" means nfs version 3.
There have been reasons to use that, but given that Scott's setup used to work, that is most likely not a solution here.
I mean that an update may have changed the default assumptions - he is runnin gTW, after all. I do not mean to use fstab, but there will be a way to specify nfs version in the command line. "mount -v ..." might give more info. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Carlos E.R. wrote:
On 19/11/2018 20.31, Per Jessen wrote:
Carlos E.R. wrote:
On 19/11/2018 18.54, Andrei Borzenkov wrote:
19.11.2018 19:26, Scott Simpson пишет:
OpenSUSE Tumbleweed 20181116
One option when mounting nfs is to specify version:
(fstab) SomeMachine:/data/nfs/ /data/nfs nfs4 noauto,nofail,_netdev,user,users,lazytime 0 0
"nfs" means nfs version 3.
Correction, as a mount option, it means 4, then 3.
There have been reasons to use that, but given that Scott's setup used to work, that is most likely not a solution here.
I mean that an update may have changed the default assumptions - he is running TW, after all.
True, I ignored that.
I do not mean to use fstab, but there will be a way to specify nfs version in the command line.
Yes, same as in fstab. -- Per Jessen, Zürich (1.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrei Borzenkov -
Carlos E.R. -
Dave Howorth -
Per Jessen -
Scott Simpson