From: John Hughes <john@Calva.COM>
To: linux-nfs@vger.kernel.org
Subject: [BUG] nfs4 client loops printing "Error: state manager encountered RPCSEC_GSS session expired" if kerberos ticket expires
Date: Thu, 10 Nov 2011 17:11:23 +0100 [thread overview]
Message-ID: <4EBBF7AB.8030907@Calva.COM> (raw)
We mount user home directories (using automount) from an nfs4 server
with sec=krb5.
Using older kernels (2.6.32 for example) when the user ticket expires
attempts to access the mount get EPERM. This is no big deal, the
workstation is probably in the screensaver so the user enters her
password, a new ticket is granted and everything carries on.
At some point (before or after 2.6.39) this behaviour changed.
Now attempts to access the mount point hang and an endless stream of:
Error: state manager encountered RPCSEC_GSS session expired against NFSv4 server xxxx
messages is printed to the kernel log. The user doesn't get prompted
for a password and can only get a new ticket by moving to a text console
and logging in again (which unblocks things).
(This is Debian bug
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648155 and Ubuntu bug
https://bugs.launchpad.net/ubuntu/+bug/794112 ).
The client is Debian Sid, with kernel 3.1.0-rc10 on a Dell core i5 based
Optiplex 390. (The same problem occurs in the standard Debian 3.0 kernel).
Linux cretic 3.1.0-rc10 #1 SMP Thu Nov 10 11:45:46 CET 2011 x86_64 GNU/Linux
The server is Debian Squeeze, kernel 2.6.32.
What should I be trying to do to debug this?
next reply other threads:[~2011-11-10 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 16:11 John Hughes [this message]
2011-11-14 14:33 ` [BUG] nfs4 client loops printing "Error: state manager encountered RPCSEC_GSS session expired" if kerberos ticket expires John Hughes
2011-11-16 10:42 ` John Hughes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EBBF7AB.8030907@Calva.COM \
--to=john@calva.com \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox