[opensuse] problem with nfs mount
I have a server exporting, nfsserver (localhost): /home/<user> *(rw,root_squash,sync,no_subtree_check) no errors from setup or "systemctl restart nfsserver" then status nfsserver. Feb 06 17:04:17 wahoo nfsserver[10485]: Starting kernel based NFS server: idmapd mountd statd nfsd sm-notify..done Feb 06 17:04:17 wahoo systemd[1]: Started LSB: Start the kernel based NFS daemon. client is set: enable nsf4 no security local open firewall port defaulst,_netdefv,bg,retry=5,sec=none 17:09 Crash: ~ # systemctl status nfs -l nfs.service - LSB: NFS client services Loaded: loaded (/etc/init.d/nfs) Drop-In: /run/systemd/generator/nfs.service.d └─50-insserv.conf-$remote_fs.conf Active: active (running) since Thu 2014-02-06 15:01:24 EST; 2h 8min ago Process: 4404 ExecStart=/etc/init.d/nfs start (code=exited, status=0/SUCCESS) CGroup: /system.slice/nfs.service └─4478 /usr/sbin/rpc.gssd -D -p /var/lib/nfs/rpc_pipefs Feb 06 15:01:24 Crash rpc.gssd[4478]: ERROR: Key table file '/etc/krb5.keytab' not found while beginning keytab scan for keytab 'FILE:/etc/krb5.keytab' Feb 06 15:01:24 Crash rpc.gssd[4478]: ERROR: Key table file '/etc/krb5.keytab' not found while beginning keytab scan for keytab 'FILE:/etc/krb5.keytab' Feb 06 15:01:24 Crash rpc.gssd[4478]: ERROR: Key table file '/etc/krb5.keytab' not found while beginning keytab scan for keytab 'FILE:/etc/krb5.keytab' Feb 06 15:01:24 Crash rpc.gssd[4478]: ERROR: Key table file '/etc/krb5.keytab' not found while beginning keytab scan for keytab 'FILE:/etc/krb5.keytab' Feb 06 15:01:24 Crash rpc.gssd[4478]: ERROR: Key table file '/etc/krb5.keytab' not found while beginning keytab scan for keytab 'FILE:/etc/krb5.keytab' Feb 06 15:01:24 Crash rpc.gssd[4478]: ERROR: Key table file '/etc/krb5.keytab' not found while beginning keytab scan for keytab 'FILE:/etc/krb5.keytab' Feb 06 15:01:24 Crash rpc.gssd[4478]: ERROR: gssd_refresh_krb5_machine_credential: no usable keytab entry found in keytab /etc/krb5.keytab for connection with host wahoo.wahoo.no-ip.org Feb 06 15:01:24 Crash rpc.gssd[4478]: ERROR: No credentials found for connection to server wahoo.wahoo.no-ip.org Feb 06 15:01:24 Crash nfs[4404]: ..done Feb 06 15:01:24 Crash systemd[1]: Started LSB: NFS client services. Kerberos is *not* set. and I cannot access nfs_share /home/<user> Yesterday this worked and at the present I have several other shares similarly configured that *do* work. What am I missing and why the key table file error. Maybe related or not: I also see in the server logs: 2014-02-06T17:16:50.746342-05:00 wahoo nscd: nss-ldap: do_open: do_start_tls failed:stat=-1 2014-02-06T17:16:50.749124-05:00 wahoo nscd: nss-ldap: do_open: do_start_tls failed:stat=-1 2014-02-06T17:16:50.749811-05:00 wahoo nscd: nss_ldap: could not search LDAP server - Server is unavailable But I do not have (ever) ldap configured/activated. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 2014-02-06 at 17:22 -0500, Patrick Shanahan wrote:
CGroup: /system.slice/nfs.service └─4478 /usr/sbin/rpc.gssd -D -p /var/lib/nfs/rpc_pipefs
Feb 06 15:01:24 Crash rpc.gssd[4478]: ERROR: Key table file '/etc/krb5.keytab' not found while beginning keytab scan for keytab 'FILE:/etc/krb5.keytab'
Hi There's a rpc.gssd instance started. It's gonna look for Kerberos. Workaround: start nfs then immediately kill rpc.gssd If you used Yast, make sure the gss security box is unchecked. Definitive: Don't know. L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* lynn
On Thu, 2014-02-06 at 17:22 -0500, Patrick Shanahan wrote:
CGroup: /system.slice/nfs.service └─4478 /usr/sbin/rpc.gssd -D -p /var/lib/nfs/rpc_pipefs
Feb 06 15:01:24 Crash rpc.gssd[4478]: ERROR: Key table file '/etc/krb5.keytab' not found while beginning keytab scan for keytab 'FILE:/etc/krb5.keytab'
There's a rpc.gssd instance started. It's gonna look for Kerberos. Workaround: start nfs then immediately kill rpc.gssd
tks, will try and report
If you used Yast, make sure the gss security box is unchecked.
it is on client and server
Definitive: Don't know.
tks, it's the only information I have received. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan
* lynn
[02-07-14 12:13]: On Thu, 2014-02-06 at 17:22 -0500, Patrick Shanahan wrote:
CGroup: /system.slice/nfs.service └─4478 /usr/sbin/rpc.gssd -D -p /var/lib/nfs/rpc_pipefs
Feb 06 15:01:24 Crash rpc.gssd[4478]: ERROR: Key table file '/etc/krb5.keytab' not found while beginning keytab scan for keytab 'FILE:/etc/krb5.keytab'
There's a rpc.gssd instance started. It's gonna look for Kerberos. Workaround: start nfs then immediately kill rpc.gssd
tks, will try and report
If you used Yast, make sure the gss security box is unchecked.
it is on client and server
Definitive: Don't know.
tks, it's the only information I have received.
Well, that appears to stop the krb5.keytab err msgs, but doesn't stop the server rejection when trying to nfs mount /home/paka: mount.nfs: access denied by server while mounting 192.168.1.3:/home/paka with no other explanation :^( tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2014-02-07 20:15, Patrick Shanahan wrote:
with no other explanation :^(
Try "mount -v ..." - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlL1Pk4ACgkQja8UbcUWM1xxJgD/fmXbANEmRtl9OYKkVTJp3Jtv BuwrlkQirEFQqo4jF0sA/3mtET7fVyXXqHIxJuKIButkeTGz5nFOkBo1kI7ZB+cY =30hI -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Carlos E. R.
On 2014-02-07 20:15, Patrick Shanahan wrote:
with no other explanation :^(
Try "mount -v ..."
should have thought of that, duh mount -vt nfs4 192.168.1.3:/home/paka /mnt/paka mount.nfs4: timeout set for Fri Feb 7 15:44:36 2014 mount.nfs4: trying text-based options 'addr=192.168.1.3,clientaddr=192.168.1.10' mount.nfs4: mount(2): Stale file handle mount.nfs4: trying text-based options 'addr=192.168.1.3,clientaddr=192.168.1.10' mount.nfs4: mount(2): Stale file handle so I stopped the server, stopped the client, restarted the server and then the client, and: mount -vt nfs4 192.168.1.3:/home/paka /mnt/paka mount.nfs4: timeout set for Fri Feb 7 15:44:36 2014 mount.nfs4: trying text-based options 'addr=192.168.1.3,clientaddr=192.168.1.10' mount.nfs4: mount(2): Stale file handle mount.nfs4: trying text-based options 'addr=192.168.1.3,clientaddr=192.168.1.10' mount.nfs4: mount(2): Stale file handle So I will completely reboot the client and report... tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan
* Carlos E. R.
[02-07-14 15:14]: On 2014-02-07 20:15, Patrick Shanahan wrote:
with no other explanation :^(
Try "mount -v ..."
should have thought of that, duh
mount -vt nfs4 192.168.1.3:/home/paka /mnt/paka mount.nfs4: timeout set for Fri Feb 7 15:44:36 2014 mount.nfs4: trying text-based options 'addr=192.168.1.3,clientaddr=192.168.1.10' mount.nfs4: mount(2): Stale file handle mount.nfs4: trying text-based options 'addr=192.168.1.3,clientaddr=192.168.1.10' mount.nfs4: mount(2): Stale file handle
so I stopped the server, stopped the client, restarted the server and then the client, and:
mount -vt nfs4 192.168.1.3:/home/paka /mnt/paka mount.nfs4: timeout set for Fri Feb 7 15:44:36 2014 mount.nfs4: trying text-based options 'addr=192.168.1.3,clientaddr=192.168.1.10' mount.nfs4: mount(2): Stale file handle mount.nfs4: trying text-based options 'addr=192.168.1.3,clientaddr=192.168.1.10' mount.nfs4: mount(2): Stale file handle
So I will completely reboot the client and report...
Same result. How do you get a "Stale File Handle" that survives a cold boot? Seems the stale file handle must be occuring on boot from the fstab entry during initial nsf instance or .... Will remove fstab entry, or set to noauto, and reboot ... brb -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan
* Patrick Shanahan
[02-07-14 15:47]: [...] So I will completely reboot the client and report...
Same result. How do you get a "Stale File Handle" that survives a cold boot? Seems the stale file handle must be occuring on boot from the fstab entry during initial nsf instance or ....
Will remove fstab entry, or set to noauto, and reboot ... brb
So, I shutdown the client and rebooted the server. Then started the client and still get "Stale File Handle". wtf, is this *really* possible? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* Patrick Shanahan
* Patrick Shanahan
[02-07-14 16:16]: * Patrick Shanahan
[02-07-14 15:47]: [...] So I will completely reboot the client and report...
Same result. How do you get a "Stale File Handle" that survives a cold boot? Seems the stale file handle must be occuring on boot from the fstab entry during initial nsf instance or ....
Will remove fstab entry, or set to noauto, and reboot ... brb
So, I shutdown the client and rebooted the server. Then started the client and still get "Stale File Handle". wtf, is this *really* possible?
The Question: server exports nfs4 /home/paka client cannot mount w/nfs4, results "Stale File Handle" Apparently nfs4, and maybe earlier, does not like the export: /home/paka I exported from the server with all the same parameters +crossmnt, /home, and can nfs4 mount /home/paka on the client, no err msgs. Is this clear as mud? Or are the questions wrong? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-02-07 19:03 (GMT-0500) Patrick Shanahan composed:
The Question: server exports nfs4 /home/paka client cannot mount w/nfs4, results "Stale File Handle"
Apparently nfs4, and maybe earlier, does not like the export: /home/paka
I exported from the server with all the same parameters +crossmnt, /home, and can nfs4 mount /home/paka on the client, no err msgs.
Is this clear as mud? Or are the questions wrong?
I don't know, but as it seems this thread has almost entirely written by you, maybe a look elsewhere would be in order. The linux-nfs list has seemed rather busy lately. http://www.spinics.net/lists/linux-nfs/ -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 2014-02-07 at 18:46 -0500, Patrick Shanahan wrote:
* Patrick Shanahan
[02-07-14 16:16]: * Patrick Shanahan
[02-07-14 15:47]: [...] So I will completely reboot the client and report...
Same result. How do you get a "Stale File Handle" that survives a cold boot? Seems the stale file handle must be occuring on boot from the fstab entry during initial nsf instance or ....
Will remove fstab entry, or set to noauto, and reboot ... brb
So, I shutdown the client and rebooted the server. Then started the client and still get "Stale File Handle". wtf, is this *really* possible?
There's confusion stemming from when nfs4 HAD to be exported from a pseudo root which you bind mounted your exports to. That changed back to the good old and well documented nfs3 style exports a few years back. Some no nonsense info: http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration HTH L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* lynn
On Fri, 2014-02-07 at 18:46 -0500, Patrick Shanahan wrote:
* Patrick Shanahan
[02-07-14 16:16]: * Patrick Shanahan
[02-07-14 15:47]: [...] So I will completely reboot the client and report...
Same result. How do you get a "Stale File Handle" that survives a cold boot? Seems the stale file handle must be occuring on boot from the fstab entry during initial nsf instance or ....
Will remove fstab entry, or set to noauto, and reboot ... brb
So, I shutdown the client and rebooted the server. Then started the client and still get "Stale File Handle". wtf, is this *really* possible?
There's confusion stemming from when nfs4 HAD to be exported from a pseudo root which you bind mounted your exports to. That changed back to the good old and well documented nfs3 style exports a few years back. Some no nonsense info: http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration
Yes, that offeres a ?possible? but quite convoluted answer. And seems to want to put nfs4 into an "expert admin" class while claiming the opposite. I am happy that I *finally* solved my "situation" but have *no* idea if the route I followed is in any way correct except in the end result! tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 2014-02-08 at 14:47 -0500, Patrick Shanahan wrote:
* lynn
[02-08-14 14:04]: On Fri, 2014-02-07 at 18:46 -0500, Patrick Shanahan wrote:
* Patrick Shanahan
[02-07-14 16:16]: * Patrick Shanahan
[02-07-14 15:47]: [...] So I will completely reboot the client and report...
Same result. How do you get a "Stale File Handle" that survives a cold boot? Seems the stale file handle must be occuring on boot from the fstab entry during initial nsf instance or ....
Will remove fstab entry, or set to noauto, and reboot ... brb
So, I shutdown the client and rebooted the server. Then started the client and still get "Stale File Handle". wtf, is this *really* possible?
There's confusion stemming from when nfs4 HAD to be exported from a pseudo root which you bind mounted your exports to. That changed back to the good old and well documented nfs3 style exports a few years back. Some no nonsense info: http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration
Yes, that offeres a ?possible? but quite convoluted answer.
Good enough for us to go cifs throughout. Fast, predictable, Kerberos out of the box if you want it and almost understandable doco.
And seems to want to put nfs4 into an "expert admin" class while claiming the opposite.
I am happy that I *finally* solved my "situation" but have *no* idea if the route I followed is in any way correct except in the end result!
tks,
Glad you got it going. L x
-- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
* lynn
On Sat, 2014-02-08 at 14:47 -0500, Patrick Shanahan wrote:
* lynn
[02-08-14 14:04]: [...] There's confusion stemming from when nfs4 HAD to be exported from a pseudo root which you bind mounted your exports to. That changed back to the good old and well documented nfs3 style exports a few years back. Some no nonsense info: http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration
Yes, that offeres a ?possible? but quite convoluted answer.
Good enough for us to go cifs throughout. Fast, predictable, Kerberos out of the box if you want it and almost understandable doco.
Well, I don't see yast handing cifs and I would have to research it while I do have a *small* understanding nfs and have used it before. cifs would be rather expensive in time for me to change, expecially since I have nfs working now.
And seems to want to put nfs4 into an "expert admin" class while claiming the opposite.
I am happy that I *finally* solved my "situation" but have *no* idea if the route I followed is in any way correct except in the end result!
tks,
Glad you got it going.
tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 2014-02-08 at 16:05 -0500, Patrick Shanahan wrote:
* lynn
[02-08-14 15:33]: On Sat, 2014-02-08 at 14:47 -0500, Patrick Shanahan wrote:
* lynn
[02-08-14 14:04]: [...] There's confusion stemming from when nfs4 HAD to be exported from a pseudo root which you bind mounted your exports to. That changed back to the good old and well documented nfs3 style exports a few years back. Some no nonsense info: http://wiki.linux-nfs.org/wiki/index.php/Nfsv4_configuration
Yes, that offeres a ?possible? but quite convoluted answer.
Good enough for us to go cifs throughout. Fast, predictable, Kerberos out of the box if you want it and almost understandable doco.
Well, I don't see yast handing cifs
Eh? It's covered better than nfs. It's called Samba! L x -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (4)
-
Carlos E. R.
-
Felix Miata
-
lynn
-
Patrick Shanahan